I've seen this all over the place with Lollipop, and it now seems to be affecting me.
I have Greenify installed, Amplify takes any big wakelocks, no google now, location on battery saving. No abnormal wakelocks. But something is keeping the radio active all the time. I've even downgraded to 2G in case it was that.
Phone was charged at 100% and in 4 hours cell standby has a 'time on' of 2h 34m.
I can post battery stats later in the day but the same happened yesterday. I can barely get 3 hours SOT.
I
I need help guys. My standby drain has become worse. I took my phone off the charger after doing a battery calibration (let battery die and recharge without turning it on) and clearing cache and battery info in TWRP. I noticed three hours later that my battery was down to 95%. This is in standby. WiFi on. No Bluetooth. No location services. And greenify.
I am currently running PA 5.1.1 with the kernel that come with it. However, I did notice worse battery life when I was running Stock Oxygen with Boeffla kernel. Most days I cannot surpass 3hr SOT. Back in November I was easily hitting 4.5 hrs SOT.
Please help. Screenshots attached.
Pls post Screenshots and Logs from BetterBatteryStats and maybe delete this Xposed and Greenify ...
Setup: running latest stock image (mhc19i). Rooted, xposed, ElementalX kernel with ghost pepper script, and I run naptime with aggressive Doze.
Issue: fell asleep with my phone around 50% battery remaining. Woke up seven hours later and it had 30 something. I typically don't see more than 1-2% idle drain over night so this got my attention. I checked better battery stats and I obviously have a wakelock issue. Not sure what it could be. Powermanagerservice was running at something ridiculously high, like 96%. Audiomix is the other wakelock running rampid. See screenshots below. Any input appreciated!
Pain-N-Panic said:
Setup: running latest stock image (mhc19i). Rooted, xposed, ElementalX kernel with ghost pepper script, and I run naptime with aggressive Doze.
Issue: fell asleep with my phone around 50% battery remaining. Woke up seven hours later and it had 30 something. I typically don't see more than 1-2% idle drain over night so this got my attention. I checked better battery stats and I obviously have a wakelock issue. Not sure what it could be. Powermanagerservice was running at something ridiculously high, like 96%. Audiomix is the other wakelock running rampid. See screenshots below. Any input appreciated!
Click to expand...
Click to collapse
Have you tried rebooting and then monitoring it to see if it happens again? It could just be a one-time bug, you'd need to reboot to confirm that though.
I was thinking that as well. I did recently reboot. I'm going to accumulate a good amount of up time and then check the stats again. As of now, battery drain seems to be normal.
Something is still keeping my phone awake while the screen is off...
Pain-N-Panic said:
Something is still keeping my phone awake while the screen is off...
Click to expand...
Click to collapse
I've seen this Audio Mix wakelock happen before on the OnePlus One, from memory I think it was kernel related, so switching kernels might be worth a try. You could also try using Wakelock Detector to see if it'll shed any more light on it, maybe it's an app rather than the kernel.
Hmm....think I solved my issue. I got audiomix wakelock to completely disappear. Simply going into settings and turning off all notification sounds did the trick. For me it's not an issue, however, for others who don't constantly keep their device on vibrate I could see this being a massive dilemma. I'm assuming "powermanagerservice" is a normal wakelock to observe?
Pain-N-Panic said:
Hmm....think I solved my issue. I got audiomix wakelock to completely disappear. Simply going into settings and turning off all notification sounds did the trick. For me it's not an issue, however, for others who don't constantly keep their device on vibrate I could see this being a massive dilemma. I'm assuming "powermanagerservice" is a normal wakelock to observe?
Click to expand...
Click to collapse
Yes, powermanagerservice is perfectly normal for when the phone is in use (or some background operation is running). You'll see it roughly correlates with your screen-on time.
I recently decided to check the huge battery drain during night and I found out that my phone would not go in deep sleep. Can anyone please help with that? Also, the 'jio' app I have been using was installed 50 days back and the battery drain similar before that too. Would be really great if I could find a solution for the deep sleep issue. I am trying to load the screenshots of betterbatterystats but not able to.
vikalp4jain said:
I recently decided to check the huge battery drain during night and I found out that my phone would not go in deep sleep. Can anyone please help with that? Also, the 'jio' app I have been using was installed 50 days back and the battery drain similar before that too. Would be really great if I could find a solution for the deep sleep issue. I am trying to load the screenshots of betterbatterystats but not able to.
Click to expand...
Click to collapse
Use gsam form the play store to find out what app is keeping your phone awake.
Uninstall said app.
Since I reformatted my phone I get a lot of battery drain. Overnight it goes down quite steeply as you can see. And during the day with usage it goes down much faster than before reformatting.
I have amplify and greenify full versions.
Before the overnight drain was basically a flat line, now it trickles down. Any ideas?
Edit: cannot post graphs because of new user limitations....
I think I've narrowed it down to this kernel wakelock
a800000.ssusb
In betterbatterystats it sits at 79% while the next closest are PowerManagerService.Display and PowerManagerService.WakeLocks at 17 and 12 percent respectively in "kernel wakelocks".
I think this process is keeping my phone awake at night and also putting additional strain on battery during regular usage.
For anyone curious, clearing system and app cache then rebooting seemed to fix it. I did this using titaniumbackup.
pementosequence said:
I think I've narrowed it down to this kernel wakelock
a800000.ssusb
In betterbatterystats it sits at 79% while the next closest are PowerManagerService.Display and PowerManagerService.WakeLocks at 17 and 12 percent respectively in "kernel wakelocks".
I think this process is keeping my phone awake at night and also putting additional strain on battery during regular usage.
Click to expand...
Click to collapse
This wakelock is the total running time of having a headphone connected by USB type c as the phone has to supply power to the DAC which is including in dongle adapter.
I have had my phone a little over a week. I don't remember changing anything major in the last few days but I must have unintentionally done something which is causing excessive idle drain. All I remember doing is turning off some apps from being allowed to run when closed. It went from estimated 100+ hours on full charge to losing a ton in a day of basically no use (checking email a few times, looking at the weather a few times, sending a few texts). I installed GSam after trying to google what was wrong so I don't know what it looked like before.
Used 48% in 1d 13h | 1.3%/h 8h40m active
Screen 3%
Phone Radio 3%
Wifi Active 5%
Held Awake 26%
App Usage 64% > Android System 35.1% GSam 16% Kernel 7.2%
I did give it extra permissions in ADB but it still doesn't seem to give me extra info about what part of Android System is being a hog.