Is anyone else experiencing a problem with battery charging on JF's ADP 1.5 release?
I've got this issue where I plug my phone in to the wall charger at night and it's on a cheap lamp timer so that it doesn't start to charge until 1.25 hours before I leave for work to prevent overcharging. Since I updated to 1.5 it seems that when the phone is On and starts the wall charge it treats it like a trickle charge as if it were connected via USB to a computer. Only after I turn the phone off does it rapidly charge like it should via the wall charger. Its a little annoying since the first day after the 1.5 update I didn't notice it and went in to work with a half charged battery. Now I know to look out for it and go turn the phone off when I wake up and by the time I'm ready to leave for work it's fully charged.
Tim
Wait, so does G1 have overcharge protection or doesn't it??
I didn't think it was necessary to protect from overcharging either.
I don't see this problem with my JF1.5 though - I plug it in at night and it charges full for when I wake up the next morning.
Dimath said:
Wait, so does G1 have overcharge protection or doesn't it??
Click to expand...
Click to collapse
it should as that is very simple technology and is standard in many cheap devices now, so my guess is it would be in g1 or there would be a heck of alot more problems.........
on another note....ive noticed with JF 1.5 my battery icon gets a little stuck.....i thought it was an improvement of battery life until yesterday it stayed at 100% for like 5 hours but then dropped to 80% out of no where when i installed an app.......is anyone else having this issue??
I use battery graph from the market to see my battery charge over time. That's how I know that it "trickle" charges for me when connected to the wall charger until I turn the phone off.
BTW, when I turn the phone off then back on after waking up it does rapidly charge properly as well. Seems like it just needs a reboot for it to work right.
...and I'm sure that the G1 does have built-in overcharge protection, I just don't really trust it to do as good of a job as my cheap lamp timer does
Turn off your phone, remove you batter, put it back in, and turn your phone on. Everything should reset and be back to normal.
will try tonight.
no problem the power indicator or measurer is just more accurate in the 1.5 builds
i agree, used to fully charge in about an hour and a half, now its been takeing about 4 hours to hit 100% from about 1/2 charge...
ive noticed the same thing.
My phone charges fine with both my regular G1 battery and my Seidio Extended 2600mAh battery since my upgrade to JF ADP V1.50.
mine is on the trickle charge bug as well. phone stays cold throughout the 2 hours i've had it plugged in and its only at 68% charge. Brought it down to around 30% charge when I plugged it in to the wall.
My phone had the same problem when i updated to any of the 1.5 builds w/ radio. today, i drained the battery all the way until the phone died and took the battery out for about a min. Put it back in and started charging. My phone went back to charging normally up to 100% within ~2.5hrs. I've still yet to see how long this full battery will last until later today. Normally, i would get up to 2 days easy w/out charging on normal usage (a text or 5 min phone call here and there), 2G only, wifi disabled, bluetooth disabled. I'll let you guys know how it goes later.
This problem happens when the G1 is offline (airplane mode). When its online there is no problem with charging
mine has been acting weird since going to jf 1.5
last night i plugged it in at like 33% charged, and like 3 hours later it was at like 65%
i unplugged it, turned it off. turned it back on and when i plugged it in it was 100%.
before i charged it (when it was at 33%) i yanked the battery for a few seconds then put it back in then started to charge.
i'm going to do what JDMr2 did and let it die, yank the battery for a min then charge it and see how it goes.
It's always been charging more slowly on Cupcake than 1.x, BUT the battery lasts much, much longer.
well I took the battery out for a minute then put it back in. I left the phone on at night and plugged in the wall charger that's on my lamp timer before going to sleep. I woke up in the morning and looked at it in battery grapher and noticed that it rapidly charged from 30% until 60% then began to trickle charge the rest of the way up to 72% when I looked at the graph. I rebooted the phone, plugged it back in to the wall charger and it rapidly charged the rest of the way to 100%.
So, taking the battery out did not solve it. But interestingly I did discover that it rapidly charges until 60% then it switched into trickle charge mode. This is only after one observation however.
I've been having this problem as well but even prior to JF's version. I originally upgraded to the stock 1.5 from HTC (radio then firmware) and noticed the very slow charge times. I've tried pulling the battery and restarting but that hasnt changed anything. In the process now of completely draining the unit and then going to try again from there.
My G1 charges like normal.
JF1.5 ADP.
JF 1.5 nothing else fancy and I have noticed that charging has went from 45 mins or so to hours. Last night from amber it took 5 or so hours to go green. They definitely changed how the phone charges. Now my battery info says 73% and it has been moderately used for 7 hours. Looks like they went in a positive direction.
Related
I charge my battery overnight. I'm guessing this is bad for the battery but how bad? And is there some app or something that will stop the charge once it hits 100% while still plugged in? Thanks
I believe the phone has overcharge protection circutry in it already
has anyone noticed that, with the new radio, it takes longer to charge and sometimes it doesn't even reach 100%. however when i reboot it, it actually is at 100%. The the batter indicator isn't as accurate anymore.
JDMr2 said:
has anyone noticed that, with the new radio, it takes longer to charge and sometimes it doesn't even reach 100%. however when i reboot it, it actually is at 100%. The the batter indicator isn't as accurate anymore.
Click to expand...
Click to collapse
yes i have, i wanna say its because its not an official mod, but im using the jf update? maybe its build specific, which one you using jd?
i thought i was the only one to notice
I've used the sapphire radio update w/ 5.0.2Hr5 and the new ADP radio update w/ JF1.5. I noticed this with both combinations.
I am noticing this as well with JF's build
So what is the deal? Is the phone actually fully charged after 2 hours and the meter doesnt actually realize it? will this cause any problems with leaving the phone charging in the wall and overcharging?
I highly doubt it has anything to do with overcharging since it's not a hardware issue.
LOL! It's never been accurate at all with any software build or radio combination. I can charge my phone all the way and pull the battery and reboot and get an accurate reading then. The battery life and measurement has been the biggest flaw with this phone. It hasn't gotten any better with a new build or ever will, imo.
wasn't THIS bad when i had JF1.42 RC33. it was just when I updated to Haykuro's or JF's 1.5 builds. An example will be where I begin charging my phone at 5% and after 3-4 hours, it'll only be at ~65%. I reboot the phone and it automatically fixes itself to 100%. It normally only takes ~2hrs for my phone to charge to 100%.
I'm running The Dude's ADP 1.5 and I noticed also that it takes a lot longer to charge the phone.
Normally if I plug it in, it was fully charged in 2-3 hours. Now it takes more than 5hours
John5788 said:
I am noticing this as well with JF's build
So what is the deal? Is the phone actually fully charged after 2 hours and the meter doesnt actually realize it? will this cause any problems with leaving the phone charging in the wall and overcharging?
Click to expand...
Click to collapse
I am also seeing this same issue. I unplugged my phone from the charger at 11am and it was 100%. At 12:45 it was down to 87%. I fell asleep by the pool and woke up and it was at 52%, this was around 3p. I went home and charge the phone. I looked at it around 5p and it was at 72%. I rebooted the phone with Call+Menu+End(thanx JF, Dude took this out his buld) and it was at 100% when rebooted. It may be that TMOBILE branded G1's may have a underlying hardware/software issue which does not allow the OS to fully read the battery. My assumption and im just taking a stab at this is that possibly since ADP 1.5 features processor frequency change (ie, 528mhz to 384, 122 when sleeping) it may be reading the battery when at 528mhz and then when it drops to 122mhz the phone cant write to the RAM or somehow it gets lost b.c on refresh it reads 100%. I may not know anything about what I wrote but its just a stab at an idea. Maybe someone can do some testing to see what happens internally between ADP and RC33 and/or G1 & ADP.
JDMr2 said:
wasn't THIS bad when i had JF1.42 RC33. it was just when I updated to Haykuro's or JF's 1.5 builds. An example will be where I begin charging my phone at 5% and after 3-4 hours, it'll only be at ~65%. I reboot the phone and it automatically fixes itself to 100%. It normally only takes ~2hrs for my phone to charge to 100%.
Click to expand...
Click to collapse
I agree... it HAS gotten worse with 1.5 builds. It takes for ever to charge up to 100% (especially if you have something running in the background. it might just be the overclocking that's doing it). After rebooting, it will give a more accurate reading. I've noticed also (with all builds) that if you reboot with the charger plugged in... it will give you a false, higher battery reading than if you rebooted with it not plugged in. If you get (or suspect) a false reading, pull the battery while phone is on and let it sit idle for a couple seconds and then reinsert and power on. That should be pretty accurate but it seems most false readings happen while the phone is charging. One way to get around this without rebooting to make sure that it's fully charged is to charge the phone while its off. Just remember green light means 90% or higher and not 100% like ALL other HTC devices. That is part of the problem itself....
if the light turned green when it is charged 100%, alot of these false readings would not be happening. I know that sounds silly but the OS/hardware have to judge when its at 90% even when it's powered off. Kinda more complicated than just orange light when charging and green when fully charged (like all other HTC devices). Instead we have to go from red flashing to red to orange and to green. Maybe that makes sense to some? I don't know for sure... it's merely my long-winded theory about the crazy, ****ed up battery life for this otherwise fantastic device, lol! Sorry for the loooooooonnnnnng reply...
I have dudes. 93 and that's when I ran to the issue you guys are talking about. I happened to just install a battery widget and thoughy that's why it had to reboot for accurate reading it hasnt been long to recharge after uninstall. The other builds all seemed accurate to me. It also seems like my battery doesn't last as long with the new radio but at the samew time it seems that it quickly drops out of the 90's and 80% range but sticks in the lower ranges longer. I don't know why with all of our technology laptops and phones can do the carziest things but only for an unreasonably short amount of time...
I drained my battery letting the phone die, took the battery out, put it back in after a min or so, and began charging. It seems to have fixed the long charging issue. It fully charged my battery in ~2.5hrs. I'll report back if the battery life lasts just as long as it charges.
The last couple of days I've noticed something strange with my battery. I keep it on the charger all night and when I get up in the morning my phone says the battery is at 100% and the charge LED is green. The instant I pull my phone off the charger it drops a couple percent. I thought that was strange so this morning instead of pulling the phone off I just shut it down. Once the phone was completely off the LED went from Green to Orange as if it was charging again. It look another 20 minutes to turn green again. I powered the phone up and as soon as sense is loaded I am back to 93% battery.
Anyone else see this? I've wiped battery stats and did the whole calibration but that didn't seem to fix the issue.
That is normal... Once the batt hits 100%, the charger goes off and lets it drop to 95% or so and starts charging again. It does this to protect the battery. Also when you turn off, it will restart the charge.
The battery is lying, but that's not such a bad thing.
Check this out.
http://forum.xda-developers.com/showthread.php?t=871051
My battery has been acting up the last few days as well. As in, going from a full charge to ~35% in 3 hours and then down to ~12% an hour later. No new apps added, nothing out of the ordinary done. Regular uses and charging cycle. I normally reset my battery stats when I flash a new incarnation of a new ROM, but after a couple of days everything seems to be back to normal.
I've been baffled by this, but have yet to find the culprit. An app or searching for signal are my only thoughts.
qman66 said:
Check this out.
http://forum.xda-developers.com/showthread.php?t=871051
Click to expand...
Click to collapse
This makes perfect sense, thank you for the link!
So I plugged my GN in last night and stayed up late enough to see it reach 100%, but I left it charging all night. When I woke up this morning, the lock screen said Charged but my battery widget said 97%. This has happened a few times and every time I can fix it by just unplugging it and plugging it back in. Anyone know why it does this? Could it be because I get lots of emails at night and the LED running all night decreases the battery a little? Thanks!
I think it stops charging when it reaches 100%, therefore the 3% may be lost during that time. This is a good thing, because a laptop, or anything else, eventually the battery will go bad. When you unplug it, then plug it back in, it can cause that battery to go bad faster. Again, I think this is it. My phone seems to do that. I would not worry about it though.
Is the first charge on the Nexus 5 still as important as a few years ago? Or is the N5's Li-Ion battery not as sensitive as Li-Po batteries?
I always used to plug in a new before booting them up, charge the battery completely and then unplug it. When the charge went down to about 5%, I plugged it back in. I always did that two or three times and then - while still trying to do it like that all the time - allowed myself to charge the device for a few minutes only when it was necessary instead of plugging it in and leaving it at home.
Well, on the N5, I didn't manage that - I actually forgot to monitor the battery level yesterday evening before going to bed. This morning, I noticed that the battery had reached 1% during the night and the N5 shut itself down.
Of course, I did now plug it back in, but I wonder if I could have damaged the battery by letting it run down to 1% on the first charging cycle? Or doesn't this matter at all and it will still reach its full capacity after a few charging cycles?
Thanks
YassinTP said:
Is the first charge on the Nexus 5 still as important as a few years ago? Or is the N5's Li-Ion battery not as sensitive as Li-Po batteries?
I always used to plug in a new before booting them up, charge the battery completely and then unplug it. When the charge went down to about 5%, I plugged it back in. I always did that two or three times and then - while still trying to do it like that all the time - allowed myself to charge the device for a few minutes only when it was necessary instead of plugging it in and leaving it at home.
Well, on the N5, I didn't manage that - I actually forgot to monitor the battery level yesterday evening before going to bed. This morning, I noticed that the battery had reached 1% during the night and the N5 shut itself down.
Of course, I did now plug it back in, but I wonder if I could have damaged the battery by letting it run down to 1% on the first charging cycle? Or doesn't this matter at all and it will still reach its full capacity after a few charging cycles?
Thanks
Click to expand...
Click to collapse
I wouldn't worry about it, running a battery to empty is indeed bad but they don't allow you to run it to empty. It is programmed to show 1% and shut down before the battery itself is at 1% to prevent you from damaging it.
Use your phone, when charge is about 20% connect your charger and do not disconect until reaches the 100%.
This is what i have done with mine.
I have reached 2 days standby with about 3 hrs of screen on time.
So I've noticed that the phone doesn't charge above approximately 73% when fully turned off. I'm using the standard Google charger for the phone. It also charges normally when the phone is turned on. See screenshot...
My refurbished Pixel also does not show only around 65% charge after being plugged in for the whole night.
But then when I use it, it sort of freezes at a specific battery percentage, so it is on for example 30% for two hours, before it goes further down. See the attached picture.
So at least in my case, the phone is fully charged when turned off and plugged in, but somehow the percentage count of the phone does not recognize it. Maybe it's more or less the same in your case?
I too am having battery issues since updating to the latest October Android 10. I have bootloader unlocked and rooted with latest magisk Canary build.
I can charge to 100% but it then tends to stick at a certain% for a while and then the battery dies at 15-20%. I've tried battery calibration but it doesn't seem to help
I've had a dose of the same lately, had a couple of days where my charge has reached 42% for the entire day? Still charges fine but from a 100% charge I will lose at least 13% - 16% charge in a few hours on idle with nothing showing as draining heavy in battery manager. If I run it down to 18% or less and try and use the camera it will shutdown and if I can get it to reboot it's on 1%. I've come to the conclusion its the battery (could be wrong) purely as it's acting exactly the same way as my nexus 6p did when it's battery started to fail.