Related
I have my phone running 99.6% of the time in spare parts and it shows android system as the culprit holding a partial wakelock.
so my question is, how do i fix this? i've tried a factory reset three times, am updated to 1.21 ota and have slowly started to reintegrate apps but it always starts again and always after a different app.
i'm getting pretty frustrated anyone got any ideas?
UPDATE In my case it was network time abusing wireless location service that was causing the problem and hence the reason a factory reset didnt solve it, i switched off network time and voila!
just to clarify, no live wallpapers, and phone is in airplane mode to avoid any data usage drainig the battery.
i have got beautiful widgets homescreen small clock and pure cal widget installed at the moment but even when i uninstall them it doesnt fix it, also im running launcher pro 0.4.2 but also had the problem when i reverted to sense.
and i have read every other thread here about battery life that i could find but no-one seems to have this problemo
anyone with any advice on why my phone wont sleep?
A long shot, but go in to Mobile Settings and untick Enable always-on mobile data.
Philosoma said:
A long shot, but go in to Mobile Settings and untick Enable always-on mobile data.
Click to expand...
Click to collapse
ok cool, giving that i try now but i had been leaving it in airplane mode to try and take the vagaries of data out of the equation.
this started about a week ago and i really noticed it when i was in a 6 hour long meeting and my battery basically draines 60% even though the phone was in airplane mode
ok tried that but with my phone just factory reset, airplane mode and no apps installed other than spare parts it's showing running 94.1 % of the time and all of it is android system.
that cant be right
i have restored data, maybe i shouldnt restore data either but that just seems plain crazy
Re: Android system - partial wake lock
What exact foreground and background processes/services do you have running when this is happening, any idea?
Apps like System Panel can show you them and some useful other details. That is certainly too high.
-------------------------------------
- Sent via my HTC Desire -
th3 said:
What exact foreground and background processes/services do you have running when this is happening, any idea?
Apps like System Panel can show you them and some useful other details. That is certainly too high.
-------------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
ok right now there is
com.android.syncml.service
sense
market
messages
people
rss reader
syncml provider
sys panel
touch input
updater
and then a load of inactive cached applications
do you see anything unusual there?
ok so i downloaded system app and killed all apps except excluded and sytem apps and my running usage has gone down, now thats no suprise in and of itself but now i need to see if it stays down.
i've just checked again and the percentage is still going down, so it's either an inactive app which i didnt list ( is that even possible if its inactive) or one of the items i listed above.
has anyone got any thoughts.
What do the logs say upon going to standby? (Use aLogcat to watch/save system log).
I had same problem I tried the turning off network always on to off, didn't change anything. the thing that worked for me was turning off my flickr account!? For some reason it kept my calendar awake so keeping system from sleeping, don't ask me why as I can't figure it out, though since doing this I'm now getting up to 2 days of average use from the battery. Also I've done the usual of reducing the different accounts sync timings etc.
Have you typed *#*#4636#*#* into the phone key pad to look at what is happening? This can give valuable info on what's draining the battery.
Jazd71 said:
I had same problem I tried the turning off network always on to off, didn't change anything. the thing that worked for me was turning off my flickr account!? For some reason it kept my calendar awake so keeping system from sleeping, don't ask me why as I can't figure it out, though since doing this I'm now getting up to 2 days of average use from the battery. Also I've done the usual of reducing the different accounts sync timings etc.
Have you typed *#*#4636#*#* into the phone key pad to look at what is happening? This can give valuable info on what's draining the battery.
Click to expand...
Click to collapse
I have the same problem as OP since the latest update. The *#*#4636#*#* code is not helping in this case. The partial wake lock is displayed as Android System - which doesn't tell me anything.
I read something about the Calendar issues but I am unable to stop the calendar in running processes.
How did you solve your problem?
ferus said:
I have the same problem as OP since the latest update. The *#*#4636#*#* code is not helping in this case. The partial wake lock is displayed as Android System - which doesn't tell me anything.
I read something about the Calendar issues but I am unable to stop the calendar in running processes.
How did you solve your problem?
Click to expand...
Click to collapse
Ok i seem to have had some luck since last night though i'm not sure of the exact reason.
i did as th3 said and downloaded system monitor and then killed all background active and inactive tasks and that seems to have solved the problem. I have no idea why that would be the case though and i am watching it carefully to see if it stays fixed.
i dont have a flickr account setup
djet said:
What do the logs say upon going to standby? (Use aLogcat to watch/save system log).
Click to expand...
Click to collapse
Djet, I installed alogcat and have found all references to wakelock, rather than post the entire log
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0)
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0)
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'keyguardWakeAndHandOff' activated (minState=0)
D/PowerManagerService( 77): wakelock: FULL_WAKE_LOCK 'keyguard'ACQUIRE_CAUSES_WAKEUP activated (minState=3)
there are also some entries in red like this one
E/vold ( 53): Unable to lookup media '/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001'
and a load of errors to do with global search etc but this is all pretty much gobbledegook to me, what am i looking for?
thanks
ok so based on that log i have switched of the use wireless networks to find my location (not gps i hardly ever use that anyway) and now the running % is dropping fast.
i will keep you posted as to whether it keeps coming down or not.
it is going to be an enormous bummer if i cant use wireless location, thats one of a smartphones greatest powers, why would this suddenly start happening now ( started about a week before the ota update) and continues even when i factory reset.
kinkade said:
ok so based on that log i have switched of the use wireless networks to find my location (not gps i hardly ever use that anyway) and now the running % is dropping fast.
i will keep you posted as to whether it keeps coming down or not.
it is going to be an enormous bummer if i cant use wireless location, thats one of a smartphones greatest powers, why would this suddenly start happening now ( started about a week before the ota update) and continues even when i factory reset.
Click to expand...
Click to collapse
I suppose it's not the feature itself guilty but the applications using it. I had the same issue with battery running out because of Location service wake locks. It turned out one of the Locale app plugins was abusing this service. Having it uninstalled battery run became normal.
djet said:
I suppose it's not the feature itself guilty but the applications using it. I had the same issue with battery running out because of Location service wake locks. It turned out one of the Locale app plugins was abusing this service. Having it uninstalled battery run became normal.
Click to expand...
Click to collapse
Yes i know what you mean, how did you go about diagnosing that? also i have done several factory resets and it still happens
Re: Android system - partial wake lock
There are a many app settings that drain battery and the stock setup is nothing I am fond of. Location/locale was one of them for me, calendar, network time and widget/app syncs being the others. A non-stock app causing such problems was NetCounter.
Calendar was fixed by killing it and restarting it. It's a known bug for many.
If many widgets are running sync very often, then you can imagine battery draining fast.
-------------------------------------
- Sent via my HTC Desire -
th3 said:
There are a many app settings that drain battery and the stock setup is nothing I am fond of. Location/locale was one of them for me, calendar, network time and widget/app syncs being the others. A non-stock app causing such problems was NetCounter.
Calendar was fixed by killing it and restarting it. It's a known bug for many.
If many widgets are running sync very often, then you can imagine battery draining fast.
-------------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
th3 you are legend, it was network time, i switched that off and all is now well in the world. cheers dude
Good find. I had the thing off anyway, but it is good to know.
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
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.
I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
bosox284 said:
I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
Click to expand...
Click to collapse
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it ?
Badger50 said:
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it
Click to expand...
Click to collapse
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
I wouldn't worry about turning off AOD saving you a bunch, I turned mine off and didn't notice any diff at all in overnight batt drain, so set it to DIM, and still haven't noticed any additional batt drain from when it was off.
If you really want to be a miser without totally losing AOD,
"always on" OFF,
"Lift to check phone" ON,
(Settings>Display>Ambient display>)
set it to DIM (Settings>Display>Screen Saver>Current Screen Saver gear>Night mode checked)
which is how mine is set up
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
Where is that fix touch module?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Where is that fix touch module?
Click to expand...
Click to collapse
Look in downloads in magisk manager.
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
bosox284 said:
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
Click to expand...
Click to collapse
Delay what? ?
Badger50 said:
Delay what? <span class="emoji-outer emoji-sizer"><span class="emoji-inner" style="background: url(chrome-extension://immhpnclomdloikkpcefncmfgjbkojmh/emoji-data/sheet_apple_32.png);background-position:73.97179788484137% 79.9647473560517%;background-size:5418.75% 5418.75%" data-codepoints="1f914"></span></span>
Click to expand...
Click to collapse
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
bosox284 said:
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
Click to expand...
Click to collapse
Haven't noticed any delay what so ever with any push notifications from any apps. Google or otherwise :good:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
I noticed this as well and it seems to have started after the January update. Although mine isn't quite as bad. Pre-January update I was losing about 2-3% in like 8 hours. I'm now losing that much in like 4-5 hours. There were 2 days in a row where I actually lost like 15-18% over like 7 hours.
rickysidhu_ said:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
Click to expand...
Click to collapse
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
The Jan update has been ****. I would get almost 7 hrs SOT with 20% left. Now all I get is ****ty 4 hrs and phone at 10%. Usage wise it's the same since day 1 nothing new as such. No rogue app on BBS. This is messed up.
Badger50 said:
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
Click to expand...
Click to collapse
Yeah I had a feeling that could be it. I'll give it a shot by removing them, thanks for the suggestion! :highfive:
Badger50 said:
Look in downloads in magisk manager.
Click to expand...
Click to collapse
It isn't there that's why i asked
Sent from my Google Pixel 2 XL using XDA Labs
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Try to run "su" and then "top" from terminal,
See what is your top process,
In one occassion, my magisk hide stucked up and using 30%++ of CPU all the time, even when idle, and that drain the battery in no time,
Am on 8.1 Jan, Kiriskura Kernel,
Tweak applied is Brevent, Amplify and my own EnableDoze for GMS.
Never lost more than 5% in 9 hours of sleep. Average is 2-3% with wifi on. Less than 2% when network is totally off
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
You can try the one attached.
I cant find it in download section as well
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
My bad. I forgot that it was a special build by another user. Install it from magisk manager. If it doesn't install, then flash it in twrp.
https://github.com/AndroPlus-org/ma...b/master/magisk-module-fix-touch-pixel2xl.zip
I know this will be almost impossible to solve with suggestions, but some of my notifications don't come through until I unlock my phone. Most notably WhatsApp. I've turned off all battery optimisation options, removed it from the sleeping apps list, allowed background data and turned off data saver. Still have the same issue.
I have naptime installed so turned that off as well.
What's strange is that a few days ago all my notifications started coming through as normal for a few hours, and then stopped again.
I know the only way to solve this is probably a factory reset, but with loads of tweaks I've gotten it so my battery life is amazing. Leaving it overnight it drains around 3% and depending on how I use it I get around 8h of SOT with 50% battery left so I don't really want to factory reset.
What launcher are you using?
I feel your pain with factory resets.
There needs to be a backup settings to cloud so you can easily restore them after a reset or even a change of phone.
I understand your frustration with this issue, I experimented it as well when I started using my device, back then I did not fully knew about all the battery optimization settings, but, when trying to get all the notifications right, I stumbled upon an app named PNF-no root, which is meant to fix the push notifications from sms, email, whatsapp, etc, I tried so many things, that I honestly can not say if this PNF solved the issue, but in the end my notifications became normal, so, I kept using it, you can give it a try, that is, before you reset your phone, it might help
Do you at least move your phone? Because a lot of apps, to bypass the system's optimisation that put apps to sleep, is that their wake up workaround is gyroscopic based.
That's why WhatsApp and such use a lot the sensor while it has nothing to do about in the first place.
If a battery monitor works for you, you can check that for WhatsApp.
winol said:
I understand your frustration with this issue, I experimented it as well when I started using my device, back then I did not fully knew about all the battery optimization settings, but, when trying to get all the notifications right, I stumbled upon an app named PNF-no root, which is meant to fix the push notifications from sms, email, whatsapp, etc, I tried so many things, that I honestly can not say if this PNF solved the issue, but in the end my notifications became normal, so, I kept using it, you can give it a try, that is, before you reset your phone, it might help
Click to expand...
Click to collapse
Thanks I have installed it and will see if that works.
Nastrahl said:
Do you at least move your phone? Because a lot of apps, to bypass the system's optimisation that put apps to sleep, is that their wake up workaround is gyroscopic based.
That's why WhatsApp and such use a lot the sensor while it has nothing to do about in the first place.
If a battery monitor works for you, you can check that for WhatsApp.
Click to expand...
Click to collapse
Yes I've got it on me all day. It's never left anywhere for extended periods of time.
Nastrahl said:
Do you at least move your phone? Because a lot of apps, to bypass the system's optimisation that put apps to sleep, is that their wake up workaround is gyroscopic based.
That's why WhatsApp and such use a lot the sensor while it has nothing to do about in the first place.
If a battery monitor works for you, you can check that for WhatsApp.
Click to expand...
Click to collapse
Yes I've got it on me all day. It's never left anywhere for extended periods of time.
I've just installed a push notification tester app and my phone goes into doze immediately once I lock my phone and the screen turns off it seems.
If I request a notification, it comes through with the phone unlocked but if I set a delay of a few seconds and lock the phone before it comes through, nothing will happen until I wake my screen up.
Any ideas on how to solve this?
I worked out what the problem was!
I have a VPN that is set to disconnect when my screen turns off to save battery. At the same time I enabled the Android setting that blocks all connections without VPN. Of course when the screen turns off and the VPN disconnects, my phone was blocking all outside connections, hence me not getting any notifications.
Well, I am glad you figured it out