Related
Hi all,
After instaling OTA 1.72.405.3 the android system is eating away my battery like crazy.
After 5 hours my battery was down to 29% (71% was used) and the android system was responsible for 60% of this. In my CurrentWidget log I can see that (with the phone in standby) it uses ~130 mA to ~160 mA.
Does anybody know what is going on or can anybody help me by telling how to find out what is going on?
[edit: If you have the same problem, please post a reply so we can find out if this is a big problem! Thx]
This happened to me yesterday! Found out that the system process had pegged out the CPU @ 100%
I couldn't fix it, and in the end restored to factory settings. Has been OK today but I killed the battery in about 4 hours.
Radio and kernel updated?
Sent from my Desire HD using XDA App
yes, i have the same problem! i posted another thread about it (titled constant sync after OTA update) as i first noticed the issue when the sync icon was always being displayed.
today my battery hit 20% after 6 hours with android system taking up 50% of the battery usage. its ridiculous!
if anyone has a workaround or a quick fix please post it up - this is untenable!
I have exactly the same issue, no problem with battery life before the latest OTA, and now the phone is dead within 8 hours with no usage, simply in the pocket with the display off.
Not happy at all, the phone is virtually unusable at the moment as any action accelerates the drain.
Strange! My phone is now with more battery life, after the update. It is SIM free ...
Sent from my Desire HD using XDA App
I posted this in another thread -
There seems to be a bug in the update for anyone who had HTCSense.com sync'ing turned on. Either disable all sync'ing for that and / or sign out of that account. It was consuming 100% of my CPU cycles and keeping the processor at the 1ghz mark. Once I disabled the HTCSense.com sync and rebooted the phone, all is good. I went from 100% CPU usage to about 4% and less when idle.
Personally, I'm not sure about HTCSense.com anyways. Way to buggy. I have all my SMS's backed up with SMSBackup+ to my Gmail and my contact / calendar is on Google. I've Wave Secure to lock down the phone if needs be / to find it. I think it's more reliable as well as I used to get a lot of "can't connect to the phone" on HTCSense.com and Wave secure uses at Text Message based system to activate the necessary features along with locking down the phone if the sim is removed / replaced! NICE!
Anywho, anyone who is having battery problems / finding the CPU is topepd at 100% try the above and see!!
Click to expand...
Click to collapse
I followed up with this:
I must say, I'm quite impressed with the battery life since the update (after I got rid of the 100% CPU bug).
I plugged the phone out at 11am this morning. Quite heavy texts (50+ sent today and at least that received). 10+ calls (incoming and out going) at 3-10mins each. Some Angry Birds, Some Market Updates. Disconnected my Facebook Acc and reconnected to cure a bug in the calendar (facebook entries were there twice), so all that data had to reload. Twitter usage through out the day. WiFi on all day. GPRS Radio only.
Now at 12.15am (so over 13 hours later), I've still got 50% Battery left! I would NEVER have gotten that previously. Not with the heavy use I gave it today.
How are other people finding it!?
Click to expand...
Click to collapse
tony_reilly said:
I posted this in another thread -
I followed up with this:
Click to expand...
Click to collapse
Thanks for that. I dont really use any of the sense features myself so i've now disabled sense syncing completely and will see how it goes (once its fully charged again!). will keep this thread updated with any news from my end in any case.
I did notice the sync logo was up quite a bit... interesting!
Mine did it randomly... couldn't clear it so just went for factory reset which appears to have fixed it!
May turn of HTCSense however if it is likely to be causing problems...
I got the same Battery problem after new OTA and Im going crazy! What can I do? My battery lasts only about 4 hours now!!!!!!
Should I factory reset and wipe everything???
As ive posted in a few other threads i went into stock application manager and force closed everything i could to do with google, htc , friendstream, maps, facebook etc. After that my cpu 100% problem stopped, has never returned and battery life has improved compared to before the update.
Sent from my Desire HD using XDA App
I have disabled now HTCSense.com sincronization. I will see how this works tomorrow for me. I will let you know guys
I had htcsense.com enabled but to be frank I never really used it much...
disabled its syncing (every 3 hours I had set), rebooted, still had "android system" at ~65% and htc sense running at about 15% (tell me, I use launcher pro 99% of the time, is there any way to actually kill the sense ui? I swear its in the background)...
This did nothing, I tried actually removing the account, and even before a reboot the proc. usage dropped down to about 15%, which was apparently being used by the monitor I use (osmonitor). rebooted, let the phone settle, it did a sync, all seems well... So in my case an actual removal of the account was needed.
Try turning USB debugging on/off. I have it off after the last OTA and I have no /INIT problems. Maybe they fixed it...
I had the same problem, with the cpu running constantly at 100%. For me the solution was to remove the HTC Sense account, and then adding it again. After this the cpu usage dropped to normal.
well its been nearly 4 hours unplugged and i'm down to around 80% with around 30m of calls made and a dozen texts. not fantastic, but much better then before.
Did you try USB debugging? previously that has been mentioned as the CPU eater and battery hogger... just a thought..
javier24 said:
I have disabled now HTCSense.com sincronization. I will see how this works tomorrow for me. I will let you know guys
Click to expand...
Click to collapse
Confirmed. I had the same exact problem and removing HTC Sense account did the trick.
I tried adding it again, but the cpu drain started again..... so I'll use it for some time without SenseSync.
reelist said:
well its been nearly 4 hours unplugged and i'm down to around 80% with around 30m of calls made and a dozen texts. not fantastic, but much better then before.
Click to expand...
Click to collapse
well it seems i spoke too soon. i've just woken up to find that the battery died overnight. so sometime in the last 9 hours i've lost 80% battery whilst it has been on standby.
prateekgujral, i currently have usb debugging turned ON due to the /init problem. are you suggesting that i turn it off?
reelist said:
prateekgujral, i currently have usb debugging turned ON due to the /init problem. are you suggesting that i turn it off?
Click to expand...
Click to collapse
It should be on So its good.. What about the sync tthing dicsussed above?
Leaving my OP in place, but I have rewritten the description with much more detail and pics here
http://forum.xda-developers.com/showthread.php?p=25401417#post25401417
I suggest skipping to there.
I am looking for general tips here. E.g., not asking you to diagnose my specific problem so much as give me ideas of what else to check or try.
Lately I have had unexplained (to me) battery drain. Yesterday I lost about 25 percent in an hour while the phone idled. It is not a constant thing, though. I can go an hour and loose 1 percent then loose massive amounts in the next hour.
Now, i have searched, but I have not found anything that applies to me.
I have:
Tried a different radio
Tried a different kernel
Reflashed my rom
Phone is entering deep sleep according to cpu spy
There are no unusual or excessive wake locks according to better battery stats
No apps are using a lot of battery.
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Ideas?
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Zepius said:
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Click to expand...
Click to collapse
beren28 said:
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Click to expand...
Click to collapse
So I don't think I can blame it on that.
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
can you give us screen shots of battery stats?
Herman76 said:
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I do, and on reflection it is a possible culprit since I added it recently.
Didn't occur to me since it was producing no wakelocks and the battery stats did not showing as using much battery.
I shall turn it off for a bit and see if that helps. (unless there is some other way to test if it is the problem first.) I am off to the search button!
Zepius said:
can you give us screen shots of battery stats?
Click to expand...
Click to collapse
This is from yesterday when i set it down unused for about 90 minutes. The amount of wakes seems liek a lot, but it is similar to what i see when i have far far less drain, so I don't think that is the problem. I didn't get the app list screen, but out should screen as the only major drain with about 2 minutes.
I know it is shows poor signal strength, so immediately after that shot I put it in airplane mode, turned of sync, and rebooted. The battery continued to drain and graph had the exact same slope under those conditions. (Forget to get a pic though.)
Sent from my jitterbug using tapatalk.
System panel paid version with monitoring enabled is the best for tracking apps using CPU.
OK, still working on this.
To recap:
When the screen is off, and no apps are running I sometimes get inexplicable battery drain. This is occurring under conditions when I should be experiencing little or no drain at all. I say this becuase:
The screen is of and no bakground apps are running
the phone is NOT awake and IS entering deep sleep (as confirmed by cpuspy)
there are no unusual kernel or partial wake locks
there are no apps listed as using unexpected ammounts of battery
This is not a universal problem. The phone *often* behaves as expected. I can leave the phone off for an hour and see a 1% or 2% drain, and I am happy with that. However, sometimes, randomly, it goes nuts on my.
This graph from a few weeks ago shows what I mean. Look in the green box. The phone is sleeping, and the screen is off. The graph starts as a flatline, then, all of a sudden, it begins to drop precipitously.
Here is a graph that shows the battery dropping at the same rate whether the phone is awake or sleeping:
I have gone the following to try and narrow the problem down:
Done a completely fresh install of my Rom including a system wipe.
Tried two kernels (the aokp default and several relases of Franco's
Tried a different radio
Activated and installed a new sim card
I have come to suspect that the problem is network related. When the problem starts, sometimes going into airplane mode and back and/or toggling 2g only temporarily fixes the problem.
I suspect that something is happening with my connection to T-Mobile that keeps the network running and draining power. This is pure speculation, but it is all I can think of.
I installed juice defender (which I had not been previously running) and noticed the that, sometimes, it didn't turn of data when it should have. I also noticed the following two things happen:
I do not believe it is a rom problem, since if so, someone else would be reporting this. It might be an app problem, but if so the app is draining battery without a wake lock and while the phone is in deep sleep.
It is not exchange (as was suggested in this thread) since it continues when I ev my exchange account.
I have no idea what else to do or try.
Since it happens at random and takes a while to identify, uninstalling one app at a time to test for that could easily take months to narrow down a misbehaving app.
I know it is not a hardware issue since last month I got this:
That was with AOKP and Franco (earlier versions obviously)
I have google searched till my fingers bleed.
I am a long way form being an expert, and I suspect I may have overlooked something obvious.
Please, any thoughts??
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
derekwilkinson said:
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
Click to expand...
Click to collapse
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Here is that chart for last night.
I had about 1 hour and 30 minutes screen on time with 65% left when I went to bed. When I woke up, phone was dead.
RogerPodacter said:
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
Click to expand...
Click to collapse
Mine often does that. But sometimes it doesn't. It is the fact that it happens seemingly at random that makes it so annoying and hard to track down.
I would replace the battery
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
arw01 said:
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
Click to expand...
Click to collapse
The thought has occurred to me, but unfortunately, no, I don't have a friend I can swap with. And really, since I have had the phone less than 3 months, the battery *shouldn't* be bad, but yeah, defective products happen.
If I cannot find any other cause I will likely order a new battery and see if that fixes it.
beren28 said:
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Click to expand...
Click to collapse
1. yes battery calibration does make a difference.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"? Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
derekwilkinson said:
1. yes battery calibration does make a difference.
Click to expand...
Click to collapse
You are incorrect. But, in any case, I DID calibrate the battery just to cover bases in the case that I was wrong.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"?
Click to expand...
Click to collapse
We'll of course it can. That is kinda my point. If I go one app at a time waiting for it to "run a process at random" I am talking literally MONTHS of testing. I would have to wait many hours, if not days after installing or uninstalling an app to be sure whether or not it made a difference, then move on the the next. This is simply not an option. I started this thread in hopes that a realistic and doable solution might exist that I was unaware of.
Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
Click to expand...
Click to collapse
I am asking because there may be a solution that I am unaware of that doesn't require me to put my entire life on hold for months. It is possible that there is no such solution, but I asked in case there was one.
Sorry to have put you out so much.
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
skadebo said:
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
when i did a complete quote and re flash i did not setup the exchange account, but the issue continued.
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Sent from my jitterbug using tapatalk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
My battery also drains at a rate similar to yours however I'm on the CDMA version. Hopefully you can figure out what's going on with yours.
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
I've just changed from a Gear Live to a Moto 360 and after charging and syncing the battery died after three hours! Horrendous. Someone please advise! My gear Live with the same settings never did this.
Hi,
I just received a Moto 360, and I know what you're going through!
I've gone from 3 charges a day previously, and today the watch is reporting I have almost 2 days remaining of charge.
First, FULLY cycle the battery. Leave it on the stand over night, run it until it turns off (if you're in a rush, ambient display, full brightness!). Then, full charge to 100% and leave it for an hour on the charger once it is full.
After that, do a factory reset on the watch (in settings). In Android Wear on phone, use the settings menu to resync your apps.
Do one more full discharge and full charge, and you should be sorted.
If not, use the Watch Battery section of the wear app to identify problem apps. Before today, I had never seen a "watch idle" entry, because an app was holding the watch awake. Identifying and removing that app has solved the rest of my problems.
Hope all this works. Some of the steps seem/may be unnecessary, such as the factory reset, multiple full charge cycles. However, I speak from experience that they do work!
Edit: Do be aware that the charge cycles where you do a factory reset and sync will drastically drain the battery, giving the illusion that the problem is still there.
chrispy_212 said:
Hi,
I had never seen a "watch idle" entry, because an app was holding the watch awake. Identifying and removing that app has solved the rest of my problems.
Click to expand...
Click to collapse
So which app was that. Could you be specific please? I've had my 360 since October and had no issues with battery life until about 2 weeks ago and now it can't make it through a work shift all of a sudden. I've seen the 'watch idle' and the android guy with no title in the battery stats (as well as 'Bluetooth', which is mind blowing) as the main drains but I can't figure out which apps need the boot. Thanks in advance for the help, this problem is driving me crazy!
For me it was WeChat. I didn't even know it had a wear component. However, using Wear Battery Stats (available on Google Play) I noticed that there was a missing icon under "app activity" because it had updated that day. Tapping on this blank icon told me it was an activity belonging to WeChat. Using this, I deduced that was the problem app. Removing it seems to have solved my issue. I'd recommend a similar process, although I only found this app on that day due to it updating, so you may struggle. I get the impression the standard of coding of wear apps so far is pretty shoddy, I don't think not providing a package name and icon is unusual or specific to this one app.
chrispy_212 said:
Hi,
I just received a Moto 360, and I know what you're going through!
I've gone from 3 charges a day previously, and today the watch is reporting I have almost 2 days remaining of charge.
First, FULLY cycle the battery. Leave it on the stand over night, run it until it turns off (if you're in a rush, ambient display, full brightness!). Then, full charge to 100% and leave it for an hour on the charger once it is full.
After that, do a factory reset on the watch (in settings). In Android Wear on phone, use the settings menu to resync your apps.
Do one more full discharge and full charge, and you should be sorted.
If not, use the Watch Battery section of the wear app to identify problem apps. Before today, I had never seen a "watch idle" entry, because an app was holding the watch awake. Identifying and removing that app has solved the rest of my problems.
Hope all this works. Some of the steps seem/may be unnecessary, such as the factory reset, multiple full charge cycles. However, I speak from experience that they do work!
Edit: Do be aware that the charge cycles where you do a factory reset and sync will drastically drain the battery, giving the illusion that the problem is still there.
Click to expand...
Click to collapse
chrispy_212 said:
For me it was WeChat. I didn't even know it had a wear component. However, using Wear Battery Stats (available on Google Play) I noticed that there was a missing icon under "app activity" because it had updated that day. Tapping on this blank icon told me it was an activity belonging to WeChat. Using this, I deduced that was the problem app. Removing it seems to have solved my issue. I'd recommend a similar process, although I only found this app on that day due to it updating, so you may struggle. I get the impression the standard of coding of wear apps so far is pretty shoddy, I don't think not providing a package name and icon is unusual or specific to this one app.
Click to expand...
Click to collapse
Thanks for the reply. I don't use that specific app so no luck there. Good call on Wear Battery Stats though. I actually already use it but I'll use its stats this time instead of the standard wear stats. Thanks again, hopefully I can find the culprit, been having issues with my phone battery as well recently too.
B1gC72 said:
Thanks for the reply. I don't use that specific app so no luck there. Good call on Wear Battery Stats though. I actually already use it but I'll use its stats this time instead of the standard wear stats. Thanks again, hopefully I can find the culprit, been having issues with my phone battery as well recently too.
Click to expand...
Click to collapse
fyi - i haven't tested this since it happened, but i disabled BT on my phone (just disabled in settings, without disconnecting the wtch first) and the watch drained itself in probably about 20-30 minutes. When I finally got it charged, it said BT took everything.
When I was having app issues, I also noticed very high bluetooth consumption. This could likely be a poorly coded app constantly trying to ping your phone for data and receiving no reply as it is not designed for a scenario where your phone is not connected.
The alternative of course is defective hardware.
A step I did not include in my original post was that I also clean-flashed a new rom on my phone. I felt this was due to a unique problem that I had (bluetooth problems in car also) but nonetheless thought I should mention that too. It's hard to be sure which step exactly cured my watch.
Same was happening to me, after several master resets and trial and error, i found that on my Samsung s7 edge i had my watch set as a trusted device so when it was connected to my phone my device would unlock without passcode. After turning that off, battery life is normal again, 24hrs plus. I think the constant bluetooth checking to see if it was attached drained battery extremely fast, hopefully this helps someone
Hello,
2 weeks after Android 11 update, my pixel 2 xl started to feel hot and the battery was discharging quickly. On Google help, many people were in my case, and many of them mentioned about unstalling Tunein. Which I did, then my phone stopped to be warm but this didn't stop the drain issue. What I have noticed is that if I don't touch my phone, the battery acts as normal, slow discharge, but when I use it, meaning when the screen is on, the battery just discharges at a crazy speed. It was not like that just before the Android 11 update. Anyone got this problem and found the reason / a fix ?
Thanks
I am having the same issue. An have not found a solution as of yet. I thought it may be the Pixel Launcher. So I changed it to Nova Launcher with no change.
Yes, strange. Mine gets a serious battery drain from 100% to 50% in a short time, even when I don't use it. Then below 50% it is very stable as long as I don't use it. Never experienced this before.
Toader944 said:
I am having the same issue. An have not found a solution as of yet. I thought it may be the Pixel Launcher. So I changed it to Nova Launcher with no change.
Click to expand...
Click to collapse
I have the same problem. before that, I was calmly getting 4-6h SOT After updating to Android 11 as lucky as I get 4h SOT. Mostly, however, I have 2.5-3.5 hours. The standby time seems ok, Only during use the battery disappears very fast. ? In my free time I will try the factory reset.
I think i got it...
Hello gentlemen, i got this problem with october update in particular.
So, digging in a google forum i found a user who recommended to install an updated version of Android System Webview (maybe you should download it from apkpure or apkmirror) , Carrier Services and.... uninstall Tune-in (yep... the radio app)
I don't know which one did the trick... but it just did..
I hope it helps!
Can you comment which versions of carrier services and webview you installed?
Arbatel said:
Can you comment which versions of carrier services and webview you installed?
Click to expand...
Click to collapse
Sure, i installed webview 86.04240 and (there was a mistake in my prev post) Device Health Services 1.17.0.331553323.
Anyway, i got 2 webview updates since then... so, just install the last one... if you got auto-updates enable you should have your problem fixed by now (i guess that happened to the op).
Pulsar.uy said:
Sure, i installed webview 86.04240 and (there was a mistake in my prev post) Device Health Services 1.17.0.331553323.
Anyway, i got 2 webview updates since then... so, just install the last one... if you got auto-updates enable you should have your problem fixed by now (i guess that happened to the op).
Click to expand...
Click to collapse
thanks for the info, unfortunately I checked and I have exactly the same version of the application installed. the problem with the battery remains. the strangest thing is that I have no problem with idle drain, but when used with the screen on, the phone uses almost twice as much energy as before ?
I have the same problem, idle drain is ok, but whenever I use the phone, the battery drains very fast.
shinigami777 said:
thanks for the info, unfortunately I checked and I have exactly the same version of the application installed. the problem with the battery remains. the strangest thing is that I have no problem with idle drain, but when used with the screen on, the phone uses almost twice as much energy as before
Click to expand...
Click to collapse
sebtai said:
I have the same problem, idle drain is ok, but whenever I use the phone, the battery drains very fast.
Click to expand...
Click to collapse
finally someone with the same problem. did you do factory reset before updating to Android 11? Because I don't, and I think I'll try to do it.
NO, i didn't do a factory reset because I have seen a lot of people (online) doing it without success. You can see this thread here on Google support, over than 580 comments today...https://support.google.com/pixelphone/thread/70445129?hl=en
But apparently some people fixed the problem with a factory reset...
shinigami777 said:
finally someone with the same problem. did you do factory reset before updating to Android 11? Because I don't, and I think I'll try to do it.
Click to expand...
Click to collapse
I actually did a factory reset today but the battery drain is still there...
sebtai said:
NO, i didn't do a factory reset because I have seen a lot of people (online) doing it without success. You can see this thread here on Google support, over than 580 comments today...https://support.google.com/pixelphone/thread/70445129?hl=en
But apparently some people fixed the problem with a factory reset...
Click to expand...
Click to collapse
I had the same problem and it was a new (at least to me) Google program called "Digital Wellbeing". I had to turn it off, which wasn't a straight forward proposition. I even "uninstalled" which just uninstalled the updates and they came back.
I don't recall exactly all the steps I took, but I now have my trusty Pixel 2 XL back to it's previous battery usage. Which is excellent for a three year old device.
Anyway, turn it off, take away all it's permissions, and do everything you can to shut it down. I was almost ready to root my device just to really get rid of it.
I disabled digital wellbeing, stopped the permissions, and uninstalled the update on the play store, but it didn't fix the battery drain...
Unicorn512 said:
I had the same problem and it was a new (at least to me) Google program called "Digital Wellbeing". I had to turn it off, which wasn't a straight forward proposition. I even "uninstalled" which just uninstalled the updates and they came back.
I don't recall exactly all the steps I took, but I now have my trusty Pixel 2 XL back to it's previous battery usage. Which is excellent for a three year old device.
Anyway, turn it off, take away all it's permissions, and do everything you can to shut it down. I was almost ready to root my device just to really get rid of it.
Click to expand...
Click to collapse
A few days have passed and I can see a significant improvement. Honestly, I don't know what actually helped. some app update or maybe something I did, but there's a significant improvement.
In general, I would like to remind that from the update to android 11 my battery was tragic but only when using it, there was no problem with standby.
I was barely able to get 4 SOT hours. Now I can safely exceed 6 hours.
The only modifications I made were:
- leave beta program of digital welbing and its complete shutdown app
- disabled wifi scanning
- disabled Location service for emergency calls ELS
Since then, battery consumption with the screen on has dropped from 25-30%/ h to 12-16%/h. The phone is like new again. In addition, everything works very quickly and smoothly. ??