Develop Bugs

Rooted unrevoked and battery is worst

Ok so I just rooted added a few apps for root nothing that I know will drain my battery, ok so my battery goes down like 10% each hour doesnt last, thats just sitting in my pocket, any ideas
Sent from my PC36100 using XDA App

Are you running stock Rom? I suggest using an SBC kernel..

more info needed what programs have you added. something maybe causing a wake lock issue.

rooted my new EVO with unrevoked3,then installed netarchy-toastmod 4.3.1 kernel and my battery lasts all day with moderate usage

I doubt rooting it made your battery worse. there are many rom choices and apps to help you out. With rooting comes tinkering and it looks like its time to tinker. Look into an app called Spare Parts and another one call Autostarts

playya said:
Look into an app called Spare Parts and another one call Autostarts
Click to expand...
Click to collapse
Spare Parts can be downloaded here: www.4shared.com/file/253237538/37996617/SpareParts.html
^^ is your best bet to find out what's eating your battery.
Cheers!

The other issue is your battery stats may be off if you did something odd during rooting. There are several ways to fix that, the generally accepted way is to charge the phone while its on, turn it off completly, then:
1: Unplug phone when light is green
2: Plug in the phone
3: Repeat 10-15 times

I had the same issue, and this is what I did to fix my battery.
1. let the phone die completely, IE when the phone cannot turn on at all anymore.
2.Leave the phone off, let it charge overnight.
3.Verify that the phone is at 100% by going into settings->about phone->status
4.Power the phone off.
5.Boot into recovery
6.Wipe battery stats.
This should fix the issue, if not then consider using a different rom/kernel combo. I myself am personally using CM7 and suffer maybe 40% drain at most with my phone in my pocket with a typical 12 hour shift at work.
**Also, turn 3G off if you aren't using the internet, facebook, or Gmail ect ect. You can still recieve phone calls and text messages using this method. I believe there used to be an option to only have 3G running when the screen is on but i'm not 100% sure if this is still available.**

Yeah like I did that crazy charge thing I read about where you let It die and it helped for a bit and now thing just goes down like 20% after 30mins of just sitting in my pocket
Sent from my PC36100 using XDA App

battery charging/draining too quickly

my battery was down to 11%, so i turned my phone off and charged it for about 60 seconds through USB and now that i turned it back on it says 47%! there's no way it could have charged that quickly. this is on cm 6.1.2
i flash a lot of different roms but wipe data, cache, and dalvik before each new one. i don't run any unusual apps that would drain my battery and i have tried wiping battery stats every once in a while. ive also tried charging techniques such as charge for 8hrs, charge for another hour, etc. and nothing seems to work. my battery will drain in about 4 hours of moderate use (just web browsing and google talk while watching TV). im in an okay signal area, not using any 4g - happens with any rom.
this is a launch day evo battery but the actual phone (was 002) is replaced with my current 003 refurb.
im gonna try to wipe the whole sdcard and start from complete scratch.
Sent from my PC36100 using XDA App

i had this problem and when i checked to see what all was running i saw Google Maps was running... I didnt turn it on either but with a force stop and reboot im back to normal.

wiped sdcard completely, repartitioned, flashed latest cm 7 nightly, used for a while, charged to 50%, unplugged and in 20 minutes went from 50% down to 31%. had the same sort of behavior before on all roms. just display, cell standby, and android system using battery - not much else. maybe i need a new battery?
Sent from my PC36100 using XDA App

wrb123 said:
wiped sdcard completely, repartitioned, flashed latest cm 7 nightly, used for a while, charged to 50%, unplugged and in 20 minutes went from 50% down to 31%. had the same sort of behavior before on all roms. just display, cell standby, and android system using battery - not much else. maybe i need a new battery?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
what pri and nv version are you on? that could be the cause.

Battery down to 60% from 80% in airplane mode - help!

I am running Myn rls 5 stock kernel with set cpu underclocked to 245 mhz...
What could possibly cause battery tl go down 25% in 8 hours while in airplane mode screen turned off???
I used autostarts to stop anything from starting up on its own. If this is a bad idea what should I re-enable?
I looked in spare parts and battery usage but I can't really make sense of it. Thanks!

25% in 8 hours is pretty darn good. Besides, isn't the autostart app using power to constantly stop apps from automatically starting?
posting & replying via the XDA Premium app.

dougjamal said:
25% in 8 hours is pretty darn good. Besides, isn't the autostart app using power to constantly stop apps from automatically starting?
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I don't know what autostart is but I think it may be the problem.
I think something is wrong. I don't lose that much when I go into airplane mode.
Edit: OP, check spare parts for partial wake usage and see if there are any rogue apps.

If my phone was in airplane mode with screen off for 8 hours, I wouldn't lose more than 5 %. Hell, I only lose 5% with screen off over 8 hours, even with my radios on.
If he was using it, that's way different, but I picture "airplane mode with screen off for 8 hours" to be like if the phone was idle on the night stand, during a night of sleep. In that case, 25% is excessive, IMO. Autostart would be my first thought, I'd ditch it.
Sent from my PC36100 using XDA App

k2buckley said:
If my phone was in airplane mode with screen off for 8 hours, I wouldn't lose more than 5 %. Hell, I only lose 5% with screen off over 8 hours, even with my radios on.
If he was using it, that's way different, but I picture "airplane mode with screen off for 8 hours" to be like if the phone was idle on the night stand, during a night of sleep. In that case, 25% is excessive, IMO. Autostart would be my first thought, I'd ditch it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You're right, my friend. The OP did state "airplane mode". Sorry 'bout that.
posting & replying via the XDA Premium app.

dougjamal said:
You're right, my friend. The OP did state "airplane mode". Sorry 'bout that.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
No need to apologize man! You're on here helping so much, I bet you got googly eyed and simply missed it I was just stating how I'd expect my device to act in the same situation, and also my two cents!
Sent from my PC36100 using XDA App

FYI I had a more extreme version of this happen to me on an airplane. Battery started dropping at like 1% every 20-30 seconds after enabling airplane mode. I killed every task I could find and it stopped. Seems like it's caused by an app that isn't checking for airplane mode before trying to make a connection. Never figured out what app it was but something similar could be causing the problem here.

Re-enable everything in autostarts and delete the app. Boot into recovery and wipe your battery stats, cache, and dalvik-cache. Turn off the phone and take the battery out for like 5-10 minutes and leave it somewhere without heat, like a dark closet. Put the battery back in and boot up the phone, turn on airplane mode and see if it does the same thing.

so you guys think autostarts could be causing the problem? from the way I understood the application, it does not run in the background - just modifies entries in the android system to avoid triggers calling programs.
That said thanks for the suggestion and I will try it out!

Also did you just flash it, because if you did you should wipe your cache, dalvik-cache, and battery stats. Then recalibrate your battery.
Sent from my......ummm...let me get back at'chya!

knowledge561 said:
Also did you just flash it, because if you did you should wipe your cache, dalvik-cache, and battery stats. Then recalibrate your battery.
Sent from my......ummm...let me get back at'chya!
Click to expand...
Click to collapse
Yes, I just flashed and did a full wipe. I will try wiping the battery stats. How do you mean to recalibrate battery?
Thanks!

berardi said:
Yes, I just flashed and did a full wipe. I will try wiping the battery stats. How do you mean to recalibrate battery?
Thanks!
Click to expand...
Click to collapse
Its like re-energizing your battery so to speak. Go to the market and download the "Battery Calibration" app. Follow the steps in the app and it does it for you.

New type of battery drain

I got a good setup going, battery last the same pretty much everyday. I shutdown, 3 finger reboot to recovery and do a backup. When its done I hit reboot, phone boots back up normally. But all of a sudden battery life starts draining fast. Now if I do the same thing but instead before reboot, wipe cache and dalvik. Battery is back to lasting like it was. It only does this after backups, all other shutdowns and reboots are good. I'm using acs recovery 1.0.5. Anybody know why that would be?
Sent from my SPH-D700 using Tapatalk

DaKillaWilla said:
I got a good setup going, battery last the same pretty much everyday. I shutdown, 3 finger reboot to recovery and do a backup. When its done I hit reboot, phone boots back up normally. But all of a sudden battery life starts draining fast. Now if I do the same thing but instead before reboot, wipe cache and dalvik. Battery is back to lasting like it was. It only does this after backups, all other shutdowns and reboots are good. I'm using acs recovery 1.0.5. Anybody know why that would be?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me too. I was at 64% battery life and I reboot my phone and I am down to 19% weird?

You're supposed to recalibrate that battery. Also, a reboot does sip at your battery, it has to boot , then does a double media scan of your entire sd card.

Jamice4u what you saw was the battery stats reboot bug. Different problem. Do not reboot below 70% unless plugged into a charger or pull your battery out for a few minutes if this happens and it will go back to what you had. This is the workaround.
Sent from my SPH-D700 using XDA App

S3 Massive battery and "Android System" usage with and without charging

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