jsimbol
-
3 votesdeclined ·
AdminCarter
(Admin, two forty four a.m.)
responded
This setting cannot be configured by third party apps such as Locale. This is because the location providers are secured settings, which only Android itself is allowed to change.
I think you might have some incorrect information regarding battery usage. The Android network location provider uses almost 0 power. Regardless of how frequently it updates, it uses information that is already available to the phone, such as which tower the device is connected to. Since that information is already available, the cost of the network location provider is almost free.
jsimbol
commented
·
Carter,
While I believe the first part of your response (after looking into it), I still have to disagree about the power issue. Watch the logcat output of the phone for a few minutes while the screen is turned off and nothing is being used up front (wifi and gos can be turned off too). You'll see every minute that the OS issues a wakelock, does an injectGPSposition and then goes back to sleep. "D/libgps ( 1131): GpsInterface_inject_location( 41.xxxxx, −72.xxxxx, 3510.000)" The total of those calls is killing battery.
If you disable the location service (uncheck "use wireless networks") then the polling completely stops, the "partial wake usage" of the OS goes way down and battery life goes up.jsimbol
commented
·
Carter,
While I believe the first part of your response (after looking into it), I still have to disagree about the power issue. Watch the logcat output of the phone for a few minutes while the screen is turned off and nothing is being used up front (wifi and gos can be turned off too). You'll see every minute that the OS issues a wakelock, does an injectGPSposition and then goes back to sleep. "D/libgps ( 1131): GpsInterface_inject_location( 41.xxxxx, −72.xxxxx, 3510.000)" The total of those calls is killing battery.
If you disable the location service (uncheck "use wireless networks") then the polling completely stops, the "partial wake usage" of the OS goes way down and battery life goes up.jsimbol
shared this idea and gave it 3 votes
·
-
774 votesunder review ·AdminCarter
(Admin, two forty four a.m.)
responded
The original request here was for a logical NOT operator, although it doesn’t make sense to create a logical NOT operator in Locale. Most of the time, NOT isn’t the right way of thinking about a Condition. For example, NOT 9 am to 5 pm could be redefined as 5pm to 9am. NOT at work would simply be the Default situation. For the other conditions built-in to Locale, thinking about the problem in a different way usually means that NOT isn’t needed. If a Condition truly needs NOT logic, then that should probably be put into the individual Condition’s UI itself rather than as part of the Edit Situation screen in Locale.
Although this request is for a NOT operator, I believe the underlying request here is a way of detecting the transition between situations. The strongest use case would be detecting when you’ve left a particular Location. While Locale… more
jsimbol
gave this 3 votes
·
Carter,
While I believe the first part of your response (after looking into it), I still have to disagree about the power issue. Watch the logcat output of the phone for a few minutes while the screen is turned off and nothing is being used up front (wifi and gos can be turned off too). You'll see every minute that the OS issues a wakelock, does an injectGPSposition and then goes back to sleep. "D/libgps ( 1131): GpsInterface_inject_location( 41.xxxxx, −72.xxxxx, 3510.000)" The total of those calls is killing battery.
If you disable the location service (uncheck "use wireless networks") then the polling completely stops, the "partial wake usage" of the OS goes way down and battery life goes up.