Related
Hi Guys,
I have spent days researching this, and have read dozens of forum posts, but nothing has worked. Here's the problem- I bought a used GNEX off of Craigslist. The phone looks great and seems to work well. But, it won't show a charge beyond about 70%.
I thought the battery might be the issue, so i bought an a new OEM extended battery, but the new battery didn't make any difference. It still won't show a charge above 70% no matter how long I leave it on the charger (with the phone turned on or off). I have done probably 20 discharge/recharge cycles, but nothing changes.
Next, I bought an external charger. When I fully charge the battery in the external charger and pop it in the phone, it still shows around 70%. So, it is definitely an issue with the phone (not the batteries).
I've also tried four different ROMs, as well as all the black-magic "battery calibration" tricks found in the forums, but nothing helps.
I am totally stumped! Is there anyway I can fix this?
Thanks!
Slim
Please HELP! More info.
Hi guys,
Just an update. Yesterday I tried three different kernels, just in case that might make a difference. No luck. The kernels didn't make a difference.
Any advice on how I can make this phone handle battery levels correctly? It's been on the charger all night and only shows 66% charge.
-Slim
Same here !
reza2224 said:
Same here !
Click to expand...
Click to collapse
Hey, Reza. How long has your GNEX been having this problem?
You might try returning to stock to see if eliminating custom ROMs helps.
imthepits said:
You might try returning to stock to see if eliminating custom ROMs helps.
Click to expand...
Click to collapse
Thanks. I actually already tried that. Took it back to completely stock, unrooted. No dice. The issue was still there. I am stumped!. I hope it's not a hardware issue.
SlimKermie said:
Hey, Reza. How long has your GNEX been having this problem?
Click to expand...
Click to collapse
I have this phone about six months,but couple days age after I tried to install cm10.1 carch up with this problem.
Changing custom rom,returning to stock,callibrating , every thing I tried didn't work.
Firs it stops about 98,then after a recharge it stops @ 95 ,then 90 and now it does'nt exceed 87.
Sent from my Galaxy Nexus using xda premium
Same problem
reza2224 said:
I have this phone about six months,but couple days age after I tried to install cm10.1 carch up with this problem.
Changing custom rom,returning to stock,callibrating , every thing I tried didn't work.
Firs it stops about 98,then after a recharge it stops @ 95 ,then 90 and now it does'nt exceed 87.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same issue here, i tried with another battery that showed 95% in other Gnex and in my gnex showed 60%.....
I'm getting crazy!
Definitely a hardware issue.
Toro | Carbon | AK SKL
try an app named "BatteryCalibration" by marosige. When opened it shows the in circuit battery voltage. 3600-3700mV is to be expected from a well charged and in good shape battery. We seam to be having the same issues with mine having progressed to showing 0%. I have a recent thread here as well. I have read that the recovery battery stat wipe is just for the application level, but I think there must be a file or setting somewhere that maps mV to %'s and that this is what needs wiped/reset.
Anyone overhere still having issues?
I updated my thread on a similar if not the same problem, and am looking for some volunteers to help gather a little data. I would like for one or more persons to install SL4A and python, run a script and report findings. If you are willing please post a reply in my thread.
Thank you
I've had my I747 at&t now for 6 months, about 2 weeks ago It started shutting down on me on it's own, at that time I was rooted and had a custom rom installed that was working perfect. It was the HighOnAndroid ROM v0.3 from galaxys3root.com. There were no problems at all until 2 weeks ago too. So I used Kies to factory restore and upgrade to1747UCDLK3 to see if it was my rom I I had installed. My phone works now, but I have a problem with the battery I can't figure out.
here's what it does, I charge my battery at the end of the day to 100% and turn it off, then the next morning it's always down to around 70% even though it is off all night. It didn't do this before at all, have you had this issue or can give me some advice? thank you
Edit...FYI I use this phone on Straight Talk and have reformatted my 32 gig sd too just to start clean.
Chocketbear said:
I've had my I747 at&t now for 6 months, about 2 weeks ago It started shutting down on me on it's own, at that time I was rooted and had a custom rom installed that was working perfect. It was the HighOnAndroid ROM v0.3 from galaxys3root.com. There were no problems at all until 2 weeks ago too. So I used Kies to factory restore and upgrade to1747UCDLK3 to see if it was my rom I I had installed. My phone works now, but I have a problem with the battery I can't figure out.
here's what it does, I charge my battery at the end of the day to 100% and turn it off, then the next morning it's always down to around 70% even though it is off all night. It didn't do this before at all, have you had this issue or can give me some advice? thank you
Edit...FYI I use this phone on Straight Talk and have reformatted my 32 gig sd too just to start clean.
Click to expand...
Click to collapse
Are you still rooted and on the stock 4.1.1 ?
This has been going on for two weeks ?
hednik said:
Are you still rooted and on the stock 4.1.1 ?
This has been going on for two weeks ?
Click to expand...
Click to collapse
No, kies removed the root and I'm on jelly bean"which was samsungs update
Chocketbear said:
No, kies removed the root and I'm on jelly bean"which was samsungs update
Click to expand...
Click to collapse
I never used the plain stock with Keis update. I would normally just suggest to just flash it again. Are you opposed to rooting again and installing a customer recovery or do you want to stay completely stock ?
hednik said:
I never used the plain stock with Keis update. I would normally just suggest to just flash it again. Are you opposed to rooting again and installing a customer recovery or do you want to stay completely stock ?
Click to expand...
Click to collapse
No, I liked it rooted....just trying to figure out what happened. I just don't understand how the battery can drain that much if the phone is off. I may reroot of I can get past this part, It's seems to run down no matter which rom is on it.
I would reccomend gsam battery monitor and cpuspy. That should help determine the problem. It helped me when I had a similar issue.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Powered off or sleeping?
If you physically turn the phone off (not just sleep mode), then something is up with the battery.
Try powering to 100% charge, then discharge all the way down to 5%. Then charge to 100% again and see if that helps.
My phone was only ever able to charge to 70% for a few days. A complete discharge was able to fix it for me.
CZ Eddie said:
Powered off or sleeping?
If you physically turn the phone off (not just sleep mode), then something is up with the battery.
Try powering to 100% charge, then discharge all the way down to 5%. Then charge to 100% again and see if that helps.
My phone was only ever able to charge to 70% for a few days. A complete discharge was able to fix it for me.
Click to expand...
Click to collapse
It's shutting down, but i cant say I've ever let it get down to 5%, I just top it off. I did charge it to 100% one night , remove the battery and reinstalled it the next morining, It was still 99% by leaving it out of the phone, go figure, I 'll try your tips too
boothcr79 said:
I would reccomend gsam battery monitor and cpuspy. That should help determine the problem. It helped me when I had a similar issue.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll check those out too
Some Users are reporting that the Battery stays at 14% for a long time.
I had this issue too , until i waited till the Phone was down to 1% and switched off, ( this took ~6h with GPS active and Display on!!) since this time i did not notice this behaviour.
drcyber said:
Some Users are reporting that the Battery stays at 14% for a long time.
I had this issue too , until i waited till the Phone was down to 1% and switched off, ( this took ~6h with GPS active and Display on!!) since this time i did not notice this behaviour.
Click to expand...
Click to collapse
+1 This issue has been part of my Fairphone experience since the beginning - and fully draining the charge like you described doesn't seem to help: Even after 20 complete discharges, it still gets stuck at 14% for hours, making a correct estimate how much battery I actually have left impossible. These three screenshots are all one week apart (Jan 17th, Jan 22nd & Jan 30th - click to enlarge):
↑ Reboot caused this glitch.
@drcyber, thanks for making a thread for this - I didn't know whether it was enough of an issue to do so myself
Repeating my question from the main thread (for the last time, don't worry): I am well aware that Joe & his crew might not be able to do/tell us anything about this, but maybe someone can shed a bit of light on this issue for me: Is this purely a hardware glitch of the battery itself? Do some sensors / parts of the measuring software need to calibrate themselves first? Is everyone experiencing this or just the few that have reported it here?
now its back, 14% for 15 hours now..
Try to monitor the kernel's power level sensors, and see if they change. There are 3 possible issues: the hardware isn't measuring correctly, the kernel isn't outputting the correct values, or the system itself is bugged, and doesn't handle the kernel's values correctly.
That's all I can say for now, as I neither have the device myself' nor the sources, as I am being in the hospital right now, but maybe I can give some theoretical help
Sent from my Nexus 7 using xda app-developers app
Same problem here
laufersteppenwolf said:
Try to monitor the kernel's power level sensors, and see if they change. There are 3 possible issues: the hardware isn't measuring correctly, the kernel isn't outputting the correct values, or the system itself is bugged, and doesn't handle the kernel's values correctly.
That's all I can say for now, as I neither have the device myself' nor the sources, as I am being in the hospital right now, but maybe I can give some theoretical help
Click to expand...
Click to collapse
Sparparts+ tells me that the mVolts are decreasing normally, so i guess the Kernel works correctly and it is just a interpreting issue.
Gute Besserung!
Gesendet von meinem FP1 mit Tapatalk
Maybe it's related. I looked at the power config XML in the framework res. And that was complete garbage. See the file in the other thread.
Chris
Sent from my FP1 using xda app-developers app
See
http://forum.xda-developers.com/showpost.php?p=49598488&postcount=337
Sent from my FP1 using xda app-developers app
chrmhoffmann said:
Maybe it's related. I looked at the power config XML in the framework res. And that was complete garbage. See the file in the other thread.
Chris
Sent from my FP1 using xda app-developers app
Click to expand...
Click to collapse
You're right, this file actually really is important
But the good thing is, it's relatively easy to fix I'm sure Fairphone should be able to bring up a fix quite soon, as they should have all values ready, and just need to insert them correctly
The other thing is, when loading the phone, it stucks for some time at 99%.
As far as I experienced it, it only comes, when you unload your phone to less than 14%
If you stop loading at less than 99% (aften unloading below 14%) you do not have the Battery keeping for hours at 14%.
Can anybody confirm this behaviour?
Edit:
I did not have the GPS active, regardless what the energy manager tells
haiag said:
The other thing is, when loading the phone, it stucks for some time at 99%.
As far as I experienced it, it only comes, when you unload your phone to less than 14%
If you stop loading at less than 99% (aften unloading below 14%) you do not have the Battery keeping for hours at 14%.
Can anybody confirm this behaviour?
Click to expand...
Click to collapse
yes after completly discahrge the 14%-Error seems to be gone, but i dont know for how long, but after the Update to 1.1 i was back again.
drcyber said:
yes after completly discahrge the 14%-Error seems to be gone, but i dont know for how long, but after the Update to 1.1 i was back again.
Click to expand...
Click to collapse
Did you had the 99%-Error when loading?
Or was it directly to 100% without the 14%-Error?
uhm, I may be wrong but doesn't the phone charge/uncharge/charge/un.. when it tends to reach 100%? So it stays at 99% the whole time
arghwhymustiregister said:
uhm, I may be wrong but doesn't the phone charge/uncharge/charge/un.. when it tends to reach 100%? So it stays at 99% the whole time
Click to expand...
Click to collapse
I think usually Android phones load to 100%, then drop to 90% and load back to 100% again. At least the Nexus S did so, IIRC.
No, if you wait long enough, it gets to 100%.
But the green LED comes earlier than 100%
Sent from my FP1 using xda app-developers app
But this 99% thing i never saw as a bug, because your Phone never tells you the full truth about the Battery, 100% is never really 100% , and never 0% because the battery would get damadegt ift its really empty or completly full all the time.
Here is a better explenation in German:
http://www.giga.de/downloads/firmwa...e-von-smartphones-lugt-und-warum-das-gut-ist/
and English:
http://forum.xda-developers.com/showthread.php?t=871051
But this 99%thing just happens, when you unload your phone to less than 14%. So IMHO it's correlated somehow.
I think the maximal capacity isn't right...
Sent from my FP1 using xda app-developers app
haiag said:
The other thing is, when loading the phone, it stucks for some time at 99%.
As far as I experienced it, it only comes, when you unload your phone to less than 14%
Click to expand...
Click to collapse
Can confirm, battery only gets stuck at 99% if discharged below 14% (click to enlarge):
haiag said:
If you stop loading at less than 99% (aften unloading below 14%) you do not have the Battery keeping for hours at 14%.
Click to expand...
Click to collapse
Can confirm, 99% is enough of a charge to make the battery information get stuck (click to enlarge):
drcyber said:
Here is a better explenation in German:
http://www.giga.de/downloads/firmwa...e-von-smartphones-lugt-und-warum-das-gut-ist/
Click to expand...
Click to collapse
Sehr informativ, vielen Dank!
All in all, I think there isn't much we can do about this without a properly set power-profile.xml in framework-res.apk, like @chrmhoffmann and @laufersteppenwolf said. Since I have not the faintest clue on how to correct the xml, I can only wait for Joe & the Fairphone team to answer this in the next round of questions - after they've adressed this week's questions, of course
simsalonaut said:
Nope, mine still gets stuck at 14%, no matter how much I had charged the battery before unplugging. This is after a discharge from less than 99% (click to enlarge):
Click to expand...
Click to collapse
Did you unload the battery before below 14% ? Than charge to less than 99%, afterwards the 14% thing shouldn't appear.
So 13% -> max 98% -> No 14% Stuck...
So, I went to look at the time on my phone and it wouldn't turn on. I held down the power button and the back & home buttons just blinked a few times but it didn't turn on. I plugged it into the charger and it's not charging, no LED light or anything, and it won't turn on.
Does anyone know what could have happened or how to fix it?? I noticed earlier it was running a little hot after some app updates. could that have something to so with this? Is my phone dead??
There have been several reports as of late where the same thing has happened. Were you running a custom Rom and kernel?
What recovery were you running?
Sent from my Lunar Ecliptic One.
brymaster5000 said:
What recovery were you running?
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
How come this would be caused by a recovery issue? My phone died just today because I forgot my charging cable at home. I charged it up just fine. If the recovery was the issue I wouldn't have been able to charge my phone up after it died. He overheated his phone which seems to be the link to every other case of this happening.
Recovery "might" be an issue, as if recovery cannot respond to a "power on" it will not turn on. Most recoveries will respond to a "adb reboot" command. That may fix his issue... If his PC recognizes the device. I know certain TWRP had issues with the DNA and it could have bled to the m7
Sent from my HTC6500LVW using XDA Free mobile app
Wouldn't this happen a lot more often if the recovery caused in considering that people run out of battery all the time?
disconnecktie said:
Wouldn't this happen a lot more often if the recovery caused in considering that people run out of battery all the time?
Click to expand...
Click to collapse
Depends if they are using a commonly used recovery, or if the MD5 matched. I never let my battery go below 30% as most users should try their hardest to not also, fully draining li batteries drastically reduces their life and capacity.
Edit: it is also good to see everyone's setup who has this issue so we can find the common thing every time it happens.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Depends if they are using a commonly used recovery, or if the MD5 matched. I never let my battery go below 30% as most users should try their hardest to not also, fully draining li batteries drastically reduces their life and capacity.
Edit: it is also good to see everyone's setup who has this issue so we can find the common thing every time it happens.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Yea I generally try to not get way to low. It's a scary thought though that if you happen to forget to charge your phone it might not charge back up. That's why I was interested in what rom and kernel he was using. Plus it seemed to be that most of the people who couldn't recharge had an overheating issue before hand which is more or less why I don't believe it is a recovery issue.
Ok, for some reason it's working again. As I said before, it was just completely dead (wouldn't power on, no LED light when plugged into two different chargers, two different outlets) then I tried again about an hour after all the problems started and it powered on again.
When it came on, it had a 70% charge, so I put it back on the charger and charged it back up to 100%. However, after about two minutes being unplugged, it dropped down to 95%. It's never done anything like that before and this is the first time I've had any kind of problems with it in the year I've had the phone.
Could this have been some sort of temporary battery issue? I'm so confused. Are there and diagnostic tools I can use to try to figure out what happened?
I'm using NuSenseONE-Max_RC6_111313 (4.3 based), not sure what kernel and TWRP recovery. Also, I usually drain the battery down to 15% before I charge it.
Also, this happened after I updated about 20 apps.
JGress said:
Ok, for some reason it's working again. As I said before, it was just completely dead (wouldn't power on, no LED light when plugged into two different chargers, two different outlets) then I tried again about an hour after all the problems started and it powered on again.
When it came on, it had a 70% charge, so I put it back on the charger and charged it back up to 100%. However, after about two minutes being unplugged, it dropped down to 95%. It's never done anything like that before and this is the first time I've had any kind of problems with it in the year I've had the phone.
Could this have been some sort of temporary battery issue? I'm so confused. Are there and diagnostic tools I can use to try to figure out what happened?
I'm using NuSenseONE-Max_RC6_111313 (4.3 based), not sure what kernel and TWRP recovery. Also, I usually drain the battery down to 15% before I charge it.
Click to expand...
Click to collapse
That almost sounds like your battery might be going out but maybe you should update your rom and recovery just out of precaution. You'll need to update your firmware as well since you're probably still running jb firmware considering the age of that rom.
disconnecktie said:
You'll need to update your firmware as well
Click to expand...
Click to collapse
Wait... I thought a ROM and firmware were the same thing.
JGress said:
Wait... I thought a ROM and firmware were the same thing.
Click to expand...
Click to collapse
Not exactly. Grab the firmware from here
http://forum.xda-developers.com/showthread.php?p=46506592
It's version 5.x.605 something lol
Get the one that has no boot and flash it per the instructions in the op. Then grab an updated recovery. I use version 2.7.1.2 from here . http://mdmower.cmphys.com/twrp-m7vzw/ you're more than welcome to flash whatever you like philz or cwm. Then grab a newer rom. Kit Kat has been way better than jelly bean in my opinion.
On the battery dropping to 95% quickly, this is a known software "feature" in android since froyo or earlier. When the phone is fully charged, power cuts off from the Phone and won't "charge" until it hits 90%. System will still show you 100%. It has been proven by many sources that keeping a "trickle" on a fully charged battery will damage it. That is why it probably dropped quickly. Only way to determine if battery is faulty is have it drop below 89% and see it's drain.
Sent from my HTC6500LVW using XDA Free mobile app
disconnecktie said:
Not exactly. Grab the firmware from here
http://forum.xda-developers.com/showthread.php?p=46506592
It's version 5.x.605 something lol
Get the one that has no boot and flash it per the instructions in the op. Then grab an updated recovery. I use version 2.7.1.2 from here . http://mdmower.cmphys.com/twrp-m7vzw/ you're more than welcome to flash whatever you like philz or cwm. Then grab a newer rom. Kit Kat has been way better than jelly bean in my opinion.
Click to expand...
Click to collapse
Ok, thanks for the help!
Does the One maybe have an auto-shutdown feature that triggers if it overheats? I was thinking that was a possibility.
disconnecktie said:
How come this would be caused by a recovery issue? My phone died just today because I forgot my charging cable at home. I charged it up just fine. If the recovery was the issue I wouldn't have been able to charge my phone up after it died. He overheated his phone which seems to be the link to every other case of this happening.
Click to expand...
Click to collapse
Just trying to get the full picture as uzephi said. Just was wondering because there are instances where it can die and if the recovery had a glitch and or missed a charging binary in one build it might not charge...
Sent from my Lunar Ecliptic One.
brymaster5000 said:
Just trying to get the full picture as uzephi said. Just was wondering because there are instances where it can die and if the recovery had a glitch and or missed a charging binary in one build it might not charge...
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
I understand. I asked because I didn't understand why this would be a recovery issue since you can't always keep your phone from dying and having your phone brick as a result would completely suck. Plus, it would be a lot more frequent (you would think anyway) for this same thing to happen. I wouldn't want to use whatever recovery had this issue either. However, I think he just really needed to update his firmware, rom and recovery. I'm surprised he made it this long without needing to upgrade. It also helps knowing all the info because if it was a rom/kernel issue the dev could take a look into what could potentially cause the overheating because the thermal protection written into the kernel isn't doing its job if it allows the phone to overheat to death.
updated my wife's phone from a version released in May to PK4 and now she says that it is charging slowly. Is there anything I can do to fix this? She's tried the OEM charger and cord as well as other ones that have always charged her phone within a couple hours.
Saafir said:
Make sure fast charging is turned on in the phones Battery settings.
Click to expand...
Click to collapse
I confirmed that yesterday and again just now. I also switched it off yesterday then back on just in case something in a db somewhere got glitched. Sadly, not fixed.
jerry43812 said:
I confirmed that yesterday and again just now. I also switched it off yesterday then back on just in case something in a db somewhere got glitched. Sadly, not fixed.
Click to expand...
Click to collapse
One of the things that is advised by Samsung for the "slow-charging after firmware update" is to go into recovery and wipe cache partitions.
Easy enough to do and it might help.
koop1955 said:
One of the things that is advised by Samsung for the "slow-charging after firmware update" is to go into recovery and wipe cache partitions.
Easy enough to do and it might help.
Click to expand...
Click to collapse
I'll try it and report back.
- compliments of the confines of my mind's sphincter