Battery wont charge past 35%. - Desire HD Q&A, Help & Troubleshooting

I re-flashed my ROM last night (Runny Extreme Surprise.) Before this, I had no issues what so ever.
Now my battery seems to refuse to charge past 35%. After flashing the ROM and setting up a few minor apps, I drained the battery to 0%, charged the phone while off via AC (not USB) for about 5 hours and it still didn't get to the green light to say it's fully charged. I booted it up to see where it's at and it's at 35% and now seems to refuse to charge any further.
I tried this again, also deleting the battstats file (Just to be absolutelyyy sure) and got the same result.
Interestingly enough (i'm not sure if it's relevant), the phone says its current battery voltage is 4179mV, which is around the same it usually reports when it's been fully charged at 100% in the past.
Does anyone have any idea what may be going on here?

Go into recovery and check what percentage you have there. If it reports 100%, download the rom again and reflash.
Sent from a dream.

Teichopsia said:
Go into recovery and check what percentage you have there. If it reports 100%, download the rom again and reflash.
Sent from a dream.
Click to expand...
Click to collapse
It also reports 35% in recovery.
Any clue what that may indicate?

Denavar said:
It also reports 35% in recovery.
Any clue what that may indicate?
Click to expand...
Click to collapse
No idea. Perhaps the battery is failing? How old is it?
You can also try a few troubleshooting steps. Test another battery in your cell, different charger and so on.
Edit: test with a different stable GB rom for good measure. I doubt it's that but you never know.
Sent from a dream.

Related

Quick Battery Drop in Initial 10%

Hi all,
I am puzzled by my problem. I am using Virtuous 2.7 + King's BFS kernel #4.
My phone battery will drop quickly from 100% to 92% right after unplugged from the power cord. By quickly, I meant I did not use the phone, killed all tasks, and battery will drop to 92% literally in minutes.
Bump charging, wiping battery stats, wiping dalvik cache, killing all tasks are not helping at all. I don't have SetCPU, but someone in the forum mentioned they have SetCPU, and it is not helping either.
Is anyone having this problem? Does anyone have any idea on how to solve this?
Please help.
Thank you!!!
chillmeow said:
Hi all,
I am puzzled by my problem. I am using Virtuous 2.7 + King's BFS kernel #4.
My phone battery will drop quickly from 100% to 92% right after unplugged from the power cord. By quickly, I meant I did not use the phone, killed all tasks, and battery will drop to 92% literally in minutes.
Bump charging, wiping battery stats, wiping dalvik cache, killing all tasks are not helping at all. I don't have SetCPU, but someone in the forum mentioned they have SetCPU, and it is not helping either.
Is anyone having this problem? Does anyone have any idea on how to solve this?
Please help.
Thank you!!!
Click to expand...
Click to collapse
I spoke to RMK as well as others about this in IRC, doesn't look like anything we can do, deep in the HTC code I guess.
I have the same issue using SkyRaider 3.1. Battery is 100% then after 5-10 minutes drops down to low 90s. It bothered me at first but after several days of moderate to heavy use and still having almost 50% battery left at the end of the day, I just figured it was some kind of bug when reading the battery level at the beginning. How is your battery life overall? If it's like mine, then i wouldn't worry too much about it as long as it's lasting longer. I'm using the 1750mAh battery from Sedio.
I was having the exact same problems until I went back to stock everything and bump charged. Took the OTA for 2.2, rooted, custom recovery, bump charged, wiped stats and cache and now I'm good to go. I usually dont think crap like this works but it made a huge difference in battery life and stopped the 100-90% problems I was having.
KB
I found this on EVO forum, but I don't know how his solution works. I personally don't think this would be the solution.
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=704272
I am using the 1500 mAh battery.
My battery life is uptime around 24 hours and awake time around 6-9 hours depending on usage.
so you're not having the issue anymore, after going back to stock (non rooted) with the official OTA 2.2?
KB Smoka said:
I was having the exact same problems until I went back to stock everything and bump charged. Took the OTA for 2.2, rooted, custom recovery, bump charged, wiped stats and cache and now I'm good to go. I usually dont think crap like this works but it made a huge difference in battery life and stopped the 100-90% problems I was having.
KB
Click to expand...
Click to collapse
KB Smoka, so you don't have this problem anymore?
Do you think format the phone and wipe all the data will help?
Have anyone tried formating the phone?
I've searched and found that the cause is the phone saying the battery is charged fully when its not basically so to fix this after it goes to 100% while the phone is one then u should turn it off and let it charge fully from there
Sent from my ADR6300 using XDA App
superchilpil said:
I've searched and found that the cause is the phone saying the battery is charged fully when its not basically so to fix this after it goes to 100% while the phone is one then u should turn it off and let it charge fully from there
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I did bump charge this phone, but it still drops like crazy.
I'll try this out tonight.
Thanks!
Is this a once time fix thing or do you have to do it every time you charge?
bump charging 4 or 5 times in a row (basically bump as many times as you need to to get it to where the light turns green withing a minute of 2 or plugging it in again) and then wiping battery stats solved this for me... kinda.. i still have to bump twice, but after that it'll stay at 100 for a good while and work it's way down normally, no jumping 10% down..
superchilpil said:
I've searched and found that the cause is the phone saying the battery is charged fully when its not basically so to fix this after it goes to 100% while the phone is one then u should turn it off and let it charge fully from there
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That is bump charging. Something htc is unable or unwilling to fix.
The issue has been known for a while and you have to 'bump charge' every time to avoid the 5-10% drop.
Here's their response about fixing the "bump charge".
"Dear **********,
I understand you would like to know if an update has be released to help get a full charge on your battery without having to bump charge it. At this time we have no information about any updates being released to help resolve this issue on your device. If an update is released for your device you will receive a notification on your device that an update is available.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number ************.
Sincerely,
Victor
HTC"
melophat said:
bump charging 4 or 5 times in a row (basically bump as many times as you need to to get it to where the light turns green withing a minute of 2 or plugging it in again) and then wiping battery stats solved this for me... kinda.. i still have to bump twice, but after that it'll stay at 100 for a good while and work it's way down normally, no jumping 10% down..
Click to expand...
Click to collapse
Do you bump charge every single time you charge right now? It's pain in the butt if I have to bump charge everyday.
Yup every day. 4 or 5 times is way overkill though. Just charge phone until green, turn off (don't need to unplug), wait until it turns green then do the plug/unplug one more time.
ufvj217 said:
so you're not having the issue anymore, after going back to stock (non rooted) with the official OTA 2.2?
Click to expand...
Click to collapse
Went to stock (official OTA), rooted, custom recovery, bump charged, reset stats and cache and I'm good now.
I charged it to "full" while it was powered on. Once the light turned green I turned the phone off, charged again until the light turned green. Took about 25 minutes. Powered up in recovery wiped battery and cache and now I'm good. The key is after doing all this you have to let the phone completely die.
If you're wiping your battery stats after a bump charge, you will have this problem every time you don't bump charge.
If you wipe your battery stats after it goes green without a bump charge, you won't have this problem.
This is because the software thinks the bump charged battery levels equal 100% charge. A bump charge adds approximately 10 percent of charge.
Formatting your phone or any software changes won't actually do anything other than wipe your battery stats while your phone is not at bump charge levels.
vantagejuan said:
If you're wiping your battery stats after a bump charge, you will have this problem every time you don't bump charge.
If you wipe your battery stats after it goes green without a bump charge, you won't have this problem.
This is because the software thinks the bump charged battery levels equal 100% charge. A bump charge adds approximately 10 percent of charge.
Formatting your phone or any software changes won't actually do anything other than wipe your battery stats while your phone is not at bump charge levels.
Click to expand...
Click to collapse
I'll try this instead! I don't want to bump charge everyday! It's too troublesome.
chillmeow said:
Hi all,
I am puzzled by my problem. I am using Virtuous 2.7 + King's BFS kernel #4.
My phone battery will drop quickly from 100% to 92% right after unplugged from the power cord. By quickly, I meant I did not use the phone, killed all tasks, and battery will drop to 92% literally in minutes.
Bump charging, wiping battery stats, wiping dalvik cache, killing all tasks are not helping at all. I don't have SetCPU, but someone in the forum mentioned they have SetCPU, and it is not helping either.
Is anyone having this problem? Does anyone have any idea on how to solve this?
Please help.
Thank you!!!
Click to expand...
Click to collapse
The reason this happens is because the battery gets charged fully to 100%, and then is allowed to slowly drain back to 90% (or so) before it's charged back to 100% again. This is how Lithium batteries are charged.
Try this: charge the battery to 100%, and immediately disconnect it after it's full. Notice how the battery doesn't drop to the low 90's immediately.
The reason "bump charging" appears to work is because there is no drain on the battery, since the phone is off. It goes to 100% and stops.
There's nothing we can do code-wise to fix this; it's just how the battery technology works. Keeping it fully charged at 100% while on would damage the charging capacity of our phones.
Btw.. wrong forum.
Solutions in search of a problem
Let me preface this by saying that I’m not an electrical engineer, or any sort of expert on phone hardware, but I think a couple issues are being confused. I’ve seen many posts about this battery “problem” here and elsewhere and an important point is being missed. People are confusing what the battery is actually doing with what the phone SAYS the battery is doing. They are NOT the same thing. The battery is a physical device and it will do what it’s going to do.
Battery life is a function of battery quality, initial state of charge, and demand. If you want the battery to last longer, look at ways of reducing demand. What applications are in use? How long is the screen on? What brightness level? Overclocking and undervolting settings? All these will affect ACTUAL battery life.
At lot of the “solutions” discussed have nothing to do with conserving energy use, but have everything to do with messing with how the phone REPORTS the state of charge. A good example is the issue of the initial drop reported by many users during the first few minutes after unplugging the charger. I see this on my own phone. If the phone is “taught” that 100% charge is when it is totally crammed with juice and plugged in as well, it’s not surprising that there is a good bit of voltage drop (+/- 10%?) right after unplugging. Does this mean there is a problem? NO! It’s just the battery doing what batteries do. A lot of the suggestions about wiping battery stats and such have nothing to do with saving energy. They are ways of fiddling with how the phone REPORTS its condition under various circumstances.
My advice: if you are happy with how your battery lasts, over the course of a day or so, then learn to relax, crack open a cold brew, and revel in just what a great phone the Incredible is. If your battery isn’t lasting as long as you need it to, then look at ways to save power or get a larger capacity battery. Tweaking the battery meter function is simply a feel-good exercise and won’t get you any actual improved performance. END OF RANT.
I can confirm that my gf's phone and my good buddies phone(both were never rooted) have never had a problem with the phone charging up slow first off(both phones charge about 1% per minute). And since they accepted the OTA, have not had the problem of charging to 100% and quickly jumping down to 90%. For instance, the other day my buddy charged his phone while on to 100%, played a game for about 2 minutes and closed it, battery was at 99%. Now I have tried and continually try every possible solution to my battery dying quick and charging slow, but am realizing that this must just be the cost of customizing my phone to my liking. And at least for the moment, a stock 2.2 DINC is just not an option for me.
larsrya8 said:
The reason this happens is because the battery gets charged fully to 100%, and then is allowed to slowly drain back to 90% (or so) before it's charged back to 100% again. This is how Lithium batteries are charged.
Try this: charge the battery to 100%, and immediately disconnect it after it's full. Notice how the battery doesn't drop to the low 90's immediately.
The reason "bump charging" appears to work is because there is no drain on the battery, since the phone is off. It goes to 100% and stops.
There's nothing we can do code-wise to fix this; it's just how the battery technology works. Keeping it fully charged at 100% while on would damage the charging capacity of our phones.
Btw.. wrong forum.
Click to expand...
Click to collapse
Sorry that I posted in the wrong forum. I thought this is related to the kernel or ROM I am using (Which is development right????).
Not to question your knowledge about the "battery technology", but why is it only happening to certain people? Nowadays most device are using Li-ion battery, why this phenomenon do not occur to all devices?

[Q] Phone won't charge to 100% unless turned off?

I have a problem with my phone hanging at 93-97% when charging. I have to turn it off and within a minute or two it shows that it is fully charged. I'm wondering if anyone has ran across this problem and is it the phone or something else? It does this across all the ROM's and kernel combos that I have used over the last few months and I can't figure it out.
gajendarksky said:
I have a problem with my phone hanging at 93-97% when charging. I have to turn it off and within a minute or two it shows that it is fully charged. I'm wondering if anyone has ran across this problem and is it the phone or something else? It does this across all the ROM's and kernel combos that I have used over the last few months and I can't figure it out.
Click to expand...
Click to collapse
I've ran into that a few times, where it would seem to stop charging at around 95 or 96%. I changed to a different kernel and also wiped my battery stats, and that solved my issue. It's odd that it does it on any ROM/kernel combo. It doesn't seem to matter if it's Sense or AOSP? Have you tried wiping your battery stats? If not, give that a try. I'd also wipe cache and dalvik cache at the same time. You want to be charged up to 100% when you wipe the battery stats, btw. If that fails to solve the problem, the next thing I'd personally try out is using a different/new charging cable.
k2buckley said:
I've ran into that a few times, where it would seem to stop charging at around 95 or 96%. I changed to a different kernel and also wiped my battery stats, and that solved my issue. It's odd that it does it on any ROM/kernel combo. It doesn't seem to matter if it's Sense or AOSP? Have you tried wiping your battery stats? If not, give that a try. I'd also wipe cache and dalvik cache at the same time. You want to be charged up to 100% when you wipe the battery stats, btw. If that fails to solve the problem, the next thing I'd personally try out is using a different/new charging cable.
Click to expand...
Click to collapse
I've tried all those and no luck. I am totally perplexed as to what it could be, but I will give the battery stats another try, I can't remember if it was fully charged or not. The other thing that I am wondering is if it could be the PRI/NV that might need to be downgraded perhaps? If so, will these be ok with the newer radio?
gajendarksky said:
I've tried all those and no luck. I am totally perplexed as to what it could be, but I will give the battery stats another try, I can't remember if it was fully charged or not. The other thing that I am wondering is if it could be the PRI/NV that might need to be downgraded perhaps? If so, will these be ok with the newer radio?
Click to expand...
Click to collapse
You should be able to run the 1.77_003 PRI and NV with the newer radio. When I downgraded my PRI, I also downgraded the radio at the same time, but I don't believe that was necessary. Just be cautious, I believe that the stock htc #15 kernel runs crappy or won't even let the phone boot on the older radios/pri. So if you do downgrade the PRI / Radio, I'd suggest using a custom kernel. All that said, I have never heard of a certain version of a PRI or Radio causing any sort of charging issues like you're having. That is sort of odd. Perhaps it's the battery itself?! Have you tried using a different battery?
I have two batteries that I switch and it does the same thing on both.
Sent from the biggest damn EVO there ever was...
its the evo, its called the way they charge the phones, the only way to get 100 percent charge is using a sbc kernal, otherwise you have a phone that comes off the charger anywhere from 90-100% because thats what the phone is told to do
iitreatedii said:
its the evo, its called the way they charge the phones, the only way to get 100 percent charge is using a sbc kernal, otherwise you have a phone that comes off the charger anywhere from 90-100% because thats what the phone is told to do
Click to expand...
Click to collapse
It should still charge to 100%, where the light turns green, even without an SBC kernel. It's true, that the Evo stops charging at a certain point, and it's very possible to take it off the charger anywhere between 90-100%, as you stated. However, when it's plugged in, it should still register full, and the led should still be green. Then once it's unplugged, a rapid decrease will be noticed, as it registers where the actual charge is at.
k2buckley said:
It should still charge to 100%, where the light turns green, even without an SBC kernel. It's true, that the Evo stops charging at a certain point, and it's very possible to take it off the charger anywhere between 90-100%, as you stated. However, when it's plugged in, it should still register full, and the led should still be green. Then once it's unplugged, a rapid decrease will be noticed, as it registers where the actual charge is at.
Click to expand...
Click to collapse
The phone will charge to full capacity only when it's turned off only, never when its on. Like I said before, it will charge at a normal rate and then just stop at the 93-97% range for hours until I turn it off and then within a minute or two the light will turn green.

Problems with my battery even after calibration

Hey there,
I have the problem that my phone always turns off when I have about ~12% of battery life. I'm using oxygen 2.2 with s-off. I tried the following:
1. turn on desire and load till 100% (green LED)
2. turn off desire and load again till 100% (which is immediately)
3. boot into recovery while plugged in and delete the batter stats file
4. boot the desire while still on the cable and when it's fully booted ->unplug from the charging cable
5. without charging again let the phone discharge completely -> phone still turns off at about 10% of battery life
how to proceed now?
tried this?.. seems a little different from what you did.. I think
bubu. said:
Hey there,
I have the problem that my phone always turns off when I have about ~12% of battery life. I'm using oxygen 2.2 with s-off. I tried the following:
1. turn on desire and load till 100% (green LED)
2. turn off desire and load again till 100% (which is immediately)
3. boot into recovery while plugged in and delete the batter stats file
4. boot the desire while still on the cable and when it's fully booted ->unplug from the charging cable
5. without charging again let the phone discharge completely -> phone still turns off at about 10% of battery life
how to proceed now?
Click to expand...
Click to collapse
What you've done is called "bump charging". I've tried it myself today because I used a battery calibration app that made my battery life worse but bump charging didn't help at all and I've read on this forum and others that some people have serious problems after this process.
I'm currently trying the process from the link bortak posted above.
Why 'bump charging'? What special step I took is responsible to call it like this? The thing is: How to discharge very very fast? It's always very bad to have to discharge completely without charging it inbetween because sometimes I need to plug it to USB to transfer some files and when it takes a day to discharge, that's just not too comfortable... That's why I ask for a very very quick discharging-way?!
And: it seems that the instructions are very close to what I did (okay not completely). strange, that it makes such a difference...
I don't know why it's called bump charging...it just is because someone decided to call it that.
The problem you're having with the phone turning off at about 12% charge could be ROM related...I think. I seem to remember reading another thread on this forum that said some ROM's do this, but for what reason I don't know. Do a search and you should find another thread regarding this issue which was posted within the last week or two. Hope this helps
Thanks so far, I'll also try the link from above But I had this with djdroid before, and now with oxygen. So dunno if it's ROM related because the one is sense, the other isn't and the one was android 2.2 and the other is 2.3. So... perhaps really something related to the battery
Edit: Other people with the same prob in this thread:
http://forum.xda-developers.com/showthread.php?p=10820607#post10820607
look especially to the linked post
bubu. said:
Edit: Other people with the same prob in this thread:
http://forum.xda-developers.com/showthread.php?p=10820607#post10820607
look especially to the linked post
Click to expand...
Click to collapse
Slightly different issue for you from the graph example. The graph shows the sharp drop but you'd still notice the countdown to 0% but it would drop considerably faster from say 10% down to 0%. Yours is just dying at 12% which is altogether something different.
It's amazing the number of threads started in the last few days regarding various battery issues. My battery's started playing up over the last 2-3 days too.
xybadog said:
Slightly different issue for you from the graph example. The graph shows the sharp drop but you'd still notice the countdown to 0% but it would drop considerably faster from say 10% down to 0%. Yours is just dying at 12% which is altogether something different.
Click to expand...
Click to collapse
oh yeah, somehow missed that you're right. hm, I'm just trying the instructions from above; the phone is just discharging, so probably tomorrow morning it's completely empty or so Let's than check, what happens
edit: tried it but didn't wor. still shutting down at about 12-13%...

[Q] Battery read?

I am used to having my phone charge to 100% over night, and then when I unplug it it goes immediately to 99% This morning I had the blue LED notification to let me know I had a full charge. But when i took it off it said 60%, my first impression was whoa thats not right.
tbh im only running stock FF13 not even rooted.
Where is that 40% difference coming from?
thnx
xjs1200x said:
I am used to having my phone charge to 100% over night, and then when I unplug it it goes immediately to 99% This morning I had the blue LED notification to let me know I had a full charge. But when i took it off it said 60%, my first impression was whoa thats not right.
tbh im only running stock FF13 not even rooted.
Where is that 40% difference coming from?
thnx
Click to expand...
Click to collapse
maybe bad battery. is it bulged?
I dont think so, its a extended life battery. I was more looking to see if anybody else had an issue similar.
for the past week i've been having battery issues where the charging LED lights up, but the phone does NOT charge. or the phone says charging, then the light turns blue saying 100% but as soon as i remove the plug, the % drops to whatever the battery truely is at.
even when I go into about phone>battery, the time spent charging does not show that it has been charging. Also better battery stats does not seem to even show any processes being run...as if theres no battery stats to read from. also Gsam battery wont even calculate the average time left
my usb port works fine. i've used all different usb cables/chargers. i've wiped battery stats numerous times. ive done clean installs of ics and even tried going back to gb roms. issue reappears on BOTH oem batteries i have.
That's just one of those pesky ICS bugs that affects some phones and not others. I ran one Epic on the official ICS update for 4days and went back to gb before any bugs occurred, so I guess I was lucky not to have any aftereffects. It may clear with a custom Rom , you need to research the threads.
Good luck.
Pp.
Sent from my GT-P5113 using xda premium

[Q] [SOLVED] S3 Slow Charge/Quick Drain

Hi,
Few days ago I noticed that my S3 was charging extremely slowly. I had it plugged in for 10 hours and it charged maybe 20%. I needed a full battery so I swapped the one from my battery charger (the official Samsung charger and battery), which was supposed to be at 100% according to the charger. Phone started up, battery was at 100%, and a few hours later it died.
Now, if I plug the phone in to charge it will gain a percent every 10 mins or so and it will only charge to about 54%. Doesn't matter how long I let it charge for, 54%. There was one instance where it charged to 100% but 2 mins after I unplugged the phone, it was back at 54%. The battery charger keeps charging the two batteries to what it says is full (green light on the charger), but when I put it in the phone it appears to only be between 10% and 50%.
Today, I took a battery which the charger said was at 100% and put it in my phone. Started the phone up, it said 2%. Put the same battery in my friends S3 and his phone said 98%. Back into my phone, 18%.
Things I've tried:
Leaving the phone plugged in for an extended period of time
Taking the battery out for 10 mins then putting it back in
Different chargers (some official Samsung, one BlackBerry, one no name)
Charging from USB and AC
Like I said, tried putting the phone in a different S3 and no problem with that. Only has a problem with my phone
Booted into recovery (TWRP) and it will report the same percentage as the OS
Tried to download a few different apps to check the current that was charging the phone but none of them worked for the i747m.
Also used Better Battery Stats to see if anything was draining the battery or had a partial wakelock. Nothing out of the ordinary.
When the problem first started I hadn't updated the software (CM 10.3) but was still planning on doing a restore later tonight.
I've searched xda and google but haven't come across anything that has worked. If anyone has any suggestions it would be greatly appreciated.
Thanks!
Restored back to stock last night using Kies "Firmware Upgrade and Initialisation", but that didn't help. I'm going to assume that is hardware at this point. Unfortunately, I'm out of my warranty. Right before it ended I took the phone in for repairs and they replaced the micro usb port. Could this be causing the issue? I had originally thought this but like I said, if I take the battery out and put it in another phone it sees it as being at 100%.
mcgrandlej said:
Restored back to stock last night using Kies "Firmware Upgrade and Initialisation", but that didn't help. I'm going to assume that is hardware at this point. Unfortunately, I'm out of my warranty. Right before it ended I took the phone in for repairs and they replaced the micro usb port. Could this be causing the issue? I had originally thought this but like I said, if I take the battery out and put it in another phone it sees it as being at 100%.
Click to expand...
Click to collapse
You said the phone itself will only charge the battery to what your phone reports as 54%, correct? What i didn't see was at that stage did you try it in the other phone? Just trying to determine if the phone is actually charging to 100% or not. If it will only charge a battery half way it is entirely possible the usb port repair wasn't up to par but I find it hard to believe that it would cause such dramatic drain as well. If it does in fact charge the battery fully then your problem is more than likely with the sensor responsible for report battery condition. Whether the sensor is bad or is simply in need of recalibration is the question at that point. Regardless of the actual charge of the battery if the OS is being reported to that it is below tolerance threshold it will assume the battery is dead.
dntesinfrno said:
You said the phone itself will only charge the battery to what your phone reports as 54%, correct? What i didn't see was at that stage did you try it in the other phone? Just trying to determine if the phone is actually charging to 100% or not. If it will only charge a battery half way it is entirely possible the usb port repair wasn't up to par but I find it hard to believe that it would cause such dramatic drain as well. If it does in fact charge the battery fully then your problem is more than likely with the sensor responsible for report battery condition. Whether the sensor is bad or is simply in need of recalibration is the question at that point. Regardless of the actual charge of the battery if the OS is being reported to that it is below tolerance threshold it will assume the battery is dead.
Click to expand...
Click to collapse
Yes the phone only reports a 54% charge at most. I took a battery from my battery charger which was at 100%, put it in my phone which reported 2%, then immediately into another S3 which reported 98% and stayed that way for 5 or so minutes.
Given enough time (upwards of 10 hrs) charging the battery via the phone and the phone will report 100%. But then within a couple minutes the phone will report 54% and will discharge as normal.
mcgrandlej said:
Yes the phone only reports a 54% charge at most. I took a battery from my battery charger which was at 100%, put it in my phone which reported 2%, then immediately into another S3 which reported 98% and stayed that way for 5 or so minutes.
Given enough time (upwards of 10 hrs) charging the battery via the phone and the phone will report 100%. But then within a couple minutes the phone will report 54% and will discharge as normal.
Click to expand...
Click to collapse
It sounds to me like the sensor responsible for reporting the battery condition to the OS is screwy. It could either be bad and need to be replaced, which would most likely mean a motherboard, or just needs to be calibrated. You can try resetting the battery statistics from CWM recovery if i recall, i wasn't able to find the same option in TWRP if that is what you are using. Its an outside chance but certainly worth installing CWM to give it a try over replacing the MB. Lastly, if you haven't already tried you can try flashing back to stock and see if that corrects the problem. If it is software related this should work, if not you cant pretty sure its hardware.
EDIT: I loaded up the latest CWM and the option for resetting battery stats isn't there so either they removed it or i am just remembering this from some other device or ROM i used in the distant past. In any case i found THIS thread that should assist in attempting to recalibrate the battery reporting.
dntesinfrno said:
It sounds to me like the sensor responsible for reporting the battery condition to the OS is screwy. It could either be bad and need to be replaced, which would most likely mean a motherboard, or just needs to be calibrated. You can try resetting the battery statistics from CWM recovery if i recall, i wasn't able to find the same option in TWRP if that is what you are using. Its an outside chance but certainly worth installing CWM to give it a try over replacing the MB. Lastly, if you haven't already tried you can try flashing back to stock and see if that corrects the problem. If it is software related this should work, if not you cant pretty sure its hardware.
EDIT: I loaded up the latest CWM and the option for resetting battery stats isn't there so either they removed it or i am just remembering this from some other device or ROM i used in the distant past. In any case i found THIS thread that should assist in attempting to recalibrate the battery reporting.
Click to expand...
Click to collapse
Ya I tried flashing stock previously and that didn't help. I had considered resetting the battery stats but I read a lot of forum posts that said this didn't have any affect on the battery and was automatically done whenever the battery was fully charged (or completely empty can't remember which one).
I ended up taking it in to the provider but they said I would have to send it out to Samsung and pay the cost since it was out of warranty. They suggested that it would be likely that I would just end up with a new refurb for $150. Instead I took it into a shop nearby and they repaired the motherboard for $90. Got it back earlier today and so far it's working fine.

Categories

Resources