Related
Hey everyone
Got a Nexus a couple weeks ago after having iphones for a couple years. Loving it so far.....ICS is very polished.
Initially, my battery life was adequate. However, recently the OS is using 45% battery and the phone gets a very hot when idle (I can feel the heat in my pocket)
I did a factory reset and still the same problems.
Is anyone else coming across these issues?
An old bug cropping up again?
http://forum.xda-developers.com/showpost.php?p=13247149&postcount=57
Can you please install Watchdog (https://market.android.com/details?id=com.zomut.watchdoglite) and let us know if it's the suspend process (which shows up in the battery meter as part of "Android OS") burning through the battery?
My phone has been on standby for about a day and has 80% battery left. However the battery consumption shows:
42% Android OS
37% Phone Idle
16% Cell Standby
- Also what is the difference between phone idle and cell standby
MY BACKGROUND APPS RUNNING ARE:
- Battery Monitor Widget (I need this on so I can tell what my battery life is easily)
- Google Services (What is this, can I kill it?)
Media (What is this app, can I kill it?)
Music (Again what is this, what happens if I kill it/should I? I never used it.)
I have the same problem. My SGN died after 7 hours without any usage.
Sent from my Optimus 2X using XDA App
Yup, me too. This morning, I took my phone off the charger at 98% for an hour and 15 minutes and didn't touch it. The battery had gone down to 88%, with Android OS using 64% and Android System using 14%. The phone was 'awake' for the entire period. I've had my Nexus since Wednesday and I haven't been getting great battery life. I'm hoping there's a fix for this.
Same problem here... (I testing radio UGKK7, XXKK7 and XXKK1... all with the same problem).
- Lightflow increment "Android OS" battery use.
- By using, Wi-Fi "Android OS" uses less battery.
try disable wifi when not on and unchecked "use wifi network" for location.
another thing could be some active widgets, i remember this was a problem a while back.
Note sure that this has got to do with wifi at all as I reset my phone to factory and I still have the 'Android OS' usage taking 23% of battery. I have no apps nor have I yet linked phone to my Google account.
I have read some comments to do with the Galaxy S2 which too suffered from the same problem. I remember reading something about Samsung driver implementation causing this with the S2. I will update the links when I find something conclusive. Also I have another HTC desire that has the AOSP code compiled rom and that does not suffer from this at all and it is happily sitting idle at almost 2 days with nearly 70% battery still left.
s1977 said:
Note sure that this has got to do with wifi at all as I reset my phone to factory and I still have the 'Android OS' usage taking 23% of battery. I have no apps nor have I yet linked phone to my Google account.
I have read some comments to do with the Galaxy S2 which too suffered from the same problem. I remember reading something about Samsung driver implementation causing this with the S2. I will update the links when I find something conclusive. Also I have another HTC desire that has the AOSP code compiled rom and that does not suffer from this at all and it is happily sitting idle at almost 2 days with nearly 70% battery still left.
Click to expand...
Click to collapse
Yes, the problem was with the suspend process eating up CPU. You can install Watchdog and set it to watch non-Android processes, and that will be able to tell you which "Android OS" process is actually the one eating up battery.
Chirality said:
Yes, the problem was with the suspend process eating up CPU. You can install Watchdog and set it to watch non-Android processes, and that will be able to tell you which "Android OS" process is actually the one eating up battery.
Click to expand...
Click to collapse
Is samsung aware of this problem? We need to file complaints.
Sent from my Galaxy Nexus using xda premium
Do you have your email or anything set up to receive things instantly? That can have a noticeable impact on your battery if so
Thanks Chirality, but I assume that this is happening to all users? Samsung have seen this before so shouldn't this be fixed from the very start? Wrong person to ask this question to, but it is annoying..
Anyways I will install Watchdog like you say, but unless I can kill the 'suspend' process, I am helpless.
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
xHausx said:
Do you have your email or anything set up to receive things instantly? That can have a noticeable impact on your battery if so
Click to expand...
Click to collapse
No, that's why I reset the phone to factory settings and the current behaviour is without any apps, or registration with google, no emails, nothing installed.
---------- Post added at 10:03 AM ---------- Previous post was at 10:00 AM ----------
Additional links indicating the problem and response:
http://androidforums.com/samsung-galaxy-s2-international/337492-s2-battery-drain-problem-solved-now.html
http://code.google.com/p/android/issues/detail?id=16721
Is there anything in the logcats that could hint to a problem? Like errors or something unusual that it keeps repeating
I have the same problem with high system CPU usage. I used SystemPanel to monitor the phone (unplugged, standby mode) during my 8-hour sleep and here's the results.
The System Processes were using 49min of CPU time while the phone was idle
When I clicked on the system processes I got a list of individual processes. Anyone knows what are there kworker processes for?
When I clicked on one of the System Processes (kworker/u:1), I got its CPU usage. It was doing something almost the whole time
Finally, I should also mention that the phone lost about 7% in these 8-hour test. Seems ok but I think it would be even better when this high system CPU usage is fixed.
xHausx said:
Is there anything in the logcats that could hint to a problem? Like errors or something unusual that it keeps repeating
Click to expand...
Click to collapse
Hmm...Now that you asked this, I remember watching logcat output and was getting a null Notification event almost one every minute a couple of days back. I therefore proceeded to uninstall all my widgets/apps but I could not reach to a conclusive outcome.
Anyways as Chirality pointed out this post (Link) indicates a 'suspend' process issue. And this guy identified the process causing it (Link), I think!
s1977 said:
Hmm...Now that you asked this, I remember watching logcat output and was getting a null Notification event almost one every minute a couple of days back. I therefore proceeded to uninstall all my widgets/apps but I could not reach to a conclusive outcome.
Anyways as Chirality pointed out this post (Link) indicates a 'suspend' process issue. And this guy identified the process causing it (Link), I think!
Click to expand...
Click to collapse
A driver issue definitely sounds plausible but there are also a lot of things different between these two phones, especially between GB and ICS.
Watching /proc/kmsg should show something if it is an issue with the kernel
xHausx said:
A driver issue definitely sounds plausible but there are also a lot of things different between these two phones, especially between GB and ICS.
Watching /proc/kmsg should show something if it is an issue with the kernel
Click to expand...
Click to collapse
Do i need to be rooted to be able to read this?
Chirality said:
Yes, the problem was with the suspend process eating up CPU. You can install Watchdog and set it to watch non-Android processes, and that will be able to tell you which "Android OS" process is actually the one eating up battery.
Click to expand...
Click to collapse
Chrality, xHausx
I have installed Watchdog and set the settings to what you indicated. I am a bit confused around the app, so I have added screenshots to update you of the data at my end.
Do let me whether you see the issue immediately or need any further information.
My experience is somewhat the same.
Out of the box battery life seemed pretty good. After the update to fix the volume issue I started to notice that the battery would fall even when the phone was idle. Android OS was the culprit. I am now running MCR and I have the same issue.
It's not terrible battery life, but it's substantially worse than it was out of the box.
I did wonder if the problem was related to how they fixed the volume bug. Is something always running to pick up the volume bug problem and deal with it when it happens?
Just a thought.
paulpenny said:
My experience is somewhat the same.
I did wonder if the problem was related to how they fixed the volume bug. Is something always running to pick up the volume bug problem and deal with it when it happens?
Just a thought.
Click to expand...
Click to collapse
Interesting. I've been thinking the same thing, and the annoying thing about that is the problem doesn't affect my network (T-Mobile), so I could be getting reduced battery performance for no reason! Ah well.
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.
Hi guys!
I desperately need some help from you experts. I have recently noticed my LG G3 has been draining more battery than it should, especially when idle (or at least, theoretically when idle).
Please take a look at the sequence of screenshots (have in mind the analysis was made overnight, when the phone was sitting idle on my bedside):
Screenshot 1: You can see app usage has been the biggest juice thief, and an abnormal drain (24%) for a (supposedly) idle period of 6 hours.
Screenshot 2: Kernel & Android system are the biggest villains, but only sums up to 45%.
Screenshot 3: Taking a deeper look at Kernel, it shows only 7 minutes of CPU usage.
Screenshot 4: A deeper look at Android system also shows a small usage, only a few seconds shy of 6 minutes.
Screenshot 5: On the chart, we can see there was an absurd drain (around 20%) from 1:30 am to 5 am, and then it got stabilized. Wifi was on the whole time, and you can see it shows the phone was (theoretically) dozed 95% of the time.
Sctreenshot 6: Even though the phone was dozed, we can clearly see it has severe CPU usage throughout the whole night, and no pattern could be distinguished between the hours were the battery got the severe drain and the hours after. Even though the CPU frequency was low between 1:30 and 5 (except for a couple of peaks), the utilization averaged 45%.
This is why I need some expert's help. I cannot understand what is draining my battery, what is keeping my phone's CPU util so high... can someone please shed a light on this for me?
Thanks in advance!!! :fingers-crossed: :good:
Hello there guys. Anyone could please take a look at this and try and help me out?
Thanks!!!
Well, it's hard to answer simply such a complicated problem. There are so many variables to consider, but I would say rule out a few things first.
First, if you have TWRP installed, backup your current ROM and do a complete factory reset. If the problem persists, then you know it's something built into your ROM causing it and I would suggest swapping out that ROM for another. If the problem is gone, you know it's something you installed or modified in the ROM and you can start to narrow that down.
Second, I would try out the app WakeBlock. It's still in development, but it allows you to see active wakelocks (Android programming object used to keep the CPU running even if dozed) and block them if you want to. But the app may be useful for just tracking down battery hogs that are activated at 2am in the morning
Hope that helps! Good luck! :fingers-crossed:
AlwaysLucky said:
Well, it's hard to answer simply such a complicated problem. There are so many variables to consider, but I would say rule out a few things first.
First, if you have TWRP installed, backup your current ROM and do a complete factory reset. If the problem persists, then you know it's something built into your ROM causing it and I would suggest swapping out that ROM for another. If the problem is gone, you know it's something you installed or modified in the ROM and you can start to narrow that down.
Second, I would try out the app WakeBlock. It's still in development, but it allows you to see active wakelocks (Android programming object used to keep the CPU running even if dozed) and block them if you want to. But the app may be useful for just tracking down battery hogs that are activated at 2am in the morning
Hope that helps! Good luck! :fingers-crossed:
Click to expand...
Click to collapse
Hi there. Thanks for trying to help!
I don't have TWRP, as I use stock ROM (phone has MobileIron installed for work use, so I can't have it rooted).
I already have wakelock detector installed on the phone, but I don't how many wakelocks during a night should be considered as OK or not...
ghnogueira said:
I don't have TWRP, as I use stock ROM (phone has MobileIron installed for work use, so I can't have it rooted).
Click to expand...
Click to collapse
True, you would need root to flash TWRP to allow backups/restores. However once TWRP is flashed, you could just install a ROM that does not have root and do not root it. That should pass all of MobileIrons checks which are mostly package name-based. In short, root is not required to keep TWRP installed. Something to consider.
ghnogueira said:
I already have wakelock detector installed on the phone, but I don't how many wakelocks during a night should be considered as OK or not...
Click to expand...
Click to collapse
Well, in reality you don't need any wakelocks active. Especially if you are asleep or not going to use the device for a while. Wakelocks can be doing anything from downloading advertisements for apps, to syncing emails with servers. You could block them all in a certain time frame, but that may be overkill. I suggest just going through the list of wakelock package names before you goto bed or when you know drain is at it's heaviest. The package name may be different from the name of the app, but it should give you something to go on. Just uninstall the heavy drainers or disable them enough so they can not drain you so much.
ghnogueira said:
Hi guys!
I desperately need some help from you experts. I have recently noticed my LG G3 has been draining more battery than it should, especially when idle (or at least, theoretically when idle).
Please take a look at the sequence of screenshots (have in mind the analysis was made overnight, when the phone was sitting idle on my bedside):
Screenshot 1: You can see app usage has been the biggest juice thief, and an abnormal drain (24%) for a (supposedly) idle period of 6 hours.
Screenshot 2: Kernel & Android system are the biggest villains, but only sums up to 45%.
Screenshot 3: Taking a deeper look at Kernel, it shows only 7 minutes of CPU usage.
Screenshot 4: A deeper look at Android system also shows a small usage, only a few seconds shy of 6 minutes.
Screenshot 5: On the chart, we can see there was an absurd drain (around 20%) from 1:30 am to 5 am, and then it got stabilized. Wifi was on the whole time, and you can see it shows the phone was (theoretically) dozed 95% of the time.
Sctreenshot 6: Even though the phone was dozed, we can clearly see it has severe CPU usage throughout the whole night, and no pattern could be distinguished between the hours were the battery got the severe drain and the hours after. Even though the CPU frequency was low between 1:30 and 5 (except for a couple of peaks), the utilization averaged 45%.
This is why I need some expert's help. I cannot understand what is draining my battery, what is keeping my phone's CPU util so high... can someone please shed a light on this for me?
Thanks in advance!!! :fingers-crossed: :good:
Click to expand...
Click to collapse
I'm in pretty much the same boat. I lose like 14-20% overnight and I have no clue why. Factory reset and it still seems to be that bad. I also use GSam and have almost exactly the same stats in terms of Android System and Kernel usage, so that means it shouldn't be an app thing (unless you and I have the same apps installed lol). I'm really at a loss as to why there is so much crazy drain.
AlwaysLucky said:
Well, in reality you don't need any wakelocks active. Especially if you are asleep or not going to use the device for a while. Wakelocks can be doing anything from downloading advertisements for apps, to syncing emails with servers. You could block them all in a certain time frame, but that may be overkill. I suggest just going through the list of wakelock package names before you goto bed or when you know drain is at it's heaviest. The package name may be different from the name of the app, but it should give you something to go on. Just uninstall the heavy drainers or disable them enough so they can not drain you so much.
Click to expand...
Click to collapse
I understand I do not need, but I meant how many wouldn't be "harmful". But I'll keep an eye in a night where this thing happens and get back to you.
Thanks for trying to help!
The same problem here. I lose 20% battery per night. Problem is only appearing on stock rom with stock recovery, I have installed Flumics and stock rom zip from TWRP - problem gone, but I need stock rom with stock recovery.
Tested on Lineage OS14.1, PurefusionNougat, CRDroid (not tried in other ROMs, it may work)
After trying a lot of modifications in two weeks regarding battery drain due to android os wakeup all time and little or no deepsleep, found a simple way to solve the issue.
1. Calibrate your battery according to post #9 (https://forum.xda-developers.com/showthread.php?t=2765663)( (Essential- it will fix almost all errors regarding battery)
2. A simple build.prop tweak wifi.supplicant_scan_interval=200
Add this line to system/buildprop using a root explorer with root permission " wifi.supplicant_scan_interval=200 " and reboot.
Screenshots after applying the mode
I edited the build.prop file via BuildProp Editor in the app store. So does i add that line in the beginning of the file or at the end?
do build.prop edits need a reboot to work ?
But yeah... WiFi has always been an issue on the HTC10 -.-
Haldi4803 said:
do build.prop edits need a reboot to work ?
But yeah... WiFi has always been an issue on the HTC10 -.-
Click to expand...
Click to collapse
yes
whi-2 said:
I edited the build.prop file via BuildProp Editor in the app store. So does i add that line in the beginning of the file or at the end?
Click to expand...
Click to collapse
Preferably at the end
Also Do this "Official fix for battery problems"
https://forum.xda-developers.com/showthread.php?t=2765663
whi-2 said:
I edited the build.prop file via BuildProp Editor in the app store. So does i add that line in the beginning of the file or at the end?
Click to expand...
Click to collapse
I'd recommend in this spot in my picture.
Battery Caliberation that also worked for me according to this xda post by @bikercr https://forum.xda-developers.com/showthread.php?t=2765663
Thanks to @bikercr
His Post
"This is directly from HTC tech support. To recalibrate battery and HTC charger when battery rapidly or erratically discharges, this procedure clears all battery stats, coordinates and normalizes charging.
Turn off Fast Boot in settings. Power off phone.
Plug phone into HTC charger and charge for two minutes or more
While charging, hold down volume up+volume down+power button and continue holding
Phone will turn on and off repeatedly every 15 seconds or so while continuing to hold all three buttons
Keep this going for 2 minutes, then release buttons when phone is ON
Now, let phone charge fully normally (with phone either on or off--doesn't matter) and battery level reporting, charging and battery life should be normalized.
Do this every month or so to keep power system healthy--even if everything seems fine. Also, don't leave phone on charger overnight for best long term battery life (according to HTC tech support: "The first thing they tell us." This is true even though charging is supposed to turn off when battery is at 100%)
NOTE: Another potential fix for battery/charging abnormalities if this procedure fails (esp. after an OTA update when corrupted files can remain stuck in device cache partition)--clear cache partition using this method: http://forums.androidcentral.com/ver...ted-phone.html"
New screenshot attached- Still 100% after 59 minutes (Note: without Gapps) Running crdroid from @andybones
Good morning, the fix works with Leedroid Oreo?? or is it for Nougat AOSP ROM?!
Thanks...
Inviato dal mio HTC 10 utilizzando Tapatalk
Martybug said:
Good morning, the fix works with Leedroid Oreo?? or is it for Nougat AOSP ROM?!
Thanks...
Inviato dal mio HTC 10 utilizzando Tapatalk
Click to expand...
Click to collapse
Tested only on Nougat, But it will work on Oreo too, Do the battery calibration first.
So how is your SOT after this fix?
eraycetin said:
So how is your SOT after this fix?
Click to expand...
Click to collapse
This fix increase standby time (battery drain and no or little deepsleep due to android os awake all time)
This fix have little impact on SOT. SOT depends on many factors like Screen brightness, Surfing on 3g, 4g or wifi, playing Games, watching videos etc.
A Little Story
I bought this device through OLX and the seller selling it due to poor battery backup and warmer device even in standby. Due to interest in tweaking and modding from my first android device(Samsung spica 256mb RAM!) i bought it (with Android MM). Found the device doesn't enter in to deepsleep and android os is in the top of battery consuming. Two weeks of flashing differnet roms, Kernels, tweaking kernel through Kernel adiutor app, disabling and removing of apps , build prop edits etc. One day i noticed that my device goes to deepsleep almost suddenly after locking. Flashed the device again and do the tweaks one by one to know which tweak give me the result, and found the wifi scanning interval build prop tweak is the reason.
And it runs smoothly almost all time and some time it shows battery drain. So done some more googling and found this post in HTC One (M8) forum https://forum.xda-developers.com/showthread.php?t=2765663)(. It realy helps to completely overcome the Battery drainage issue. Then i tried almost all nougat roms and all of them are giving excellent battery backup.
Now my device have no deepsleep battery drain issue and now trying some bloat removed nougat stock.
Anyone say the experience Sense Oreo Rom with this tweak ? and how much default interval ?
frostnicko said:
Anyone say the experience Sense Oreo Rom with this tweak ? and how much default interval ?
Click to expand...
Click to collapse
im on lees R143. I did the following 15 mins ago,
turned off phone
did the vol + vol- and power button thing
after that i flashed r143 again and wiped cache.
turned off my phone
now i just wait for full chariging my battery while phone is turned off.
i will test it tomorrow and report back
first reaction of my phone.... a few days ago, it stops showing the % while loading the battery when phone was turned off.
now it shows % of loading... when im on 100% i do the wifi tweak and report
bstiti said:
im on lees R143. I did the following 15 mins ago,
turned off phone
did the vol + vol- and power button thing
after that i flashed r143 again and wiped cache.
turned off my phone
now i just wait for full chariging my battery while phone is turned off.
i will test it tomorrow and report back
first reaction of my phone.... a few days ago, it stops showing the % while loading the battery when phone was turned off.
now it shows % of loading... when im on 100% i do the wifi tweak and report
Click to expand...
Click to collapse
Did you try ?
frostnicko said:
Did you try ?
Click to expand...
Click to collapse
Yes i tried today i take my phone away from charger 6:30am
i made some screens.,. will upload later
first of all, it was defintly better than last 4-6 weeks...
battery juice goes down from 100-0% not like 100 to 98 to 86 to 80 to 52... u know that % jumping around, reboot between 19 and 23% and so on...
but i have had a screen on time of about max 2 hours and my battery was down after 8~9hours... -10%battery per hour in power saver mode with lowest brightness
heere my results :
6:25 100%
74% after 2h30m with screen on 21 min
45% after 6 hours with 52min screen on
12% after 9 hours with 1h16 screen on
3% after 10h15min with 1h18m screen on
after the 10 hours i have had battery usage:
40% Mobile Network Standby
29% Apps
15% System
6% Phone inactive
it was defintly better than before but i have had also the battery draining... btw im on lees r143 with cleanslate kernel....
i install elementalX Kernel with a bit of uc and deactivate some stuff i dont need i will test it tomorrow and report....
maybe we find a solution together....
sorry for bad english:cyclops:
bstiti said:
Yes i tried today i take my phone away from charger 6:30am
i made some screens.,. will upload later
first of all, it was defintly better than last 4-6 weeks...
battery juice goes down from 100-0% not like 100 to 98 to 86 to 80 to 52... u know that % jumping around, reboot between 19 and 23% and so on...
but i have had a screen on time of about max 2 hours and my battery was down after 8~9hours... -10%battery per hour in power saver mode with lowest brightness
heere my results :
6:25 100%
74% after 2h30m with screen on 21 min
45% after 6 hours with 52min screen on
12% after 9 hours with 1h16 screen on
3% after 10h15min with 1h18m screen on
after the 10 hours i have had battery usage:
40% Mobile Network Standby
29% Apps
15% System
6% Phone inactive
it was defintly better than before but i have had also the battery draining... btw im on lees r143 with cleanslate kernel....
i install elementalX Kernel with a bit of uc and deactivate some stuff i dont need i will test it tomorrow and report....
maybe we find a solution together....
sorry for bad english:cyclops:
Click to expand...
Click to collapse
40% Mobile network standby is due to low network coverage and network use more battery to establish a good connection.
pradeeppk said:
Tested on Lineage OS14.1, PurefusionNougat, CRDroid (not tried in other ROMs, it may work)
After trying a lot of modifications in two weeks regarding battery drain due to android os wakeup all time and little or no deepsleep, found a simple way to solve the issue.
1. Calibrate your battery according to post #9 (https://forum.xda-developers.com/showthread.php?t=2765663)( (Essential- it will fix almost all errors regarding battery)
2. A simple build.prop tweak wifi.supplicant_scan_interval=200
Add this line to system/buildprop using a root explorer with root permission " wifi.supplicant_scan_interval=200 " and reboot.
Click to expand...
Click to collapse
on my phone , wifi running is always 100% , I think that is "always scanning option enabled", so this option is draining my battery?
or
which I sacrifice doing your method to my phone?
(Im on LeeDroid R147 Oreo and battery tip is done. )
rudywall said:
on my phone , wifi running is always 100% , I think that is "always scanning option enabled", so this option is draining my battery?
or
which I sacrifice doing your method to my phone?
(Im on LeeDroid R147 Oreo and battery tip is done. )
Click to expand...
Click to collapse
wifi.supplicant_scan_interval=200 if you switch on the wifi always scan mode, then wifi trying to search for available networks all time, if you add these lines to buildprop it pause 200 seconds between scans and it help to reduce battery consumption, drawback - time for find a new wifi hotspot may increase.
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