View Single Post
Posts: 203 | Thanked: 596 times | Joined on Jan 2015 @ Finland
#63
Originally Posted by zagrim View Post
This morning again the situation failed to change after leaving home...
My config goes like this:
  • At home: based on list of cell IDs, turn off mobile data and bluetooth and turn on wifi
  • At work: based on list of cell IDs, turn on mobile data and turn off wifi
(there's also "Near home" with situation!="At home" but since I had my wifi AP missing from the "At home" conditions, "Near home" wasn't actually working as meant at that time)

The cell ID sets consist of two non-adjanced physical areas, so basically the situation should've changed once on my way to the office and another time when I reached it. Now it did finally change after I modified the "At home" situation (added the missing wifi AP condition) which I guess triggered not only re-evaluation of that situation but also re-evaluation of all other rules since "At work" also got activated immediately. The phone was locked (device lock, display off) while I was on my way, but unlocking it had no effect.

Also, before leaving home I was experimenting with the "baseline" thing: I closed Situations app (swipe from top), went to settings and set things up as I want them to be when there's no situation active (or Situations is not running) and restarted Situations. The active situations were correct after start-up, but they didn't seem to affect the settings (e.g. mobile data was not turned off). Should I have also killed the background process (via Terminal) to have Situations completely shut down? Is the GUI process actually even needed for the rules to be effective?

Anyway, as I noticed that the settings were incorrect for the active situations, I manually deactivated "At home", which automatically activated "Near home" as it should (and I guess "At home" got automatically activated shortly after that). Thus, the app seemed to be running ok just before I left home.
Ok, not sure if this is related but there is currently an issues with the wakeup timer failing randomly (and quite rarely) that might cause the behavior you described. I'm hoping to have fixed it to the next update but really not sure if it is related. Need to see if there is something else that could be causing this.

The UI does not need to be running at all for Situations to work - there is a separate background process doing all the work. You can disable the app (including the backround process) via the settings page but it is not the same as abruptly stopping and restarting the app. To do that you need to kill the background process.
 

The Following User Says Thank You to hhaveri For This Useful Post: