Related
Hi all, i have developed this weird problem in my jasjar and i'm sure it's some settings that need to be changed somewhere and not the battery itself. When i first got the jasjar, it gave me a good 48 hours battery backup on standard use but i lost my charger and started using usb to charge it. it's since then that my jasjar drains the battery in less than 12 hours. i have tried replacing 3 batteries but to no better effect. I remember reading something about the Li ion polymer batteries having the memory effect or something and how to reset that in the bootloader mode. if you guys could help me figure it out and fix the problem, i'd appreciate it! here's the details of my rom.
R:1.13.00
G:42.47.p8
D 2.01.06 wwe
the rom is the wm6 from jwright.
(nb: i had the same problem with my shipped wm5 rom and i thought upgrading it would help but it didnt apparently).
How long do i need to use the battery to check the drain thingy. the reseller tells me to use it for 2 weeks before judging it. i'm screwed with having no battery life to this otherwise beauty of a device! if i could get any help, it would be much appreciated. thanks in advance. (josh).
Had the same problem, been happening all week, the phone would just switch of even though it registered over 80% charge. no i am happy again because i read on the forum that you need to totally discharge the battery occationally for it to get to a full charge, it appears that there is some sort of memory effect where the battery thinks it is nearly discharged, try it, i am sure you will find that it workes.
Had the same problem, been happening all week, the phone would just switch of even though it registered over 80% charge. now i am happy again because i read on the forum that you need to totally discharge the battery occationally for it to get to a full charge, it appears that there is some sort of memory effect where the battery thinks it is nearly discharged, try it, i am sure you will find that it works.
awright...i'd try it. thanks for ur help.
mayer said:
Had the same problem, been happening all week, the phone would just switch of even though it registered over 80% charge. now i am happy again because i read on the forum that you need to totally discharge the battery occationally for it to get to a full charge, it appears that there is some sort of memory effect where the battery thinks it is nearly discharged, try it, i am sure you will find that it works.
Click to expand...
Click to collapse
thanks..
I too has a similar problem but this method did not solved my prob as my jasjar switches off by itself at 40%.
I had a similar problem a couple of weeks ago as a charge would last less than 24 hours when I used to be able to last 2-3 days.
Soon sorted it when I found that the Jasjar had decided to disable the automatic switch off, now a charge is back to lasting 2-3 days.
Mike
Had my MDA PRO for 1.5 years, and never had this problem. Battery lasted for 2-4 days on average, although now I have a 3200mAH battery it lasts for well over a week on a single charge
Lithium ION and Lithium ION Polymer (the HTC Universal uses the latter) do not suffer from any "memory effect". The only battery type that does to any significant extent is Nickel Cadmium, which is rarely used these days.
It's also impossible (well, almost) to completely discharge Lithium ION Polymer batteries - internal circuitry in the battery shuts down the cells when the charge gets too low, at up to 10% charge. This is because a completely discharged L.I.P. battery becomes unstable, broken (unable to be recharged), and runs the risk of explosion or leaking in this state. So don't attempt to drain those batteries completely dry folks - it's dangerous! Letting them run down naturally in your Universal should be safe though because of the cut-out mentioned above.
Maybe the Uni just has a large batch of bad batteries? You should also check what apps you have running on it all the time, and how often you use bluetooth and wi-fi - these two REALLY drain the battery if you keep them on all the time... Also try MemMaid, this is great at cleaning up your notifications queue, which is where lots of apps leave old and obsolete entries clogging it up.
I have the same problem. I do not know where the charger is, so I am always using the USB while syncing. I also tried 2 batteries, but they both last about 12 - 14 hours. Maybe it is caused by WM6.
I did not quite get this solution:
"Soon sorted it when I found that the Jasjar had decided to disable the automatic switch off, now a charge is back to lasting 2-3 days.
Mike"
What is the solution?
2 421....:
sorry for lang. the above understands(i hope)
nastavenia(settings)/napajeni(power)/rozsireni(advanced) tam zaskrtnes co xces a nastavis casy. ak pouzivas phonealarm musis aj tam. pozri si aj podsvirtenie(backlight).
btw aj had the same prob. appeared after 6mnth. i bought new battery. btw here is several threads with same prob. try 2 look for solutions there(imho its only one-new batt.)
I feel like I'm walking on eggs...I bought my Jasjar used on eBay just over a year ago, still the original battery. I almost never use the 110v charger, always a USB conection with my Mac, often recharging at 55-75%. I just intentionally ran down my battery to 18% (got warnings to recharge), and recharge via USB/Mac again. It took me almost 4 days to get to 18%, and Bluetooth is constantly on for ready use with my earpiece.
Curious: are the problems with original or replacement batteries? Cheers,
Update to Radio 115 or 114
It's worth taking into consideration that when flashing, you really need to have a full battery. There are reports of batteries starting this kind of behaviour after user has flashed with drained battery, then causes battery charge issues until next reflash.
IMHO even if u charge with a full charged battery still u get a prob so i think its a common issue with the jasjar and its power managment software itself by default as lot of people with diffrent ROMs are complaining about it.
no changes...
well, folks, i tried all these gimmicks but not to any definite changes ... i guess i need to consult the service center guys at last...i didn't want to do that but i guess i need to. i'm sure it's not my battery as i've replaced 3 of them...i dont kno what else to do!!! thanks for ur posts tho as i get to try diff things to check if ma battery is doing ok...keep postin...thanks...
josh.
how 2 discharge a battery >>>>>
problem with battery?
I have the same problem, it firs appear on original battery when charge was 40-50% so I have bought the same battery model (1620mAh). But it doesn't help. Now I,m using the 3200mAh battery and it doesn't help as well. The thing is that XDA switch off it self always on deferent charge level (sometimes is on 20%, 45% ar 80%...so is very difficult predict when it happen again). And one more thing...when it switch-off and I try to switch-on back, I can't (keep switching off), only slolution is put on charger!!!
I have downloaded the service manual (I think called "confidential") and it mentioned that it could be a problem with main board (so its HW problem). So can anybody tell me is a problem with bat or MB? (replacing the MB is fcjfdj$#ing expansive). Thanx.
well if your XDA does not switch on until you start charging it that's a clear indication that your battery is empty. I have the same with my faulty battery. Replaced it by a working one and it's fixed. Something is definately messed up with the charging circuit or the batteries though. They are not supposed to die so easily.
SpyderTracks said:
It's worth taking into consideration that when flashing, you really need to have a full battery. There are reports of batteries starting this kind of behaviour after user has flashed with drained battery, then causes battery charge issues until next reflash.
Click to expand...
Click to collapse
The first time I flashed the PDA I ruined my battery. This time I thought I'd be smart and I put in the old battery while flashing. After flashing I put back the new battery and now that one is broken too! It wasn't even in the PDA when I flashed it. How bizarre is that?
I have to admit I did not fully charge that new battery before flashing, but I figured it would be safe since it wasn;t in while flashing. The battery worked fine the day before I flashed my phone (got the "charge now or save your work" message), but after the flashing and putting it in, it just crashes at around 30% or 40%. The usual battery misery.
Maybe I should try fully charging it and then flashing again. Trouble would be how to get it fully charged though. I always felt charging cuts off early on the "broken" batteries (pull the charge plug and stick it back and it charges for a while again).
I managed to restore my battery to good health by completely discharging it in bootloader mode.
First I completely charged it. When the led went green I pulled the shcarge cable and connected it back again. After doing this a few times it doesn't stay orange so long and then I stopped and left the cable disconnected.
I reset the phone (on full battery) and then I set the unit to boatloader and waited for it to completely discharge. I reset the phone again (on empty battery) and low and behold my trusty "charge now or lose data" warning came back.
BTW I reset the PDA hoping maybe it would store the power levels. I remember that trick from my Palm days where sometimes you had to reset a PDA on full battery to calibrate it.
I charged it back to full capacity and started using the phone as normal. When the battery was empty I got no crash but a friendly warning telling me my battery was going low. Phew.
Will try the same with my other troubled battery over the weekend.
I have the same Issue.But , I think it's about Rom.
and I'm try a lot of ROM version ,only one Version canbe use more than 3 day.
I can't find any reason ,.
discharge in bootloader ,I do it ,But battiery is same time for used.
I have charged my Nexus One yesterday for the first time. I live in holland so i had to use my USB cable, and the power adapter that came with my HTC hero to plug my USB cable in.
After the phone was charged 100%, i disconnected it from the charger and only downloaded + added a widget to my home screen. After i did that the battery was already down tot 97% :O:O
Is it defective ?
i noticed having to complete a few charge cycles.. charge fully, use it till dead, charge again
now it seems to hold out much longer
Hmm ok i'll try that. But did yours also drain this fast?
what setting is your screen on? seriously though, im sure some other battery experts here would know, but i think they take a few cycles to get to maximum efficiency
malicious85 said:
what setting is your screen on? seriously though, im sure some other battery experts here would know, but i think they take a few cycles to get to maximum efficiency
Click to expand...
Click to collapse
What do you mean with screen setting, and what should i put it on?
Sorry totally new to the phone hehe
I've noticed this too. However as soon as the battery reaches around 50% it takes a lot more to drain so it evens out in the end I guess
teihoata said:
I've noticed this too. However as soon as the battery reaches around 50% it takes a lot more to drain so it evens out in the end I guess
Click to expand...
Click to collapse
Hmm ok so it also went that fast on your phone? i have been using it for about an hour now and its down to about ~90% =\, concerns me a bit.
Found out something else, concering the usage of the screen. When i look here:
Menu -> Settings -> About Phone -> Battery Use
The phone tells what uses the battery the most or something, but the strange thing is that it says:
Display 55%
Isn't that very high? Maybe that is causing my battery to drain so fast
Battery meters are not an exact science. Its using what it knows about the battery's state to guess of how much % is remaining. The battery meter will need to be calibrated once, and then overall battery should improve with your next normal 3-6 full charges.
Again, you do not need to and you shouldn't repeatedly drain the battery to 0, only once is this needed to set the phones battery meter, unless you clear it (possible within amon ra's bootloader).
As for your observation, yes that is completely normal, there is not a whole lot of definition within 3% of battery as far as displaying it. What the real picture? Enter in #*#*4363*#*# on your dial pad and then go to battery information, and you'll see the accurate voltage. (this is also accessible from "spare parts" if you have it)
Nipje said:
Found out something else, concering the usage of the screen. When i look here:
Menu -> Settings -> About Phone -> Battery Use
The phone tells what uses the battery the most or something, but the strange thing is that it says:
Display 55%
Isn't that very high? Maybe that is causing my battery to drain so fast
Click to expand...
Click to collapse
All %'s here are vs the amount of time on battery (shown at the top in h:m). If you just unplugged your phone and you go looking here, you'll see the display % VERY HIGH... because the screen has been on the entire time its been unplugged
Its a % after all of the usage since last unplugged.
i've noticed my battery life is much better since i got the desktop dock.. lots of people charge until the light turns green then immediately grab it and start using..
leave it for another hour or two and it seems to get much better.
dont know if anyone else has noticed this but the top corner indicator light turns green once the battery goes somewhere over 90%, leaving it charge longer will get you to 100
malicious85 said:
dont know if anyone else has noticed this but the top corner indicator light turns green once the battery goes somewhere over 90%, leaving it charge longer will get you to 100
Click to expand...
Click to collapse
Good point, I did notice this by accident a few times.
Nipje said:
What do you mean with screen setting, and what should i put it on?
Sorry totally new to the phone hehe
Click to expand...
Click to collapse
You probably found this by now, but one flick to the left and you should have a widget for WiFi, GPS, etc. The far right one toggles 3 levels of screen brightness. The brightest two settings really suck down battery.
just a tip, when you are draining it to recalibrate the battery, after you get to the point that the phone shuts off, boot into the bootloader and run that thing till it completely dies... i did this for my phone, sat it in bootloader with a bright ass screen for like 15 min before it finally finished off... get every last ounce of juice out of it before you start charging it back up
Hmm thanks for al the reactions guys. I'm going to recalibrate my battery now, and lets see if that helps a bit .
Then i have a other question, its not about my battery but since i already have a open topic i dont want to create another one .
Can anyone of you test the following:
When you are calling with someone, and your calling volume is on the maximum (so the volume of the speaker that you hold against your ear). Can anyone notice a little crack from the speaker when the other person talks a bit loud or make's a loud noise? I'm wondering if there is something wrong with mine. With several tones the ear speaker cracks a little bit, like the sound is to loud or something?
Nipje said:
Hmm ok so it also went that fast on your phone? i have been using it for about an hour now and its down to about ~90% =\, concerns me a bit.
Click to expand...
Click to collapse
Yep sounds about the same on my phone, dont worry about it lol
The draining thing is from the old nickel days, the lithium batteries are made for daily use so just treat the phone as you would normally. The battery will get better as time goes by.
Also I am not having that problem with the speaker
Hmm, I have my device since last week (Netherlands) and the battery usage is frightening. Sucking it dry in about 24 hours. I haven't let it die out completely though: I thought lithium batteries were not supposed to be used that way. Ni-Cad batteries were used that way.
Ah, see here:
Guidelines for prolonging lithium-ion battery life
Lithium-ion batteries should never be depleted below their minimum voltage (2.4 to 2.8 V/cell, depending on chemistry). If a lithium-ion battery is stored with too low a charge, there is a risk that the charge will drop below the low-voltage threshold, resulting in an unrecoverable dead battery.[citation needed] Usually this does not instantly damage the battery itself but a charger or device which uses that battery will refuse to charge a dead battery. The battery appears to be dead or not existent because the protection circuit disables further discharging and there is zero voltage on the battery terminals.
Lithium-ion batteries should be kept cool. Ideally they are stored in a refrigerator.[citation needed]
Aging will take its toll much faster at high temperatures.[citation needed]
[edit] Prolonging life in multiple cells through cell balancing
Analog front ends that balance cells and eliminate mismatches of cells in series or parallel significantly improve battery efficiency and increase the overall pack capacity. As the number of cells and load currents increase, the potential for mismatch also increases. There are two kinds of mismatch in the pack: state-of-charge (SOC) and capacity/energy (C/E) mismatch. Though the SOC mismatch is more common, each problem limits the pack capacity (mA·h) to the capacity of the weakest cell.
Click to expand...
Click to collapse
So, if you want to brick your battery, by all means, suck out all the power.
i have a mytouch but i think the things i do can be used with all androids....first recalibrating is a good way to get a fresh battery...then the brightness also helps along with any wireless things u dont use like wifi gps etc.. they should be turned off an brightness should be low...i have downloaded a app lately called automatic task killer..i think this is better than any other task manager because other task managers dont kill apps wen phone is on standby ..apps r still running wen screen is off an automatic task killer kills them..i think u should download this and also have a task manager to kill apps wen u use the phone..another thing is charging the phone wen its completely off..wait until the the light turns green then leave it on for another hour or two then turn it back on....i have seen an increase in bettery life by doing all this...any one esle have any tips ..let me kno
After being dropped while charging, the battery of my Kaiser just use almost a day (previously from 2 to 3 days).
I installed acbPowerMeter to measure power consumption and it shows an unbelievable value: 4294967mA
When plugged into the charger, the power consumption back to normal (I think), between 90-275mA. I wonder if Kaiser power circuit is broken or not.
Who have experience please give me an advice. Thanks!
Hi, if you've dropped your device you should check the connections to the batery. Try pulling out the batery, check if the "pins" are aligned, check if you batery isn't cracked.
Other thing that might have happened is that if you install new software it may drain you batery, i had the same problem after flashing and was only solved after getting a fix from the chef.
Thank you for reply me!
I checked the battery connectors and tried different battery (borrowed from my friend), so the result is still the same. I did not install any software before and then.
Hello, I have same issue with battery drain. I don;t know if it was droped because I just bought it used and battery is draining in one day. I tried another tool called Mobadi, and it saying that my Kaiser using 90-200mA. how about you?
90 -200mA is normal draw. Your battery is losing capacity over years of use, thats normal.
V3rt!g(o) said:
90 -200mA is normal draw.
Click to expand...
Click to collapse
...normal draw during screen on and active use...
with these older devices, there are too many tiny things that can go wrong which cause weirdness.
1. Testing with a known good battery (NEW does not equal 'known to be good'-- I had two new batteries which would not even take a charge, followed by a new NON OEM battery with a low capacity cell inside! they use some undersized cells probably for pricing reasons... sort of like sticking an AA battery in a C cell shell. Not really sure what you can do in that case...)
2. Hard reset and see if the problem persists before doing any more troubleshooting.
Does anyone have any suggestions on what I can do to test which one might be bad? Any app you know of that can monitor things and tell me if a rogue app is killing the battery or if the battery is bad?
I was running mik 1.1 and was using it pretty heavily with gaming and downloading stuff. The phone died after about 7 hours. I thought that maybe the rom or cwm or something else might be killing the battery. Something strange though is that, like I said, I ran the battery until the phone shut off. Then I left it off and put it in a wall wart charger for about 8 hours and the status light was still orange. My gf had the phone and told me once she left it plugged in overnight and in the morning it was only at like 50 something percent. I thought maybe the charger went bad so I gave her another one and she didn't say anything else about it. I'm starting to wonder if maybe the phone's battery has a weak or bad cell. I kinda doubt that there's something wrong with the charging circuitry of the phone but there could be, anything is possible. I will probably take it to the repair center and tell them about it and see what they say. I tried looking on htc's site for oem replacement batteries but couldn't find anything. I found lots of aftermarket but I didn't want to go that route.
I don't know if it would not be a good idea or not to try and use my original evo battery just flipped over. I suppose if that's the only thing I have to try and troubleshoot this problem then it will have to do.
Can anyone give me suggestions or has something similar happened to you?
Now let me see if I can find that evo battery..........
Spare parts, in the market if not on your rom by default, had a battery information tab that will indicate battery health as well as what kind of plug the phone detects when charging (usb, ac, or none)
Sent from my PG06100 using XDA App
Like danaff37 said, spare parts can be useful. Also try CPU Spy, free from the market, which shows what % of the time your CPU spends at each frequency, but this actually more relevant for determining if your phone is properly sleeping..
For proper charging you can get an app like CurrentWidget or Battery Monitor Widget which tells your the current consumed during usage or current injected during charging, as well as the voltage in mV. Full charge should reach around 4200 mV, and when charging the current should be around ~800 mA for lower % battery left.
Thanks for your input. I found the evo battery and did the same thing as before. I ran it until the phone shut off and then put it one the (same) charger and went to bed. About seven hours later, it was still orange charging. Both times the phone was off. Now something that could be a possibility is the charger is weak or bad. When I put my evo on it, it charges seemingly fine. I should try using the battery until it shuts off again and use a different charger and see what happens. Six to eight hours charging, with the phone off, coming from a dead battery, on a Motorola charger that has a rated output of eight hundred milliamps at five volts. I have others at different output rates and a two amp charger intended for an ipad. Some might say that the charger is too much for the phone. The charging circuitry only pulls as much amperage from the charger as the phone was designed to. Now on the other hand if I put a smaller output charger on, say one hundred and fifty milliamps, it will take longer to charge the phone than usual. "They" say trickle charging is better. Whatever. I will post my results if I find any. Or, I just might trade the phone in for a nexus s or an evo 3d.
I was just about ready to throw in the towel and say the phone was defective, but then things started happening. I will fill you in on what I have done in the meantime. Okay so the flipped over evo battery kinda works but not completely. It will charge but not to 100% and green light. To test this, I took the evo battery out of the shift. It didn't seem to want to go more than 98 or 99%. I put the battery into the evo and after a few minutes the light went green. This was initially off. Then I booted the evo and let it go to sleep. After it booted the light went orange then green after a few minutes. Okay so the evo battery is capable of going to 100%. These charging tests were done with a different charger.
I forgot to tell you, I let the evo battery charge while I was at work and the phone was off. So the battery was charging roughly twenty hours and still no green light. I suspect that even though the positive and negative terminals aligned with the correct tabs on the shift, the center two contacts must be different internally than the shift battery. I speculate that those center tabs are for the battery and phone to communicate to each other during it's charging state. I am guessing that the battery tells the phone it is fully charged and to go trickle charge and perhaps the evo battery wasn't communicating to the phone or the phone didn't know when to say it is done charging. The battery never got hot either.
The shift was rooted, running mikshift 1.1 and the latest clockworkmod recovery. Here is where I suspect that there still might be charging bugs with that setup. I used the pcxx.zip file that when booting into the bootloader, would flash the phone back to stock everything. After trying this and assuming that the phone was back to stock, I kept going with my what the hell is going on with this phone battery charging test. A note about the flipped evo battery. Yes it will work in a pinch but it won't charge properly. Luck has it that the notches in the battery and phone allow it to work in a shift. Only thing is, the shift battery won't work in the evo. The tabs are on the wrong side and the phone's tabs won't allow the contacts on the battery to meet up with the phone's terminals.
Okay, where was I? Trying different chargers wouldn't make the shift green light full charge. I tried the same chargers on the evo with it's original battery in and it would green light after a few minutes on or off. There wasn't anything wrong with the chargers. Oh and another note, while using the battery monitor widget, I noticed that both phones wouldn't pull more than a little over three hundred milliamps of power from the charger to the battery. Interesting to know how much it really pulls from the charger.
Anywho, I tried something different for my process of elimination testing. I actually ruu flashed the shift back to factory and guess what happened..... The battery and phone were charging both on and off all the way to green full charge at 100%! I think I'm getting somewhere with this! All my luck, either it is a known bug somewhere in the forum in a place I haven't stumbled across or I'm the only one that this is happening to. It doesn't really matter I guess.
My conclusion, which isn't scientific by any stretch of the imagination, is that the phone isn't truely back to factory unless you ruu it. The pcxximg.zip doesn't put everything back to stock. I haven't narrowed it down to what is causing this behavior. I don't think it is root. It could be cwm recovery or the rom or both. I didn't try the stock rooted zip either. I suppose I could go further with this investigation but I am too lazy to now. I might root it again and just leave things stock rooted. I might activate this phone in the morning and run it all day tomorrow and see how it acts. I will have to charge it a few times during the day to keep the levels up when I really use the phone heavily. I've written enough for now. Does anyone have anything to ask or add to this topic?
Since the latest update to CWM phone-off charging finally works again but the light never turns green. It charges fully but with the phone off the LED never turns green. It's not just you.
EDIT: If this is not the actual question I apologize. The posts were far too long to actually read
^ Shift Faced
OK. I thought something might have been broken.
Forgive me, I am truly a newbie to Android after having a BB for 8 years. This battery thing is killing me. I am on my 2nd Evo Shift, the 1st one wouldn't last for more than 2 hours with barely any usage so they gave me a new one. This one barely lasts 5 hours. I am barely running anything. I took it into the store and they thought I was going to be running all these programs, but I kill everything. They told me the "battery trick" about turning off the phone and unplugging it and plugging it back in 10 times so I did that but I am not getting any more life out of the battery. My display is constantly using at least 70% of the battery it says even if I turn it down very low or if I set it to choose its setting. Do you have any advice for me? I am not running a task killer, I kill all the programs I am not using. I have no widgets running because I am afraid to use the battery, I only have 2 screens out of the 7 with things on them. I am being help hostage by my cool phone that I want to use but am scared to kill the battery! (sorry for the long post)
Ok if you use a lot apps just close them after (for stock 2.2) . Even on stock you can literally stream music and movies for about 4-6 hours. (sometimes a lot more) . The background info that runs doesn't use a lot of juice , but if you want you can go to your home screen any of them hit menu (but not with the app drawer open) select settings go to accounts and sync turn off background info and just turn it on manually when needed such as the android market . You can also turn off the auto sync and just manually choose to sync , like in the clock (and gmail etc.) it will say no weather after you click it , just hit menu you will see a little sync button option to sync and voila you have weather . So when you visit the market it will automatically ask you to turn it on (background info as will all apps that need this) . And the screen on any android is a battery killer . So when not using your phone simply tapp your power button to turn your screen off and lock (and to keep from pocket dialing lol) . But if all you do is text , emails , and web surfing (surfing drains more but no where near as much as streaming) you can literally do that all day , the screen will actually suck the most power . If manually turning off your apps is too much . Just turn your phone off (not just the screen) and on . If a new app didn't turn off after you start your phone back up you know that will be a problem later . So when not using your phone turn off your screen it will last soooo much longer . I only make a call or two and a couple of texts maybe a few minutes of internet with opera mini . My battery lasts over 24 hrs , but I barely use my phone . Hope that helps .
Sent from my HTC Vision using XDA App
BTW if you have a bunch of apps running in the background video games etc ... and you charge your phone all night and in the morning it is not charged . You should probably turn your apps off . Or simply power your phone off which shuts off most apps . Then turn it back on . The phone should not take all night to charge , it should only take an hour or 2 . 3 hours max .
Sent from my HTC Vision using XDA App
i suggest watchdog lite,it monitors cpu usage and alerts you when 1 uses more than your max threshold.if this helps,please click thanks.
When you changed ROMs, did you do it with a full charge? If not, your battery stats file is probably messed up.. Ive used Battery Calibrator free from the market in the past to fix that problem.. I believe a brand new battery on the Shift shows about 4200mV when fully charged or just slightly below that.. Run the app, when it gets close, calibrate (which essentially just deletes the battery stats file and creates a new one)
I'm really frustrated because i really used to love the n7 so much I was an early adopter and bought another one after I dropped my first and then went on to buy my girlfriend one. But after being plagued with this issue and stuck on 4.1 its just not the same anymore since I cant flash custom roms all day :/
I've been having a charging issue with android 4.2.1 since it came out (both stock and all the roms I tried) but I noticed that whenever I reverted to 4.1.2 the issue went away completely. So I've been waiting for 4.2.2 to come out for a while now to see if it fixed the issue and after flashing the update tonight it seems to have the same problem.
I've tried searching for months now and haven't found any answers.
So this is the issue with both 4.2.1 and 4.2.2:
The battery charges at an insanely slow pace to the point that it ruins the tablet completely. I'll plug it in over night for 8+ hours and it will not gain more then 40% battery life in that time.
Its to the point that when I was just using it right now on the charger with brightness turned all the way down and nothing on other then sync and WiFi that light web browsing for 10 mins caused it to discharge a percent after being plugged in for 19 minutes.
Notes:
Its a c70 16gb
I tried 3 different stock N7 chargers with stock cables as well as trying them with other cables.
I'm not plugged into any kind of extension cords and I've tried multiple wall sockets at different locations.
My girlfriends nexus 7 32g charges fine on 4.2.1 and I have not updated her to 4.2.2 to test yet.
I haven't checked the battery connection because like I said whenever I revert to stock 4.1.2 or any 4.1.2 rom it charges in 4 hours flat or 6 hours with heavy usage while charging.
So anyone have any ideas? If not I guess I have to rma.
Do both, yours and your girlfriend's devices take that long to charge?
sl4y3r88 said:
Do both, yours and your girlfriend's devices take that long to charge?
Click to expand...
Click to collapse
Nope her nexus 7 charges fine. ( a little slower on 4.2 then 4.1 but nothing like mine)
Her nexus does have issues with turning on sometimes on 4.2.1 like a lot of other users but its nothing holding the power button for 10 seconds doesn't fix.
It also just noticed it seems to discharge at an extremely fast pace. (still on 4.2.2)
It just dropped from 55% to 51% in the time I've typed these responses with brightness all the way down.
So anyone want to try and help me figure this out before I send it in friday? I called it in to Google play device support to try and report the software bug and they said its the first they heard of it and they would pass it on but I felt like the rep didnt want to help as I bought it from a third party. I'm willing to do any tests suggested and hop between software versions to try and figure out this bug.
Why do you think it is a "software bug" when millions of people running the "same software" don't experience the same behavior?
I realize that software can exhibit data-dependent behaviors, and thus exhibit low occurrence rates... but there is no "software" involved in charging the battery.
Do you think a booted Linux kernel is needed to charge a battery? How would the battery get charged when the device is turned off in that case? C'mon!
Send it back and tell them the battery (or charge contoller CIRCUIT) is defective.
If it's out of warranty, PAY them to replace it.
bftb0 said:
Why do you think it is a "software bug" when millions of people running the "same software" don't experience the same behavior?
I realize that software can exhibit data-dependent behaviors, and thus exhibit low occurrence rates... but there is no "software" involved in charging the battery.
Do you think a booted Linux kernel is needed to charge a battery? How would the battery get charged when the device is turned off in that case? C'mon!
Send it back and tell them the battery (or charge contoller CIRCUIT) is defective.
If it's out of warranty, PAY them to replace it.
Click to expand...
Click to collapse
Then how do you explain that if right now I flash back to 4.1.2 it will work fine? If you want I'll provide screenshots.
I just flashed back to 4.1.2 this morning and it worked perfectly. Just now I flashed codefires 4.2.2 build and the problems back.
Please explain how that is hardware related.
I may of jumped the gun assuming it was a charging issue. It seems like it might be a battery drain issue. Here's a couple screenshots from a fresh install of codefirex 4.2.2 build.
Sent from my Nexus 7 using XDA Premium HD app
All I was trying to say is that when the OS is booted, at most all it does is monitor battery voltage and current - it doesn't get actively involved in control of charging circuitry.
At most this historical data can be used to *predict* when the battery will run out of juice, and this number is what is shown to the user as a % charge number. Hopefully that allows the prediction to be sort of correct as the battery ages and it's characteristics change.
This "calibration data" is only used for prediction - it does absolutely nothing to alter the rate at which current is drawn from the battery by the motherboard, nor for attempting to alter the behavior of a battery charge controller.
Li-Ion and Li-Polymer batteries are indeed complicated enough that they should not be charged by extremely simple circuits if a long operating lifetime is desired. For this purpose though, monolithic battery charge controllers chips are used - they do not need any assistance of a micro-controller or advanced CPU running a modern OS. That's why they are able to charge batteries rapidly and appropriately when the motherboard is in a "powered down" state.
Relative to a big multi-core CPU chip, which might have hundreds of millions of transistors, battery charge controllers are extremely small circuits - they are sold by the billions and cost in the ballpark of one to several pennies. They don't need the support of a CPU or even a microcontroller to operate correctly.
Good luck with your tab; I hope you enjoy it.
bftb0 said:
All I was trying to say is that when the OS is booted, at most all it does is monitor battery voltage and current - it doesn't get actively involved in control of charging circuitry.
At most this historical data can be used to *predict* when the battery will run out of juice, and this number is what is shown to the user as a % charge number. Hopefully that allows the prediction to be sort of correct as the battery ages and it's characteristics change.
This "calibration data" is only used for prediction - it does absolutely nothing to alter the rate at which current is drawn from the battery by the motherboard, nor for attempting to alter the behavior of a battery charge controller.
Li-Ion and Li-Polymer batteries are indeed complicated enough that they should not be charged by extremely simple circuits if a long operating lifetime is desired. For this purpose though, monolithic battery charge controllers chips are used - they do not need any assistance of a micro-controller or advanced CPU running a modern OS. That's why they are able to charge batteries rapidly and appropriately when the motherboard is in a "powered down" state.
Relative to a big multi-core CPU chip, which might have hundreds of millions of transistors, battery charge controllers are extremely small circuits - they are sold by the billions and cost in the ballpark of one to several pennies. They don't need the support of a CPU or even a microcontroller to operate correctly.
Good luck with your tab; I hope you enjoy it.
Click to expand...
Click to collapse
Thank you for taking the time to write out this detailed explanation. I read it over a couple times and that all makes a lot of sense and now I have a little better understanding of how things work charging wise.
But I still can't wrap my head around how the problem DISAPPEARS COMPLETELY on any 4.1 based build...
I'm not trying to contradict you in anyway it seems like you are way more knowledgeable then me on the subject.
It just doesn't make any sense and I was hoping you could make more of it for me.
Maybe it isn't the charging but a battery drain issue something on 4.2 based builds is draining more current then the charger can dish out.
But while i was doing research I read that chargers up the current they dish out if the device is in use. Is that correct?
I've looked into the media server bug but as I just did a fresh install of stock 4.2.1 and haven't changed or added anything to the file structure that wasn't included in the factory image, I also went through and turned off the keyboard press sound and all other sounds like explained in some of the threads I have read. I also read that the problem is supposed to be fixed in 4.2.2. I also haven't installed any apps from the market.
I guess all I'm looking for is the answer to this question:
Could there really be a hardware related problem of any sort (not just charging and battery problems but anything) that causes problems with 4.2 based builds specifically but doesn't cause problems with 4.1?
If the answer is yes then I don't have to feel bad about sending it in but if its software based issues I'll be upset that I wasn't able to fix it and gave up.
Have you let the battery drain all the way or do you just plug it in at a certain point? if not let it get to the point were it will turn itself off. if the battery with the cross in it stays for more than it would take for 1% to drain then it just might be your battery stats file. even if its not let it drain and then charge it while its off. you can check the battery by pushing the power button quick. i know i have had this problem with other devices that were fixed by doing this. and my N7 did it last night were i updated and plugged it in, it was at 60% and when i woke up it was at 46%.
projectzro said:
Have you let the battery drain all the way or do you just plug it in at a certain point? if not let it get to the point were it will turn itself off. if the battery with the cross in it stays for more than it would take for 1% to drain then it just might be your battery stats file. even if its not let it drain and then charge it while its off. you can check the battery by pushing the power button quick. i know i have had this problem with other devices that were fixed by doing this. and my N7 did it last night were i updated and plugged it in, it was at 60% and when i woke up it was at 46%.
Click to expand...
Click to collapse
I'll give this a try right now then post results, the battery is already pretty low so It shouldn't take very long. Thanks for the response.
projectzro said:
Have you let the battery drain all the way or do you just plug it in at a certain point? if not let it get to the point were it will turn itself off. if the battery with the cross in it stays for more than it would take for 1% to drain then it just might be your battery stats file. even if its not let it drain and then charge it while its off. you can check the battery by pushing the power button quick. i know i have had this problem with other devices that were fixed by doing this. and my N7 did it last night were i updated and plugged it in, it was at 60% and when i woke up it was at 46%.
Click to expand...
Click to collapse
So I let it run dry and am getting some weird behavior...
The dead battery symbol did not pop at all. It actually booted played the low battery sound half way through the nexus logo loaded into the OS and immediately was greeted by the battery to low logo powering down message and then it returned off. It did this cycle all the way through three times in a row before holding the power button did nothing. I let it sit for a minute before trying again and I got another boot out of it all the way to the OS again. But I've yet to be greeted by the battery with the cross symbol. Holding the power button will do the cycle described above or do nothing at all.
krisserapin said:
But while i was doing research I read that chargers up the current they dish out if the device is in use. Is that correct?
Click to expand...
Click to collapse
Well, the 120v->5v converter certainly can be providing more current @5v because the device is active, but that's only because the motherboard is drawing current in parallel with the battery charging circuit. It doesn't mean the battery charge rate is higher.
krisserapin said:
Could there really be a hardware related problem of any sort (not just charging and battery problems but anything) that causes problems with 4.2 based builds specifically but doesn't cause problems with 4.1?
Click to expand...
Click to collapse
I suppose so.
I would do a few things to determine whether that is a reasonable hypotheses, though.
1) See how fast the battery charges with the tablet turned off. Should be close to 40%/hour for a new battery. You know there is no "software" running with the tablet turned off, so if you don't see some reasonable number here (say > 20%/hr) then a bad battery or charge controller circuit in the tab are the most likely culprits. Also, if the temperature rise of the tablet while doing this seems higher than the gf's unit, that would implicate the battery, not the charging circuit.
2) There's software, and then there's software. (Preinstalled vs. User installed) Run the battery down a ways, and then observe the battery charging rate with the device on but screen off (sleeping), but on a stock 4.2 install with ZERO user apps installed. Then, install/restore all your favorite apps, reboot, maybe use a couple of your fave apps, and repeat the same charge rate trial (screen off/sleeping). Are there large differences between the two cases? If so, that would implicate one of your apps in causing either lots of additional compute operations or preventing entry into the LP0 state (perhaps because of wakelocks?)
The thing is, the N7 battery is rated at 4325 mAh; that is sort of the same thing as 4.325 amps of current for 1 hour. (Voltage range of roughly 4v to 3.5v).
So, if a "good battery" can be charged in 2.5hrs, that is sort of like stuffing 1.73 amps into the battery for that time (1.73 x 2.5 = 4.325 A-h or 4325 mA-h). That's pretty near to the max capacity of the AC charger (2A)
Now, some users have reported discharging their tabs in 4 hours under heavy continuous use; that would be about 1.08 amps for 4 hours.
Since the wall charger is rated to produce 2A, this suggests that very heavy usage simultaneous with charging would indeed cause battery charging to slow down significantly - let's suppose it drops from 1.73a to 0.65a. Now it takes the battery 6.6hrs to charge ... but that is still just over 15%/hr ... with the tab in active use.
But that's not what you were noticing - you were seeing much worse charge rates than this when the tablet was supposed to be more or less idle!
Finally I should point out that I previously mentioned that the % charge number is a prediction, not a measurement! If for some reason this number were screwed up, then the "charge rate" observations could be completely screwed up. (Think of this as being analogous to trying to partially fill a gas tank in a car or estimate fuel mileage with a broken gas gauge) The only way to be sure that you are not falling victim to something like this is to record battery voltages - the 100% level should be up around 4v, and the 10% values down around 3.5v.
You can observe this value at /sys/devices/platform/tegra-i2c.4/i2c-4/4-0055/power_supply/battery/voltage_now
(note value is reported in uV)
Whew - long post. It doesn't directly answer your question about "why was 4.1 so different?" - but gives you an idea about why I was skeptical when you saw charging rates as low as you did.
I dunno, maybe the % charge prediction value numbers are screwy on your tab for some strange reason in 4.2, perhaps because of a minor hardware difference. I can't rule it out - I once saw a bug expression in a hardware/software combination that required three independent conditions (from three separate vendors!) to have precise configurations before the bug would show itself.
I hope this post gives you some ideas to try; it certainly doesn't give a solution.
Good luck - if you feel like spending more time investigating, go for it; just don't let the clock run out on the warranty period if you have one left.
bftb0 said:
Well, the 120v->5v converter certainly can be providing more current @5v because the device is active, but that's only because the motherboard is drawing current in parallel with the battery charging circuit. It doesn't mean the battery charge rate is higher.
I suppose so.
I would do a few things to determine whether that is a reasonable hypotheses, though.
1) See how fast the battery charges with the tablet turned off. Should be close to 40%/hour for a new battery. You know there is no "software" running with the tablet turned off, so if you don't see some reasonable number here (say > 20%/hr) then a bad battery or charge controller circuit in the tab are the most likely culprits. Also, if the temperature rise of the tablet while doing this seems higher than the gf's unit, that would implicate the battery, not the charging circuit.
2) There's software, and then there's software. (Preinstalled vs. User installed) Run the battery down a ways, and then observe the battery charging rate with the device on but screen off (sleeping), but on a stock 4.2 install with ZERO user apps installed. Then, install/restore all your favorite apps, reboot, maybe use a couple of your fave apps, and repeat the same charge rate trial (screen off/sleeping). Are there large differences between the two cases? If so, that would implicate one of your apps in causing either lots of additional compute operations or preventing entry into the LP0 state (perhaps because of wakelocks?)
The thing is, the N7 battery is rated at 4325 mAh; that is sort of the same thing as 4.325 amps of current for 1 hour. (Voltage range of roughly 4v to 3.5v).
So, if a "good battery" can be charged in 2.5hrs, that is sort of like stuffing 1.73 amps into the battery for that time (1.73 x 2.5 = 4.325 A-h or 4325 mA-h). That's pretty near to the max capacity of the AC charger (2A)
Now, some users have reported discharging their tabs in 4 hours under heavy continuous use; that would be about 1.08 amps for 4 hours.
Since the wall charger is rated to produce 2A, this suggests that very heavy usage simultaneous with charging would indeed cause battery charging to slow down significantly - let's suppose it drops from 1.73a to 0.65a. Now it takes the battery 6.6hrs to charge ... but that is still just over 15%/hr ... with the tab in active use.
But that's not what you were noticing - you were seeing much worse charge rates than this when the tablet was supposed to be more or less idle!
Finally I should point out that I previously mentioned that the % charge number is a prediction, not a measurement! If for some reason this number were screwed up, then the "charge rate" observations could be completely screwed up. (Think of this as being analogous to trying to partially fill a gas tank in a car or estimate fuel mileage with a broken gas gauge) The only way to be sure that you are not falling victim to something like this is to record battery voltages - the 100% level should be up around 4v, and the 10% values down around 3.5v.
You can observe this value at /sys/devices/platform/tegra-i2c.4/i2c-4/4-0055/power_supply/battery/voltage_now
(note value is reported in uV)
Whew - long post. It doesn't directly answer your question about "why was 4.1 so different?" - but gives you an idea about why I was skeptical when you saw charging rates as low as you did.
I dunno, maybe the % charge prediction value numbers are screwy on your tab for some strange reason in 4.2, perhaps because of a minor hardware difference. I can't rule it out - I once saw a bug expression in a hardware/software combination that required three independent conditions (from three separate vendors!) to have precise configurations before the bug would show itself.
I hope this post gives you some ideas to try; it certainly doesn't give a solution.
Good luck - if you feel like spending more time investigating, go for it; just don't let the clock run out on the warranty period if you have one left.
Click to expand...
Click to collapse
Wow thank you so much for the help. I'll play around with this tonight and see what happens. If I can't figure it out by the morning I think I'll be able to RMA it without feeling like I just rolled over and let my n7 get the best of me.
So after charging it on stock 4.2.1 with the power completely off it only charged 3% in a little over a hour and voltages read 3.6. I'm gonna leave it on the charger over night turned on starting from 3% with only two extra battery monitoring apps installed and report back in the morning with screenshots of the results. After that ill probably revert to 4.1.2 drain the battery fully, charge it off for an hour report the values then let it charge fully with the battery apps on for reference take a few more screenshots then lock the bootloader install the ota and ship it off to good old ASUS since it sounds like its hardware from whats been explained.
FWIW, I drained my N7 last night (LOL, typing novels into XDA threads) - when I finished I was at 6% charge - that was 3.66v. In the morning @ 100%, the battery voltage was 4.1-something.
Sounds to me like you've definitely got a hardware problem.
Good luck with the RMA.
Canyou help me?
Since I flashed 4.2.2 my 240V-USB charger only cahrges thes battery about 5% in one hour.
Before (with 4.2.1) It was definitely faster. It charged more tha 5% per hour (maybe 20-25%).
I double checked the plug in the socket. checked the correct fit of the USB cable on the docking station.
Everything fits tight. No wiggle.
It must be software related, since it started after flashing the OTA zip from 4.2.1 to 4.2.2
Polarfuchs said:
Canyou help me?
Since I flashed 4.2.2 my 240V-USB charger only cahrges thes battery about 5% in one hour.
Before (with 4.2.1) It was definitely faster. It charged more tha 5% per hour (maybe 20-25%).
I double checked the plug in the socket. checked the correct fit of the USB cable on the docking station.
Everything fits tight. No wiggle.
It must be software related, since it started after flashing the OTA zip from 4.2.1 to 4.2.2
Click to expand...
Click to collapse
From a partially charged state, say below 50%, turn the device off, (NOT sleeping, but powered OFF) and put it on the charger for one hour.
It should charge at around 30-40%/hr.
As I pointed out above, how is it possible that software would be affecting the charging with the device turned OFF?
I believe you are seeing exactly what you report; my best guess is that a hardware problem occurred just about coincidentally with your upgrade. Just coincidence - not causation.
You also should inspect the battery voltage (see above for path in /sys) in case something crazy is happening with the %charge *prediction* (it is not a measurement) - because the total charging range is from about 3.65v-4.15v, a normal charge rate should be roughly 150 to 200 mV/hr
good luck