Let me preface this by saying I'm not complaning about battery life as 36h is very good. That said, I feel like my phone is awake much longer that it should be. Anyone have any ideas why my Awake time is so much higher than my Screen-on time?
Once again, I'm not complaining but considering my phone was awake almost 5x longer than the screen was on, I feel like I could squeeze some more life out of the phone. I had 1 exchange account @ 15min, 1 gmail on push, no talk/g+, ~2-3 hours off wifi (4g), gps on, bluetooth off, 4.0.4, leanKernel.
When analyzing the wakelocks, I don't see anything that would explain almost 6 hours of extra awake time:
Considering most of this charge I was on wifi, I think I should have been able to achieve more than 1.5h screen-on time. Especially when I see people getting 4-5+ hours on theirs. What could be causing this seemingly excess awake time?
Since those screen shots, I've done another full cycle and here are my results. Same settings as before. It looks as if I did a bit better with the ratio of awake vs screen on, but I still only got ~20 hours. I'll admit, this had much more 4g time and heavier usage.
As you can see it's better, as it was only awake about 3x as much as the screen. You can see where I was at home in the second screenshot (The long bar of wi-fi) and that included me sleeping yet it shows that the phone was consistantly waking up overnight without any usage. Short of "email", I'm not sure what could be causing it. I got MAYBE 3 e-mails overnight.
Signed out of talk/g+/latitude
Location services was NOT disabled in either set of screenshots. Disabled it and charging now. Maybe that will help?
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
armanatz said:
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
Click to expand...
Click to collapse
I have attached all the wakelocks to the previous two posts. I didn't attach CPU spy but I did check it every time. Usually it's between 60-80% but most often it's >70% in deep sleep.
Just did a fresh wipe with a app restore using the market. Location services have been disabled. I have uninstalled all gMaps updates and disabled the app. Is this good enough? Should I convert to user and uninstall using TB?
Just wanted to chime in and say I'm seeing a very similar profile to what you posted. And I'm not entirely sure, but I think this started when I flashed this ROM. What I feel like I'm seeing is that active use of the phone seems to be more of a drain than it used to, but I'm not sure how much of that would be placebo (i.e. remembering when I first got the phone around the holidays and there were a lot of relaxed days at home with constant wifi).
But right now I'm seeing 5.5 hours of awake time and 1 hour of screen on time, with 27% remaining. Total time is 42 hours, which seems to round everything out to a decent battery life, but again, 1 hour of use for 70% of the battery seems lower than what I remember. Not sure if a vote for seeing the same behavior is one for this being normal or us both having the problem, but I can try to post screenshots/more detailed info later if it would help.
This is on the above linked rom with stock kernel, 4.0.4 radios.
That's the same ROM I'm using and I agree, 70% usage for 1h screen time seems too much. I've seen people get over 2.5h screen on time on pure 3/4g
I'm going to see if disabling maps and location services help. Will report back.
I would be interested to see any SS you have, might help.
Sent from my Galaxy Nexus using XDA App
This is after a fresh wipe, fresh kernel install, no maps, no g+, no gTalk, no GPS, no location services, just gmail and 1 exchange @ 15 minutes
Any advice as to what's going on would be very helpful. Thanks in advance.
I also have a problem with wake-locks.
Since phone is relatively new ~2weeks its still stock 4.0.2 GSM. After some time my battery life fell and thanks to XDA i think i found the problem Google backup.
I disabled Google backup to see if i get the same awake time tomorrow.
If the problem doesn't go away, is it possible to resolve this problem without factory reset of the phone?
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
JoeSyr said:
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Click to expand...
Click to collapse
This looks to me like some sort of Maps issue. Try to uninstall/disable maps and see if it goes away. Looks like it's stuck trying to locate you with maps somehow based on those wakelock names.
Catoss said:
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
Click to expand...
Click to collapse
Hopefully the factory reset will fix it, that is an odd problem.
It seems to me like my problem was the version of leankernel I was using. I went from 10.0exp2 to 2.01exp2 and it's much much better
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Timdor said:
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Click to expand...
Click to collapse
mine is opposite of that, i standby fine on data but terribly on wifi. im guessing that is background syncing. i just have to figure out what is doing it
i have my wifi set to never too for better battery life. It seems counter intuitive, but wifi is better on power than 3g/4g. So preventing the phone from leaving wifi back to cellular is better for battery. All my phones have been like this.
yeah thats what i thought it does but mine drains faster on wifi...i leave it on cause i barely get signal in my room an if i sit on 3g it just takes a long time to do anything
What type of drain do you get over 3g vs wifi?
Yesterday I was playing around on 3g all day and I was seeing an average of 6%/hr. My phone is consistantly awake 20-25% of the time according to betterbatterstats. Screen on will always be far less than half of my awake time. Wifi drains around 1%/hr
I did a wipe of my 4.0.4 install and flashed a fresh kernel download. I'm not logging into exchange because, for some reason, I think that's my problem.
Also, changing to Never didn't really fix my issue.
Hey all,
I have a rooted Desire Z, that's almost 2 years old. I had been using the Virtuous Sense ROM for the most part and had been quite happy with it. Recently, I figured it was time I switched to ICS. So I flashed the Andromadus Mimicry ROM and have been loving it ever since. My only gripe with it is the battery life. I have been meaning to test it out extensively before I could bother the DEV with my nooby queries, but haven't had the time to do so.
When I check Settings > Battery, the screen always seems to be using up most of the %. I have searched through the forums and have done the following, in addition to a few steps that I could think on my own -
Re-calibrated Battery Stats
Clear cache & devklik cache fortnightly
Brightness - Set to 20% (No Auto)
Set to dim after 30 seconds
No render effects (ROM specific I think)
Animations are On.
No Bloatware Installed (Facebook, Twitter, Chrome, etc)
Sync is Auto (I need this)
Froze Google Maps and few other unnecessary background apps that I rarely use with Titanium (using Watchdog to monitor what was eating up CPU)
Disabled Google Backup
Wifi is always Off (I have to depend on 3G for my connectivity needs)
No Battery Saving Apps or Auto Kill Task Managers installed.
News & Facebook widgets set to manual update.
V6 SuperCharger with stock Services.jar.
CPU clock runs @ 245 Mhz on idle, which is most of the time.
GPS is always Off
Google's Location Service (Wifi & mobile network) is On.
Coming to the point, last night the phone was fully charged to 100%. I decided to turn Airplane mode On before I went to sleep to figure the drain in the absence of networks. Woke up to find 78%. That's 2.2% per hour. I checked Better Battery Stats and it seems the phone was awake for the whole ~10 hours. The culprit seems to be GPSLocationProvider. Note that the GPS is Off ; so this has to be the Google's Location Service (Wifi & mobile network)? Disabling this would be inconvenient because it's needed for Weather, and a few other things.
I'm attaching the screens, because I'm pretty new to this and would like to see what people who know more than me have to say about this. A drain of 22% in Airplane mode isn't normal and is crazy, right? Or perhaps,it's time to get a new battery?
PS: The battery has drained a further 20% since the time I took the screenshots, while I was typing this. I merely used the phone for a few messages and to check my mail. (see second-to-last vs last screen)
Radio - 12.56.60.25_26.10.04.03. Signal Strength is usually ~ -89dBm. I have noticed people claiming that the .19 radio is quite battery-friendly but I live in India, so I had to go with the WWE radio that seemed the latest. I didn't think it'd work here. Perhaps I'm wrong?
Any insights offered would be greatly appreciated.
It's an app calling the location services api. Try disabling Facebook and/or whatsapp and see if that helps. I'm unfamiliar with either of those apps, but I've heard nothing but bad things about the Facebook app, so that would be the first one I'd remove to see if it helps.
This goes without saying but of course make sure you've done a full wipe of /data since coming from your old rom. Hope that helps. I'm currently sitting at 12 days since my vision has been unplugged in airplane mode (radio off, wifi off, etc).
Sent from my SAMSUNG-SGH-I747 using xda premium
GPSLocationProvider - Reboot to Fix.
Thanks for your input, blk_jack. I did do a full wipe before migrating. As suggested in your ROM's OP, I don't use the Facebook app. The Facebook entry seen in the screenshot belongs to the Facebook Messenger app, which might partly be the cause. Upon further searching, I found that many people have been complaining about this issue on many different flavors of ROMs (ICS / JB) and hardware (HTC, Samsung, LG). Let me elaborate.
Searching for 'GPSLocationProvider' brings a ton of threads about this issue. I will post here whatever I could gather from these posts, for the benefit of others who face this.
Some people get this wakelock if they use GPS for anything and then turn it off. For example, if you turn on GPS, use a map application for a short while, close the map application and turn off GPS, the wakelock is born. Even if you kill any active map services, it will still be there and ends up draining your battery.
It seems to be chiefly caused by apps that use Location such as Google Maps, Facebook, Facebook Messenger, etc. Turning off all location services is advisable.
In some cases, the GPS does not turn back on until the phone is rebooted but that is not the case in this ROM. GPS works when turned On.
To get rid of the wakelock caused by GPSLocationProvider, rebooting seems to be the only working option as of now.
There is a step-by-step instruction guide (written by Karpfenhai) in the [APP]BetterBatteryStats thread OP, that deals with configuring autostarts, which apparently fixes this issue. I'm yet to try it, so I can't comment if it works or not.
I wish I'd been smarter and searched for 'GPSLocationProvider' instead, before creating this thread. Thanks for your time, anyway.
Screen Off Widget/Shortcut on Desktop?
@blk_jack
If I may use this opportunity to ask you something else related to your ROM.. I just found out that I don't have 10 posts yet, so I can't post it in the ROM thread.
Is it possible to create a widget/shortcut on the desktop to turn off the screen, perhaps by using the Launcher Activity options? I am currently using the one that's there in the Notification Drawer (Power Widget), pulling it down each time to turn the screen off is a tad inconvenient. The desktop Power Widget doesn't seem to have the Screen Off option. Is this possible at all without having to use an external app?
Yep, I have a nova launcher gesture set to run the root app killscreen.apk (search google).
You could add that app to your home screen too.
Sent from my SAMSUNG-SGH-I747 using xda premium
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
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.