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.
Related
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.
Think i have made a pigs ear of my new i9000, well its new to me, only a week old
when i got it i could charge to 100% fairly fast and then when id unplug my charger it would hold at 100% for a fair bit, certainly if the screen was off it would be their for maybe 1hr with push email, but then when i updated to the new 2.2.1 froyo i read to wipe batterystats, so i did and now my phone charges to 98% (by the way when at 98% its showing around 4.28V ,it used to show that at 100%) without a problem but it had to be left on charge ALL night, yes over 10hrs to get to 100% from about 40% and as soon as i unplug the charger it drops to either 99% or this morning it dropped straight away in a blink of an eye to 98%
whats the best thing to do, i really dont want to wipe batterystats again since i have to drain the battery fully and i have done that about 3-4 time since having it, since i was trying new ROMs
is it possible that if i leave it then maybe by magic it could sort itself out, i mean this morning my battery pro app i have installed was showing 98% but an other battery reading in the phone showed 100%, i have no idea how thats possible!!
*update*
guess I answered my own question, just charged it to 100% and unplugged it at 4.238v and straight away immediately after i unplugged it it went to 97% 4.191v so its getting worse.
am I getting no help because no one can help or have i posted in the wrong section??
any help would be fantastic
thank you
same problem with me
If you search around for battery drain threads, you'll find that this 100->98,97 phenomenon was specifically coded in for 2.2.1, ie: intentional. It supposedly makes your battery last longer or something by preventing overcharging, or something along those lines..
nwsk said:
If you search around for battery drain threads, you'll find that this 100->98,97 phenomenon was specifically coded in for 2.2.1, ie: intentional. It supposedly makes your battery last longer or something by preventing overcharging, or something along those lines..
Click to expand...
Click to collapse
Thanks for clearing that up, yeah that makes sense that it will help the battery, it was not a huge deal just i wanted to know if i had messed it up but from what you said all is good
although the strangest thing this morning just before i read your post i unplugged my phone and it stayed ay 100% for about 4 mins which for me is rather good since i only get about 4hrs on screen time, but thats enough for me, i get easily 30+hrs with push emails
used to get half that on my HD2
My original device always seems to take forever to go below 100%, and I just got a new device that has the opposite issue - it never goes above 94%. So I did some further tests, tonight.
My 94% device goes down fairly steadily once unplugged. But, the device at 100% does not. Also, when the 100% device is drained and I recharge it, it still says it's charging when its at 100% - so what does this mean?
I think that the battery calibration is off, as we already assumed. So, my 94% device is really 100% and I suspect that it would survive beyond 0% as it probably still has 6% juice left in reality. And, in the case of the 100% device, it's probably mis-calibrated to 105 or 110% (or more?). Since the UI can't show you 105%, it just shows the max of 100% until it goes below 100% which can take some time. I also suspect that the device would cut out at 5% or 10% since it's actually drained completely.
So that's the reason, I think. As to the fix, I don't know. What's weird is that these two devices are so different in terms of how the battery status is calibrated.
How can this be fixed? Or "Recalibrated?
I'm letting one of them completely drain, to see what happens.
At least the 94% one gives me an idea on what the battery life is, since I can just tack on +6%. But the one stuck at 100% is a complete mystery - it could be 5% off, 10% or even more.
Also, these run on 2 cell batteries making 7.4V nominal. All the devices before are using single cell batteries at 3.7V nominal. So Android may have issues with that voltage difference.
roebeet said:
I'm letting one of them completely drain, to see what happens.
At least the 94% one gives me an idea on what the battery life is, since I can just tack on +6%. But the one stuck at 100% is a complete mystery - it could be 5% off, 10% or even more.
Click to expand...
Click to collapse
I had the 100% battery issue before and it took a long time for it to dip below 100% (so long that it seemed unreal). Later I decided to let it drain to zero before recharging it to full again. Since then the battery indicator seemed to behave normally and discharged at a normal rate when the tablet was in use.
Have you tried deleting /data/system/batterystats.bin to wipe battery status? Mine sits on 100% for ages so I'm trying this now.
roebeet said:
My original device always seems to take forever to go below 100%, and I just got a new device that has the opposite issue - it never goes above 94%. So I did some further tests, tonight.
My 94% device goes down fairly steadily once unplugged. But, the device at 100% does not. Also, when the 100% device is drained and I recharge it, it still says it's charging when its at 100% - so what does this mean?
I think that the battery calibration is off, as we already assumed. So, my 94% device is really 100% and I suspect that it would survive beyond 0% as it probably still has 6% juice left in reality. And, in the case of the 100% device, it's probably mis-calibrated to 105 or 110% (or more?). Since the UI can't show you 105%, it just shows the max of 100% until it goes below 100% which can take some time. I also suspect that the device would cut out at 5% or 10% since it's actually drained completely.
So that's the reason, I think. As to the fix, I don't know. What's weird is that these two devices are so different in terms of how the battery status is calibrated.
Click to expand...
Click to collapse
samepic said:
I had the 100% battery issue before and it took a long time for it to dip below 100% (so long that it seemed unreal). Later I decided to let it drain to zero before recharging it to full again. Since then the battery indicator seemed to behave normally and discharged at a normal rate when the tablet was in use.
Click to expand...
Click to collapse
I tried that once, by setting it to never shutoff and letting it go over night. The next morning I charged it to green plus 30m as someone suggested in the TnTL thread, but I still had the problem of the meter sticking at 100% for a long time.
Anyways, I installed 3.0.0(TnTL) on monday and decided to also use the CWM clear battery data option, and now it seems to be dropping more as expected, but I'm not entirely sure that I did it completely correctly as by the time that I did the clear battery data option it would've been below 100% charge since I did so AFTER running the update.zip... just have to wait and see now...
Battery Stays at 100% For Ages
My battery stayed at 100% for ages the first time I charged it. Then it dropped quickly and cut out around 50%. I recharged it and it seems to be behaving more normally now. It still seemed to hang at 100% for a while, but no where near as long as the first time. I'm waiting to see at what percentage it dies this time.
my zt 180 tablet never got above 94% also. And it dropped pretty quickly and at around 40% it seemed to get a second life and slow down, but eventually it went all the way down to about 10% and then I would charge it (about 3 hours max). It too is a 7.4v supply.
My Odroid T had a 3.4 supply and it was pretty linear, showed charged at 100% and went down accordingly, though the developers had some issues with a few software releases where it did behave erraticaly and they did a few patches that fixed it.
roebeet said:
My original device always seems to take forever to go below 100%, and I just got a new device that has the opposite issue - it never goes above 94%. So I did some further tests, tonight.
My 94% device goes down fairly steadily once unplugged. But, the device at 100% does not. Also, when the 100% device is drained and I recharge it, it still says it's charging when its at 100% - so what does this mean?
I think that the battery calibration is off, as we already assumed. So, my 94% device is really 100% and I suspect that it would survive beyond 0% as it probably still has 6% juice left in reality. And, in the case of the 100% device, it's probably mis-calibrated to 105 or 110% (or more?). Since the UI can't show you 105%, it just shows the max of 100% until it goes below 100% which can take some time. I also suspect that the device would cut out at 5% or 10% since it's actually drained completely.
So that's the reason, I think. As to the fix, I don't know. What's weird is that these two devices are so different in terms of how the battery status is calibrated.
Click to expand...
Click to collapse
Warning: Slightly off topic -
I'm glad Roebeet was able to get a 2nd Gtab. Hope you found a good discount. Happy Holidays!!!
Now back to the topic discussion...
Butch1326 said:
Warning: Slightly off topic -
I'm glad Roebeet was able to get a 2nd Gtab. Hope you found a good discount. Happy Holidays!!!
Now back to the topic discussion...
Click to expand...
Click to collapse
Off-Topic x2 : yep, got used one that another XDA user had returned!
On-Topic: Still waiting for the battery to discharge, it went to sleep last night. Getting close....
roebeet said:
Off-Topic x2 : yep, got used one that another XDA user had returned!
On-Topic: Still waiting for the battery to discharge, it went to sleep last night. Getting close....
Click to expand...
Click to collapse
I also had the issue of battery showing 100% for a long time and then cutting out around at 50%. One of the posts mentioned doing a battery stat wipe in CWM after charging to 100% + 30 minutes.
I did this with a little twist of my own.
I allowed the battery to drain completely and tab to shut off. Plugged in the charger and immediately did a battery wipe in CWM. Allowed the battery to charge fully upto 100% + let it be on charger for additional time till the battery symbol in the notification bar no more showed charging sign. Again did the battery stat wipe in CWM and then rebooted the tab.
Since then i observe that the battery has been draining as it should be expected to. down to 72% after about 4+ hours of use. I will still be monitoring the battery discharge further for two or three more charge cycles. But I feel doing battery stat wipe in cwm 2 times at full drain and then again at full charge might have helped caliberate it properly.
Let me know if anyone else tries this and gets same or different observations.
Try installing this to measure your current usage over the life of the battery... (dont have a GTab and still considering). Since most likely this widget and the battery monitor are using the same API we will see if its a hardware sensor issue or a software issue...
http://www.appbrain.com/app/currentwidget/com.manor.currentwidget
I suspect its in their battery monitor and not the sensor or API... if that is the case it should be easy to debug (if you have the source). Typically these issues are due to poor polling algorithms...
Im new to android so I am unfamiliar with profiling capabilities of the platform...(Still learning)
Perhaps this will be one of the 'little fixes' that will be present in the latest FW update when VS drops it tomorrow. I have the 100% unit BTW. A fix would be nice.
Reading this thread this morning it got me thinking about my gtab battery situation. When I first got the gtab, the battery stayed at 100% for hours, then the percentage dropped like a rock. Over time, the battery dropped in more regularly, although it drops in large numbers (like from 100% to 83%, then to 67%, and so on). I'm currently running TnT Lite 3.0.
This morning I charged the battery to 100%, and while plugged in (to the AC outlet), I reset the battery stats using cwm. The battery today has been steadily going down throughout the day as I would expect. In over 8 hours, I watched the battery go down steadily from 100% to 84%. So far, so good.
my exp
Tried draining once, just let it sit, didn't fix it.
Tried again but this time I kept the screen on and watched the voltage, shutdown was near 6.8 volts. Now the meter is accurate. YMMV...
@it'sDon - it wasn't fixed in the update.
I was in the same boat as most of you. Took a very long time to go down from 100% and then zonked out completely at ~10-15%. It's now been charging for a few hours and it's been sitting at 100% for quite a while but the light is still red (so it's still charging) which means it will probably happen again looks like it's charging to some value over 100% and when it discharges, knocks out while the meter is still reading as having juice. Roebeet is 100% on the money.
I am going to try the CWM battery value reset some of you mentioned to see if it does something once my light is green, then I won't charge it and watch it like a hawk once it hits 20% to see if it shuts down at 10-15% or a value less than 3% which is acceptable I think.
I never had a problem on my stock(ish) g-tablet. That is until I installed the latest update.
I had to do a data wipe before any of the cosmetic TnT changes would show. After that the battery now seems stuck at 100%. This wasn't that way before, so I will try draining the battery, and see what happens.
Since I found that this was tied to my latest update, I think that I should call CS and complain.
My battery drain didn't make a difference, either. Still haven't pinned down a fix that works.
At least those of you with 94% max have a general idea when your battery will die. With us "100% forever" ones, we have no clue.
Actually, I may not have a problem after all. I have had my tablet on for about two hours. It is now showing the battery at 86%.
So this has happened twice now. I'm running on ARHD 4.1.0 w/ Bricked 1.0.
My battery will be running normally, normal drainage, etc., and then it'll just drop from 90 to 70% in less than an hour, and normally drain for another hour or so, and then at around 60% just die. I can't attach a screenshot since normal screenshot apps aren't working and the stock function keeps producing invalid images, otherwise I would, but it literally just looks like it got to 60% and instantly dropped to 0%, there's just a vertical line of missing percentage. I took my phone out of my pocket, expecting it to be around 40 or 50%, and it wouldn't turn on. When I hooked it up to the charger, it took a good 5 or more minutes to even respond to the power button. Do I have a bad battery or just incredibly out of whack battery stats? I have never had this problem with an android phone before, and I thought for sure one full charge overnight would fix it, but I guess not because it happened twice. Any suggestions?
Edit: I use an app called battery snap to monitor the battery level and temperature with a widget, I checked a snapshot history while it was charging and for a few seconds it was at 0.002 volts. But then it jumped back up to 3.897 or something around there. That doesn't sound very good to me.
MusicMan374 said:
So this has happened twice now. I'm running on ARHD 4.1.0 w/ Bricked 1.0.
My battery will be running normally, normal drainage, etc., and then it'll just drop from 90 to 70% in less than an hour, and normally drain for another hour or so, and then at around 60% just die. I can't attach a screenshot since normal screenshot apps aren't working and the stock function keeps producing invalid images, otherwise I would, but it literally just looks like it got to 60% and instantly dropped to 0%, there's just a vertical line of missing percentage. I took my phone out of my pocket, expecting it to be around 40 or 50%, and it wouldn't turn on. When I hooked it up to the charger, it took a good 5 or more minutes to even respond to the power button. Do I have a bad battery or just incredibly out of whack battery stats? I have never had this problem with an android phone before, and I thought for sure one full charge overnight would fix it, but I guess not because it happened twice. Any suggestions?
Edit: I use an app called battery snap to monitor the battery level and temperature with a widget, I checked a snapshot history while it was charging and for a few seconds it was at 0.002 volts. But then it jumped back up to 3.897 or something around there. That doesn't sound very good to me.
Click to expand...
Click to collapse
I don't know much about this, but I don't think battery stats have anything to do while the phone is dead. Even if it does, the phone would at least respond after a minute or two, not 5..
My suggestion is that you can order an Anker battery which is kinda cheap ($15 I think) and try.
You won't loose anything
Edit: Try wiping battery stats, do a full charge, fully discharge and fully recharge again and see if it helps (In your case I don't think this will help, but huh, let's hope ;D)
Sent from my HTC Sensation Z710e
claudenegm said:
I don't know much about this, but I don't think battery stats have anything to do while the phone is dead. Even if it does, the phone would at least respond after a minute or two, not 5..
My suggestion is that you can order an Anker battery which is kinda cheap ($15 I think) and try.
You won't loose anything
Edit: Try wiping battery stats, do a full charge, fully discharge and fully recharge again and see if it helps (In your case I don't think this will help, but huh, let's hope ;D)
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse
Thanks, I'll try it. I flashed the new cm7, since I just got tired of sense woes. I read battery life on this was amazing, and I'm hoping it was just a bug with the kernel/rom I was using. Battery stats would've been wiped when I wiped for flashing this ROM, so I'll do a full battery cycle and cross my fingers. My only thought is that maybe, if the battery stats were screwed up enough, it thought it was at 50 or 60% but really it was more like 10%. I remember having issues after I flashed the custom kernel, where before I flashed I was at 70%, and when I rebooted I was at ~10%, and I was like what the hell? So it ended up dying on me, but then I turned it back on and it said 50% or something around there. And then it functioned as normal until it died again, for real that time. Hopefully it was the kernel causing the issue. I'll run a few tests with this and see. If it is the battery, I'll try t-mobile for a warranty replacement of the battery.
The battery measurements seem to be really quirky on this phone. When the phone is idle it seems to drain anything from 50ma to 400ma for no particular reason. You cant really rely on the % too closely
Yeah, I've found the percentages to be pretty inaccurate. Hardly an hour and a half on the battery and it's down to 84%. I did play a game for like 10 minutes and the screen has probably been on for 20 or so, so that's not incredibly unreasonable. I'm just waiting for that dropoff to 0%, if that happens again I'm thinking it's hardware, because I'm running an entirely different ROM and kernel right now.
So it just happened again, went from 42 to 14 after reboot, had to remove battery and reinsert to fix. But other people have reported this issue on cm7. So, I'm thinking maybe that it's an issue with android 2.3.5 or the kernel for it, since it's happened on both arhd 4.1 and cm7, both 2.3.5 roms. I'm going to try and flash faux's cm7 kernel over it and see if it fixes it. May or may not, might be a long shot but worth a shot, I'd rather not switch roms for a third time in the same day.
I posted this in another forum and the response I got was somewhat weak. Instead of re typing everything I will cut and paste my posts and hopefully you guys can guide me in the right direction!
Here was post 1 -->
I just bought a Rooted Nexus S from ebay. It is running this ROM Nexus S ICS 4.0.4 stock OTA ROM (IMM76D)
Now, I know nothing about android, I'm coming off a series of old turd phones because i'm always breaking them. I'll probably break this one too, but hopefully not for a while.
When I got the phone I put the battery in and turned it on, then charged it overnight. It will only charge to 54% and stay there. I talked to the seller he said it charged normally for him. He said he did a complete wipe and USB wipe before he shipped it.
The battery seems to drain normally (I guess, I have nothing to really compare it to) from 54% but it would be nice to have it charge to the 90% -ish range haha. I allowed the battery to drain to 40% and put it back on charge, it been on charge for almost an hour and will only charge to 41%? Do you guys have any ideas what I can do to fix this? Is this a sign it needs a new battery, or a software glitch? The seller said the battery shouldn't need replacing.
Also in the battery app under setting, Android System is using 28% is that a lot?
My last question is an important one to me haha. Is there anyway to convert the querty keyboard to a T9? I 've gotten used to texting with one hand and T9 makes it so much easier to do so.
Thanks everybody!
Someone recommended I try the battery calibration app So I did!
Post 2
Ok, I ran the Battery Calibration app. I let my phone charge for hours. It would only charge up to 38% this time. However, the percentage was 38% but it was charged to 3810 mV (and would not charge past this point). And full charge is approximately 4200 mV according to the Battery Calibration app. So I assumed that 3810 mV was my current battery's max charge (keep in mind it is a couple months old) and set battery calibration at that point.
This is from the app description --> It's suggested, but not necessary, to let the phone fully discharge after calibration, then charged to 100% without break.
So thats what I'll do. I should mention that even though I ran the battery calibration, the battery percentage has been draining from 38%. In other words, my phone now reads 26% battery charge, but is at 3758 mV.
I'm thinking that when I go to charge it after fully draining the battery, it will hopefully charge close to 100%. It seems as though the percentage is the only thing that is off. Because the mV reading seems accurate.
Here is a screenshot, what do you guys think?
This site won't let me post the screen shot until 8 posts, but I will do that once I get there!
Post # 3
The app says to let the phone fully discharge after calibration. I am now at 15%, but mV is at 3658. Should I recharge when the percentage has dropped lower, or when the mV reaches a low point? Are these phones really this finicky. I'm starting to miss my old 2007 flip phone haha
It's now at 14% and now asking for me to plug it in to charge lol but mV is still way high (3655)
Post #4
update, charge % reached 0 and the phone shut down. Now charging, Current charge is at 0%, 3595 mV. No one has any idea whats up?
Shouldn't mV be near 0 when charge is at 0%, and be near 4000mV when charge is near 100%?
hopefully you guys can help me fix this issue. Otherwise it'll have to go back to 'ol reliable, the 2007, multiple cracked screen, nokia slider lol It's not pretty, but it works!
There is a built in safety feature in our batteries to prevent deep discharges. IIRC, the safe cutoff point is around maybe 34xx mV. I could be off, but its to prevent damage to the battery. Here's more on them
http://batteryuniversity.com/learn/article/is_lithium_ion_the_ideal_battery
As for voltages, a full battery should be around 4100mV. Mine tops out around 4196. I'm not too familiar with all of it though. Most of the stuff I learn is through observation and links others provide.
Thanks for the reply! So are you saying that when the voltage is around 34xx the battery charge % should be close to or around 0%. And when the voltage is near the 4000mV range the charge %tage should be approximately 9x%
Do I have the right idea here?
Its hard to say while its charging. My phone is at 4000mv around 70% so I don't really know exactly how it works. But a full battery should read around the voltages I posted. There's people on here who know more about it, so hopefully they'll chime in.
But yes. When its close to zero, it should be around that range. It will differ from battery to battery.
Ah k thanks! My original problem was that the phone would only charge to 54% and would not go past that point. I'm waiting to see if it will get into the 90 ish % range after running the battery calibration now.
The app itself doesn't actually do anything. The stats will get reset once the charge reaches 90% My girlfriend's phone was the same way. It wouldn't charge past 75%. I let the phone run dead and charged it while it was off and it fixed the problem. If it doesn't go to 90%, try charging while off and just letting it run until it gives the warning to charge, turn it off and let it charge overnight .
Ok. Well I let the phone run dead earlier today as I mentioned in one of the above posts. But I didn't charge it with the phone off. I put it on charge with the phone on, and now it won't charge past 11%
It just seems to be getting worse and worse? It's been going between 10% and 11% and has been at 11% for about 2 hours now. Maybe this time I will drain it again and try charging it with the phone off like you suggested.
This is slightly annoying
All else fails grab another battery. They're dirt cheap on eBay. Just get one from a reputable seller
Ok, so I let the battery drain. then fully charged it with the phone off. When I turned it on, it had 47% charge.
The guy I bought it from said that before I buy a battery I should download an app called rom manager and download a new rom. he thinks its a software bug because he had no problems with the battery when he was running cyanogen mod 9 on it.
I wouldn't mind giving trying this, except I don't even know what a rom is. Is it operating system? I like the way the phone works now, If only I could get it to charge fully.
Thoughts?
Ok, I just did a bunch of reading and downloaded ROM manager premium. Hopefully I get this figured out. Owning one of these phones is a lot of work
lts pretty much a pocket computer. Coming from an older type of phone, a lot of things are going to be different. Gotta start somewhere. Reading up on it and toying around with the phone will help in the long run. Trust me.
or not....
louderstill said:
or not....
Click to expand...
Click to collapse
Haha, pretty much. I'm slowly starting to learn more. I didn't think there was this much of a learning curve, thats what took me by surprise thats all. I'm a fast learner so I'm not too worried. I didn't have time to play around on it tonight, maybe on the weekend. I found out I could use it without the sim card which is awesome! Because now I can use old faithful while I learn more about android.
Thanks for the help so far though, I'm sure I'll have more questions soon haha
Haha. Yep. You can have tons of fun just using it over wifi!
Do keep in mind, fully dishcharging a lithium ion (li-ion) battery deteriorates the battery even more. We only discharge because older phones use nickel cadmium batteries which need more maintenance to get to their maximum life span and use.
Off topic though.
Battery calibration just wipes your battery stats. You can do this by going into any recovery program eg clockworkmod receovery or team win recovery project. You can wipe the battery stats yourself. If that still doesnt work. Try doing a clean install of your custom rom or kernel. If your not on a custom rom or kernel. Nor your rooted. Try formating the SD card in the Nexus S (or fully wiping the sd card). Than do a factory reset.
Ok, so I finally had some time to learn to flash etc. After backing up, I downloaded and flashed the same rom from SD, I cleared davlik cache and also selected the wipe data and cache option from ROM Manager (I assume that this is what is called a clean install?)
This is the ROM I am using http://forum.xda-developers.com/showthread.php?t=1653713 Slightly customized stock ROM, rooted.
After start up I waited a while and then plugged it into the charger, it only charges to 54% still. Sometimes it creeps up. One thing I noticed is that if I use the phone while it is charging, it actually drains the battery. So it will go from 54% to 52% and slowly drain. Is this an indication of a pooched battery?
Any suggestions? I will order a battery. Where do you guys order your batterries, I read that the oem samsung 1500 is reliable.