Related
This topic has been up a couple of times before, perhaps most interestingly discussed in this thread.
It appears the problem still exists (asusdec_wake kernel wake), and I'm experiencing extreme battery drain during sleep with the dock attached. Currently running Cromi-X 5.4, and I have tried hunds 3.4.4, and _that 8 and 9 kernels.
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up. It only occurs when the tablet is docked, it can occur at both high charge levels and when the dock is empty (mine always drains to 0%). It does not seem to matter whether wifi is on or off. I monitor the battery with better battery stats.
It's a real pity, since I have to turn the tablet off whenever I want to keep the dock attached.
Is anyone else experiencing this drain? Any suggestions for fixes?
Also: obligatory first post thanks-for-making-my-tablet-great to @sbdags, @_that and all the other contributors to Cromi :good:
rkha said:
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up.
Click to expand...
Click to collapse
How do you know that it first enters deep sleep and that it's woken up later?
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
_that said:
How do you know that it first enters deep sleep and that it's woken up later?
Click to expand...
Click to collapse
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
_that said:
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
Click to expand...
Click to collapse
Good point. Any tips on how this can be diagnosed?
rkha said:
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
Good point. Any tips on how this can be diagnosed?
Click to expand...
Click to collapse
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
sbdags said:
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
Click to expand...
Click to collapse
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
rkha said:
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
Click to expand...
Click to collapse
It's Google now constantly polling for your location as far as I can tell.
Hello guys, I had some battery trouble with my Nexus 5, and during my investigations I saw something strange.
I used CurrentWidget app to track my
current drain, during wake and during sleep. Settings: Update Interval = 10 sec, Log Values to file = true, Force Log in sleep mode = true.
When I viewed the log as graph I saw that during sleep the current drain never decreases to something close to 0 mA, it stays around 100 mA,
or goes down to 30-40 mA, but absolutely never less than this, as you can see in the attached screenshots.
I tested and confirmed this behavior with 4.4.4 and 5.0.1, both flashed clean with factory images, without any other apps installed besides Google apps. During the tests I kept the phone with normal usage: WiFi on, 2G network, Bluetooth on, Location Battery saving, Auto-sync on, and just some net browsing. But of course the most important information was collected during sleep with screen off. Surprisingly, by putting the phone in Airplane mode the current drain in sleep remained exactly the same, between 30-100 mA.
I also tested this on a Nexus 4 with 5.0.1 and during sleep it consumes around 2-4 mA, so there is a big difference.
Can any of you also install the CurrentWidget app, configure the logging, wait a few hours than make a screenshot of your current drain graph ?
I want to see if it's something abnormal with my phone of if it's a general thing. It would be very grateful. Thank you.
Is the widget keeping the phone out of deep sleep? A la wakelock... Just a theory.
what are your wakelocks ?
try gsam battery monitor,
i thought currentwidget drains the battery,i only used that program to check charging current and display idle, but never kept it when display was off.
or try betterbatterystats
http://forum.xda-developers.com/showthread.php?t=1179809
republicano said:
what are your wakelocks ?
try gsam battery monitor,
i thought currentwidget drains the battery,i only used that program to check charging current and display idle, but never kept it when display was off.
or try betterbatterystats
http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
I'm not interested in wakelocks, just current drain.
And no, I don't think it's keeping the phone from entering deep sleep, it just wakes up from time to time to log the current.
Anyway, the same app with the same settings on my Nexus 4 records 2 mA in sleep mode, so it's definitely in deep sleep.
So , please can you do this experiment on your phone and share the results ? Thank you so much.
I very rarely got below 27mA. Though I've no idea of it was in deep sleep at that time.
rootSU said:
I very rarely got below 27mA. Though I've no idea of it was in deep sleep at that time.
Click to expand...
Click to collapse
An even better app that can log the current drain of the phone is Battery Monitor Widget. I configured the recording interval to 10 seconds for testing and played with the Graphics window.
The first picture is from a friend's Nexus 5 (stock 5.0.1) and the second one is mine (stock 4.4.4, but same tested on 5.0.1),
As you can see the current drain even in sleep never decreases below 30 mA and the mean is around 100 mA.
This is very bad, because even the Nexus 4 with 5.0.1 has a 3 mA drain in sleep,
so why is the Nexus 5 drain from 10 to 30 times more ?
Can someone shed any light on this ?
At 100mA drain, your phone would hypothetically last 23 hours. 100mA * 23 hours = 2300mAh. I doubt that. It surely must last longer than that, if it is indeed in deep sleep and not kept awake by some application.
My hypothesis is that what you're seeing is a calibration error. The current measurement is more than likely inferred by accounting for other factors. (I doubt the current is measured directly - ie. as an ammeter). Therefore, I would suggest taking it with a grain of salt.
That being said, with all things being equal, if someone were to do the test, they would probably get similar results to you.
JayR_L said:
At 100mA drain, your phone would hypothetically last 23 hours. 100mA * 23 hours = 2300mAh. I doubt that. It surely must last longer than that, if it is indeed in deep sleep and not kept awake by some application.
My hypothesis is that what you're seeing is a calibration error. The current measurement is more than likely inferred by accounting for other factors. (I doubt the current is measured directly - ie. as an ammeter). Therefore, I would suggest taking it with a grain of salt.
That being said, with all things being equal, if someone were to do the test, they would probably get similar results to you.
Click to expand...
Click to collapse
Can you please do the test on yours?
My results are comparable to yours, andreipaval. The current sensor was more than likely designed for limiting charging current and not for measuring sleep current. Plus, more importantly, the phone definitely has to be pulled out of deep sleep to even make a measurement. The sensor being off by less than a hundred milliamps makes little difference when one can charge at much higher rates but it will falsely report the idle drain.
Perhaps it was your Nexus 4 that was off by -100mA and falsely reported 3-4mA. It can safely assumed that the internal leakage of the battery itself is probably more significant than 3-5mA... Thus, as I previously suggested - you might want to consider taking this with a grain of salt. If you want to do a more conclusive test, see how long your phone lasts from 100% to 0% in deep sleep and airplane mode. You can get a pretty good estimate of the drainage that way. (Batt capacity divided by number of hours)
JayR_L said:
My results are comparable to yours, andreipaval. The current sensor was more than likely designed for limiting charging current and not for measuring sleep current. Plus, more importantly, the phone definitely has to be pulled out of deep sleep to even make a measurement. The sensor being off by less than a hundred milliamps makes little difference when one can charge at much higher rates but it will falsely report the idle drain.
Perhaps it was your Nexus 4 that was off by -100mA and falsely reported 3-4mA. It can safely assumed that the internal leakage of the battery itself is probably more significant than 3-5mA... Thus, as I previously suggested - you might want to consider taking this with a grain of salt. If you want to do a more conclusive test, see how long your phone lasts from 100% to 0% in deep sleep and airplane mode. You can get a pretty good estimate of the drainage that way. (Batt capacity divided by number of hours)
Click to expand...
Click to collapse
I have looked into this myself recently using software readings from Current Widget and agree with your findings. Basically once the phone enters true deep sleep the measurement intervals increase until it's the only process waking the phone and measuring higher rates than would be found without the software waking the device.
andreipaval said:
Can any of you also install the CurrentWidget app, configure the logging, wait a few hours than make a screenshot of your current drain graph ?
I want to see if it's something abnormal with my phone of if it's a general thing. It would be very grateful. Thank you.
Click to expand...
Click to collapse
I have made a log of power level readings with Current Widget in various forms of usage. The update interval was set to 5 seconds but you can see at the beginning when the phone was mostly idle the update interval becomes delayed and sees above average idle measurements. Compare this to after when I began to listen to music on the phone with the screen mostly off. Here we can see lower numbers while the phone is actively playing music, less so than before when the phone was said to be in deep sleep. There are periods of idle followed by various periods of screen usage following that, more details can be found in the album included below.
There's also the case of background software drains. Things like Google Now and Auto Syncs kicking in, and whatever other apps and services may be installed. These results were with Google Now off, Locations off, Hotword off, Auto syncs on, and Adaptive Brightness on set to 40%.
I took screen shots of my usage having ended the voltage measurements at the 45% mark of this charge.
http://imgur.com/a/5VsRI 45% remaining
http://imgur.com/a/vQpoz 5% remaining
bblzd said:
I have looked into this myself recently using software readings from Current Widget and agree with your findings. Basically once the phone enters true deep sleep the measurement intervals increase until it's the only process waking the phone and measuring higher rates than would be found without the software waking the device.
I have made a log of power level readings with Current Widget in various forms of usage. The update interval was set to 5 seconds but you can see at the beginning when the phone was mostly idle the update interval becomes delayed and sees above average idle measurements. Compare this to after when I began to listen to music on the phone with the screen mostly off. Here we can see lower numbers while the phone is actively playing music, less so than before when the phone was said to be in deep sleep. There are periods of idle followed by various periods of screen usage following that, more details can be found in the album included below.
There's also the case of background software drains. Things like Google Now and Auto Syncs kicking in, and whatever other apps and services may be installed. These results were with Google Now off, Locations off, Hotword off, Auto syncs on, and Adaptive Brightness on set to 40%.
I took screen shots of my usage having ended the voltage measurements at the 45% mark of this charge.
http://imgur.com/a/5VsRI 45% remaining
http://imgur.com/a/vQpoz 5% remaining
Click to expand...
Click to collapse
You got almost 6 hours of SOT from a single charge? How did you do that?
It seems impossible to me...
Well, I get anywhere between 5 to 6 hours of SOT if I use the phone heavily (continually). If I'm working and just using the phone regularly, I get between 3-4 hours of SOT. I assume it's the moving around, changing cell towers, turning WiFi on and off and things like that. Also, web browsers are notorious for ramping up CPU frequencies, and hence power drain. I can get 5-6 hours using Tapatalk but not playing games and browsing the web.
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
bblzd said:
I have looked into this myself recently using software readings from Current Widget and agree with your findings. Basically once the phone enters true deep sleep the measurement intervals increase until it's the only process waking the phone and measuring higher rates than would be found without the software waking the device.
I have made a log of power level readings with Current Widget in various forms of usage. The update interval was set to 5 seconds but you can see at the beginning when the phone was mostly idle the update interval becomes delayed and sees above average idle measurements. Compare this to after when I began to listen to music on the phone with the screen mostly off. Here we can see lower numbers while the phone is actively playing music, less so than before when the phone was said to be in deep sleep. There are periods of idle followed by various periods of screen usage following that, more details can be found in the album included below.
There's also the case of background software drains. Things like Google Now and Auto Syncs kicking in, and whatever other apps and services may be installed. These results were with Google Now off, Locations off, Hotword off, Auto syncs on, and Adaptive Brightness on set to 40%.
I took screen shots of my usage having ended the voltage measurements at the 45% mark of this charge.
http://imgur.com/a/5VsRI 45% remaining
http://imgur.com/a/vQpoz 5% remaining
Click to expand...
Click to collapse
Thank you @bblzd for following up with the research and confirming my hypothesis.
andreipaval said:
You got almost 6 hours of SOT from a single charge? How did you do that?
It seems impossible to me...
Click to expand...
Click to collapse
Battery life is determined mostly by usage, settings and signal. So the apps I used, with the settings mentioned, on a strong WiFi signal.
There are ways I could increase battery life further such as lower brightness, disable auto syncs (or have them set on an automated schedule like I was forced to do on Kit Kat) or even disable Dashclock despite its minimal attributed drain. There are also always random factors such as incoming calls, texts, app updates, etc.
Generally the Nexus 5 is great on battery using WiFi, but only average when using data connection or making voice calls. This can be seen in Anandtech's review back from Dec. 2013.
http://anandtech.com/show/7517/google-nexus-5-review/3
hi
i have a new (3 months old) unrooted nexus 5 update to latest OS version which is showing some very odd stats wrt battery consumption.
first i had heavy battery drain but then i disabled the scanning options in the location menu which helped. but still even with brightness at only 18%, battery saver on 95% of the time, location & mobile data off all the time & wifi only used for short bursts it still seems to drain quite quickly.
app usage stats as reported by the inbuilt battery stats option differs quite a bit from other battery management apps (du battery saver, battery doctor, gsam battery monitor)
for eg. inbuilt battery stats doesnt even show wifi consumption in the stats even if i use it for few hours (then suddenly one time it showed up with some excessive consumption stats - 1500mah for 2 hours usage; photos attached). very often it shows gravity screen app as the biggest consumer of battery while other apps show gravity screen as consuming very little power. otoh gsam shows battery doctor as consuming the most of all the apps.
what could be the issue?
gsam shows average battery life with screen on as 3h 42m. is that ok?
was also wondering if the optimization options of the battery management apps work or are they gimmicks? for eg both du battery saver & battery doctor show 'x' number of apps consuming power in background & when you press the optimise/close apps button it shows some cool effects of shutting down those apps but you come back after a few hours & the same apps show up in the running in background.
also, the front camera is very grainy. cant believe its that bad in what was a flagship phone. is it just my phone or is that the how it is for other users?
anyone with any inputs?
You got nearly 5 days on a single charge??? Yes, your battery consumption is fine. Nearly 4 hours of SOT is fantastic.
The graininess of the camera will depend a lot on the lighting. Unless you have a light shining directly on your face, the picture is probably pretty dark. That said, it's "only" like a 3MP camera. It's well known as a sub-standard front camera (I'm not a selfie machine so I don't really care). When you think about how microscopic the light sensor is on the front camera, it's no wonder the picture is grainy.
exninja said:
You got nearly 5 days on a single charge??? Yes, your battery consumption is fine. Nearly 4 hours of SOT is fantastic.
The graininess of the camera will depend a lot on the lighting. Unless you have a light shining directly on your face, the picture is probably pretty dark. That said, it's "only" like a 3MP camera. It's well known as a sub-standard front camera (I'm not a selfie machine so I don't really care). When you think about how microscopic the light sensor is on the front camera, it's no wonder the picture is grainy.
Click to expand...
Click to collapse
thanks for your reply exninja
that 5 days was a one time thing where i barely touched the phone & then only to test it. i wish it were that good LOL. normally i get about 2 days with very conservative usage (brightness at only 18%, battery saver on 95% of the time, location & mobile data off all the time & wifi only used for short bursts, 0 talktime)
is 4 hrs SOT that good? i see a lot of people getting 5 to 6 hours + & that too without those conservative usage patterns.
the thing that got me worried is the strange battery usage stats reported in the stock settings.
Honestly I wouldn't worry that much about what each app says is using energy. They're each consuming very little anyways. I'm not familiar with gravity screen so I wouldn't know about it.
I haven't heard of many people getting 5-6 hours of sot, especially since lollipop. I got 4 hours on KitKat, then dropped to 3 or less on lollipop. Now it's usually around 2 hours.
@fguy76
First of all, just to let you know, recently Google Play Services have been acting up. Sometimes I get normal battery drain overnight when I sleep, and sometimes it drains like crazy. For now, there is nothing we can do about Google Play Services.
However, if u noticed that WiFi has been turned on the whole time via the battery history chart, despite the fact that you did not even turn on WiFi at all during that period, then this can only mean one thing. You must have enabled WiFi Scanning (the famous Scanning always available bug in Lollipop & KitKat).
To disable WiFi Scanning, go to Settings first. Then on the top of settings, there is a search bar. Type in "Scanning".
Then u will see the following options. Make sure u disable WiFi Scanning.
Having said this, there is another annoying bug. This bug is when you have left a WiFi hotspot and forgotten to turn of WiFi. So after awhile u realised it and u proceed to turn off WiFi. But hours later, u check your battery stat, and it still shows your WiFi have been active the whole time despite turning it off. For this, the only workaround is to reboot the phone. To avoid this bug, always turn off WiFi b4 u leave the WiFi hotspot area.
@pcphobic i have wifi scanning off & i always remember to turn wifi off when not using it so that second scenario is not an issue with me
fguy76 said:
@pcphobic i have wifi scanning off & i always remember to turn wifi off when not using it so that second scenario is not an issue with me
Click to expand...
Click to collapse
@fguy76
The other solution that I can offer is under Location settings, go to Google Location History and make sure it is turned off.
You can still use GPS based apps with Google Location History turned off.
I suspect that if u find intermittent wifi showing up in your battery history, it could only mean that Google Location History is periodically waking up and using wifi to get an approximate location. I used to get this until I turned off Google Location History.
I have a serious problem with stand-by time of my galaxy s7.
I have updated my device to Nougat and i am using ForceDoze to put the phone to sleep (without root, with adb command), although i am not sure if it is really working.
I lose about 3-4% battery every hour when idle.
With idle i mean always on display on, wifi or data on, gps and bluetooth off, power saving off.
When i check better battery stats and accubattery, it shows the phone in deep sleep most of the time.
I think this amount is ridiculous. It shouldn't consume more than 2% with this setup, assuming AOD consumes 1% per hour.
I don't have a problem with screen-on time. Only with stand-by time.
Do you have any suggestions for me? What could be the problem?
Find out what is running on your phone by going to running services. Disable the apps you dont need running, turn off always on display and see your battery times then. Clearly something is running in the background and this is up to you to find out what is running....
Second option root your phone, uninstall the bloat and install greenify.
omeren83 said:
I have a serious problem with stand-by time of my galaxy s7.
I have updated my device to Nougat and i am using ForceDoze to put the phone to sleep (without root, with adb command), although i am not sure if it is really working.
I lose about 3-4% battery every hour when idle.
With idle i mean always on display on, wifi or data on, gps and bluetooth off, power saving off.
When i check better battery stats and accubattery, it shows the phone in deep sleep most of the time.
I think this amount is ridiculous. It shouldn't consume more than 2% with this setup, assuming AOD consumes 1% per hour.
I don't have a problem with screen-on time. Only with stand-by time.
Do you have any suggestions for me? What could be the problem?
Click to expand...
Click to collapse
Hi mate
Most of times is configuration issues or a rouge app , install a an like BBS let it run for a few hours and check the log to see who is keeping the phone awake.
review your settings wifi , location email, FB ........
I think i found what the problem is. It is always-on display. Last night, i turned it off. With only wi-fi on, i lost 1% per hour.
Apparently, AOD consumes way more juice than i thought.
omeren83 said:
I think i found what the problem is. It is always-on display. Last night, i turned it off. With only wi-fi on, i lost 1% per hour.
Apparently, AOD consumes way more juice than i thought.
Click to expand...
Click to collapse
I found AOD prevented Doze from working, which in turn used way more in idle, so it's not specifically AOD draining it, it's because it's not at it's lowest power state during idle
I just got an LG V20 which is good on battery when in use but sucks when not in use. The culprit is always wifi. I just discovered the root cause is Location services that is using wifi to get locations even when wifi is off.
To stop this, go to settings->location->scanning.
Uncheck wifi scanning. For good measure, uncheck bluetooth scanning.
Go to wifi menu ->advanced-> keep wifi on when screen is off
Change to never or "only when plugged in"
Hi,
thanks for your helpful tips..
So out of the 3 tips you have:
1. Uncheck wifi scanning
2. Uncheck bluetooth scanning
3. Turn wifi off when screen is off
Any idea how much does each option save (if you've quantified)?
I'm happy to follow points 1 and 2. I'd only do 3 if it really helps a lot, because most apps would use data if wifi isn't available to periodically phone home.
I have always been dissappointed with my V20 standby time.. I had all of these settings on.. so i'll see how she does now they are off.
Thanks!
My standby time is from 0-4% over 8-9hrs. I really cant complain.... but the phone is facing down.
I wasn't aware of the wifi location scanning, and the bluetooth scanning. Giving it a try as my standby time has been horrible lately.
I am also facing severe battery drain on my LG V20. Battery easily drains by 5-10% per hour even when the phone is lying idle with screen off. Major culprits are 'Phone Idle', 'Android System' and 'Android OS'.
coolravsun said:
I am also facing severe battery drain on my LG V20. Battery easily drains by 5-10% per hour even when the phone is lying idle with screen off. Major culprits are 'Phone Idle', 'Android System' and 'Android OS'.
Click to expand...
Click to collapse
Try what is mentioned here
Post your screen shots here and tag or quote this post
As a side note, I've found that using wifi and cell data to help location services causes maps to scan these options and slow down (maps keeps saying every 5 to 15 seconds "searching"). By using gps only, the maps app is faster and less battery drain.
Obviously if you are indoors you need the help of wifi or cell data. But in the car or outside it is unnessary.
Thanks for your tips it's very good for my life battery. :good:
One Twelve said:
Try what is mentioned here
Post your screen shots here and tag or quote this post
Click to expand...
Click to collapse
I tried as suggested in the post you shared. Once the Bugreport was generated, I got a notification to click it to share. But, upon clicking nothing happened. I did not get anything (no pop-up, no options) further to share it. I tried thrice but, every time same end result.
How can I access the Bugreports generated on the phone?
coolravsun said:
I tried as suggested in the post you shared. Once the Bugreport was generated, I got a notification to click it to share. But, upon clicking nothing happened. I did not get anything (no pop-up, no options) further to share it. I tried thrice but, every time same end result.
How can I access the Bugreports generated on the phone?
Click to expand...
Click to collapse
Ah, seems like the obvious question but you can't.
I've found the most reliable way is to email them and then download them
One Twelve said:
Ah, seems like the obvious question but you can't.
I've found the most reliable way is to email them and then download them
Click to expand...
Click to collapse
Finally! I was able to share and download the bug report. I am attaching the Historian Graph and Aggregated Stats screenshots here. Please let me know what you find.
coolravsun said:
Finally! I was able to share and download the bug report. I am attaching the Historian Graph and Aggregated Stats screenshots here. Please let me know what you find.
Click to expand...
Click to collapse
- see the cpu running, userspace wakelock & screen on lines. They seem to match. Screen is on, cpu working with userspace wakelock. Close to 7pm the screen is off but the cpu is running, because you were listening to audio. I don't see a problem here. Looks normal
- you screen off discharge rate is 2.56%/h which seems a bit high. If you were streaming audio this might add to it. Do you have the second screen on when the main screen is off ?
- somewhere around 12pm you are using data for about an hour. Mobile Signal strength isn't very good, mostly yellow. What i don't understand is why your wifi is also on ? and this is in an area where wifi signal is bad. Both of these will add to drain. And in two hours your battery dropped from 70 to 40
- little after 1pm you're on wifi for a couple of hours but the signal is weak
- around 5pm you're back on data streaming audio and battery takes a nose dive here. Down 30% in like an hour. Were you moving ?
- then you charge up to 85%, doze kicks in which is good, if there was app drain doze would not come on, for the next 5h without use, you lose about 5%
- the part i don't understand is between 1am & 6am, battery drops 10% yet full doze (blue) is on. So there is some activity going on there. What ? sync ? updates ?
Not sure about the aggregated stats as you've recharged up and run down fr a second cycle so it could be your off screen drain is twice as high because of that
charge up again, go through your day and save log when you're at 5% and lets see the two screenshots from just one charge cycle
One Twelve said:
- see the cpu running, userspace wakelock & screen on lines. They seem to match. Screen is on, cpu working with userspace wakelock. Close to 7pm the screen is off but the cpu is running, because you were listening to audio. I don't see a problem here. Looks normal
- you screen off discharge rate is 2.56%/h which seems a bit high. If you were streaming audio this might add to it. Do you have the second screen on when the main screen is off ?
- somewhere around 12pm you are using data for about an hour. Mobile Signal strength isn't very good, mostly yellow. What i don't understand is why your wifi is also on ? and this is in an area where wifi signal is bad. Both of these will add to drain. And in two hours your battery dropped from 70 to 40
- little after 1pm you're on wifi for a couple of hours but the signal is weak
- around 5pm you're back on data streaming audio and battery takes a nose dive here. Down 30% in like an hour. Were you moving ?
- then you charge up to 85%, doze kicks in which is good, if there was app drain doze would not come on, for the next 5h without use, you lose about 5%
- the part i don't understand is between 1am & 6am, battery drops 10% yet full doze (blue) is on. So there is some activity going on there. What ? sync ? updates ?
Not sure about the aggregated stats as you've recharged up and run down fr a second cycle so it could be your off screen drain is twice as high because of that
charge up again, go through your day and save log when you're at 5% and lets see the two screenshots from just one charge cycle
Click to expand...
Click to collapse
Thanks a lot! Please find my answers in sequence.
- I listen to music while going to work. But, that is, till 8:30 AM only. Yes, I have 2nd screen ON when the Main display is OFF.
- I watch stored videos during lunch (12-1pm) for around an hour but it shouldn't be using data as I am playing stored videos.
- Around 5 pm, I leave for home. Again while going home I listen to music for half an hour.
- I have no Idea of what is happening during Night because I just leave it and don't use it until morning. In fact, I have scheduled the 2nd screen to be off between 11 pm and 6 am
I will try to run a proper cycle as you have suggested and will recapture the logs.
I understand the battery dropping while I am using the phone (listening to music/watching videos/browsing/anything else). What I don't get is the battery dropping insanely when I am not using it. For example, once I reach the office, I stop the music, kill the music player and just keep the phone aside. After 1-2 hours, as I check my phone I find battery dropped by 10% or so! It's the battery drain while my phone is just lying idle that is troubling.
Also, I have noticed that once I charge my phone and then leave it (Not using it) the battery drain is minimal like 1% per hour. But, once I run some app (music/browsing etc) for a little while and then leave the phone, the idle battery drain is pretty high.
coolravsun said:
Thanks a lot! Please find my answers in sequence.
- I listen to music while going to work. But, that is, till 8:30 AM only. Yes, I have 2nd screen ON when the Main display is OFF.
- I watch stored videos during lunch (12-1pm) for around an hour but it shouldn't be using data as I am playing stored videos.
- Around 5 pm, I leave for home. Again while going home I listen to music for half an hour.
- I have no Idea of what is happening during Night because I just leave it and don't use it until morning. In fact, I have scheduled the 2nd screen to be off between 11 pm and 6 am
I will try to run a proper cycle as you have suggested and will recapture the logs.
I understand the battery dropping while I am using the phone (listening to music/watching videos/browsing/anything else). What I don't get is the battery dropping insanely when I am not using it. For example, once I reach the office, I stop the music, kill the music player and just keep the phone aside. After 1-2 hours, as I check my phone I find battery dropped by 10% or so! It's the battery drain while my phone is just lying idle that is troubling.
Also, I have noticed that once I charge my phone and then leave it (Not using it) the battery drain is minimal like 1% per hour. But, once I run some app (music/browsing etc) for a little while and then leave the phone, the idle battery drain is pretty high.
Click to expand...
Click to collapse
Same sequence
- When you have the second screen on, is the phone facing up or down. What i notice with that second screen is it ignores any brightness settings. If the phone is face up and pointed at a light, the second screen becomes very bright. If its facing away from the light then it dims. Depending on how your phone faces you will either have more or less drain here, without doing anything and phone just sitting there. Typical overhead with second screen on and normal brightness ie not too bright is around 1% per hour. This could be adding to your off screen drain. Why not try a couple of cycles. One with second screen off and another with second screen on. Just to see how your off screen drain rate is like.
You say you listen to music only upto 8:30AM, take a look at the audio line. Can you see audio triggering ? there's little blips there after 8:30AM which continues till 5:30PM where its solid. This is your ride back where you listen for an hour. The 5:30 audio is ok but the blips in between are not leaving aside lunch video. Each time there is an audio blip there is a wakelock. Pay attention to the duration of the audio blip, if its a few seconds it could just be notification, but if its longer, does it correspond to your use.
Now look at the top app line, try to find which apps are running when audio triggers. To do that hover over the top app line which coincides with audio when you were not listening to audio. You will see a popup screen with a list of apps. Or check History Stats - TopApplicationSummary for a table, screen shot that and post
Do you use a lot of widgets that update in the background ?
- something was using mobile data when you were watching stored videos at lunch. Take a look at the'mobile radio active' line and you see activity there around lunch. Your wifi however is off and not running. If there were any apps running they were using mobile data, this is extra drain
- take a look at the line that says 'foreground process'. it's pretty solid right through both your runs. The only time it stops is when you recharge. This is a hint something is up. If you hover above it what does the popup say ? try moving along the line and observe whether the information changes
There shouldn't a foreground process running when you're not using the phone. Maybe if you can screen shot, the table that displays under History Stats - Foreground Process Summary
Scroll down and under the graph and on the left you will see three headers with twisties, System stats, History stats & App Stats
Hold on to your bug report files and they will be useful to verify if any changes you make take effect or not
- 1% per hour corresponds to second screen on, with it off your drain would be halved. However having drain after leaving a music or browsing app isn't good. It means a wakelock was caused and its not releasing so doze can't kick in. So battery will drain. If the phone is shaking, say in your pocket as you walk around, full doze won't kick in either
Which social media apps do you use.
Stock launcher or other if so which
I've found just buying a new battery off of ebay for $10 is the the easiest way to gain back that extra hour of on screen time and extend stand by. That's why the phone was made with a removable battery. I have 3 of them and don't need to touch a charger for a week. and when the time comes to charge the batteries, just put them in the charging docks and done.