More Efficient Condition Checking
Please let me order my triggers so that it doesn't check the gps every ten minutes and then check the clock just to see that it's weekend and the trigger is disabled.
This is basically implemented in Locale 1.0. Locale 1.0 intelligently schedules situation updates. If a situation contains both a location and time condition, then Locale won’t schedule a wakeup until the time condition is met. Once the time condition is met, then location will be checked periodically.
You might still see Location is being checked rarely even while the Time condition isn’t met, as Locale may do a full refresh every once in a while. (For example, when launching the Locale UI, and sometimes when waking the screen, or during the transition between other situations.)
8 comments
-
AdminCarter
(Admin, two forty four a.m.) commented
@Kosi2801 K.:
I understand that you're trying to optimize your battery usage. The Android battery statistics are buggy and not correct, so please ignore them.We've found the only way to accurately gauge battery usage is to perform multiple trials using a stopwatch and measure how long it takes for the battery to drain completely. This is how we perform our own battery usage testing.
Locale is extremely efficient and is working as expected. While we are always improving Locale's efficiency, no changes are planned or necessary in this area as such changes would counter-intuitively increase Locale's CPU and battery usage.
-
Kosi2801 K.
commented
Would it be possible to also work on those "rare" re-checks? I recognize WLAN being enabled almost every time I turn on the screen even when none of my time-guarded location-situations apply. Currently my WLAN-usage with Locale is at 4% (I never need WLAN), I guess it could be as low as 1% when it would recognize the time-condition before checking location.
Android 2.2
-
webreaper
commented
I'd like to see this, but I think it's more a case of "make conditions work together properly".
I have a situation which has two conditions:
1. Time between 5pm and 8pm
2. Location is at railway stationThe idea is I want to tweet that I'm at the station for my homeward journey, so my wife has an idea of when to expect me.
However, it didn't seem to be working, so as well as the tweet I added a notification too - which fired at 5pm - despite me being nowhere near the station location.
It looks like the combination of conditions just isn't working right. It should ignore the location outside of the particular times, and should ignore the time unless I'm in the particular location.
-
ihsubandos
commented
Please make locale only check location when necessary! Also can you make the interval configurable so one situation would only check location every hour whilst another would check more often...
-
Jason71
commented
I agree that this should be handled internally but what I see is Locale hammering the GPS constantly when I am at work with no chance of finding a location. From 8 till 5 each week day work in a big concrete box with no WIFI and no view of the sky. As a result I use time to set my location. There is no higher priority situation so there is no need for Locale to check my position and yet it still does. Because there is no GPS signal it spends longer trying and therefore wastes more battery life with no chance of success and no benefit even if it managed it so why check location when it is not required?
-
Sturmeh
commented
Carter what I think he's saying is the code needs a way of understanding priorties, it's almost impossible for you to have to guess some of them, for example the program doesn't necessarily know you can't be at work on a Sunday.
If I want to save some work I'll make a pre-condition that it's a weekday, then I'm at work.
Possibly make it optional to make ordering strict or loose.
-
Marcus Gustafsson commented
Well, yes, more intelligent Locale would be nice, but I understand that the implementation of that is a lot harder than letting the user choose, since you allow costum triggers (if I'm not misstaken).
Also, sorry for the mail, I'm just not used to this kind of well-shaped feedback system.
-
Sturmeh
commented
This would also be solved by implementing this... http://feedback.twofortyfouram.com/pages/5655-locale-feedback/suggestions/322078-sub-situations?ref=title