Battery discrepancy between booted and 4EXT - HTC Sensation

Noticed this morning after a full night of charging that when booting into recovery my battery says it is only at 81%. When I was booted into my ROM the screen read fully charged! I wiped battery stats YESTERDAY. Can anyone tell em what I might be seeing here?
Running KANG 4.1.1 8-12 build and using 4EXT. Stock kernel.

shahkam said:
Yeah I think recovery has some issue reading the battery ..
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
It just got a little weirder...
So first the phone said full and recovery said 71, went ahead and wiped battery stats again and rebooted the phone. After that they matched. I turned my phone off to let it charge up a little faster. When I rebooted I went straight to recovery where it said full, a welcome change to my previous issue. But then when I booted up, my battery was LOWER THAN BEFORE! Down to 68%?!?! All this after a good 20 minutes of phone off charging.
Maybe I'm worried about nothing, but the phone is over a year old now. Is it time for a new battery? Or do you still think it is just a number and there is nothing to worry about?

awacker89 said:
It just got a little weirder...
So first the phone said full and recovery said 71, went ahead and wiped battery stats again and rebooted the phone. After that they matched. I turned my phone off to let it charge up a little faster. When I rebooted I went straight to recovery where it said full, a welcome change to my previous issue. But then when I booted up, my battery was LOWER THAN BEFORE! Down to 68%?!?! All this after a good 20 minutes of phone off charging.
Maybe I'm worried about nothing, but the phone is over a year old now. Is it time for a new battery? Or do you still think it is just a number and there is nothing to worry about?
Click to expand...
Click to collapse
Can you please google the "Deleting battery stats myth android" and then read the google plus post by the google engineer.
Wiping battery stats doesnt solve/create any issues, it gets deleted everytime phone is charged to ~90% by the OS anyway

I'd love to take a look at that, although I gotta say I'm positive after the way the rest of my morning went that there is definitely SOMETHING going on. After repeating this full battery followed by a stats wipe again I was at 82% immediately after the power up and it took 3 hours to reach fully charged status again. Oh well, I can see I've irritated someone so I'll just sleep well in the fact that my phone is running like a dream on JB, strange battery stats aside.
Sent from my HTC Sensation using xda app-developers app

awacker89 said:
I'd love to take a look at that, although I gotta say I'm positive after the way the rest of my morning went that there is definitely SOMETHING going on. After repeating this full battery followed by a stats wipe again I was at 82% immediately after the power up and it took 3 hours to reach fully charged status again. Oh well, I can see I've irritated someone so I'll just sleep well in the fact that my phone is running like a dream on JB, strange battery stats aside.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Recovery and OS always report slightly different values. I would take the recovery as the true value but after ~5 of the OS booted the battery level quickly drops to the same level as the recovery, closer to the true value

Related

[Q] Can't boot after Batterystats.bin wipe

Alright, so to get to the point, I pretty much finally got my phone setup and stable, but when I tried to reset the batterystats.bin to hopefully lengthen my battery life, I found myself staring at the lovely HTC boot screen for 13 minutes straight before pulling the battery and just leaving it on the charger. Does anyone know what I did wrong, or what even went wrong?
ROM = LeeDroid 2.2.2
Kernel = LeeDroid 2.2.8
StarzSpirit said:
Alright, so to get to the point, I pretty much finally got my phone setup and stable, but when I tried to reset the batterystats.bin to hopefully lengthen my battery life, I found myself staring at the lovely HTC boot screen for 13 minutes straight before pulling the battery and just leaving it on the charger. Does anyone know what I did wrong, or what even went wrong?
ROM = LeeDroid 2.2.2
Kernel = LeeDroid 2.2.8
Click to expand...
Click to collapse
I read somewhere that you have to charge phone to 100% and then wipe. Not sure if that's the case.
Well if that's the case, I was at 100% according to the phone(after boot up), but the battery itself might of not been at 100%. I'll try charging it to 100 percent, before wiping it, but as of right now, I can't even turn off my phone. Well... I can, but clockwork keeps turning itself on and just sitting there, I can't like fully turn off the phone and let it charge.
StarzSpirit said:
Well if that's the case, I was at 100% according to the phone(after boot up), but the battery itself might of not been at 100%. I'll try charging it to 100 percent, before wiping it, but as of right now, I can't even turn off my phone. Well... I can, but clockwork keeps turning itself on and just sitting there, I can't like fully turn off the phone and let it charge.
Click to expand...
Click to collapse
Reflash to stock?
I can't afford to do all that work as of right now, I'm very busy, and I'm hoping that I can just get a simple reset of the battery. It seems pretty senseless that the whole ROM and Kernel must fall with simple reset of the battery. All I ask for, is a few more hours of life on my phone, not a nights work of re-doing everything that I have accomplished... If I must though, I will.
Don't you have a recent nandroid backup you can restore?
I do, but unfortunately, it's the downgrade that I used to S-OFF, Root, and all that other jazz, I never thought of doing a backup over something that seemed so measly. I guess I was wrong.

Some more crazy battery antics

So a couple weeks ago I went to bed with my phone unplugged with maybe 80% juice left. Woke up, phone was completely dead and refused to turn on, even after sitting on a charger for 20 minutes. The only way I was able to get it to boot was through recovery. I checked my battery stats and it showed that it dropped steadily to maybe 65% over the course of 4 hours and then dropped straight to zero from 65%. I chalked it up to issues with my ROM because I was having other quirks here and there. The other day I flashed CleanROM 4.5 and everything was gravy. I also flashed the radio from 2.20 and had great signal and LTE speed increases after the flash.
Last night I decided to see how well my phone was sleeping so I took it off the charger at about 11 with 100% charge. When I unplugged it the phone was very warm and was reading about 110 F. I killed everything just to be safe. This morning at 8 my phone was down from full to 75%. WTF. I used to lose MAYBE 2% over night so 25% is a massive drop for me. I plugged it in to my MBP to charge (like I always do) and as soon as I did I got a warning message saying my phone was using more current than the charger could output and the battery dropped instantly from 75% to 18%. I am going to flash a different radio but I am not hopeful that it will solve this considering it has happened with two completely different ROM/Radio combos. I have checked betterbatterystats and even had system panel on monitor all night and nothing was out of the ordinary. Cell standby was at the top of the list in the stock battery stats but that seems normal to me considering I didn't turn the screen on once. There was no time without signal. Has anyone else experienced this issue? What do you guys think- hardware or software?
Couple weeks ago, sometime after flashing the rooted stock 2.23 and 2.23 radio, I had the issue of the battery being dead overnight. It was something like 70% when I went to bed, so I was surprised it died. I typically get more drainage while idle than you, but still usually only 2 to 3% per hour. Even less on the 2.23 radio, around 1.5% (or less) an hour while idle.
Hasn't happened since. I'm still wondering what happened?
This happened to me once as well, dropped from 70% to completely dead overnight. I could not figure out why, but it hasn't recurred.
It's a virus!
Sent from my HTC One X using xda premium
I'm having a ton of awake time with very little screen on time when using aokp/cm10.
Sent from my One X using xda app-developers app
Yeah I have no idea what's going on. Now it seems to be fine, and I haven't done anything to it yet. Took it off the charger at noon with about 80% on it, now it's almost 9 and I'm at 65% with 33min screen time and 30 minutes of voice calls. Pretty good for only a 15% drop. Really confused. Gonna charge it up all the way and unplug it again before bed to see if the same thing happens again.
ECEXCURSION said:
It's a virus!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Oh noes! Maybe I should get an iPhone?!
_MetalHead_ said:
Oh noes! Maybe I should get an iPhone?!
Click to expand...
Click to collapse
Definatly.
My battery has been absolute crap the last 2 days but that's just from installing google now I think. Going to have to revert to my backup soon.
Last night I went to bed with 83%, woke up 7 hours later with the same 83%. This is madness I tell you. Madness.
Just my hunch, a dead vertical drop on the battery meter (you mentioned it had dropped straight from 65% to zero?) is just an error in the meter reading, and the "later" reading is the correction. I would think such an instantaneous (or near instantaneous) drop in actual voltage is improbable, if not impossible. But I'm just a dump civil engineer, not an electrical.
I've seen a vertical drop once. Others have reported seeing it repeatedly. In those cases, a factory reset seems to fix it, but flashing a ROM (with the usual data and cache wipes) would seem to do the same.
I've seen it twice now, across two different ROM/radio configs. I'll just chalk them up to random flukes and go about my merry way.
_MetalHead_ said:
I've seen it twice now, across two different ROM/radio configs. I'll just chalk them up to random flukes and go about my merry way.
Click to expand...
Click to collapse
sir, i sent you a pm .. can you have a look ?
dullhunk said:
sir, i sent you a pm .. can you have a look ?
Click to expand...
Click to collapse
Just replied. Sorry for the delay.

My S3 battery dies at around 20% on the regular? wtf

So i've searched and not came up with anything. Im on a custom ROM and have recently noticed my phone will completely die when it says around 22-20%. I've changed ROMS and even went to JellyBean recently with no luck. I've reset battery stats, no go. Any suggestions beside taking the battery back to VZW? Im going to leave my phone turned off, and charge like that tonight to see if anything else changes.
It seems that its a battery issue. Nothing software related. Are you using a custom kernal?
Sent from my SCH-I535 using xda app-developers app
Bump for the EXACT same issue. My battery has died for the past three days when the phone is between 20-22%. I'm on Synergy rom with no custom kernel. I've ordered some extra batteries so I'll have a better understanding in the next week or so if it's the phone or the battery. Any feedback/suggestions would be great.
Also note that the phone gives me zero warnings that it's about to die. No flashing lights, low battery indicator, nothing. I'm usually using the phone and it completely powers off without a seconds notice, as if the screen has dimmed. Trying to power it back on just produces a light vibration but no led or screen activity until it's connected to a charger.
joshw0000 said:
Bump for the EXACT same issue. My battery has died for the past three days when the phone is between 20-22%. I'm on Synergy rom with no custom kernel. I've ordered some extra batteries so I'll have a better understanding in the next week or so if it's the phone or the battery. Any feedback/suggestions would be great.
Also note that the phone gives me zero warnings that it's about to die. No flashing lights, low battery indicator, nothing. I'm usually using the phone and it completely powers off without a seconds notice, as if the screen has dimmed. Trying to power it back on just produces a light vibration but no led or screen activity until it's connected to a charger.
Click to expand...
Click to collapse
Did the new batteries help? i just started having the same issue. Verizon was nice enough to send me a new battery which should arrive in a few days
fatalfuryy said:
Did the new batteries help? i just started having the same issue. Verizon was nice enough to send me a new battery which should arrive in a few days
Click to expand...
Click to collapse
Yes and no. I'm no longer having the issue anymore but I don't think it was the battery. I was a making a backup so I could install GW. Instead of booting to TWRP, I accidentally went to Download Mode. I couldn't figure out how to get out so I pulled the battery. I then booted to recovery, backed up, wiped cache, and flashed GW.
I didn't have the issue for a couple more days until I received the new batteries and haven't had to use the stock battery since getting the others. Still no issues (knock on wood).
I think one of the following fixed it:
Wiping cache
Booting to download mode
Pulling the battery
Sent from my SGH-I535 using Tapatalk 2
Bump...anyone have any luck? Same exact thing is happening to me...except my screen flickers a bit before dying.

Battery indicator doesn't drop below 23% and then dies.

I am stock, rooted and unlocked just before the last minor OTA. My battery has been dying on me a lot recently because it keeps showing that I'm at around 23% when it's low. So I've never received the low battery warning, and after a while it just shuts off and doesn't turn back on... so it obviously drained.
I'm gonna try clearing battery stats in CWM after a full nights charge, but was wondering if anybody has an explanation for this? Or possibly any other solutions other than clearing battery stats.
Again, I'm running Stock ROM, rooted, and unlocked. The last OTA has not been installed and fails when it tries. The only other thing I have flashed is Google Now.
Please help, this glitch is seriously killing my battery because it keeps draining down to 0 before i even know it.
you dont have to wait for a full charge to wipe battery stats...sounds like the battery is going bad imo.
wiping stats didnt do anything... I'm back at being stuck at 23% as i type.
And a battery going bad after 3 months?? My Incredible's battery is still working just fine after 2+ years now.... Is it really possible for a battery to crap out this quick?
KrisPeezy said:
wiping stats didnt do anything... I'm back at being stuck at 23% as i type.
And a battery going bad after 3 months?? My Incredible's battery is still working just fine after 2+ years now.... Is it really possible for a battery to crap out this quick?
Click to expand...
Click to collapse
Batteries usually last around 1-2 years then they start to degrade.
There will be times where the battery you get will be defective. Just go to the Verizon store and show them. They will be happy to replace it.
ya i would say the battery is going bad too
Sent from my SCH-I535 using xda app-developers app
Ok, I'll try to go into the verizon store some time next week.
I'm gonna take some screen caps of the battery drain to show them. And maybe I'll bring it in when it's at that 23% point...
I Should probably unroot and lock before i bring it in right?
KrisPeezy said:
Ok, I'll try to go into the verizon store some time next week.
I'm gonna take some screen caps of the battery drain to show them. And maybe I'll bring it in when it's at that 23% point...
I Should probably unroot and lock before i bring it in right?
Click to expand...
Click to collapse
Try wiping the phone and getting that update or wipe and Odin the vrlhe update on. See if this does any thing for you you might end needing a new phone. But it could also just be the battery.
Wow! Same here dude. I've been off TW for a month, with it dying at exactly 23%. Yesterday, it did the same thing on JB TW. 23%.
Michael Jordan pissed at us or something? Using his magical powers to turn our phones off?
Sent from my SCH-I535 using Tapatalk 2
I'm running into the exact same issue with my one week old CLN phone and brand new battery. Battery meter will not drop below 23%. If I shut the phone down, remove the battery, and power it back on, it will start resuming normally but the problem happens again once I charge the phone back up.
Has anyone found a solution?
Edit: BTW, I am rooted/unlocked running Beans11 and ktoonz kernel.
Ive recently run into this issue as well, anyone find a solution?
Happened to me once. i switched rom/kernel
iSheep... iSheep... Meowww that's Apple VZW GSIII
KrisPeezy said:
I am stock, rooted and unlocked just before the last minor OTA. My battery has been dying on me a lot recently because it keeps showing that I'm at around 23% when it's low. So I've never received the low battery warning, and after a while it just shuts off and doesn't turn back on... so it obviously drained.
I'm gonna try clearing battery stats in CWM after a full nights charge, but was wondering if anybody has an explanation for this? Or possibly any other solutions other than clearing battery stats.
Again, I'm running Stock ROM, rooted, and unlocked. The last OTA has not been installed and fails when it tries. The only other thing I have flashed is Google Now.
Please help, this glitch is seriously killing my battery because it keeps draining down to 0 before i even know it.
Click to expand...
Click to collapse
This same excate thing happened to me. The cause, I used a hacked battery app. I tried everything to fix it, switched roms, kernels, wiped stats as many different ways as I could, but everytime I would be stuck at 23% till the phone died.
Restored all my apps without the battery montior app, let the phone do its thing, and its been fine.
Remove the app, wipe stats, reboot. Should work.
And I bet your using Battery monitor widget from 3c, aren't you?
Sent from my PACmaned SCH-I535

Galaxy S3 won't charge past 85%

I just a Verizon Galaxy S3 as "like new" replacement. I bought a new oem Samsung 2100mah battery for it. I have it rooted with Incubus JellyWiz rom at the moment. I had another rom before that as well. I have an issue with the phone not charging past 85%. The phone constantly shows the charging symbol and stays at 85% when plugged in and will actually start going down while still plugged in. When I unplug the phone the battery percentage will actually slowly go up to like 92% letting the phone sit idle. I tried wiping battery stats, but the problem is I can't wipe them at 100% because the phone won't get there. Any ideas? Is the battery bad or is it something with the phone itself. This is really annoying. I get good battery life it seems, just the battery % is out of wack
Dutt1113 said:
I just a Verizon Galaxy S3 as "like new" replacement. I bought a new oem Samsung 2100mah battery for it. I have it rooted with Incubus JellyWiz rom at the moment. I had another rom before that as well. I have an issue with the phone not charging past 85%. The phone constantly shows the charging symbol and stays at 85% when plugged in and will actually start going down while still plugged in. When I unplug the phone the battery percentage will actually slowly go up to like 92% letting the phone sit idle. I tried wiping battery stats, but the problem is I can't wipe them at 100% because the phone won't get there. Any ideas? Is the battery bad or is it something with the phone itself. This is really annoying. I get good battery life it seems, just the battery % is out of wack
Click to expand...
Click to collapse
Did it does this stock? First step for me when I get something wacky like this is to Odin back to stock, and see how it acts. Problem persists probably is a bad battery, if it goes away something somewhere got goofed up, reroot/unlock and go from there.
Sent from my SCH-I535 using xda app-developers app
Try cleaning dalvik cache... Someone had same problem in the Inspire 4G forum a couple of years ago and that's what it was..
nosympathy said:
Did it does this stock? First step for me when I get something wacky like this is to Odin back to stock, and see how it acts. Problem persists probably is a bad battery, if it goes away something somewhere got goofed up, reroot/unlock and go from there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I will try to Odin back to stock 4.0.4 first and see how that acts with the battery.
There is one seller on Amazon who was selling "oem" batteries that did not charge up completely, just as you described. Luckily I checked the reviews before purchasing. It's likely the battery itself.
Sent from my SCH-I535 using xda app-developers app
Try re setting battery stats .
I put the phone back to stock and problem is still there. Is it most likely a bad battery?
Did you try cleaning the dalvik cache?
Sent from my SCH-I535 using xda premium
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Looks like it works
Roland_D said:
Try cleaning dalvik cache... Someone had same problem in the Inspire 4G forum a couple of years ago and that's what it was..
Click to expand...
Click to collapse
I've dealt with this issue occasionally, both on my S3 running AOKP 4.2.2 and my wife's Fascinate running Cyanogenmod 4.2.2. A simple reboot while it's plugged in and charging has always cured it. Today, however, it stopped charging at 75%. After a reboot, it charged to 78% and stopped. Several more reboots didn't help. I cleared Dalvik, and my phone charged right up to 100%. Thanks for the advice.
scubamike said:
I've dealt with this issue occasionally, both on my S3 running AOKP 4.2.2 and my wife's Fascinate running Cyanogenmod 4.2.2. A simple reboot while it's plugged in and charging has always cured it. Today, however, it stopped charging at 75%. After a reboot, it charged to 78% and stopped. Several more reboots didn't help. I cleared Dalvik, and my phone charged right up to 100%. Thanks for the advice.
Click to expand...
Click to collapse
Mine had stopped at 95% (GN2 + PP 399 Rc2) and deleting the Dalvik fixed that instantly. So one can conclude the bat was charged, but something in the cache was preventing the display of charge to reach 100. Strange one!

Categories

Resources