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.
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.
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
Hi,
I have problem with in Jiayu S3 2GB. Under 50% battery drop to 0% in few minutes. Also battery doesnt last long , max 3 hours screen time and it is problem to use it whole day withnout charging, but normally screentime should be around 6 hours what i read.
I recived phone with Android 5.1 2015-06-23 tryed flashing newer version 2015-07-14, also tryed battery calibration, fully charging, discharging few times and still same.
When is fully charged voltage is 4,2V (measuded with app battery calibration) at 50% is only around 3,6V (this is almost 0 capacity for lion battery) and is turning off at 3,4V.
Have anybody simmilar problem? It looks battery is bad not just software problem, but dont understand that it is showing 50% for that low voltage.
Thank you
kecimalah said:
Hi,
I have problem with in Jiayu S3 2GB. Under 50% battery drop to 0% in few minutes. Also battery doesnt last long , max 3 hours screen time and it is problem to use it whole day withnout charging, but normally screentime should be around 6 hours what i read.
I recived phone with Android 5.1 2015-06-23 tryed flashing newer version 2015-07-14, also tryed battery calibration, fully charging, discharging few times and still same.
When is fully charged voltage is 4,2V (measuded with app battery calibration) at 50% is only around 3,6V (this is almost 0 capacity for lion battery) and at is turning off at 3,4V.
Have anybody simmilar problem? It looks battery is bad not just software problem, but dont understand that it is showing 50% for that low voltage.
Thank you
Click to expand...
Click to collapse
IF you are on lollipop then its software problem as 5.1 seem to have the battery bug, and never calibrate battery on MTK devices, Calibration apps mess up MTK phone,they are not made for mtk devices.
I recieved phone with defective battery, after changing it dont have any battery problem even with Lollipop.
I noticed that battery discharging very fast below 8% (Stock 4.4.4 13.08 and other KK versions)
Well, i had different problem
My phone didnt charge, no matter how much i change cables or chargers.
But when the device was shut down, charged well.
I bought mine from pandawill, so i sent them a mail,and they sent me another battery...
In the meantime, the problem had solved, maybe the battery calibration i did helped.
Anyway,i got now 2 batterys...
Silentshadowalker said:
My phone didnt charge, no matter how much i change cables or chargers.
But when the device was shut down, charged well.
I bought mine from pandawill, so i sent them a mail,and they sent me another battery...
In the meantime, the problem had solved, maybe the battery calibration i did helped.
Anyway,i got now 2 batterys...
Click to expand...
Click to collapse
Me also bought s3 basic from pandawill, the phone is not charging when on.. also when connected to pc thru usb, ipc shows device malfunctioning ,and there is no indication on phone...did new battery solve your problem ?
deleted
Silentshadowalker said:
My phone didnt charge, no matter how much i change cables or chargers.
But when the device was shut down, charged well.
I bought mine from pandawill, so i sent them a mail,and they sent me another battery...
In the meantime, the problem had solved, maybe the battery calibration i did helped.
Anyway,i got now 2 batterys...
Click to expand...
Click to collapse
my s3 basic is not charging when on.. also when connected to pc thru usb, ipc shows device malfunctioning ,and there is no indication on phone..I try to connect to sp flash tool also no success..same error"usb device not recognized pops up every 2s.everything else is fine..Any method to upgrade to 5.1 now on official kk USB OTG Works for me, also bought from pandawill
Any suggestions?
---------- Post added at 07:50 PM ---------- Previous post was at 07:46 PM ----------
konyvfalovb said:
I also have the problem and have the following conclusions:
1. Battery level will be displayed correctly after a reboot. Otherwise, the battery level indicator doesn't change as quickly as it should: it doesn't go up as fast while charging and doesn't go down enough when in use.
2. The point where the battery indicator starts going down by about 5%/minute varies and is in connection with the time it has been used. After two days without charging and without using the phone for more than one or two phone calls, it happened at around 5%, while lots of screentime made it happen when the indicator was above 50%. Some experimenting made it clear that it's not the battery's fault (in my case, at least) but rather a software problem.
Using stock KK 4.4.4.
Click to expand...
Click to collapse
Any rom you reccommend?
kecimalah said:
Hi,
I have problem with in Jiayu S3 2GB. Under 50% battery drop to 0% in few minutes. Also battery doesnt last long , max 3 hours screen time and it is problem to use it whole day withnout charging, but normally screentime should be around 6 hours what i read.
I recived phone with Android 5.1 2015-06-23 tryed flashing newer version 2015-07-14, also tryed battery calibration, fully charging, discharging few times and still same.
When is fully charged voltage is 4,2V (measuded with app battery calibration) at 50% is only around 3,6V (this is almost 0 capacity for lion battery) and is turning off at 3,4V.
Have anybody simmilar problem? It looks battery is bad not just software problem, but dont understand that it is showing 50% for that low voltage.
Thank you
Click to expand...
Click to collapse
Try to go battery settings and find out what application is eating your power.
Hi! I have this phone and few weeks ago I had a similar problem, when my phone had about 20%, it spend a lot of battery and in some minutes, it was without battery. I installed the Xtreme Rom and this was fixed. I hope you can fix your problem too with this.
Sorry for my bad english
Battery not charging when on - Solutions ?
Hi all,
My Jiayu will not charge when the fone is on, will only charge when switched off.
Any suggestions ?
Thanx Geoff
Known problem.
Saw it at my phone and in another phone.
How to solve: charge with original charger and cable and then switch to the other charger.
It worked for me twice.
Play it a little if its not working, switch cables,chargers, turn on and off...
Good luck.
Hello all,
facing an unexpected problem on my device Samsung Galaxy Grand Neo Plus Duos (double sim one) with battery and not sure if it's the battery fault, or android just decided to troll me and drive me nuts.
Running stock 4.4.4 android, but rooted (due to read/write restrictions for SD card and for the ease of Link2SD), had original battery inside for two years (phone is three years old, but for entire year it just sit at the desk, unused). Old battery recently swelled a little (found accidentally when I needed to replace SIM) so I opted for exchange for a new one. Same model, same number, original from Samsung (from local electro store, so 99%sure it's not fake).
Problem is, I put it in, charged it fully (it showed 50% charge when I put it in) and used the phone. At 30% the phone switched off and upon plugging it back in powered off, the indicator showed 0%. This happened three times in a row, so I returned the battery as a faulty piece and get another one (from the same store, everything is the same).
This time battery "died" at 19% charge (under load) and I charged it fully back, powered off. Next day I let it discharge with regular use, but noticed abrupt drop from roughly 30% down to 4% (no load, just standby with active wakelock - because without it the phone with SDcard refuses to get up from the deep sleep, another long story) where it discharged at normal speed down to zero. This time, when I tried to power the phone on, it did powered on for a few moments (this wasn't possible in previous attemtps), announced battery needs charge (with 0%) and shut off itself. Right now charging it fully in poweroff again, but have no idea what is going on ....
anyone knows, please? Seems the device is wrongly estimating and displaying the real charge left. Tried Battery Calibration apk from google store I found recommended online, but it didn't seem to have any effect .... is there something I can do with root access to "reset" the estimation and set it back on track? Or do I need to reflash the ROM from the scratch? (have it stored in my PC from before).
How are the chances two original batteries in a row are faulty pieces? I already disposed of the old battery, so don't have any comparisons as I never needed to study the charge and discharge processes into such detail ...
Also noticed with both the new batteries (thanks to the battery calibration apk) that the voltage drops down abruptly when I unplug the phone from charger. From 4,6mV to roughly 4,3mV instantly but without any changes in %charge display. Also seems the voltage is dropping down faster than the charge onscreen .... including the one in battery calibration apk.
Please help ....