Related
Please can I get some assistance, I cannot for the life of me figure out what has happened.
LeeDroid 3.3 latest.
I have gone from 48h standby to 14h. During use it's depleted in a matter of hours, it's incredibly low in relativity to what I'm used to.
I was on LeeDroid 3.0.2 previously and battery life was VERY long, I loved it - going back to this version doesn't help and the battery issue remains, and therefore it also remains on the newest build.
Previously I was running a bucket load of apps/games with normal 50% brightness, I have resorted to deleting apps/keeping tasks closed but to no avail. The Statistics for battery usage seem to look similar to how it used to be before, with display taking up a large chunk.
I tried the battery trick today but it hasn't helped. My phone has already gone to 98% (40m uptime) with screen turned off + SetCPU set at powersave/lowest mhz while screen is off.
I hope you can help, Thanks.
This does happen sometimes, not sure what causes it but a wipe and reflash sorts it out for me.
What kernel are you using? Have you made any recent changes before massive drain started happening?
Try monitor the current using current widget. If it's normal, around 1-4ma during standby, perhaps, your battery need calibrated. If it didn't resolve your problem, then, maybe the battery is dead.
ErOR22 said:
What kernel are you using? Have you made any recent changes before massive drain started happening?
Click to expand...
Click to collapse
I dont think this is the problem because when it happens to mine it just happens by itself after a few weeks of having the ROM installed with very few extra applications which I install immediately.
anyone know if the proximity sensor is classed under display? could be that thats stuck on. got any apps that use or used the proximity sensor? or maybe the touch screen is stuck on.
have you tried removing the SD card? see if its something on there.
Well I reinstalled Leedroid with the recommended rom and although the battery life is nowhere near what it was previously... its at a respectable 22h or so... enough to give me time to actually find a fix...
Theres no apps, nothing, just the rom and its apps so I will try it without SD card also, i dont understand how to check for proximity sensor though
Thanks
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.
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Checkout this thread to see if the gsiff_daemon is your problem. tl;dr when the system is hot and tearing through the battery, go to system settings -> Developer options -> and check Show CPU usage. If gsiff_daemon is the top or second highest on the list, then that is your problem. To solve it for the moment, use system tuner, or something else, to kill gsiff_daemon. There is no permanent cure at the moment, other than to delete gsiff_daemon. Both of those fixes require root, the non-root fix is to reboot.
If gsiff_daemon is not on the list, then something else is the problem, but Show CPU Usage should give you an idea of what system process is running hard.
Samsung Push problem
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
dansushi said:
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
Click to expand...
Click to collapse
Interesting, I installed "micro cpu monitor" shows thin line at top of screen showing both cores.
I haven't had this happen for some time now but after playing with google play and maps downloading offline maps etc I noticed my 2nd core pegged out.
Having seen this in the past & ignoring it I now realize that majorly drains the battery as well as it getting warm.
A simple reboot seems to be the only thing that fixes it. Clearing ram and closing recent screens dies nothing to clear the "cpu jam".
If left alone, it always shows the culprit as "android system"
As to what part of "android system" I don't know.
But until we figure this out for good, that little micro cpu monitor. App is sweet for peace of mind to know all is well or whether a reboot is needed. For what it's worth, I also noticed that after the event, that my auto rotate to landscape was mysteriously unchecked?
If it jams again, I'll have to see if it gets unchecked again, unknown if there is a relation.
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
That happened to me too. But for me, flashing another rom fixed it.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Swaggernaut said:
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No there is a cwm flashable fix floating around here for that
Galaxy SIII via XDA premium
do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?
Contact sync?
i noticed this today and while troubleshooting, noticed contact sync from google says "sync is currently experiencing problems..." maybe?
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
I read the thread about gsiff_daemon culprit. I had it listed as a possible battery drain culprit. The thread says the issue may happen after a hot reboot...which I did have. Killing gsiff_daemon was not immediately effective. I renamed the file so it wouldn't get used...like the thread recommended. I had to reboot to get normal battery drain back and have yet to see the issue again. But i wont know for some time...or maybe when/if i get a hot reboot...which is really rare. Do yourself a favor, and buy better battery stats. Its a must have tool...and it's not expensive.
I wonder if this problem has been solved with latest lj7 jellybean from sprint
Sent from my SPH-L710 using xda app-developers app
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
eatonjb said:
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
Click to expand...
Click to collapse
My experience with froyo/gb/ics is that things have been getting progressively better over the years. But with each so called UPGRADE of an OS or even APPS, we often have to deal with bugs or incompatibilities. I am eager to upgrade to a stock based JB soon, but wisdom says, for 20 things improved, there will be 5 things broken....or hurting in some way. Early adopters suffer the most as usually these issues get ironed out...most of them.
BUT...these stuck drains...wake locks etc., it seems they will happen when they do no matter how many issues get fixed. Over the years, I've had random standby drains caused by Maps/Nav. Maybe it's ok for months, then after a particular update, it's back...and unpredictable. The YES...a reboot, just like with a PC, is a quick short term workaround.
Finally, with the App CURRENT WIDGET, there is a provision to watch for high drain in standby. It watches MilliAmp (ma) readings over time..to determine if you have a rogue drain. That's different than monitoring the CPU. (Some drains do not cause much CPU activity) BUT UNFORTUNATELY, that app won't work with our S3's because of a lack of hardware support. Works great with HTC and many others. It's a bummer because I used to use it and have my HD2 reboot if a 15min consecutive high drain was recorded in standby....thereby saving the battery and usually killing the bug.
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app
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 even broke my phone with App Ops trying to figure it out, disabling wake permissions for most apps which caused FC's and even reboots. I have since restored all permissions but I still get FC's whenever I leave an app or switch out of it. Not sure if it's really crashing, but I get a FC message every time. So much so that Substratum turned off its theming for Files because it "crashed" after every screenshot was successfully uploaded to this post. Btw I just removed CrossBreed Lite and it seems to have helped. So far no reboots doing the same stuff that caused reboots! Not sure why it caused problems though. I used it for a few days with no issues.
Anyway, back to my battery woes. 30-40% kernel system usage. Why is this happening? Even Snapchat which is abusing wake locks is nothing compared to kernel system.
I'm running the latest build of AIM 8.1 with EX Kernel. I have just visited the other thread about tweaking governer values to optimize battery life so I'll report back with results although I doubt that's relevant to my battery drain.
I've Googled quite a bit on the subject and it seems that each case is different. Usually caused by a certain bug, although a lot of people say it's "normal" which I strongly disagree with.
Update: optimizing the CPU has definitely made an improvement, but the kernel battery drain still exists.
Could it really be pick up to wake and wifi search behind the drain? Isn't this phone supposed to have a sensor hub that allegedly allows for all sensors to constantly be on while using minimal power? I never noticed this drain on any other phone with both of these features on.
Anyway, I disabled pick up to wake and I'll start trying to remember to turn off wifi when not in use.
I think you're trying too hard and running a bunch of stuff. The kernal usage looks about right. I wouldn't run Gsam and BBS at the same time. They can fight each other. What makes you think there's a problem? Nothing jumps out at me.
Sent from my [device_name] using XDA-Developers Legacy app
I also can't see anything out of the ordinary, except this one picture where it shows the phone being active while dozing. I don't know how to understand that because I don't use that app, maybe I'm reading it wrong. What does Android's built-in battery monitor show? Is it dozing properly while screen is off? What is your average SOT? Is your mobile signal strong? I'm also using AIM 8.1+EX combination with satisfying results. Is your radio up to date?
maybe Wakelock Detektor or Greenify can help you.
And if you currently have things crashing all the time, start with a factory reset. Much easier to diagnose the cause when the apps aren't doing random stuff.