Develop 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

fire OS using most the battery, new update to blame?

The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.

Just to maybe assist you in finding the culprit I'm on 4.6.3 with google apps but no root. I've not experienced any wake locks. Perhaps clearing Google's cache and data?

Sorry I meant I was on 4.6.1 still. Will clear data and see.

adam.nox said:
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Click to expand...
Click to collapse
Probably one of those glitches that can be solved by a reboot. However, you can disable updates using hdxposed module for xposed if you want.

Done both of those things plus much more. Anyone else having this issue?

try taking a titanium backup of everything and then factory reset.. with everything backed up to your PC. then root and start restoring everything gradually.. start by social apps and call log and messages.. then your essential apps.. and see.. then add the rest of the apps bit by bit till you find the offending application or maybe something just got screwed will be fixed when the data clears..
just make sure there is nothing out of the norm in your essential apps, meaning they are all tried and tested by everyone.. facebook, whatsapp, keep, launcher.. that stuff. and also make sure in these apps to limit their ability to check every X minutes as they can really drain your battery.

I've disabled wakelock on anything that has reported to use it by wake lock detector that I don't absolutely need to have it. I've uninstalled any non-essential apps. I've done too much tinkering and have too much important app data to risk doing a reset when it may not work.
I need a way to actually get to the bottom of it first.
Why is google play services waking the phone 2000+ times per day? Wake lock detector says the phone has been awake 5 hours out of 10, but then the list of times for each app only adds up to 20 minutes. How do I find out what was keeping it awake the rest of the time?

Possibly some kind of location based frippery. Try removing location access from troublesome app. And turn off auto sync if it's on

Location services are completely disabled. Auto sync is off. Both have been since this started happening.
Used app quarantine to disable almost every app I put on here, and Fire OS is still 51%.
Possible culprits, though I'm not sure if I find it likely: Ultimate dynamic navbar, lightning chat, foscam viewer, google apps, xposed mods (have a few). greenify (that would be ironic), flixter, es file explorer, buildprop editor, calculator, jellybean keyboard, multi timer, skana battery alerts, nova launcher, power toggles, slacker radio, bank app, super user, terminal emulator, outlook, wakelock detector.

Get better battery stats from xda, it gives a better breakdown of wake locks.

Alright what should I look for in there?

Ok here is what I believe I have found out, using network log along with better battery stats.
The phone is waking up constantly due to netbios pings (I know not technically pings), from various computers on my network, mostly my main PC. I don't know why it's doing this. Could be one of many background processes. In my opinion, it shouldn't matter. The phone shouldn't be that stupid.
I was able to... I think, mitigate a lot of this by doing a few things.
The first is editing qcom's ini inside etc/wifi so that if it says offload, I put a 0, I assume it's offloading to the cpu, which causes it to wake for pointless crap. The second thing I did was re-enable optimized wifi. This is probably already on, on everyone else's phone. I turned it off because I was trying to figure out how to tether while connected to a vpn through the phone. Still can't get that to work. And I know how to, because I did it on my nexus prime, but something in the fire OS is f'ing that method up (iptable configs).
I'm considering seeking an app to turn off wifi when the phone sleeps, because better battery shows wifi on 100%, and even with the changes above, I was still responding to some netbios pings in the network (about 1/5th as many). I imagine most networks will have noise like this.
However, even after all this, fire OS is still the main battery draw. Better Battery doesn't account for all the wake time, not even by half.
For now I've put enough time into this.

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.

delayed notifications on Pixel 3 XL

Got my pixel a few days ago. Not receiving notifications in time drives me nuts. So usually gmail notifications appear on screen as soon as I unlock and wait or after about 15-30 minutes after I received an email. Sometimes longer for whatsapp No battery saver, no adaptive battery, optimizations are off for gmail. Also tried all permutations of those settings. Tried factory reset and Q up and downgrade. Nothing seems to work. Happens on wifi and cellular. Devices isn't rooted.

ryzion said:
Got my pixel a few days ago. Not receiving notifications in time drives me nuts. So usually gmail notifications appear on screen as soon as I unlock and wait or after about 15-30 minutes after I received an email. Sometimes longer for whatsapp No battery saver, no adaptive battery, optimizations are off for gmail. Also tried all permutations of those settings. Tried factory reset and Q up and downgrade. Nothing seems to work. Happens on wifi and cellular. Devices isn't rooted.
Click to expand...
Click to collapse
Since you are fairly new here in terms of posts, why not update your profile with at least your location and carrier. We don't need your exact GPS coordinates, but knowing what city/country you live in and which carrier you are using can be very helpful in diagnosing your problem. Others in your area may also chime in with their experiences if they see you are close by. If you are on an MVNO, then state exactly which one. To start with, how many APN's do you have for your carrier and have you tested any other than the default? Verify your APN settings with your carrier's web site, and fill in any that are blank or wrong. Was your SIM from your last phone, or did you get a new SIM from your carrier provisioned for your Pixel? You should not have to tweak your phone at all for the issues you are describing. Just some thoughts. Cheers.

ryzion said:
Got my pixel a few days ago. Not receiving notifications in time drives me nuts. So usually gmail notifications appear on screen as soon as I unlock and wait or after about 15-30 minutes after I received an email. Sometimes longer for whatsapp No battery saver, no adaptive battery, optimizations are off for gmail. Also tried all permutations of those settings. Tried factory reset and Q up and downgrade. Nothing seems to work. Happens on wifi and cellular. Devices isn't rooted.
Click to expand...
Click to collapse
I have the same issues. I just ordered mine from Google, unlocked.
Sim from Sprint, updated PRL. Doesn't matter.
Sometimes I don't get notifications from my "battery charged" app.
It is frustrating. I don't know the fix, and I haven't mentioned it here either.

What seems to work so far is disabling deep/light idle via adb:
$ adb shell dumpsys deviceidle disable
Deep idle mode disabled
Light idle mode disabled
Click to expand...
Click to collapse
This will be lost on reboot

scrap that, it's not working either way. Don't know what to do, it's unusable that way. Kinda need fast notifications for business

I have the same problem, but, only with certain apps. I'm on Verizon in St Louis, USA. I'm currently on Q beta, but, this happened on Pie at least since the start of this year.
Messages does this the worst. I'll get the message on the web app sometimes a couple minutes before it pops up on my phone. A REALLY funny one, when connected to my SUV via Bluetooth, a message will popup on its screen several seconds, sometimes more before it does on my phone. So, to me it seems like the phone is getting them right away, but doesn't send the notification immediately?
Now, Outlook on my phone I get them before they show on my work computer. So, thankfully I'm not getting delayed work emails, that could be bad considering I'm a sys admin.
I've noticed with some others, like Facebook or whatever, that if I wake up my phone, unlock it, or another notification comes in, all of a sudden I'll get some for those if there are any. In checking FB it's definitely a late notification.
I just turned off adaptive battery yesterday for other reasons, that hasn't helped. I wonder if it's one of the battery settings though that are somehow affecting it. Like the optimization for example. I don't know. It's REALLY annoying though. This plus the Bluetooth problems that Google can't seem to fix (but no other phone that I know about has these problems), I'm really starting to get pushed away here. If it weren't for day one updates, the camera, and things like that, I'd consider jumping ship...
If anyone figures this out, let me know! I'll keep digging too.

disable adaptive battery + exempt apps from battery optimization

virtyx said:
disable adaptive battery + exempt apps from battery optimization
Click to expand...
Click to collapse
Yeah... that was the first thing I've tried. Haven't found any solution still. Basically gmail notifications don't work. Old mails will stay as unread for half-an hour and vice versa. Pretty useless

ryzion said:
Yeah... that was the first thing I've tried. Haven't found any solution still. Basically gmail notifications don't work. Old mails will stay as unread for half-an hour and vice versa. Pretty useless
Click to expand...
Click to collapse
I noticed this for the first week after a clean flash then went back to normal
Might have something to do with the new battery management

So, I've been paying more attention to this, and, I've noticed something. Every time a notification doesn't come through, even though it pops up on my watch or my car, the tap to wake doesn't work. I wonder if the screen just isn't waking up for some reason? I'm not sure how that's controlled, so I don't know how one would fix it though.

Just wondering if anyone has figured this out. It is beyond ridiculous to have to wake up my phone in order for for a notification to come though. I am noticing this mostly with Gvoice and Gmail. My most frequently used and important apps. Connected to wifi 99% of the time as coverage is terrible in my area. All battery optimization is turned off. Also, it is intermittent. Most times things come through fine. For example. I woke up in the middle of the night and looked at my phone and I Gvoice message went off as soon as I woke it up. In this case the message was coincidentally sent right then, but that is the same behavior I have been experiencing when a message is delayed. Phone and watch are quiet, wake phone, suddenly my watch and phone go off with one or more notifications from one or more apps.

The one thing I have noticed is that push notifications get effed up for certain apps and I have to turn off app notifications, fully close app/clear cache, re-enable notifications and turn the app back on/reboot.

Delayed Whatsapp notifications

So I've been having this issue for quite some time, but i guess i got used to it so it didn't pose much of a problem untill now. All of my Whatsapp messages are delayed when screen off and WiFi on, and they come through from 2-4 all the way up to 20+ min after they are sent. As soon as i turn screen on, they pop up on screen.
I assumed that it was due to greenifys rigorous doze settings, so i uninstalled it. Some threads suggested Titanium backup may be culprit, so i uninstalled it too. I also added Whatsapp to battery optimization whitelist and ticked on run in background and unrestricted data usage, but with no success, and also completely reinstalling Whatsapp.
I even reflashed stock pie and oreo, but same thing happens. I suspected that deep sleep might be interfering with cloud messaging services, but even on stock pie device enters deep sleep even with WiFi on in minutes after screen off, so im pretty confused with it all.
I am running Pie v10.0.9.0.PLDMIXM with magisk, busybox, xposed, substratum, gravitybox installed. Apart from that there are no other apps interfering with the system whatsoever.
Any help would be much appreciated.

CrimosUmbro said:
So I've been having this issue for quite some time, but i guess i got used to it so it didn't pose much of a problem untill now. All of my Whatsapp messages are delayed when screen off and WiFi on, and they come through from 2-4 all the way up to 20+ min after they are sent. As soon as i turn screen on, they pop up on screen.
I assumed that it was due to greenifys rigorous doze settings, so i uninstalled it. Some threads suggested Titanium backup may be culprit, so i uninstalled it too. I also added Whatsapp to battery optimization whitelist and ticked on run in background and unrestricted data usage, but with no success, and also completely reinstalling Whatsapp.
I even reflashed stock pie and oreo, but same thing happens. I suspected that deep sleep might be interfering with cloud messaging services, but even on stock pie device enters deep sleep even with WiFi on in minutes after screen off, so im pretty confused with it all.
I am running Pie v10.0.9.0.PLDMIXM with magisk, busybox, xposed, substratum, gravitybox installed. Apart from that there are no other apps interfering with the system whatsoever.
Any help would be much appreciated.
Click to expand...
Click to collapse
It's the system power and ram management. That system kills the processes and doesn't allow them to revive for instant notification. Same happens with facebook and facebook messenger, not only watsapp. Instagram does this also. I receive a follow notification on my iPhone and the notification appears on the Mi A2 Lite only after the screen is on and unlocked.

TheoXSD said:
It's the system power and ram management. That system kills the processes and doesn't allow them to revive for instant notification. Same happens with facebook and facebook messenger, not only watsapp. Instagram does this also. I receive a follow notification on my iPhone and the notification appears on the Mi A2 Lite only after the screen is on and unlocked.
Click to expand...
Click to collapse
Oh i see. i totally get that over agressive ram managment, because even with 4 tabs open, it kills them very soon, to a no avail have i tried to fix it, it seems to be rooted issue...
Do you know any possible fix or workaround for this? Maybe to convert these apps to privileged, e.g. system apps or something? There must be some kind of solution for this.

CrimosUmbro said:
Oh i see. i totally get that over agressive ram managment, because even with 4 tabs open, it kills them very soon, to a no avail have i tried to fix it, it seems to be rooted issue...
Do you know any possible fix or workaround for this? Maybe to convert these apps to privileged, e.g. system apps or something? There must be some kind of solution for this.
Click to expand...
Click to collapse
Nope. Some said that this is purely Xiaomi's fault. But no. I have another Allview phone doing the exact same stuff. This may be an unmodified kernel for the said chipset. Companies like Samsung, Sony, HTC etc. may edit that kernel to be more mild, while Xiaomi, to reduce the costs doesn't.