Related
...definitive solution to the overheating (and subsequent crap battery life) issue with the Tytn/Hermes/8525?
This seems to be one of the most prevalent hardware-related problems I've encountered after perusal of numerous boards.
Charging, it heats up. Duh. Fine. Disconnect, put it in my breast pocket after it cools down, twiddle my thumbs. During this whole time, for purposes of this test, EVERYTHING is switched off: phone radio, wifi, bt, push, and as many of the background processes as I can kill without having the phone hang on me.
You'd think the symptoms would be the same every time. But nooooo...this thing has a mind of its own. Sometimes it'll be 5 mins before I start feeling the heat, sometimes 40. It's totally unpredictable. I've tried every way I can find to extend the battery life with no luck; this is getting retarded.
So: Battery life drops drastically once the thing starts heating up. But not before. From 3PM to 4PM today, battery life was at 100% and did not move. Sweeeet! I thought...too soon. Got that warm and fuzzy feeling - then it's in free fall. 10% down in 45mins, another 20% by 5:30, dead as a doornail by 8PM. That's exactly FIVE hours of "standby" with ZERO activity. Screen was turned on maybe 4 times just to check battery status. 200 hours of standby?? Sure, in a deep freezer packed with dry ice...
Installed Batti: if anyone with close to normal (advertised?) battery life has also installed it, could you tell me what your temperatures are like? When I'm charging, I'm at 35.6C. My voltage is at 4.213V - this might be the problem since the battery is listed as a 3.7V 1500mAH. Also, I removed the charger for about 30 seconds after Batti said it was charged, then reinserted it. It took about 30 minutes to tell me again that it was full - all the while listing the "Percent" as 100%. Gah!
Anyway - back to the reason I've posted:
1) Is this a phone issue, tweak/registry/software issue, or a good old fashioned battery issue? I've got another battery coming in shortly but it's nothing special, not sure of the brand, just want to compare it to this one - which is a Seidio.
2) If anyone else has had this problem and solved it, please let me know what you did.
3) This phone is for sale if anyone wants it and knows how to fix it. Other than the 5 hours of battery life, the phone is perfect.
Thanks all!
The only time I've ever had this problem was when I installed the very first Palringo mobile beta, and it continuously polled the Palringo servers whenever it was connected... I had a battery life of about an hour and a half!
I can only suggest you have some poorly-written app on your device which is polling some piece of hardware or using (or trying to use!) the data connection, subsequently failing and looping round to try again and again.
I'm not using Batti (using the BatteryStatus Today Screen plugin), but it shows temps - I'm charging my device at the moment and it shows ~41 degrees celcius. When I unplug the charger, I have about 70mW usage and when I tap to turn the backlight back on it roughly doubles (backlight on its lowest setting). Using roughly 40-45mA just idling, I have push mail turned on and ActiveSync is syncing probably every 5/10 minutes or so (can't remember the interval).
I get about a day's worth of usage including regular phone usage, data usage, then locking the device (including turning the backlight off) when it's just on the desk or in my pocket (less if I have BT turned on all the time, obviously). All I can think of is that you have some app on there which is either interacting with something else or causing the problem itself.
@slidizzy:
what is the manufacturer name on the battery?
There are threads around about certain manufacturer brands (there are a couple of different brands) and their performance..
i had a dynatec and it was crappy.. took it back and got a sanyo battery and all was good...
Possible solution - Same geographic location
Hi. I seemed to have the same problem recently. I think my radio was the new 1.54.00.10. I have two batteries and each one was killed in 6 to 8 hours.
I first downgraded the radio to 1.51.00.10 and it seemed a little bit better, but upon upgrading to 1.54.70.00, it seemed to have gone away. My OS is Pandora's 7.1 w/ 3.62.
With 1.51.00.10, I was able to get over a day's worth of life on one charge in 3G/H mode. It seems this 1.54.70.00 is giving me more life, but I'm still testing.
Maybe give this a try, upgrading to 1.54.70.00 and a 3.62 os. No problems for me so far and it seems like it's a keeper!
Hope this helps!
Quakie
Soft reset when it starts getting warm, soft reset after charging if it is warm when on the charger.
My 8525 used to have this problem, but it went away on its own. However, soft resets when the device felt warm did solve the problem when it was occurring. Note that my phone is no longer warm while charging, either.
A lot of people try various radio upgrades/downgrades and ROM changes to fix this, but I think that's on the wrong track as I've never seen anyone report that doing these things made any difference. However, if you're not using WM6, I recommend at least making that change.
Other than that, hit the reset button if it starts to feel warm for no reason and after charging, and you should be fine.
My guess on this is that there is some kind of problem where the device thinks it is plugged in when it isn't, and then it over stresses the battery causing the heat and fast battery drain.
My experience
I am on Rogers in Canada, the same company that owns Fido, and I wonder if there is a problem with their network/ActiveSync/3G/units compatibility.
carrier: Rogers wireless (Canada)
device: branded HTC TyTN WM 5
ROM: 1.34.631.14
Radio: 1.42.00.00
Recently activated Push Email and connecting to exchange server via Activesync. Push requires an "always-on" data connection. It seemed to have been working fine for about 2 days, then suddenly my unit started to heat up significantly, (luckily no screen warp), and my battery would drain from 100% to 0% in 5 hours (if I was lucky). Unsatisifed with Rogers suggestion that replacing the unit with a refurbished unit was the way to go... I continued my research and experimentation and 48 hours later here is whatI came upwith so far:
1) Hard Reset - did not help the situation
2) Soft Reset when heating up - did not help the situation
3) Most frequently associated activity - ActiveSync on with 3G Data Connecton enabled and server directed to exchange server... no difference depending on how often I had the mobile device ping the exchange server. The heat and battery drain occurred while the TyTN was in hibernation (dead unit in the AM when I awoke).
4) Battery drain modifiers - worsens with worsening heat, worsens and acclerates if you remain in an area of low signal (less than 2 bars showing)
Best solution(s)/explanation(s) to date:
1) 3G is a battery killer - it uses a lower intenisty signal, and it generally draws heavier on the battery and hardware when using the network
2) In Phone settings, switching your Band to GSM (2G) fixes the device into one band (does not allow automatic switching and constant detection of best signal). Unless you are a real Power User and rely heavily on every ounce of speed that can be squeezed out of 3G there is no noticeable difference.
3) I have switched off the "receive allincoming beams" for the Ir interface to conserve every mV of power in my battery.
4) Since the switch (a few hours now) I have had no heat issues and the voltage has remained stable with ActiveSync on and mild websurfing to download a couple of CABs... granted it is minimal usage as it is 2:30AM but I think this may be the trick (on Rogers with a TyTN anyways)
I'll keep an eye on this and do some more analysis on the battery... Any input readily welcomed...
M
sounds like you simply need to buy a new battery.
It's not a tumoh!
Doesn't seem to be battery...
I recently tweaked reg with some battery hacks, locked it into 2G and all has been well. Holding a charge with the data connection engaged 24/7 - drops to about 65% charge over 24h, having to charge only every 2nd/3rd day...
M
Hi,
I noticed the following problem on my Diamond 2:
If I turn off the phone for night charge it never shows green in the morning.
The only way to see that amazing green light is to charge the phone whent it is turned on.
Of course I applied the latest hotfix - no use for the off mode charging. And of course I wrote to htc - will not waste your time repeating their suggestions.
And I am not happy with my phone battery life - it hardly endures one working day - lets say - 10 hours...
ROM - Official, yet.
orlean said:
Hi,
I noticed the following problem on my Diamond 2:
If I turn off the phone for night charge it never shows green in the morning.
The only way to see that amazing green light is to charge the phone whent it is turned on.
Of course I applied the latest hotfix - no use for the off mode charging. And of course I wrote to htc - will not waste your time repeating their suggestions.
And I am not happy with my phone battery life - it hardly endures one working day - lets say - 10 hours...
ROM - Official, yet.
Click to expand...
Click to collapse
I never turn my phone off so the green light problem never arises. However I will check and see if occurs.
As for battery life, you will need to give it a few weeks of use before you see maximum battery life.
Make sure you don't continually discharge the battery (better still keep it charging whenever you can) and you should see improvement over time.
Unlocking and replaceing the ROM can also have a significant effect on battery performance as does the Radio version in use. That's going to need some work on your part but the improvements are there to be had.
Some apps that are in common use are also power hungry and can cause a significant drain on power.
And if you install your apps to mem card then again that uses more power than installs to phone storage memory.
You can also turn off any unused background apps and processes.
Only turn on Bluetooth and WiFi when needed.
All these things help.
Personally I carry a spare standard battery with me at all times and strangely since I bought it I haven't needed to us it. The placebo battery effect?
Thanks for the answer.
About the battery usage conseption:
You suggest that I plug my phone each time when possible?
I thought that as the battery has XX recharges according to the specifications it is not good to charge each time whenever you got AC or USB access
I started to follow your recommendation anyway.
For example however - my laptop is never (when possible) with battery in it. I use the battery only when necessary, becasue in the user manual is written that has 300 cycles of recharging. And I always wait until completely discharged before charging. That is how I began treating the Dimond, too.
orlean said:
Thanks for the answer.
About the battery usage conseption:
You suggest that I plug my phone each time when possible?
I thought that as the battery has XX recharges according to the specifications it is not good to charge each time whenever you got AC or USB access
I started to follow your recommendation anyway.
For example however - my laptop is never (when possible) with battery in it. I use the battery only when necessary, becasue in the user manual is written that has 300 cycles of recharging. And I always wait until completely discharged before charging. That is how I began treating the Dimond, too.
Click to expand...
Click to collapse
With Lithium Ion batteries the "quoted" numbers of "rechage" is is an approximate equivalent to give some idea of life expectacy.
It's a hangover from the old NiCad battery days and is not really very helpful when applied to Lithium Ion usage.
The most important aspect of LIon is it's ability to hold it's voltge at max current for longer than other technology. It does this best when well charged and maintained at near max as possible as often as possible. The downside is it's life expectancy which does deteriorate over time.
If you require max daily useage then max charging whenever possible will give you this and you will have to accept that the battery will at some point loose it's charge retaining capabilities and will have to be replaced.
For most of us that's the most important thing.
This is not a battery issue, I believe that this is a software one.
I noticed this morning, having left my phone on charge, and 'off', all night, that the indicator light was still red. When I switched on the phone, it showed only 80% charged.
Having seen this before, I carried out a soft reset, the battery indicator then showed fully charged.
So the battery is charging fully, but the battery charge indicator is showing less than that.
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
(it happens on every rom, stock or not, currently on latest 7.1.2 RR)
sometimes when I let my phone charge it's battery to 100% my rom just completely ****s itself up, and basically resets it. I'm unable to log into my google accounts. this has been happening two times now with my new battery and a lot of times with my old battery.
this basically ****s everything up, making me have to completely wipe and reinstall reinstall everything onto my phone
does anyone have the same problem? are there fixes? battery charge limiter apps usually do it but they're not reliable.
If you use the turbocharger, try switching to a regular one that charges the phone much slower. I didn't have this problem or anything but this should at least be worth trying.
I have never encountered this kind of problem with either the stock charger from the box or with a quick charger 3.0. Either way you probably shouldn't let it charge overnight because you're slowily killing the battery.
You may try Magisk module called Magic Charging Switch. By default it lets the battery charge up to 90% and will resume charging when it's below 80%. I'm using it with great success for quite some time now and I can highly recommend it. Also, the battery will be able to make much more cycles.
[TL;DR]
Phone battery suddenly drains faster than usual, drains to 0% overnight. Problem still persist even after April update and after battery change. Can't find any solutions. Help me.
Hey, so about a week ago something very strange happened to my Mi A1 and got worse overtime. So what happened was my battery went from 80+% to 0% overnight. I woke up confused and just recharged it and didn't think too much. After a full charge, I noticed the battery drains abit more than usual and had to plug it in constantly. Before going to bed I charged my phone to 100% to see if it would drain to 0% again. It did. As time passes the problem gets worst. The phone started getting warm when charging (around 40+°C up to 50°C) then after a while the phone runs warm even when not charging (never goes below 40°C). My phone always used to run at about 30-35°C even when charging. I changed the battery myself because there was no warranty on it but it didn't fix the problem. However it did help abit. The battery drains ever so slightly slower now but still drains to 0% overnight. It still runs warm but now it does go below 40°C (rarely). Before and after the battery change, the discharging rate is about 700mA and sometimes reaches 1000+mA (used an app called Ampere, not too sure how accurate it is). The phone was also warmer than usual when charging even when the phone was off (before and after the battery change). I tried factory resetting to see if that does anything but had no luck. I also tried using a Wakelock detector app to see if there was an app excessively triggering a wakelock but all seemed normal. I even tried downloading a "battery calibration app" which obviously didn't work. So I feel like it's a hardware problem.
Now here's what I did and did not do to the phone before the problem happened. What I did was I do charge the phone quite alot most of the time. What I mean by that is when it hits about 30% I'll plug it in but I never leave it plugged in after a full charge or charge it overnight and I seldom let the battery drain to below 10%. Even so, the phone never got warm like how it is now. That's about all I did to it. Now what I didn't do was, I never tried to install custom ROMs or root/modify my phone in anyway except for the post about how to enable 4G+ which didn't work for me.. My phone is completely stock. I also didn't install any new apps from the playstore or from any 3rd party sites nor were there any updates for any apps installed in my phone. I've had the same apps installed for a couple of months before this happened. I also haven't dropped my phone for a couple of months. I only dropped it less than 5 times from short heights and I have a very rugged case on. I also didn't use any 3rd party chargers. I'm still using the charging brick and cable that came with the phone. I have tried using other chargers that are 2A but no luck. So basically I didn't do anything out of the ordinary prior to this problem.
Just some extra information
1. The hottest part of the phone is at the top right corner of the back. I assume the CPU is there (?).
2. It happened before the April update. It was the same before and after the April update.
3. Phone is running on Android Pie if that wasn't clear
4. The phone is only 10 months old
5. My phone is the Global ROM version
6. Performance wise, its still responsive and snappy. Doesn't lag or freeze or anything.
6. I always have mobile data on and use it as hotspot for my laptop at uni. I have been using it like that for the past 9 months. However the problem happened when I was at home during sem break so I was mostly connected to Wi-Fi.
Sorry for such a long post. I hope somewhere out there, there is someone who can help me or other people that have a similar problem so we can fix it.
Thanks.
In the upper right corner, should be the modem area.
Try holding the phone on airplane mode during the night and monitor drain.
Also, try changing the SIM slot and do an APN reset. If this fails too, try changing your SIM card or if u can, try another operator SIM.
If you changed any value with QXDM PRO , try and put back the default values.
Good luck