Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,769,453 Members 41,639 Now Online
XDA Developers Android and Mobile Development Forum

location settings and battery drain

Tip us?
 
jmichaels1982
Old
(Last edited by jmichaels1982; 2nd February 2014 at 11:29 PM.)
#1  
jmichaels1982's Avatar
Senior Member - OP
Thanks Meter 258
Posts: 605
Join Date: May 2011
Location: Long Island, NY
Default location settings and battery drain

I am confused in regard to two settings that I have noticed affects my idle battery drain significantly , even though my phone sleeps well with them on :

1- Google Wi-Fi & mobile location
2- and under advanced Wi-Fi settings: always allow scanning

I finally , after years of struggle with Android, have managed to achieve battery lives like people claim. My problem was Immense drain during idle time. My phone can never survive the say without the need for charging. Even when I am not touching.

After putting compulsion kernel and turning these two off, underclocking my cpu to 97 mhz and 2ghz on wheatley governor, my phone is sitting at 77 % 1 day and 3 hours idling . I left all services syncing on , including gvoice and whatsapp. I dont have facebook or twitter. It has also been on LTE this entire time and GPS on.

This is not really a battery stats thread.

My question is , Idle stats are really important to me, and i dont really understand the use for the above mentioned options and the difference between the two. Are they vital for anything at all ? can i leave them off al the time without any significant location deterioration ?


Thank you all !
Attached Thumbnails
Click image for larger version

Name:	2014-02-02-18-21-53.jpg
Views:	150
Size:	128.0 KB
ID:	2555675   Click image for larger version

Name:	2014-02-02-18-22-08.png
Views:	186
Size:	179.8 KB
ID:	2555676   Click image for larger version

Name:	2014-02-02-18-23-15.jpg
Views:	155
Size:	146.6 KB
ID:	2555677   Click image for larger version

Name:	2014-02-02-18-23-32.jpg
Views:	140
Size:	124.0 KB
ID:	2555678  
Ask not what your developer can do for you, ask what you can do for your developer.


'Tis better to be silent and be thought a fool, than to speak and remove all doubt.
 
bftb0
Old
(Last edited by bftb0; 3rd February 2014 at 08:23 PM.)
#2  
Senior Member
Thanks Meter 795
Posts: 2,122
Join Date: Feb 2010
<speculation>

#1 is only a grant of permission to collect location data from your handset - but not a power management control. It might mean that a small amount of additional data traffic occurs when either GPS or WiFi are already on - but doesn't affect *whether* those devices (WiFi and GPS) are powered up. So it applies at all times but is only meaningful when those devices are enabled by other means - either manually or automatically. Think of it as nothing other than a legal escape hatch for Google against privacy violation lawsuits.

#2 allows the *WiFi* hardware to be powered up for *reception* (probably with no indication that it is indeed dissipating power!) - but it won't try to associate and connect with any WiFi APs that you have set up. It is listening for beacons only*, and possibly band-hopping, if not channel hopping**. Think of it as "receive only WiFi"

It is my *guess* that #1 affects #2 - there shouldn't be any data collection if you have not allowed it so the #2 toggle state should not do anything if #1 is set to disable.

Having the WiFi radio in receive-only mode might not really use any noticeable amount of power for two reasons: 1st, because operating a radio in Rx mode only uses far less power than Tx mode, and 2nd because it is possible that when both #1 & #2 are enabled, the WiFi radio is only polled, rather than left on full-time. So, it's duty cycle might be extremely low.

</speculation>

None of the above speculation has been confirmed by me by looking at source code.

Whether or not this is important to you depends on your need for high precision location information. Parents that snoop on their kids' handset locations might want that WiFi listener stuff turned on - GPS does not work indoors in many locations.

HTH


* note that the geolocation databases (that map WiFi AP MAC addresses/SSIDs to lat/lon) are on Google servers, not on your phone - so this implies that there must be a way to get the data to Google even if the WiFi is "pseudo-off: receiving but not transmitting". Presumably this would then happen via the Mobile Data radio (LTE/CDMA/1xRTT)... which - perversely - would use even more power than a WiFi connection (for the same data).

**WiFi APs are supposed to broadcast their beacons on all channels (the beacon packet tells the STAs what the correct channel they should "talk" to the AP on). So it might be necessary to band-hop the receiver to account for single band APs, even if it is not strictly necessary to channel-hop within a band to observe available beacons. In any event, bear in mind that power usage by WiFi chips that are never transmitting is far lower than when transmission by the WiFi radio is also occuring.
"I'm gonna start coding placebo apps. That way I will be sure that the complaints are real and the praises hollow."
The Following User Says Thank You to bftb0 For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes