This must be new to the 4.2 update. As I've never noticed it before.
Basically in the advanced settings menu for WiFi.
There are the following options:
Keep Wi-FI on during Sleep:
The Optimisation option is set to on by default. Potentially this could maybe be having the opposite effect with quite a few people stating batter draining quicker than ever which especially if this option works should be opposite if anything.
I'm going to try a drain and full charge then turn this option off and see what happens in terms of drain.
If anyone wants to try this or do it properly and timed etc would be helpful.
PLEASE Search for existing threads before posting a new one. Thanks.
Your opinion matters. But should you disagree - please try not to be disagreeable
Mobile OS devices personal pantheon...
ANDROID: Doogee DG310; SGS; Huawei Y300; Motoroloa Xoom 2ME; Razr; Defy Mini; CnM Touchpad II;
Asus TF101; Lenovo A1; Samsung Tab 2 7.0
APPLE: iPhone 4s; iPhone 5c; iPad 3; iPad Mini 2; iPad Air 2 64gb
CHROMEBOOK: HP 14-Q010sa Celeron 14 Inch 4GB 16GB Chromebook - White.
I'm still trying it with this option turned off..
Battery in settings is showing WiFi as using 67% battery. Previously this was around 40-50% with the setting on I think. Either way I'll let this drain out and try again with this on.
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Stock 4.2.1 Rooted.
UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE http://forum.xda-developers.com/show....php?t=2204100
I know it's fairly unreliable but if the % goes from being stated at 50% to around 65% their's clearly something causing a jump is my thinking!
I've found the battery monitor in Settings to be fairly enlightening, even though it's not 100% accurate. Keep in mind when looking at it, the listed apps and their usage have to add up to 100% (give or take), so there'll always be some app at the top of the list, even if nothing's consuming anything at a great rate.
I was initially disappointed with my TF700's battery life. I got both my TF700 and Nexus 7 to consume approximately 1-2% per 24 hour period with no use -- other than active standby, by turning off wiFi when the screen is off. On the TF700, I did this in two locations (the Asus settings and the WiFi advanced menu option).
My TF700 went back to it's 20-30% per 24-hour period with the latest Jelly Bean update. The battery monitor revealed that Google Maps was the culprit -- allegedly due to WiFi use. I suspect that Maps is/was attempting to obtain location by way of WiFi, despite me turning the setting off. I don't believe that Maps has the ability to subvert the WiFi service's setting in Android, and perhaps its failure was causing the app to continually wake up while trying. I successfully returned my TF700 to its 1-2% consumption by manually shutting off the GPS, which I presume caused Maps to quit trying...
I'm an Android developer, and I've messed around with plenty of various devices in recent years. The TF700 seems to be the most "frail" from a software perspective than any other device I've touched. Granted, I haven't handled any of those $50 android knockoff tablets, but the fit and form of the TF700 leaves a bit to be desired.
Actually, Maps activates GPS and wifi and ACTUALLY does bypass the wifi settings on this tab, meaning your tablet's wifi is still running. It has been a bug that have been here for awhile. I dont use maps so I disable it or dont install it for that reason. in a 8 hour period, I lost 1% on my tablet, none on dock, so about 3-4% per 24 hours, which is not bad at all.
I'll need to review some resources, but if I recall properly, there's some not-so-standard things that the Location Manager binder service does to interface with the actual GPS device driver and its associated hardware. My guess is that the TF700 is using a GPS receiver that's substantially different from other devices (I believe it has GLONASS support, where my N7 does not -- so a radically different chip and device driver is not out of the question).
I'll drill around in DDMS with the tablet in my spare time to see if I turn up anything obvious. Something's clearly out of whack, and it definitely smells like the Location Manager's underpinnings.