Ever since I've been on the developer preview for android m, my nexus has been charging from ~10%-100% in about 30-40 minutes using the turbo charger. I was suspicious whether or not the electrical current was lowering as the battery was getting closer to a full charge so I decided to use the app Ampere to see what was going on. From the results I got in the app, I can confirm that the turbo charger isn't working properly and might even be damaging your battery. With a regular charger, the app showed the max output at 380mA and current output was varying around 200-360mA most of the time at ~90% charged. As for the Turbo charger, the max output was 1420mA with the current output varying around 1300-1420mA at ~90% charged. That is significantly higher than the regular charger when the battery is almost fully charged. If these results are accurate, I would highly recommend not using the turbo charger on the android m developer previews since it can potential damage and shorten your devices battery life. I'll update this post if the next preview fixes the issue.:fingers-crossed:
ive been using the turbo charger on my phone every single day since m, now m v2, has been released. not a single issue with using it. and my battery life has been normal as well, about 5-6.5 hours sot daily.
and at 90%, when charging, it should be higher than in a regular charger. the voltage will drop at 92%, and again at like 97 or 98%. and at 100% it rarely stops, as it isnt full yet normally. itll stop when it actually hits full, not 100%.
will it is normal i would say even for 5.1
it get to 1620 mah
and i have another turbo charger(auky) where it reach 2040 mah
simms22 said:
ive been using the turbo charger on my phone every single day since m, now m v2, has been released. not a single issue with using it. and my battery life has been normal as well, about 5-6.5 hours sot daily.
and at 90%, when charging, it should be higher than in a regular charger. the voltage will drop at 92%, and again at like 97 or 98%. and at 100% it rarely stops, as it isnt full yet normally. itll stop when it actually hits full, not 100%.
Click to expand...
Click to collapse
That and m2 preview has battery calibration issues and it may say say battery is at 90% full but it probably isnt
The charging continues even when the indicator is at 100% (i use a different widget to monitor that)
Charging does stop about half an hour after hitting 100%
It does not matter what charger you use.
The calibration is way off with Android M.
holeindalip said:
That and m2 preview has battery calibration issues and it may say say battery is at 90% full but it probably isnt
Click to expand...
Click to collapse
i guess that when my battery dies at 0%, that it isnt accurate either? that 5-6.5 hour sot that i normally get is just my imagination? btw, i charge not til it reaches 100%, but until it actually stops charging. which us usually within 30 min of hitting 100%. oh, and full battery it is.
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
Brotuck said:
The charging continues even when the indicator is at 100% (i use a different widget to monitor that)
Charging does stop about half an hour after hitting 100%
It does not matter what charger you use.
The calibration is way off with Android M.
Click to expand...
Click to collapse
its always like that, not just on m. ive been watching my n4, n5, and n6 charge over the last few years, and it never ever stops charging at 100%. it stops charging when there's no more voltage going in.
I suppose no one has a multimeter they could hook up inline with the charger to actually read the current without relying on software? Even if the current displayed in that app is accurate you'll then have to check the voltage of the battery to eliminate the possibility that a bug is causing the level of charge to be displayed incorrectly, and need a frame of reference for comparison.
simms22 said:
ive been using the turbo charger on my phone every single day since m, now m v2, has been released. not a single issue with using it. and my battery life has been normal as well, about 5-6.5 hours sot daily.
and at 90%, when charging, it should be higher than in a regular charger. the voltage will drop at 92%, and again at like 97 or 98%. and at 100% it rarely stops, as it isnt full yet normally. itll stop when it actually hits full, not 100%.
Click to expand...
Click to collapse
Can you link the source where you got those percentages from? Because those numbers are off from an article I read in the past. Can't seem to find it though.
elvintopalov said:
Can you link the source where you got those percentages from? Because those numbers are off from an article I read in the past. Can't seem to find it though.
Click to expand...
Click to collapse
no, i cant, sorry. the numbers are guesstimates according to me watching them over the years. most articles i never listen to anyways, as most the people who write those articles are generally clueless(in reality).
simms22 said:
no, i cant, sorry. the numbers are guesstimates according to me watching them over the years. most articles i never listen to anyways, as most the people who write those articles are generally clueless(in reality).
Click to expand...
Click to collapse
Quick Charge 2.0 was released about a year ago. And your numbers are guesstimates that have no proof or factual backing where as the article I read was backed by information from Qualcomm (if I recall correctly). The turbo charger starts slowing down around the 50% mark and then progressively gets slower as the battery gets closer to a full charge. If the turbo charger were to still output a significantly higher voltage compared to a regular charger at the percentages you listed, that would still harm the battery. The factual numbers don't lie, but your guesstimates can be inaccurate.
elvintopalov said:
Quick Charge 2.0 was released about a year ago. And your numbers are guesstimates that have no proof or factual backing where as the article I read was backed by information from Qualcomm (if I recall correctly). The turbo charger starts slowing down around the 50% mark and then progressively gets slower as the battery gets closer to a full charge. If the turbo charger were to still output a significantly higher voltage compared to a regular charger at the percentages you listed, that would still harm the battery. The factual numbers don't lie, but your guesstimates can be inaccurate.
Click to expand...
Click to collapse
thats fine, but you can watch the voltage yourself when you charge it. i can only tell you what i see, not what its supposed to be in theory. speaking of, ive been at 100% for 7 minutes, and am still having voltage enter my phone, i mean its still charging(my widget shows 83mA still going into the phone). if you listened to what qualcomm says, they say it stops charging at 100%, will drop to 98%, then itll start charging again. guess what? it doesnt work that way in reality.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 06:07 PM ---------- Previous post was at 05:46 PM ----------
btw, im using the CurrentWidget.
The battery only has to last a couple of years. I wouldn't sweat it too much.
Sent from my Nexus 6 using Tapatalk
It's already been stated elsewhere that there is a bug in preview 2 and it thinks the battery capacity is only 2000mA.
That's why it charges so fast, and drains so fast, and the reason it will charge more if left charging after 100% - and why it doesn't trickle charge when it gets close to 100%..
Luxferro said:
That's why it charges so fast, and drains so fast, and the reason it will charge more if left charging after 100% - and why it doesn't trickle charge when it gets close to 100%..
Click to expand...
Click to collapse
well, no. considering it behaves this way on android 5.1.1, 5.1, 5.0, 4.4, 4.3, 4.2, 4.1, etc..
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
brizey said:
The battery only has to last a couple of years. I wouldn't sweat it too much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
very true. the chances of me getting rid of the device, or a new device, way before the battery starts seeing age is much better than something happening to it before i get rid of it.
simms22 said:
well, no. considering it behaves this way on android 5.1.1, 5.1, 5.0, 4.4, 4.3, 4.2, 4.1, etc..
Click to expand...
Click to collapse
You are just wrong. So many people have this problem... but yet you don't. It's already been pointed out an issue with the kernel...
Normally when it gets to around 90% it's charge rate will slow to a crawl to prevent battery damage (trickle charging). This doesn't happen on preview 2 because it's not really fully charged, even though it will say it's at 100%.
Luxferro said:
You are just wrong. So many people have this problem... but yet you don't. It's already been pointed out an issue with the kernel...
Normally when it gets to around 90% it's charge rate will slow to a crawl to prevent battery damage (trickle charging). This doesn't happen on preview 2 because it's not really fully charged, even though it will say it's at 100%.
Click to expand...
Click to collapse
listen, as i said ive been watching my devices charge for years. when it hits 100%, it almost never stops charging. a little charge goes into the device for some time after 100%. again, you can watch this. you can flash 5.1.1 instead of m and it will do the same thing. my battery doesnt have an issue on m v2. it acts exactly the same as before m v2. no matter what, i see between 5-6.5 hours sot, that didnt change. now i know some people have issues with the battery on m v2, I AM NOT ONE OF THOSE PEOPLE. i have been with android since the very begining, and am by far not a noobie. all im saying here is exactly what i see, no more, and no less.
simms22 said:
listen, as i said ive been watching my devices charge for years. when it hits 100%, it almost never stops charging. a little charge goes into the device for some time after 100%. again, you can watch this. you can flash 5.1.1 instead of m and it will do the same thing. my battery doesnt have an issue on m v2. it acts exactly the same as before m v2. no matter what, i see between 5-6.5 hours sot, that didnt change. now i know some people have issues with the battery on m v2, I AM NOT ONE OF THOSE PEOPLE. i have been with android since the very begining, and am by far not a noobie. all im saying here is exactly what i see, no more, and no less.
Click to expand...
Click to collapse
I'm also not a noob, and been using Android since the OG Droid. Have had every nexus since. Don't use enable-a-noob tool-kits, blah blah blah. I'm also exclusively using the M Preview since it was released (haven't switched back to lollipop at all - full wipe going to preview 1), and there is a huge difference from preview 1 to 2. Basically I was fully charged when going from preview 1 to 2, and after flashing 2 it drained the battery at an alarming rate to below 15%. But it didn't really, since it was a full charge on preview 1, it ran at less than 5% for hours with no battery saver mode (playing movies trying to make it power off). Fully charged it afterwards, and while better than the 1st battery cycle, it's still messed up. It will charge to full from ~10% in like 30 minutes, and doesn't last as long as M1. So I'm pretty confident that it doesn't completely charge, and that M2 is just messed up...
I'm not sure how it's working fine for you, but since you don't daily driver it, and switch back and forth to different roms, then that might be a reason. But your case seems to be the exception, and not common - most people are complaining about the terrible battery life because something isn't right with the battery /stats/calibration/capacity setting/ of the battery. But your case seems like a one-off.
Luxferro said:
I'm also not a noob, and been using Android since the OG Droid. Have had every nexus since. Don't use enable-a-noob tool-kits, blah blah blah. I'm also exclusively using the M Preview since it was released (haven't switched back to lollipop at all - full wipe going to preview 1), and there is a huge difference from preview 1 to 2. Basically I was fully charged when going from preview 1 to 2, and after flashing 2 it drained the battery at an alarming rate to below 15%. But it didn't really, since it was a full charge on preview 1, it ran at less than 5% for hours with no battery saver mode (playing movies trying to make it power off). Fully charged it afterwards, and while better than the 1st battery cycle, it's still messed up. It will charge to full from ~10% in like 30 minutes, and doesn't last as long as M1. So I'm pretty confident that it doesn't completely charge, and that M2 is just messed up...
I'm not sure how it's working fine for you, but since you don't daily driver it, and switch back and forth to different roms, then that might be a reason. But your case seems to be the exception, and not common - most people are complaining about the terrible battery life because something isn't right with the battery /stats/calibration/capacity setting/ of the battery. But your case seems like a one-off.
Click to expand...
Click to collapse
lol, ive been reading about people with battery issues on m v2 since it came out, i know about it. ive even had one very bad battery day since, but it was a rare circumstance. generally, i keep my phone on a charger for long periods of time, even after 100%. i actually watch it until it stops charging, until 0-1mV is coming in. sometimes it happens 5 min after 100, sometimes 20-30 minutes after. but that charge that still goes in at that point is extremely light, less then 100mV, almost a trickle.
our battery % stats are also not 100% accurate, never have been, from the very begining. its more of an educated guesstimate. so thats another reason, i think, could be why it still charges a little after 100%.
oh, and if you look at my xda history, its extremely rare that i get an issue. most of the time i have no issues when many have them. i yend to fix them myself, if and when i actually have an issue.
simms22 said:
listen, as i said ive been watching my devices charge for years. when it hits 100%, it almost never stops charging. a little charge goes into the device for some time after 100%. again, you can watch this. you can flash 5.1.1 instead of m and it will do the same thing...
Click to expand...
Click to collapse
I concur. My phone on LP charges anywhere from 10 - 30 mins even after hitting 100%. I usually wait for it to stop charging but sometimes I unplug before and then within a few secs it drops to 99/98%.
I can't speak for M as I used it for a very brief period of time.
Khizar said:
I concur. My phone on LP charges anywhere from 10 - 30 mins even after hitting 100%. I usually wait for it to stop charging but sometimes I unplug before and then within a few secs it drops to 99/98%.
I can't speak for M as I used it for a very brief period of time.
Click to expand...
Click to collapse
its the same as in 5.1.1, 5.1, and 5.0 for me
Related
Anyone else notice this?? I've run both the first and the second 2.2 leaked Rom, and both exhibit this same issue. Okay first a little info: stock battery, stock HTC wall charger and stock use cable. I don't charge off a use port on a comp, always the wall charger.
Now, on stock 2.1, I could run the battery all the way down, connect the charger, and be back to full charge in max 1.5 hours. On 2.2, it takes more than twice that long. So I went thru the whole downgrade process (pain!) to get back to stock 2.1, ran that for a day and confirmed, charging on the wall charger gets about 1% a minute. Went back to 2.0 radio and second leaked 2.2 ota, and yeah, back to taking 2-3 mins to get a percent, about 3.5-4 hours to full charge.
So..... what gives? Anyone else noticing this? Can it be fixed via patch or something? Is it the radio, the new kernel, what?
its probably the new radio. i dont know how the radio directly affects battery life tho. it is not the kernel, because i am running cm6 and the problems have persisted on cm6 too. i have been experienceing these problems too
-jd
Radio
jdkoreclipse said:
i dont know how the radio directly affects battery life tho
Click to expand...
Click to collapse
The radio could be the #2 drain on a battery (short of 100% on screen) ... if the radio is not getting the signal it wants, it hunts and hunts, and 1x draws incredible power from the battery vs 3G.
The buggy radio and buggy beta could easily be causing you trouble in your area, if they just don't play right with the signal you are getting. Hopefully when the non-beta radio comes out, things will change.
Mind you, my battery life seems fine, no worse than stock anyways. It's just the charging time that has gotten dramatically worse.
Same..there's no reason my phone should be charging for close to 4 to 5 hours I don't know what's up with that
sylent101 said:
Same..there's no reason my phone should be charging for close to 4 to 5 hours I don't know what's up with that
Click to expand...
Click to collapse
I may be all wet...but there is a battery file in your phone that I think gets wiped when you install a new ROM.
I do all of my charging at night, so I don't know how long it takes after wiping and installing ROMs. I do remember it taking about three hours to charge the battery the very first time I plugged it in.
douger1957 said:
I may be all wet...but there is a battery file in your phone that I think gets wiped when you install a new ROM.
I do all of my charging at night, so I don't know how long it takes after wiping and installing ROMs. I do remember it taking about three hours to charge the battery the very first time I plugged it in.
Click to expand...
Click to collapse
Doesn't explain why after I wiped and went back to 100% stock my charge time went back to taking no more than 90 mins...
Nah I flashed roms all the time on my Droid never took this long to charge. Even on my inc cyanogen 6 never took that long its definitely something about 2.2 roms or sky raider.
I have this problem on mine and made a thread on androidforums. After watching a few things I came to the conclusion its the cpu speed. It never throttles down below about 500-600 mhz. Open setCPU and don't touch anything. You'll see it won't drop to the 200s like its supposed to.
Someone came up with a work around by using setcpu. Create a profile for when the screen is off so that the max is 245 mhz. You'll find that your charge times will be a lot better.
Even though this works I would like to know why the phone is not throttling down at idle like its supposed to. Someone with more knowledge might have the answer.
I had noticed that and posted a thread about it awhile back. I have a hard time believing that is the sole reason for tripping charge times though
Dsoto87 said:
I have this problem on mine and made a thread on androidforums. After watching a few things I came to the conclusion its the cpu speed. It never throttles down below about 500-600 mhz. Open setCPU and don't touch anything. You'll see it won't drop to the 200s like its supposed to.
Someone came up with a work around by using setcpu. Create a profile for when the screen is off so that the max is 245 mhz. You'll find that your charge times will be a lot better.
Even though this works I would like to know why the phone is not throttling down at idle like its supposed to. Someone with more knowledge might have the answer.
Click to expand...
Click to collapse
all the explanations posted so far would be a cause of battery DRAIN issues, which most people claim to see better overall battery life since jumping on 2.2 (myself included). none of these could explain why charge times would take twice as long. i myself have had better battery life on 2.2, but charge times are definitely in the 3-4 hour range as opposed to the 1.5 hours it was before. BUT, one theory is htc might have lowered the charge input from what it was before, meaning a slower charge time but preserving battery health and possibly increasing battery life. just a guess, chemistry majors correct me if im wrong lol.
mb02 said:
all the explanations posted so far would be a cause of battery DRAIN issues, which most people claim to see better overall battery life since jumping on 2.2 (myself included). none of these could explain why charge times would take twice as long.
Click to expand...
Click to collapse
If the phone isnt underclocking even when the screen is off, it would be using more power even while charging, which would explain the long charge times.
Proof of concept would be, if you try and charge while using bluetooth and gps in the car you may not lose charge, but it will not charge as quickly as if you are not using those things.
if the CPU use is high then the battery would not charge as quickly.
I'm still not so certain that the setcpu profle has solved my problem, still havent been conscious of it enough to be sure.
mb02 said:
all the explanations posted so far would be a cause of battery DRAIN issues, which most people claim to see better overall battery life since jumping on 2.2 (myself included). none of these could explain why charge times would take twice as long. i myself have had better battery life on 2.2, but charge times are definitely in the 3-4 hour range as opposed to the 1.5 hours it was before. BUT, one theory is htc might have lowered the charge input from what it was before, meaning a slower charge time but preserving battery health and possibly increasing battery life. just a guess, chemistry majors correct me if im wrong lol.
Click to expand...
Click to collapse
Common sense would tell you that if something is draining the battery, charge times would be higher...
Gbenj. Its definitely not a full fix for it since it requires the screen to be off but it has definitely cut down on my charge times. Its still no where near what it was for 2.1 but atleast I dont have to wait 4 hours for 10%.
gbenj said:
If the phone isnt underclocking even when the screen is off, it would be using more power even while charging, which would explain the long charge times.
Proof of concept would be, if you try and charge while using bluetooth and gps in the car you may not lose charge, but it will not charge as quickly as if you are not using those things.
if the CPU use is high then the battery would not charge as quickly.
I'm still not so certain that the setcpu profle has solved my problem, still havent been conscious of it enough to be sure.
Click to expand...
Click to collapse
Dsoto87 said:
Common sense would tell you that if something is draining the battery, charge times would be higher...
Gbenj. Its definitely not a full fix for it since it requires the screen to be off but it has definitely cut down on my charge times. Its still no where near what it was for 2.1 but atleast I dont have to wait 4 hours for 10%.
Click to expand...
Click to collapse
All understood, BUT, yesterday when using gps nav for a few hours and on the car charger, i was actually still LOSING battery. nothing else was on (bluetooth or wifi) no calls, no texts or anything. 2.1, i still gained charge while using gps on the car charger as well as having an overclocked kernel. so its definitely not a cpu issue considering peak processor speed has not been tampered with.
Just a thought but perhaps the FROYO Rom that you flashed has a fix in it for the problem with charging. In otherwords perhaps it is actually charging the whole battery. I haven't paid any attention to mine as to whether it is taking longer. I usually just charge while I sleep and then while I am in the car and sometimes at my desk if I plan to plug in for something I will just leave it plugged so I get more use of higher drain features when I go home. I noticed though that if you bump charge as recommended, (pre-update) I only did it once and saw little to no improvement, it took for ever. After I charged it to green, I turned it off and charged it to green, unplugged it plugged it back charged to green, and repeated until it was green when I first plugged in. Now it seems to me that the problem is a software/system issue so it would be plausible that a software solution could be developed. I haven't tried since I updated and the ROM I am currently using gives me the same battery life I had before but now I can leave GPS on all the time something I couldn't even think about with Stock everything.
So I may be wrong but it may be that it is taking longer to charge because it is actually charging the chunk of battery that it hadn't been charging before. Just a thought and since I am pretty sure I don't have the same ROM you have I won't venture to test and post results but perhaps you could.
fezzik77 said:
Just a thought but perhaps the FROYO Rom that you flashed has a fix in it for the problem with charging. In otherwords perhaps it is actually charging the whole battery. I haven't paid any attention to mine as to whether it is taking longer. I usually just charge while I sleep and then while I am in the car and sometimes at my desk if I plan to plug in for something I will just leave it plugged so I get more use of higher drain features when I go home. I noticed though that if you bump charge as recommended, (pre-update) I only did it once and saw little to no improvement, it took for ever. After I charged it to green, I turned it off and charged it to green, unplugged it plugged it back charged to green, and repeated until it was green when I first plugged in. Now it seems to me that the problem is a software/system issue so it would be plausible that a software solution could be developed. I haven't tried since I updated and the ROM I am currently using gives me the same battery life I had before but now I can leave GPS on all the time something I couldn't even think about with Stock everything.
So I may be wrong but it may be that it is taking longer to charge because it is actually charging the chunk of battery that it hadn't been charging before. Just a thought and since I am pretty sure I don't have the same ROM you have I won't venture to test and post results but perhaps you could.
Click to expand...
Click to collapse
bump charging is still required by anyone on 2.2 so its not charging any more of the battery than what it used to, just a lot slower.
Agreed, it doesn't make bump charging any less required for "full" charge, also, this theory would mean we'd be getting significantly better battery life.... I most definitely was not.
It's possible they reduced the charger output to the battery to increase battery life/reduce heat while charging.
sryan2k1 said:
It's possible they reduced the charger output to the battery to increase battery life/reduce heat while charging.
Click to expand...
Click to collapse
if by battery life you mean overall battery health over time then yes, that is what i believe as well. also, these leaked froyo roms are all developmental, not final releases. im guessing that they may have tried a fix for battery issues but it didnt work out right in these roms so im hoping in the final release it will be truly fixed.
has anyone noticed that the battery stops charging after a while? it almost seems like the system is stopping the charge because its running for so long. anyone seen anything like this?
I noticed that I was getting some really bad battery life with only average usage, so I figured that this might be in part due to it being turned on and activated at the store without first being charged. So last night I tried to go through the motions of recalibrating the battery, but there is no way to reset the stats. I finally got the battery down to about 5% and it hovered there for long over an hour with constant audio streaming and then later 3d gaming, so I know it is not reading the battery properly. I charge it all the way with the phone off overnight, and when I get up, it is reading 100% without the disconnect warning. I turn it on and I have been using it all day today, but I am having the same symptoms.
Is there a way to accurately recalibrate the battery sensor?
Having the same problems.
Same problem for me... I recharged my phone to 100% and did a factory reset today, hopefully that helps.
Sent from my SPH-D700 using XDA App
you could try the battery conditioning method that fixed a lot of evo users' battery issues: h**p://forum.xda-developers.com/showthread.php?t=701567
dwyw42 said:
you could try the battery conditioning method that fixed a lot of evo users' battery issues: h**p://forum.xda-developers.com/showthread.php?t=701567
Click to expand...
Click to collapse
I did this and the battery is great! I checked an email and browsed the web for 5 minutes and my battery is at 97 after an hour and a half.
lehaman310 said:
I did this and the battery is great! I checked an email and browsed the web for 5 minutes and my battery is at 97 after an hour and a half.
Click to expand...
Click to collapse
did anyone else try this and have success? I had my phone on 0% for a good long while the other day and it never shut off. There is definitely something wrong with the initial battery calibration for a lot of us.
trying this at the moment. will update when done.
It's a lithium-ion battery, guys... They don't have a memory effect. All calibrating it (as you all call it) is going to do is shorten the overall lifespan of the battery. You can argue all you want, but it only takes a little bit of research to learn all of this. People are too used to the days of nickel-metal hydride and nickel-cadmium batteries where calibration and training were necessary.
These batteries like to hold a charge and be full. They like top-offs and constant charging. If you can, charge your phone mid-day, but at least every night. Draining your battery - especially as regularly as some as you do to "calibrate" it - will only bring it closer to its eventual death.
DevinXtreme said:
It's a lithium-ion battery, guys... They don't have a memory effect. All calibrating it (as you all call it) is going to do is shorten the overall lifespan of the battery. You can argue all you want, but it only takes a little bit of research to learn all of this. People are too used to the days of nickel-metal hydride and nickel-cadmium batteries where calibration and training were necessary.
These batteries like to hold a charge and be full. They like top-offs and constant charging. If you can, charge your phone mid-day, but at least every night. Draining your battery - especially as regularly as some as you do to "calibrate" it - will only bring it closer to its eventual death.
Click to expand...
Click to collapse
No one is talking about draining the battery as a calibration method. Read the post on xda.
odub303 said:
No one is talking about draining the battery as a calibration method. Read the post on xda.
Click to expand...
Click to collapse
Read the first post, got frustrated (a lot of Hero users had the same idea about discharging... poor people probably get awful battery life now), and posted my reply.
The EVO users might be on to something, but that behavior is more associated with a battery that has been let dormant forever. If you have an Xbox 360 (with play and charge kit) or PS3 with multiple controllers, you can test this. Most people use one controller and the extras don't get much play. When you try to charge it, it'll read full much before it is actually full and will die quickly, but if you continue to connect and disconnect the charger, it will keep trying to charge it and eventually will come back to life...
If this is the case with our Epics, I wonder if we're using old batteries... My manufacturing date on my battery is July 27, which means it probably sat around for a little over a month before it got used again. But that shouldn't be long enough to cause this problem.
Did anyone else have an almost-dead battery when they got it? My package said that the battery should have been fully charged, but it certainly wasn't. What is the manufacturing date on everyone else's battery?
DevinXtreme said:
Read the first post, got frustrated (a lot of Hero users had the same idea about discharging... poor people probably get awful battery life now), and posted my reply.
The EVO users might be on to something, but that behavior is more associated with a battery that has been let dormant forever. If you have an Xbox 360 (with play and charge kit) or PS3 with multiple controllers, you can test this. Most people use one controller and the extras don't get much play. When you try to charge it, it'll read full much before it is actually full and will die quickly, but if you continue to connect and disconnect the charger, it will keep trying to charge it and eventually will come back to life...
If this is the case with our Epics, I wonder if we're using old batteries... My manufacturing date on my battery is July 27, which means it probably sat around for a little over a month before it got used again. But that shouldn't be long enough to cause this problem.
Did anyone else have an almost-dead battery when they got it? My package said that the battery should have been fully charged, but it certainly wasn't. What is the manufacturing date on everyone else's battery?
Click to expand...
Click to collapse
The build date on my battery is 7-25-10, and it was really low when I got my phone. Of course, I had no clue because the battery icon in the upper right hand corner is horribly inaccurate lol. I have a feeling a lot of the July 2010 build batteries are defective in some way or another. There is a running thread on adroidcentral where people are posting their phone and battery build dates and what, if any, issues they are having.
DevinXtreme said:
Read the first post, got frustrated (a lot of Hero users had the same idea about discharging... poor people probably get awful battery life now), and posted my reply.
The EVO users might be on to something, but that behavior is more associated with a battery that has been let dormant forever. If you have an Xbox 360 (with play and charge kit) or PS3 with multiple controllers, you can test this. Most people use one controller and the extras don't get much play. When you try to charge it, it'll read full much before it is actually full and will die quickly, but if you continue to connect and disconnect the charger, it will keep trying to charge it and eventually will come back to life...
If this is the case with our Epics, I wonder if we're using old batteries... My manufacturing date on my battery is July 27, which means it probably sat around for a little over a month before it got used again. But that shouldn't be long enough to cause this problem.
Did anyone else have an almost-dead battery when they got it? My package said that the battery should have been fully charged, but it certainly wasn't. What is the manufacturing date on everyone else's battery?
Click to expand...
Click to collapse
Maybe I didn't word my post correctly, but I know about the Ni-Cd/Li-Ion difference, and I know that the Li-Ion's don't have memory, but I am talking about recalibrating the sensor to accurately report the battery life. I know that this prinicple works even if my explanation isn't accurate, because when I first switched to Darchstar's (may his name be praised) CyanogenMod Froyo port, the battery life was terrible; but when I applied the battery fix, the "recalibration", or whatever the proper word is, the battery life increased fivefold. That is what I want to achieve on the Epic, move that extra power which is found on the low end so it is accurately displayed on the scale (no, not physically move it, I just didn't know how else to say that). I'm going to try the Evo fix now and see how that works, but I hate the "Charging Complete" thing, because I woke up, and my phone was at 68% battery, so it just sat there plugged in but not recharging all night.
My battery manufacture date is August 12th, and when I got the phone, I didn't actually look at the real battery life, but the indicator was in the second stop, so it could have been anywhere in a wide range, since the first stop doesn't seem to occur until about 70%.
dwyw42 said:
you could try the battery conditioning method that fixed a lot of evo users' battery issues: h**p://forum.xda-developers.com/showthread.php?t=701567
Click to expand...
Click to collapse
trying this now as i type. hope it works because my battery life is no good lol. let yall know results when im done and test it out
USAF22 said:
Maybe I didn't word my post correctly, but I know about the Ni-Cd/Li-Ion difference, and I know that the Li-Ion's don't have memory, but I am talking about recalibrating the sensor to accurately report the battery life.
Click to expand...
Click to collapse
Your understanding is the same as mine. Tjhe old NiCads needed to be "conditioned" by deep discharge, but the Lithium Ions don't. However, our problem is not conditioning the physical battery, but calibrating the logic on the phone that calculates the battery status. It needs to learn what 0% and 100% look like to phone's sensors.
The sensors themselves, IIRC, are reading two physical properties: voltage and temperature. The calculated percentage is a function of these, but can vary with the state of a given battery unit.
So it is a good idea to do a deep-discharge cycle at the beginning, and maybe occasionally later, to calibrate this function. However, it is also true that a deep discharge is not healthy for the long-term battery life, so the procedure should be performed sparingly.
DevinXtreme said:
Read the first post, got frustrated (a lot of Hero users had the same idea about discharging... poor people probably get awful battery life now), and posted my reply.
The EVO users might be on to something, but that behavior is more associated with a battery that has been let dormant forever. If you have an Xbox 360 (with play and charge kit) or PS3 with multiple controllers, you can test this. Most people use one controller and the extras don't get much play. When you try to charge it, it'll read full much before it is actually full and will die quickly, but if you continue to connect and disconnect the charger, it will keep trying to charge it and eventually will come back to life...
If this is the case with our Epics, I wonder if we're using old batteries... My manufacturing date on my battery is July 27, which means it probably sat around for a little over a month before it got used again. But that shouldn't be long enough to cause this problem.
Did anyone else have an almost-dead battery when they got it? My package said that the battery should have been fully charged, but it certainly wasn't. What is the manufacturing date on everyone else's battery?
Click to expand...
Click to collapse
I had an all but dead battery when I picked up my first phone. I had many other problems with that phone and took it back for another. Unfortunately I kept the original battery. After numerous little problems with the phone, and poor charge times, I swapped the battery out for the one in the charger/battery kit I picked up. It was almost fully charged out of the box. I did a full charge on it, and all the little problems seem to have vanished. The date on the "bad" battery was 7/27/2010. I'm guessing there's a bunch of unreliable batteries out there, and they may be the cause behind other problems people are having.
Now if they can just come up with a fix for the WiFi config file corruption problem, I'm totally sold on this phone.
There is a thread on here that talks about calibrating the battery for an Evo and it did wonders for my phone. I don't have the link but here are the steps:
1. Phone is on. Charge untill told to unplug charger.
2. Unplug charger and turn off phone.
3. Plug in charger and charge until phone beeps (about 1-5 minutes)
4. Unplug charger and turn on phone
5. Charge to 100% again (1-5 minutes)
6. Unplug charger and reboot.
7. All done! Enjoy a new battery.
Before I did this "calibration", I was really feeling bummed that my battery didn't last. I followed a few other recommendations (dark screen, turn off unused services, etc) and I got 1.5 days and still had 10 percent left! This was using the device lightly to moderately. Try it but DO NOT RUN YOUR BATTERY ALL THE WAY DOWN! It's not good for these types of batteries even though there is a safety zone built in.
johnnyh64 said:
There is a thread on here that talks about calibrating the battery for an Evo and it did wonders for my phone. I don't have the link but here are the steps:
1. Phone is on. Charge untill told to unplug charger.
2. Unplug charger and turn off phone.
3. Plug in charger and charge until phone beeps (about 1-5 minutes)
4. Unplug charger and turn on phone
5. Charge to 100% again (1-5 minutes)
6. Unplug charger and reboot.
7. All done! Enjoy a new battery.
Before I did this "calibration", I was really feeling bummed that my battery didn't last. I followed a few other recommendations (dark screen, turn off unused services, etc) and I got 1.5 days and still had 10 percent left! This was using the device lightly to moderately. Try it but DO NOT RUN YOUR BATTERY ALL THE WAY DOWN! It's not good for these types of batteries even though there is a safety zone built in.
Click to expand...
Click to collapse
I'll try this tonight, I did the method that was posted earlier in the evo thread and my charge actually reached 100% for once but was back down to 98% 2 minutes later. I'll try it again I suppose.
p2flol said:
I'll try this tonight, I did the method that was posted earlier in the evo thread and my charge actually reached 100% for once but was back down to 98% 2 minutes later. I'll try it again I suppose.
Click to expand...
Click to collapse
Well I just did it so we'll see how my battery is at work, it still sits at 98% I'm guessing the cells are not balanced.
I did the charge, power off, charge, power on sequence this morning about 5 times. I have the Battery Watcher widget installed, and I just now I charged it until it said it was fully charged and Battery Watcher said it was 97%. I powered off the Epic, and charged it until it said it was full, I powered it on and Battery Watcher said 91%. What's going on?? Is Battery Watcher inaccurate? Is the phone's way of determining how charged it is inaccurate?
USAF22 said:
I noticed that I was getting some really bad battery life with only average usage, so I figured that this might be in part due to it being turned on and activated at the store without first being charged. So last night I tried to go through the motions of recalibrating the battery, but there is no way to reset the stats. I finally got the battery down to about 5% and it hovered there for long over an hour with constant audio streaming and then later 3d gaming, so I know it is not reading the battery properly. I charge it all the way with the phone off overnight, and when I get up, it is reading 100% without the disconnect warning. I turn it on and I have been using it all day today, but I am having the same symptoms.
Is there a way to accurately recalibrate the battery sensor?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just topping the battery off, I thought this was funny, took it off charger, and put back on charger. and it still says fully charged + charging.. yeah.. I agree something wack with the sensor. This lasted for 4-5 mins.. then phone gave me pop up/vibrated.. (fully Charged!)
Yes, according to this guy.
http://forum.androidcentral.com/galaxy-tab/44768-bettery-life-results.html
Anyone feel the same way?
its better than i expected, but i doubt its better than sammys tests
Same here it seem way better than I expected but I haven't tested the battery life thoroughly yet but indeed it is very good.
Tomorrow I will be flying back home. I'll be in the air for about 6 hours. I have 2 movies to watch, plus I'll be playing games and will listen to music. I am planning not to charge my tab until I get home. Let's see how it goes. I will update.
Being that my battery use is ~80% display, i should probably consider turning down the brightness. Still, I have been playing with it here and there throught the day (about 7 hours away from the charger now) and the battery level is still 75%
Somebody needs to find a way to mod the autobrightness to have a few options...I like the feature, but it is just a bit too dim for me.
beestee said:
Being that my battery use is ~80% display, i should probably consider turning down the brightness. Still, I have been playing with it here and there throught the day (about 7 hours away from the charger now) and the battery level is still 75%
Somebody needs to find a way to mod the autobrightness to have a few options...I like the feature, but it is just a bit too dim for me.
Click to expand...
Click to collapse
My tab lost 10% battery for one hour medium usage (display on, 30% brightness, reading mainly). Dose it mean I have a battery issue here?
raymentchen said:
My tab lost 10% battery for one hour medium usage (display on, 30% brightness, reading mainly). Dose it mean I have a battery issue here?
Click to expand...
Click to collapse
no. it just depends on what your doing. Wifi signal strength, Cell radio strength. the position of the moon and sun, etc.
BTW, battery life does not decrease linearly. so the numbers in that post are ridiculous.
the discharge curve will look something similar to this in most cases
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(red line, also note phones cut off the extreme ends of the scale with regards to voltage to promote cell life)
it takes a few days for the battery (more specifically the charging circuitry) to get into a 'groove' when it comes to properly charging the battery and displaying the correct percentage.
if you want to know more about the Batteries in our phones and Tablets look at RCcar and RC plane sites. they use the same batteries as phones do so pretty much everything you learn there will apply here (except our phones don't draw 20+amps! )
http://www.fmadirect.com/lipo_handbook/fma_lipo_handbook_section2.htm
Mine can easily last and day and a half, very impressed with the battery
crazy talk said:
no. it just depends on what your doing. Wifi signal strength, Cell radio strength. the position of the moon and sun, etc.
BTW, battery life does not decrease linearly. so the numbers in that post are ridiculous.
the discharge curve will look something similar to this in most cases
(red line, also note phones cut off the extreme ends of the scale with regards to voltage to promote cell life)
it takes a few days for the battery (more specifically the charging circuitry) to get into a 'groove' when it comes to properly charging the battery and displaying the correct percentage.
if you want to know more about the Batteries in our phones and Tablets look at RCcar and RC plane sites. they use the same batteries as phones do so pretty much everything you learn there will apply here (except our phones don't draw 20+amps! )
http://www.fmadirect.com/lipo_handbook/fma_lipo_handbook_section2.htm
Click to expand...
Click to collapse
Well, I understand you saying here. But 10% (90% to 80%) per hour for reading ebook only is far away from having a good battery at 4000mah. I will give it a few more days to check.
calin75 said:
Tomorrow I will be flying back home. I'll be in the air for about 6 hours. I have 2 movies to watch, plus I'll be playing games and will listen to music. I am planning not to charge my tab until I get home. Let's see how it goes. I will update.
Click to expand...
Click to collapse
Well? How did that go?
Sent from my GT-P1000 using XDA App
raymentchen said:
Well, I understand you saying here. But 10% (90% to 80%) per hour for reading ebook only is far away from having a good battery at 4000mah. I will give it a few more days to check.
Click to expand...
Click to collapse
That's 10 hours at that usage, give or take, and right around what I'm seeing, 10% per hour of actual usage as an ebook, about 2-5% per hour if it's just sitting there connected, and about 15-20%/hour with heavy surfing or game playing.
I expect if I'm careful and keep the connectivity to a bare minimum, I can stretch 12 hours out of it when travelling.
Oh, and everyone...let the battery run down to zero at least once, preferably twice. We're talking total discharge to the point the phone turns itself off, then charge to 100%. This doesn't hurt or help the battery, but it does help make the actual battery monitoring more accurate.
honestly im not too impressed with the battery. i think the standby time sucks too. the iPad doesnt do a lot of things right, but the one thing it seems to do is to last for days. i realize the battery is close to twice as big but i was just use to that. i mean sure i dont use my ipad anymore, but it seems to last forever. anway, when i first got my tab, i managed to drain it in less than 6 hours. that was right out of the box (so it proly wasnt full all the way, but close to it). i was mad when that happened. that was with the brightness on auto and everything turned off except wifi. i could be just expecting too much. i thought conditioning the battery would be good for it. so i let it die all the way and recharged it to full. today, i wouldnt say i used the tablet like i usually would (i am a HEAVY user) and its been less than 12 hours and its already at 21%. this time it was running on 3G and brightness on low (not all the way, but about 30% or so). i dont even set the brightness to the highest cuz its too bright, auto seems to work the best. maybe im just being a tough critic. i mean my nexus only lasts like 5 hours now a days cuz i just use it too much. but im so use to just picking up another battery and moving along.
been having a good battery life after draining the battery to 3% twice then charging it to full again and now it almost last me 2 days better than my old nexus one using it primarily for comic book reading and bluetooth stereo music almost 6hrs. per day and a little gaming of angry birds and a little video and youtube + browsing calling and texting really don't like games too much
@croak
i've read a forum sometime ago that it's bad to drain li-ion to 0% so i think its better to drain it to near zero before charging again as i've read it may damage the cells if you drain it to 0%
how often should we condition the battery? (let it drain near 0 and charge up)
geogetski666 said:
@croak
i've read a forum sometime ago that it's bad to drain li-ion to 0% so i think its better to drain it to near zero before charging again as i've read it may damage the cells if you drain it to 0%
Click to expand...
Click to collapse
Doesn't hurt a lithium ion battery much at all, it's just another charge cycle.
But if you don't go down to the point that the device shuts off at least once, your battery meter can and often will be off by a good bit. There's never any confirmation. When yours was reading 3%, it might have actually been 8%, or it may have been 1% or less, but until you zero it out, you'll never know, and neither will the device. It'll still know when it's at 100%, but any reading below that can be inaccurate.
And keep in mind, this is NOT zero charge, it is not completely drained (the device does the auto-shutdown specifically to AVOID a complete drain).
ayman07 said:
how often should we condition the battery? (let it drain near 0 and charge up)
Click to expand...
Click to collapse
Lithium Ion batteries don't need to be conditioned. But if you want to calibrate the battery meter, you'll need to do it at least once.
Using my Tab as a 3rd device, with my 1st being a HTC Evo and my 2nd being a Motorola i890, i am very impressed with the battery. Even treating my 1st and 2nd devices as red-headed step children and my Tab being in my hands more then them, my battery is yet to go below 50% in a day, the week i have had it. Even with checking 7 different email accounts every 5 min. Also, my Tab is on Wifi a majority of the day, which i would think puts more of a drain on the battery.
i was a little worried when i found out that the battery was not accessable to be able to swap it out at some point of the day. I have (6) batteries for my Evo, 2 red and 4 blacks. Before my tab, if my evo didnt touch a charger during the day, i would use atleast 4 of those batteries during the day. Yea, the size difference between the Evo and Tab battery is different, so i figured i wouldnt need 5 more Tab batteries, but atleast 1 or 2 extra.
My only complaint with regards to Power/Charging is the length of the USB Charge/Data cable. It is super short. i bought a 6ft extention @ Staples for about $5!
The fresh Tab battery is only spoiling us and will get worse as time goes by. I have been looking for other options in the mean time. Here are a few options i found:
ZAGGsparq 4000 mAh $90 @ fommy
Mophie - Juice Pack Powerstation 3600 mAh $99 @ BestBuy
ClearMax External Battery Pack 5000 mAh $39 @ eBay (questionable)
eGear UB-181 1800 mAh $19 @ eBay
eGear S220 (3-way charge: Solar,ac&usb) 2200 mAh $39 @ eBay
Yoobao YB-602 Power Bank (White or Black) 4800mAh $49 @ eBay
Personally, i think i am going with the Yoobao or Mophie or ZAGG.
***EDIT***
the ZAGGsparq is 6000 mAh, NOT 4000 like i stated above...
Yoobao has only 800 mA of output, too few !
Sent from my GT-P1000 using XDA App
The ZAGG has 2 x 1000 mAh. i wonder what the output is @ 1? I doubt very much that it is 1 x 2000 mAh...
Im impress with the batterry , way much better than my Ipad that I just sold ...
Many of you have read byrong's article on actual battery charge.
http://forum.xda-developers.com/showthread.php?t=871051
He discusses the creep down from 100% to 90% overnight; as well as bump charging.
I am offering a solution that will give you 100% (or over 100% if you so choose) every night without any effort after initial setup.
Lets first look at the charger:
Output:
5v
1000 mAh
So every hour, your charger could potentially flow 1000 mA into your battery, right? There's actually two contingencies:
How much can the battery pull, and the roll-off at the peak of the charge.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to byrong's data, the last 10% charge rate rolls from 650 to 100mah in 45 minutes almost linearly. Prior to this roll-off, we are seeing 650 mAh pull from the battery which appears to be linear.
Ok now we can do our time calculation:
mAh of your battery: A = (1300 for stock)
Charge Rate: CR = (650)
10% roll-off: -(650-100)/(45/60) = -733 mAh/h (approx) Feel free to do the integral .1A/∫(650-733t)dt. Im just going to call it a flat +45 mins.
(A-A*.1)/CR + (45/60) = charge time in hours.
For stock, this is:
(1300 - (.1*1300))/650 + (45/60) = T (h)
T(h) = 2.55 hours. FROM ZERO CHARGE
I normally run down to about 30%. In that case... 1300*.3 = 390 -1300 = 910 mAh to charge
Run the calc again:
(910 - (.1*910))/650 + (45/60) = T (h)
T(h) (30%) = 2.01 Hours
Now what do we do with this?
Say hello to the appliance timer (you can get them at the dollar store):
http://www.amazon.com/50460-24-hour-Multi-Event-Appliance-Timer/dp/B000G1MD80
100% Charge Procedure:
Set ON 2 hours before you normally wake up.
Set OFF sometime prior to when you go to sleep.
You get:
100% charge every morning
If you oversleep, worst case scenario you end up with 90%.
BUMP Charge Procedure:
Set ON 3-4 hours before you normally wake up.
Set OFF 2 hours after that.
Set ON immediately after OFF,
Set OFF .5 hours after,
etc... until you've bumped to your desired level.
From now on just plug your phone in when you go to bed, and wake up to a 10% fresher battery every morning!
If you normally deplete your battery to a point where it will not make it until 2 hours before you wake up, consider setting your first OFF to 30 mins after you normally go to sleep.
ENJOY.
(+ Thnx if it helped you plz!)
After testing different batteries I have sort of a mini stockpile going on, so I'll be using this to bump charge my phone. Before it was just too much of a hassile to bump charge but this makes it easy
awesome, how many bumps do you normally do?
sweeeet. but question; do these appliance timers tick like a timeR? haha that would drive me insane while sleeping
jayochs said:
sweeeet. but question; do these appliance timers tick like a timeR? haha that would drive me insane while sleeping
Click to expand...
Click to collapse
nope. it will tick once when it switched from off to on etc. There are also digital ones.
Simple, ingenious and falls into that "Why didn't I think of that" category. Thanks for the tip.
Just tried this last night, worked flawlessly; woke up @99% charge
vassskk said:
Just tried this last night, worked flawlessly; woke up @99% charge
Click to expand...
Click to collapse
Yep woke up to 97% here so still some tweaking to do, but better than the 92% I normally wake up to.
UHF3 said:
Simple, ingenious and falls into that "Why didn't I think of that" category. Thanks for the tip.
Click to expand...
Click to collapse
Yes it does. Thanks for the idea!
i greatly appreciate mashing of the thnx button
I thought that bump charging was bad for the battery. Is the slight increase in initial charge worth degrading the life of the battery? Any insight on how bad this actually is for the batter?
pharpe said:
I thought that bump charging was bad for the battery. Is the slight increase in initial charge worth degrading the life of the battery? Any insight on how bad this actually is for the batter?
Click to expand...
Click to collapse
Bump charging while the phone is fully turned on has almost no affect because it doesn't truly bump charge- you're just keeping it at 100% instead of having your phone drain it down to ~90% and keeping it there. If you want to go over 100% you have to turn off Android (phone) and purely charge the battery, then if you unplug and do it again that's real bump charging.
If done regularly (with phone turned off) it can and will damage your battery degrading the overall lifespan. The benefit is you can end up with 105-115% normal battery capacity where when you turn on your phone, it will stay at 100% for hours.
But yea when I said bump charging before I meant with the phone on :s
This walkthrough assumes you have read the linked article. Definitely turn your phone off first if you are planning on doing the bumpcharge method.
Sent from my ADR6300 using XDA App
Question for the expert
vassskk said:
This walkthrough assumes you have read the linked article. Definitely turn your phone off first if you are planning on doing the bumpcharge method.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Love the linked article and this walk through. My questions are do these timers(or the one you linked on Amazon) allow for multiple settings (like 4 different on/off times) or just one time for on and one time for off?
And I'm assuming the initial method is with your phone left on, bump charge with phone turned off? Since you are definitely the expert, which method do you prefer and why?
wkupike2000 said:
Love the linked article and this walk through. My questions are do these timers(or the one you linked on Amazon) allow for multiple settings (like 4 different on/off times) or just one time for on and one time for off?
And I'm assuming the initial method is with your phone left on, bump charge with phone turned off? Since you are definitely the expert, which method do you prefer and why?
Click to expand...
Click to collapse
Almost all timers you can set an on/off time for half-hour increments- the digital ones you can probably be more specific.
Mine I set off/on 3 times right before I wake up.
Bump charging with your phone on will just keep your battery at 100%, since android by default keeps it around 90% if plugged in constantly (keeping a battery fully charged for extended periods of time is potentially damaging/ also reports of cheap batteries that are overcharged or on the charger too long exploding)
Bump charging with your phone off will overcharge your battery, this will cause some battery cells to die and lessen the amount of charge your battery can hold the next time you charge it. If you continue to do this then after 2-4+ months of bump charging, you may end up with a battery that will only bump charge as much as a normal charge used to be. This would be where you either buy a new battery or live with that fact.
+1
Byrong calls bumpchargers 'power users' that will 'buy new batteries every few months.' So it really doesnt matter that your trashing your battery if you perceive the temporary life gain to outweigh the loss of longevity.
Most timers have "multiple events." You just set them using little plastic pins so it really doesn't cost them anything to give you a bunch of pins.
I personally leave my phone on, as it is my 2nd alarm clock. I have my inital off set to 2am (about 30 mins after my usual sleep time) to bring the battery up to the optimal 40% charge it should sit at. My on is set to 6am, 2 hours before i normally wake up. I do not bump, as i am not baller' $$$$$.
vassskk said:
This walkthrough assumes you have read the linked article. Definitely turn your phone off first if you are planning on doing the bumpcharge method.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i thought if you charge you phone when its "off" you dont need to bump charge. I always charge mine at night and i will turn it on in the morning after boot i get 99% 2 min later after everything is done loading it still at 99% and i can get a whole day out of it. (stock battery) or if i run pandora for 11 hours (work 8 hours and commute 1.5 hours each way.) i will end up with 13%
Cool, Going to try tonight.
synisterwolf said:
i thought if you charge you phone when its "off" you dont need to bump charge. I always charge mine at night and i will turn it on in the morning after boot i get 99% 2 min later after everything is done loading it still at 99% and i can get a whole day out of it. (stock battery) or if i run pandora for 11 hours (work 8 hours and commute 1.5 hours each way.) i will end up with 13%
Click to expand...
Click to collapse
Well ya, charging your phone regularly with it off will get you 100%, but people like bump charging because you can overcharge the battery to 105-120%
Unless.. what you're saying is I don't need to 'bump charge' with my phone on when I can just normal charge with it off? And to that I say neh! I use mine as my main alarm clock and would like to be woken up if someone calls or texts me (most of the time anyway..)
For some or maybe even most people turning off your phone and charging might be the better choice.
I believe that even charging your phone with it off, will still allow it to creep down to 90% though yea? Those protect circuits are physically part of the battery.
Heres one:
http://datasheet.sii-ic.com/en/battery_protection/S8200A_E.pdf
My Droid Turbo 2 has been loosing its battery very rapidly lately, and has also started to overheat. I'm not sure whats going on with it or why its doing this, and I've been looking for solutions online and finally I am here, making my own thread because nothing seems to be working or related to my issue.
A lot of other users reported massive battery usage after the Android N 7.0 update, and that's where I started my research. I haven't noticed any significant battery drain after the Android N update, but after the security patch that just came through I am finally starting to see some issues.
After taking my phone off its charger (I use a wireless charging pad), within 5 minutes I was down to 97% battery. The entire day I have been watching the percentage tick down pretty rapidly. According to the battery page, I've had the screen on for 1 hour and 28 minutes and I'm at 58% battery. The screen accounts for 11%, cell standby for 6% and phone idle for 5%.
I use my phone very lightly throughout the day, I do NOT have the Facebook app or the Messenger app installed, and I cannot figure out where the battery drain is coming from. When I have the screen on, I'm usually around half brightness most of the day unless I'm in direct sunlight. When the phone is on, within 10 minutes the back starts to get pretty warm, and I can watch the battery level drop pretty rapidly. When the phone is off, its cool to the touch and holds its battery level right at the percent where I left it at.
According to the Android battery page, I have 8 hours left with 58% battery, which I don't think is accurate at all considering I can watch the level drop as I'm using it. I installed Gsam Battery monitor and I'm going to let it run throughout the day tomorrow after it charges up tonight.
I usually have the phone on the wireless charger every night and take it off around 7AM. I used to get a full days use out of the phone with plenty left over, but not anymore.
Here's the "fixes" I've done so far:
Factory reset (clean start)
Wiped cache partition from recovery
Disabled WiFi and Bluetooth scanning
Set WiFi to sleep when device sleeps
Put location settings to battery saver
Did the "reset app preferences" from the battery menu
Set the cellular preference to LTE\CDMA
Any help, or should I inquire about a replacement phone?
Those numbers seem high. Might be worth a call to LenoMoto or a trip to a store.
Also, leaving wifi on during sleep might lessen the cell stand-by.
Sent from my XT1585 using Tapatalk
FirePsych said:
Those numbers seem high. Might be worth a call to LenoMoto or a trip to a store.
Also, leaving wifi on during sleep might lessen the cell stand-by.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
I had shut that off in order to hopefully conserve battery, still no luck. No Motorola stores in my area, so I'll have to call.
Unfortunately my warranty ran out in May........I wonder if they will make in exception since its not that far out of it?
I was thinking VZW store.
Tried attaching a screenshot of my Batt screen, no wifi at the station and week cell signal.
Doesn't hurt to call.
Sent from my XT1585 using Tapatalk
FirePsych said:
I was thinking VZW store.
Tried attaching a screenshot of my Batt screen, no wifi at the station and week cell signal.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Getting on the phone with them now.
How has your battery held up for the time you have had your Turbo 2? Has it ever lasted you anywhere near the 48 hours its marketed as?
I can get 24 hours depending on usage and location. Never got 48 hours.
Generally weak cell and wifi are my biggest drains.
I have a Samsung S2 smartchwatch and the Sammy app is a bit of a drain.
Sent from my XT1585 using Tapatalk
FirePsych said:
I can get 24 hours depending on usage and location. Never got 48 hours.
Generally weak cell and wifi are my biggest drains.
I have a Samsung S2 smartchwatch and the Sammy app is a bit of a drain.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Weak cellular signal can drain the battery faster than a strong cellular signal? Never heard about that before.
FireGuy0723 said:
Weak cellular signal can drain the battery faster than a strong cellular signal? Never heard about that before.
Click to expand...
Click to collapse
Yup, radio in the phone is essentially working harder trying to pull a weak signal.
Sent from my XT1585 using Tapatalk
FirePsych said:
Yup, radio in the phone is essentially working harder trying to pull a weak signal.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
And keeping the WiFi awake during sleep can fix that?
After a lengthy conversation with Motorola, here is the diagnosis from them.
Because I have been using a wireless charger, they don't believe its been supplying the correct voltage for the phone to properly charge, and therefore wont hold a proper charge. The charger I have is a wireless one by Anker and supplys 5v at 1.0 amp compared to the Motorola Turbo charger which supplies according to the back of the plug
Standard output 5v at 1 amp
Turbo 1: 9v at 2.85 amp
Turbo 2: 12v at 2.15 amp
I'm guessing mine is the Turbo 2 (duh?)
Here is what they suggested. They want me to charge the phone using the turbo charger tonight, and install GSam battery monitor and use the phone like I normally would tomorrow. At the end of the day the Gsam battery monitor should be able to tell me if there is something system based or app based that is killing the battery.
So that's the plan for now. I completely forgot to ask them about a replacement phone since its not that far outside the factory warranty, but hopefully my issue has just been an improper charger this entire time and I haven't bothered to notice the crappy battery life up until now. I just hope the useage of a wireless charger hasn't caused any permanent damage to the phones battery.
I'll post back once I have some results tomorrow night, and I'll post up some screenshots.
I keep wifi on during sleep for that and to save data.
Interesting diagnosis. 2nd time I've heard that about wireless chargers and length of time the phone holds its charge.
Doesn't make sense to me the 2nd time either.
If the phone says its charged to 100%, then why wouldn't it be charged to 100%?
How does the rate of charge effect the rate of discharge?
I use a wireless charger at home at night and the original Moto T2 turbo charger at work at night. Never noticed a difference in rate of discharge during the day.
I've also used GSAM periodically to chase drain and haven't found it too useful without root.
Now that I think of it, I turned Moto Voice off months ago. I don't miss it much. That did cause more drain.
I also disable or uninstall any apps I don't use.
Sent from my XT1585 using Tapatalk
FirePsych said:
I keep wifi on during sleep for that and to save data.
Interesting diagnosis. 2nd time I've heard that about wireless chargers and length of time the phone holds its charge.
Doesn't make sense to me the 2nd time either.
If the phone says its charged to 100%, then why wouldn't it be charged to 100%?
How does the rate of charge effect the rate of discharge
I've also used GSAM periodically to chase drain and haven't found it too useful without root.
Now that I think of it, I turned Moto Voice off months ago. I don't miss it much. That did cause more drain.
I also disable or uninstall any apps I don't use.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
I have heard about improper chargers causing issues with phones in general, nothing specific to the Turbo 2, but I guess anythings possible. I have also heard about one of the bad side effects of wireless chargers is that they generate quite a bit of heat sometimes. Since mine is only on the wireless charger when I'm asleep I can't confirm nor deny that. I could definitely see how if you charge up a battery and it gets hot, as it cools down the capacity diminishes also (sort of similar to blasting air into an SCBA cylinder rapidly so it gets hot as hell, then when it cools you only end up with half the capacity you thought you had) so in my head I could see how that could translate over to a phone battery in some weird way.
Gsam now has a work around where you can use ADB from your computer to grant it the same permissions it needs on a non rooted phone, I just did it today and it worked.
I had a strange suspicion that Moto voice may have been a culprit, I only recently started using the hands free driving to announce texts and calls and allow you to reply by voice commands part of it since NH passed the hands free law. I shut that off today, so I will see if that makes any sort of a difference tomorrow. The only other part of the Moto features I use are the gestures (twists, chops, etc.)
Aside from that I also use the Google Smart Lock feature to keep it unlocked when I go home, but I've used that since I got the device and it hasn't caused any battery problems. I keep the location service in the battery saving mode.
I only have apps I need on my phone, and I have disabled 99% of the Verizon bloatware excluding the MyVerizon app.
FireGuy0723 said:
I have heard about improper chargers causing issues with phones in general, nothing specific to the Turbo 2, but I guess anythings possible. I have also heard about one of the bad side effects of wireless chargers is that they generate quite a bit of heat sometimes. Since mine is only on the wireless charger when I'm asleep I can't confirm nor deny that. I could definitely see how if you charge up a battery and it gets hot, as it cools down the capacity diminishes also (sort of similar to blasting air into an SCBA cylinder rapidly so it gets hot as hell, then when it cools you only end up with half the capacity you thought you had) so in my head I could see how that could translate over to a phone battery in some weird way.
Gsam now has a work around where you can use ADB from your computer to grant it the same permissions it needs on a non rooted phone, I just did it today and it worked.
I had a strange suspicion that Moto voice may have been a culprit, I only recently started using the hands free driving to announce texts and calls and allow you to reply by voice commands part of it since NH passed the hands free law. I shut that off today, so I will see if that makes any sort of a difference tomorrow. The only other part of the Moto features I use are the gestures (twists, chops, etc.)
Aside from that I also use the Google Smart Lock feature to keep it unlocked when I go home, but I've used that since I got the device and it hasn't caused any battery problems. I keep the location service in the battery saving mode.
I only have apps I need on my phone, and I have disabled 99% of the Verizon bloatware excluding the MyVerizon app.
Click to expand...
Click to collapse
Took it off Moto Turbo charger around 02:00 when we went on a call. Didn't plug it back in when we got back.
Been outside the last 2-3 hrs doing yard work and streaming Pandora. Batt at 60% and estimate of 19 hours left.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1585 using Tapatalk
Here is where my phone currently is at. Took it off the charger around 9AM and have been using it fairly light since. According to the doze menu it is going into its proper sleep mode, but it still does drain incredibly fast when I am actively using it.
A lot of the drain is coming directly from Android is and Google services. I'm not sure why.
Here is my tablet for a comparison. The tablet is an Nvidia Shield K1, which is not known for its battery life at all due to the fact its designed for gaming and performance. Its inky rated for around 4ish hours of constant game streaming and around 10 hours of standby time.
I'm up to 1 day and 3 hours with 30% remaining, which is insanely good for this thing, so the Android Doze is working. Android system and Kernel are also at the top of this list, but have far less active time.
Also, on my Droid I disabled the moto quick notification glance, thinking that was keeping of from going into doze.
FirePsych said:
Took it off Moto Turbo charger around 02:00 when we went on a call. Didn't plug it back in when we got back.
Been outside the last 2-3 hrs doing yard work and streaming Pandora. Batt at 60% and estimate of 19 hours left.
Click to expand...
Click to collapse
Another question, what is your screen on time? I'm at 63% at 1 hour of screen on time which seems like way too little to have drained so much (24% from the screen at half to 3/4 brightness.)
FireGuy0723 said:
Another question, what is your screen on time? I'm at 63% at 1 hour of screen on time which seems like way too little to have drained so much (24% from the screen at half to 3/4 brightness.)
Click to expand...
Click to collapse
2 hrs -14 minutes now, but this is several hours later and I had it sitting on the pad for about 20-30 minutes or so, my stats for the rest if the day aren't valid.
I have it around 40% with Adaptive Brightness-on.
Looked like you had twice as many wakelocks on your phone compared to your tablet.
I don't know enough about GSAM to interpret it effectively. Hopefully someone else will chime in.
Sent from my XT1585 using Tapatalk
FirePsych said:
2 hrs -14 minutes now, but this is several hours later and I had it sitting on the pad for about 20-30 minutes or so.
Click to expand...
Click to collapse
So I'm up to about 2 hours of screen time on mine with 41% remaining 12.5 hours total.
That's actually really disappointing considering everywhere else I read, people are posting anywhere upwards of 5+ hours of screen on time with between 60 and 70% of their battery remaining.
According to Gsam, 30% of my loss is through apps, the top 3 being Google play services, kernel and Android os.
Google play services and the Kerbel have both kept my phone awake for close to an hour each. can't figure out what is doing that with kernel, but Google play wakelock reports show something called
NlpCollectorWakelock as the #1 culprit at 40.3 minutes.
The Phone radio accounts for 23% of the loss as well. Im not sure if that's because of a low signal but I attached a screenshot.
It still sucks being able to watch the battery percentage drop an average of 1% every 2 minutes, since that's 44% of my loss. I posted a screenshot of that too. I usually have mine around half brightness with the adaptive on.
FireGuy0723 said:
So I'm up to about 2 hours of screen time on mine with 41% remaining 12.5 hours total.
That's actually really disappointing considering everywhere else I read, people are posting anywhere upwards of 5+ hours of screen on time with between 60 and 70% of their battery remaining.
According to Gsam, 30% of my loss is through apps, the top 3 being Google play services, kernel and Android os.
Google play services and the Kerbel have both kept my phone awake for close to an hour each. can't figure out what is doing that with kernel, but Google play wakelock reports show something called
NlpCollectorWakelock as the #1 culprit at 40.3 minutes.
The Phone radio accounts for 23% of the loss as well. Im not sure if that's because of a low signal but I attached a screenshot.
It still sucks being able to watch the battery percentage drop an average of 1% every 2 minutes, since that's 44% of my loss. I posted a screenshot of that too. I usually have mine around half brightness with the adaptive on.
Click to expand...
Click to collapse
Do a Google search for "phone radio battery drain"
Sent from my XT1585 using Tapatalk
FirePsych said:
Do a Google search for "phone radio battery drain"
Click to expand...
Click to collapse
I remember you mentioning that now,
This is what my cellular chart looks like. Perks of living in a small town.
Still don't see why that would cause things to drain super fast with the screen on, because it seems like it's standby power is holding up fine. Earlier today I locked the screen at 70%, 3 hours later checked my phone for the time and it was still at 70%.
Another interesting find, you had mentioned my tablet didn't have anywhere near the same amount of wake locks as my phone. I just checked that again and here's what I found.
Tablet: Wakelocks from NlPCollectorWakeLock - 160, keep awake time for 9m
No NLPWakelock
Phone: Wakelocks from NLPCollectorWakeLock - 837, keep awake time for 41.7m
NLPWakeLock - 3869, keep awake for 5m
Total keep awake time from google play services
Phone: 51m
Tablet: 19m
That's just google play services however. Kernel and Android System are account for way higher battery drain, but only the Kernel has a keep awake time of an hour, Android system is only 5 minutes.
Doing another factory data reset, this time I'm going to install anything on the phone at all except the necessary updates, just to rule out the possibility of a app that's killing the battery. If it still drains rapidly after this, It either has to be a bug within Android or Google Play Services or faulty hardware.
After speaking with Verizon the best they where able to offer me is a $150 replacement.