Originally Posted by hhaveri

I haven't noticed such problems, but then again I haven't probably tested all possible scenarios with all conditions - like when phone is locked. So I'll check if I can find out something...

Originally Posted by zagrim

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.

Originally Posted by abyzthomas

Thank you for looking into it.

I did not mean "Device lock", when I said the when the phone is locked. I just meant when the screen is off. Device lock is not enabled on my phone.

As soon as I double tap to wake the phone up, situations app evaluates and does what it is supposed to do, depending on where I am. It works on all situations profiles correctly.

Is there a log or something I can send you that may help you trouble shoot?

Thanks for this great app. Even with this issue, it works great. I just have to wake the phone up when I want it to change the profile.

Originally Posted by zagrim

Uh, after the update it seems that cell ID based situations are not triggered anymore Or well, at least the one that should be active now doesn't get activated, not even by killing the app (well, it killed itself when I disabled it, is that supposed to happen?) or by trying to modify the situation condition (which seemed to do the trick before the update).

Tried creating a new situation with just cell ID condition, but so far it hasn't recorded any cells even though I have proper coverage here ATM.

edit: I'd go for remove & reinstall (as I've backed up .local/share/harbour-situations2application), unless there's something that could first be tried to figure out why it broke... @hhaveri?

Originally Posted by LVPVS

Hej,

I just noticed that when a Situation is triggered by an 'Accessory' that is my car kit, when the phone receives a call, it starts switching on and off the given Situation, as far as the call is received or declined.

When BT is the condition, the same car kit is connected, everything works fine. Only the power hogging nature of the BT condition is the problem.

LVPVS out.