I've had this phone for a few days now and I notice some mean battery drain that happens from time to time. I dumped a Bug Report via developer options, and used Google's Battery Historian after leaving my phone unplugged and idle overnight after a full charge and reboot. The tool seems to show that the following kernel wakeup reason seems to be the problem and holding the phone awake for over 1.5 hours:
Code:
Ranking Name Duration/Hr Count/Hr Total Duration Total Count
0 Abort:Wakeup IRQ -1111803216 (null) pending 10m8s737ms 779.87 1h34m13.62s 7243
The only thing that looks remotely relevant is that on the tool WiFi signal strength became weaker when the above wakeup events started.
Has anyone else had similar issues with random battery drains like this and/or happen to know any workarounds?
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
I tried setting wifi to stay on when sleeping when plugged in, after a full idle overnight, I used my phone in the morning and the same issue came up. The ID above was different, but generally the same problem (IRQ with no description pending). Again, it looks to be wifi related based on the battery stats in Historian. I've rebooted, charged up and turned off wifi to see if the problem goes away.
ru_ready said:
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
Click to expand...
Click to collapse
You might want to try enabling developer options and getting a bugreport generated (which has battery stats), and then visualizing it in Google's Battery Historian to see if it is the same problem. Kind of convoluted, I know, but without root, I don't know of any better way to analyze kernel wakelocks (it isn't a partial wakelock issue on my device).
Last night I left my phone idle with wifi off and WLAN Scanning and Bluetooth Scanning off under Location Settings. The battery ran down only 2% over 9 hours and the Wakeup IRQ pending problem did not keep the phone awake!
I am going to try turning wifi back on today but keep the scanning off and see if that keeps this problem at bay. If not, I may use Tasker to force wifi off when the screen is not on and not plugged in.
The wakelocks seem to happen randomly no matter what my wifi settings are. Though I do think it is related to location settings trying to use wifi scanning.
I give up, there is no reason why a phone I just bought should be like this.
Maybe there are some apk wake up the system
@kumodog Maybe there are some apk wake up the system, you can reboot the system and kill all of application programs when you test it in night with wifi on.
After test, you can also use : "adb dumpsys alarm" in command line to find Top Alarms. it will tell you which alarm make system wakeup.
Related
Hi everyone here
I got a concern about my TF101 Tablet.
When I switch my Tablet screen off and set the WiFi as turn off when screen off, my battery still drains extremely fast. From the pic you can see, my battery is running out from full to 10% in only 1day and 6 hours without any use. My GPS and bluetooth are also turned off in this period. From the pic you can also see my CPU load is over 30% at most of the time.
From the second pic, I can see the process "System" uses the CPU very hard
Can some one figure it out and I will appriciate it very much!
Here I have to bump...
wm2001wm2001 said:
Hi everyone here
I got a concern about my TF101 Tablet.
When I switch my Tablet screen off and set the WiFi as turn off when screen off, my battery still drains extremely fast. From the pic you can see, my battery is running out from full to 10% in only 1day and 6 hours without any use. My GPS and bluetooth are also turned off in this period. From the pic you can also see my CPU load is over 30% at most of the time.
From the second pic, I can see the process "System" uses the CPU very hard
Can some one figure it out and I will appriciate it very much!
Click to expand...
Click to collapse
I am seeing the exact same problem, not sure what the cause is either. I read somewhere about "wakelocks" where some app will try to keep the CPU awake when you try to go into standby and it results in high system usage.
Thank you for this thread, I am also having this problem. I think the problem for me may be because of Google Maps.
Basically, I'm running some tests now. I had massive battery drain overnight while I slept. The tablet would go from 90% down to 50% in an 10 hour period (4%/hr). It didn't matter if it was docked or not docked. I was running Google Maps v5.8.0 and saw some people post that the new version is eating up the battery. So I removed the updates for Google Maps and tried again.
Now I'm running v5.6.1 of Google Maps and the battery went from 100% to 42% in a 17 hour period with absolutely no use (3.5%/hr). I checked battery usage, and Google Maps is at the top and it's taking up 41% of what was used. That's ridiculous.
So now I'm going to install the latest Google Maps and see if this helps at all. I've also attached some screen shots of my latest tests.
Other details:
Wi-Fi is set to sleep when the screen turns off.
MobileDock Battery saving mode is checked.
Use location for Google Search is unchecked.
I did another test last night after having updated Google Maps to v5.9.0 (latest). I got the same results. Google Maps is eating through my battery when the tablet should be sleeping.
Here's the results:
The tablet was undocked, and fully charged.
I didn't touch the tablet for 15 hours.
The battery went from 100% to 55% in 15 hours = 3%/hr drain.
Google Maps was largest user of battery at 75%!!
I also did a reboot after I updated Google Maps to v5.9.0.
WTH is going on here?! Anyone have any ideas??
ScubaSteveo said:
I did another test last night after having updated Google Maps to v5.9.0 (latest). I got the same results. Google Maps is eating through my battery when the tablet should be sleeping.
Here's the results:
The tablet was undocked, and fully charged.
I didn't touch the tablet for 15 hours.
The battery went from 100% to 55% in 15 hours = 3%/hr drain.
Google Maps was largest user of battery at 75%!!
I also did a reboot after I updated Google Maps to v5.9.0.
WTH is going on here?! Anyone have any ideas??
Click to expand...
Click to collapse
Try turning off all location services (WIFI/GPS) and see if the problem goes away. I did something similar and the sleep mode CPU utilization dropped back to 1% or so. I haven't yet enabled the settings one by one to see which one cis causing the issue.
wilkster said:
Try turning off all location services (WIFI/GPS) and see if the problem goes away. I did something similar and the sleep mode CPU utilization dropped back to 1% or so. I haven't yet enabled the settings one by one to see which one cis causing the issue.
Click to expand...
Click to collapse
You are correct. I am able to turn the Airplane mode on and see virtually no battery drain at night. But this is rather annoying to have to turn on airplane mode every time you are done using the tablet and turn it back off whenever you want to use the tablet.
The best option would be to locate the source of this issue and fix that. Tonight I'll be testing Google Latitude turned off to see if this fixes anything.
As a test I turned back on location services (GPS/Google) but unchecked the use WiFi for location and found the problem went away overnight. Only a few % CPU use. Not quite as good as leaving in Airplane mode but close. Lost about 2-3% CPU over 7 hours. WiFi use setting is to disable with screen turned off.
So after my test last night, I still had massive battery drain.
I turned off Latitude as best I could last night and still same result. Google Maps is chewing up my battery like no other: from 100% to 52% in 15 hours with zero usage by me. Anyone have any other ideas? Any other apps that might be causing this?
ScubaSteveo said:
So after my test last night, I still had massive battery drain.
I turned off Latitude as best I could last night and still same result. Google Maps is chewing up my battery like no other: from 100% to 52% in 15 hours with zero usage by me. Anyone have any other ideas? Any other apps that might be causing this?
Click to expand...
Click to collapse
I had previously logged out of latitude and saw the same high drain result as you, so don't think it is that. When I disabled the WiFi location the drain stopped (leaving gps on). I agree it may be Google maps related since it uses the WiFi location services (since maps uses that service to locate the tablet along with gps).
I have a similar issue, but my problem is not with Google Maps. Instead, the main battery drain is "Android System." I usually leave my Transformer on standby 24/7 and used to only have to charge once a week. This problem appeared out of the blue a few days ago.
Google mail is the only thing on auto-sync, and this setting has never caused any issues in the past. Thus, I'm not sure why Android System is now suddenly waking up at random when asleep. You can see in the plot that System constantly requires 30% CPU usage once it happens, until I actually turn the device back on.
In addition, my wi-fi sleep policy is set to turn off when the screen is off. Recently, it seems it is always on, even when the device is asleep.
EDIT: The graphs from the OP suggest that our issue might be related, but the problem appears to manifest much more frequently for the OP. Crossing my fingers that next week's update somehow fixes this problem.
LagginTimes said:
I have a similar issue, but my problem is not with Google Maps. Instead, the main battery drain is "Android System." I usually leave my Transformer on standby 24/7 and used to only have to charge once a week. This problem appeared out of the blue a few days ago.
Google mail is the only thing on auto-sync, and this setting has never caused any issues in the past. Thus, I'm not sure why Android System is now suddenly waking up at random when asleep. You can see in the plot that System constantly requires 30% CPU usage once it happens, until I actually turn the device back on.
In addition, my wi-fi sleep policy is set to turn off when the screen is off. Recently, it seems it is always on, even when the device is asleep.
EDIT: The graphs from the OP suggest that our issue might be related, but the problem appears to manifest much more frequently for the OP. Crossing my fingers that next week's update somehow fixes this problem.
Click to expand...
Click to collapse
The system process was the same issue on my system as well (didn't show up as google maps). I confirmed that turning off the "Use Wireless Networks" under Location and Security stopped the constant 30% cpu usage when in standby.
After freezing Maps, which is the biggest culprit for me....i noticed, System Process' was way high now.
28%
After doing some searching.... came up with this
http://forum.xda-developers.com/showpost.php?p=16828183&postcount=605
At least for my case.
Google Maps battery drain Solved!
For me, I figured out the issue was Latitude.
I was getting bad battery drain overnight and Google Maps was the largest user by far. I finally signed out of Latitude completely. Battery drain dropped to around 2% (total) overnight! This is acceptable!
As it turns out, Latitude wakes up my device while it should be sleeping in order to update my location and therefore draining massive battery overnight. I'm going to post this as a bug with Latitude/Google Maps because this is causing waaaay too much battery drain.
So it looks like I won't be able to leave Latitude signed in. Once I'm done using it, I will have to sign out of Latitude. This way I can leave Wi-Fi on and set to turn off when the screen turns off. Thereby I get really good battery life again.
On a side note, my phone has the same behaviour, but I never noticed it because I'm usually charging my phone at night. So Latitude...basically...sucks (battery).
Okay, I've been trying to diagnose a somewhat annoying issue. I've been using a fairly simple set of conditions in the Llama utility to automatically disable Wifi when the screen turns off in CM7 to prevent a wakelock condition and reduce battery drain.
So I activate wifi, I reset the log in CPU Spy, and I lock the phone disabling the screen. When I reactivate the phone and check CPU Spy, wifi was definately off but the phone was never in Deep Sleep, so something was holding the wakelock I guess. I repeat the experiment with no changes and Llama still running, but this time I manually disable wifi before locking the screen. This time the phone immediately goes into Deep Sleep according to CPU Spy-- it works perfectly.
So what is the difference between Llama autodisabling and manually disabling wifi that leaves a wakelock active? I've repeated this experiment like ten times last night, and it isn't making much sense to me.
Thanks,
Gnat
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
mikel81 said:
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
Click to expand...
Click to collapse
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
On the general battery issues on Triumph, one of the more helpful discussions I've seen is this one here-- http://androidforums.com/triumph-all-things-root/456795-cm7-triumph-battery-life-improvement.html. In it a quote from Tickerguy blesses the JuiceDefender approach to throttling data use for battery savings, but I don't think he had done any analysis regarding wakelocks. BTW, I reverted to stock today, and I am finding the exact same problems as CM7-- wifi imposes a wakelock, and Llama can't shut down wifi automatically without the wakelock persisting. I have to manually toggle wifi off before screen off before the wakelock is gone.
Regards,
Gnat
gnatd said:
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
Click to expand...
Click to collapse
Sorry; the wakelock is WLAN. It is almost always active if JD is toggling wifi. I hadn't tried disabling wifi manually but leaving JD active yet. I just tested that and got deep sleep immediately. So it must have something to do with how it disables wifi isn't releasing the wakelock.
You know, after switching back to stock from CM7 I'm really not sure I'm not happier. With CM7 I was getting worse battery performance, which led me to start obsessing about wakelocks and deep sleep. Now that I am back on stock, I do the same analysis and see that I have the same problems with wakelocks and deep sleep-- but the battery performance is better so it's not that big a deal. I'm sure that there are things I could do to make CM7 have better battery performance-- but I wasn't enjoying the process and wasn't finding answers, so why bother?
It's like power management programs. I ran Green Power for a long time, and had some glitchy problems with being unable to get wifi to turn on even though it wasn't supposed to be managed while the screen was on. Then I disabled it, and you know what... my battery life was good enough to get me through the day. Froyo is good enough to get me through the day.
The wakelock was put in there on purpose to prevent the phone from hanging when WiFi was on and the phone went to sleep. I use my power widget to turn off WiFi before I turned off the screen unless I'm actually using it.
You could try and build it to see if removing the wakelock is still necessary. If you need help on that side, just post and I'll help. It's not hard, really.
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.
Hi, so basically, i've got a weird issue. and i've gone through many other threads regarding this, but still have not been able to find a proper solution.
firstly, when i'm connected to wifi, i don't receive my notifications when the screen is locked. until i wake the phone up the notifications come up. and yes, on advanced wifi - keep wifi on during sleep is on always.
when i disable wifi optimisation, it's slightly better but not completely solved. it's jumpy, as in sometimes i get a notification and sometimes i don't till i wake the phone. however the phone's idle battery consumption jumps from 9-20 mAh to about 40-100mAh which i hate.
this leads to - when im not on wifi my idle battery consumption is between 6-10mAh, whilst on wifi with wifi optimisation enabled its 9-20mAh.
Through reading numerous threads, i installed push notifications fixer - root. it has kind of fixed my push notifications issue, but now idle battery consumption is between 100-145mAh.
I do believe it's an issue with my router, but when i installed another router, the same issue popped up. could it be both routers are at fault. or something else?
guys please help as i'm sure others have the same issue.
There is a jira open here:
https://jira.cyanogenmod.org/browse/BACON-1649
Now i've taken screenshots to display how the it was and how it is now with push notifications fixer.
no one?
I can only say I noticed this when I wake up my phone all notifications comes at batch. Also, while in deep sleep I do get combined notifications at batches.
it looks like scheduled data connection, goes on and off. In term of the delay its max 3 minutes when I compare it with message notification time sent and time arrival.
In my case I don't suffer from battery drain.
Hello,
my battery only lasts half a day max, before needing a recharge. I've already tried different custom roms, and currently I'm on Blisspop for android 5.1. The area I live in has good coverage, so that shouldn't be the culprit. I never play games on my device, but even basic web browsing drains my battery very rapidly. I do use android wear, but I don't think that is the reason I only get around 1 hour of screen on time.
Here are the things I've tried already:
- Turning off location reporting
- Disabling Google Now
- Removing Google Fit
- 'recalibrating' the battery by letting it discharge and then charge it fully without unplugging
- Using 3g instead of 4g
- Turning off location access
This is driving me nuts, and I don't know if it's my battery's fault or my phone's fault.
Thanks in advance.
Go to wifi, special, and disable scanning when the wifi is off. It helps A LOT. Also keep location reporting off, as setting it to network only creates tons of wakelocks even when mobile data and wifi are turned off.
I know some custom ROMS have had issues with Bluetooth battery drain in the past. Try turning it off and see what happens.
Turn down the brightness as well. There is significant difference in power usage between %50 and %100 brightness .
Hold power button and select power off. Helps