Hi guys, I'm facing a weird problem for the last one or two months, my hox never goes to deep sleep. It's not a wakelock problem as I have even tried checking in safe mode. See the attached screenshots.
http://tinyurl.com/wakelockproblem
It's as if my hox has forgotten that it has a deep sleep core, for the past two months it has never been to deep sleep for even 1sec, I check it everyday. There seems to be a kernel wakelock process "main" that keeps it online for 100%, what is it?
Related
My HOX does not enter deep sleep at all on wifi (according Cpu Spy). Resulting: battery drain 15-20% /h idle.
Did a factory restore, but to no avail. The problem is still there. If I dissable wifi, phone enters deep sleep in 2-3 minutes.
Some others who have experienced similar? solutions?
ohh .. Phone is running OTA JB.
Run this app and let the phone sit for some time.
Then check results and you'll find out what is preventing deep sleep.
Is it normal for this phone not to deep sleep? I installed CPU spy and it shows that it always stays at 300mhz when the phone is idling. I have all apps closed in the recent apps tray and my phone is stock. Just wondering if this is normal. Thanks
I've been wondering the same thing... battery seems fine and none of my apps or keeping the device away, so I'm assuming it's the whole dt2w feature they have on it. Plus, they mention a "sleep mode" on the HTC website, so maybe they got their own thing or something...
Any info would be nice.
EDIT: Apparently, while charging the device, it will rarely go into deep sleep mode. After I took it off the charger, it was going into deep sleep exactly like it should.
Long story short, I have been experiencing a severe battery drain with any ROM I try for the last month or so. Some ROMs seemed not to have it until first reboot, then the drain showed up.
Installing BetterBatteryStats showed me there was a "fingerprint wakelock" active 100% of the time. This was a bit strange, because my fingerprint sensor doesn't even work most of the time (sometimes it works after installing a ROM, sometimes after a few reboots, but it always stops working eventually for no apparent reason).
But searching around, I came across this page, where the following step is suggested:
mv "/vendor/bin/hw/[email protected]" "/vendor/bin/hw/[email protected]"
By renaming the corresponding file on my current ROM (/vendor/bin/hw/[email protected]) and restarting the device, I got rid of the battery drain and it now shows a healthy deep sleep time! I suppose that kills the fingerprint sensor, but since it wasn't working anyway, no harm done.
Just posting it for posterity and reference to whoever wants to try, I have no idea if anyone else has the same issue. (now I'll go hunt down PowerManagerService wakelocks, which seem to be the next big thing eating battery)
First, thank you for your guide. After updating from 7.1.2 to 9 i experienced a severe battery drain issue as well and this solved it. Actually, the fingerprint sensor never worked on android pie for me (crdroid 5.3). I would like to add some information that may be usefull to people.
This battery drain was caused by the fingerprint sensor and can be diagnosed by cpu spy where you will see your phone not going into deep sleep at all (interactive mode kernel, no idea for performance or gaming modes), and better battery stats showing finger print sensor being responsible for a big part of kernel wake lock when the screen is off.
Renaming the file can be done either if you are rooted on the phone or ( as i have noticed many apps like netflix refusing to work on rooted phones, making it inplactical to having your phone rooted ) using adb usb debugging to rename the files. if you are not allowed to rename the files, remount the phone and try again, remounting will automatically mount it in ReadWrite, while sometimes the first time will mount only as read.
If the problem is fixed the cpu spy app will show a much larger time spent in the lowest clock state in interactive mode and actually phone spending time in deep sleep.
PS: DO NOT hunt down the power wake locks as stated in your post, as those are active when your screen is on, and those should be on.
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?
I found on Reddit posted by u/zakazak:
Due to the help of people over at xda, I manged to figure out two scenarios where a software bug will prevent the phone from ever going into deep sleep. I am posting this here because r/GooglePixel seems to have changed into a territory for haters of rooting and custom ROMs/Kernel. How ever, without root you will probably never figure this out.
So here I am posting this for everyone who is facing massive battery drain (like I did):
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
Other notes regarding testing:
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.
Deep Sleep means that the phone will save a lot of battery while the screen is off. Usually the drain during deep sleep is 0,2-0,5%/h. Without deep sleep it is somewhere at 2-4%/h.
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
Hope this helps some people.
https://www.reddit.com/r/GooglePixel/comments/rboc06