Before I begin, let me state that I have already factory reset countless times and reflashed my firmware at least 3 times in the past week. Neither of these have helped me at all, so PLEASE do not suggest this. I've been trying to solve this problem for a week or two and everyone has suggested this to me and of course I've already done it, so it hasn't helped me at all.
PHONE: E980
FIRMWARE: Stock 4.4.2 E98020g
BASEBAND: APQ8064/MDM9x15M
SYMPTOMS:
-Battery draining ridiculously fast (appx 10%/hr, but before my last reflash, it was draining 50%/2hrs!)
-Phone only lasts about 5hours.
-Android OS is consuming about 80-90% of battery, followed by Screen at around 10%
-Phone is constantly warm
-Phone rarely enters Deep Sleep (it stays awake 95% of the time).
TESTS DONE:
-As I said, I factory reset numerous times with the same exact problem
-I reflashed my firmware 3x, with same problems
-I usually keep auto-sync on, but the issue occurs whether it is on or not.
-There is supposably a Kitkat 4.4.2 (in general) issue where the camera will consume a ton of CPU resources and get stuck that way. I haven't used my camera much, but do use Smart Stay, so I disabled this. No positive result.
-Disabled the Google Now "OK Google" hotword detection. This helped reduce the drain, but didn't solve it. Drain went from like 15%/hr to 10%/hr.
-Took battery out of phone for 10 minutes and placed back in. Seemed to help at first, but after about an hour or so, it returned.
-"Recalibrated" the battery numerous times. This was done by draining the battery until the phone shut itself off. Then I charged the phone to 100% while the phone was still off. Once the phone read as having 100% charge, I let it charge for another 1 hour. Then I unplugged the phone and booted it up. Again, this appeared to help at first, but after a while, the phone began to drain rapidly again.
NARROWING THE ROOT PROBLEM:
-Both WakeLock Detector and BetterBatteryStats show "wlan_wake" and "wlan_wd_wake" as being the largest wakelocks.
-As previously mentioned, "Android OS" is consuming a huge amount of battery
-Problem only seems to happen when wifi is on, whether it is connected to an SSID or not.
OTHER:
I have narrowed the issue down to wifi but I can't seem to figure it out any more than this.
Both of the "wlan_" wakelocks are caused by wifi being on and I need wifi on whenever possible because I can't afford a huge data plan. My current one is 2GB/mo and it is shared between 3 people.
I noticed today that my phone drained 10% within 1 hour after taking the phone off the charger, and I was connected to my home wifi. I then went to work, but still had wifi turned on on my phone. At work, I was only connected to mobile data (but the phone was just sitting in my pocket). The battery drained another 15% within an 1hr 30min, and the phone was warm in my pocket (very uncomfortable!). I then turned wifi off completely, and the battery drain completely disappeared!!! The battery life was amazing in fact!
PICTURES:
I've provided some screenshots with notes. Please take a look at them.
I'm going to manually make the problem happen again and will upload new pictures afterwards. They will be of WLD and BBS. Any current info I have is tainted since I turned wifi off and the problem temporarily turned off too. I want to get only screenshots of what is going on when the problem is happening.
EDIT: BTW, the problem occurs whether my mods are installed or not (the mods used to remove the icons in statusbar, AdAway, etc)..
The issue seems to be pureply related to wifi and nothing else.
IDEAS:
Could adding a wifi supplement scan interval to the build.prop solve this problem?
Is Wifi bugged in this firmware? (This never happened on Jelly Bean!!!!)
Is maybe the "Battery Saving for Wifi" feature bugged?
Would maybe flashing the Jelly bean modem (e98010p) solve this issue (since it didn't happen on Jelly Bean)? If so, does anyone have a flashable version of this? <- I just did some research and it seems that the baseband (AKA modem) is the same in Kitkat as it was in Jelly Bean. Weird....
These pictures were taken shortly after making my first post. I already had wifi turned off, so I turned it back on and after a few minutes, the battery began to plummet. I went from roughly 77% to 66% in just an hour!!!!
Just to make sure that it is clear, I have both BBS and WLD set to start recording data after the phone has been unplugged from the charger. So to restart the data collection, I simply plugged the phone into my charger for a few seconds and then removed it. THEN I turned wifi on. The data seen in the pictures should only have occurred between the time when I unplugged the phone and the time I took the pictures.
EDIT: Also just to make sure it's clear: All the data shown in the System picture is actually since I unplugged the phone this morning. I only posted these pictures to show any changes from the similar ones posted earlier.
PLEASE! Can anyone help me solve this!?
Or is this a major Kitkat bug!? (or ATT bug, or modem bug, etc etc).
After a full week of this problem, I think I just made another breakthrough. Unfortunately, I think it IS one of my Xposed modules, which is weird because I didn't think any of them would have a need to constantly connect to the internet.
All I know is that I just completely uninstalled the Xposed Framework and the phone started to sleep like a baby... with wifi on!
Now I just need to pinpoint the module, which I can do myself.
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
spexwood said:
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
Click to expand...
Click to collapse
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Toledo_JAB said:
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Click to expand...
Click to collapse
In this case, I need to be more specific about my solution then.
The problem seems to be caused by the module, Xposed Torch. It's still usable, but you need to tap the overflow (3-dot) icon and disable ads (it's free to do this). The module requires internet access permissions, which I was not aware of, and it constantly connects to the internet to stream the ads. This in turn causes the wifi to constantly receive data (thus the wlan_wd_wake and wlan_wake). When wifi is on, but not connected to a network, I think it forces wifi to constantly scan in order to find a connection so that it can get that ad data. I'm not sure why it doesn't just use mobile data though... unless it does and it's just more power efficient.
So far, I have disabled the ads via module settings and the phone is now sleeping like it should.
So if anyone else is having wlan_wake wakelocks of any kind, especially followed by wlan_wd_wake or wlan_rx_wake, then this means that something on your phone is constantly accessing the internet via wifi. FIrst turn off auto-sync, and if this doesn't help, then you need to uninstall apps until the problem ceases.
My phone is currently icy cold in my hand and I've never been so happy to feel it like this!
Problem came back today. I've basically uninstalled every app now and the battery is still draining whenever wifi is turned on.
Under Better Battery Stats, there is a process (?) called dhc_dpc that's been running the entire time my phone has had wifi on. There are also the wlan_wakes too. (NOTE: IIm backing up my phone right now, so these names are coming from memory).
According to this thread (different phone and unknown Android version, but similar problem), the wifi driver may be bugged. They recommend doing a reinstall, but I've done this many times now and it doesn't seem to help:
http://forum.xda-developers.com/galaxy-s2/help/dhddpc-t1246190
EDIT: I think I've found the culprit and while it is definitely wifi-related, it's NOT an app. It's the actual Android system constantly pinging the internet. According to my research, it's constantly collecting location data by using either mobile data or wifi and will do this whether you have location services (gps) or Location Reporting enabled. This has been described as a "bug." It was introduced by Google as a cool new feature, but it's implementation was buggy.
I am currently testing a fix to resolve this issue, but want to be certain that it's fully working first.
Just an an FYI, this fix SHOULD help anyone running Android 4.4.2 and experiencing high battery drain caused by Android OS. Even better, the fix does not require root, so anyone can do it!
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
3617 said:
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
Click to expand...
Click to collapse
Not to be rude, but the first sentence of my first post says I did this several times.
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
zamajalo said:
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
Click to expand...
Click to collapse
It's definitely Xposed related I think.
I've disabled Xposed during some testing a day or two ago and yeah, battery definitely improved.
The only modules I have installed are:
App Settings
Enable BatteryStats Permission (just to allow me to track this issue. I installed this after problems had already begun)
Greenify (all Xposed settings checked)
YouTube AdAway
I have also been using G2 TweaksBox up until last night. I only used it to declutter my status bar and to enable the advanced reboot menu. (I hate all the icons in the status bar!!!). Last night I disabled G2 TB and battery life improved dramatically!
I can't explain why G2 TB would cause battery drain, but I did notice it doing something odd yesterday. I have the lockscreen off sound enabled in the system settings, so I hear the sound whenever I lock the screen. Well, I turned my phone on yesterday for some reason when in my car. I then turned the screen off, heard the lock sound, and started driving. 15 minutes (NOT seconds!) into my drive, I randomly heard my phone make the locking sound, but the screen was not turned on!! I wonder if G2 TB delays my lock somehow.
I switched to GravityBox[KK] today since so many people claim that it works perfectly on their OGP, and so far, battery drain is MUUUUUCH better than with G2 TB activated, but it still may not be as good as pure stock. I need more time to figure it out though. This morning, my battery dropped 5% in 40 minutes while connected to my home wifi. I then left my house for a few hours, but left wifi turned on on my phone (it's hard for me to remember to switch it off and on all the time!). The battery seemed to be pretty stable after that, but I can't explain the weird 5% drop, but I did receive 2 missed calls and a text during that time too. Should I lose 5% just from getting a text and having my phone ring?
It's now night time and I'm at 75% battery. This past week, I would be at about 10% by now or even DEAD, so I'm happy as heck right now.
I would LOVE to be able to keep using GB, but I now just need to figure out if it too is draining battery, or if everything is stable. I'm going to continue comparing stock VS GB tonight and tomorrow. I'll live with stock if needed, but I'm just very OCD about the statusbar clutter.
In GB, I only disabled some icons, centered the clock, enabled advanced reboot menu, and enabled the lockscreen torch.
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
zamajalo said:
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
Click to expand...
Click to collapse
OK, so I just got home from work and today I not only had GravityBox disabled, but I also had the ENTIRE Xposed Framework uninstalled.
My battery is now at 30% and I was only gone for 7 hours!!!!!!!!!!!!!!!!!! This is ridiculous!!!!!!!!!
*sigh* <- frustrated with this whole situation
Yes, the wakelocks are still active.
The top two Kernel Wakelocks are "wlan_wd_wake" (46.3%) and "wlan_wake" (46.2%) in that order. The next in line is "PowerManagerService.Wakelocks" (8.0%) and then "msm_hsic_host" (6.1%). This was since my last reboot, which was about 2 hours ago (I had to rebooted after removing an app that I thought was the culprit... apparently it wasn't).
Again, I keep Auto Sync on, but disablign it seems to not help in this matter at all.
I also keep wifi on. When at work, it isn't connected to a network, but I often forget to disable wifi when I leave the house, or I come home and forget to enable it and end up sucking my data plan dry. Nonetheless, I also did this while on Jelly Bean and had no issues whatsoever.
My phone is only staying in deep sleep less than 10% of the time and the time when it is awake, the CPU is running at full 1.7GHz! This is causing the phone to get warm in my pocket. It doesn't hurt, but it's enough to make things uncomfortable.
According to the battery stats (in system settings), Android OS is consuming 83% of the battery.
The biggest network drainers are "Google Play Services" (33.3%), something simply called "0" (14.8%), and a weather app. I had the weather app open manually not too long ago though, so that explains that one, but the other two I can't. I have no clue what "0" is and I have not opened Play at all today.
It's something to do with wifi itself I think, and maybe not a specific app accessing wifi. (?)
I turned wifi completely off about an hour ago and the battery drain has been stable. It's been like this for days too. If I turn off wifi, the drain is "normal." If wifi is on and connected, drain is higher than with wifi off, but barely. If wifi is on and not connected, the battery level plummets like a rock in a pond.
OH! One thing I just thought about and should mention:
Before I discovered that G2 TweaksBox was causing serious drain, I was on another battery-related thread in the OGP forum. Someone told me to delete the "libiq_client.so" file from System/lib. He assured me this would give me excellent battery life (which apparently it did not). So I did. Normally, I just rename system files so I can restore them if needed, but I guess I accidentally deleted this one.
Could this be causing the drain, and if so, can someone upload a copy of libiq_client.so so I can try it on my phone (after setting it's permissions correctly)?
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
zamajalo said:
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
Click to expand...
Click to collapse
"Scanning always available" has been disabled since day 1
The only nand backup I have is after I already deleted the file :/
I did try clearing Google Service's cahce/data at one point and I think it helped for a few hours. It may have been a placebo effect though. I also di the recovery cache wipe and dalvik wipe with same results.
I don't keep location on at all since I don't use it. It's always off, but at one point, I did enable it to select the battery mode and then turned it off again. I did this mainly so that if and when I do use location, it would always use Battery and not High Precision.
I'm currently backing up my rom, so all partial wakelocks were cleared for now. Sorry.
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
spexwood said:
"Scanning always available" has been disabled since day 1
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
Click to expand...
Click to collapse
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
zamajalo said:
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
Click to expand...
Click to collapse
It's OK, I'll get the file from the flashing. I know it'll be a pain, but this may be safer just in case there is some sort of difference between the E988 and E980 versions. I doubt there would be, but better safe than sorry I guess.
I did add those settings to my build.prop as a test, but I was smart there and backed up my stock build.prop first and ended up restoring it a few hours later. It was causing my screen to not always turn on when I pressed the power button.
I have not tried any other ROMs. I prefer to stick to stock ROMs (or modified versions of stock... basically anything stock-based and not CyanogenMod or AOSP). I had bad experiences with AOSP-based ROMs on my old phone.
If I tried a stock-based ROM though, it must have everything working though. I mean everything: calls, texts, LTE, bluetooth, speaker phone, etc etc.
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
spexwood said:
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
Click to expand...
Click to collapse
Better to misplace than to delete it, trust me
Post results.
zamajalo said:
Better to misplace than to delete it, trust me
Post results.
Click to expand...
Click to collapse
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
spexwood said:
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
Click to expand...
Click to collapse
Libiq.so enables carrier IQ, its removal should only help battery drain, not cause it.
Just to ask, have you tried adjuating wifi scan interval? You can try as well the xposed module, "wifi deep sleep". Helped minimize my wifi related drain
I would have posted directly to the PurpleDrake thread in development but the forum wont let me.. (New User)
Since rooting my G3 (D855 with 10e) the battery is draining really fast, even on standby.
When in use you can actually see the % battery going down.
All I have installed is Titanium, and Droid Mate App Ops.
The only things I have changed are a few permissions for Facebook, and a couple of games.
I've looked at running apps and the battery usage, and I can't see anything strange.
Any ideas, or should I un-root?
Cheers
Neo_Ge said:
I would have posted directly to the PurpleDrake thread in development but the forum wont let me.. (New User)
Since rooting my G3 (D855 with 10e) the battery is draining really fast, even on standby.
When in use you can actually see the % battery going down.
All I have installed is Titanium, and Droid Mate App Ops.
The only things I have changed are a few permissions for Facebook, and a couple of games.
I've looked at running apps and the battery usage, and I can't see anything strange.
Any ideas, or should I un-root?
Cheers
Click to expand...
Click to collapse
Most likely it's not your root causing the issue.
You might want to check this out
navlem said:
Most likely it's not your root causing the issue.
Click to expand...
Click to collapse
It was fine before rooting.
Neo_Ge said:
It was fine before rooting.
Click to expand...
Click to collapse
that will simply be a coincidence, there is nothing root itself can do that would cause battery drain.
The chances are it's some application or something you changed which is causing the battery drain like lennyuk said root won't cause battery drain at all.
daleski75 said:
The chances are it's some application or something you changed which is causing the battery drain like lennyuk said root won't cause battery drain at all.
Click to expand...
Click to collapse
I only installed Titanium and App Ops after root, and neither run in the background.
The only other change is I now have the quick circle case, which I fitted a couple of hours after rooting, but I can't see how that would have any affect.
Could the changing of permissions for Facebook etc with app ops. cause problems with battery life?
Maybe continuous polling for a response on a permission I blocked (like send sms). I will revert all the permission changes and see what happens.
Neo_Ge said:
I only installed Titanium and App Ops after root, and neither run in the background.
The only other change is I now have the quick circle case, which I fitted a couple of hours after rooting, but I can't see how that would have any affect.
Could the changing of permissions for Facebook etc with app ops. cause problems with battery life?
Maybe continuous polling for a response on a permission I blocked (like send sms). I will revert all the permission changes and see what happens.
Click to expand...
Click to collapse
Revert it on Facebook first as that's probably the biggest culprit I reckon.
Download wake lock detector and find out what's not letting your device go into deep sleep. Also download something that will allow you to monitor your cpu. If your cpu is running at high frequencies for long periods of time then there's an app somewhere that is causing this issue. Like others have said root can not cause battery drain. Root is not an app that runs in the background giving you admin privileges. It runs ones and that's it. Also the changing of the resolution isn't advised. I have my resolution set at its default and get about 5 hours screen on time with 15+ hours off the charger
Sent from my LG-D850 using XDA Premium 4 mobile app
High battery drain.
The same here!
After root my LG G3 D855 with purpledrake I note high battery drain.
I simply root my device, install TWRP recovery and made device complete backup.
I installed "supersu", "flashify" (to install recovery), "quick boot", "nexapp SDFix" (to fix KitKat SD write issue).
I gave root permission (by SuperSU) to ES File Explorer, Flasjhify, QuickBoot, SDFix.
No other change.......
Why battery drain so fast, now?
Thanks.
PS I see battery drain graph with "GSam Battery Monitor" (installed since I buyed my G3).
Edit 2. I install "wakelock detector" and I found "SuperSU" using screen for 8h 43m... The second was Torque with 12m 21s.
Why SuperSU use so more resources?
For some reason my M9 doesn't want to go into deep sleep much. Out of the 1 hour I have it off the charger, only 2 minutes were in deep sleep. I haven't used the phone at all in that 1 hour, so I'm not sure why it wouldn't be sleeping.
Does anyone have this problem or know how to fix it? Thanks
https://play.google.com/store/apps/details?id=nextapp.systempanel.r1
Buy, install, do proper settings, put it into monitoring mode.. then switch of screen and go sleep - in the morning see the activities what were happening during the night monitored..
jauhien said:
https://play.google.com/store/apps/details?id=nextapp.systempanel.r1
Buy, install, do proper settings, put it into monitoring mode.. then switch of screen and go sleep - in the morning see the activities what were happening during the night monitored..
Click to expand...
Click to collapse
I've used a very similar app. There are no wake locks. All it says is "Android OS" is using 100% of the screen off battery. Even in the normal HTC battery settings, android OS is using 100%. Thanks for the help though.
System Panel is neither similar nor showing you those funny wakelocks..
It thoroughly informs you about CPU usage last night..
jauhien said:
System Panel is neither similar nor showing you those funny wakelocks..
It thoroughly informs you about CPU usage last night..
Click to expand...
Click to collapse
Thanks, but all those apps are the same. They can only get a certain amount of info from the core system. There are apps that do the exact same thing for free, which is what I use.
As an update to my problem, rebooting the phone and clearing cache seemed to have solved the issue for now.
aooga said:
Thanks, but all those apps are the same. They can only get a certain amount of info from the core system. There are apps that do the exact same thing for free, which is what I use.
As an update to my problem, rebooting the phone and clearing cache seemed to have solved the issue for now.
Click to expand...
Click to collapse
If you run out of ideas on how to fix this, I'd say get root, get Xposed, and get Power Nap. Pretty much blocks all wakelocks at night and I see like 1% drain the next morning.
Cryosx said:
If you run out of ideas on how to fix this, I'd say get root, get Xposed, and get Power Nap. Pretty much blocks all wakelocks at night and I see like 1% drain the next morning.
Click to expand...
Click to collapse
Wait...xposed works on 64bit phones? Wow I've been missing out for nothing lol.
Yes, but make sure you use the xposed arm64 file.
This thread has the stuff
Here's the zip you want xposed-sdk21-arm64.zip
And you also need the alpha installer.
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?