Related
Hello Everyone,
I have been asked to put together an instruction on how to correctly calibrate
your Sammy Charge battery... so here it goes.
First of all you need to be ROOTED there are plenty of roms and kernels here
for you to pick from so get the package you want Odin or Clockwork whatever you want.
-i will be referring to Clockwork Recovery Mod as 'cwr' from now on-
I am currently running IMNUTS 710 Non-Overclock Kernel and Humble 1.4.2 ROM. Humble ROM comes with a battery calibration app that you might find helpful for this task.
The kernel or rom you have doesnt matter for calibration but you must have the latest cwr witch is bundled with any of IMNUTS' Kernels.
You may have heard of the term 'Bump Charging' this only needs to be done before you calibrate (so you Chargers that are doing this every full charge, you are wasting your time). I will explain what this is if you do not know.
Here are the steps:
1.Turn your phone ON and charge it to 100%
2Turn your phone OFF and leave it plugged in. (you will notice that the battery will begin to
charge again but it will not be at 100% anymore it will show something like 95%.
3.LEt your phone get back to 100% (it will vibrate when it is done)
4.Unplug your phone, wait 30 seconds, and plug it back in.
5.WTH! it is back to 95% again!dont panic... LEt it charge again to 100% (2-5 minutes)
6.Now do it again. (unplug wait 30 seconds, plug in, let charge to 100%)
continue this until it shows 100% after 10-20 seconds on plug in. (it took me 15 times,
although i have seen upwards of 20 times)
- some users are saying that the time does not decrease to 100% while doing step 6, 20 times is good enough as all phones/batteries are not from the same mold-
7.Now boot into cwr (if you dont know how then you shouldnt be here)
8.Go to the advanced menu and 'wipe battery stats'
9.Reboot phone via cwr
(((this is where it will differ from the other posts or whatever)))'
10.Drain your phone to 0% and immediately plug it in. (others will tell you to let it die completely and shut itself off... YOUR PHONE WILL NOT LOG CHARGING INFORMATION IF IT IS OFF!!! ((I suggest you do a little troubleshooting to see when your phone will actually turn off. Mine turns off after being at 0% for a few mins. Your's may shut off at anywhere between 10%-0%. If it does shut off just turn it on again and plug it in)). Basically what u am saying is make sure your phone is ON during charging while doing these steps.
11.Charge to 100% (DO NOT UNPLUG IT WHILE IT IS CHARGING... if you get a call or a txt it is fine to use it a bit (and for clearification on 'proper charging' I contacted Samsung it is OKAY to use phone while charging (my bad)).
12.I did this full charge and full drain, plug in at 0% -ON charging, 4 times.
13.Charge it whenever you want.
The android OS logs 'battery stats' and charging habits based on a small window of use. Following these directions will let your phone lock in enough information to max out your battery life.
With strong 4G signal expect 18-20 hours of light use. If you are in a known 4G deadzone download LTE Switch from the Market, it lets you turn off the 4G radio and run only 3G. I personally turn off mobile data unless i need it and have no syncing actions automated. My best uptime was 41 hours and 12 minutes to 0%. Dont forget that all roms and kernels are different so your results will vary. If you are on your phone all the time... playing games, on the net, making calls you will of course have less time.. with heavy use i can burn 10%-15% an hour easy. Get rid of your 'antivirus' crap, your monitoring apps all that shat... it will only sacrifice your battery and it is unnecessary.
For those wondering about LAGFIX:
AlexDeGruven states-
'RFS is the bastard child of FAT and a Samsung developer who didn't understand how modern filesystems work with NAND storage. It has nothing to do with battery usage. For data access, the longer it takes to access the data, the longer the processor is waiting and running wasted cycles. The faster the data is returned from storage, the less battery gets used.'
So turn it on or leave it off, up to you.
I hope this helps everyone get calibrated.
Let me know if you have any questions.
(916) 877-4460 or forum it up!
Reserved for updates
Nice. Hopefully this will stop clogging the forums a little bit.
Sent from my Droid Charge running Humble 1.42
Why is this in the dev forum?
suzook said:
Why is this in the dev forum?
Click to expand...
Click to collapse
...because everyone asks in the rom threads. Im just trying to be helpful so we don't see the same questions over and over again by those who refuse to actually look for info. This way they don't have to go too far.
Thanks criticalhit. If the mods have a problem with the location of this thread...I'm sure they'll move it. Thanks again for the tutorial.
tkm20 said:
Thanks criticalhit. If the mods have a problem with the location of this thread...I'm sure they'll move it. Thanks again for the tutorial.
Click to expand...
Click to collapse
I pmd the mod in charge of the charge dev forums already with reasoning why it should stay.. so we shall see.
I <3 Humble 142!
I went to 100% let it die. next day i used it normal and it was "ok". today my phone has been off the charge for 16 hours now and im still at 39%. Display took 80% of my battery so I'm sure i could easily idle for a few days. the whole time i had 4g and gps on. btw im at stock voltages and oc'd to 1.1ghz
gogreenbay07 said:
I went to 100% let it die. next day i used it normal and it was "ok". today my phone has been off the charge for 16 hours now and im still at 39%. Display took 80% of my battery so I'm sure i could easily idle for a few days. the whole time i had 4g and gps on. btw im at stock voltages and oc'd to 1.1ghz
Click to expand...
Click to collapse
Yeah display burns it up fast. And if you don't have strong 4g 4-5 bars it will constantly 'look' for a better signal where is cycles from 3g to 1x to 4g... eventually someone will write an app or make a system change to combat this.. (I hope). I wish I had the knowledge to do this and make our phones satisfied with low signal strength. :/
I <3 Humble 142!
Well written post... thank you
Sent from my Fascinate (soon to be Charge) via Tapatalk
JOrtenzi said:
Well written post... thank you
Sent from my Fascinate (soon to be Charge) via Tapatalk
Click to expand...
Click to collapse
Hey thanks mang! Im going to do a 3g only all day tomorrow to see what kind of life I get... will update on findings (I usually data off completely).
I <3 Humble 142!
This is exceptional. Great job. Appreciate it man.
Sent from my SCH-I510 using Tapatalk
I am finally getting some decent life
Thanks for writing this and for all the other posts you have spread about your methods, yes I read them.
Today was my best day by far. I was 11hrs and 20 minutes unplugged today when I got home and still had 25% of my battery left. I work in a 4G market, and for the first time today I left 4G off and only had mobile data on a few times. I had 1 hr 30 minutes of cell talking ( thats a lot for me) and had my display on 1hr and 48 minutes. This is on the same ROM and Kernal CritalHits is running (with lagfix enabled).
For those of you that think you can't carry this phone around without a charger, you are wrong (glad I finally beleive this). You just can't have your foot on the Hemi throttle all day and expect to get Prius mileage.
Ya I have at least 4 bars of 4g all over my town. I saw 3g once and it changed back to 4g right away
Sent from my SCH-I510 using XDA App
Awesome post. I've read a couple other posts on battery calibration. They've been somewhat similar (except for the last part, like you pointed out), but not as clear.
I do have a question though: Are battery stats erased along with data and other stuff when you flash a new rom, for example? I'm just wondering if this is something you should do every time you flash a new rom and require a data/cache reset. I'm assuming so, since you mentioned that each rom's battery level may vary.
Anyway, thanks again!
leenephi said:
Awesome post. I've read a couple other posts on battery calibration. They've been somewhat similar (except for the last part, like you pointed out), but not as clear.
I do have a question though: Are battery stats erased along with data and other stuff when you flash a new rom, for example? I'm just wondering if this is something you should do every time you flash a new rom and require a data/cache reset. I'm assuming so, since you mentioned that each rom's battery level may vary.
Anyway, thanks again!
Click to expand...
Click to collapse
yes, every time you wipe data, cache and delvik...recalibrate. Good method. This was the same method posted a year ago or so to help the Dinc get better battery life.
If the battery is properly calibrated shouldn't it make sense to only have to bump charge once?
Sent from my Droid Charge running Humble 1.42
This is the right place for this thread. The Charge forum moderator specifically said "*Only ROM Development, Hacks, Mods, Fixes, Reference, and Tutorials go in the Dev Section"
This is clearly a tutorial, and clearly belongs here.
http://forum.xda-developers.com/showthread.php?t=1074281
criticalhit said:
(((this is where it will differ from the other posts or whatever)))'
10.Drain your phone to 0% and immediately plug it in. (others will tell you to let it die completely and shut itself off... DO NOT LET IT DIE! YOUR PHONE WILL NOT LOG CHARGING INFORMATION IF IT IS OFF!!!
11.Charge to 100% (DO NOT USE OR UNPLUG IT WHILE IT IS CHARGING... if you get a call or a txt ignore it).
Click to expand...
Click to collapse
There's a problem with your process, and it is step 10. Some Charges will shutdown prior to hitting 0% battery level. I've seen my Charge auto-shutdown at 5%, 3%, 2% and 1%.
Also, I don't see the point of letting it drain to zero then charging it back up to 100% without any use. One more thing, you didn't specify whether you wanted the phone off or on during step 11's charge process, but I'll assume you want the device on considering the fact that you mentioned getting calls/texts.
OP, please explain comments about lagfix
What does "lagfix" do? Are you saying that it causes the battery to be used at a faster rate?
I thought lagfix involved making at least some of your on-phone partitions into ext4 rather than Samsung's format.
Thanks for the clear instructions, it includes a detail that makes a lot of sense, except wouldn't the phone shut itself down gracefully when the battery was gone, saving the battery stats?
I have searched the interwebs high and low for this one, but I haven't found another with this issue.
Phone: One XL, ATT - 4.0.3 - CleanRom 4.1 - 1.85
Was browsing using chrome this morning with my battery at 48%. Right before my eyes it flashed the "0% battery - plug in" alert for a split second before it powered off and literally had no battery.
Furthermore, this seems to have been happening 1-2 times a week for a couple months. I keep waking up in the morning to a phone w/ 0% power, despite going to bed with somewhere between 50-100% charge.
I have also experienced the problem where I hold the phone in my hand and the are a near the antennae/camera gets very warm and my battery drops at almost a percent a second until it's dead. This occurs even with Wi-Fi turned off (which I tested due to "scanning" being the perma-status of wifi when the antennae area got warm).
Coming from every iPhone generation, I really like this phone , but the battery issues are pretty substantial. (worse, dare I say than the annoying death-grip apple tried denying was even real)
---------------
Lastly, each time, the battery meter appropriately reflects the drop of power to 0% from 50%+. I have tried reformatting phone to default RUU, upgraded to 1.85, tried newer Cleanrom, everything, no cigar. If anybody has any advice, I'd really appreciate it. I'd also be happy to provide more info if I can.
Thank You!
robenwzrdhat said:
Coming from every iPhone generation, I really like this phone , but the battery issues are pretty substantial. (worse, dare I say than the annoying death-grip apple tried denying was even real)
Click to expand...
Click to collapse
Pulling the "I had an iPhone, and it was better" card is pointless, and is only going to win you enemies here.
I'd say close to half the people I know with iPhones have had battery issues, or other severe hardware issues, at some point.
Have you tried flashing a different radio? If there is a reception issue, it can be killing your battery quickly searching for the network, even while connected to WiFi.
Also, posting a screenshot of your battery usage (particulary the "large" battery graph called "History details") for us to look at may be useful to help diagnose the problem.
redpoint73 said:
Pulling the "I had an iPhone, and it was better" card is pointless, and is only going to win you enemies here.
I'd say close to half the people I know with iPhones have had battery issues, or other severe hardware issues, at some point.
Have you tried flashing a different radio? If there is a reception issue, it can be killing your battery quickly searching for the network, even while connected to WiFi.
Also, posting a screenshot of your battery usage (particulary the "large" battery graph called "History details") for us to look at may be useful to help diagnose the problem.
Click to expand...
Click to collapse
forums.androidcentral.com/htc-one-x/207174-instant-battery-drain-0-t-one-x.html
This pretty much sums up my issue. Guy just went to ATT to replace his.
Also, I'm not pulling the iPhone is better card. It isn't. Period. This phone is amazing and android is vastly superior to iOS. I hate programming in objective C anyway and though the NDK isn't exactly straightforward at least I can run native code. If anything, my complaining about iPhone's crappy hardware problems should gain me praise and camaraderie. I left iPhone and blindly made the leap to an android phone for a reason. "anything has to be better than this (except blackberry o.0)"
Would hate to try and exchange this phone with ATT, given that mine is rooted and unlocked. I'm expecting resistance, and I haven't done my homework to see if I can walk out of ATT with the latest version replacement and still unlock it. Also, I have a tiny chip on the bottom. Don't know if they'll replace it.
Edit: Also, no issues with reception (4g LTE all day). Haven't tried flashing a new radio, but that may help with the second issue. The battery just plummeting to 0% though makes absolutely no sense.
robenwzrdhat said:
Edit: Also, no issues with reception (4g LTE all day). Haven't tried flashing a new radio, but that may help with the second issue. The battery just plummeting to 0% though makes absolutely no sense.
Click to expand...
Click to collapse
You're right, it doesn't make sense for the actual battery voltage to instantaneously drop like that. Steep line yes, vertical, I don't think its really possible. The vertical drop is likely an incorrect battery meter reading, and the phone correcting itself.
I've seen this once on my phone, and a factory reset cleared it up (never saw it again). Same with at least one other use on here. But the fact that you've flashed some ROMs and ran the RUU should have accomplished the same.
I'd still encourage you to post a screen shot of the battery usage (for several hours of use), as looking at the battery grapsh versus the bars for network signal, awake, etc. might shed some light.
redpoint73 said:
You're right, it doesn't make sense for the actual battery voltage to instantaneously drop like that. Steep line yes, vertical, I don't think its really possible. The vertical drop is likely an incorrect battery meter reading, and the phone correcting itself.
I've seen this once on my phone, and a factory reset cleared it up (never saw it again). Same with at least one other use on here. But the fact that you've flashed some ROMs and ran the RUU should have accomplished the same.
I'd still encourage you to post a screen shot of the battery usage (for several hours of use), as looking at the battery grapsh versus the bars for network signal, awake, etc. might shed some light.
Click to expand...
Click to collapse
I had hoped a factory reset would solve it for me as well, but once it started happening nothing would stop it I will update the thread the next time it happens then. Just got off the phone with ATT and they'll exchange it if it doesn't have physical damage, but the small chip out of the bottom could possibly deem it out of warranty, in which case they charge the full price of the phone (509$)!
robenwzrdhat said:
Just got off the phone with ATT and they'll exchange it if it doesn't have physical damage, but the small chip out of the bottom could possibly deem it out of warranty, in which case they charge the full price of the phone (509$)!
Click to expand...
Click to collapse
From what other XDA users have posted, I don't think one small ding will void your warranty, if its in good shape otherwise. Its when people try to send a phone in that is pretty beat up, or has a cracked screen or water damage, and want a warranty replacement, that they get denied.
Been having the exact same issue with my Rogers One X recently. The problem comes and goes... I woke up and found it dead twice just like you described. Sometimes it even dropped 20% of battery in a flash second.
I'm on Clean Rom V SP1. Just flashed BeastMode kernel a couple days ago and it's normal so far for two days... Just a note (it might not even be relevant), I had to use flashlight for a longer than usual period once. Not sure if the aggressive draw of battery screwed up the battery's voltage meter and thus causing this issue..
redpoint73 said:
From what other XDA users have posted, I don't think one small ding will void your warranty, if its in good shape otherwise. Its when people try to send a phone in that is pretty beat up, or has a cracked screen or water damage, and want a warranty replacement, that they get denied.
Click to expand...
Click to collapse
Thanks for this. Am leery of ATT, as it's often their way or the highway.
robertyouu said:
Been having the exact same issue with my Rogers One X recently. The problem comes and goes... I woke up and found it dead twice just like you described. Sometimes it even dropped 20% of battery in a flash second.
I'm on Clean Rom V SP1. Just flashed BeastMode kernel a couple days ago and it's normal so far for two days... Just a note (it might not even be relevant), I had to use flashlight for a longer than usual period once. Not sure if the aggressive draw of battery screwed up the battery's voltage meter and thus causing this issue..
Click to expand...
Click to collapse
Hope new version of cleanrom works for you. It's a great rom. I haven't used the flashlight beyond turning it on and going "spiffy" and turning it back off, so I doubt that contributed to it. Mine started out every once in a while, then just happened more and more frequently. I don't want to leave my phone charging all night. Think I'm going to try and exchange at ATT today.
redpoint73 said:
You're right, it doesn't make sense for the actual battery voltage to instantaneously drop like that. Steep line yes, vertical, I don't think its really possible. The vertical drop is likely an incorrect battery meter reading, and the phone correcting itself.
I've seen this once on my phone, and a factory reset cleared it up (never saw it again). Same with at least one other use on here. But the fact that you've flashed some ROMs and ran the RUU should have accomplished the same.
I'd still encourage you to post a screen shot of the battery usage (for several hours of use), as looking at the battery grapsh versus the bars for network signal, awake, etc. might shed some light.
Click to expand...
Click to collapse
I think the described problem looks like this (attached)
nvsmksru said:
I think the described problem looks like this (attached)
Click to expand...
Click to collapse
Yup, I understand perfectly what it looks like, and I've seen it myself. I want to see a screenshot of the OP's phone, not random other people. In particular, the screen "History details" accessed when you tap the graph, which shows bar graphs for Mobile network signal, Awake time, etc.
It also seems the OP is talking about 2 completely different issues. One is the vertical drop in the %battery graph (which is probably just a metering error). The other is a steep (but not vertical) battery drainage including the phone possibly overheating. I'm more interested to see the screenshot for that case.
redpoint73 said:
Yup, I understand perfectly what it looks like, and I've seen it myself. I want to see a screenshot of the OP's phone, not random other people. In particular, the screen "History details" accessed when you tap the graph, which shows bar graphs for Mobile network signal, Awake time, etc.
It also seems the OP is talking about 2 completely different issues. One is the vertical drop in the %battery graph (which is probably just a metering error). The other is a steep (but not vertical) battery drainage including the phone possibly overheating. I'm more interested to see the screenshot for that case.
Click to expand...
Click to collapse
Yes, I do mention two issues. The main one I address here is the vertical drop. And the above poster is right, that's exactly what it looks like when the battery dies. If (when) it happens again though I'll include the more detailed graph.
The secondary issue though, some have speculated is a result of the phone losing and then regaining 4g lte signal. Not sure about that one though, as it happens late at night for me. The one night I left my phone in the charger is when I discovered it in the morning. My phone was at 100% charge when I fell asleep, but when I woke it was at 80% and was very warm. It was using more power than the charger was providing, it seems, and that is when I experienced the rapid drop of a percent every second-ish after I took it off the charger. The wi-fi status was also set to "scanning" the entire time the phone was discharging until I rebooted it once it hit 10%. The issue stopped and the phone cooled off. Charged as advertised afterwards.
---Edit
Also, I went to the ATT store and since it was a core store they weren't familiar with exchanges. I got the manager though and had them take a peek at the phone and made certain they noted in my account that it's in good condition (they didn't notice care about the chips, I suppose). Replacement will be here in 6-10 days, but it will be a refurb (which surprised me). Hopefully I won't get two with the same issue.
robenwzrdhat said:
Yes, I do mention two issues. The main one I address here is the vertical drop. And the above poster is right, that's exactly what it looks like when the battery dies. If (when) it happens again though I'll include the more detailed graph.
Click to expand...
Click to collapse
No need to post that graph. I think its just a metering error, and I don't think the "History details" graph will shed much light.
robenwzrdhat said:
The secondary issue though, some have speculated is a result of the phone losing and then regaining 4g lte signal.
Click to expand...
Click to collapse
Could be. The "History details" graph indicates data network strength, as well as dropouts (amongst other things). So that is the one I want to see (not the graph for vertical drop).
redpoint73 said:
Could be. The "History details" graph indicates data network strength, as well as dropouts (amongst other things). So that is the one I want to see (not the graph for vertical drop).
Click to expand...
Click to collapse
Will post it next time it happens!
robenwzrdhat said:
Will post it next time it happens!
Click to expand...
Click to collapse
I've actually had this issue happen to me about once a week, and I haven't figured it out.
I used to think it was from Google Maps or some rogue app eating battery, but I've really been careful about leaving them running and it still occurs.
I'll also try and grab a battery graph next time, but it literally looks like a complete instantaneous jump from 70% or whatever to 0%.
quasitime said:
I've actually had this issue happen to me about once a week, and I haven't figured it out.
I used to think it was from Google Maps or some rogue app eating battery, but I've really been careful about leaving them running and it still occurs.
I'll also try and grab a battery graph next time, but it literally looks like a complete instantaneous jump from 70% or whatever to 0%.
Click to expand...
Click to collapse
Not sure if this has anything to do with it, but I have had "auto-brightness" turned off since I made this post and it hasn't happened since. My phone might also have known that I ordered a replacement, so now it's trying to be on its best behavior.
quasitime said:
I've actually had this issue happen to me about once a week, and I haven't figured it out.
I used to think it was from Google Maps or some rogue app eating battery, but I've really been careful about leaving them running and it still occurs.
I'll also try and grab a battery graph next time, but it literally looks like a complete instantaneous jump from 70% or whatever to 0%.
Click to expand...
Click to collapse
As I've already mentioned, the vertical jump is likely not related to any actual battery usage (such as a rogue app). Its probably just a metering error, and the vertical jump is the meter trying to correct itself. If the issue persists, the only solution that I have seen that helps is a factory reset.
redpoint73 said:
As I've already mentioned, the vertical jump is likely not related to any actual battery usage (such as a rogue app). Its probably just a metering error, and the vertical jump is the meter trying to correct itself. If the issue persists, the only solution that I have seen that helps is a factory reset.
Click to expand...
Click to collapse
You're probably right. The other possibility is a battery failure... I hope not. I've definitely reset battery stats in recovery but I haven't done a factory reset recently. Next time I flash I will.
quasitime said:
You're probably right. The other possibility is a battery failure... I hope not. I've definitely reset battery stats in recovery but I haven't done a factory reset recently. Next time I flash I will.
Click to expand...
Click to collapse
I doubt its a battery failure. I'm no expert on batteries or anything. But I would think that it would be impossible for the battery voltage to just drop to zero. Where would all the energy go? It would at least have to be expelled in a burst of heat or go to ground, or something. Conservation of energy says its got to go somewhere, it just can't vanish. That's what leads me to believe its just a metering error, not a real life event.
As for clearing battery stats, it really does nothing. It just clears the stats displayed on the battery usage screen, which also happens when you turn the phone off, or charge it fully. The myth of clearing battery stats was debunked a while ago: http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/
Either way it's really hard to tell. If it's a battery failure issue, then capacity won't be reliable. In conjunction with a metering problem, then the voltage is not really dropping, it's just reading much lower than it thought it was... which signals the phone to power down.
I'm definitely going to factory reset soon when I flash, and see what happens.
redpoint73 said:
I doubt its a battery failure. I'm no expert on batteries or anything. But I would think that it would be impossible for the battery voltage to just drop to zero. Where would all the energy go? It would at least have to be expelled in a burst of heat or go to ground, or something. Conservation of energy says its got to go somewhere, it just can't vanish. That's what leads me to believe its just a metering error, not a real life event.
As for clearing battery stats, it really does nothing. It just clears the stats displayed on the battery usage screen, which also happens when you turn the phone off, or charge it fully. The myth of clearing battery stats was debunked a while ago: http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/
Click to expand...
Click to collapse
So I think it happened again.
quasitime said:
Either way it's really hard to tell. If it's a battery failure issue, then capacity won't be reliable. In conjunction with a metering problem, then the voltage is not really dropping, it's just reading much lower than it thought it was... which signals the phone to power down.
I'm definitely going to factory reset soon when I flash, and see what happens.
Click to expand...
Click to collapse
Actually, I spoke too soon.
So, my battery is playing funny. It stayed at 100% battery for 8 hours unplugged, then drained itself to 43% (over the course of 4 or so hours)... and shut off at that point. The battery voltage is reported as being 6mV.
Running CM10 latest. Any thoughts?
And most importantly - are there any safety concerns given that the battery voltage is being reported incorrectly by the OS?
small bump due to edit of first post.
Accophox said:
small bump due to edit of first post.
Click to expand...
Click to collapse
You could try a factory reset and don't forget to backup your stuff. There should be no safety issue, its either the OS or the battery is dying.
Three weeks ago I had it not charge past 86% -- a wipe of the battery stats seemed to have fixed, for I haven't seen it since. (There's no way to tell if it actually did anything, but it doesn't hurt to try either.) As far as safety goes, well, it might get a bit warm, but it won't burn down your house.
Welp, small update. Haven't had the time to do much regarding tablet until now. It's now turning off when the battery reads ~55% percent. So my 55% is 0% (it'll fail to turn on). So I guess my battery is dying in the machine. Which sucks. Cause it's no more than 4 months old at this point. And warranty is out of the question, no squaretrade in Canada - and the bootloader is unlocked.
I can tell you one company that I'm not buying another tablet from, ever. Hardware issue, but cause the software is modified... (yadda yadda yadda - I know, I unlocked it... but still, this is clearly a hardware problem and probably would have happened anyway given that my workload remains the same).
Accophox said:
Welp, small update. Haven't had the time to do much regarding tablet until now. It's now turning off when the battery reads ~55% percent. So my 55% is 0% (it'll fail to turn on). So I guess my battery is dying in the machine. Which sucks. Cause it's no more than 4 months old at this point. And warranty is out of the question, no squaretrade in Canada - and the bootloader is unlocked.
I can tell you one company that I'm not buying another tablet from, ever. Hardware issue, but cause the software is modified... (yadda yadda yadda - I know, I unlocked it... but still, this is clearly a hardware problem and probably would have happened anyway given that my workload remains the same).
Click to expand...
Click to collapse
Have your tried wiping the battery stats under Recovery? I had this with my SGS2, but the battery life in itself was quite good. Wiping the stats made my SGS2 read the battery's data anew and fixed the issue of funny percentages being reported (it also kept recharging out of nowhere, which is a hint in itself that something has gone awry with the calibration).
MartyHulskemper said:
Have your tried wiping the battery stats under Recovery? I had this with my SGS2, but the battery life in itself was quite good. Wiping the stats made my SGS2 read the battery's data anew and fixed the issue of funny percentages being reported (it also kept recharging out of nowhere, which is a hint in itself that something has gone awry with the calibration).
Click to expand...
Click to collapse
Nope. Already tried clearing battery stats and doing the full discharge/recharge routine. As I said - it's reporting the incorrect battery voltage... 8mV, which is physically *impossible* for a lithium-ion cell. I'm inclined to believe that my battery is more or less shot. After 4 months.
Accophox said:
Nope. Already tried clearing battery stats and doing the full discharge/recharge routine. As I said - it's reporting the incorrect battery voltage... 8mV, which is physically *impossible* for a lithium-ion cell. I'm inclined to believe that my battery is more or less shot. After 4 months.
Click to expand...
Click to collapse
That's a shame. I was hoping the issue would be with the stats... Guess your battery indeed is dead as a dodo, and you'd better off contacting ASUS for a replacement. I just want to add it is not necessarily their 'fault' -- batteries do die every once in a while, and although I agree that four months is way too quickly, sometimes things like this just slip by, even with good QC (which I do nto pretend ASUS to have, mind you ).
MartyHulskemper said:
That's a shame. I was hoping the issue would be with the stats... Guess your battery indeed is dead as a dodo, and you'd better off contacting ASUS for a replacement. I just want to add it is not necessarily their 'fault' -- batteries do die every once in a while, and although I agree that four months is way too quickly, sometimes things like this just slip by, even with good QC (which I do nto pretend ASUS to have, mind you ).
Click to expand...
Click to collapse
Given it has an unlocked bootloader, Asus will be charging me probably the cost of a new tablet. Overall, I think I'm more or less done with 10" tablets. Nexus 7 is good for the road, and a lightweight laptop will do more for me than a new 10" tablet, even if the cost is higher.
Just wanted to report similar behavior in my tablet.
It stays at 100% after a full charge for like 30 minutes during gaming usage. It used to start dropping from 100% at 8200mv but now doesn't start dropping until 8000mv.
it shuts down at 15%, so it pretty much feels like I have a +10-15% offset.
Using CleanRom inheritance and clemsyns kernel, but after reading this thread and http://forum.xda-developers.com/showthread.php?p=35345450 i feel that this is a sign that my battery is going to kick the bucket in the near future. My tablet is also about 4 months old.
Going to try the usual steps, reflash, return to stock, different rom, factory reset, etc., but I have little hope.
Sent from my ASUS Transformer Pad TF700T
Greetings;
Im having a weird issue (again - but with different device now).
After re-flashing about 4 or 5 times my p3110 with stock firmware (i never used customs) my battery wont charge to 100% anymore... It will reach 99% and wont reach 100%.
This happened to me previously with i9003.
Actually with i9003 everytime i flashed my device the battery would show a lower value each time.
Also; with i9003 i used Custom Roms; and used to " Erase Battery Stats "; wich such erase seemed to be the problem.
Since i've never erased my stats (to keep my device as close to factory as possible); what could be causing this issue?
Any experts on this matter that can provide me accurate info?
Thanks in advance.
Best Regards;
Richard
rgxHost said:
Greetings;
Im having a weird issue (again - but with different device now).
After re-flashing about 4 or 5 times my p3110 with stock firmware (i never used customs) my battery wont charge to 100% anymore... It will reach 99% and wont reach 100%.
This happened to me previously with i9003.
Actually with i9003 everytime i flashed my device the battery would show a lower value each time.
Also; with i9003 i used Custom Roms; and used to " Erase Battery Stats "; wich such erase seemed to be the problem.
Since i've never erased my stats (to keep my device as close to factory as possible); what could be causing this issue?
Any experts on this matter that can provide me accurate info?
Thanks in advance.
Best Regards;
Richard
Click to expand...
Click to collapse
The first thing that must be checked here is that wall charger and usb cables are not at fault. It maybe a coincidence that happened at the same time you started flashing stock firmware.
2nd depends on the firmware which you have chosen,
Different firmwares have different ways of working. Some have blocking modes, some have power saving modes, different set of features, different bugs as well too.
It might be a glitch altogether as well.
Nobody can explain this exactly accurate unless you try these options. Mine aee just aimed at pointing you to the right direction.
---------- Post added at 05:15 PM ---------- Previous post was at 04:41 PM ----------
One more point, tried discharging it completely? Then charging it in offline/online mode?
Now what about battery stats?
Erasing battery stats, well if you have searched on google about it, you would have seen mixed comments about it's affecting battery life, some says it does help, some says it doesn't.
Some feels It's better to do it and
some prefer better to leave it untouched.
My experience on same issue
I had 2 same sduos devices.
on both I used to flash roms
Custom, stock, everything.
Only difference was, on first one, I did erase battery stats many times.
And the second one I didn't ever touched it.
Result-well the first one, I got 4 other batteries replaced for it, and even the new ones would have trouble keeping the charge on the device after I wiped the battery stats. I couldn't blame the battery stockist for giving me 4 faulty batteries. Battery levels were erratic on stock, on custom.
Second one seems working pretty much nicely and i still haven't replaced the original one. Although on this, sometimes I have a glitch, where battery level would drastically go down after restarting the device and slowly build up to the same level without charging.
I know it's a glitch coming from the custom kernel side. Altogether it's better this way.
Greetings Billysam;
Thanks for your repply.
I aleady had checked both (Charger and Cables) they seem to be just fine.
Yesterday i decided to give my p3110 a good rest while charging and finally it charged completely.
Seems like the last 1% (to achieve full battery charge) requires a little bit more time than usual.
It may have been something related to the last flash i've done or due to constant use.
Stil... It is hard to point out what has really happened.
I was a little bit affraid that my battery or System got messed up somehow.
Do you know if flashing affects the Battery Stats in any way?
rgxHost said:
Greetings Billysam;
Thanks for your repply.
I aleady had checked both (Charger and Cables) they seem to be just fine.
Yesterday i decided to give my p3110 a good rest while charging and finally it charged completely.
Seems like the last 1% (to achieve full battery charge) requires a little bit more time than usual.
It may have been something related to the last flash i've done or due to constant use.
Stil... It is hard to point out what has really happened.
I was a little bit affraid that my battery or System got messed up somehow.
Do you know if flashing affects the Battery Stats in any way?
Click to expand...
Click to collapse
The last one percent does take extra time to reach that last 100% charged level.
The answer to your question is Yes and no.
Where is batterystats stored? It's stored inside root/data/system folder
When you flash or format your device data, it gets wiped too as well
So, Yes. cause it got deleted even when you only deleted data.
It affect battery No. Why?
What information that file has? Is it really important?
Information that you see in settings battery
It holds record of all the past history not the current ones. Or future ones.
Now you decide.
Greetings;
Superb Answer!
Exactly the answer i required.
That gives me whole new perspective, and confirms my theory regarding past and new files when flashing.
rgxHost said:
Greetings;
Superb Answer!
Exactly the answer i required.
That gives me whole new perspective, and confirms my theory regarding past and new files when flashing.
Click to expand...
Click to collapse
Further additional bummers
I was checking the batterystat in my device, and to my findings i saw, the file got modified after I full charged the device. So, it gets rewritten/modified/deleted after each full cycle. So, regardless of flashing rom or data, that file is constantly deleted, modified and created!!
Now suppose if I decide to delete that file holding my current charge capacity information, or the better so called "battery calibration" or "wipe battery stats" from cwm, which is nothing more than deleting it the same way from a root manager.
The file would be created again after restart, with new stats, which could be random or the lowest or highest values, according to the algorithm. Which would be seriously clueless of what the heck did happened to it!
That should clear why people claimed to have good and bad experience with their battery stats.
Even if their battery were good, the stats showed it bad and vice versa.
The algorithm is not at all easy to crack, let alone be calibrated. Even If someone would try to do it, Highly impractical, nor worth it. False claims.
Easiest was deleting it, thinking of it as a refresh, users would do it. And termed the coin calibrated.
"Got better", worked!!
No? Keep Wipe again and again.
So many apps were popular for calibration as well that time. Around 4 years back. I Can't remember their names but i did tried them as well!, in the beginning!!
I did learn from my mistake over the years, thanks to you I looked for answer inside me today. Although I stopped that habbit long ago, but you reminded me of digging deeper today
It should never be done.
Greetings Billysam;
Thank God i'm not the only one reaching such conclusion.
I've done pretty much the same steps; except i didn't knew what to check within the "battery stats" file, and i wasn't aware of the algorythm behind it.
I've tested pretty much those applications as well by that time with my i9003. (Back then someone said iDeleting Battery Stats / Calibrating had a "bogus" effect...)
Well.. I did noticed lots of differences each time i Deleted the " Battery Stats " - Either with CWM or through some application.
Sometimes Good improvement, sometimes terrible (until battery got fat, and stopped charging completely - Actually my i9003 is stuck at 60 or 80%, it simply wont go further).
After so many "Mistakes" on my i9003 i realized that the Battery Stats should be left untouched to prevent any " damage " / issues. I just didn't had a clue what exactly was behind that " Battery Stats " file ( Changes and Operations - or Code if you Prefer)
...
With all this being said and tested.
It seems Logical that Whenever we put a device charging, it should charge completely without interruptions.. Else it may or may not corrupt the file, algorythm or make the battery faulty.
Maybe these are the reasons why manufacturers advice people to fully charge their devices, and in some devices to "Not Fully Discharge " them.
Ofcourse, this is just a theory.
Hi everyone !
I haven't seen this info anywhere on XDA, at least on this forum, but i think everyone should know this.
Not trying to take credit in any way, because OP made a terrific job at researching and testing, just wanna spread the knowledge.
Basically : Charging your phone at night or leaving it charging even while at 100% for a few hours will have a big impact on how it behaves and how your battery holds up.
Quick explaination : Since Nougat, you don't get the App Optimization screen anymore on the first boot.
That's because Google has delayed it, and it triggers only in specific conditions : When the device is idle, fully charged, and still plugged in.
This optimzation allows to build the ART cache, which speeds up the system and apps, saving CPU power because it avoids using the JIT (Just In Time) compiler, thus, saving battery juice.
This also means wiping cache isn't going to help with your battery life, quite the opposite.
You'll see he made a test with other users, and the results are quite clear.
Here is a link to the post with detailled explaination and testing, thanks a lot to anupritaisno1 for all this info :
https://forums.oneplus.com/threads/...-and-battery-calibration-myths-busted.993896/
Forced the building through "cmd package bg-dexopt job" on my own OP6 running Pixel Experience, took like 15mn. SOT improved quite a lot.
Interesting read, thanks
What if you charge it at night while the phone is OFF?
Thank you for sharing this :laugh:
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
SOCOM-HERO said:
What if you charge it at night while the phone is OFF?
Click to expand...
Click to collapse
Read the thread linked in OP.
The system works harder when you charge your phone while it's off.
Very interesting read. Basically debunks majority of the stuff people preach to maximize phone performance and battery.
SOCOM-HERO said:
What if you charge it at night while the phone is OFF?
Click to expand...
Click to collapse
If the phone is OFF it can't trigger the optimization task, this won't be beneficial.
In the article he actually made a test about this, you should read it !
Interesting, but... who claimed that clearing the cache helps with the *battery*?
Also, what happened to the old adage "never leave your phone plugged in" because it causes battery wear?
krakout said:
Interesting, but... who claimed that clearing the cache helps with the *battery*?
Also, what happened to the old adage "never leave your phone plugged in" because it causes battery wear?
Click to expand...
Click to collapse
A lot of people claim this, that you should clear the cache after an update, without clear reason why. At least we have a reason not to.
And this old adage is indeed old, like the "Fully discharge it for calibration". We're not in 2002 anymore. Modern technology had the nice idea to remember to stop the charge, and use Lithium batteries haha !
Leaving it plugged at 100% is not causing any wear. The post mentions a response from an electrical engineer, saying the battery is in fact on stand by and the phone is running off the charger only.
krakout said:
Also, what happened to the old adage "never leave your phone plugged in" because it causes battery wear?
Click to expand...
Click to collapse
Debunked here
Totone56 said:
A lot of people claim this, that you should clear the cache after an update, without clear reason why. At least we have a reason not to.
And this old adage is indeed old, like the "Fully discharge it for calibration". We're not in 2002 anymore. Modern technology had the nice idea to remember to stop the charge, and use Lithium batteries haha !
Leaving it plugged at 100% is not causing any wear. The post mentions a response from an electrical engineer, saying the battery is in fact on stand by and the phone is running off the charger only.
Click to expand...
Click to collapse
That's just one way to read it. Leaving it plugged in does not, indeed, mean that it keeps trying to charge. But once it goes down, it will charge up again. Also, supposedly, the fuller the battery is when charging, the higher the temperature and hence, the wear. Cannot attest to that, that's just how the argument goes.
casual_kikoo said:
Debunked here
Click to expand...
Click to collapse
Yes, but that's irrelevant. Totally different issue, I was not talking about calibration.
krakout said:
That's just one way to read it. Leaving it plugged in does not, indeed, mean that it keeps trying to charge. But once it goes down, it will charge up again. Also, supposedly, the fuller the battery is when charging, the higher the temperature and hence, the wear. Cannot attest to that, that's just how the argument goes.
Click to expand...
Click to collapse
Indeed. But from the looks of it, and what i've read in other places, it waits for it to drop a bit. If the battery is not used, it won't fall to 99% in a night, and won't be charged again until you unplug it. Kinda like when your phone is off. It's gonna be a long time before the battery goes down on it's own.
Interesting, gotta try it.
Still, does the <50, >70% not apply in terms of battery wear? I mean, even for straight-forward charges?
krakout said:
Interesting, gotta try it.
Still, does the <50, >70% not apply in terms of battery wear? I mean, even for straight-forward charges?
Click to expand...
Click to collapse
I'd say yes, it still applies. It's a different topic ! Everithing said here is related to software and charging control, when this is more related to battery chemistry. But you're right, it's still true.
To sum it up :
- Charging above 70 or 80% and discharging under 30% (Thoses are the values i read about) is indeed not the best thing for your battery health on the long term.
- BUT, the superior battery life your phone will get with these app optimizations easily counter-balances it. If the phones lasts twice longer, it means 2 times less chaging cycles required, when you think about it (Ofc not accurate, but you see what i mean)
Best thing you can do, if you really want to get the best of both worlds, is staying in between those ideal values, and triggering the optimization manually via the Linux Terminal Emulator
Although, i don't think i'm not personally going to bother, i'll just charge my phone, use it, and charge it again in the evening.
Two days after triggering dexopt manually, without flashing or changing anything, using the phone the same way, i went from 16h idle/2h SOT at the end of the day with 50% remaining to 20h idle/2h15 of SOT with 70% remaining, that's quite a drastic improvement.
Ooh can you share more?I tried googling about triggering the optimization but came up empty...
Yes, that's logic in that, if optimization is so dramatic!
PS I meant 80, not 70, just as you mentioned.
Sent from my ONEPLUS A6000 using Tapatalk
krakout said:
Ooh can you share more?I tried googling about triggering the optimization but came up empty...
Yes, that's logic in that, if optimization is so dramatic!
PS I meant 80, not 70, just as you mentioned.
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Yes, it's hard to get an info about this, wierd.
Run any terminal app on you phone, type "su" to ask for root permission, then enter "cmd package bg-dexopt-job" (without quotes).
It will run for a certain amount of time (between 10mn and more than an hour, depending of the number of apps you have installed).
When you get the shell back (A line appears under the last one to enter another command), it means it's complete.
If you wanna be sure, run it again, it will finish very fast, because the cache will be up to date (It still checks it, so it's not an instant completion).
Do it plugged in the charger, but with like 30% charge, maybe on USB so it doesn't get to 100% too fast, to avoid the awkward situation where it overlaps with the actual automatic background process doing the same thing haha
The phone can heat up a bit because the CPU is working quite a bit.
You can also run the command through an ADB shell on a PC, if you're not rooted.
Or just leave it charging during a night for once, works too
Best way seems to let if charge for the night regularly though (Quote from the OP) :
"I just say overnight because the device being idle is a condition for the optimisation to begin
Also the optimisation is profile guided. If you were to AOT compile your entire base system it would take 4-5 GB off your storage and that is just the base system we haven't even considered the apps you'll install. Since optimisation generates huge optimisation files it is more sensible to only compile what is slow for JIT to do at runtime. This might seem weird but it takes the cache size down to less than 1 GB on most devices
In other words every time you use your phone the runtime sees what is slow and queues it up for optimisation the next time the condition is satisfied"
Wow. This should be pinned somewhere!
I'll do it in the terminal just for fun, but will also leave it (for my first time ever) overnight too.
Thanks, man!
Sent from my ONEPLUS A6000 using Tapatalk
krakout said:
Wow. This should be pinned somewhere!
I'll do it in the terminal just for fun, but will also leave it (for my first time ever) overnight too.
Thanks, man!
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
I think everyone should read this yes, even if it's just for the sake of knowing how things really work.
And i can confirm again, my battery life is so much better ...
A few days ago, going to work, listenting to Spotify on my motorcycle for 20mn, and checking my mails for 2m got me to 96% battery.
Yesterday, and today, same routine, an an hour after that i'm still at 100% ... That's very impressive.
Really interesting.
Sadly the command does nothing on my device.
Sent from my OnePlus6 using XDA Labs
Stroky said:
Really interesting.
Sadly the command does nothing on my device.
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
Are you sure ? It doesn't display anything, that's true. But you'll know it's over when the shell returns.
Or you can juste leave your phone plugged for a night or two, same result.
My battery goes from 100% to ~97% within minutes without using it after unplugging the phone from the charger when charging overnight.
Why is that and how can I get rid of it? It occurs since a few days on custom rom as well as on oos now again.