Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
I have autorotation turned on but not the face orientation sensing. I haven't noticed a significant battery loss, at 19 hours with 10 left according to battery spy, but I'll give this a try and see if it increases it any.
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
madsquabbles said:
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
Click to expand...
Click to collapse
I have noticed Google Talk drains batteries when your signed in. By default your phone will sign in. If you don't use TALK, sign-out of the app and you will see increased battery life. Your wont ping the internet as much which saves batteries.
Thanks viperboy I took your suggestion and so far it seems to be helping.
I haven't tried that app yet, however I have definitely noticed an improvement in battery life by disabling auto rotation. Thanks for the info.
THIS NOTE 2 IS SENT FROM A GALAXY WHERE SAMSUNG SPRINTS TO THE TOP, AND JELLY BEANS EAT APPLES!!!!
after a bit of troubleshooting i found that battery monitor widget pro was the cause of my drain. after removing it i went from 2 to 3% an hour to 3% overnight. this really sucks as i love the info bmw colleects. this is the only device i have that suffers drain from the app.
Thanks for the info. I have been losing % 15 battery every night while I'm asleep and was wondering why
...from a Galaxy Note II
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Thank you for this info. I consistently get a full days charge of of my phone but was pretty clueless when it came to what was draining my battery. I've used the rotation lock app and will report my results to see if I get even more remaining battery each day.
Sent from my SPH-L900 using xda app-developers app
Thanks for the helpful advice Viperboy! I've definitely been having wake lock issues with my phone. Hopefully these apps will help me eliminate the problems.
kat3k said:
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Click to expand...
Click to collapse
As viperboy mentioned, BetterBatteryStats is your friend. It really will help you figure out why your phone isn't sleeping like it should. It definitely takes some time to monitor and figure out what the readings mean to help point you to the apps or settings that're affecting your battery, but well worth it. I also like having a better understanding of how things work on my phone.
i did a double check on battery monitor widget pro and it started draining my phone again. as soon as i uninstalled it everything was fine again. this is with both cleanrom and blazer. i'll just wait til official support comes and try it again.
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
ZenInsight said:
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
Click to expand...
Click to collapse
I'm on it now, but I haven't looked to see if it fixed the auto rotation bug yet,
rudyrude432 said:
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
That app is unnecessary. Pegasusq governor already does that by default. Goes to 1 core and 200mhz when screen off, at least that's how my Note 10.1 was. I assume it is the same here since the International GS3, GN 10.1, and GNII basically share the same kernel with a few minor differences.
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Interesting... I have a script that reports on CPU freq and, when plugged into USB (maybe the wall charger too, didn't check), it appears that the kernel runs cpu0 and cpu3 all the time, even when screen off. With the phone unplugged, it went to using only cpu0 but didn't cap the freq. It was spending a good amount of time at the higher frequencies even though I had nothing running.
MiguelHogue said:
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1959898&page=5
Post #42
I installed the app to turn the rotation off when the screen is off so far everything good but when I get a call this goes crazy because the screen goes while in call. I know this because I have an smartwatch which it has a notification app and every message that the phone has my watch vibrates with that message and I had a call few minutes ago my watch started vibrating non stop until I hang up.
Sent from my SPH-L900 using Tapatalk 2
Hello,
I'm currently running the lastest (150118) release of mokee, and my phone can't seem to enter deep sleep. In BBS, the event0 and event2 wakelocks take up nearly 50% of the device on time, and I get an average of a few seconds of deep sleep time, resulting in terrible battery life. Attached are the BBS screenshots.
I did some research and figured out that event0 and event2 are the events from the touchscreen and hardware buttons, but I'm not sure how this would affect the battery levels especially when the screen is off.
Any help is appreciated.
Thanks in advance!
it's not, it's a wifi issue, and most likely an issue with your router. it seems that with some routers produce some weird signals with your phone, and leads a rogue app to constantly try and use your wifi whilst you're in deep sleep.
Is this supposed to happen even while my WiFi is off? It seems that no matter where I go, the phone just won't enter deep sleep and seems to drain more battery locked and off than unlocked. I've tried switching to nameless 4.4 and it is giving me the same problem, which doesn't seem right.
Sent from my Find7 using XDA Free mobile app
The nature of eventN wakelocks is that they almost NEVER actually hold the device awake for very long.
They're a symptom, not a cause - when the system resumes, they hold a wakelock from the time the kernel resumes, up to the time when the frameworks wake up and process the event (which in the case of a resume is, if I recall correctly, pretty much a null event.)
So if you have high eventN wakelocks - something is causing your system to suspend-thrash.
In older kernels, there was a "suspend_backoff" driver to handle this case, and at least hint as to the nature of the problem. I reimplemented the backoff functionality in Omni's kernel to help debug such an issue. (Way back last spring, there was a bug in the battery/charger management driver that would cause a stuck interrupt to prevent suspend. The device would try to suspend, error and abort, then resume, then immediately try again, over and over and over again. You could actually SAVE power by holding a wakelock to prevent the thrashing.)
You'll probably need to look through dmesg to figure out why your device is suspendthrashing.
Hi Entropy!
I've gone through and attached a dmesg.
I'm not particularly sure how to interpret this, but instead of trying to suspend and abort, it seems as if the device is continuously suspending for 0 seconds and waking up. I'm not quite sure why.
Could you take a look? If you need anything else to figure this out I'd be happy to provide it.
Thanks!
I even broke my phone with App Ops trying to figure it out, disabling wake permissions for most apps which caused FC's and even reboots. I have since restored all permissions but I still get FC's whenever I leave an app or switch out of it. Not sure if it's really crashing, but I get a FC message every time. So much so that Substratum turned off its theming for Files because it "crashed" after every screenshot was successfully uploaded to this post. Btw I just removed CrossBreed Lite and it seems to have helped. So far no reboots doing the same stuff that caused reboots! Not sure why it caused problems though. I used it for a few days with no issues.
Anyway, back to my battery woes. 30-40% kernel system usage. Why is this happening? Even Snapchat which is abusing wake locks is nothing compared to kernel system.
I'm running the latest build of AIM 8.1 with EX Kernel. I have just visited the other thread about tweaking governer values to optimize battery life so I'll report back with results although I doubt that's relevant to my battery drain.
I've Googled quite a bit on the subject and it seems that each case is different. Usually caused by a certain bug, although a lot of people say it's "normal" which I strongly disagree with.
Update: optimizing the CPU has definitely made an improvement, but the kernel battery drain still exists.
Could it really be pick up to wake and wifi search behind the drain? Isn't this phone supposed to have a sensor hub that allegedly allows for all sensors to constantly be on while using minimal power? I never noticed this drain on any other phone with both of these features on.
Anyway, I disabled pick up to wake and I'll start trying to remember to turn off wifi when not in use.
I think you're trying too hard and running a bunch of stuff. The kernal usage looks about right. I wouldn't run Gsam and BBS at the same time. They can fight each other. What makes you think there's a problem? Nothing jumps out at me.
Sent from my [device_name] using XDA-Developers Legacy app
I also can't see anything out of the ordinary, except this one picture where it shows the phone being active while dozing. I don't know how to understand that because I don't use that app, maybe I'm reading it wrong. What does Android's built-in battery monitor show? Is it dozing properly while screen is off? What is your average SOT? Is your mobile signal strong? I'm also using AIM 8.1+EX combination with satisfying results. Is your radio up to date?
maybe Wakelock Detektor or Greenify can help you.
And if you currently have things crashing all the time, start with a factory reset. Much easier to diagnose the cause when the apps aren't doing random stuff.
Since I already made several posts / topics regarding issues on my phone with deep sleep, I was able track down different issues and scenarios which prevented the phone from going into deep sleep.
Thanks to
@Freak07
@Lughnasadh
@RetroTech07
@TNSMANI
@craznazn
ProxyHandler gets stuck after a reboot
Link: https://support.google.com/pixelpho...oxycontroller-wakelock-draining-battery?hl=en
Basically every now and then the "ProxyHandler" will get stuck after a reboot and prevent the phone from ever going into deep sleep.
Fix:
To temporarily fix this go into airplane mode and reboot again. Disable airplane mode after the reboot and use your phone until the next reboot
When the screen gets stuck at 60Hz
I wasn't able to figure out which service is keeping the device awake.
But I did track down that the 60Hz stuck-issue is also prevent the phone to going into deep sleep.
Fix:
Reboot the phone
I will update this post when new bugs get reported or figured out.
In my testing it doesn't seem like "Naptime" will fix or help with any of the issues.
Also in my testing it seems like "Naptime" in general doesn't do anything regarding battery drain / deep sleep.
So far I have been using BBS to track down most of the issues.
To use BBS on Android 12:
Install BBS
Grant all permissions
Run in adb: adb shell settings put global hidden_api_policy 1
Reboot phone
Everything except kernel wakelocks will work
Utini said:
Since I already made several posts / topics regarding issues on my phone with deep sleep, I was able track down different issues and scenarios which prevented the phone from going into deep sleep.
Thanks to
@Freak07
@Lughnasadh
@RetroTech07
@TNSMANI
@craznazn
ProxyHandler gets stuck after a reboot
Link: https://support.google.com/pixelpho...oxycontroller-wakelock-draining-battery?hl=en
Basically every now and then the "ProxyHandler" will get stuck after a reboot and prevent the phone from ever going into deep sleep.
Fix:
To temporarily fix this go into airplane mode and reboot again. Disable airplane mode after the reboot and use your phone until the next reboot
When the screen gets stuck at 60Hz
I wasn't able to figure out which service is keeping the device awake.
But I did track down that the 60Hz stuck-issue is also prevent the phone to going into deep sleep.
Fix:
Reboot the phone
I will update this post when new bugs get reported or figured out.
Click to expand...
Click to collapse
Please check whether the A12 update fixes any of your issues.
TNSMANI said:
Please check whether the A12 update fixes any of your issues.
Click to expand...
Click to collapse
I intend to do so. Will get released in one week for Pixel 6 Pro. So I still have to wait ;-)
Don't seem to have any issues with deep sleep, unlocked 512Gb version.
Utini said:
In my testing it doesn't seem like "Naptime" will fix or help with any of the issues.
Also in my testing it seems like "Naptime" in general doesn't do anything regarding battery drain / deep sleep.
So far I have been using BBS to track down most of the issues.
To use BBS on Android 12:
Install BBS
Grant all permissions
Run in adb: adb shell settings put global hidden_api_policy 1
Reboot phone
Everything except kernel wakelocks will work
Click to expand...
Click to collapse
In general, Naptime, and similar apps, have not really been needed since Android 10. In my experience, they can do more harm than good, for what it's worth. A properly running OS with properly running apps shouldn't need apps like this nowadays. If you feel the need to use apps like this then something else is wrong. These types of apps only address the symptom, not the cause (Rocky Horror flashback ).
Just my opinion...
Does anyone know if poor signal strength prevents deep sleep or causes the phone to take longer into deep sleep?
Could it be that countries where the pixel is not official being sold somehow affect deep sleep?
It is weird because usually I am like 65% deep sleep while screen is off and 35% awake while screen is off.
Today I am in a country where the Pixel is also officially being sold (I actually bought it here) instead of my home country and I am like 95% in deep sleep and only 5% awake.
Utini said:
Does anyone know if poor signal strength prevents deep sleep or causes the phone to take longer into deep sleep?
Could it be that countries where the pixel is not official being sold somehow affect deep sleep?
It is weird because usually I am like 65% deep sleep while screen is off and 35% awake while screen is off.
Today I am in a country where the Pixel is also officially being sold (I actually bought it here) instead of my home country and I am like 95% in deep sleep and only 5% awake.
Click to expand...
Click to collapse
I remember when traveling to Europe my P5 (or P4 perhaps it was long ago) drained like 20% overnight while in the US, same programs same everything, it was loke 4 or 5%. So you might have something there.
bobby janow said:
I remember when traveling to Europe my P5 (or P4 perhaps it was long ago) drained like 20% overnight while in the US, same programs same everything, it was loke 4 or 5%. So you might have something there.
Click to expand...
Click to collapse
Well US and EU are quite different (some brands/models even sell the same device as US model and as EU model). I think the frequency bands are different and maybe other things?
But if this is caused simply because I am in the neighbor country in which the P6 is not being officially sold...well **** google and my carrier then.
Has this issue been resolved?