Related
So since the latest Google Play Services update, I have been suffering some serious battery drain issues. There are various mentions all around the internet and most point to the issue being 4.2.1, which, we aren't running.
I spent some time over the last few days trying to figure out what the issue is and have some observations. But, for some background, last few days I have been getting no more than 10 hours battery with no more than an hour or two screen time.
Google Play Services is listed as the biggest battery drainer with 49%, so I started looking into that.
First off, I noticed in battery stats that if Wifi is on, the device doesn't deep sleep, even though wifi is set to never on when sleeping, the wifi never turns off and the phone never deep sleeps.
First thing to try was turning off wifi, so, I turned off wifi, straight away, phone deep sleeps again.
Next I began messing with Google related things, first of all I "uninstall updates" on GPlayS, tested with Wifi on, great, no more battery drain, phone sleeps, BUT, phone keeps bugging me with notifications to update.
Next was to update, battery drain returns. So, disable Google Now in its own settings, battery drain remains when on Wifi, however, if I kill "Google Search" after disabling Google Now, the battery drain stops.
Various mention on the internet has attributed it to location history and location services in the "Google Settings" however I have had those disabled for a few days now and they seem not to be the issue in this case.
My conclusion so far is that the link between the latest GPlayS and Google Now is the real killer.
At present, I have Google Now disabled, and no battery drain, Wifi turns itself off as it should and the phone sleeps. This isn't a great solution since I use Google Now regularly.
I'm hoping that unless someone has come up with a realistic solution that doesn't involve disabling services, Google will release an update to fix the issue.
Currently without access to another device other than my N10, I'm unable to test whether this particular version of the issue is specific to the XZ or the GoogleNow/GPlayS versions.
My next test is to install Network Info from F-Droid and Better Battery stats, and see if I can attribute the thing preventing wifi from turning off during sleep, and hence the failure for the device to deep sleep, to a particular activity going on.
Further, I have already tested the GPlayS related services by disabling everything such as Calendar and Contact Sync, disabled all of books, movies, photo sync, disabled Google Plus, none of these had any effect on the issue, which all but rule them out of the equation.
Has anyone else got observations on this, is anyone else suffering the issue, or has anyone got a real solution?
I'm off on Holiday on Saturday and would really like to have access to Google Now back, but not have the battery drain that's going to kill my battery while roaming the streets of Rome without access to a charger.
alias_neo said:
So since the latest Google Play Services update, I have been suffering some serious battery drain issues. There are various mentions all around the internet and most point to the issue being 4.2.1, which, we aren't running.
I spent some time over the last few days trying to figure out what the issue is and have some observations. But, for some background, last few days I have been getting no more than 10 hours battery with no more than an hour or two screen time.
Google Play Services is listed as the biggest battery drainer with 49%, so I started looking into that.
First off, I noticed in battery stats that if Wifi is on, the device doesn't deep sleep, even though wifi is set to never on when sleeping, the wifi never turns off and the phone never deep sleeps.
First thing to try was turning off wifi, so, I turned off wifi, straight away, phone deep sleeps again.
Next I began messing with Google related things, first of all I "uninstall updates" on GPlayS, tested with Wifi on, great, no more battery drain, phone sleeps, BUT, phone keeps bugging me with notifications to update.
Next was to update, battery drain returns. So, disable Google Now in its own settings, battery drain remains when on Wifi, however, if I kill "Google Search" after disabling Google Now, the battery drain stops.
Various mention on the internet has attributed it to location history and location services in the "Google Settings" however I have had those disabled for a few days now and they seem not to be the issue in this case.
My conclusion so far is that the link between the latest GPlayS and Google Now is the real killer.
At present, I have Google Now disabled, and no battery drain, Wifi turns itself off as it should and the phone sleeps. This isn't a great solution since I use Google Now regularly.
I'm hoping that unless someone has come up with a realistic solution that doesn't involve disabling services, Google will release an update to fix the issue.
Currently without access to another device other than my N10, I'm unable to test whether this particular version of the issue is specific to the XZ or the GoogleNow/GPlayS versions.
My next test is to install Network Info from F-Droid and Better Battery stats, and see if I can attribute the thing preventing wifi from turning off during sleep, and hence the failure for the device to deep sleep, to a particular activity going on.
Further, I have already tested the GPlayS related services by disabling everything such as Calendar and Contact Sync, disabled all of books, movies, photo sync, disabled Google Plus, none of these had any effect on the issue, which all but rule them out of the equation.
Has anyone else got observations on this, is anyone else suffering the issue, or has anyone got a real solution?
I'm off on Holiday on Saturday and would really like to have access to Google Now back, but not have the battery drain that's going to kill my battery while roaming the streets of Rome without access to a charger.
Click to expand...
Click to collapse
I shut it off it was draining my battery!
I had the same problem.
And here's a solution for you: Factory data reset
After that there will be no problems with battery drain.
NXT3 said:
I had the same problem.
And here's a solution for you: Factory data reset
After that there will be no problems with battery drain.
Click to expand...
Click to collapse
I did a factory reset and have the problem.
So the amount of battery drain has lowered significantly, but it is still there. I attached a screenshot from before the change and a screenshot from after.
use link 2 sd ( root required ) search at playstore
open it and seacrh google play service
option and sleep it..and u done
echopark15 said:
use link 2 sd ( root required ) search at playstore
open it and seacrh google play service
option and sleep it..and u done
Click to expand...
Click to collapse
it must be a way without root
Update Google play Service to version 5.x
So here's the deal. Wasn't getting great idle drain but figured I'd give it a while to see if it worked itself out. It hasn't. Took my phone off the charger and slept for less than 8 ours and loss almost 16% about 2% per hour.
I had wifi on. Blue tooth off. gps off. i have greenify stopping my voicemail and facebook app. I have about 60 something apps frozen. Android OS took up most of my battery life as you can see in pictures. Went to partial wakelocks and saw email at 30seconds but there are only like 45 secs of partial wakelocks so not that big of a deal. Noticed that better battery stats said my phone was awake for almost an hour (I was on it for 10 minutes looking at stuff which is why the screen on pic saus about 10 minutes, the screen wasn't on at all from unplug to me waking up). Noticed under kernal lock that something was keeping stuff on for almost an hour.
So why on earth was my phone on for almost an hour of the 8 hours i was asleep? Further, why does my battery drain look like it was pretty consistent over that time even though the phone was on for an hour. It makes me think that it continuously must be turning itself back on. I know that wifi is the problem for some people but I figured that I would be able to see that in partial wakelocks yet it isn't there. I can try changing wifi stuff if some sees something showing that it is wifi issues.
Otherwise, maybe i should return the phone???
So , I would say that the main issue is your mail service process. It woke up 184 times, every time it wakes its going to keep the phone awake for a little before the phone completely goes back to sleep. it is work related i assume?
anotherfiz said:
So , I would say that the main issue is your mail service process. It woke up 184 times, every time it wakes its going to keep the phone awake for a little before the phone completely goes back to sleep. it is work related i assume?
Click to expand...
Click to collapse
yes that mail account is work and there is an account for my school. It is the email apk that bypasses security that plenty of other people are running. Do you think that it is an account issue or the Email.apk? So the 180 wake ups only totaled for 30 something seconds of partial wakelock. Is it not showing upas a partial wakelock and that is why the phone says that it was on for so long?
also, I read that something having to do with wifi and the qcom_rx_wakelock cause severe battery drain. Know anything about that.
So, yes, the app only worked for 33 seconds because each wakelock probably required only a few milliseconds to do what it needed to do.. but the phone does not go to sleep instantly after each wakelock. so for each of the 184 times that app woke your phone up, it was "awake" for 5-15 seconds or however long it takes the phone to decide its time to go to sleep again. Awake time for me is almost always a function of screen time, like 1.5x - 2x my screen time.
anotherfiz said:
So, yes, the app only worked for 33 seconds because each wakelock probably required only a few milliseconds to do what it needed to do.. but the phone does not go to sleep instantly after each wakelock. so for each of the 184 times that app woke your phone up, it was "awake" for 5-15 seconds or however long it takes the phone to decide its time to go to sleep again. Awake time for me is almost always a function of screen time, like 1.5x - 2x my screen time.
Click to expand...
Click to collapse
so any idea on a solution besides setting up for my email to only check every half hour. It is set to push right now. Given I don't need it at night really and i can set something up to change when it is allowed to check for emails. But sometimes I am up at 2 because I get an email that requires me to do work. Also, the qcom_rx_wakelock that kept m phone on for 32 minutes or something doesn't seem to have to do with the email. But maybe when the email tries to access the internet that wakelock runs to try to get wifi...
edit: I did more research on the qcom_rx_wakelock. I still don't understand it all but it is some issue that the 4.2.2 update came with. It causes major battery drain on some wifi networks and not on some others. It has to do with the wifi connection continuously having to talk to the router and waking the phone up which is also tied to some apps that are syncing. People on nexus's have created patches that fix the issue, but I don't think I'm going to be doing anything like that. I PMd a member to try and get more information.
For now I have two routers at my house and will be switching to using the other router for my wifi connection on my phone to see if it creates the same battery draining issues while in sleep. If I get any more information I will update again. I also think this could explain a lot of the reason that some people are experiencing sub-par battery life while others are getting great battery life. Depending on what router (work, school, home, public place) you are on might make the phone constantly turn itself on and off trying to reconnect or do something with that wifi network. I know many people have had 15 to 20% battery drain overnight then turned wifi off and just stayed on 3g/4g connection and battery drain went to 4 to 5% over night. FYI
I just got the Moto X and have a few things installed. My question is, in the battery mete graph you have screen on and awake. Is the awake always supposed to be on? I'm guessing it is since it has the touchless controls always listening.
Figured why it won't go to sleep. Has anyone ever had it where the phone app gets stuck and stays awake? Only way to get rid of it for me is to reboot.
I have this wakelock called diagnostics.client.wakelock that's destroying my battery. I've searched Google and here to get some more info but couldn't find anything. Anyone know of a fix?
Recently I've heard that wakelock drains battery while I am sleeping. At first I thought it was a Social App or background data running while I was asleep but today I made sure everything similar to that was not running.
My GN3 phone had been doing great with battery usage until this month (use less than 20 percent per day).
To resolve the problem, I rooted my phone and backed up everything and did a factory reset.
I found that my wakelock time was less than one percent until I installed AT&T Visual Voicemail, PayPa,l BofA, and Shazam.
I have since done another reset and installed Google Voice instead. My wake time is still less than one percent now.
--------------------------
After a few days, I am seeing the horrible wakelock again. Ugh.
After no success fixing this wakelock issue and battery drain, I got the NB4 software update OTA today and it looks like the problem is fixed.
--- Not fixed.
I was still having the diagnostics.client.wakelock with NB4, too. I switched to the X-Note 7 ROM and the battery drain problem was gone. During the night, I was seeing 0.2 percent per hour battery drain. That still did not tell what was wrong with NB4.
Just recently, I switched to FireNote as that is closer to AT&T stock MJ5. I started getting the same wakelocks again. Someone in the FireNote thread reported that he never gets that wakelock and that is must be an app. I went back to re-install FireNote and put a few of my testing apps on and found the wakelock again. After removing each one, I found that Active Apps widget was causing the wakelock problem. That widget is not available on X-Note 7. This is one of the first widgets I always install.
I still see occasional diagnostics.client.wakelock but not the hundreds per day as I did before.
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Lilmanio said:
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Click to expand...
Click to collapse
Hi,
I do not have the exact same problem, but my phone drains battery more than often. With wifi, mobile data etc turned off, i have ~10% of drain overnight (7~8 hours). But my phone does enter in deep sleep and battery stats shows me nothing weird (most of battery is being taken from phone iddle /standby cell), it is driving me nuts! My wife have the same phone as mine, same firmware, same system apps, the only diference is mine have the new bootloader, but her phone drains almost half than mine. I'm now reinstalling the firmware with the exact same steps i did in her phone and if someone want i post some screenshots later.
Did you tried installing some custom roms out here who have not all the system apps the original package have?
Lilmanio said:
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Click to expand...
Click to collapse
I am using 4.3 Alliance Rom with boeffla kernel. I had the same problem with battery drain during airplane mode. While I was at work with airplane mode on, I lost nearly 20% in one hour. Because of it I switched to 4.4.2 aosp rom "aosb 1.3.0. Probam" (meanwhile there is 1.3.2 published) but there I had music stuttering and camera issues, but perfect battery life. Because of the problems I decided to go back to 4.3 and gave Alliance Rom another chance. And now the battery life is wonderful like on 4.4.2.
Maybe try the same way, first to update on an aosp rom with excellent battery life and then go back to android 4.3. Maybe this will solve your problem, too.
Lilmanio said:
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Click to expand...
Click to collapse
Hi,
By any chance, do you have XPOSED framework enabled and do you use for example Wanam Xposed module ? If an option like "Turn on screen when unplugged" is unchecked (ie if you don't want your phone to wake up after you unplug it from USB), you may encounter battery drain. It seems that sometimes the phone doesn't enter in deep sleep if the USB cable is unplugged from a PC in this case. I have this kind of battery drain and since I've checked "Turn on screen when unplugged" option, no more battery drain after a reboot.
I'm not sure but you must give it a try as it worked for me. No problem so far.... I hope it will help.
Hi and thank you all,
I'm taking good note of your advices.
I did install Xposed and Wanam. I didn't pay attention to this option and since then completly reinstalled 4.3 official ROM. Battery drain vanished.
I now have the phone going to deep sleep normaly.
I've been reinstalling all my apps slowly one after the other, and didn't try yet to reinstall Wanam Xposed, as I know it modifies the system relatively deeply.
But the envy is here and I think I'll install it again. Ok, let's go, I'll do it tonight. I'll pay attention to "Turn on screen when unplugged" option and will ensure it is checked !
It's worth trying, though all these battery draining problems seem mysterious...
I'll post a reply in a few days with the results...
By the way, I installed Agni kernel wich uses Boeffla engine too. After activating "Extreme battery save" mode, the battery life has doubled or so. I'm happy about this.
Thank you again, and let's see how xposed wanam behaves...
GREAT.
Sent from my GT-I9305 using XDA Free mobile app
I have a Moto G 2014 (XT1064) running Android 6.0 that will not go into deep sleep. I could see that the CPU was never going into the deep sleep state even when the phone was not being used and no user apps were actively running in the background. This is causing abysmal battery life as expected. The phone was updated to Android 6.0 via regular OTA updates. I haven't flashed any third party ROMs onto it at all since I bought it.
The first thing I did to investigate was to unlock the bootloader (it was still locked since purchase prior to this) so that I could obtain root access to see what was going on. This also had the additional affect of wiping the phone to stock Andoird 6.0, which I had hoped would maybe solve the problem but it did not.
My first thought was that it was a user app that was holding a wakelock keeping the phone awake. I looked at the user and kernel wakelock counts via BetterBatteryStats and WakeLockDetector, but from what I can tell it is not any user app that is holding a wakelock at all. Instead it must be some kernel level app keeping the CPU awake, but I can't determine what it is. There isn't any single entry in the wakelock list that sticks out as the culprit.
I have done some other investigative tests such as turning WiFi off while the phone sits unused overnight. This did not have any effect as the phone still remained awake the whole time. I also repeated this test with the phone in airplane mode (WiFi + cellular radios off) and again it had no affect. From this I could only conclude that it was not the wireless radios that were keeping the phone awake. The wakelock counts also didn't show any evidence that WiFi, cellular or GPS were holding wakelocks.
Here are two screenshots I took of the BetterBatteryStats and WakeLockDetector apps showing the highest count kernel wakelocks over a roughly 17 hour period:
(I'd link them in properly but I am prevented from posting outside links on this forum until I have 10 cumulative posts...)
i.imgur.com/nPAY3S6.png
i.imgur.com/5VfgFv1.png
You can see that the phone has been awake 96% of the time during this period, and that the highest count kernel wakelocks are from "event8-1877", "event9-1877", "qpnp_soc_wake" and "qpnp-vadc-e4a28400". I could not find any information as to what these entries mean or what they're related to. Whatever they are, they appear to have abnormally large wakelock counts which leads me to believe that they are related to this problem. The other thing that puzzles me is that the total time for the top four entries in that list only sum to about 2 hours, yet the phone has been awake for almost 17 hours within the same period.
If anyone has any idea about this I'd appreciate the help. I may be completely wrong about the root cause here but I'm running out of ways to debug this.
Updating this thread to say that I have also tried re-flashing stock Android 6.0 using the firmware files linked from this thread (in my case I used XT1064_TITAN_RETCA_6.0_MPB24.65-34_cid14_CFC.xml since I am in Canada). I still experienced the same behaviour where the phone would rarely enter deep sleep. It seemed to be marginally better after re-flashing, going into deep sleep about 10% of the time over a 12 hour period or so, where as before it was only going into deep sleep about 4% of the time during the same period. This still doesn't solve the problem though.
Now I am thinking about downgrading to stock Android 5.0.2 and see if that fixes the problem since I don't know how else to diagnose this.