Keep current Situation until a new one is found, or if not, THEN Default
I'm tired of having Locale check every so often not find a location for a minute and set to Default, leaving window for that minute where stuff can make noise, or my Wifi shuts off, or whatever. Can the Default really be a last resort?
janiskfp
shared this idea
If Locale can’t determine your location, it assumes that you’re still at the same location you were last at.
What you describe would only happen if there is extremely bad location data in your area. E.g. cell tower locations place you completely outside of the location you defined (e.g. no overlap of the circles at all). Once Google told me I was in New Jersey, when I was actually in Boston. Given such terrible data, there’s really nothing Locale can do.
You can disable Google’s location service, which might improve your accuracy. This is the “Use Wireless Networks” under the Android location settings. Turning this off may increase or decrease battery usage, depending on your environment.
3 comments
-
AdminCarter
(Admin, two forty four a.m.)
commented
@janiskfp:
Hypothetical: Let's say you have a Time-based situation, an orientation-based situation, and defaults. All three are satisfied. The time based situation ends. The orientation based situation would take over and any settings in the orientation-based situation would override defaults. Defaults would not override the orientation-based situation during this transition.
The only time what you describe might happen is when a situation's conditions aren't satisfied yet. E.g. if the orientation-based situation wasn't satisfied yet, then Defaults would indeed take over.
Regarding your second question: Locale *could* determine your location with instantaneous, perfect accuracy. But then your battery would be dead within 4 hours. I don't think 4 hour battery life would meet your needs though.
-
janiskfp
commented
By the way, Google Maps, Browser, Car Locator, Sherpa, Layar, Waze, Hoccer, GPS status, iMap Weather, even Weather Forecast Widget can find my accurate location is less than 30 seconds, usually about 3-5 seconds, while Locale is still hanging on to lower-priority Situations and not enabling the Situation that is associated with my current location, sometimes for up to about 8 or so minutes, even when I disable and re-enable Locale. I don't really have the need for faster switching than that, but I have had a heck of a time understanding why that happens like it does. I always have my GPS enabled unless my battery is less than 15% just because I want as accurate and fast a location as I can get, and the battery charge is worth it to me. Is there anything I can do, besides maybe disabling "Use wireless Networks" to improve the speed of location-dependent Situations?
-
janiskfp
commented
I guess I wasn't clear.
I'm not talking necessarily about location, I was addressing the behavior of Situation switching. What happens on my phone is that between most switches, via time, the calendar plugin, shake, or whatever, the Default Situation becomes enabled first (and only), then after that the new applicable Situation (or the current Situation, if that's what's fits).
I was wondering if there could be a 30-60 second delay (maybe as an option) to release the current Situation while the new one is being activated, then after that release the former Siuation when the new one is actually Active.
