Related
So i rooted my evo and installed a custom rom pretty much as soon as I had it out of the box. And then started installing apps. And i've pretty much NEVER had a fully charged battery last for a whole day even with very little to no usage of the phone.
A few days ago my friend also got an evo but hasn't rooted it or installed any apps yet. And he is easily getting TWO days or more out of a charge.
so i decided to do a full wipe of my phone, and what do you know, I'm suddenly getting 2 days out of the battery, maybe even a little more then 2 days.
Previously, i had setcpu installed as well as system panel. And i was never able to figure out what was draining the battery. When i looked in system panel the only thing that was using the cpu a little bit was system. Pretty much every other app listed was showing 0.1% of cpu usage.
So i'd like to know if there's a better method to figure out what's draining the battery. Do I have to install apps one at a time and wait a few hours/a day to see if the battery starts going down? or is there a better method?
thanks
I always check the awake time versus the time on. If the wake time is very high that means there is an app acting up.
What I'll do to investigate which app is I'll just go to the little stock battery report thing and look at what is using my battery.
Also, it should be noted that be wary of the facebook app. That thing is a complete and total battery hog. It was draining my battery from 20% over the course of an hour.
I was checking the stock battery report - it wasn't showing me anything useful when the battery was going dead.
right now i'm getting amazing battery life compared to before.
90 minutes since the phone was unplugged and it's only down to 96% and that's with me using it a bit. Previously, it would have been down to 85-80% by now.
I just have no clue at all what was causing the drain. I was hoping there was a better method other then installing apps one at a time until the battery starts draining to figure out the culprit.
There's an app called Watchdog and it monitors the background activity happening on your phone. If some seems to be getting out of hand it will notify you.
I had the same problem I installed Smobile security and it was KILLING my battery. Watchdog was able to tell what it was.
Hope this helps.
It looks like watchdog does basically the same thing that system panel does. and system panel wasn't showing me anything unusual. System panel shows the cpu usage of apps - and none of my apps were showing high cpu usage.
I guess there's really no app that can actually show you the battery usage per app - it can only show you the cpu usage.
You can try SpareParts from the Market,it may help you see if you have a wakelock issue of some kind and its free so no harm if it doesn't help.
BrianBusby2038 said:
You can try SpareParts from the Market,it may help you see if you have a wakelock issue of some kind and its free so no harm if it doesn't help.
Click to expand...
Click to collapse
actually, the rom i am using already has spareparts in it. I'm not sure what you mean by wakelock though. How do i determine that? What is it?
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
Hey everybody,
Just made the jump from the iPhone 4S and have done the custom ROM/kernel thing the past week. Things were good at the start but I feel them slowly deteriorating.
I find my battery life during sleep has become much worse than before. I mean, it still kills the 4S which would see ~25% overnight. But I'm seeing 10% overnight right now, and was ~2% earlier in the week. I normally have my phone on the charger at night, but didn't last night and I'm kinda glad I got to see this. Makes me realize why I was likely chewing through more in the day too.
You can see what I'm running below in my signature. Last night I had 5 instances where the phone woke on its own. Likely due to emails coming in.
Am I expecting too much from my modifications? Am I doing something wrong? I'm ready to toss AOKP aside because of other issues anyway, but yesterday I also read it was known to have some excessive battery drain as well. Without turning this into a battle to defend the ROM you use (like half the threads in here), if you have other suggestions, feel free to throw in a ROM suggestion. I'll attach some pictures of my battery screen so anyone willing to give me a hand can help.
Thanks in advance.
I had this problem when I was running franco too. Switched to leankernel and never looked back. I get about 4-6% drain overnight as long as I dont do something stupid like leave something running by exiting with home instead of the back button. I also have wifi on 24/7 and gps off unless im nav'in. No BT
Screwedupsmitty said:
I had this problem when I was running franco too. Switched to leankernel and never looked back. I get about 4-6% drain overnight as long as I dont do something stupid like leave something running by exiting with home instead of the back button. I also have wifi on 24/7 and gps off unless im nav'in. No BT
Click to expand...
Click to collapse
I'm hesistant to blame the kernel. I was using franco prior to AOKP without issue. I didn't make that clear in the OP. I went 4.0.4 Stock -> Stock + franco -> AOKP b31 + franco. Things were good the first two steps and I'd like to think the first few days on AOKP.
Perhaps I have some background processes chewing battery - but there's nothing with a higher battery drain than Chrome beta with 2%. My phone idle and Cell standby had huge drain though. Could a weaker than normal signal cause this? Could my radio be the culprit?
Steps to best diagnose idle battery drain.
-Install CPU Spy and Better Battery Stats.
-Charge phone to full and let it run for several hours undisturbed (easiest to charge before bed, then unplug it when you know it won't be used till morning).
-Take quick note of your % loss per hour. Around 1%, you're golden. 1-2 is pretty normal. >3 and you've got issues.
-Launch CPU Spy. Most of the time should be deep sleep (we're talking about 95%). If your phone has been awake a lot, there's either an app that refuses to let your phone rest, or an OS/Kernel issue. If it's not extreme but noticeable, you likely just need to reign in settings on some apps to keep them from syncing so often or working in the background.
-Launch Better Battery Stats. Select Partial Wakelocks from the menu. These are all cases of apps waking the phone up, sorted by length. Go look at problem apps' settings/consider uninstalling if you don't need them. Kernel wakelocks should be low too.
Keep in mind that the goal here isn't really to get all these things to zero so do not obsess over small showings. Facebook with push notifications but updates set to never keeps my phone awake for about a minute or two every night, for instance. So does Handcent SMS. If you flash a rom and your phone needs to do a lot of syncing it's likely to show up in this kind of test as well. But for a night with nothing going on, nothing should be keeping your phone up for more than a few minutes total.
myrdog said:
I'm hesistant to blame the kernel. I was using franco prior to AOKP without issue. I didn't make that clear in the OP. I went 4.0.4 Stock -> Stock + franco -> AOKP b31 + franco. Things were good the first two steps and I'd like to think the first few days on AOKP.
Perhaps I have some background processes chewing battery - but there's nothing with a higher battery drain than Chrome beta with 2%. My phone idle and Cell standby had huge drain though. Could a weaker than normal signal cause this? Could my radio be the culprit?
Click to expand...
Click to collapse
Weaker than normal signal can kill a phone battery, when I'm in lecture out in the bumfuck nowhere school I go to, I get -100 to -120dbm, which kills my battery while i'm at school. If thats your situation not much to do besides hope radios may increase your signal, but if not then your basicly as SOL as i am and may have to just charge it
JoeSyr said:
Steps to best diagnose idle battery drain.
-Install CPU Spy and Better Battery Stats.
-Charge phone to full and let it run for several hours undisturbed (easiest to charge before bed, then unplug it when you know it won't be used till morning).
-Take quick note of your % loss per hour. Around 1%, you're golden. 1-2 is pretty normal. >3 and you've got issues.
-Launch CPU Spy. Most of the time should be deep sleep (we're talking about 95%). If your phone has been awake a lot, there's either an app that refuses to let your phone rest, or an OS/Kernel issue. If it's not extreme but noticeable, you likely just need to reign in settings on some apps to keep them from syncing so often or working in the background.
-Launch Better Battery Stats. Select Partial Wakelocks from the menu. These are all cases of apps waking the phone up, sorted by length. Go look at problem apps' settings/consider uninstalling if you don't need them. Kernel wakelocks should be low too.
Keep in mind that the goal here isn't really to get all these things to zero so do not obsess over small showings. Facebook with push notifications but updates set to never keeps my phone awake for about a minute or two every night, for instance. So does Handcent SMS. If you flash a rom and your phone needs to do a lot of syncing it's likely to show up in this kind of test as well. But for a night with nothing going on, nothing should be keeping your phone up for more than a few minutes total.
Click to expand...
Click to collapse
This is what every user should use to diagnose battery problems at first.
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
How much does your Jellytime ROM drain from battery? Using battery e.g. Battery monitor widget, I can see 60mA drain when phone is standby. Seems to be a lot for me. I didn't find comparsion just subjective claims - high/low drain. 60mA is with wifi turned off, bt disables, no gprs/3g data, just standby. No application seems to be running. Battery stat shows that 60 % is display (but I can confirm that display is off), 40 % cell stand by and about the same amount phone idle.
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
xbiggyl said:
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Thanks, I will try it. So far I was using Battery Monitor apk. However, I have no reference if my battery drain level is expected for that rom or not.
I'm also having issues with battery drain on JT... really strange. It seems to have drain when in standby, and when the screen is on it goes like crazy, I can't get more than like 20-30 minutes of screen-on time. I really like this ROM, it is pretty stable and works fine, no major bugs but the battery drain is crazy. I took a couple of screenshots. It seems that process Media is keeping it "awake" and causing battery drain. In all other ROMs I used (and in stock) I have never seen any other process except SCREEN using more than couple of percent of battery. Now this media process is using almost as screen! Any clues as what it is?
Also, I noticed that it discharges quickly when screen is on, but it also charges quickly! Something wrong with battery stats? It simply can't go from 20% to 70% in 10 minutes while charging?
xhejtman said:
How much does your Jellytime ROM drain from battery? Using battery e.g. Battery monitor widget, I can see 60mA drain when phone is standby. Seems to be a lot for me. I didn't find comparsion just subjective claims - high/low drain. 60mA is with wifi turned off, bt disables, no gprs/3g data, just standby. No application seems to be running. Battery stat shows that 60 % is display (but I can confirm that display is off), 40 % cell stand by and about the same amount phone idle.
Click to expand...
Click to collapse
Its about 1% per hour about the battery drain..quite good battery with usage
KeshavJave said:
Its about 1% per hour about the battery drain..quite good battery with usage
Click to expand...
Click to collapse
Hmm, could you provide mA value (battery monitor shows it in history in 10 minutes intervals..)
I can do five hours with normal use on a full charge..
These are battery stats for my DHD. The first one is standby over night with stok HTC ROM (2.3.5), the second one is with JellyTime ROM 9.1. It takes 10times more power.
marclooman9 said:
I can do five hours with normal use on a full charge..
Click to expand...
Click to collapse
That's not much. Was it better as long as you can remember with stock HTC ROM? I could do 2-3 days with normal use with stock ROM.
xhejtman said:
That's not much. Was it better as long as you can remember with stock HTC ROM? I could do 2-3 days with normal use with stock ROM.
Click to expand...
Click to collapse
Wow 2 to 3 days? Last time I had a phone like that was back in non smart phone days...
ai6908 said:
Wow 2 to 3 days? Last time I had a phone like that was back in non smart phone days...
Click to expand...
Click to collapse
Yes, but my cost for 2-3 days is: no gsm data, no wifi (or wifi for something like 5 minutes), no widgets except htc clock & weather, almost no background apps, few phone calls, moderate number of sms. (Yes I hear you saying, you don't need 'smart' phone , I do, I use some apps but not too frequently, so avg running time from 100% to say 10% of battery was 2-3 days, mainly depending on number of sms sent
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
dalanik said:
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
Click to expand...
Click to collapse
perhaps try to install: http://play.google.com/store/apps/details?id=ccc71.bmw
it provides history of current consumption, that can tell whether it is a lot or not.
Btw, what do you exactly mean by "played for 10m"? What did you do?
xhejtman said:
Btw, what do you exactly mean by "played for 10m"? What did you do?
Click to expand...
Click to collapse
Thanx for the tip, I'll try installing the app you suggest. "Played" means I turned the screens on louncher a couple of times to update all widgets, went into settings, looked at the battery stats etc. Maybe lounched foursquare and titanium backup, nothing really intensive... Here are shots from batterystats. Seems to me media service is doing it...
dalanik said:
Thanx for the tip, I'll try installing the app you suggest. "Played" means I turned the screens on louncher a couple of times to update all widgets, went into settings, looked at the battery stats etc. Maybe lounched foursquare and titanium backup, nothing really intensive... Here are shots from batterystats. Seems to me media service is doing it...
Click to expand...
Click to collapse
yes media service seems to be suspicious. It says, the phone was in deep sleep only half an hour for last hour while screen on was really only for about 10 minutes. I think the problem is in remaining time. I am not really familiar with bbs logs, maybe post the log into BBS thread here on XDA for help if you cannot figure it yourself.
dalanik said:
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
Click to expand...
Click to collapse
There is no need for wiping battery stats.
Once your phone recharges to 100%, battery stats reset by default.
xbiggyl said:
There is no need for wiping battery stats.
Once your phone recharges to 100%, battery stats reset by default.
Click to expand...
Click to collapse
I know, I read that somewhere, but just wanted to be sure This is really driving me nuts, I always have to be near charger
xbiggyl said:
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Ok, I figured out, what is causing high battery drain. It FM radio. After clean flash and basic setup, it consumes 10mA when standby. Which is twice more than with stock ROM, but seems to be acceptable. If I run and then exit Sprite FM radio app, phone starts to consume 60mA until reboot. After reboot, it is ok, until I run Sprite FM app again.
However, BBS does not show anything useful. Maybe because of FM HW keeps running? There is shown no SW battery eater..
I still can't figure it out Here's log of consumptuon in standby from last night, I have it set on profile manager to turn off data and set airplane mode from 1am-7am. Looks good to me, can someone confirm these are OK values?
Code:
2012/09/24|00:28:43|587mA|60%|4182mV|34.0ºC|.258|1
2012/09/24|00:29:43|529mA|60%|4182mV|34.0ºC|.100|1
2012/09/24|00:39:43|-61mA|60%|3869mV|32.0ºC|.256|2
2012/09/24|00:49:43|-11mA|59%|3960mV|27.0ºC|.0|0
2012/09/24|00:59:43|-28mA|59%|3957mV|25.0ºC|.0|0
2012/09/24|01:09:43|-18mA|59%|3960mV|23.0ºC|.0|0
2012/09/24|01:19:43|-8mA|59%|3957mV|22.0ºC|.0|0
2012/09/24|01:29:43|-10mA|58%|3940mV|22.0ºC|.0|0
2012/09/24|01:39:43|-13mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:49:44|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:59:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:09:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:19:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:29:43|-7mA|57%|3945mV|21.0ºC|.0|0
2012/09/24|02:39:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|02:49:44|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|02:59:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:09:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:19:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:29:44|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:39:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:49:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:59:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:09:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:19:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:29:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:39:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:49:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:59:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:09:43|-10mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:19:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:29:43|-13mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:39:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|05:49:44|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|05:59:43|-12mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:09:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:19:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:29:43|-7mA|53%|3891mV|20.0ºC|.18|0
2012/09/24|06:39:43|-7mA|53%|3891mV|20.0ºC|.0|0
2012/09/24|06:46:44|-210mA|53%|3740mV|21.0ºC|.0|0
2012/09/24|06:56:44|356mA|57%|4187mV|24.0ºC|.3|6
2012/09/24|07:00:44|-264mA|71%|3816mV|25.0ºC|.360|2
2012/09/24|07:10:44|-254mA|51%|3721mV|24.0ºC|.1000|0
2012/09/24|07:20:44|-32mA|36%|4174mV|24.0ºC|.736|6
2012/09/24|07:30:44|397mA|75%|3933mV|26.0ºC|.3|2
2012/09/24|07:40:44|-61mA|73%|3784mV|26.0ºC|.76|0
2012/09/24|07:50:44|-121mA|63%|3779mV|26.0ºC|.450|0
2012/09/24|08:00:44|-233mA|44%|3730mV|26.0ºC|.998|0
2012/09/24|08:10:44|-125mA|37%|3769mV|27.0ºC|.200|0
2012/09/24|08:19:36|607mA|55%|3850mV|27.0ºC|.1|1
2012/09/24|08:29:35|611mA|64%|4187mV|28.0ºC|.130|1
2012/09/24|08:39:35|426mA|69%|4189mV|28.0ºC|.0|1
2012/09/24|08:49:18|136mA|94%|4087mV|27.0ºC|.8|3
But look at the 2nd attached screenshot, at the end of the graph - how fast it charges, isn't that unusual?
Code:
2012/09/24|00:28:43|587mA|60%|4182mV|34.0ºC|.258|1
2012/09/24|00:29:43|529mA|60%|4182mV|34.0ºC|.100|1
charging at rate 500-600mA, is it external charger? I do charging on ntb and it's up to 400mA when battery is not close to 100%.
Code:
2012/09/24|00:39:43|-61mA|60%|3869mV|32.0ºC|.256|2
2012/09/24|00:49:43|-11mA|59%|3960mV|27.0ºC|.0|0
2012/09/24|00:59:43|-28mA|59%|3957mV|25.0ºC|.0|0
2012/09/24|01:09:43|-18mA|59%|3960mV|23.0ºC|.0|0
2012/09/24|01:19:43|-8mA|59%|3957mV|22.0ºC|.0|0
2012/09/24|01:29:43|-10mA|58%|3940mV|22.0ºC|.0|0
2012/09/24|01:39:43|-13mA|58%|3955mV|21.0ºC|.0|0
seems to be of slight using or runnign backgroud processes this hour?
Code:
2012/09/24|01:49:44|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:59:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:09:43|-7mA|58%|3955mV|21.0ºC|.0|0
this is expected consumption, with stock HTC ROM I got -3 - -5mA, but -7mA is pretty good. With R10 I got -10mA, don't know why it does sleep less than it should.
Code:
2012/09/24|06:46:44|-210mA|53%|3740mV|21.0ºC|.0|0
2012/09/24|06:56:44|356mA|57%|4187mV|24.0ºC|.3|6
2012/09/24|07:00:44|-264mA|71%|3816mV|25.0ºC|.360|2
2012/09/24|07:10:44|-254mA|51%|3721mV|24.0ºC|.1000|0
what happened here? -264mA is a lot of power consumption, do you remember what did you do? Common usage should be around -100mA.