Develop Bugs

[Q] Battery drain on Note 2 after 4.3 update

Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock detector, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks

I had the very same problem until yesterday myself but think I found a solution on the web.. Uninstall Google Search and Google Play Services and the goto the Play Store and wait for them to reinstall and that's it....! As I found that there is a bug in Google Services (Nlpwakelock and Location service)
Hope this helps...?
Sent from my GT-N7100 using xda app-developers app

terzisc said:
Hello
I have had a massive battery drain problem on my Note 2, a couple of days after the 4.3 update. While being idle during the night it loses 25% to 30% of its battery and while using it I can literally see the percentage drop. I have tried everything that I could find on the net. EVERYTHING! Nothing worked. These included: Factory reset (twice), letting the battery frain completely and then recharging it while the phone was switched off, switching off all sync,disabling bloatware including KNOX components (the actual KNOX app is not installed), installing only a few apps after factory reset, using Gsam, Wakelock defender, Deep sleep battery saver (which could not make my phone sleep), no GPS, no 3G, wifi on only when needed and more besides.
The phone is only one year old and unrooted. On 4.1.2 it had a beastly battery performance of almost 1.5 days of normal to heavy use, with 300 apps on it. Now it cannot go for more than a few hours with the same use.
I cannot say for sure but it seems to me that the drain is the same when it is sleeping and when I am using it. Wakelock has given me a 75% awake time even though I only use it for 15-20% of the day at most nowadays. Battery settings show everything normal, or at least I think so, eg Screen 35%, Android OS 15-28%, Voice calls 10%, Android system 5-15%, Cell standby 7%, Device idle 4%, Media server 4%. The batttery chart shows a constant steep drop all the time.
The problem started one day when the Media server went mad consuming 50% of the battery. After I did the factory reset it has never again been a problem but the drain still persists.
I have also read that it's a mess up between syncing of Samsung apps and Google services, but I have no way of verifying that.
Can anyone help?
Thanks
Click to expand...
Click to collapse
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app

yeminswe said:
Download wakelock detector from the play store. It detect which app is waking your device (both screen and cpu) by list.. Then download greenify from the play store and herbinate (greenify) upper most apps from wakelock detector. Hope you can solve your problem
Sent from my GT-N7100 using XDA Premium 4 mobile app[/
Thanks. I already have Wakelock Detector on. I mistakenly wrote "defender" instead of detector on the original post. It gives me Viber and Messenger as the most active wakelock apps. But they both were not installed when the problem started. Besides, on the 4.1.2 they created no problems. In essence I believe that Wakelock Detector cannot help much. Whatever this problem is , it is well hidden. Thanks for your interest and help anyway. Much appreciated.
Click to expand...
Click to collapse

In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk

Manjunath324 said:
In wifi settings, goto advanced and untick scanning always available.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I have checked and it was not ticked in the first place...unfortunately...

terzisc said:
Thanks, but I have checked and it was not ticked in the first place...unfortunately...
Click to expand...
Click to collapse
Which kernel you are using? And also i recommend using Greenify. Widgets usually eat a lot of battery, I went from battery lasting only 8 hours to get my battery use only 30% in 8 hours.
What i did: installed wakelock detector, gsam battery monitor and better battery stats.
Monitorized the wakelocks.
Applied greenify to the apps which were waking most
Removed widgets which were waking alot
Installed Toggle 2G.
Kernel settings: 200-1600mhz | zzmoove | AFTR+LPA | Multicore power saving (SCHED_MC) = 0 | GPU = stock settings
Works like a charm for me. Hope it helps! Any question, ask!

I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.

Nukkels said:
I've read all sorts of things about this problem since I updated and got hit. I have too much app data to lose by trying the factory restore (which by all accounts shouldn't change anything anyway since you'd still be stuck with 4.3)
I finally decided to try the age old blackberry cure-all: "if in doubt, pull it out" (the battery). Since the entire issue seemed to be related to battery caused problems (ie slow charging, fast drain, etc) it made a lot of sense.
And it worked.
I think the main reason this isn't more commonly tried to fix issues on Android is the same reason I didn't try it earlier. My case is pretty serious and isn't easy to remove. I'm glad I did take the time to take the case off though or I could have ended up wiping my phone.
Click to expand...
Click to collapse
Thank you for the suggestion. I have already taken the battery on and off several times. It had no improvement. The phone is only a year old, that is why I don't believe the battery is the culprit. Besides, problems started only after the 4.3 update. Before that it was working perfect. Too much of a coincidence.

Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.

Nukkels said:
Sorry to hear that it didn't work for you
I'm not saying the battery is faulty in any way - however removing the battery and letting the phone power drain completely seems to stop whatever process is running under the buggy 4.3 long enough for it to work again as intended. It's basically just a more thorough way to reboot.
As I said, I've read all sorts of suggestions, many of which don't work for everyone (such as the factory reset) - this is hopefully just one more thing for people to try before they end up wiping their phone in desperation. I mainly posted here in the hopes that others with this issue that may not be forum members can get some more suggestions.
At least for me, wakelock and all the other diagnostic tools at my disposal showed nothing different to before the update. Many other people have found that the Android System is using a lot more of their battery than normal or some other apps are involved - if this is the case, it's likely to be a combination of things causing the issue (the firmware, the drivers, apps, hidden Samsung processes, etc).
Also, for what it's worth, I found that Knox supposedly wasn't installed (when I find it in the apps list, the button to install it is showing...). But it's showing in the list of apps so it must already be installed. I dug through the list of running processes (had to show the system processes too) and I discovered that several Knox and some other new Samsung processes were indeed running.
One other quick tip - If you wanted to check/tweak the 'developer options' and can't seem to find it any more, that's because it's now hidden since 4.2 - go to 'About Device' and tap 7 times on the Build Number. I tried disabling all background processes however it seems this only disables application level processes, not system level processes but if you've tried everything else, it can't hurt to try playing around with some of the options in there.[/Q
Thanks mate
I think you are right. It is probably a combination of many things. I have opened the Developer options some time back. The one thing that I do for sure in there is limit background processes to 4. Besides that I don't experiment much, exept maybe to change transition animation scale. I am actually thinking of rooting the phone and downgrading to 4.1.2. It was just fine before. I can live without the 4.3 add ons.
Click to expand...
Click to collapse

Problem still persists, even with Google+ and most other Google applications disabled

Sent from my GT-N7100 using xda app-developers app Some screenshots taken from 3 different apps. Wakelock detector, Better battery stats and Gsam battery monitor

Sent from my GT-N7100 using xda app-developers app

The only battery apps on my phone are the 3 mentioned above, so I don't know what the battery monitor that keeps my phone awake is. The drain existed before I installed these apps. I have read that Chrome could prevent the phone from going to sleep but it is disabled on my phone.
Sent from my GT-N7100 using xda app-developers app

http://www.youtube.com/watch?v=ak1sYWRaEKg

I faced same battery drainage issue, after installing wanam kernel and freezing all bloatwares through Titanium Backup. I'm satisfied with my battery now.
You can try.
Sent from my GT-N7100 using XDA Premium 4 mobile app

Here is detail-
Disable sync always, enable when needed.
Disable wifi always scan from settings
Display set to auto
Uninstall apps of playstore you rarely use
Use widgets on lock and homescreen as less as you can (I don't use any)
Disable motion on settings
Freeze all bloatwares by TB except allshare and samsung content agent
Install Agni kernel, from agni control app-
profile: normal
Governor: pegasusq
Scheduler: cfq
Don't touch other tweaks, hardly you can tweak sound boost.
THIS GIVES ME A SATISFIED BATTERY STATUS.
regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app

Wew 4.3 does have may bugs

PLEASE help me troubleshoot my ridiculous battery drain!

Before I begin, let me state that I have already factory reset countless times and reflashed my firmware at least 3 times in the past week. Neither of these have helped me at all, so PLEASE do not suggest this. I've been trying to solve this problem for a week or two and everyone has suggested this to me and of course I've already done it, so it hasn't helped me at all.
PHONE: E980
FIRMWARE: Stock 4.4.2 E98020g
BASEBAND: APQ8064/MDM9x15M
SYMPTOMS:
-Battery draining ridiculously fast (appx 10%/hr, but before my last reflash, it was draining 50%/2hrs!)
-Phone only lasts about 5hours.
-Android OS is consuming about 80-90% of battery, followed by Screen at around 10%
-Phone is constantly warm
-Phone rarely enters Deep Sleep (it stays awake 95% of the time).
TESTS DONE:
-As I said, I factory reset numerous times with the same exact problem
-I reflashed my firmware 3x, with same problems
-I usually keep auto-sync on, but the issue occurs whether it is on or not.
-There is supposably a Kitkat 4.4.2 (in general) issue where the camera will consume a ton of CPU resources and get stuck that way. I haven't used my camera much, but do use Smart Stay, so I disabled this. No positive result.
-Disabled the Google Now "OK Google" hotword detection. This helped reduce the drain, but didn't solve it. Drain went from like 15%/hr to 10%/hr.
-Took battery out of phone for 10 minutes and placed back in. Seemed to help at first, but after about an hour or so, it returned.
-"Recalibrated" the battery numerous times. This was done by draining the battery until the phone shut itself off. Then I charged the phone to 100% while the phone was still off. Once the phone read as having 100% charge, I let it charge for another 1 hour. Then I unplugged the phone and booted it up. Again, this appeared to help at first, but after a while, the phone began to drain rapidly again.
NARROWING THE ROOT PROBLEM:
-Both WakeLock Detector and BetterBatteryStats show "wlan_wake" and "wlan_wd_wake" as being the largest wakelocks.
-As previously mentioned, "Android OS" is consuming a huge amount of battery
-Problem only seems to happen when wifi is on, whether it is connected to an SSID or not.
OTHER:
I have narrowed the issue down to wifi but I can't seem to figure it out any more than this.
Both of the "wlan_" wakelocks are caused by wifi being on and I need wifi on whenever possible because I can't afford a huge data plan. My current one is 2GB/mo and it is shared between 3 people.
I noticed today that my phone drained 10% within 1 hour after taking the phone off the charger, and I was connected to my home wifi. I then went to work, but still had wifi turned on on my phone. At work, I was only connected to mobile data (but the phone was just sitting in my pocket). The battery drained another 15% within an 1hr 30min, and the phone was warm in my pocket (very uncomfortable!). I then turned wifi off completely, and the battery drain completely disappeared!!! The battery life was amazing in fact!
PICTURES:
I've provided some screenshots with notes. Please take a look at them.
I'm going to manually make the problem happen again and will upload new pictures afterwards. They will be of WLD and BBS. Any current info I have is tainted since I turned wifi off and the problem temporarily turned off too. I want to get only screenshots of what is going on when the problem is happening.
EDIT: BTW, the problem occurs whether my mods are installed or not (the mods used to remove the icons in statusbar, AdAway, etc)..
The issue seems to be pureply related to wifi and nothing else.
IDEAS:
Could adding a wifi supplement scan interval to the build.prop solve this problem?
Is Wifi bugged in this firmware? (This never happened on Jelly Bean!!!!)
Is maybe the "Battery Saving for Wifi" feature bugged?
Would maybe flashing the Jelly bean modem (e98010p) solve this issue (since it didn't happen on Jelly Bean)? If so, does anyone have a flashable version of this? <- I just did some research and it seems that the baseband (AKA modem) is the same in Kitkat as it was in Jelly Bean. Weird....

These pictures were taken shortly after making my first post. I already had wifi turned off, so I turned it back on and after a few minutes, the battery began to plummet. I went from roughly 77% to 66% in just an hour!!!!
Just to make sure that it is clear, I have both BBS and WLD set to start recording data after the phone has been unplugged from the charger. So to restart the data collection, I simply plugged the phone into my charger for a few seconds and then removed it. THEN I turned wifi on. The data seen in the pictures should only have occurred between the time when I unplugged the phone and the time I took the pictures.
EDIT: Also just to make sure it's clear: All the data shown in the System picture is actually since I unplugged the phone this morning. I only posted these pictures to show any changes from the similar ones posted earlier.
PLEASE! Can anyone help me solve this!?
Or is this a major Kitkat bug!? (or ATT bug, or modem bug, etc etc).

After a full week of this problem, I think I just made another breakthrough. Unfortunately, I think it IS one of my Xposed modules, which is weird because I didn't think any of them would have a need to constantly connect to the internet.
All I know is that I just completely uninstalled the Xposed Framework and the phone started to sleep like a baby... with wifi on!
Now I just need to pinpoint the module, which I can do myself.
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/

spexwood said:
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
Click to expand...
Click to collapse
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed

Toledo_JAB said:
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Click to expand...
Click to collapse
In this case, I need to be more specific about my solution then.
The problem seems to be caused by the module, Xposed Torch. It's still usable, but you need to tap the overflow (3-dot) icon and disable ads (it's free to do this). The module requires internet access permissions, which I was not aware of, and it constantly connects to the internet to stream the ads. This in turn causes the wifi to constantly receive data (thus the wlan_wd_wake and wlan_wake). When wifi is on, but not connected to a network, I think it forces wifi to constantly scan in order to find a connection so that it can get that ad data. I'm not sure why it doesn't just use mobile data though... unless it does and it's just more power efficient.
So far, I have disabled the ads via module settings and the phone is now sleeping like it should.
So if anyone else is having wlan_wake wakelocks of any kind, especially followed by wlan_wd_wake or wlan_rx_wake, then this means that something on your phone is constantly accessing the internet via wifi. FIrst turn off auto-sync, and if this doesn't help, then you need to uninstall apps until the problem ceases.
My phone is currently icy cold in my hand and I've never been so happy to feel it like this!

Problem came back today. I've basically uninstalled every app now and the battery is still draining whenever wifi is turned on.
Under Better Battery Stats, there is a process (?) called dhc_dpc that's been running the entire time my phone has had wifi on. There are also the wlan_wakes too. (NOTE: IIm backing up my phone right now, so these names are coming from memory).
According to this thread (different phone and unknown Android version, but similar problem), the wifi driver may be bugged. They recommend doing a reinstall, but I've done this many times now and it doesn't seem to help:
http://forum.xda-developers.com/galaxy-s2/help/dhddpc-t1246190
EDIT: I think I've found the culprit and while it is definitely wifi-related, it's NOT an app. It's the actual Android system constantly pinging the internet. According to my research, it's constantly collecting location data by using either mobile data or wifi and will do this whether you have location services (gps) or Location Reporting enabled. This has been described as a "bug." It was introduced by Google as a cool new feature, but it's implementation was buggy.
I am currently testing a fix to resolve this issue, but want to be certain that it's fully working first.
Just an an FYI, this fix SHOULD help anyone running Android 4.4.2 and experiencing high battery drain caused by Android OS. Even better, the fix does not require root, so anyone can do it!

have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone

3617 said:
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
Click to expand...
Click to collapse
Not to be rude, but the first sentence of my first post says I did this several times.

I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.

zamajalo said:
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
Click to expand...
Click to collapse
It's definitely Xposed related I think.
I've disabled Xposed during some testing a day or two ago and yeah, battery definitely improved.
The only modules I have installed are:
App Settings
Enable BatteryStats Permission (just to allow me to track this issue. I installed this after problems had already begun)
Greenify (all Xposed settings checked)
YouTube AdAway
I have also been using G2 TweaksBox up until last night. I only used it to declutter my status bar and to enable the advanced reboot menu. (I hate all the icons in the status bar!!!). Last night I disabled G2 TB and battery life improved dramatically!
I can't explain why G2 TB would cause battery drain, but I did notice it doing something odd yesterday. I have the lockscreen off sound enabled in the system settings, so I hear the sound whenever I lock the screen. Well, I turned my phone on yesterday for some reason when in my car. I then turned the screen off, heard the lock sound, and started driving. 15 minutes (NOT seconds!) into my drive, I randomly heard my phone make the locking sound, but the screen was not turned on!! I wonder if G2 TB delays my lock somehow.
I switched to GravityBox[KK] today since so many people claim that it works perfectly on their OGP, and so far, battery drain is MUUUUUCH better than with G2 TB activated, but it still may not be as good as pure stock. I need more time to figure it out though. This morning, my battery dropped 5% in 40 minutes while connected to my home wifi. I then left my house for a few hours, but left wifi turned on on my phone (it's hard for me to remember to switch it off and on all the time!). The battery seemed to be pretty stable after that, but I can't explain the weird 5% drop, but I did receive 2 missed calls and a text during that time too. Should I lose 5% just from getting a text and having my phone ring?
It's now night time and I'm at 75% battery. This past week, I would be at about 10% by now or even DEAD, so I'm happy as heck right now.
I would LOVE to be able to keep using GB, but I now just need to figure out if it too is draining battery, or if everything is stable. I'm going to continue comparing stock VS GB tonight and tomorrow. I'll live with stock if needed, but I'm just very OCD about the statusbar clutter.
In GB, I only disabled some icons, centered the clock, enabled advanced reboot menu, and enabled the lockscreen torch.

Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.

zamajalo said:
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
Click to expand...
Click to collapse
OK, so I just got home from work and today I not only had GravityBox disabled, but I also had the ENTIRE Xposed Framework uninstalled.
My battery is now at 30% and I was only gone for 7 hours!!!!!!!!!!!!!!!!!! This is ridiculous!!!!!!!!!
*sigh* <- frustrated with this whole situation
Yes, the wakelocks are still active.
The top two Kernel Wakelocks are "wlan_wd_wake" (46.3%) and "wlan_wake" (46.2%) in that order. The next in line is "PowerManagerService.Wakelocks" (8.0%) and then "msm_hsic_host" (6.1%). This was since my last reboot, which was about 2 hours ago (I had to rebooted after removing an app that I thought was the culprit... apparently it wasn't).
Again, I keep Auto Sync on, but disablign it seems to not help in this matter at all.
I also keep wifi on. When at work, it isn't connected to a network, but I often forget to disable wifi when I leave the house, or I come home and forget to enable it and end up sucking my data plan dry. Nonetheless, I also did this while on Jelly Bean and had no issues whatsoever.
My phone is only staying in deep sleep less than 10% of the time and the time when it is awake, the CPU is running at full 1.7GHz! This is causing the phone to get warm in my pocket. It doesn't hurt, but it's enough to make things uncomfortable.
According to the battery stats (in system settings), Android OS is consuming 83% of the battery.
The biggest network drainers are "Google Play Services" (33.3%), something simply called "0" (14.8%), and a weather app. I had the weather app open manually not too long ago though, so that explains that one, but the other two I can't. I have no clue what "0" is and I have not opened Play at all today.
It's something to do with wifi itself I think, and maybe not a specific app accessing wifi. (?)
I turned wifi completely off about an hour ago and the battery drain has been stable. It's been like this for days too. If I turn off wifi, the drain is "normal." If wifi is on and connected, drain is higher than with wifi off, but barely. If wifi is on and not connected, the battery level plummets like a rock in a pond.
OH! One thing I just thought about and should mention:
Before I discovered that G2 TweaksBox was causing serious drain, I was on another battery-related thread in the OGP forum. Someone told me to delete the "libiq_client.so" file from System/lib. He assured me this would give me excellent battery life (which apparently it did not). So I did. Normally, I just rename system files so I can restore them if needed, but I guess I accidentally deleted this one.
Could this be causing the drain, and if so, can someone upload a copy of libiq_client.so so I can try it on my phone (after setting it's permissions correctly)?

Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?

zamajalo said:
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
Click to expand...
Click to collapse
"Scanning always available" has been disabled since day 1
The only nand backup I have is after I already deleted the file :/
I did try clearing Google Service's cahce/data at one point and I think it helped for a few hours. It may have been a placebo effect though. I also di the recovery cache wipe and dalvik wipe with same results.
I don't keep location on at all since I don't use it. It's always off, but at one point, I did enable it to select the battery mode and then turned it off again. I did this mainly so that if and when I do use location, it would always use Battery and not High Precision.
I'm currently backing up my rom, so all partial wakelocks were cleared for now. Sorry.
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.

spexwood said:
"Scanning always available" has been disabled since day 1
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
Click to expand...
Click to collapse
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?

zamajalo said:
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
Click to expand...
Click to collapse
It's OK, I'll get the file from the flashing. I know it'll be a pain, but this may be safer just in case there is some sort of difference between the E988 and E980 versions. I doubt there would be, but better safe than sorry I guess.
I did add those settings to my build.prop as a test, but I was smart there and backed up my stock build.prop first and ended up restoring it a few hours later. It was causing my screen to not always turn on when I pressed the power button.
I have not tried any other ROMs. I prefer to stick to stock ROMs (or modified versions of stock... basically anything stock-based and not CyanogenMod or AOSP). I had bad experiences with AOSP-based ROMs on my old phone.
If I tried a stock-based ROM though, it must have everything working though. I mean everything: calls, texts, LTE, bluetooth, speaker phone, etc etc.
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....

spexwood said:
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
Click to expand...
Click to collapse
Better to misplace than to delete it, trust me
Post results.

zamajalo said:
Better to misplace than to delete it, trust me
Post results.
Click to expand...
Click to collapse
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.

spexwood said:
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
Click to expand...
Click to collapse
Libiq.so enables carrier IQ, its removal should only help battery drain, not cause it.

Just to ask, have you tried adjuating wifi scan interval? You can try as well the xposed module, "wifi deep sleep". Helped minimize my wifi related drain

~4-5% Battery drain per hour on stand by, lol. Help!

Hello,
I'm running @Schischu 's MM 6.0.1 AOSP ROM on my SM-T705W. I haven't flashed a kernel myself, it's just running what's in the ROM. I run the tablet in airplane mode, with the bluetooth, cell radio, and NFC off. Just the wifi is on.
The core of my problem is that I have no EFS. I lost it a bunch of flashes ago, and have no interest in getting it back. I'm happy without that functionality. HOWEVER, on this ROM (doesn't happen on stock, or any of the official/unofficial 5.0.1 LP AOSP derivatives, I've tried AICP, CM12.1, PacMan) The battery drains super quick.
I figured it was GApps, and there was a wakelock that was trying the missing cell radio, so I did a clean flash from stock (TW 5.0.1, the BOH1 release) to the latest MM ROM (root using chainfire, TWRP 2.8, wipe dalvik, cache, system, data, internal mem, flash ROM, and boot to system) with no GApps. I get the same battery drain, no apk's added, no GApps. So it's a MM problem, or something with the ROM.
I downloaded @leducbao 's Battery Stats Plus (shout out, that app is awesome. Got it free in his thread, then bought it on Play Store.) The data from it is too advanced for me to understand, I'm hoping someone can help me find the troubled process and freeze it. What it shows is umts_boot0 and xmm626x sucking up 87% and 86% respectively (I don't know how that's possible, but I don't really understand the data output anyway, so whatever) under the kernel wakelocks menu. The rest of the behaviors look fine to me.
Can anyone help with this? I just want to find and stop the processes draining the battery and use the tablet like a wifi model, without the cell functionality.
Thanks in advance.

Something is keeping your tablet awake when it should be in deep sleep in standby, install a wakelock detector app, also disable sync and any alarms.
Also the weaker your cell signal the more power you t705 transmitter will use, I don't have an cell data contract, so i set my phone to GSM as it gives me full bars.
John.

The problem does feel a lot like the cell radio is draining it, but I can't think of anything more to do than keep it in airplane mode. Is there a process you know I can freeze to stop it?

Android OS wakelock

Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx

raied115 said:
Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx
Click to expand...
Click to collapse
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.

htr5 said:
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.
Click to expand...
Click to collapse
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...

raied115 said:
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...
Click to expand...
Click to collapse
I'll tell you what I've done for battery life on my phone and maybe on of those will fix your problem.
1. Uninstall stock bloat (only the stuff actually running in the background; no need to remove stock launcher ect.)
2. Disable Wi-Fi scanning when wifi off
3. Use Amplify to limit wakelocks and alarms
4. Freeze the apps you don't regularly use. I have a titanium backup widget on my homescreen that will unfreeze snapchat and launch it. It is the pressed again to freeze it after use.
5. Greenify apps you don't want running in the background for no good reason. If you get the donate version, you can still get GCM notifications so it's win win. For apps that don't have GCM notifications, it will coalesce the notifications so your phone doesn't wake up as often.
6. Make sure you have all logging turned off from the LG hidden menu.
7. If you're on a bad wi-fi network run by work/school, then get the auto disable IPv6 app on the play store.
8. Use the HEBF Optimzer app to prevent Google wakelocks and battery drains.
9. Use PNF Root app on the play store to custom choose how often your phone checks for GCM notifications.
With these changes, I finish the day with around 4 hours of screen on time doing regular things. Don't believe the posts about 7-8 hours SOT because you don't know what they were doing. I once used my phone as a timer while studying and had the screen on for 3 hours and only drained 12% battery.

absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.

kakaovnik said:
absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.
Click to expand...
Click to collapse
Try clearing the Google Play Services data, then removing all Google accounts and then adding them back. This time, make sure not to agree to any data collection.
When you turn GPS on, it should show as GPS only in the location settings. Disagree to any prompts.
If your location defaults to high energy GPS and networks, then try flicking the toggle on and off very quickly after you have cleared the play services data. This is how I got the prompt for data collection to come back. It's annoying and you have to always disagree but it fixed my mysterious battery drains from android os.

High held awake time and battery drain

So my battery on my phone seems to suck... I just made a full wipe clean install of ICE Rom 3.5.0 with cleanslate kernel, balanced pnp profile v. 22, magisk root and got a whooping battery loss of around 30 percent overnight!
I was using stock before and had around 20 battery loss overnight, which sucks and is the reason i wanted to try a custom rom.
My phone is already 4 months old and I did a battery diagnosis, which ended with 94 percent (which is good right?).
Can anyone please help me?
I don't have Facebook or Facebook messenger installed, turned of WiFi and Bluetooth Scan and Location Services.
And I'm using Greenify, although I didn't greenify any apps yet
Here is a link with Screenshots h t t p://m.i mg ur.co m/a/xk9A8

RyuHayabusa710 said:
So my battery on my phone seems to suck... I just made a full wipe clean install of ICE Rom 3.5.0 with cleanslate kernel, balanced pnp profile v. 22, magisk root and got a whooping battery loss of around 30 percent overnight!
I was using stock before and had around 20 battery loss overnight, which sucks and is the reason i wanted to try a custom rom.
My phone is already 4 months old and I did a battery diagnosis, which ended with 94 percent (which is good right?).
Can anyone please help me?
I don't have Facebook or Facebook messenger installed, turned of WiFi and Bluetooth Scan and Location Services.
And I'm using Greenify, although I didn't greenify any apps yet
Here is a link with Screenshots h t t p://m.i mg ur.co m/a/xk9A8
Click to expand...
Click to collapse
What email app are you using? How have you got it synced? See how many times it wakes your device using Gsam or some similar app. This was my battery drainer (I use Bluemail). Anyway, check that out first.
20% battery loss overnight is horrible. Something is not set up correctly or is misbehaving.
Reboot your device and let it set for 2 minutes. Now go to System/Settings/Developer options and select Running Services. Everything look OK there?
I cant see your screenshot.

comstockload said:
What email app are you using? How have you got it synced? See how many times it wakes your device using Gsam or some similar app. This was my battery drainer (I use Bluemail). Anyway, check that out first.
20% battery loss overnight is horrible. Something is not set up correctly or is misbehaving.
Reboot your device and let it set for 2 minutes. Now go to System/Settings/Developer options and select Running Services. Everything look OK there?
I cant see your screenshot.
Click to expand...
Click to collapse
Here they are again - does this work?
I somehow can't directly upload images and can't post direct links...
imgur.com/a/q1bWX

Have you tried flight mode? and use WiFi only?

Haldi4803 said:
Have you tried flight mode? and use WiFi only?
Click to expand...
Click to collapse
Yes, I lost the same amount although I had the phone in flight AND extreme energy saver mode...

I'm facing the same problem after i updated my Firmware to 2.28.617.6. My Battery Usage show 45% of ANDROID OS an 39% of ANDROID SYSTEM, I'm already tried Viper 4.1, 4.3, 4.5, 5, 5.1, all with the same problem.
I updated firmware using RUU.exe, and i already updated firmware again to 2.41.401.3 with RUU again. Same problem
I realized the problem is not with rom, all of then, stock or custom, show the same situation. Its a firmware problem with Nougat
My phone is a Unlocked version, with S-ON
Any help?

I would perform a full wipe (+data!). Reinstall your Rom freshly, and the problem should be gone.

RogerF81 said:
I would perform a full wipe (+data!). Reinstall your Rom freshly, and the problem should be gone.
Click to expand...
Click to collapse
I'm already did that, all ROM's installs i did with a clean install.
With no one third app installed, the problem persists
i'm already tested turn of wifi, bluetooth, location, put phone on save battery mode, restart all permissions
Nothing helped
The main question is thats something who did not let phone enter in deep sleep

Yeah I've got the same problem with Android OS and Android System (the wakelocks are HVDCPD_WL and NETLINK) keeping the phone awake and preventing deep sleep almost 100% of the time, which is absolutely killing my battery life.
Frustratingly, the problem is not solved with a full wipe + reflash of any ROM. I originally had the problem sometime after the stock 7.0 OTA upgrade, at which point I unlocked the boot loader, flashed Maximus HD, then the problem went away for about a month until just returning a couple days ago. I've tried flashing the latest Maximus HD, Viper, but nothing is fixing it so far.
I bet it's some kind of hardware issue. I'm almost at the point of giving up and getting a OnePlus 3.

Just sharing my experience: I tried every Sense-based ROM I could find, problem of phone not going to sleep persisted. Even tried RUU to latest 2.41.617.3, which of course wipes absolutely everything - same problem, phone not going to sleep. As last ditch attempt, flashed the LineageOS Jan 28th nightly, and the problem is gone. Phone sleeping properly and battery life is back to normal. Not sure if coincidence or what... Going to stay on Lineage for a while as it works pretty well, but will go back and try Sense again in a couple weeks maybe.

This issue started to affect my phone while still on Marshmallow, around 3 weeks ago. It felt like it started after updating an app. This is what prompted me to update to Nougat. However, the issue persisted, even with full wipes, and even with LineageOS installed.
Moving from stock ROM to LineageOS has reduced battery drain from 10% per hour, to 5%.
Airplane mode and battery saver mode makes no difference to the drain. Neither does any WiFi and GPS setting changes - I have already read about a few possible "causes".
Perhaps the only option is S-OFF and re-flash all partitions of the phone?

veilsides2000 said:
This issue started to affect my phone while still on Marshmallow, around 3 weeks ago. It felt like it started after updating an app. This is what prompted me to update to Nougat. However, the issue persisted, even with full wipes, and even with LineageOS installed.
Moving from stock ROM to LineageOS has reduced battery drain from 10% per hour, to 5%.
Airplane mode and battery saver mode makes no difference to the drain. Neither does any WiFi and GPS setting changes - I have already read about a few possible "causes".
Perhaps the only option is S-OFF and re-flash all partitions of the phone?
Click to expand...
Click to collapse
Running a RUU would be your best option. This will wipe the phone and restore the stock ROM (system, firmware, etc).
Have you looked at wakelocks or app usage to see if there is any unusually high usages? I had a problem with my 10 awhile back that ended up being a particular version of Google Play Services. Usually these issues can be traced to a particular app or setting, it's just a matter of knowing what to look for.

Ohio wake_lock and no deep sleep. Same issue after reflash ruu, lineage, viper... on all roms same issue and no deep sleep. I think it's hardware issue. I try to flash elementalx kernel and it fixed problem for a day, one day only. Worst phone ever for me.

RyuHayabusa710 said:
So my battery on my phone seems to suck... I just made a full wipe clean install of ICE Rom 3.5.0 with cleanslate kernel, balanced pnp profile v. 22, magisk root and got a whooping battery loss of around 30 percent overnight!
I was using stock before and had around 20 battery loss overnight, which sucks and is the reason i wanted to try a custom rom.
My phone is already 4 months old and I did a battery diagnosis, which ended with 94 percent (which is good right?
Click to expand...
Click to collapse
How do you make a battery diagnosis?

Hi, since about a month I've been having the same issue, the kernel HVDCPD_WL and NETLINK wakelocks are keeping the CPU in use and consuming the battery charge at a rate of about 10%/hour. Has anybody got any new info on this? I read of someone that claims of having fixed it by cleaning the usb-c port, but in my case it doesn't seem to make any difference.