Mode Off functionality

[Zebur]

Hi,

1) I have seen other members talk about this 3 years ago - Is there really no 'Mode off' action?
I simply need something to happen when a mode turns off. The fact this is not available is absolutely annoying as some specific functions (like Control Smart things) have their own 'when mode ends' functionality. Routines are not enough as they can only Turn a mode on, not turn it off (!).

2) On a similar note, why are there no settings for when a mode automatically deactivates? I set my work mode to start when GPS hits the office and I THINK it turns off when I leave but it is not clarified anywhere and I can't modify it if I wanted it to be kept on after I leave.
Similarly, if Driving mode turns on when it connects to Android Auto/Connects to BT, does that mean it turns off when it disconnects? Who decides on that functionality and how am I to know if it works that way?

Thanks

[realaud]

You can absolutely automate a mode's activating and deactivating.
Go into the mode in question to edit it and set the activation/deactivation parameters. For example, to edit sleep mode, go to modes and routines, select sleep mode, and in the section where it says "turn on automatically", enter the the condition (sleep schedule, sleeping, other condition).  When the condition is met, the mode will go on automatically, when the condition no longer is active, the mode turns off.  So if you set it to be on from 11:00 p.m. to 6:00 a.m. the next day, it will automatically turn on at 11 p.m. and turn off at 6:00 a.m.   Similarly, you can set conditions for any mode to turn on/off automatically, or create a custom mode.  You can create a routine to do several things a mode won't do - you can have it turn on the mode with certain triggers along with other things you might want to have done automatically while a mode is active.  (there's no need to use a routine when you can automate the mode, unless you want other things to happen at the same time that you can't add to a mode).

You can run multiple routines simultaneously as long as their actions don't conflict, but only one mode can be active at a time.  Even if you automate a mode, you can still turn it on and off manually whenever you choose to.  If you set your work mode to go on when you hit your office, when you are no longer in your office it should turn off automatically, as the condition for the trigger no longer applies. 

You can tell if a mode is on by the icon on your status bar (one of the few icons that still show on the primary status bar) lock screen and AOD. You might be better off setting it for a time period, rather than location if you work regular hours.  And, yes, if driving mode is set to turn on when you connect to your car's BT, then it will automatically turn off when you are no longer connected to the car.  Actually,*you* decide the functionality.  You don't have to have it automatically start when it's connected to the car's BT, you can use another trigger.  Once again, you can edit any of the triggers and add other triggers and select whether they will activate when any or all of the conditions are met.  They will end automatically when none of the conditions are met, so if you set a time and location for work mode and select "any of the conditions", it will trigger when either condition is met but turn of only when no triggers are active, so if you step out of your office for lunch, it will still be in work mode unless you either manually turn it off or it is also after the time period you set.  If you only set it by location, if you step out of your office, it will deactivate and reactivate when you return.  Both modes and routines are very flexible.

The screen shot below shows the theater mode active on my status bar.  Whatever mode you have active at any given time will have its icon shown there, along with the do not disturb icon if the mode includes dnd.  If you don't see the icon there, then the mode has been deactivated automatically per the parameters you set.  If you see the icon, you know the mode is active.

[realaud]

I think I may need to correct myself here.  You are likely better off with routines to trigger both driving mode and work mode.

You can configure your work mode for manual activation (which, as stated can also be automated, but I think it's best you add the time frame to it if you are going to do that), and then create a routine with the location and time trigger and set it to start the mode when either or both of those conditions are met.  As for driving mode, if you have it configured to trigger when you are connected to the car's BT, it should deactivate when you are no longer connected to it.  Or, you can create a routine for driving and configure it the same way driving mode is configured and it will run when the parameters are met and stop when no longer applicable.  Routines have a definite end process that reverts to the state your device was in prior to the routine running, and you can add custom actions to the end routine, if you want other stuff to happen.  Since, as I said, only one mode can be active at a time, and and the possibility exists that driving mode may conflict with work mode, you can make either or both a routine. Making them both routines will give you the assurance that you need that the actions will revert when the conditions are no longer met.  What are you trying to accomplish with driving mode?  Personally, I don't find it necessary, since when the phone is connected to the car's BT,  calls are hands free anyway.  Some people may need it if they have older cars without BT, but it would have to be a really old car.  I think cars have had BT connectivity since at least 2014.

[Zebur]

Thanks for the reply. I wrote the post with a very specific action in mind - I wanted a thing to happen (an app to open) once 'Mode off'. Your response does not seem to confirm that to be possible. I am only able to select what happens if 'Mode on', and then the reverse can happen if it goes off automatically. Routines also only feature 'When routine ends' if there is already an action that can be reversed (e.g., Return Power saving mode to what it was before). I am still unable to simply select - 'When a mode turns off, Open App'.

Obviously, I can circumvent that with another routine like 'When car BT disconnects, open app' but that is exactly my point - I need to work around that when it should have been a basic functionality to begin with.
If I need to achieve something similar and the BT workaround cannot be used, I will be stuck.

[realaud]

If you create an automated trigger for modes, when the conditions for the trigger are no longer met, the mode should end.  By adding the time frame to the automation trigger, it insures the mode will end at a specific time.  My preference is for routines over modes in most cases, as it's easier to see and set the end action for reversal of the trigger conditions and end whatever restrictions I put on. My modes I generally activate/deactivate manually. As I don't have a specific schedule for when I use them  - even sleep mode, as my bedtime varies.  Since your concern is with the ending of the mode or the reversal of actions, your best bet would be to use routines rather than modes. they are somewhat interchangeable, but you can generally add more flexibility into a routine.  And, as I said, only one mode can be active at a time, while routines can run concurrently and overlap.  If, for instance, you had work mode on, and needed to drive somewhere to perform a work function, driving and work mode cannot be active at the same time.  Using the work mode, though, by leaving the location that was used as a trigger, would likely turn off the mode, and when you connect to your car, driving mode would take over.  Many people automate their modes, and I have never heard a complaint about the mode not deactivating when it was supposed to. Except in the instance where modes and routines had a glitch and were just not working properly at all.  So, you are either not understanding how automation of the modes work, or not configuring your modes properly.  Modes and routines is the single best feature of Samsung devices.

I also told you that you will always know when a mode (and which mode) is active by the icon on the status bar.  No icon, no mode is running or has been de-triggered (ended).  Any mode, or routine, can be started and ended manually, even if you have them automated.  You don't need to work around anything, you just need to use the correct parameters.

Whether you automate a mode, or turn it off manually, it's actions will reverse themselves to return your phone to its normal state.  The only difference between modes and routines in that respect is that the routines usually show the end action (not all of them do show it).  But, if knowing the end action will reverse the actions is important to you, you are much better off using routines rather than modes.

[Zebur]

This does not really answer my question - Can I have a 'When Mode/Routine ends -> Open App' function? It sounds like I can't.

[realaud]

No. You have to do that with a routine. You can have the routine start your mode as configured, then you can add the open app action to the when routine ends action. Which is why routines are generally better than modes for certain things - more actions and more flexibility. Sorry. I misunderstood your original question.

[Zebur]

'When routine ends' only allows me to revert actions. There is no revert action causing an App to Open.

If there was, that would still mean an app would open when mode becomes active, which is not something I want to happen.

 

[realaud]

You can create a second routine:  

trigger:  Driving ended

actions: open app (select app)

This type of routine has no end action, so when your app opens and you use it it will close when you normally close it.  It will work without conflicting with either driving mode (if you choose not to use the routine) or the drive mode routine.  It will simply trigger after the other routine  or mode ended.

Some routines have end actions that are automatic and some have no end actions.  It depends on what you are asking the routine to do.  Generally any routine that causes a change in settings will have an end action of the reversal of the action automatically added, but you have options on what the end action will do - reverse the original actions, keep the current condition or do a custom action pertaining to the original action.  

I am slightly curious why you would need find hub opened in driving mode.  Or is that the app you want opened when driving mode ends? Is it just a placeholder app to indicate you want an app to open?