So. I tried updating from CM10.2 to CM11 a few months ago and I encountered a whole mess of wakelock issues that utterly destroyed any semblance of battery life. Compared to 10.2, I literally got half the battery life I was getting, which was not acceptable as a normal day of average usage on 10.2 would end me around 50% and a heavy-use day would have me around 30%. Losing half my battery life is simply not an option.
Using BetterBatteryStats, I discovered that the browser and Google Play Services were both generating absurd numbers of wakelocks via NlpCollectorWakelock. Turning off location services "fixed" this, but also disabled all location services. Not a real useful solution for someone who actually uses location services, especially since there's no "fast" way to enable location services and GPS all at once from location completely off.
This was annoying enough, but then I noticed as well that I was getting another wakelock when on wifi: msm_hsic_host. This didn't happen every time, but it seemed to be entirely linked to using wifi. Again, like the location services wakelocks, this conspired to murder battery life. Rebooting seemed to clear this one, but the fact that it exists at all in CM11 (and does not happen ever in CM10.2) is causing me a problem in that I have to allow wifi to turn itself off when the phone sleeps. This uses less battery than getting stupid wakelocks but not less than simply leaving wifi on all the time in CM10.2. So that's annoying.
These issues conspired to kill my battery life so thoroughly that I flashed back to CM10.2 and everything was fine, but Kitkat brings a lot of great things that I really don't want to give up. So I tried installing CM11 again, this time using the M6 snapshot release. At first, everything was pretty cool and I didn't see any unusual wakelocks, but after a few days, the wakelocks returned. All of the same ones from the nightly I used back in March!
NlpCollectorWakelock on both the Browser and Google Play Services, and msm_hsic_host whenever using wifi. The gremlins were back and my battery started going fast.
This time I tried a few things to help and managed to kill the NlpCollectorWakelock issues simply by using App Ops to prevent Play Services and the Browser from ever being allowed to create a wakelock. That actually worked really, really well to kill those wakelocks and any others (I don't see any reason why either application would need to wakelock my device other than to phone home to Google and tell them where the phone is, and my tests have borne this out, though occasionally the restricted apps will force-close when I wake the phone from sleep).
However, this didn't stop the msm_hsic_host kernel wakelocks. I can't stop them other than by either not using wifi at all (not an option) or allowing the device to power the wifi radio off when the device is asleep, or simply dealing with msm_hsic_host wakelocks when they appear, rebooting the device whenever I catch them. For now this is what I'm doing, letting the device power off my wifi radio, but it's annoying because my signal at home is bad and I sometimes miss notifications when in certain rooms of my apartment due to dropped cell signal.
Anyway, I don't really want to have to go back to CM10.2 again. But having my battery randomly slaughtered by msm_hsic_host wakelocks are making it somewhat less useful. I had this wakelock hit me tonight and for five hours the phone was awake when it should have been asleep for four hours and fifty minutes... and I dropped from 75% to 55% battery in that five hours. That's absolutely crippling.
Some things are attached below--unfortunately I didn't take screenshots of BetterBatteryStats before rebooting and the log doesn't stick around after reboots in Kitkat like it did in 4.3.
Device Stats:
ROM: CyanogenMod 11 M6 release
Kernel: Stock CM11 kernel
Radio: .33/.98 hybrid radio (LTE enabled)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hello and thanks for reading ,
I am experiencing a very bad tablet battery life since November 2013.In these past month's i have visited forums, flash factory OS,turned off the radio(and wifi), installed many battery saving apps (didn't work), boot safe mode(drain still there), rubbed snake oil(really dangerous) and the battery still drains faster than a monsoon gutter.
Below is a screen shot of the tablet after I left it to idle for one night .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions in solving of the problem are much appreciated and no ,i do not like 4.4.2 cause it breaks my FLAC playback (and still [email protected]% perhour)(currently running 4.3)
Thanks and regards shinra_co
I've got exactly the same problem; battery drains very quick even with airplane mode on. Tablet Idle is the culprit according to the power settings. I wonder what this means and how to solve this issue. can hardly use the tablet, i always need to recharge it.
shinra_co said:
Hello and thanks for reading ,
I am experiencing a very bad tablet battery life since November 2013.In these past month's i have visited forums, flash factory OS,turned off the radio(and wifi), installed many battery saving apps (didn't work), boot safe mode(drain still there), rubbed snake oil(really dangerous) and the battery still drains faster than a monsoon gutter.
Below is a screen shot of the tablet after I left it to idle for one night .
Any suggestions in solving of the problem are much appreciated and no ,i do not like 4.4.2 cause it breaks my FLAC playback (and still [email protected]% perhour)(currently running 4.3)
Thanks and regards shinra_co
Click to expand...
Click to collapse
yves.alexis said:
I've got exactly the same problem; battery drains very quick even with airplane mode on. Tablet Idle is the culprit according to the power settings. I wonder what this means and how to solve this issue. can hardly use the tablet, i always need to recharge it.
Click to expand...
Click to collapse
Same here, and this just started a couple of days ago. Usually, with my usage pattern, I only needed to recharge once a week. Just over night this changed to nightly... Quite annoying.
Me too
Newfarm said:
Same here, and this just started a couple of days ago. Usually, with my usage pattern, I only needed to recharge once a week. Just over night this changed to nightly... Quite annoying.
Click to expand...
Click to collapse
Registering only to add my "me too" to this problem. The battery is depleted in a few hours (6 to 10) when the tablet is turned off, no sleeping, turned off, even after using the recovery menu option in order to force the power down. It is always lightly hot to the touch when it is automatically discharging, again when turned off.
This is my first Asus device and I am trying to request a refund, I don't want a new device, or a repaired one. I want my money back. I am not sure this will happen because it was bought on December, but this is not tolerable
5 Months in and various updates later (KK 4.4.4 KTU84P right now).
The battery still drain away @ 5.0 per hour minimum.
As per original post, I have still not been able to find the source of the drain.
wakelock detector, better battery stats and battery doctor have been of little help this past months.
Assuming it is not software related, what are the chances it is the hardware ie the battery itself being the culprit.
if so i think i'll wait for the rumored 8" nexus tablet.
Premise:
idle battery drain in LP is much worse than in KK (1% per 1 hour vs. 3 hours.)
Personal experience : after disabling most of background apps in both OS's, the battery drain in LP is about 1% per hour, while it was 1% per 3 hours in KK.
New information:
I did a new test. I restarted the phone and charged it full. I then left it idle for about 6 hours.
Here are the results after 6 hours of a charged idle phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Conclusions:
1) The constant wakelocks in idle state are due to S-Health app. They are not responsible for the battery drain.
2) Cleanly after restart, the phone drains the battery in idle mode at a rate of 1% per 3 hours, even in LP.
3) Something else is responsible for draining the battery at 3x the rate (of 1% per 1 hour.) This new culprit is only introduced on using the phone for a while.
I will continue testing this.
Any new ideas are appreciated.
The single biggest reason that I miss root is to figure out wakelocks on these things.
usmaak said:
The single biggest reason that I miss root is to figure out wakelocks on these things.
Click to expand...
Click to collapse
Someone posted a way to get Wakelock Detector working w/o root:
1) Connect phone to usb.
2) Do "adb devices" then do "adb tcpip 5555"
3) Open Terminal Emulator and do "adb kill-server" and "adb devices"
4) At this point, Wakelock Detector works.
Thanks for that info. I'll have to give that a try.
usmaak said:
The single biggest reason that I miss root is to figure out wakelocks on these things.
Click to expand...
Click to collapse
You can use wakelock detector without root, over usb adb
Sent from my SM-N910V using Tapatalk
I have been seeing the same awake vs screen on behaviour, my fiance isn't seeing that trend as much and her battery life is better. I'm not complaining much about mine, but it could be better. I've tried clearing cache, battery pull, uninstalling apps, and changing sync settings.
Android Central published an article about the bad battery life on the S6. Samsung just updated the push service that affects the S6, S5 and Note series. Might be worth looking into.
http://www.androidcentral.com/galaxy-s6-battery-life-bad-update-might-help
I got wakelock detector set up with the instructions in this thread. It sort of works. It shows no Kernel wakelocks, and I think that it's very unlikely that my phone has had no Kernel wakelocks in the last 18 hours.
Yes I have been tracking this Note 4 with WLD for a couple months now and I haven't been able to pinpoit the issue of battery/wakelocks. It seems to be something very fundamental inside android itself. My wife's Note 3 absolutely does not have these problems. She can get 8 hours of screen time in a day. I am lucky to hit 4
Hello,
I find the OPT's battery life to be pretty disappointing, and a bit inconsistent over time.
I rooted and installed Amplify with some pretty aggressive settings. I have also tried Powernap, but disabled it when I saw it had very little impact.
Below are today's stats for my battery, which is just about 20% after 13 hours of moderate use.
It looks to me like wakelock should be under control (1% of battery in GSAM), but why is the phone awake so often then? Plus there was some odd GPS behavior: what is your opinion on this?
I hope I am not breaking any rules. Any suggestions would be much appreciated.
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You're not reading the GSam stats properly, your wakelocks are almost equal to your screen time, and like 28% of your screen off time.. Not good. Your awake time percentage is roughly three times what mine is. You may have a kernel wakelock rather than apps causing problems but can't tell without wakelock detector or similar.
Sent from my A0001 using Tapatalk
Thanks, will try wakelock detector and report back
Can't confirm your disappointment...
In my opinion it's OK to have roundabout 2,5h DOT and last half battery with an Lollipop rom
Wow, wakelock detector revealed a massive drain from the fingerprint scanner... Probably due to the fact that I keep the phone in my pocket with no case, so it turns on very frequently only to "read" my thigh through the fabric.
I tried disabling fingerprint scanner and had immediate benefits on standby time. I wonder if this means I will be unable to ever use this great feature, or if sensitivity will be adjusted in future OTAs.
Screen on time remains rather poor though, or at least a far cry from the 5 hours everyone else seems to get.
My battery with screen off goes down 52% after 2 days. Have 2.1, latest custom kernel,greenify + amplify. the culprit is mobile standby as there are parts of house with bad reception. airplane mode not an option
Last night I tested battery drainage overnight from around 11pm to 7am.
I lost 3% total.
I set the phone to LTE (WiFi off) and disabled Auto-Sync Data under Accounts.
3% overnight is not bad IMHO.
Hi guys,
The standby time on OPT is very bad, however if I use it I get amazing SOT.
I am gettng these 2 kernel wakelocks in OPT, qpnp_fg_memaccess & qpnp_fg_update_sram.
These are always in top 3 wakelocks. I tried to search about them but could not find anything.
Can anyone tell me what are these and why do they occur and how can i avoid them?
Donaroriak said:
Wow, wakelock detector revealed a massive drain from the fingerprint scanner... Probably due to the fact that I keep the phone in my pocket with no case, so it turns on very frequently only to "read" my thigh through the fabric.
I tried disabling fingerprint scanner and had immediate benefits on standby time. I wonder if this means I will be unable to ever use this great feature, or if sensitivity will be adjusted in future OTAs.
Screen on time remains rather poor though, or at least a far cry from the 5 hours everyone else seems to get.
Click to expand...
Click to collapse
So ... why don't you keep it somewhere else? Or put it in a flip case? That would be an easy remedy without sacrificing usability too much. I never really get it why people deliberately expose their thighs and possibly also their reproductive organs to so much radio waves ... or keep their mobile connection activated over night ...
Actually I have solved this by always pocketing the phone with the screen facing away
I am using Sky dragon ROM and Boeflla v18
Used 70 % battery in 23 hours with around 6 Hrs active. so it is good. Mostly Used in real racing 3 and asphalt. Plus I am running several xposed mods and Layers Themes
I've noticed some WiFi weirdness since I got my (vzw) 10. While watching a video in chrome, sometimes (usually right after a reboot) it'll play perfectly fine. Other occasions it'll have issues streaming, and when it pauses to buffer, it takes way longer than it should. Most of the time it completely freezes up chrome. Disconnecting from WiFi so it uses the data connection and it immediately resumes playing and has zero issues. Even occasionally while browsing the web, it'll just completely fail to load a page.
On a side note, I won't be able to confirm till tonight when I sleep and I leave it on disconnected from WiFi, but it seems to drain the battery. Obviously WiFi drains battery, but I'm talking crazy drain, 10-12% over 7 hrs.
Can anyone corroborate this happening to them? I'm thinking possibly firmware or ROM bug.
I have the wifi on during sleep only when plugged in and wifi stayed on all night, its a solid bar. I've barely used my phone since waking up and its already dropped 9%. I am seeing a drain issue and I can't find it.
RusTachio said:
I have the wifi on during sleep only when plugged in and wifi stayed on all night, its a solid bar. I've barely used my phone since waking up and its already dropped 9%. I am seeing a drain issue and I can't find it.
Click to expand...
Click to collapse
So it seems like we have WiFi issues then. I'm curious, do you have a vzw 10 or no? Wondering if it's a vzw only issue.
Yeah VZW 10. I don't know if it is actually the wifi, but I had to charge 3 times yesterday. Everything drains the battery.
yeah lost 15% in a 6 hour night. wifi always on.
I'm not even sure myself but my battery drains at a rate of 1% every 10 minutes even on standby. I've disable auto-sync, and it helped slightly but it's still draining abnormally fast.
You guys with issues on drain are you on 5ghz radio or 2.4ghz.?
dottat said:
You guys with issues on drain are you on 5ghz radio or 2.4ghz.?
Click to expand...
Click to collapse
I've tried both, there doesn't seem to be a difference.
I'm on AT&T network. I lost 1% overnight over a 7+ hour period. I was quite impressed.
Sent from my HTC 10 using XDA-Developers mobile app
AU unlocked set, lost 10% throughout the night with WIFI on.
Anyone who has root (obviously not vzw yet) wanna do some testing and find what the drain cause is?
I still haven't been able to nail down a fix for WiFi being unusable sadly.
I have the same issue when it comes to battery drain on wifi. You guys could try and disable the following settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The settings are underground locaties then in the menu on the top right.
This helped for me on the international HTC 10
Verstuurd vanaf mijn HTC 10 met Tapatalk
I installed Resurrection Remix 5.6.9 two days ago and thing have been GREAT until this afternoon.
On the way home from, I suddenly noticed my battery started draining way too fast.
Tonight, I've been monitoring, and it's lost the same amount of battery in less than an hour as it did all last night unplugged 7 hours while I slept.
I installed gsam battery monitor in the hopes it would provide me with more inromation than the standard battery info from Android settings menu, but it's not telling me much more.
Also, in the time from 8:50 - 9:10 that I had the screen off and phone unplugged, the phone is warm like I've had the screen on using a CPU intensive app.
What else can I do to track what is causing this battery drain? (and i'm assuming CPU usage).
The only thing I did today that was any different was to install the Asus Pixelmaster camera app from the play store. other than that, absolutely no different usage today than the past two days.
I have just now uninstalled the Asus camera app to see if that is the culprit, but I don't see how it could be.
This is my first go with Resurrection Remix, but I did use the Asus Pixelmaster camera on CM13 and (obviously) stock and stock rooted ROMs.
Please, any thoughts on this?
@BigBrosMo this might interest you as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Craziness.... Not the camera. Something in cyanogen. The flat a section is airplane mode.
i could not track down what was causing the problem. this morning was even worse - about 1% drain every two to three minutes .
i'm trying out the XOSP ROM now.
I noticed if i turn the wifi off the drain is reduced significantly. Bluetooth is on, cellular on, wifi off.
Did you get any further in diagnosing battery loss? It's taking forever for RR 5.7.1 to get released.
I am having this issue to! On a couple roms at that. Anything you have found to resolve this?
KyleMart06 said:
I am having this issue to! On a couple roms at that. Anything you have found to resolve this?
Click to expand...
Click to collapse
No.. I just keep trying different Roms. I use resurrection remix latest and it's ok as long s location is completely off. If on high accuracy or battery Saver it kills battery. So I only use sparingly.
huh... so odd. I was excited about this one but I am getting ADs now and the battery issues. Had the same thing in Resurrection and now XOSP. In my troubleshooting, I installed an original ROM and that seemed to run fine. Going to see if someone deodexed one and flash that...
Take a look at this
It may be with 'Keep Wi-Fi on during sleep' activity. Set it to 'Never'.
OR
Step A: Set 'can modify system settings' of 'Xender' in 'modify system settings' to off.
(But by keeping this off, everytime Xender prompts 'allow changing settings' and you need to allow it to use the app. After the use, you need to again do the Step A)