Related
Hi everyone,
I just flashed ARHD 7.0.2 on my Desire HD last night and I'm experiencing the following problem:
The CPU remains at 99-100% all the time, the battery drains excessively fast and the phone gets really hot.
Using "Watchdog Lite", I detected that when the CPU does not stay at 100% (after a battery-pull), the "Phone" process uses 0,0% of CPU.
However, for some reason, after a while it will jump up to 80-90% and stay there, causing the CPU to go berserk.
I suppose the heat-issue comes from the fact that the cpu works all the time at 100%.
The battery drain issue comes also from the CPU.
However, I do not know why the Phone process would suddenly go crazy and use that much cpu - and keeps doing it until the battery is dead.
I'm thinking it is because the ARHD 7.0.2 ROM is actually a stock Sensation XL base and thusly requires another RIL than the one that was on it before that.
Before flashing another RIL or radio I would like it very much if somebody could confirm that the fact that the Phone process goes crazy like that could very well be linked to the fact that the RIL and Radio don't match.
It seems obvious, but I don't know enough of the inner workings to verify this, so therefor: this thread
Thanks in advance to all!
sstm
The RIL should be pretty standard between HTC devices so that shouldn't cause any issues. Did you do a full wipe before the install?
Hello TransientMotion,
Yes I did a full wipe, I even cleared the battery stats for good measure.
I even formatted my SD-card to make sure nothing remained from some app somewhere.
The phone is as if I'd have bought it fresh out of the store with ARHD 7.0.2 on it (and rooted of course)
It's just weird to see that the "Phone" process is using this much cpu, even when on Airplane mode.
Thanks for you reply,
sstm
It may be worth trying out an earlier version of the rom just to see what happens. I used 6..3.1 before I switched over to ICS and never had any major problems with it. If that works fine then try newer versions until you get glitches again or it works without the drain
Hey,
I just found out that it is Llama (kebabApp 'location aware' application) who is causing the problem.
Whenever I leave an area and then re-enter it, the CPU goes berserk and stays that way as if some loop can never be interrupted.
I didn't have this problem on ARHD 6.3.1, but I didn't have the same Llama configuration on it either so I tried the Llama config on ARHD 6.3.1 and it did the exact same thing: cpu 100% and slowness all over.
So conclusion: Llama config is the culprit.
Anyways, thanks for you help TransientMotion.
sstm
Last week I flashed my Fire to run CM10. I love it except for one thing.
My battery used to last 30-40 hours before needing a charge. Now, It seems like I get about 8.
Does anyone know of any services I can kill to improve that? Should I turn off wifi unless I'm using it? Or is CM10 on the Fire just a battery hog?
My thoughts are that theres something in the rom looking for GPS, or location or phone signal or something, but I'll be hornswaggled if I can figure out what it is. (yeah, that's right, I said hornswaggled)
Tips or pointers would be appreciated.
I'm running a Mac, so if I need to run software, it'll have to be compatible. (trashed my Windows when parallels stopped working with 10.8)
ottermann said:
Last week I flashed my Fire to run CM10. I love it except for one thing.
My battery used to last 30-40 hours before needing a charge. Now, It seems like I get about 8.
Does anyone know of any services I can kill to improve that? Should I turn off wifi unless I'm using it? Or is CM10 on the Fire just a battery hog?
My thoughts are that theres something in the rom looking for GPS, or location or phone signal or something, but I'll be hornswaggled if I can figure out what it is. (yeah, that's right, I said hornswaggled)
Tips or pointers would be appreciated.
I'm running a Mac, so if I need to run software, it'll have to be compatible. (trashed my Windows when parallels stopped working with 10.8)
Click to expand...
Click to collapse
Download cpu spy from Play store and let it run for a few hours. Then open it and see how long your fire stays in each state. It should be deep sleeping most of the time (~80%) if you're not using the fire at all. If not, try turning wifi off and limit background app processes via developer options. If your CPU is spending a lot of time around 1000 mHz try setting up some profiles with SetCPU, such as 216 mHz max when screen is off. Once these are implemented you should see battery life pick up a bit, although not as much as a stock kindle fire. I'm getting around 80 hrs of standby time, maybe 12-15 with moderate use.
My wife don't get that much on jb eye candy. Actually her battery life is horrible on that rom
Sent from my Droid Razr using xda app-developers app
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
Was skeptical about the N5100 battery life since it only have 4600mAH battery.
Now that I have bought it, it seems my worries are confirmed.
I'm running stock rom, only rooted it without other modification.
Installed and have greenify running. Not using any sim card, only using it on WiFi.
Playing a video using MX Player, drained up about 20% of battery for a 45min video. That's rather heavy imo.
Normal browsing and reading forums eats up about 4% per 6min of use.
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old.
Btw the above test were with Power Saving mode(CPU and Screen) and screen brightness was at 25%~30%. Currently on 4.2.2.
And does using the S Pen eats up significantly more battery?
Thanks in advance for the feedback.
hahnliang said:
Was skeptical about the N5100 battery life since it only have 4600mAH battery.
Now that I have bought it, it seems my worries are confirmed.
I'm running stock rom, only rooted it without other modification.
Installed and have greenify running. Not using any sim card, only using it on WiFi.
Playing a video using MX Player, drained up about 20% of battery for a 45min video. That's rather heavy imo.
Normal browsing and reading forums eats up about 4% per 6min of use.
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old.
Btw the above test were with Power Saving mode(CPU and Screen) and screen brightness was at 25%~30%. Currently on 4.2.2.
And does using the S Pen eats up significantly more battery?
Thanks in advance for the feedback.
Click to expand...
Click to collapse
Do a search on battery and charging by me, in the Q&A threads. I won't repeat myself here, but I go into how to correct drain issues. Many developers will push their apps for calibration. The real trick is discovering what is doing the drain. I have seen for myself how one app can do a lot of damage with media. Normally I get 12% per hour on battery usage while Miracasting Netflix to my tv, and about 10% on normal usage with WIFI always on. I have MXplayer and a bunch of apps as well running so I am not going to get the same power savings as with a cleaned up stock ROM without any apps, what would the point of having a tablet if that is the case???? I guess peeps like to show off when it comes to numbers. I like to show off when it comes to usability and function without all the apps get in the way.
my battery stats
I'm running CivZ-FLEX-BEAM-REV3.6.2 ROM.
Installed and have greenify running. Not using any sim card, only using it on WiFi, even off the WiFi before I off the screen.
Even use underclock to 1.2Ghz cuz only used for normal browsing, nothing intense that require more power.
Here's my battery stats:
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old, now 9 or 10 months already.
Now considering should I replace the battery or just get a powerbank to help.
Thanks in advance for the feedback.
hahnliang said:
I'm running CivZ-FLEX-BEAM-REV3.6.2 ROM.
Installed and have greenify running. Not using any sim card, only using it on WiFi, even off the WiFi before I off the screen.
Even use underclock to 1.2Ghz cuz only used for normal browsing, nothing intense that require more power.
Here's my battery stats:
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old, now 9 or 10 months already.
Now considering should I replace the battery or just get a powerbank to help.
Thanks in advance for the feedback.
Click to expand...
Click to collapse
From what the graphs show... it looks like the battery could be going bad, as there has some that say Samsung is aware of bad batteries in some units. You could contact them, but you will need to un-root if sending to Samsung for repair.
Since you are rooted, I suggest installing xposed framework and install Wanam DVFS Disabler for Xposed. It is a standalone utility from the complete Wanam xposed app. Once installed make sure both xposed is functional, and the app in xposed is enabled. These apps act as a separate process from the OS. So installing them requires user interaction for activation and updating, along with a reboot most of the time.
Once they are running... it is best to turn off the tablet for 1 minute and then plug in the USB charger and wait til it is showing 100%. Then turn on the tablet. You can unplug the USB power cable and wait 1 minute, then plug it in. Take note if the charge takes less than a minute to get to 100%. If it takes a minute or more... you will need a stop watch, as it should take about 15 to 20 seconds to go to fully charged, unless you have music or media running at the time. If it does charge quick, you can then disconnect and do another days worth of use and check your stats. Hopefully disabling DVFS will cure your issue if it is not battery related.
As for unrooting, make sure you do a clean uninstall, and have any apps that require root uninstalled. If running triangle away uninstall that as well. You may have to check within the apps settings to make sure you uninstall properly, as to uninstall from play store or the system may not properly remove the app.
Updated Battery Stats
this is my updated battery stats, now I'm suspecting it maybe due to calibration problem?
My screen on time is now 2 hrs 45 mins, and for the last 45 mins it has been running on that last 1% of battery(but with screen dimmed, as brightness is automatically dimmed and can't be adjusted when below 5%).
Even until now the device haven't auto shut down due to run out of battery yet even though been running 45mins SOT for that 1%.
Calibration problem? I've tried calibrating using calibration apps, which I charged to 100% then press calibrate, but didn't help.
hahnliang said:
this is my updated battery stats, now I'm suspecting it maybe due to calibration problem?
My screen on time is now 2 hrs 45 mins, and for the last 45 mins it has been running on that last 1% of battery(but with screen dimmed, as brightness is automatically dimmed and can't be adjusted when below 5%).
Even until now the device haven't auto shut down due to run out of battery yet even though been running 45mins SOT for that 1%.
Calibration problem? I've tried calibrating using calibration apps, which I charged to 100% then press calibrate, but didn't help.
Click to expand...
Click to collapse
Sudden drop of more than 3% at any level after doing the DVFS disable and properly charging can be one of two things.
A bad battery, or bad charging cable. Yep, I have had two bad Samsung cables, one did exactly what is happening with you, and the other did a melt down at the USB connection on my tablet. If you have a good cable from a Blackberry or a Sony/Ericson device, you can try that. I have moved over to Sony Xperia cables, as they are pretty well built and longer.
If another cable does not solve your issues, I suggest unrooting and cleaning up rooted apps before having Samsung service your tablet. It very well could be a bad battery.
thanks for the reply, I think I'll just resort to sending it back to Samsung to fix it.
Now I have made a nandroid backup already, then I flashed stock firmware, so my device is now unrooted and on stock firmware, however my flashcount is still there, and now I can't run triangle away cuz my device is unrooted already.
If I were to root it, it'll flash custom recovery again then it won't be on stock firmware anymore.
hahnliang said:
thanks for the reply, I think I'll just resort to sending it back to Samsung to fix it.
Now I have made a nandroid backup already, then I flashed stock firmware, so my device is now unrooted and on stock firmware, however my flashcount is still there, and now I can't run triangle away cuz my device is unrooted already.
If I were to root it, it'll flash custom recovery again then it won't be on stock firmware anymore.
Click to expand...
Click to collapse
Your unroot sequence was done out of order.
Set USB debug
Root stock rom with saferoot.zip
Install triangle away
perform clear of counters
Verify after clearing in about device that custom is not set.
If so make sure triangle away is set to clear and perform clearing.
Remove triangle away
Remove SuperSU through the settings, clear for reinstall.
To make sure everything is proper... do a factory reset.
Once those steps are done, your tablet should be stock and able to perform OTA or Kies updates, without any issues with counter and root.
Hello, new to the forums here. I recently updated to 4.4.2 on my LG Optimus G Pro and I went from having a battery that lasted all day, sometimes two days to my phone being dead by the time I get home from work for the day ever since the update.
Two days ago I had 1hr18min of screen time within a 6 hours off the charger and the phone was at 15% battery life left. Today, I had 13 minutes of on screen time and at the end of my 6 hour shift my phone was at 40% and dead a few hours after I got home. I have GPS, bluetooth, NFS all disabled and my brightness set to 30%.
Any help would be greatly appreciated, I'm thinking of doing a factory reset and just not updating to the new version of android when it prompts.
Thanks
silentvelcr0 said:
Hello, new to the forums here. I recently updated to 4.4.2 on my LG Optimus G Pro and I went from having a battery that lasted all day, sometimes two days to my phone being dead by the time I get home from work for the day ever since the update.
Two days ago I had 1hr18min of screen time within a 6 hours off the charger and the phone was at 15% battery life left. Today, I had 13 minutes of on screen time and at the end of my 6 hour shift my phone was at 40% and dead a few hours after I got home. I have GPS, bluetooth, NFS all disabled and my brightness set to 30%.
Any help would be greatly appreciated, I'm thinking of doing a factory reset and just not updating to the new version of android when it prompts.
Thanks
Click to expand...
Click to collapse
Get betterbatterystats and see if you phone deep sleeps. If not then check what the wakelocks are in partial wakelocks. If it's a kernel problem maybe you need to flash a different kernel.
cxyjordan said:
Get betterbatterystats and see if you phone deep sleeps. If not then check what the wakelocks are in partial wakelocks. If it's a kernel problem maybe you need to flash a different kernel.
Click to expand...
Click to collapse
i am running stock phone. it is not rooted or anything
Same exact battery drain problem. Im on stock e980 rom (rooted) with no custom kernel.
Gsam battery monitor app is showing the kernel as keeping my phone wake for the entire time my phone has been unplugged.
The problem seems to come and go though. One day itll be fine, but another day the battery will be sucked dry fast.
Sent from my SM-P600 using Tapatalk
I'm running stock rooted for e980 and have pretty good battery life .... Try clearing Google play services data and rebooting ... Check and see what's draining your battery mol its pretty easy
2SHAYNEZ
I'm also running stock kernel, and have great battery life on kitkat. Just reset your phone to factory defaults
Sent from my LG-F240L
ccelis said:
I'm also running stock kernel, and have great battery life on kitkat. Just reset your phone to factory defaults
Sent from my LG-F240L
Click to expand...
Click to collapse
I've done this twice in the past 3 days....
I'm sick of having to set up my phone over and over again. And this is a new phone too. I just got it Monday under warranty because my old phone broke.
It's getting annoying. I used to get 14-17hrs+ of battery life (casual use, usually ending the day at 30-50% too, so I never even reached 0%) with my old phone on Jelly Bean. Now with Kitkat, I get around 6 hours if I'm lucky! According to Wakelock detector, my phone is awake 85%+ of the day! All it points to is Kernel (Android OS). I see lots of Wlan_wake triggers too, so I suspect wifi, but even with wifi off, the drainage still occurs. And I only have a 2GB data plan shared between 3 people, so it's not like I can just use data all the time either. I actually NEED wifi.
spexwood said:
I've done this twice in the past 3 days....
I'm sick of having to set up my phone over and over again. And this is a new phone too. I just got it Monday under warranty because my old phone broke.
It's getting annoying. I used to get 14-17hrs+ of battery life (casual use, usually ending the day at 30-50% too, so I never even reached 0%) with my old phone on Jelly Bean. Now with Kitkat, I get around 6 hours if I'm lucky! According to Wakelock detector, my phone is awake 85%+ of the day! All it points to is Kernel (Android OS). I see lots of Wlan_wake triggers too, so I suspect wifi, but even with wifi off, the drainage still occurs. And I only have a 2GB data plan shared between 3 people, so it's not like I can just use data all the time either. I actually NEED wifi.
Click to expand...
Click to collapse
do you have an SD card installed? Maybe you can try to remove that and get rid of all other media from your phone storage. Might be a media scanner problem? Or maybe you can try to disable auto sync, and check if Google play services is the culprit.
Sent from my LG-F240L
ccelis said:
do you have an SD card installed? Maybe you can try to remove that and get rid of all other media from your phone storage. Might be a media scanner problem? Or maybe you can try to disable auto sync, and check if Google play services is the culprit.
Sent from my LG-F240L
Click to expand...
Click to collapse
The media scanner usually shows up in the battery stats window though, and it isn't. I've had a corrupted SD card on my tablet once before and it caused media scanner to go berserk, but the Mediascanner entry appeared under Settings>Battery as the highest battery consumer.
In this case of my phone right now, it is Android OS in Settings>Battery. According to Wakelock detector, GSam, and BetterBatteryStats, it's more specifically Kernel.
spexwood said:
The media scanner usually shows up in the battery stats window though, and it isn't. I've had a corrupted SD card on my tablet once before and it caused media scanner to go berserk, but the Mediascanner entry appeared under Settings>Battery as the highest battery consumer.
In this case of my phone right now, it is Android OS in Settings>Battery. According to Wakelock detector, GSam, and BetterBatteryStats, it's more specifically Kernel.
Click to expand...
Click to collapse
Have you tried reflashing your firmware, instead of just doing a factory reset?
I assume you are rooted since you are using BBS and wake lock detector on KK. Why not flash a custom rom?
Sent from my LG-F240L
Battery
silentvelcr0 said:
Hello, new to the forums here. I recently updated to 4.4.2 on my LG Optimus G Pro and I went from having a battery that lasted all day, sometimes two days to my phone being dead by the time I get home from work for the day ever since the update.
Two days ago I had 1hr18min of screen time within a 6 hours off the charger and the phone was at 15% battery life left. Today, I had 13 minutes of on screen time and at the end of my 6 hour shift my phone was at 40% and dead a few hours after I got home. I have GPS, bluetooth, NFS all disabled and my brightness set to 30%.
Any help would be greatly appreciated, I'm thinking of doing a factory reset and just not updating to the new version of android when it prompts.
Thanks
Click to expand...
Click to collapse
Hi i had the same problem as you but i started digging inside the system of the phone i found the problem but you will require root access. If you have root you have to delet a lib file tand it carrier iq wich run in background and drains your battery the file to delete is libiq_client.so do that and you will see an increase in battery life
Hav
ccelis said:
Have you tried reflashing your firmware, instead of just doing a factory reset?
I assume you are rooted since you are using BBS and wake lock detector on KK. Why not flash a custom rom?
Sent from my LG-F240L
Click to expand...
Click to collapse
I did this on Tuesday or Wednesday.
... I messed something up on my phone while trying to install a custom recovery, so I was basically forced to reinstall everything. I'm on stock ATT e980 ROM (on an E980) + root. I reflashed the Jelly Bean tot file and then did the OTA update with no apps installed.
On the phone that got warrantied, I had flashed the E980 kitkat backup (now has a flashable version too), and the battery life seemed to be much better on it for about a week, and then the issues started there too.
I just rebooted the phone into recovery and wiped cache and Dalvik cache. Many people on Kitkat are reporting that this helps, but only for about 2 days then the issue returns. Obviously, I want a permanent solution.
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
xoLEOox said:
Hi i had the same problem as you but i started digging inside the system of the phone i found the problem but you will require root access. If you have root you have to delet a lib file tand it carrier iq wich run in background and drains your battery the file to delete is libiq_client.so do that and you will see an increase in battery life
Hav
Click to expand...
Click to collapse
I just tried this right now. Will see what happens.
Will report back if I see anything noticeable.
How would this this battery though? Like, what does it do? Are there any adverse effects to removing it?
EDIT: BTW, I know you weren't addressing this at me, but I'm still trying it LOL
spexwood said:
I did this on Tuesday or Wednesday.
... I messed something up on my phone while trying to install a custom recovery, so I was basically forced to reinstall everything. I'm on stock ATT e980 ROM (on an E980) + root. I reflashed the Jelly Bean tot file and then did the OTA update with no apps installed.
On the phone that got warrantied, I had flashed the E980 kitkat backup (now has a flashable version too), and the battery life seemed to be much better on it for about a week, and then the issues started there too.
I just rebooted the phone into recovery and wiped cache and Dalvik cache. Many people on Kitkat are reporting that this helps, but only for about 2 days then the issue returns. Obviously, I want a permanent solution.
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
I just tried this right now. Will see what happens.
Will report back if I see anything noticeable.
Click to expand...
Click to collapse
Ok restart when you delete the file this is a permanent solution for me i hope this helps you as it did me
ccelis said:
I assume you are rooted since you are using BBS and wake lock detector on KK. Why not flash a custom rom?
Sent from my LG-F240L
Click to expand...
Click to collapse
I didn't see this part of your message, but I just had to respond lol
Yes, I'm rooted and I absolutely hate custom roms. They take out all the features of the phone that I originally bought the phone for, like Smart Screen, the IR remote (yes, I know it can be ported), and the quick memo button. Plus I used custom ROMs on my old SGS2 and they always caused me tons of problems. Crashes, overheating, random reboots, random SODs, etc etc etc. Plus I hate the AOSP feel. I know it's true Android, but I just don;t like it.
---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------
xoLEOox said:
Ok restart when you delete the file this is a permanent solution for me i hope this helps you as it did me
Click to expand...
Click to collapse
I'm still getting more than usual battery drain, but it is better now.
I just got a replacement OEM LG battery, so I will try that to see if maybe the battery is defective. When I got my phone replaced under warranty, they didn't have batteries in stock, so they just gave me back my old one and ordered me a knew one. The old phone was overheating a lot too, so maybe the battery is bad.
UPDATE: OK, MUUUUUUUUUCH better battery now!
I put in that new battery and "recalibrated" it by draining it to 0% and charging with the power off. Once it reached 100%, I let it charge an extra hour, unplugged, and started up the phone.
I also installed Qualcomm Snapdragon's Battery Guru. I set it up so that it's mostly managing app syncing, but I also set it up so that it will not rely on location services to turn on/off my wifi. I don't want to leave my location services on all the time. I don't know how it is on Kitkat, but on older Android versions (ICS and GB), leaving GPS on was a huge battery drainer! I still treat location like it was back then.
Anyways, it will take a few days for the app to learn my usage patterns, but it's already helping by making certain apps only sync when I open them, etc. I suspect that all the wlan_wake wakelocks are being caused by auto-sync but I'm reluctant to turn it completely off since i rely on it to sync my work schedule, calendar, etc between my phone and tablet. I just wish there was a system setting to allow auto-sync to run every X hours or something. I really only need the sync to run every 6 hours or so.
It's been about 35mins now with 6mins of screen time and the phone is still at 100%. A few text messages and the installation of Battery Guru too. This is normal and how things used to be. After a while, the phone will most likely go to 99% and then have faster drain, but it shouldn't be so rapid like before. Earlier today, after 30mins, the battery would be at at least 95% or lower by now! After a full day, the battery usage graph would should a 45 degree angle too! It used to be an almost level, very gradual angle instead.
I should also mention that for a while, I was using a Zero Lemon slim battery (3150mAh). I bought it because of all the hype Zero Lemon was getting here on XDA, but I really regret it now. I used it for 2 weeks (1 week on my broken phone and 1 week on my replacement) and the drain wasn't consistent, even after several calibration attempts. It lasted me all day though, but I'd be stuck at maybe 3% for like an hour, then while in deep sleep, the battery would "magically charge" to 6%.
After I swapped back to the OEM battery, I don't think I recalibrated, so I wonder if my phone thought I was still using the Zero Lemon.
I'm planning to return the Zero Lemon.
UPDATE2: It's been a couple hours now and the Android OS is starting to retreat from the #1 slot in the battery consumption list!
Screen is #1 now and Android OS went from 65% usage to 14%! :good: :good:
UPDATE3: :crying: OK, it's broken again. I didn't do anything to the phone, but when the phone hit 50%, I left it alone for 2 hours and the battery drained 30% while it was supposed to be sleeping. Android OS is back up to 80% usage!
Wifi on, Location off, Bluetooth off, auto-sync on. I'm trying auto-sync off today to see if there's any dramatic improvement.
UPDATE4: I might be on to something now. I noticed 2 things: 1st, when the screen is off and the phone is SUPPOSED to be in deep sleep, the back of the phone stays warm to the touch. It wasn't hot, but it was warm enough to be noticeable. 2nd, I had System Tuner installed yesterday but uninstalled it this morning. Despite uninstalling and rebooting, the phone was still draining battery fast (I still lost 25% in 2 hours today!). I noticed that System Tuner had added a script to System/etc/init.d, so I deleted that and rebooted. Now the phone seems to be sleeping (says so in BetterBatteryStats and WakeLockDetector), and the back of the phone is COLD to the touch when doing so. I took a shower today (I take fairly long showers too LOL), and then checked my email, and the battery life didn't decrease at all during that time while it was asleep.
Obviously, I need to test this throughout the day now, but this is definite progress, if not the solution.
Also, on my warrantied phone, when I had the Zero Lemon battery inserted, battery drain was high (battery's fault), so I installed System Tuner then too, trying to tweak the phone. After switching back to the stock battery, the drain remained, but most likely due to System Tuner's script.
Then when I got my replacement phone, I ALSO installed System Tuner and of course, I got battery drain issues! I factory reset, but did not install System Tuner, but the problem still remained. However, it probably remained because the reset doesn't remove system files, so this script was still in the init.d folder.
FINAL: I ended up flashing the stock ROM again (I used Eazy Kat 1.0 this time). My phone began bugging out on me. Random crashes here and there, mobile data randomly disappearing (no LTE/4G/3G at all), and worst of all, people were having difficulty hearing me during calls. Reflashing seems to have worked perfectly this time. *knock on wood*
FYI: The last flashes I did, I used .tot files to flash back to stock Jelly Bean and then updated to Kitkat via OTA.
xoLEOox said:
Hi i had the same problem as you but i started digging inside the system of the phone i found the problem but you will require root access. If you have root you have to delet a lib file tand it carrier iq wich run in background and drains your battery the file to delete is libiq_client.so do that and you will see an increase in battery life
Hav
Click to expand...
Click to collapse
I stumbled across this post and tried that fix. I'll check back in later to see what it does.