Google Play Services HUGE Wakelocks (FreedomOS+Ex) - OnePlus 3 Questions & Answers

Since a few days I have been getting these humongous wakelocks (by nIPCollectorWakelock mostly) which are draining my battery too fast.
I was using Naptime earlier with Greenify, which worked but I usually missed my whatsapp messages because the thing won't retrieve messages unless screen was turned on. After that, however even Naptime could not keep the drain from hogging on my battery.
So I installed xposed and amplify and set this service and nIPWakelock to limited which had an effect for just a couple of hours after which the same drain came back.
As of now I'm totally out of ideas except factory reset or reflashing rom and kernel (which I don't want to do).
I have just turned the always scanning option in location to Off and also WiFi available during sleep to Off. Maybe that will do some good. Does this also keep the messages from being received until the screen is woken up?
I am on FreedomOS 1.6.1 with ElementalX kernel. Xposed is installed and only has 4 modules (Amplify, Greenify, iFont and Flat Status Bar)

Tried clearing cache?
Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk

Use amplify? I can link u one if you pm me. Maybe Appsops xposed? Last one really helps me!

mharis05 said:
Since a few days I have been getting these humongous wakelocks (by nIPCollectorWakelock mostly) which are draining my battery too fast.
I was using Naptime earlier with Greenify, which worked but I usually missed my whatsapp messages because the thing won't retrieve messages unless screen was turned on. After that, however even Naptime could not keep the drain from hogging on my battery.
So I installed xposed and amplify and set this service and nIPWakelock to limited which had an effect for just a couple of hours after which the same drain came back.
As of now I'm totally out of ideas except factory reset or reflashing rom and kernel (which I don't want to do).
I have just turned the always scanning option in location to Off and also WiFi available during sleep to Off. Maybe that will do some good. Does this also keep the messages from being received until the screen is woken up?
I am on FreedomOS 1.6.1 with ElementalX kernel. Xposed is installed and only has 4 modules (Amplify, Greenify, iFont and Flat Status Bar)
Click to expand...
Click to collapse
NLP will be fired when GPS is used. Find out what app is using GPS and disable it and check. Amplify should block it. Use a higher value in Amplify.

Are you using the stock launcher? I've seen someone else with battery/GPS wakelock issues and it was because of the weather updates from the shelf preventing the phone from deep sleep.

Roykooiman said:
Tried clearing cache?
Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
Click to expand...
Click to collapse
Yup tried that.. didn't help. Thanks for the tip though
Demian3112 said:
Use amplify? I can link u one if you pm me. Maybe Appsops xposed? Last one really helps me!
Click to expand...
Click to collapse
I already am using Amplify - the free version. App-ops just gets stuck on loading. Does it work Ok for you on OP3?
Man I miss CM App privacy
tnsmani said:
NLP will be fired when GPS is used. Find out what app is using GPS and disable it and check. Amplify should block it. Use a higher value in Amplify.
Click to expand...
Click to collapse
I thought of doing that as well. For now, I have turned off amplify completely along with Wifi Scanning and Wifi during sleep. Turned on aggressive doze for Naptime. Appears to be working for now. For now I want it to make it through the day. Then I will Factory reset and flash FreedomOS 1.6.1 with Stock kernel to see if it helps.
Hw4ng3r said:
Are you using the stock launcher? I've seen someone else with battery/GPS wakelock issues and it was because of the weather updates from the shelf preventing the phone from deep sleep.
Click to expand...
Click to collapse
Yes I read it too on the Oneplus Community.. I am using the stock launcher, according to a lot of people that might have been because of the weather panel in Shelf, I have turned that off too.. Not sure which one of the changes I made is working.

Same ROM here, same problem. For me the Android OS wake lock ended up being Google Assistant which I had enabled via an exposed module. I haven't looked into the why of it yet or searched out if others were seeing the same. I've been using the assistant on a couple devices and half a dozen 6.01 ROMs without issue so I suspect it might be fixable...

Related

Lollipop battery drain system(adsprpcd) media server

After updating to lollipop im getting heavy drain by media server which is named as system adsprpcd by gsam battery monitor . I never got this battery drain in kitkat .
I got this problem in every lolli rom viper sd insertcoin etc . I fixed all files and removed all corrupted files but the issue doesnt solve .
I flashed back viper kitkat rom a few days back and surprisingly kitkat battery was good as is should be no battery drain whatskever. But after comjng back to lolli rom (sd rom now ) the problem again started .
Is it lollipop software ?
Sent from my unknown using XDA Free mobile app
I think it might be nuplayer in developer options just disable it
Muradsikandar786 said:
I think it might be nuplayer in developer options just disable it
Click to expand...
Click to collapse
I have the same problem. I have disabled Nu player from developer options but the problem occurs again.
When I notice in GSam battery that adsprpcd is beginning to drain the battery I reboot the phone and that fixes it for a while.
Does anyone know of a permanent fix?
I have been trying to find answer to this problem. I've had it on ALL lollipop Roms. Aosp, sense, and gpe. It's driving me nuts. I have figured out however that it has nothing to do with nuplayer or Google music. It's something to do with notifications.
In gsam it lists audio on for X hrs, x m, xs. Now if I send myself a text or anything that gives me a notification, that timer starts ticking. If I go back and refresh, the audio on time keeps going up for several minutes before it will stop. But if I clear notification from my notification screen the timer stops immediately. That's what's causing it to show up at the top of gsam. That's the cause. I haven't figured out a solution except clearing the notifications.
I am curious though if this isn't some issue with gsam because bbs does not show anything for that process.
Edit: here's a screenshot
razen_kain said:
I have been trying to find answer to this problem. I've had it on ALL lollipop Roms. Aosp, sense, and gpe. It's driving me nuts. I have figured out however that it has nothing to do with nuplayer or Google music. It's something to do with notifications.
In gsam it lists audio on for X hrs, x m, xs. Now if I send myself a text or anything that gives me a notification, that timer starts ticking. If I go back and refresh, the audio on time keeps going up for several minutes before it will stop. But if I clear notification from my notification screen the timer stops immediately. That's what's causing it to show up at the top of gsam. That's the cause. I haven't figured out a solution except clearing the notifications.
I am curious though if this isn't some issue with gsam because bbs does not show anything for that process.
Edit: here's a screenshot
Click to expand...
Click to collapse
i have same problem as u.. but to me didnt help clear notifications.. i have disablet nu player, voice recognition and after read your post im clearing all time my notifications but adsprpcd is still draining my batt.. but i have all camera on and sound on all time on.. wtf??
im running on ice rom with elementalx kernel on M9..
BLEK0TA said:
i have same problem as u.. but to me didnt help clear notifications.. i have disablet nu player, voice recognition and after read your post im clearing all time my notifications but adsprpcd is still draining my batt.. but i have all camera on and sound on all time on.. wtf??
im running on ice rom with elementalx kernel on M9..
Click to expand...
Click to collapse
Yes. I have since had to change that opinion but never updated my post since no one responded.
Do you by any chance leave your data on 3g only?
Im on LTE still with still turned off wifi but in batt history and gsam batt history is still on..
BLEK0TA said:
Im on LTE still with still turned off wifi but in batt history and gsam batt history is still on..
Click to expand...
Click to collapse
I figured as much. It's still a mystery to me. I've gotten to where I just ignore it. When I see it start showing up at the top of gsam I just reboot. I've no idea what makes it run constantly like that. I'm hoping when I update to mm soon it will go away but I'm not holding my breath
So Wi-Fi is solved.. cuz in settings is in lollipop in Wi-Fi settings default enabled Wi-Fi for location so this is solved for me.
but adsprpcd still comsupt too much batt life .. BTW WTF is audiomix?
BLEK0TA said:
So Wi-Fi is solved.. cuz in settings is in lollipop in Wi-Fi settings default enabled Wi-Fi for location so this is solved for me.
but adsprpcd still comsupt too much batt life .. BTW WTF is audiomix?View attachment 3579628
Click to expand...
Click to collapse
Audio mix is something like a wakelock for when you get a notification I do believe
razen_kain said:
Audio mix is something like a wakelock for when you get a notification I do believe
Click to expand...
Click to collapse
Same problem here. I pulled out my SD card now which I had all my mp3 songs to see if it is the reason for this wakelock. Before that the following screenshots show my situation:
I want to add also that I'm on mm 6.0 (jw version) with xposed installed.
Στάλθηκε από το HTC One M8 μου χρησιμοποιώντας Tapatalk
I also notice this on Lollipop but today I finally found what is causing this wakelock for me: notification about battery saving when I turn on Extreme battery saving. It's weird, but it's true. How I noticed it? Yesterday I read on xda that this wakelock is causing by notifications. After last night, when I always turn on extreme battery saving, I saw that adsprpcd has about 8h, what is exactly same time I was sleeping. I tested it once again: I checked how much time adsprpcd had, then turned on extreme battery saving, turned it off after a minute and again check time - it increased. Because I have Xposed I installed NotifyClean, remove notification about battery saving and repeated test, time didn't increase Adsprpcd can be caused by other notifications I think, I will examine it.
But as mentioned on xda, I don't see really impact on battery by this wakelock, because I lost 1-2% per night, when adsprpcd increase time.

Android System always higher ?

Guys got my OP3 few days back but what I'm noticing is that after 2-3 days that my Android System is higher then Screen usage which wasn't before. Never facing this kind of drain before on OP3 or on my Nexus 5 that I used to use before. Is there anything unusual? I'm attaching screenshot of better battery stats also please do look into them.
Anyone ?
I had the same issue resulting in terrible battery life since Android System was constantly working the CPU. It's probably due to the Oxygen OS kernel. I sent back my unit and asked for a replacement because I didn't want to install a custom ROM on a brand new phone just yet.
Same issue here, Android System uses more battery than my screen. Also it looks like the phone was awake all night tonight with screen off, so I had more standby drain.
This is most likely due to an app that has a rogue process running in the background constantly keeping gms awake. Try clearing data for the play store and turning off sync for any apps you have. See the drain overnight and report back.
Same problem here... "Android-System" is consuming the highest amount of all my other apps ...
My OP3 has a lifetime of about 6-8 hours ...
Yeah even it's the same for me... Even did a factory reset but didn't help
Sent from my ONEPLUS A3003 using Tapatalk
Facing the same problem. Amplify Forcedoze and Greenify don't help
Turn off the auto sync. I am consistently getting 8hrs SOT. Using LTE and wifi.
Sent from my ONEPLUS A3003 using Tapatalk
nickporwal said:
Turn off the auto sync. I am consistently getting 8hrs SOT. Using LTE and wifi.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
when you turn off auto sync, does whatsapp still work without having to manually sync every now and then? afaik, most of the social apps rely on this sync to function properly and having to manually sync every time for whatsapp or twitter would defeat its purpose.
sahirhussain said:
when you turn off auto sync, does whatsapp still work without having to manually sync every now and then? afaik, most of the social apps rely on this sync to function properly and having to manually sync every time for whatsapp or twitter would defeat its purpose.
Click to expand...
Click to collapse
Whatsapp doesn't use sync to fetch messages. Sync is for syncing contacts on Whatsapp
guys try disabling ambient mode and see if that lowers the android system drain.
i'm checking it myself on my op3
That does not work for me. I have everything disabled - daydreams, ambient, proximity wake, Google now, now on tap, auto sync, oneplus launcher but android system continues to take up more battery even when the screen is off.
The Opskin package is included in Android system, maybe rendering the ui drains more battery
I think I fixed this by disabling "location" and/or "location determination" (DE: Standortbestimmung)
cruzs said:
I think I fixed this by disabling "location" and/or "location determination" (DE: Standortbestimmung)
Click to expand...
Click to collapse
Nope ... not fixed

Insane battery graphs consistently

I have been having these kinds of battery graphs since very long time. Using stock oos 4.0.3 without root and have locked bootloader.
I tried cleading data of google play & service' apps and even cleared cache from recovery. Disabled the hibernation feature in battery settings and enabled doze from developer options. This made no effect. So switched back to default settings again.
Ashish.akc said:
I have been having these kinds of battery graphs since very long time. Using stock oos 4.0.3 without root and have locked bootloader.
I tried cleading data of google play & service' apps and even cleared cache from recovery. Disabled the hibernation feature in battery settings and enabled doze from developer options. This made no effect. So switched back to default settings again.
Click to expand...
Click to collapse
What's the problem exactly?
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
What's the problem exactly?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Phone doesn't doze' properly. It stays awake even when am not using it and drains battery a lot. I have seen phone getting warm several times even when it's just lying. SOT is very poor considering i have not changed my usage scenario and have given a lot of time for the OS to settle properly as well..
Here's another screenshot just after i woke up. Phone was chraged upto 98% when i went to sleep and it came down to 65%
Ashish.akc said:
Here's another screenshot just after i woke up. Phone was chraged upto 98% when i went to sleep and it came down to 65%
Click to expand...
Click to collapse
Your phone is awake most of the time. Install BBS from its thread in XDA, learn how to produce idle logs in BBS and post one in the BBS thread.
Mind you, on Nougat, there is not much option for controlling alarms/wakelocks except using Greenify and MyAndroidTools. No Xposed and so no Amplify.
Ashish.akc said:
Here's another screenshot just after i woke up. Phone was chraged upto 98% when i went to sleep and it came down to 65%
Click to expand...
Click to collapse
Did you turn on the aggressive doze option? I bet you have some app like Facebook keeping the phone awake. The other answer to grab BBB is a good idea
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
Did you turn on the aggressive doze option? I bet you have some app like Facebook keeping the phone awake. The other answer to grab BBB is a good idea
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Yes i have enabled the aggressive doze and about the facebook draining, i think it is not from facebook because i rarely use it and it appears rarely in battery stats.
Here are some screenshots from BBS:
Custom one is when in the evening i had set the custom ref. after clearing all recent tasks. Check these if get something from these. I don't see any deep sleep stats any given time
Ashish.akc said:
Yes i have enabled the aggressive doze and about the facebook draining, i think it is not from facebook because i rarely use it and it appears rarely in battery stats.
Here are some screenshots from BBS:
Custom one is when in the evening i had set the custom ref. after clearing all recent tasks. Check these if get something from these. I don't see any deep sleep stats any given time
Click to expand...
Click to collapse
You need to get an idle dump of at least 6 hours along with screenshots of the battery and battery history page of Settings. These screenshots are not going to help anyone to analyze your issue.
install logcat and see if it spams same error message over and over.

High battery drain with doze overnight

I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
bosox284 said:
I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
Click to expand...
Click to collapse
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it ?
Badger50 said:
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it
Click to expand...
Click to collapse
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
I wouldn't worry about turning off AOD saving you a bunch, I turned mine off and didn't notice any diff at all in overnight batt drain, so set it to DIM, and still haven't noticed any additional batt drain from when it was off.
If you really want to be a miser without totally losing AOD,
"always on" OFF,
"Lift to check phone" ON,
(Settings>Display>Ambient display>)
set it to DIM (Settings>Display>Screen Saver>Current Screen Saver gear>Night mode checked)
which is how mine is set up
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
Where is that fix touch module?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Where is that fix touch module?
Click to expand...
Click to collapse
Look in downloads in magisk manager.
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
bosox284 said:
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
Click to expand...
Click to collapse
Delay what? ?
Badger50 said:
Delay what? <span class="emoji-outer emoji-sizer"><span class="emoji-inner" style="background: url(chrome-extension://immhpnclomdloikkpcefncmfgjbkojmh/emoji-data/sheet_apple_32.png);background-position:73.97179788484137% 79.9647473560517%;background-size:5418.75% 5418.75%" data-codepoints="1f914"></span></span>
Click to expand...
Click to collapse
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
bosox284 said:
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
Click to expand...
Click to collapse
Haven't noticed any delay what so ever with any push notifications from any apps. Google or otherwise :good:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
I noticed this as well and it seems to have started after the January update. Although mine isn't quite as bad. Pre-January update I was losing about 2-3% in like 8 hours. I'm now losing that much in like 4-5 hours. There were 2 days in a row where I actually lost like 15-18% over like 7 hours.
rickysidhu_ said:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
Click to expand...
Click to collapse
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
The Jan update has been ****. I would get almost 7 hrs SOT with 20% left. Now all I get is ****ty 4 hrs and phone at 10%. Usage wise it's the same since day 1 nothing new as such. No rogue app on BBS. This is messed up.
Badger50 said:
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
Click to expand...
Click to collapse
Yeah I had a feeling that could be it. I'll give it a shot by removing them, thanks for the suggestion! :highfive:
Badger50 said:
Look in downloads in magisk manager.
Click to expand...
Click to collapse
It isn't there that's why i asked
Sent from my Google Pixel 2 XL using XDA Labs
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Try to run "su" and then "top" from terminal,
See what is your top process,
In one occassion, my magisk hide stucked up and using 30%++ of CPU all the time, even when idle, and that drain the battery in no time,
Am on 8.1 Jan, Kiriskura Kernel,
Tweak applied is Brevent, Amplify and my own EnableDoze for GMS.
Never lost more than 5% in 9 hours of sleep. Average is 2-3% with wifi on. Less than 2% when network is totally off
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
You can try the one attached.
I cant find it in download section as well
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
My bad. I forgot that it was a special build by another user. Install it from magisk manager. If it doesn't install, then flash it in twrp.
https://github.com/AndroPlus-org/ma...b/master/magisk-module-fix-touch-pixel2xl.zip

Question GSAM Battery Monitor - How to find wakelocks? What is preventing me from deep sleep?

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

Categories

Resources