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
Hi all, just visiting from the gnex forums. My wife has a desire running the official gingerbread rom. She has a recurring problem whereby she'll power off the phone and it appears to shut down but will still have a grey tint like the screen is still slightly lit. Last night from a full battery it had permanent screen on in the battery stats and was near empty in the morning showing a constant drain all through the night. Has anyone had this issue?, is it related to the gingerbread update or is it just a rogue app??
I've attached an image of the battery stats with the night period being the steep drop on the right...
Any tips or advise is greatly appreciated....
Probably a rogue app. Search for Better Battery Stats app here on XDA to help you see what's keeping it awake.
Furthermore, try disabling fastboot from settings, don't remember which settings, but it should be in there somewhere.
Thanks for the replies. I've got that better battery stats app and just need to read up a bit on how to use it then I'll give it a go tonight. From my searches I found multiple things suggesting it could be an app but it seemed odd to me that it was preventing the phone from powering off and not just preventing it from sleeping.
Regarding the fast boot option I've just found that and it was turned on - what is this option for and why could it cause this problem then? ....
On Better Battery Stats, I usually check Partial Wakelocks - Since Unplugged. Most processes should be below 1% from what I understand. But it will depend on how long you are using a certain app. If you see a process that's been running for so long but you've just used the app related to it for a relative short period of time, then you check that particular app. Maybe the sync option is too frequent or it's just really poorly coded app.
If it appears that a valid android process is the one eating the battery, then an app is probably keeping it awake and you may need to dig a little deeper to figure out what app is causing that.
Regarding the fast boot option, all I know is that it's a feature to reboot the phone without going through the main HTC logo animation. So it's really like rebooting the phone without actually killing the background processes. (Not sure about it though maybe someone can explain this.)
Basically, with the Fastboot option the phone never REALLY turns off, it's a little bit like it's on hibernate, that's why it can boot a lot quicker, as it skips the bootloader and goes straight to booting the system.
Thanks guys. With the fast boot turned off it didn't do it last night so I'll try with fast boot turned on tonight and see what happens - try to confirm what's happening......
Many thanks for your help!
I turned fast boot on again yesterday and the fault occurred again overnight. Went from 100% battery to 55% overnight. Pictures of the stats for useage during this period are attached.
Anyone know what this alarm manager and sleep broadcast are?
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
hi friends, my HOX acts funny sometimes. in idle mode the battery drops by 30-40% and when i check the power consumption, android os is the main culprit, consuming 30-40% and sometimes up to 70%. Also when this happens the phone gets warm...i haven't rooted the phone. however after reboot the issue seems to resolve. this happens once a week. other wise the battery is performing good... i have watchdog lite but there aren't any rogue apps as such that it can detect...
any inputs would be appreciated...
No replies!!!
kartoonz said:
hi friends, my HOX acts funny sometimes. in idle mode the battery drops by 30-40% and when i check the power consumption, android os is the main culprit, consuming 30-40% and sometimes up to 70%. Also when this happens the phone gets warm...i haven't rooted the phone. however after reboot the issue seems to resolve. this happens once a week. other wise the battery is performing good... i have watchdog lite but there aren't any rogue apps as such that it can detect...
any inputs would be appreciated...
Click to expand...
Click to collapse
Its difficult to say what the exact problem is as 'Android OS' could be many things.
I don't know Watchdog Lite, but you might want to try Better battery Stats, it has many options and ways to find rogue and batteryg hungry apps. Perhaps this wil help you solve your problem.
It sure helped me solve some battery drain problems.
Otherwise, try disabling as many automatic syncs and try uninstalling/disabling apps one by one, you might find the culprit that way.
If nothing else helps a reset to factory defaults and restoring all apps and setting one by one after that migth help, but seeing your not rooted that might be a big pain in the ***.
Oh, and make sure all your apps and your phonesoftware are up to date