Hi all,
I've tried to find somewhere a discussion on this topic. What do you think of it?
Here it's my report:
12h4m Deep sleep
54m47s Awake (screen off)
26m11s Screen
Honeslty, I don't know if it is correct or not. Basically, I find this statistic of Awake (screen off) as a Key Performance Indicator (KPI) to analyse whether your system is working correctly or not. I've seen many people going ahead to the partial wakelocks screen. I believe it is better to make an initial diagnosis using this KPI.
My point is that I feel people is too obsessed with wakelocks but the main point is whether your system is working in a normal awake (screen off) ratio.
Summarizing, what is a correct ratio of awake (screen off) time?. In my case it is under 10% of the deep sleep time. Of course, I understand there are other variables like if you check screen very often then deep sleep is achieved less time. Or, as in this case I post, 7h of those 12h, the phone was in plane mode as I was sleeping.
Thanks for participating
BUMP! I like to know aswell since i have 25% awake(Screen off) which i believe is too high but really dont know.
paco_ramirez said:
Hi all,
I've tried to find somewhere a discussion on this topic. What do you think of it?
Here it's my report:
12h4m Deep sleep
54m47s Awake (screen off)
26m11s Screen
Honeslty, I don't know if it is correct or not. Basically, I find this statistic of Awake (screen off) as a Key Performance Indicator (KPI) to analyse whether your system is working correctly or not. I've seen many people going ahead to the partial wakelocks screen. I believe it is better to make an initial diagnosis using this KPI.
Thanks for participating
Click to expand...
Click to collapse
No, what you have displayed is not correct. In a proper dump file (Which is taken while the device is idle), your 'Screen On' time must be less than one minute.
Your 'Screen On' time is 26 m 11 s.
That means you used the device, which throws all other device statistics off, rendering your findings ineffective.
What you have displayed is 'Usage' mixed in with deep sleep. 'Awake' time will vary, but means nothing if your device is in deep sleep the entire time. Airplane Mode simply kills all device radios, it fixes nothing. To gain an accurate picture of what keeps your device from sleeping properly you must:
1. Charge device to 100%
2. In Better Battery Stats, you should have 'Unplugged to Current' as your start point. (For Beginners)
3. Unplug the device.
4. Let the device idle for 6+ hours. Do not touch the device, put it on a table and walk away.
5. When completed, save the log as Dump File (Default setting). The log is saved in the root of your SD card as a *txt* file.
That log will tell you what happens when your device sleeps.
1. 0% /h drain, or lower is acceptable battery drain.
Below is an example what proper deep sleep while idle will resemble.
fossils-n-dents said:
No, what you have displayed is not correct. In a proper dump file (Which is taken while the device is idle), your 'Screen On' time must be less than one minute.
Your 'Screen On' time is 26 m 11 s.
That means you used the device, which throws all other device statistics off, rendering your findings ineffective.
What you have displayed is 'Usage' mixed in with deep sleep. 'Awake' time will vary, but means nothing if your device is in deep sleep the entire time. Airplane Mode simply kills all device radios, it fixes nothing. To gain an accurate picture of what keeps your device from sleeping properly you must:
1. Charge device to 100%
2. In Better Battery Stats, you should have 'Unplugged to Current' as your start point. (For Beginners)
3. Unplug the device.
4. Let the device idle for 6+ hours. Do not touch the device, put it on a table and walk away.
5. When completed, save the log as Dump File (Default setting). The log is saved in the root of your SD card as a *txt* file.
That log will tell you what happens when your device sleeps.
1. 0% /h drain, or lower is acceptable battery drain.
Below is an example what proper deep sleep while idle will resemble.
Click to expand...
Click to collapse
I have done these steps and identified those kernel wakelocks:
bam_dmux_wakelock (*api*): 1 h 34 m 13 s Cntc/wc/ec)5285/0/0 20,4%
[timerfd] (*api*): 49 m 3 s Cntc/wc/ec)20174/0/0 10,6%
What steps are to do to reduce these wakelocks?
Related
Hello world,
I just noticed this disturbing issue. I lost about 16% battery in one night. When I looked at battery state I noticed alot of tiny little wake moments during the night.
What kind of application can cause this? Or are there any known bugged apps that cause this?
Wakker is dutch for Wake
Sent from my GT-N7000 using xda premium
. THE Galaxy Notes when goes into standby (screen off) should go into deep sleep mode is a mode that allows you to keep to a minimum processor frequency to conserve the battery. Unfortunately, between the various firmware updates that we do and the various programs that we install (some of these work in backround without noticing it) can happen that the Note is no longer able to enter deep sleep mode remains fixed at 200mhz even while on table with display off.
To find out if our notes go into deep sleep, just install the free CPU Spy download here: https://play.google.com/store/apps/...wsMSwyLDEsImNvbS5idmFsb3Nlay5jcHVzcHkiXQ..--- If your notes do not enter into deep sleep the greater the percentage occupied by the item above, or 200mhz. The fact that it is a 200mhz is quite useless to us since we're not doing anything with the device as it should be on standby at that time. It happens so that at night, leaving the device on but without the latter is used, however, so battery consumption (having remained fixed at 200mhz) and the following morning surprise that we find the percentage of low power.
To overcome this problem needs to be done in the following way: Deep Sleep Guide
- Go into settings and remove the following tones: sound freezes the screen and sound selection - Set the device in flight mode - Turn off the device - Remove the battery for 10 seconds - Power on the device - Wait until everything is loaded - Remove Airplane mode
And that's it. The Notes should regularly go into deep sleep after doing this guide. To check everything just to keep notes on standby for about ten minutes and see if The candidates and the percentage of deep sleep increases.
Hi
Even I face this battery issue....it is severe in my case. I hardly get 14 HRS of battery life even after about 30 charging cycles
I've installed CPU spy, I found that the CPU stays in 200Mhz, for testing purpose I had kept my cell phone untouched in flight mode for about 12hrs but still I lost more 50% of battery.
I had tested the battery by completely charging it, it just drains before my eyes . . .
I don't know if this is deep sleep issue. please help me.
Naveen
Sent from my GT-N7000 using XDA
1. Flash and test different kernels in case of battery drain. Some are easier on your battery than the others. 2. Use Titanium Backup to freeze or uninstall crapware. This list is a useful guide as to what can/can't be removed from your system: https://spreadsheets.google.com/spr...SENVeXlqUm5vV0E&single=true&gid=0&output=html 3. Set Brightness to low value, disable autobrightness 4. Disable or scale down vibration and haptic feedback 5. Automatic syncing of your accounts is battery consuming. Sync manually if you can 6. Set screen timeout to 15 seconds 7. Disable fast dormancy (dial *#9900# and do it from there) 8. Don't keep your WiFi/Packet Data on all the time. However, if you must have WiFi on the second you wake up your phone, go to Settings/Wireless and Network/Wi-Fi settings - once in Wi-Fi Settings, hit the menu button (the bottom left one), choose Advanced/Wi-Fi sleep policy/When Screen Turned Off. This way your connection will toggle on/off depending on your screen on/of state 9. Disable location services via wireless networks - are you travelling that fast that you need those? 10. GPS is heavy on the battery, therefore use it sparingly
And don't use Juice or any other battery 'defenders': they keep running in the background and consume your juice by trying to save it. Not to mention other problems they can (and often do) create.
Hope this helps.
Download BetterBatteryStats and look for wakelocks (partial and kernel). Google them if you don't know what they do. Then uninstall them or fix them somehow.
Del
Sent from my GT-N7000 using Tapatalk 2
Am happy to say that the deep sleep issue haS been resolved.
I downloaded better battery stats, found that the process l2_hsic was stopping my phone from going to deep sleep mode. I tweaked the wifi settings and the battery life increased exponentially.
Thanks better battery stats
Naveen
Sent from my GT-N7000 using XDA
naveeent said:
Am happy to say that the deep sleep issue haS been resolved.
I downloaded better battery stats, found that the process l2_hsic was stopping my phone from going to deep sleep mode. I tweaked the wifi settings and the battery life increased exponentially.
Thanks better battery stats
Naveen
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
What do you mean "tweaked the wifi settings"?
devid801 said:
. THE Galaxy Notes when goes into standby (screen off) should go into deep sleep mode is a mode that allows you to keep to a minimum processor frequency to conserve the battery. Unfortunately, between the various firmware updates that we do and the various programs that we install (some of these work in backround without noticing it) can happen that the Note is no longer able to enter deep sleep mode remains fixed at 200mhz even while on table with display off.
To find out if our notes go into deep sleep, just install the free CPU Spy download here: https://play.google.com/store/apps/...wsMSwyLDEsImNvbS5idmFsb3Nlay5jcHVzcHkiXQ..--- If your notes do not enter into deep sleep the greater the percentage occupied by the item above, or 200mhz. The fact that it is a 200mhz is quite useless to us since we're not doing anything with the device as it should be on standby at that time. It happens so that at night, leaving the device on but without the latter is used, however, so battery consumption (having remained fixed at 200mhz) and the following morning surprise that we find the percentage of low power.
To overcome this problem needs to be done in the following way: Deep Sleep Guide
- Go into settings and remove the following tones: sound freezes the screen and sound selection - Set the device in flight mode - Turn off the device - Remove the battery for 10 seconds - Power on the device - Wait until everything is loaded - Remove Airplane mode
And that's it. The Notes should regularly go into deep sleep after doing this guide. To check everything just to keep notes on standby for about ten minutes and see if The candidates and the percentage of deep sleep increases.
Click to expand...
Click to collapse
My galaxy note 2 battery is draining fast and the "android os" is at about 65% at end of day and now my battery last about 10 hours. I was trying to follow your instructions above but got lost trying to find the settings to remove some tones you mentioned. Which tones are you speaking of.
Thanks...
houstonjudge said:
My galaxy note 2 battery is draining fast and the "android os" is at about 65% at end of day and now my battery last about 10 hours. I was trying to follow your instructions above but got lost trying to find the settings to remove some tones you mentioned. Which tones are you speaking of.
Thanks...
Click to expand...
Click to collapse
Note 2? Wrong forum..However, to answer your question, he is talking about the tones under Settings> Sound> System.
Hi!
I just noticed that my phone does not go to deep sleep if I have wlan on. Though I do not have any long wakelocks according to BetterBatteryStats, just some minutes total while the device have been awake for much more.
Stock .534 unrooted, newly repaired with _only_ BetterBatteryStats and CPU Spy installed. No accounts added etc.
Wlan/Advanced: "Always on"
Location-based wlan: "on"
Low battery mode: "on"
STAMIN mode: "off"
Location based services "on" / "off" tested.
When I have wlan on CPU Spy reports as Deep sleep unused, and instead most of the time is spent in 300 MHz.
Any of you that can reproduce?
Have the same problem. Is that normal that it doesnt goes to deep sleep ?
muslim187 said:
Have the same problem. Is that normal that it doesnt goes to deep sleep ?
Click to expand...
Click to collapse
No, it's absolutely not normal. Something is keeping the device awake, probably a bug.
I left the device over night,
wlan kernel wakelock for 7h, but no long-standing partial wakelocks. I don't get it, how can something keep wifi awake without actually issuing a wakelock?
Bah I have suddenly been afflicted with this issue since yesterday. Noticed battery drain from 100% to 33% with minimal use between this morning and lunchtime while at work. Currently it is charging off my laptop but only holding its own, not increasing. Only had it a week, very little installed on it.
Battery life was fine for the first week of ownership, today it lost 75% with little or no use in 5 hours, then it did not charge when connected by USB to laptop it merely held the same charge, before quickly discharging again when disconnected.
No deep sleep all day
https://www.dropbox.com/s/b19ixx16dgnqrcb/2013-10-07 17.46.20.png
Inquitus said:
Battery life was fine for the first week of ownership, today it lost 75% with little or no use in 5 hours, then it did not charge when connected by USB to laptop it merely held the same charge, before quickly discharging again when disconnected.
No deep sleep all day
https://www.dropbox.com/s/b19ixx16dgnqrcb/2013-10-07 17.46.20.png
Click to expand...
Click to collapse
Hi, can you please verify that you indeed do not have any wakelocks caused by any other third-party programs you have installed? Just to knwo that we are in fact experiencing the same issue. You could also try to disable wlan (and mobile data (I haven't tested to turn that on, as I do not yet have a data plan).
The application needed to test that is Better Battery Stats, available here on XDA (or on Play): http://forum.xda-developers.com/showthread.php?t=1179809
Exry said:
Hi, can you please verify that you indeed do not have any wakelocks caused by any other third-party programs you have installed? Just to knwo that we are in fact experiencing the same issue. You could also try to disable wlan (and mobile data (I haven't tested to turn that on, as I do not yet have a data plan).
The application needed to test that is Better Battery Stats, available here on XDA (or on Play): http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Today's issue on my phone was driven by several hours of a "bam_dmux wakelock."
edit: and no partial wakelocks so no idea of the driver.
Inquitus said:
Today's issue on my phone was driven by several hours of a "bam_dmux wakelock."
edit: and no partial wakelocks so no idea of the driver.
Click to expand...
Click to collapse
Ok. So it might be the same issue then, though I don't really know what the "bam_dmux" wakelock is.
FYI Mine is back to normal today. Lost 3% in 3 hours of light use. Only thing I have changed is I deleted a Wifi network from my preferred list that the phone was having trouble connecting to, may or may not be related.
I'm opening this thread to clean up the Dev thread, since the most probable cause of battery drains are software/configuration related.
Here's my own experience with this matter.
Most of the drains I've seen are related to Location settings and Google Now. It seems Google's Location Reporting and Location History keep pinging WiFi for the location at a fairly high rate, so keeping the phone Awake and/or the WiFi running all the time. An usual indication of this is that in BetterBatteryStats you get:
1) Screen On % very low
2) WiFi On 100% of the time
3) WiFi Running 100% of the time.
4) Awake with moderate-to-high %.
To test it, here's what should be done:
1) Get BetterBatteryStats (BBS), enable Root, install it as system app (in advanced settings). Reboot.
2) Disable WiFi and GPS completely, preferably leaving Data Network also off. You may go all the way and just turn on airplane mode.
3) Leave the phone idle for at least 1h and check that there is no battery drain.
If you get any considerable drain (more than 5%/h), check Kernel Wakelocks and Partial wakelocks, or try again with 2G networks only. You may have a baseband problem. Consider this step as your "control group" as it ensures nothing in the hardware or in the ROM is wrong.
If there is no drain, enable WiFi and GPS again, but make sure all this settings are UNCHECKED:
1) Settings->WiFi-> Advanced: "Network notification", "Keep wifi on during sleep" set to "Never", "Scanning always available".
2) Settings->Location->Google Location Reporting: "Location Reporting" set to off and "Location History" set to off. Or just disable Location completely.
3) Check Settings->Security -> Device Administrators -> Disable at least Android Device Manager. If you can, disable everything else in this screen, such as Airdroid, Cerberus, etc
4) App drawer -> Google Settings -> Search -> Set Google Now to Off. You can also configure Android Device Manager here.
Leave the phone idle again for 1h and check BBS. In theory you shouldn't need to recharge completely, just enable the watchdog in BBS. Always check the wakelocks too.
You should get this on BBS:
1) Screen On % very low
2) WiFi On 100% of the time
3) WiFi Running with low % (anything less than 50% is ok, depending on Sync settings and background apps)
4) Awake with low %.
5) Deep Sleep with almost 100%
Go back enabling stuff as needed, one by one, leave the phone idle and check BBS. Rinse and repeat until you find the culprit.
One thing, make sure you do this after letting the phone sync some of the stuff. Don't do this immediately after a setting up a Google account.
Some people also reported that doing a factory reset solves the drains. It's always recommended anyway.
Any other hints are also appreciated.
For people with trouble making BBS work, Try getting the latest version, enable Root in Settings->Advanced and them System App, also in Settings-> Advanced.
Also:
1) When the phone is charging it WILL BE AWAKE WITH BOTH CORES, ALL THE TIME. Depending on the governor used, both cores may even stay at full speed (aka 1GHz). This is BY DESIGN and stock ROMs does that too. So any measurement while the phone is charging is useless.
2) Most "calibration" procedures are myths and don't have any effect. Erasing batterystats.bin also does nothing to increse battery life or remove drains (but may solve some charging issues, still unclear).
Very interesting.. Good thread and good options to test our battery drain ! thanks for the post.
I'll try this when I get home from school, thanks.
Weird thing happened last night, I thought the battery drain was gone when I recalibrated, but my phone discharged over night, weird thing is my settings show the phone didn't go to sleep once during the entire night, even though it was on airplane mode and I had already used it for like 3 or 4 hours with no apparent brain
There is a lot of battery drain only when WiFi in on. Even if the phone is idle.
I'm on:
Maclaw CM 11.0 [20131210]
I8190XXAMJ2
I'll do the exact tests and post my results.
Do you get notifications with wifi set to never during sleep?
RodHQ said:
I'll try this when I get home from school, thanks.
Weird thing happened last night, I thought the battery drain was gone when I recalibrated, but my phone discharged over night, weird thing is my settings show the phone didn't go to sleep once during the entire night, even though it was on airplane mode and I had already used it for like 3 or 4 hours with no apparent brain
Click to expand...
Click to collapse
Use the 1st step I wrote above with BBS. Check Kernel Wakelocks and Partial Wakelocks. You will be able to pinpoint exaclty what is keeping your phone awake.
I was about to start a thread on the same topic but my problem is with Carbon Rom 4.4.2 . The phone never goes into deep sleep and is awake 100% of the time. I'm attaching what I see as the culprit in B.B.S. I already disabled sync and yet the wakeclocks are sync related I hope anyone can help me with this.
i just changed to peagusq everything is fine
BBS How-to
ArtCar said:
I was about to start a thread on the same topic but my problem is with Carbon Rom 4.4.2 . The phone never goes into deep sleep and is awake 100% of the time. I'm attaching what I see as the culprit in B.B.S. I already disabled sync and yet the wakeclocks are sync related I hope anyone can help me with this.
Click to expand...
Click to collapse
Maybe BBS How-to will help you
http://forum.xda-developers.com/showpost.php?p=15869904&postcount=3
If not than post screens and collected dumps on BBS thread
gimme link to maclaw 4.4.2 for s advance
Sent from my GT-I9070 using xda app-developers app
Link
Here you are
http://maclaw.pl/downloads/
same here
eswarvf said:
i just changed to peagusq everything is fine
Click to expand...
Click to collapse
+1
ArtCar said:
I was about to start a thread on the same topic but my problem is with Carbon Rom 4.4.2 . The phone never goes into deep sleep and is awake 100% of the time. I'm attaching what I see as the culprit in B.B.S. I already disabled sync and yet the wakeclocks are sync related I hope anyone can help me with this.
Click to expand...
Click to collapse
Notice that the Count is 0 on both GoogleServices related wakelocks. To me this seems that Chrome and something else (maybe G+?) are trying to sync (perhaps the first one?) but are not getting enough network time/bandwidth to do so. I suggest you connect to an wifi, turn on the sync, and leave the phone awake for a while (try not to use the network very much). See if that solves. If not, backup and factory reset are your friends.
rcoacci said:
Notice that the Count is 0 on both GoogleServices related wakelocks. To me this seems that Chrome and something else (maybe G+?) are trying to sync (perhaps the first one?) but are not getting enough network time/bandwidth to do so. I suggest you connect to an wifi, turn on the sync, and leave the phone awake for a while (try not to use the network very much). See if that solves. If not, backup and factory reset are your friends.
Click to expand...
Click to collapse
I fixed my problem by switching back to dalvik and now my phone only looses about 5% battery overnight.
I have a Moto G 2014 (XT1064) running Android 6.0 that will not go into deep sleep. I could see that the CPU was never going into the deep sleep state even when the phone was not being used and no user apps were actively running in the background. This is causing abysmal battery life as expected. The phone was updated to Android 6.0 via regular OTA updates. I haven't flashed any third party ROMs onto it at all since I bought it.
The first thing I did to investigate was to unlock the bootloader (it was still locked since purchase prior to this) so that I could obtain root access to see what was going on. This also had the additional affect of wiping the phone to stock Andoird 6.0, which I had hoped would maybe solve the problem but it did not.
My first thought was that it was a user app that was holding a wakelock keeping the phone awake. I looked at the user and kernel wakelock counts via BetterBatteryStats and WakeLockDetector, but from what I can tell it is not any user app that is holding a wakelock at all. Instead it must be some kernel level app keeping the CPU awake, but I can't determine what it is. There isn't any single entry in the wakelock list that sticks out as the culprit.
I have done some other investigative tests such as turning WiFi off while the phone sits unused overnight. This did not have any effect as the phone still remained awake the whole time. I also repeated this test with the phone in airplane mode (WiFi + cellular radios off) and again it had no affect. From this I could only conclude that it was not the wireless radios that were keeping the phone awake. The wakelock counts also didn't show any evidence that WiFi, cellular or GPS were holding wakelocks.
Here are two screenshots I took of the BetterBatteryStats and WakeLockDetector apps showing the highest count kernel wakelocks over a roughly 17 hour period:
(I'd link them in properly but I am prevented from posting outside links on this forum until I have 10 cumulative posts...)
i.imgur.com/nPAY3S6.png
i.imgur.com/5VfgFv1.png
You can see that the phone has been awake 96% of the time during this period, and that the highest count kernel wakelocks are from "event8-1877", "event9-1877", "qpnp_soc_wake" and "qpnp-vadc-e4a28400". I could not find any information as to what these entries mean or what they're related to. Whatever they are, they appear to have abnormally large wakelock counts which leads me to believe that they are related to this problem. The other thing that puzzles me is that the total time for the top four entries in that list only sum to about 2 hours, yet the phone has been awake for almost 17 hours within the same period.
If anyone has any idea about this I'd appreciate the help. I may be completely wrong about the root cause here but I'm running out of ways to debug this.
Updating this thread to say that I have also tried re-flashing stock Android 6.0 using the firmware files linked from this thread (in my case I used XT1064_TITAN_RETCA_6.0_MPB24.65-34_cid14_CFC.xml since I am in Canada). I still experienced the same behaviour where the phone would rarely enter deep sleep. It seemed to be marginally better after re-flashing, going into deep sleep about 10% of the time over a 12 hour period or so, where as before it was only going into deep sleep about 4% of the time during the same period. This still doesn't solve the problem though.
Now I am thinking about downgrading to stock Android 5.0.2 and see if that fixes the problem since I don't know how else to diagnose this.
Hello there . Using Better Battery Stats I found out about this process which takes my phone out of Deep Sleep for about 5 minutes every hour. Totally annoying.
My phone is seriously trimmed down. I'm very strict when it comes to what is running. Data connection is almost permanently disabled, no weather widgets anywhere (that I'm aware of), no sensors active, extremely few processes in background, and even those that are have been thoroughly vetted. I'm using Disable Service / Greenify & Autostart to seriously trim down on whatever is running.
I did notice that when the phone is in Airplane mode, ssp_sensor_hub_wake_lock is keeping my phone alive "only" about 1 minute / hour. That is still too much, since I do NOT have any sensors that should be active at that time.
CONCLUSION AND THE ACTUAL QUESTION:
How can I investigate WHAT PROCESS starts ssp_sensor_hub_wake_lock OR ALTERNATIVELY get any logs / debug that could lead me to the culprit.
Thank you in advance!
try better battery stats