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?
Hello,
Sometimes my battery dies overnight, finally I managed to find the issue which prevents my device goes to deepsleep. Screenshot is attached, I need help to fix this issue.
Thanks
Bump
Hello everyone,
initially I had great battery life on my P6P. I then later started to root, add a 2nd SIM card and installed more and more apps (the same ones I already had on my P4 XL).
I can't really say when deep sleep stopped working, but it does not work at the moment.
I am at the stock ROM and Kernel atm, but rooted.
Usually I would start BBS and figure out which wakelock is preventing me from going to deep sleep.
However, BBS doesn't seem to work on Android 12. So I tries GSAM Battery Monitor.
Attached are screenshots from 2 days with GSM Battery Monitor.
It can be seen that the device does not go to deep sleep at all.
The only way to get it into deep sleep atm, is to enable battery saver.
This causes a huge battery drain over a whole day.
This post will contain the screenshots from day #1.
The next post will contain the screenshots from day #2.
Can anyone tell me how to figure out which wakelock / which app / feature / whatever is preventing my phone from going into deep sleep?
Thanks in advance!
And this is day #2 with more detailed screenshots.
@Lughnasadh @RetroTech07 Maybe you can help me here? :S
Thanks!
I also just "Force stopped" pretty much everything under Settings -> All apps (user apps and the few system/google apps that are in the user apps list).
Still no deep sleep
Utini said:
Still no deep sleep
Click to expand...
Click to collapse
BBS works.. sometimes. You need to stick with it and get the alarms tab to show stats. That should tell you what is keeping it awake. Kernel wakelocks are useless imo. Partial wakelocks and alarms and even network usage perhaps. I have it working but it's sketchy.
Finding a needle in a haystack.
Factory reset and don't restore backup.
bobby janow said:
BBS works.. sometimes. You need to stick with it and get the alarms tab to show stats. That should tell you what is keeping it awake. Kernel wakelocks are useless imo. Partial wakelocks and alarms and even network usage perhaps. I have it working but it's sketchy.
Click to expand...
Click to collapse
So you basically install it, grant it root, and then wait until somehow magically starts to show stats?
therock3181 said:
Finding a needle in a haystack.
Factory reset and don't restore backup.
Click to expand...
Click to collapse
Ye well there must be a way to troubleshoot this.
Can't just always factory reset because something gets bugged?
Utini said:
So you basically install it, grant it root, and then wait until somehow magically starts to show stats?
Click to expand...
Click to collapse
Haha, no I don't have root. I just grant the permissions via adb. But "magically" is the key word actually. Here are a few screenshots from just now. The first 2 are pretty usual for a few of the stats but that changes. The second 2 are what I can sometimes get although that varies as well. Every other stat on the app is like the first two, not stats collected. That's what I mean by you have to stick with it. It will magically show randomly. lol Unfortunately, this round didn't show partial wakelocks which means a bunch to me. Tomorrow morning it will show.
Thanks.. I just flashed kirisakura kernel from @Freak07 since I believe that it also block some wakelocks which are enabled on stock kernel. Will try that tomorrow together with AccuBattery.
If that doesn't work, then I will try to get magic by BBS.
Utini said:
Thanks.. I just flashed kirisakura kernel from @Freak07 since I believe that it also block some wakelocks which are enabled on stock kernel. Will try that tomorrow together with AccuBattery.
If that doesn't work, then I will try to get magic by BBS.
Click to expand...
Click to collapse
If your issue is caused by an app or service (which it sounds like it probably is) constantly running in the background flashing the kernel won't help at all.
Your best bet might be BBS, battery historian (you can take a bug report and then view it there, just google it) or maybe top command.
Freak07 said:
If your issue is caused by an app or service (which it sounds like it probably is) constantly running in the background flashing the kernel won't help at all.
Your best bet might be BBS, battery historian (you can take a bug report and then view it there, just google it) or maybe top command.
Click to expand...
Click to collapse
Well, for now it seems like your kernel fixed the issue though.
I am on 70% deep sleep while screen is off according to accubattery. So I will monitor this through the rest of this day and report back.
Utini said:
Well, for now it seems like your kernel fixed the issue though.
I am on 70% deep sleep while screen is off according to accubattery. So I will monitor this through the rest of this day and report back.
Click to expand...
Click to collapse
Flashing a kernel can't fix issues with apps or services getting stuck in the background.
I guess it was the reboot that helped in the end or whatever was stuck got updated or unstuck some other way.
Freak07 said:
Flashing a kernel can't fix issues with apps or services getting stuck in the background.
I guess it was the reboot that helped in the end or whatever was stuck got updated or unstuck some other way.
Click to expand...
Click to collapse
Hmm really weird. My deep sleep is now also slowly dropping (only at 50% now).
But will see how it ends up after a working day.
I did try reboots before already. It didn't help.
But maybe so far I was working with a mix of several wakelocks which I can now narrow down.
Will try battery historian as recommend by you. Just need to find a decent guide for it first
Utini said:
Hmm really weird. My deep sleep is now also slowly dropping (only at 50% now).
But will see how it ends up after a working day.
I did try reboots before already. It didn't help.
But maybe so far I was working with a mix of several wakelocks which I can now narrow down.
Will try battery historian as recommend by you. Just need to find a decent guide for it first
Click to expand...
Click to collapse
Install better battery stats ( only kernel wakelocks tab is not working)...to check wakelocks and alarms
whats the differencd between doze and deep sleep? and is there a way in accubattery to find out, if the device is sleeping?
cultofluna said:
Install better battery stats ( only kernel wakelocks tab is not working)...to check wakelocks and alarms
Click to expand...
Click to collapse
It didn't work for me at all and I just installed it and it still isn't working for me at all.
It has root and according to the permissions tab in the app everything seems to be granted.
I downloaded the RC 2.6-382 from here: https://install.appcenter.ms/users/...stats-xda-edition/distribution_groups/testers
I will let it run for a few hours and check again.
Edit: Oh I just noticed under the permissions tab:
STATUS: Failed: Transaction failed on small parcel; remote process probably died
Any ideas?
xflowy said:
whats the differencd between doze and deep sleep? and is there a way in accubattery to find out, if the device is sleeping?
Click to expand...
Click to collapse
In Accubattery under "discharging" check for "deep sleep while screen off".
Utini said:
In Accubattery under "discharging" check for "deep sleep while screen off".
Click to expand...
Click to collapse
just found it. is 37% of it, good?
Utini said:
It didn't work for me at all and I just installed it and it still isn't working for me at all.
It has root and according to the permissions tab in the app everything seems to be granted.
I downloaded the RC 2.6-382 from here: https://install.appcenter.ms/users/...stats-xda-edition/distribution_groups/testers
I will let it run for a few hours and check again.
Edit: Oh I just noticed under the permissions tab:
STATUS: Failed: Transaction failed on small parcel; remote process probably died
Any ideas?
Click to expand...
Click to collapse
Working for me properly... besides kernel wakelocks
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