[Battery Drain] [Lollipop] [LRX21O] - UPDATED 19-NOV-2014 - Nexus 5 Q&A, Help & Troubleshooting

Star & Report this issue to Google here: http://tinyurl.com/pgcmfma​********** UPDATE 19-NOV-2014 **********
Test 3: Battery Consumption Lollipop 5.0 [LRX21O] vs KitKat 4.4.4 [KTU84Q] (4h 30m)
[LINK TO POST IN THREAD HERE]​Scenario:
STOCK + ROOT + SELinux Mode (Permissive) + GSAM Battery Monitor (Root) + Whatsapp + Viber + Stock Apps Only
WiFi: ON
WiFi Notification: OFF
WiFi Scanning: OFF
Cellular Network Mode: 3G
NFC: OFF
Google Now: OFF
Brightness: AUTO/ADAPTIVE
OK Google: ON (Default)
Location Mode: High Accuracy
Location History: ON
Location Reporting: ON
Alarms: NO
Observations after 4h 30m:
Initial Charge: 100% (BOTH)
Remaining Charge: KitKat - 74% | Lollipop 67%
Power Consumption Per Hour: KitKat - 5.7% | Lollipop - 7.6% (~2%/hr MORE)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Total Battery Consumption: LOLLIPOP CONSUMES 7% MORE
[Note: In KitKat Phone & WiFi were significantly more used]
Application/Service Specific Battery Consumption: LOLLIPOP CONSUMES 8% MORE (APPROX)
[NOTE: KitKat Phone Call - 1h 45m while Lollipop Phone Call - 45m]
Screen Consumption: LOLLIPOP CONSUMES 11% MORE
Phone Radio: KitKat = LOLLIPOP
WiFi: LOLLIPOP CONSUMES 1.7% MORE (MATHEMATICALLY PROJECTED)
Conclusion:
Overall Battery Consumption of Lollipop is significantly higher than that of KitKat.
The default Battery Stats are inaccurate in Lollipop. It's accurate in KitKat.
WiFi shows as 'Always ON' in Lollipop's default battery stats but it is actually OFF and consumes no extra power. (Thanks to GSAM).
No 3rd Party Applications are causing drain in Lollipop. Neither is WiFi (Scanning always available or Network Notification or Whatever....)
Cast Services in Lollipop are not draining battery.
Project Volta & App Optimizations - Google Apps are expected to be optimized to consume less power. But it seems exactly the opposite.
Android System, Kernel (Android OS) & Google Play Services in Lollipop 5.0 consume 2.5 times more power to run than in KitKat 4.4.4 (6.1% vs 15.3%)
Extremely disappointed with Google. Lollipop 5.0 LRX21O has rendered the Nexus 5 unusable.
The Rest is for you to judge my friends.
Thanking everyone for their continued support. Keep Testing. Keep Reporting.
kyinx
********** END OF 19-NOV-2014 **********​
********** UPDATE 16-NOV-2014 **********
Test 2: Overnight Battery Drain [WiFi OFF] (8h 0m)
[LINK TO THIS POST HERE]
[SCREENSHOTS IN CONTENT BELOW]
Scenario:
Cleared Cache: YES
Initial Charge: 100%
WiFi: 0FF ***** Notice how the WiFi still remains ON in the Battery Stats - Screenshot 1 of Test 2.
Cellular Network Mode: 3G
NFC: OFF
Google Now: OFF
Location Mode: High Accuracy
Location History: ON
Location Reporting: ON
Alarms: NO
Observation:
Initial Charge: 100%
Remaining Charge: 85% (86% when the screenshot was taken, but dropped immediately)
Total Battery Use: 15%
Unreported Use (Hidden/Masked): 8%
Reported Battery Use: 7% (Summation of individual usage as per battery stats)
Note: 15% of battery consumption in 8h 0m results to 17.81% (18%) in 9h 32m (Mathematically). This is exactly same as Test 1's battery consumption i.e. with WiFi ON.
Whatsapp - 2%
Google Services - 1%
Phone Idle - 1%
Viber - 1%
Cell Standby - 1%
Android OS - 1%
[LINK TO THIS POST HERE]
Conclusion:
The [WiFi ON] battery drain has been consistent with [WiFi OFF] battery drain. [Test 1 = Test 2]
The WiFi service is somehow always ON whether we disable the WiFi or simple put the device in Airplane mode. This is a definite flaw with the OS.
An idle phone with WiFi ON has never ever consumed this much of battery - 16% overnight (as per Test 1). Today's test (Test 2) proves that there definitely is a WiFi Battery Drain Bug in the final version of Lollipop LRX21O.
Such high overnight battery consumption with either WiFi ON or OFF cannot be contributed only to the WiFi Bug. There are definitely other hidden battery drain issues other than this which Google knows but we do not.
50% of battery usage is still unaccounted/masked/hidden. The Developer Preview version of Lollipop shows that the Battery Stats are not incorrect. Hence I believe that Google does/did not want the users to know about the drain by MANIPULATING the stats.
It is now upto Google to come up, acknowledge this issue and fix it. They have already made a fool of themselves by releasing the Developer preview about 6 months back and still not being able to rectify the bug in the final release. I wonder if they actually are listening to us!
I thank all readers and participants of this thread for their support. Kindly continue tracking the battery usage and report observations and fixes if any..
[LINK TO THIS POST HERE]
kyinx
********** END OF 16-NOV-2014 **********​
********** UPDATE 15-NOV-2014 **********
Test 1: Overnight Battery Drain [WiFi ON] (9h 27m)
[LINK TO THIS POST HERE]
[SCREENSHOTS IN CONTENT BELOW]
Scenario:
Initial Charge: 100%
WiFi: 0N
Cellular Network Mode: 3G
NFC: OFF
Google Now: OFF
Location Mode: High Accuracy
Location History: ON
Location Reporting: ON
Alarms: NO
Observation:
Initial Charge: 100%
Remaining Charge: 82%
Total Battery Use: 18%
Unreported Use (Hidden/Masked): 14%
Reported Battery Use: 4% (Summation of individual usage as per battery stats)
WiFi - 1%
Phone Idle - 1%
Google Services - 1%
Android System - 1%
[LINK TO THIS POST HERE]
Conclusion:
There is something seriously wrong somewhere. 14% of Battery Drain overnight with screen off is ridiculous.
In KitKat the overnight battery consumption used to be 5% (Average) and 8% (Max). This used to be reported in Battery stats and this was not a drain.
Google is surely hiding the battery drain in Lollipop. It is a half baked cake and Google knows it.
I request all users (not only Nexus) to track their battery usage on Lollipop and report their observations. A comparison report with KitKat would be Excellent.
[LINK TO THIS POST HERE]
kyinx
********** END OF 15-NOV-2014 **********​
********** ORIGINAL POST 14-NOV-2014 **********
My Device: Nexus 5 LG-D821 (India). Not an OTA update. Flashed LRX21O Factory Image. Did not use Google or any other Backup & Restore utility. No Root.
Flashback: Lollipop 5.0 Developer Preview LPV79, LPV81C & LPX13D had serious battery drain issues. Detailed as "Miscellaneous" it was the WiFi Battery Drain bug which bothered all Lollipop users.
Report: After using my Nexus 5 for two complete charge cycles, I have observed that the WiFi battery drain bug persists and the details are very cleverly hidden by Google. I am framing my observations and conclusion below.
[SCREENSHOTS IN ATTACHMENT BELOW]
Initial charge: 100%
Used: 45% (Summation of individual usage as per battery stats)
Remaining: 10%
Unreported Use (Hidden/Masked): 45%
Wifi was ON the whole time (11h 5m). Consumption: 2% [SUSPICIOUSLY LOW]
uTorrent was downloading over WiFi (3h 14m). Consumption: 5% [LOOKS GOOD]
Phone idle (9h 52m). Consumption: 1% [SUSPICIOUSLY LOW]
Voice Calls (1h 20m). Consumption: 11% [LOOKS NORMAL]
Screen ON (2h 6m). Consumption: 12% [SUSPICIOUSLY LOW]
Conclusion:
There is about 50% masked battery drain in the final release of Lollipop LRX21O which Google does not want it's users to know.
Google has termed the "Miscellaneous Wifi Battery Bug" as SOLVED by just MANIPULATING the Battery Stats.
At first anyone would be very happy to see that "Miscellaneous" does not appears in the Battery stats and each service uses battery economically. But by observing carefully and refering to the Kitkat 4.4.x battery consumption stats one can easily makeout that the Lollipop battery stats are incorrect. Services are using far less amount of battery than they should (logically) and the device is still draining battery over WiFi.
Google did a hasty job with their final release of Lollipop. They are trying to hide the unresolved bugs.
Project Volta is supposed to give us 30% battery gain and not 50% battery drain.
I request Nexus users to track their battery usage on Lollipop and report their observations.
kyinx

Maybe reflash again?
Sent from my Nexus 5 using XDA Premium 4 mobile app

I was wondering the same....
Let me first talk about my old Nexus7 (2012-WiFi-32GB)...
I jumped onto the AOSP build as we got one after Google released AOSP sources publicly...
I was happy on having it running on my 2 year old device...
Performance was improved and acceptable.. Antutu scores were nearing about 22k mark with Faux kernel...... Some apps ran smoother... some took much more time to start... All credits to NAND dependency of Lollipop...
However, when I used device actively on wifi...Wi-Fi battery drainage was quite high... When I switched off Wi-Fi it went fine...
There was miscellaneous in battery usage...which accounted 30% of battery on AOSP Nexus 7 buikd...
I was unhappy and came back to Kitkat stock build...
Later on I came across the Official Build Image by Google on its servers... I downloaded and flashed on my Nexus 7... It was up and running...
Initially I was happy... Miscellaneous bug was not present(rather visible in stats)....
I used it for day...same battery drainage was there...
I felt Google did not solve anything they have just hidden the miscellaneous battery issue....just to release the lollipop as scheduled..
I get much lesser SOT (3-4 hours) compared to 5+ hours on KK... and while using with WiFi battery decays exponentially... While Wi-Fi not being used... it acts normal....
Another thing, WiFi was on for 12 hours almost and accounts to only 1% battery? I don't agree.... Google(battery stats) is faking this time I feel....
-via Nexus 7

dec1153 said:
Maybe reflash again?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashed twice. Not a problem with flashing.
Does your battery usage stats sum up to about 100% ??

kyinx said:
uTorrent was downloading over WiFi (3h 14m)
Click to expand...
Click to collapse
Rerun the test without downloading anything in the background, this is a huge wakelock. You can see when your phone was awake and when you had the steepest drain.
Leave your phone with WiFi connected and idle, screen off for several hours.
Then work out the average % / hr drain. And to anyone else who sees drain, I'm not saying there's no issue, but please at least verify that it is actually drain by logical testing. Fresh install, no additional apps other than those bundled. 'Seems' worse is not a measurement.

I went to sleep with 53% battery and woke up with 10%... Wifi on ofcourse.
I've also noticed my screen turns on when I receive messages. Not always, but sometimes it does it which is weird...
I can wait for the next update for L...

eddiehk6 said:
Rerun the test without downloading anything in the background, this is a huge wakelock. You can see when your phone was awake and when you had the steepest drain.
Leave your phone with WiFi connected and idle, screen off for several hours.
Then work out the average % / hr drain. And to anyone else who sees drain, I'm not saying there's no issue, but please at least verify that it is actually drain by logical testing. Fresh install, no additional apps other than those bundled. 'Seems' worse is not a measurement.
Click to expand...
Click to collapse
I agree that it is a huge wake lock. The battery drop curve is definitely steep. But the curve does not improve even when the download is complete and the device sleeps. The steep curve continues.
If uTorrent/WiFi/Wake Lock consumes so much battery, then why is it not reported in the stats under any category?
Kitkat used to report this usage. Lollipop is not. There is definitely something which we do not know. Google had not released the bug fixed binaries yet.
Right now my device is on charge and I would do the idle on WiFi test and no WiFi test and report my observations in the next couple of days.

experienced the same. but i think in my case my battery has had its time (1 year now, intensivly used). I ordered a new battery, should arrive tomorrow. I am curious if it will improve, because when i bought my n5, i could easily get 5h screen on. now its just 2-3h (even with kitkat)

I can confirm I'm seeing the exact same battery life (drain) as with the last Dev. Preview. They are definitely hiding the drain now... This needs to be addressed. Before, I could get 5+ hours of SOT on 4.4.4.. Ever since the last Dev. Preview until now on the official factory image flash 100% stock it's roughly 3 hours SOT..

02busa said:
I can confirm I'm seeing the exact same battery life (drain) as with the last Dev. Preview. They are definitely hiding the drain now... This needs to be addressed. Before, I could get 5+ hours of SOT on 4.4.4.. Ever since the last Dev. Preview until now on the official factory image flash 100% stock it's roughly 3 hours SOT..
Click to expand...
Click to collapse
What do you mean by "hiding the drain now"?

tfouto said:
What do you mean by "hiding the drain now"?
Click to expand...
Click to collapse
They're not listing it as miscellaneous in the battery stats menu anymore, but the drain is definitely still there. Also, they marked the issue as fixed in the issue tracker.. It's not fixed, just being covered up.

02busa said:
They're not listing it as miscellaneous in the battery stats menu anymore, but the drain is definitely still there. Also, they marked the issue as fixed in the issue tracker.. It's not fixed, just being covered up.
Click to expand...
Click to collapse
Isn't this open source code? Cant it be checked?
---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------
bhargav143 said:
I was wondering the same....
I felt Google did not solve anything they have just hidden the miscellaneous battery issue....just to release the lollipop as scheduled..
-via Nexus 7
Click to expand...
Click to collapse
Do they hide their bug, or is something that they hid on purpose? Like scanning wi-fi and sending data even tough people think it's isn't happening?

tfouto said:
Isn't this open source code? Cant it be checked?
---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------
Do they hide their bug, or is something that they hid on purpose? Like scanning wi-fi and sending data even tough people think it's isn't happening?
Click to expand...
Click to collapse
Yes it should be open sourced...however after the so called fix by Google... the sources are not updated...they are still in R6 branch.... No new addition/manipulation to code....
The reasoning is...they wanted the rollout take place as scheduled... And WiFi is functional... Its not that its not working at all... So they have hidden as of now... And we might see some bug fixes in coming weeks...
-via Nexus 7

tfouto said:
Isn't this open source code? Cant it be checked?
---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------
Do they hide their bug, or is something that they hid on purpose? Like scanning wi-fi and sending data even tough people think it's isn't happening?
Click to expand...
Click to collapse
It MAY be fixed in AOSP, but they pushed out the factory image with the battery stats changed after the issue was marked fixed and acknowledged as fixed by a team member. The drain is still there though. I guess they're thinking that by not showing the "miscellaneous" drain in battery stats it will have some mental placebo effect on the end user... Yet any dumbass can see their actual battery life over their average daily use. Also, the items listed in battery stats DON'T add up to 100%, there's a huge percentage not showing up in the list.
For instance right now as I type this from my N5 my percentages are as follows.
Exactly 20% Battery life left.
Exactly 40% showing in battery stats among everything added up.
Thus leaving exactly 40% unaccounted for in the list..
Like I stated before, they considered this "fixed" last week, well before the factory images were pushed out this week. Yet, our LRX21O build for the Nexus 5 is dated at approximately October 21, 2014 before the issue was "fixed".
Follow me now?

coming from android 4.4.3
and flashing the OTA with this method
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
i haven't observed any battery drain at all
slept last night with wifi ON at 75%
work up and it was a respectable 60%
pretty good !

qwerty warrior said:
coming from android 4.4.3
and flashing the OTA with this method
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
i haven't observed any battery drain at all
slept last night with wifi ON at 75%
work up and it was a respectable 60%
pretty good !
Click to expand...
Click to collapse
I suggest you watch your battery life a little closer.. That's not that good. A lot of people aren't familiar with the drain, having not run the Dev. Preview for any extended amount out time.

I suspect Google for hiding Miscellaneous in battery stats.
For example, on top list of batt stats is obviously display (for example) but the "screen" only show ¼ bar graphic, not full graphic. (Just like the third picture in the OP)
So, what is on the top list above display actually?? ?

I agree. The stats no longer add up..
FYI. Miscellaneous wasn't just related to WiFi drain. If you open miscellaneous in battery stats, it said it accounted for the difference between the guesses made in battery screen (they've always been very approximate calculations and always been very inaccurate) and what the battery management chip reports as reality.
Having miscellaneous in principal was a good thing as we could see how inaccurate the battery stats really were. Its just unfortunate that there was also a WiFi bug that reported in miscellaneous too.

rootSU said:
I agree. The stats no longer add up..
FYI. Miscellaneous wasn't just related to WiFi drain. If you open miscellaneous in battery stats, it said it accounted for the difference between the guesses made in battery screen (they've always been very approximate calculations and always been very inaccurate) and what the battery management chip reports as reality.
Having miscellaneous in principal was a good thing as we could see how inaccurate the battery stats really were. Its just unfortunate that there was also a WiFi bug that reported in miscellaneous too.
Click to expand...
Click to collapse
Yeah. They should know being a developer device, that this would still be noticed by many people.

02busa said:
Yeah. They should know being a developer device, that this would still be noticed by many people.
Click to expand...
Click to collapse
Honestly not sure what's going on. Also better battery stats is about as much use as a chocolate tea pot
That said, they've managed to make a chocolate tea pot now so...

Related

Tricky Idle battery drain problem

***********************
**** I have been performing controlled experiments to the best of my ability. See below for results. ****
Experiment #1: Isolate if this is due to Wifi
Methodology (one test per night)
1. Keep wifi off. Perform a set usage pattern, then keep phone on sleep all night.
2. Perform the set usage pattern using wifi, then keep phone on sleep all night with wifi turned on.
3. Perform the set usage pattern using wifi, then keep phone on sleep all night with wifi turned off.
Results:
http://forum.xda-developers.com/showpost.php?p=50548879&postcount=27
Experiment #2: Isolate if this is due to GPS/Location Services (Ongoing)
Methodology (one test per night)
1. Keep GPS off. Perform a set usage pattern, then keep phone on sleep all night. [This is identical to the WiFi experiment, so there is no need to replicate this]
2. Perform the set usage pattern using WIFI, then keep phone on sleep all night with GPS turned on.
3. Perform the set usage pattern using GPS, then keep phone on sleep all night with wifi turned off.
Results:
http://forum.xda-developers.com/showpost.php?p=50685378&postcount=69
***********************
So, I've been battling idle drain battery problems for a while now . I was unable to make much progress because I did not have visibility into partial wakelocks on the system . So I did what any inquisitive person would, I rooted my phone. Bye bye warranty.
Now that I have root, I am able to see the partial wakelocks in better battery stats. To my partial surprise , I do not see any substantial partial wakelocks that would explain the significant battery drain at night. I have good cellular signal, and wifi signal where the phone is placed.
Any clues?
Almost 25 percent in 9 hours. Also notice the lack of activity between successive awake blips, and the constant battery drain that occurs between them. Before I even got root and was able to look at the partial wakelocks, I had already suspected that there were no wakelocks going on but yet the battery was draining.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below are screenshots from the stock battery app showing the top battery drainers and the details of the major ones.
By the way, I would attribute approximately 6 percent of the battery drain due to the screens. I have quite a bit of data that suggests at the brightness levels I was using the screen for those 30 minutes, the drain rate should have been around 12 percent per hour. That still leaves 18 to 20 percent of battery to be accounted for. According to better battery stats, the phone was only awake for around 30 minutes total when the screen was off. And looking at the CPU Lodge, it's clear that those 30 minutes or so were spent in the lowest frequency mode , and that the phone was in deep sleep at all other times.
Attached are the better battery stats logs that shows the partial wakelocks as well. I don't know why the CPU's states are not included in the file but I can assure you I took a look look at it and the 30 or so minutes of awake time were perfectly captured by the 300mhz state.
http://pastebin.com/j685pa5q
Sent from my XT1034 using Tapatalk
I turned airplane mode on, and left location services on. Battery drain was 2.8%/hr (measured over a 5% battery drain interval) with the phone only being awake for 7min 28sec when the screen was off. There were around 5min of NLP wakelocks, and some other miscelaneous ones. I don't think that explains the battery drain fully.
Then, I turned off location services, and the battery drain has been 1.7%/hr (measured over an 8% battery drain interval) with a total awake time of 5 mins, and of that only 1 min of awake time when the screen was off. Very few to no wakelocks.
What is wrong? Why is the battery draining at ~2%/hr with airplane mode on, location services off, and the phone being in deep sleep pretty much the whole time!?
Hey I'm trying to find if there of a pattern with the battery drain and the battery voltage (mv) .I slightly have the felling the battery is a bit wonky . Could you check the battery voltage while charging just before 100% and the voltage when it has fully charged ? .. Try the code *#*#4636#*#*
I feel the my peak battery voltage has dropped significantly over the last 2 weeks.
Sent from my XT1033 using Tapatalk
I have the same problem with mine, no clue what the problem is, I turned off location services and I dont use 3g at all, only wifi while at home or other places sometimes, but the drain persists, still dont know what to do
Sent from my Moto G :3
Try a Cache wipe in recovery - http://forum.xda-developers.com/showthread.php?t=2634361
neu - smurph said:
Try a Cache wipe in recovery - http://forum.xda-developers.com/showthread.php?t=2634361
Click to expand...
Click to collapse
I don't think a cache wipe is the solution. For example, see the updated battery settings screenshot below. The flat line at the end is the result of just rebooting the device (no cache wipe). The battery is no longer draining constantly, even though the same services are activated.
I'm the OP of the thread that I think first reported this issue. Note that I found that the drain is noticeable in airplane mode as you expect there to be almost zero drain, however it still happens when not in airplane mode as well, you just notice it less as the device is doing other stuff which all adds up to battery drain.
I think there is a driver bug, most likely a WiFi driver bug or possibly GPS driver bug. For example maybe GPS is somehow constantly active but the bug manifests itself in such a way that this is not reported to the OS itself which is why you do not see it active in the battery screen .
I had the exact same issue as reported above, no wakelocks over and above the normal amount but the drain was 3% hr or so. A reboot fixed it but it would reoccur when i connected to another WiFi network.
A factory reset fixed it completely until a few weeks ago when I was on the road and used GPS. That night I had the battery drain issue again.
So whether its WiFi or GPS that's the cause I don't know, and why, for me, did it stay fixed for so long. I also can't remember if I had GPS switched on when I first had the issue before the factory reset so makes it harder for me to determine the cause.
The above was all on 4.3. I've now upgraded to 4.4.2.
I think the only way to debug will to be to pull off all the various logs from android, you may even need to turn on various debugging/logs from the OS to capture more logs. I'm pretty sure you wont diagnose from just looking at wakelocks and battery screens.
If you can recreate this problem, and sounds like some of you have it a lot, then you are in a good position to get the logs.
BTW does anyone use the BBC weather app, I noticed this caused a LOT of NLP wakelocks so don't think its related but I did notice on 4.4.2 that it drained battery fast so I uninstalled. There is a thread in xda that I started about it.
A poster above says to clear cache, this is normally pointless as /cache will usually contain nothing except a few empty folders and a couple of log files. Also clearing cache means a reboot which temporarily fixes the issue anyway.
scott_doyland said:
I'm the OP of the thread that I think first reported this issue. Note that I found that the drain is noticeable in airplane mode as you expect there to be almost zero drain, however it still happens when not in airplane mode as well, you just notice it less as the device is doing other stuff which all adds up to battery drain.
I think there is a driver bug, most likely a WiFi driver bug or possibly GPS driver bug. For example maybe GPS is somehow constantly active but the bug manifests itself in such a way that this is not reported to the OS itself which is why you do not see it active in the battery screen .
I had the exact same issue as reported above, no wakelocks over and above the normal amount but the drain was 3% hr or so. A reboot fixed it but it would reoccur when i connected to another WiFi network.
A factory reset fixed it completely until a few weeks ago when I was on the road and used GPS. That night I had the battery drain issue again.
So whether its WiFi or GPS that's the cause I don't know, and why, for me, did it stay fixed for so long. I also can't remember if I had GPS switched on when I first had the issue before the factory reset so makes it harder for me to determine the cause.
The above was all on 4.3. I've now upgraded to 4.4.2.
I think the only way to debug will to be to pull off all the various logs from android, you may even need to turn on various debugging/logs from the OS to capture more logs. I'm pretty sure you wont diagnose from just looking at wakelocks and battery screens.
If you can recreate this problem, and sounds like some of you have it a lot, then you are in a good position to get the logs.
BTW does anyone use the BBC weather app, I noticed this caused a LOT of NLP wakelocks so don't think its related but I did notice on 4.4.2 that it drained battery fast so I uninstalled. There is a thread in xda that I started about it.
A poster above says to clear cache, this is normally pointless as /cache will usually contain nothing except a few empty folders and a couple of log files. Also clearing cache means a reboot which temporarily fixes the issue anyway.
Click to expand...
Click to collapse
Thanks you very much for your reply Scott.
As you can see in my troubleshooting, I eventually turned location services and wifi off, but still measured a considerable battery drain. Do you suppose that once you use wifi, or location services after bootup, the effect may remain afterward even if they are switched off? If so, do you agree that if I turn off location services and wifi, then reboot so that the phone boots up with neither - that should be able to verify your hypothesis?
I'll go ahead and try that for a few days and see how it goes. Will report back.
Others have mentioned something to do with the cellular radio power management, and how rebooting and clearing the cache helps with that (apparently this came from a motorola rep...). I've included a data point in this thread where I merely rebooted without a cache clear and the problem went away. So, perhaps the clearing of the cache really does nothing at all ...
If this is a software issue, why aren't all phone with the same software version effected? How are people getting 6-7 days of standby time consistently? Maybe they never use wifi or location services? Well, I intend to test the wifi/gps hypothesis soon .
google+, google now etc caused me a massive battery drain until i greenified them. now i get a solid 2 days and about ~6 hours screen on time.
twist3d0n3 said:
google+, google now etc caused me a massive battery drain until i greenified them. now i get a solid 2 days and about ~6 hours screen on time.
Click to expand...
Click to collapse
Do you need the donate version to hibernate them?
twist3d0n3 said:
google+, google now etc caused me a massive battery drain until i greenified them. now i get a solid 2 days and about ~6 hours screen on time.
Click to expand...
Click to collapse
So that´s exactly what I did, too. Turns out my Moto G is a battery monster, 2 days with average screen time without any problems.
tictac0566 said:
So that´s exactly what I did, too. Turns out my Moto G is a battery monster, 2 days with average screen time without any problems.
Click to expand...
Click to collapse
This thread is specifically about battery drain caused by something unknown, not an app or wakelock, I think we should try to keep it clean by not cluttering with app related issues as that can then be confusing for people who are reading through the thread. Thanks.
---------- Post added at 11:40 AM ---------- Previous post was at 11:16 AM ----------
if0rg0t said:
Thanks you very much for your reply Scott.
As you can see in my troubleshooting, I eventually turned location services and wifi off, but still measured a considerable battery drain. Do you suppose that once you use wifi, or location services after bootup, the effect may remain afterward even if they are switched off? If so, do you agree that if I turn off location services and wifi, then reboot so that the phone boots up with neither - that should be able to verify your hypothesis?
I'll go ahead and try that for a few days and see how it goes. Will report back.
Others have mentioned something to do with the cellular radio power management, and how rebooting and clearing the cache helps with that (apparently this came from a motorola rep...). I've included a data point in this thread where I merely rebooted without a cache clear and the problem went away. So, perhaps the clearing of the cache really does nothing at all ...
If this is a software issue, why aren't all phone with the same software version effected? How are people getting 6-7 days of standby time consistently? Maybe they never use wifi or location services? Well, I intend to test the wifi/gps hypothesis soon .
Click to expand...
Click to collapse
Well I cant answer all your questions but I will tell you about my test last night. I hardly use GPS at all (and my battery is normal) and last time I did use GPS I had the battery drain as per my post above, so last night I:
1. Drove 15mins from my house.
2. Switched on GPS (high accuracy).
3. Started google maps and drove for 2mins with GPS in use.
4. Shutdown maps app and drove home (GPS still on - ie high accuracy).
5. At home used phone for bit of XDA on wifi for a bit.
6. Switched on airplane mode but location service still on (note airplane mode does NOT switch off GPS), woke up at 02:00AM and noted I had the annoying battery drain - arghhh.
7. Switched off GPS - woke up 2 hrs later and drain still happening.
8. Switch off location altogether - woke up in morning and drain still happening.
9. Rebooted phone and now battery back to normal, Im back on wifi/mobile location (battery saving).
So to me it looks like its maybe related to GPS in some way but whether its purely GPS or a GPS/wigi/location combo I have no idea.
However I have in the past switced on GPS in my house just to play about and havent has the drain, so is it due to a larger change of location when GPS is on (ie 15mins drive from my house) that causes it to go bad.
So annoying, I took a CWM backup before I booted up my phone so I will pull that to my laptop and see if there are any obvious error logs to look at but I doubt it.
Im still leaning towards a driver issue or maybe some component, eg GPS chip, staying alive/awake even when not in use but m sure others have reported they have it with location/GPS off completely. Maybe its even a few different problems.
You said not everyone has the error, but I bet quite a few non-xda people do but do not realise. A lot of people will just charge their phones overnight so wont even realise, during the day they will think ~2% drop per hour is normal. Even if they do notice the drop in airplane mode they probably think thats normal and ignore it.
I think getting Motorola to accept there is an error is going to be almost impossible especially if its hardware related. Also as we have unlocked bootloader I doubt they will even accept a call once they know that.
I think it would be interesting to get a list of phones that are affected, ie model, serial no, location brought, ROM etc. maybe its a certain batch of phones, if we can determine that it would be some help, maybe we could buy one that isnt affected
So to start it off my phone is
XT1032 UK retail brought from Basildon, Essex, UK from phones4u.
Problem happens on 4.3 stock and 4.4.2 stock.
Baseband version is MSM8626BP_1032.340.63.00R.
Im tempted to flash GPE and/or new basenband radio but I bet the same thing happens.
I may see if there is a new GPS driver but no idea how to flash it etc.
Such a shame as this phone is excellent for me otherwise.
Just seen this thread as well, it blames GPS
http://forum.xda-developers.com/showthread.php?t=2607641
if0rg0t said:
Do you need the donate version to hibernate them?
Click to expand...
Click to collapse
if they're system apps, yeah. totally worth it tho cos you can do maps/fb etc too, also you can allow apps that get push messages to still give you notifications whilst greenified.
e: just to note, i have gps (high accuracy) enabled constantly and still manage 2 days.
twist3d0n3 said:
if they're system apps, yeah. totally worth it tho cos you can do maps/fb etc too, also you can allow apps that get push messages to still give you notifications whilst greenified.
e: just to note, i have gps (high accuracy) enabled constantly and still manage 2 days.
Click to expand...
Click to collapse
Maybe you can help test if you don't mind.
1. Use Google maps with high accuracy when you go out for 5mins or so.
2. Once home use phone as normal on WiFi for a bit, just 10mins will be enough.
3. Take note of battery percent.
4. Switch on airplane mode for 2hrs - DO NOT USE PHONE during this time.
5. After 2hrs take note of battery percent.
6. Report the battery percents recorded in this thread.
If you can do this we would be grateful.
Let us know your phone model, where purchased, ROM etc.
Thanks.
Hi,
Following this MotoG thread for some time I have to admit that my MotoG also has the same issue from time to time.
This is the reason now that I joined XDA because this issue is a real pain.
Having my MotoG for three weeks now I had to restart it four or five times to get rid of the excessive battery drain.
My MotoG (XT1032) is bought in the Netherlands, unlocked, rooted, CWM and stock ROM.
I did remove some Motorola apps and disabled some.
Because of the last remarks that it seems to be GPS related, I want to let you know that it also happened to me without using the GPS.
Yesterday it happened at school, at first the drain was not present but suddenly it started.
In the between the two situation I only checked my mail through Wifi and checked some news.
My MotoG has Wifi always on, bluetooth off, GPS off.
There must be something more than just GPS which causes this drain.
Hopefully we can find the root cause soon.
Mickeyvdb said:
Hi,
Following this MotoG thread for some time I have to admit that my MotoG also has the same issue from time to time.
This is the reason now that I joined XDA because this issue is a real pain.
Having my MotoG for three weeks now I had to restart it four or five times to get rid of the excessive battery drain.
My MotoG (XT1032) is bought in the Netherlands, unlocked, rooted, CWM and stock ROM.
I did remove some Motorola apps and disabled some.
Because of the last remarks that it seems to be GPS related, I want to let you know that it also happened to me without using the GPS.
Yesterday it happened at school, at first the drain was not present but suddenly it started.
In the between the two situation I only checked my mail through Wifi and checked some news.
My MotoG has Wifi always on, bluetooth off, GPS off.
There must be something more than just GPS which causes this drain.
Hopefully we can find the root cause soon.
Click to expand...
Click to collapse
Thanks for your reply, have you confirmed this drain happens when in airplane mode as well and that no wakelocks occur, no unusual statistics in battery screen etc. I ask as some people say they have the issue but then say they have greenified an app etc to stop it which basically means they dont have the issue at all. Im not saying I dont believe you, far from it, I just want to confirm its exactly the same issue as a few of us are seeing. Next time can you NOT reboot but leave phone in airplane mode for a few hours and DONT use it at all, then see if battery has gone down by 2-3% per hour.
Thanks.
Have not used airplane mode to check it, but will sure do this when it happens next time.
What I observed in battery stats was a high percentage of android-os.
I have not used greenify so far.
Sent from my GT-P3110 using xda app-developers app
Mickeyvdb said:
Have not used airplane mode to check it, but will sure do this when it happens next time.
What I observed in battery stats was a high percentage of android-os.
I have not used greenify so far.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Doesn't sound like the same issue if android OS shows high in battery stats. That sounds more like a wakelock issue of some kind which still means you may get drain in airplane mode but for a different reason.
This thread is specifically for the problem of ALL battery stats looking normal, so android OS doesn't show up as high.
I think your best get is to root and install 'wakelock detector' app and you will probably see some high wakelock for android OS.
Thanks for your post on the Motorola forums Scott. It was well written, and to the point. I hope this issue gets the attention it deserves. I'll be reporting in the next few days with my experiments.
scott_doyland said:
Doesn't sound like the same issue if android OS shows high in battery stats. That sounds more like a wakelock issue of some kind which still means you may get drain in airplane mode but for a different reason.
This thread is specifically for the problem of ALL battery stats looking normal, so android OS doesn't show up as high.
I think your best get is to root and install 'wakelock detector' app and you will probably see some high wakelock for android OS.
Click to expand...
Click to collapse
Sorry to post this wrong condition.
I had the impression that I was suffering the same problem.
Will have a look with a 'wakelock detector' to see if I can tackle the high android-os consumption since I rooted my device already.
Although the issue seems different I will have a good look this morning since I have to use the GPS.
Will keep you informed if I notice something weird.

[Q] Moto G idle battery drain

Hi,
I have searched the forum for this and even though there are a number of cases they all seem different from this one. Instead of confusing matters more I decided to open a separate thread.
My Moto G (European version, en. DE, Android 4.4.2) so far had always been running for 7-10 days on a charge. Mobile data is off, GPS is off, data is off, WiFi is on only occasionally, no calls at all.
This has changed. My use is the same but the battery now drains at around 1.5-2% per hour, effectively cutting running time in half.
The only thing I (consciously) changed was to install SwiftKey. I have read that there have been issued like this with a previous version of it but that seems to have been fixed since 4.4 or so. Either way my other android device handles SwiftKey well so I am really not sure what might be causing this.
Of course I removed SwiftKey but that did not fix the problem.
The OS reports this battery usage: idle 35%, display 27%, cell standby 23%, Android system 5%, Android OS 3%.
Also I have no idea what kind of background update might have been made without me knowing it.
Do you have any idea what might be causing this? Is anyone of you experiencing the same issue?
What kind of battery do you have?
fertchen said:
Hi,
I have searched the forum for this and even though there are a number of cases they all seem different from this one. Instead of confusing matters more I decided to open a separate thread.
My Moto G (European version, en. DE, Android 4.4.2) so far had always been running for 7-10 days on a charge. Mobile data is off, GPS is off, data is off, WiFi is on only occasionally, no calls at all.
This has changed. My use is the same but the battery now drains at around 1.5-2% per hour, effectively cutting running time in half.
The only thing I (consciously) changed was to install SwiftKey. I have read that there have been issued like this with a previous version of it but that seems to have been fixed since 4.4 or so. Either way my other android device handles SwiftKey well so I am really not sure what might be causing this.
Of course I removed SwiftKey but that did not fix the problem.
The OS reports this battery usage: idle 35%, display 27%, cell standby 23%, Android system 5%, Android OS 3%.
Also I have no idea what kind of background update might have been made without me knowing it.
Do you have any idea what might be causing this? Is anyone of you experiencing the same issue?
Click to expand...
Click to collapse
Just curious to find out what kind of battery do you have and where did you purchase it? It may be the new installation but hard to tell.
mugenbatteriesOwner said:
Just curious to find out what kind of battery do you have and where did you purchase it? It may be the new installation but hard to tell.
Click to expand...
Click to collapse
What kind of battery I do not know - I did not change anything on this phone and as far as I know the battery can not be removed. I bought the phone in early January 2014, it was one of the cost to be delivered and still had the previous android version (4.3?) back then.
fertchen said:
What kind of battery I do not know - I did not change anything on this phone and as far as I know the battery can not be removed. I bought the phone in early January 2014, it was one of the cost to be delivered and still had the previous android version (4.3?) back then.
Click to expand...
Click to collapse
Go to developer Options in settings and if you do not have this option then go to About Phone and tap 5 times on Build Date or number (should be last one) then go to "PROCESS STATS" which is under "ENABLE BLUETOOTH HCI SNOOP LOG" and when you are at process stats click on the three dots on top right and change the duration for 1 day and then you might be able to find the application that is running in the background constantly, mine is Facebook lol and Facebook Messenger....
NextGenGTR said:
Go to developer Options in settings and if you do not have this option then go to About Phone and tap 5 times on Build Date or number (should be last one) then go to "PROCESS STATS" which is under "ENABLE BLUETOOTH HCI SNOOP LOG" and when you are at process stats click on the three dots on top right and change the duration for 1 day and then you might be able to find the application that is running in the background constantly, mine is Facebook lol and Facebook Messenger....
Click to expand...
Click to collapse
this is mine lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bublz654 said:
this is mine lol
Click to expand...
Click to collapse
From that i cant see anything but im sure that you are facing a wakelock from the qcamera2factory, you usually get this wakelock from apps such as Skype and Snapchat, force close these types of applications and hopefully you will get your great Battery life back. Those apps didnt allow me device to enter deep sleep so i was loosing a lot of battery life and to check if you have this wakelock you need root because of kitkat permissions but if you dont want to root then just force close those applications and wait a few days and test it out.
NextGenGTR said:
From that i cant see anything but im sure that you are facing a wakelock from the qcamera2factory, you usually get this wakelock from apps such as Skype and Snapchat, force close these types of applications and hopefully you will get your great Battery life back. Those apps didnt allow me device to enter deep sleep so i was loosing a lot of battery life and to check if you have this wakelock you need root because of kitkat permissions but if you dont want to root then just force close those applications and wait a few days and test it out.
Click to expand...
Click to collapse
what's qcamera2factory ? yeah I am rooted, I hibernate my apps with greenify whenever I can. what app can you suggest for viewing battery stats and wakelocks ?
bublz654 said:
what's qcamera2factory ? yeah I am rooted, I hibernate my apps with greenify whenever I can. what app can you suggest for viewing battery stats and wakelocks ?
Click to expand...
Click to collapse
Just search wakelock detector on Play store and it should be the first application there. The qcamera2factory is a wakelock inside of the "Media Server" wakelock. Check how long your device has been on for and how much screen on time you have and compare to how long you have had deep sleep, if you have like 10 hours of on time and 1 hour of screen on time you should have about 9 hours of Deep sleep, if it is anything weird like 1 hour or 2 hours then you have something preventing your phone from deep sleeping.
NextGenGTR said:
Just search wakelock detector on Play store and it should be the first application there. The qcamera2factory is a wakelock inside of the "Media Server" wakelock. Check how long your device has been on for and how much screen on time you have and compare to how long you have had deep sleep, if you have like 10 hours of on time and 1 hour of screen on time you should have about 9 hours of Deep sleep, if it is anything weird like 1 hour or 2 hours then you have something preventing your phone from deep sleeping.
Click to expand...
Click to collapse
OK I'll search for that app . what happens if I'm on my phone all the time n don't switch off screen. does that count ?
bublz654 said:
OK I'll search for that app . what happens if I'm on my phone all the time n don't switch off screen. does that count ?
Click to expand...
Click to collapse
lol if you are on your phone all the time then you will see somethinh like this xD 10 hours on time - 9 hours screen on time and 1 hour deep sleep. lol
https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector is this it ?
Hmm... No app like that (Skype etc.) is running on my phone. Could it be the camera app itself? Never had any issues with that before though.
My phone is not rooted. I just want to use it in place and not think about it too much. Researching which is the best path to root for Moto G was to mich for me back when I bought it and I have been happy with it or if the box - so far...
here was my stats after one night. kernel wakelock
CPU wake lock
in kitkat, wakelock policy was changed and you cant clearly see any system wakelock without root (i have tried many apps like wakelock detector and there is nothing to see in compare with Jelly Bean 4.3)
i had this annoying battery idle drain - it happened randomly, sometimes battery ran 7 days with light usage of phone but sometimes 30-40% was gone in 24 hours = 1-2%/h
i didnt have any apps installed like Skype, Facebook, or any other "keep awake" app - i also set up my gps, wifi settings, nothing helped
i also switched to ART runtime..again, didnt help
i decided to switch back to factory Jelly Bean 4.3 - you CAN flash stock ROM without unlocking bootloader (im locked without root) and now im running 4.3 with battery drain 0,1-0,4%/h in idle...battery life is now amazing - final battery drain is always ~0,6%/h (light usage)
im charging my phone from 30% to 80% and now it enough for 3 days ! for my 6h night it is only 1-3%
in background i have 3 apps running for battery monitoring (battery hd, batterydrain [analyser], gsam battery monitor) and few schedule apps...i disabled unnecessary apps like motocare and few other google/motorola apps
yes, im missing better alarm (kitkat), better RAM (now i have 60-100MB less...but if 380MB free or 460MB free...it doesnt matter for me) and some other little things that everything i can handle for MUCH MORE BETTER battery :good:
Mine drains 10% when it's in plane mode per hour...
But others days can last longer for at least 8-9 hours of screen time.
Is your phone running hot? I've had a problem with some custom kernels that caused my phone to run hot and drain fast without any visible signs.
this is after some time. im concerned by the second one on the list because it has Wheelock's at the end of name and it has x1441
I just rooted the thing and installed Greenify and GSam Battery Monitor. Now I'm down to 0,3-0,4%/h. That is fine for me.
It is a bit sad that it had to come to this but that is how the world works these days, I guess. Isn't it amazing how mch technology we can fit in these small packages?
0,3-0,4%/h is amazing !
im on 0,34%/h as final result now (BatteryDrain [Analyser])
yesterday i ended 5 days cycle on 53% battery i charged to 82% then with very light usage i need to charge after 5 full days (120 hours) on 29% (= no idle battery drain)
this idle battery drain is not hardware related, its issued by (stupid) KitKat - i really dont believe that it will be fixed in any next release (4.4.x or 5)
im enjoying JellyBean 4.3 much more than KitKat - all you need is flash stock system image WITHOUT unlocking bootloader/root/losing your warranty

[Q] About Battery Life

Hi,
I have a question regarding battery life of the OPO. I'm still not sure whether I have a defective battery, or some apps drains my battery like crazy (or both?). I hope you can help me with this.
In the first 2 weeks since I got it, I use my OPO for mid to heavy activities (a lot of Whatsapp, Youtube, streaming music, etc). I always start the day with 100% battery and I thought it was normal to see the battery drops to at least 20% at the end of the day. To be honest, I didn't check the battery stats in Settings even once in this time frame, and due to my heavy usage, once again I thought this was normal.
Until one night I decided to plug the charger earlier than usual, unplug it around 11pm (w/ 100% battery), then I fell asleep. I was shocked the next morning (8am) when I saw the battery has decreased to 65% with no activities whatsoever. I check the battery usage in Settings and then saw Google Play Services (GPservice) at the top of the list with 45% usage, with "keep awake" time almost identical to total time on battery. I did some research and found some advice including 1) denying GPservice abilities to "keep awake" and "wake up" via privacy guard (from this thread http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525), 2) turn off location, 3) turn off sync, but none of them seems the solution to my problem. Since then, I always check the battery usage and reset it, to see if GPservice still at the top. Sadly it still there. After I reset the stats, go to sleep directly and check it about 1 hour later, GPservice uses 40% - 60% of the battery usage, draining about 6% battery / hour.
With screen on a few minutes, it easily drops to 5th or 6th place with ~7% usage, with screen and main apps I use on the 1st and 2nd place. When I googled about this using Firefox, that's when I start worrying about something else, the battery itself. With wi-fi and low brightness (less than >20% if I convert it from the slide bar), browsing with Firefox decrease the battery 1% in 2-3 minutes, no or low usage drains 1% in about 5-6 minutes. In contrast, charging increase the battery 1% in 1 minute. Is that normal? IDK, usually bad battery increasing faster when charging and decrease significantly when in use.
Please help, especially about the excessive GPservice battery usage. And if it's possible, I prefer non-root solution for it. Thanks and sorry for my bad English.
OPO - stock rom (unrooted XNPH44S)
Google Play Services 6.7.76 (reverted back to 5.0.89 factory version but things pretty much the same)
cliffflip said:
Hi,
I have a question regarding battery life of the OPO. I'm still not sure whether I have a defective battery, or some apps drains my battery like crazy (or both?). I hope you can help me with this.
In the first 2 weeks since I got it, I use my OPO for mid to heavy activities (a lot of Whatsapp, Youtube, streaming music, etc). I always start the day with 100% battery and I thought it was normal to see the battery drops to at least 20% at the end of the day. To be honest, I didn't check the battery stats in Settings even once in this time frame, and due to my heavy usage, once again I thought this was normal.
Until one night I decided to plug the charger earlier than usual, unplug it around 11pm (w/ 100% battery), then I fell asleep. I was shocked the next morning (8am) when I saw the battery has decreased to 65% with no activities whatsoever. I check the battery usage in Settings and then saw Google Play Services (GPservice) at the top of the list with 45% usage, with "keep awake" time almost identical to total time on battery. I did some research and found some advice including 1) denying GPservice abilities to "keep awake" and "wake up" via privacy guard (from this thread http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525), 2) turn off location, 3) turn off sync, but none of them seems the solution to my problem. Since then, I always check the battery usage and reset it, to see if GPservice still at the top. Sadly it still there. After I reset the stats, go to sleep directly and check it about 1 hour later, GPservice uses 40% - 60% of the battery usage, draining about 6% battery / hour.
With screen on a few minutes, it easily drops to 5th or 6th place with ~7% usage, with screen and main apps I use on the 1st and 2nd place. When I googled about this using Firefox, that's when I start worrying about something else, the battery itself. With wi-fi and low brightness (less than >20% if I convert it from the slide bar), browsing with Firefox decrease the battery 1% in 2-3 minutes, no or low usage drains 1% in about 5-6 minutes. In contrast, charging increase the battery 1% in 1 minute. Is that normal? IDK, usually bad battery increasing faster when charging and decrease significantly when in use.
Please help, especially about the excessive GPservice battery usage. And if it's possible, I prefer non-root solution for it. Thanks and sorry for my bad English.
OPO - stock rom (unrooted XNPH44S)
Google Play Services 6.7.76 (reverted back to 5.0.89 factory version but things pretty much the same)
Click to expand...
Click to collapse
Definitely sounds like somethings not right, what apps do you have that access or could potentially access your location? If you're still not having any luck, as a last resort you could try a fresh install of CM11S and install your apps one by one to see if you can determine if any are responsible for sucking battery.
Give the below app a try:
https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix&hl=en_GB
Install Gsam to see if you can gain any more insight into whats causing battery drain.
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm
cliffflip said:
Hi,
Until one night I decided to plug the charger earlier than usual, unplug it around 11pm (w/ 100% battery), then I fell asleep. I was shocked the next morning (8am) when I saw the battery has decreased to 65% with no activities whatsoever. I check the battery usage in Settings and then saw Google Play Services (GPservice) at the top of the list with 45% usage, with "keep awake" time almost identical to total time on battery.
Click to expand...
Click to collapse
did you try to use this App: http://forum.xda-developers.com/showthread.php?t=1179809
there you can see which app prevents your phone from going to sleep (partial Wakelocks)
gsmyth said:
Definitely sounds like somethings not right, what apps do you have that access or could potentially access your location? If you're still not having any luck, as a last resort you could try a fresh install of CM11S and install your apps one by one to see if you can determine if any are responsible for sucking battery.
Give the below app a try:
https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix&hl=en_GB
Install Gsam to see if you can gain any more insight into whats causing battery drain.
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm
Click to expand...
Click to collapse
Maps, Google Fit, Google Now, among other things.
CMIIW but I read somewhere that GServicefix does the same like privacy guard, denying some service to keep awake, wake up, etc.
So I installed Gsam and run it about 1 hour. Interestingly in there, Kernel (Android OS) is on the top the % list with 60% usage (mostly phone in idle/sleep). When I switch sorting to Kernel Wakelocks, it shows event0-798 & event2-798 as the top 2 wakelocks with around 7000 wakelocks. I'll update in few hours, thanks.
drcyber said:
did you try to use this App: http://forum.xda-developers.com/showthread.php?t=1179809
there you can see which app prevents your phone from going to sleep (partial Wakelocks)
Click to expand...
Click to collapse
From what I read on the Play Store description, Kitkat and above requires root?
cliffflip said:
Maps, Google Fit, Google Now, among other things.
So I installed Gsam and run it about 1 hour. Interestingly in there, Kernel (Android OS) is on the top the % list with 60% usage (mostly phone in idle/sleep). When I switch sorting to Kernel Wakelocks, it shows event0-798 & event2-798 as the top 2 wakelocks with around 7000 wakelocks. I'll update in few hours, thanks.
Click to expand...
Click to collapse
Please post screenshot of gsam
Try clear cache+dalvic cache in recovery
Hi, sorry for the late reply.
It seems reboot the phone a few times solves the problem. Battery usage now seems normal when idle, even with location & sync turned on.

Battery life considerably worse after update to 9.0

OTA update to 9.0 available a couple of days ago so I let it install. Since then, I've seen considerably quicker draining of the battery, with my usage of the phone being much the same as before. For example, when I went to sleep last night the battery was at 64%, and there were no apps running according to a swipe up from Home, but when I woke this morning, battery was down to 2%. I normally charge once a day, and previously the battery was hardly ever below 50% after 24 hours - I'm a pretty light user.
As an aside, with 9.0 there no longer appears to be possible under battery usage information in Settings to see the percentage of battery that has been used by the various apps and processes.
NickJHP said:
OTA update to 9.0 available a couple of days ago so I let it install. Since then, I've seen considerably quicker draining of the battery, with my usage of the phone being much the same as before. For example, when I went to sleep last night the battery was at 64%, and there were no apps running according to a swipe up from Home, but when I woke this morning, battery was down to 2%. I normally charge once a day, and previously the battery was hardly ever below 50% after 24 hours - I'm a pretty light user.
As an aside, with 9.0 there no longer appears to be possible under battery usage information in Settings to see the percentage of battery that has been used by the various apps and processes.
Click to expand...
Click to collapse
Click the three dots in the top right and choose battery usage.
As for battery life, mine has improved greatly on Android P
NickJHP said:
OTA update to 9.0 available a couple of days ago so I let it install. Since then, I've seen considerably quicker draining of the battery, with my usage of the phone being much the same as before. For example, when I went to sleep last night the battery was at 64%, and there were no apps running according to a swipe up from Home, but when I woke this morning, battery was down to 2%. I normally charge once a day, and previously the battery was hardly ever below 50% after 24 hours - I'm a pretty light user.
As an aside, with 9.0 there no longer appears to be possible under battery usage information in Settings to see the percentage of battery that has been used by the various apps and processes.
Click to expand...
Click to collapse
Ok here. 62% drop over night doing nothing suggests you have a rogue app in there. I'm assuming you have ok cellular coverage and nothing has changed there by coincidence. I would reboot and force close every app you have that's not essential overnight and try again. Swipe up from home and clearing those apps doesn't force close the apps. Greenify is an app that (in manual mode) will make it easy to select as many apps as you want and force close the lot of them. If that improves the situation you can then begin to work out which app(s) might be doing bad stuff whilst you sleep...
Battery on my P2 has significantly improved with Pie even if I didn't have any major problem with 8.1 either. Overnight drain 3-4%. After regular use after a full day I easily exceed 5h SOT. Everything stock with just Greenify in non root mode. I couldn't be happier, best Android release so far for me.
NickJHP said:
OTA update to 9.0 available a couple of days ago so I let it install. Since then, I've seen considerably quicker draining of the battery, with my usage of the phone being much the same as before. For example, when I went to sleep last night the battery was at 64%, and there were no apps running according to a swipe up from Home, but when I woke this morning, battery was down to 2%. I normally charge once a day, and previously the battery was hardly ever below 50% after 24 hours - I'm a pretty light user.
As an aside, with 9.0 there no longer appears to be possible under battery usage information in Settings to see the percentage of battery that has been used by the various apps and processes.
Click to expand...
Click to collapse
I've had my p2 installed with PIE for about 2 days now. I suggest giving it a week (which is what I'm doing) and then getting a full overview of how my battery is performing. Usually, after any major OS updates, being that apps are trying to utilize your resources and a new version of Android would try to allocate and learn your usage (in this case battery), you'd get a much better definitive idea of your overall performance.
I also think that since its now available, turn on Adaptive Battery mode. After a day of upgrading the OS, Adaptive battery at my 26 hr mark of upgrade said that one of my apps was taking in a lot of resources to be used in the background (ES File Explorer). I made AB to stop ES from taking battery resources.
So in conclusion, if it a week and then you'll be able to get a better overall understanding of whether your battery REALLY has gotten worse or better.
Hope this helps!
Interestingly, my battery was dropping really quickly too after the update to DP3, I switched off Adaptive Battery and it fixed the issue completely.
I tried it again with Android Pie and the issue resumed, so I turned it back off. Maybe try this too?
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Interestingly, my battery was dropping really quickly too after the update to DP3, I switched off Adaptive Battery and it fixed the issue completely.
I tried it again with Android Pie and the issue resumed, so I turned it back off. Maybe try this too?
Exact same problem here after updating. Even tried a factory reset in case it was an updating issue. Same problem. My battery is currently at 43% 4 hours after a full charge. And I've barely used it. This is really poor.
No new apps installed.
My Oreo battery life was great. I'll try shutting off adaptive battery as suggested - but seems a real shame if one of the flagship battery saving features is doing the total opposite on Google's current flagship phone!
Doesn't seem to be a massively common issue so not sure if a likelihood of a patch either
Just a quick update - Google play services has now become the biggest drain on my battery, just as it was before I factory reset after the first install...
Anyone else had the same?
gbmasterdoctor said:
Interestingly, my battery was dropping really quickly too after the update to DP3, I switched off Adaptive Battery and it fixed the issue completely.
I tried it again with Android Pie and the issue resumed, so I turned it back off. Maybe try this too?
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Interestingly, my battery was dropping really quickly too after the update to DP3, I switched off Adaptive Battery and it fixed the issue completely.
I tried it again with Android Pie and the issue resumed, so I turned it back off. Maybe try this too?
Click to expand...
Click to collapse
I had the same issue and did the same thing... until dp3 and my battery usage was terrible again even with adaptive battery turned off. I ended up turning it on again and after about a week my battery usage was back where it was before. So there doesn't seem to be a magic bullet here. FWIW app usage offered no insight as to what was causing the drain in the first place.
MaxNXS said:
Battery on my P2 has significantly improved with Pie
Click to expand...
Click to collapse
THIS.
I got like 8+ hours of SOT.... no mobile network though, all day wifi use only.
I have this issue. Dropped about 40% over night. I found that turning wifi off stopped the drain completely. I did not have this problem with Oreo at all so it's not the networks im connecting to. Weird thing is this did not happen when I first installed Pie. This started happening about 3 days into installing. Also, I put it in safe mode and saw the same drain with wifi on vs off.
Hi guys,
I seem to have fixed my terrible battery life!
The below might be worth a try if you're still suffering from it.
I noticed in GSAM that RCSphone was the front runner in battery drain so did a little research and found this site.
SOLUTION: Turn off app preview messages (settings / google / app preview messages). Apparently its only function is to allow Allo messages to be received without the app. To me, totally pointless as i don't know - nor have ever met - a single person who uses it.
I've gone from draining 8-10% an hour (screen off) to around 2.5%/hour and from 1hr 35 total SOT to 3hrs 39 minutes with 32% left (and an hour of that was Google maps navigating, so a proper work out for the phone).
Do give it a try and let me know if it works for you.
Although there's room for improvement (idle 2.5%/h seems high to me!) and it's ludicrous that I should have spent several hours finding a fix for this on 100% stock android, I'm very happy to have a usable battery life back again...
Adam.
UPDATE: Seems like in the night I lost 40% again. Idle drain climbed it's way up to 5.6% in the night. Still an improvement from where it was before, but not quite as good as it first appeared...
WibblyW said:
Ok here. 62% drop over night doing nothing suggests you have a rogue app in there. I'm assuming you have ok cellular coverage and nothing has changed there by coincidence. I would reboot and force close every app you have that's not essential overnight and try again. Swipe up from home and clearing those apps doesn't force close the apps. Greenify is an app that (in manual mode) will make it easy to select as many apps as you want and force close the lot of them. If that improves the situation you can then begin to work out which app(s) might be doing bad stuff whilst you sleep...
Click to expand...
Click to collapse
@Burkules I drop 0.4 - 0.7%/hr over night with Bluetooth off/Wifi on/strong cellular signal. Much the same as it was with Oreo. Not quite sure why's there's such a big range (almost 2x) but either way it's ok for me. Did you try the technique above?
WibblyW said:
@Burkules I drop 0.4 - 0.7%/hr over night with Bluetooth off/Wifi on/strong cellular signal. Much the same as it was with Oreo. Not quite sure why's there's such a big range (almost 2x) but either way it's ok for me. Did you try the technique above?
Click to expand...
Click to collapse
Cheers for getting back on this.
I left it on safe mode the other night and it still drained absurdly fast, which suggests to me it's a google system drain rather than rogue app, but will try again with app preview now switched off. Likewise will try greenify again and report back.
Burkules said:
Cheers for getting back on this.
I left it on safe mode the other night and it still drained absurdly fast, which suggests to me it's a google system drain rather than rogue app, but will try again with app preview now switched off. Likewise will try greenify again and report back.
Click to expand...
Click to collapse
Likewise maybe app preview set to off will help me even more. If I recall correctly rogue apps can cause some google system apps to wake up, but perhaps not in safe mode...
WibblyW said:
Likewise maybe app preview set to off will help me even more. If I recall correctly rogue apps can cause some google system apps to wake up, but perhaps not in safe mode...
Click to expand...
Click to collapse
So, switched off adaptive battery again (i'd enabled it after my short-lived miracle recovery the other day) and now I'm down to 4%/hour. Which is better but still really high for idling! Cleared cache and data in Google play services for good measure too as it still comes up super high on the list of battery drainers.
Booting into safe mode now to check the drain without adaptive there and will report back...
UPDATE: Exactly the same drain in safe mode. This is a straight up google problem....
Burkules said:
So, switched off adaptive battery again (i'd enabled it after my short-lived miracle recovery the other day) and now I'm down to 4%/hour. Which is better but still really high for idling! Cleared cache and data in Google play services for good measure too as it still comes up super high on the list of battery drainers.
Booting into safe mode now to check the drain without adaptive there and will report back...
UPDATE: Exactly the same drain in safe mode. This is a straight up google problem....
Click to expand...
Click to collapse
Have you tried to force close every app you've downloaded too?
WibblyW said:
Have you tried to force close every app you've downloaded too?
Click to expand...
Click to collapse
Haven't tried this - but if the battery drain is the same in safe mode (with only google/system apps running) I can't see how it will make a difference. Ill be in rehearsal for several hours today so will force close everything and will then be leaving my phone idling for a few hours anyway.
I signup up to the google play services beta yesterday, and google play services no longer appears as one of the top battery users... but the battery drain is the same and the numbers given in *all* battery apps (Gsam/accubattery/system) don't add up to anything close to the actual % drain. System battery displays 15% of usage (with 'full device usage' on show) when the battery is quite evidently at 48% from full charge. Total cluster****. So pissed off I updated.
Have you seen any improvement in yours with any of these workarounds?
Burkules said:
Haven't tried this - but if the battery drain is the same in safe mode (with only google/system apps running) I can't see how it will make a difference. Ill be in rehearsal for several hours today so will force close everything and will then be leaving my phone idling for a few hours anyway.
I signup up to the google play services beta yesterday, and google play services no longer appears as one of the top battery users... but the battery drain is the same and the numbers given in *all* battery apps (Gsam/accubattery/system) don't add up to anything close to the actual % drain. System battery displays 15% of usage (with 'full device usage' on show) when the battery is quite evidently at 48% from full charge. Total cluster****. So pissed off I updated.
Have you seen any improvement in yours with any of these workarounds?
Click to expand...
Click to collapse
Nothing to lose by trying. And as I said, Greenify makes it easy/quick to do. Force closing is almost as good as uninstalling those apps as the vast majority of installed apps won't restart or run in background until you use them for the first time again. In my experience, quiescent battery consumption (e.g. noticed over night):
Is vastly affected negatively by poor cellular signal strength. Marginal coverage can really drain the battery fast.
Gradually gets worse between reboots
Can be improved (once it degrades) if you force close all the apps you've installed, and swipe away the background apps just before you go to bed!
If quiescent consumption suddenly rises I can normally fix it by force closing all the apps (not being sure which was the one gone rogue/suddenly misbehaving)
At night I generally have excellent cellular coverage, good WiFi, and Bluetooth is off. NFC is always off
I don't enable sync on 2 of the 3 Gmail accounts I have configured
I disable notifications from any apps I don't actually need them from
Quiescent battery consumption is between, say, 0.4% and, 0.7%/hr at home, around 2 to 3%/hr when out and about which I put down to all background data being driven over 4G instead of Wifi, and variable cellular coverage
I've not noticed quiescent battery consumption change between Oreo and Pie, but this may be because I keep force closing apps at night and not giving adaptive battery (which I have on) a chance to have the same effect intelligently
Turning off app preview messages has made no practical different for me
I'm completely stock (stock launcher, not rooted, etc.)
If you can't fix it, at least a factory reset as the next experiment has the option to restore *most* of what was there before (so long as you have had the backup setting enabled). But because not everything is restored it's still a pain. And if that doesn't work it's another factory reset and test and then restore everything manually and gradually :-S. But I think you already tried that?
Burkules said:
Hi guys,
I seem to have fixed my terrible battery life!
The below might be worth a try if you're still suffering from it.
I noticed in GSAM that RCSphone was the front runner in battery drain so did a little research and found this site.
SOLUTION: Turn off app preview messages (settings / google / app preview messages). Apparently its only function is to allow Allo messages to be received without the app. To me, totally pointless as i don't know - nor have ever met - a single person who uses it.
Thanks, just tried that as well and my battery has stayed resolutely at 68% on idle beside me for the last few hours, previously it had gone from 100% down to 69% in about 4 hours whilst similarly doing nothing.
Click to expand...
Click to collapse

Tips and tricks to maximize battery life?

Creating this thread so people can mention what settings to turn on or off, what apps to.disable or what apps to install to improve battery life.
It's got a pretty big battery .... keep everything as you would like to have and just enjoy!
Well for me I would say to have found a good balance between performance and battery life.
Didn't do anything special though except the following:
- turn off location for apps that don't really need it
Only turned it on for Maps & fitness tracker)
- installed Blokada app which gets rid of those
pesky ads which are also hurting battery life.
Last but not least: try the Android 9.0 Beta. On 8.1 I got around 6.5 hrs of SOT with mixed use while on 9.0 I'm closer to 8 hrs. Massive improvement, also on standby drain.
YMMV
I'm guessing Smart Resolution doesn't improve battery life at all?
My last charge was 32 hours ago, got 20% left and have had almost 7 hours screen time. Haven't done anything special apart from using the dark UI and most of the apps I use have a dark mode.
Try Greenify: https://forum.xda-developers.com/apps/greenify
Restrict background activity in App start and set everything to manual and off despite the apps that really need to be active like messengers.
Restrict background data usage for same apps as above.
Make sure setting mobile data always active is turned off.
spindowski said:
Well for me I would say to have found a good balance between performance and battery life.
Didn't do anything special though except the following:
- turn off location for apps that don't really need it
Only turned it on for Maps & fitness tracker)
- installed Blokada app which gets rid of those
pesky ads which are also hurting battery life.
Last but not least: try the Android 9.0 Beta. On 8.1 I got around 6.5 hrs of SOT with mixed use while on 9.0 I'm closer to 8 hrs. Massive improvement, also on standby drain.
YMMV
Click to expand...
Click to collapse
Yea, i use the adguard dns in my router so that all devices connected to my router gets blocked ads
---------- Post added at 10:59 AM ---------- Previous post was at 10:54 AM ----------
Theandroidfan said:
I'm guessing Smart Resolution doesn't improve battery life at all?
Click to expand...
Click to collapse
A little but i hate 720 on such a big screen so for those extra 2% that you save i dont think its worth it.

Categories

Resources