Related
I remember that someboy have already said it, but i've not found on the forum a solution.
disconnecting the charger means an immediately pass from 100% to 99%.
why this bug?
how can we solve it?
thanks
Hmmm i think you must connect charger
Sent from my GT-I9000 using Tapatalk
ilbulgaro89 said:
I remember that someboy have already said it, but i've not found on the forum a solution.
disconnecting the charger means an immediately pass from 100% to 99%.
Click to expand...
Click to collapse
This seems to be a much more common behaviour since 2.2.1 ROMs came out.
However a pattern is still to be extracted from this: for example, when i charge the phone while powered off, and then boot it, once boot is completed i was able to see 100% for 1-2 minutes even after finally unplugging the charger.
why this bug?
Click to expand...
Click to collapse
One guess is that Samsung changed "the mathematics of charging" the phone, at least while charging with phone on, and may have done something wrong with displayed charging levels, but not necessarily with battery life itself.
Another guess is that your "2.2-calibrated" battery is somehow different/seen differently from a proper "2.2.1-calibrated" battery. Could be a matter of recalibration, or a combination with the previous point.
how can we solve it?
Click to expand...
Click to collapse
At the moment is unknown.
This issue, and many others related to battery, it's currently being analyzed much more deeply in this thread.
For example, a user has just found out that 3rd party applications like Juice Plotter properly recognise 100% level even after unplugging the charger. This is interesting.
So it's still a work in progress.
It's just displaying it different. Battery meters are not accurate, that's just the way it is.
If the charger really kept your battery at 100% while it was on the charger then your battery would wear out very quickly. In reality it allows it to drop to around 90% after hitting 100%. The battery meter just stays at 100% for a bit on most phones so clueless users don't think something is wrong and wear their battery down by repeatedly forcing it to 100%.
Stop worrying over little 1 or 2% differences in battery readings, they are nowhere near accurate enough to judge such small differences.
It is interesting though, that this problem doesn't occur to me. I'm on JPY based Darky's rom v7, and the battery is reported as 100% for I don't know how long, after plugging in. I could confirm exactly how long but atm I'm testing to see how many days I can push out of the battery
Also, it doesn't seem like a problem to me. I think that maybe Samsung altered the algorithm for calculating battery level, because, pure technicly, a battery cannot house 100% while not plugged in.
Sent from my GT-I9000 using XDA App
Well they did change how they show the battery status in 2.2.1
You still has same capacity.
Think its better it show this way then 100% for 20 minutes before it moved to 99%.
**Using my own JPX kernel, z4mod, 345MB Ram and ext2 filesystem**
I came across this article recently
http://www.androidpolice.com/2010/1...bump-charging-and-inconsistent-battery-drain/
this explains things well, check it out
ilbulgaro89 said:
I remember that someboy have already said it, but i've not found on the forum a solution.
disconnecting the charger means an immediately pass from 100% to 99%.
why this bug?
how can we solve it?
thanks
Click to expand...
Click to collapse
I'm sure this is a ROM specific issue. ON JPX Rom (I think), the charge used to reduce from 100% to 97% instantaneously after removing the charger. This however, was resolved after I flashed to the newer JPY firmware.
I've only had my Xoom for a day, havent had a chance to use it much. So far there are a few minor problems, but one is really bugging me. The battery level is constantly changing from 100% to what I can only guess is the actual level. Most of the time it reads 100%, but for whatever reason sometimes it will briefly show the actual level for awhile, then back to 100%.
I did some searching and couldn't find anyone talking about this problem, any idea what it is or how to remedy it?
BoostedSR20 said:
I've only had my Xoom for a day, havent had a chance to use it much. So far there are a few minor problems, but one is really bugging me. The battery level is constantly changing from 100% to what I can only guess is the actual level. Most of the time it reads 100%, but for whatever reason sometimes it will briefly show the actual level for awhile, then back to 100%.
I did some searching and couldn't find anyone talking about this problem, any idea what it is or how to remedy it?
Click to expand...
Click to collapse
That is odd. Unplugged, it switches to a lower number then back up to 100% again? Did you install any battery apps or monitoring tools?
keitht said:
That is odd. Unplugged, it switches to a lower number then back up to 100% again? Did you install any battery apps or monitoring tools?
Click to expand...
Click to collapse
Not at first. I watched it happen for awhile then I installed a gauge to see what it would do, and it matches the stock battery meter perfectly.
Sent from my Xoom using XDA Premium App
Looks like your Xoom actually came with a magical unicorn inside that chargers it with magic dust...lol, j/k. But I wish mine had a unicorn.
I say drain the battery, recharge and see if that does anything..or just exchange it.
Been sitting here using it for awhile, and it seems to be time based. I would say 5ish minutes at 100%, then it changes to the actual % (which has been going down) then back to 100% in about 1 or 2 minutes.
I'm going to kill it, then charge it while its off and see what happens. I guess we have no way yet to delete the battery stats?
Sent from my Xoom using XDA Premium App
Killed the battery last night, charged it fully while it was off. Same problem. I guess the next step is a factory reset, then if that doesn't work its going back.
Sent from my Xoom using XDA Premium App
Factory reset didn't help either. I also noticed that the charge light isn't showing the right colors while charging, it just stays white. Guess I'm going to return this thing for another one.
The manual is incorrect re: charging colors. It is just white and only when off. It will turn green if off and fully charged, but there is no red and none of the percentage variations.
Where are you looking at the battery level? Are you keeping the little window in the lower left hand corner open?
Xatt said:
The manual is incorrect re: charging colors. It is just white and only when off. It will turn green if off and fully charged, but there is no red and none of the percentage variations.
Where are you looking at the battery level? Are you keeping the little window in the lower left hand corner open?
Click to expand...
Click to collapse
Actually just returned it, the new one is charging now, haven't turned it on.
It didn't matter where you looked at the battery level. I looked at the notification area, and the setting/status area. Every couple of minutes it would switch between 100% and actual %. Also, when it was plugged in, when it switched to 100%, it would say charged, and wouldn't charge.
Has anyone solved the "Low battery" and "immediate turn off" problem yet?
Man this is the most frustrating issue EVER.
I'm running SRF 1.1.0
I have a 3500 mAh battery.
For some Farking reason, if the battery is under 50% and I get a call. It will RANDOMLY beep LOW BATTERY and turn off, in the middle of the farking call!!!
You turn it back on and it'll have 40+ % charge left!!!
AHHHHH!!!!!
After watching the 25 how to videos, I fixed almost everything that pissed me off, but this one thing drives me bonkers!!!!
I think that's the battery. Is its a yoo-bao from china (cheapie) or a good brand from a reputable source(sedio)? I have that problem with all the cheapies I bought on ebay.
Sent from my SPH-D700 using XDA App
It's not just the battery. My stock phone and rom does it too when the battery gets to 15%. When it reboots it has 20 or 30%.
This phone should never have been released with such a serious bug.
Sent from my SPH-D700 using XDA App
For "such a serious bug" it doesn't seem like many of us have it... I can keep a call all the way to 0%...did it a few minutes ago. Have you tried calibrating the battery stats?
Sent from my SPH-D700 using XDA Premium App
Now I dont normally let my phone get down to 0% but yeah i know i've gone WAYYYYYYY past even 10% and the phone hasn't done this. Stock battery not extended.
Kcarpenter said:
For "such a serious bug" it doesn't seem like many of us have it... I can keep a call all the way to 0%...did it a few minutes ago. Have you tried calibrating the battery stats?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
it's a cheapy battery.
However, it's also a bug somewhere in some software...
If it hits 15% when u are NOT on a call, the phone doesn't shut off. It's only when you're actually talking that it does it.
I'm surprised to hear STOCK people saying it happens to them... When I had my phone stock it didn't do this. I assumed it was a ROM issue.
I would try calibrating... I believe there's an actual app in the market to do everything for you. I'm fairly certain its free, so ill post a link, but if its not, I apologize, and well get a mod to take it out.
http://db.tt/NaGV1TB
J3ff said:
I assumed it was a ROM issue.
Click to expand...
Click to collapse
I love how people assume I sprinkle magic fail dust on my ROMs.
Charge to 100% with the device off and wipe battery stats in CWM.
Key word there, "Assumed"
Kcarpenter said:
For "such a serious bug" it doesn't seem like many of us have it... I can keep a call all the way to 0%...did it a few minutes ago. Have you tried calibrating the battery stats?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yes. I've calibrated my battery. I have seen a couple threads on the issue. I have repeated the issue on several roms and modems. Happens every time i'm on a call and the battery gets to 15%. That makes it serious since it is a phone after all. What if I was talking to 911?
Sent from my SPH-D700 using XDA App
k0nane said:
I love how people assume I sprinkle magic fail dust on my ROMs.
Charge to 100% with the device off and wipe battery stats in CWM.
Click to expand...
Click to collapse
Not just YOUR rom, I've read that this is a problem on all different ROM's including the stock one!
J3ff said:
Not just YOUR rom, I've read that this is a problem on all different ROM's including the stock one!
Click to expand...
Click to collapse
Right, but you said you assumed it was a ROM issue before you found out stock users had it.
k0nane said:
Right, but you said you assumed it was a ROM issue before you found out stock users had it.
Click to expand...
Click to collapse
well even stock is a rom right?
What I'm hoping for is I can figure out what you guys are running that doesn't crash on you when the low battery beep happens.
I think this is a battery issue. I never had this problem with stock battery and it happened twice on cheap 3000 ma battery I bought. Returned the battery and got another one (same kind) and this one works fine. I think this is a manufacturing problem with cheap batteries. When you look at reviews of more expensive ones online, you never see anything about this problem.
I have found the solution! It turns out that our phones, much like a simple light bulb, just don't function when they don't have enough juice...
Since I can't modify a light bulb to magically require less power, the only solution I have found is to provide the specified power level. I have applied this same method to my phone - when the battery gets close to that magic threshold, all I do is - get ready for this - charge the phone again!
Seriously, though - everything takes power to operate, and a low battery can't put out the same current and voltage as a fully- or even half-charged battery. This isn't a bug, it's just a fact of life (with current technology, anyway). Who here complains when their almost-dead AA batteries can't power an Xbox 360 controller? Most of us just replace them with fresh ones (or charge them) and keep going.
Sent from my SPH-D700 using XDA App
styles420 said:
I have found the solution! It turns out that our phones, much like a simple light bulb, just don't function when they don't have enough juice...
Since I can't modify a light bulb to magically require less power, the only solution I have found is to provide the specified power level. I have applied this same method to my phone - when the battery gets close to that magic threshold, all I do is - get ready for this - charge the phone again!
Seriously, though - everything takes power to operate, and a low battery can't put out the same current and voltage as a fully- or even half-charged battery. This isn't a bug, it's just a fact of life (with current technology, anyway). Who here complains when their almost-dead AA batteries can't power an Xbox 360 controller? Most of us just replace them with fresh ones (or charge them) and keep going.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This! Cheap batteries are never worth the money. I bought some cheap chinese rechargeable packs for my 360 controllers... they ALWAYS show low charge even if I just charged to full. Same deal with cheap chinese cell phone batteries.
I am sure the battery calibration is way off with one of the cheapies.
styles420 said:
I have found the solution! It turns out that our phones, much like a simple light bulb, just don't function when they don't have enough juice...
Since I can't modify a light bulb to magically require less power, the only solution I have found is to provide the specified power level. I have applied this same method to my phone - when the battery gets close to that magic threshold, all I do is - get ready for this - charge the phone again!
Seriously, though - everything takes power to operate, and a low battery can't put out the same current and voltage as a fully- or even half-charged battery. This isn't a bug, it's just a fact of life (with current technology, anyway). Who here complains when their almost-dead AA batteries can't power an Xbox 360 controller? Most of us just replace them with fresh ones (or charge them) and keep going.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok Mr. Smarty pants. You are not understanding the problem. It happens with the stock battery too.
The SECOND you hit 15% while on the phone and get the battery low warning, the phone turns off, MID CALL. You turn the phone back on and it will last hours, even on the stock battery.
If it hits 15% without being on a call, it does not shut down.
That is the real problem here.
This has happened to me once , what could be the cause ? Defective phone or software?
J3ff said:
Ok Mr. Smarty pants. You are not understanding the problem. It happens with the stock battery too.
The SECOND you hit 15% while on the phone and get the battery low warning, the phone turns off, MID CALL.
If it hits 15% without being on a call, it does not shut down.
That is the real problem here.
Click to expand...
Click to collapse
You mean just like a 360 controller can have enough juice to turn on, but not enough to actually play? Or how a flashlight will be too dim to be worth it when the batteries get low?
Would it be better if the battery ran like a champ right up to the second that it shuts off without warning? That would fix your problem - no notification when the battery is low (the sudden shut off can't be avoided until we find an unlimited energy source small enough to fit in our phones)
Your expectations are unrealistic. Just sayin'...
Sent from my SPH-D700 using XDA App
J3ff, it's likely the cheap battery. Here's why:
Charge level is a simple linear voltage function. Our phones consider 4.2V to be full charge (100%), and empty to be around 3.6V (0%). The voltage drops roughly linearly between these two values as charge is consumed.
The kicker is this: The voltage seen at the battery terminals is also affected by the interaction between the internal resistance of the battery and the instantaneous load, or current draw. For electronics buffs, this is the classic V=IR, and what happens is that the voltage on the battery will drop by IR in addition to it's unloaded voltage level due to whatever the stored charge state is.
Good quality batteries have a very low internal resistance, and will not drop much voltage due to an increased load. Crappy batteries are just the opposite, and even though they do carry the charge storage (most of the time) advertised, they are only suitable for low load applications.
What's happening is you have a battery with a horribly high internal R. When you make a phone call, the load increases A LOT -- transmit power goes way up. This if why phones get hot when talking on them -- they really suck the juice.
As a consequence, because of the high resistance, voltage from the battery takes a nosedive. At an "idle" reading of 50% (3.9V, thereabouts) you're probably dropping more than 0.3V when the load goes up during a call, the phone panics, and shuts down to protect the battery (LiIon doesn't like to be discharged below 3.3V, and can be damaged).
When you reboot, the high load is gone, so the voltage shows higher again, reflecting the fact that there is truly still plenty of charge stored and available. The battery simply can't handle gulps, but only slow sipping.
High internal R is one of the most common reject reasons from mfgs, and those batts are sold on the cheap to dealers and distributors in a secondary market. Honest ones then resell into appropriate application spaces where low-current is all that is needed. Most, however, are not that scrupulous, and sell right back to the same market, leaving behind puzzled and unhappy customers.
Sent from my mind using telepathitalk
The topic pretty much explains it. I've been using different modified stock roms and now I'm on the latest nightly of CM7, and I keep having this issue. After a reboot at around 50%, the battery drops to 15%. The weird part is that while I continue to use the phone, it slowly rises back up to sometimes 30% and then starts going back down. I've always cleared battery stats when flashing and calibrated (which I believe is unnecessary), but I don't know if this is a problem with the battery, the phone, or if anyone else is having the same issue?
Attached is a screenshot of battery usage. You can see I never actually charged the phone.
Sent from my GT-I9100 using Tapatalk
I have exactly the same issue.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
[email protected] looks like a bow and arrow..
anyway guys, you need to recalibrate your battery, its not being read accuracy.
download BatteryCalibration from the market, charge your phone till 100% (not just 100% but when it beeps, that its truely at 100%), then use BatteryCalibration to calibrate your battery, and then drain it to 0.. (crank full brightness, turn on LED flashlight, blast internet radio, whatever makes it drain faster to get this part overwith), then recharge it to max.
so;
charge to full 100%
while still plugged in, run BatteryCalibration
discharge to 0%
recharge to 100%
battery successfully calibrated, you will now have an accurate reading
I had exactly the same issue on 3 different custom roms....finally resolved by going bck to stock rom
mgxplyr said:
The topic pretty much explains it. I've been using different modified stock roms and now I'm on the latest nightly of CM7, and I keep having this issue. After a reboot at around 50%, the battery drops to 15%. The weird part is that while I continue to use the phone, it slowly rises back up to sometimes 30% and then starts going back down. I've always cleared battery stats when flashing and calibrated (which I believe is unnecessary), but I don't know if this is a problem with the battery, the phone, or if anyone else is having the same issue?
Attached is a screenshot of battery usage. You can see I never actually charged the phone.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sent from my GT-I9100 using XDA App
soraxd said:
[email protected] looks like a bow and arrow..
anyway guys, you need to recalibrate your battery, its not being read accuracy.
download BatteryCalibration from the market, charge your phone till 100% (not just 100% but when it beeps, that its truely at 100%), then use BatteryCalibration to calibrate your battery, and then drain it to 0.. (crank full brightness, turn on LED flashlight, blast internet radio, whatever makes it drain faster to get this part overwith), then recharge it to max.
so;
charge to full 100%
while still plugged in, run BatteryCalibration
discharge to 0%
recharge to 100%
battery successfully calibrated, you will now have an accurate reading
Click to expand...
Click to collapse
I'll try this one more time and report back.
mgxplyr said:
I'll try this one more time and report back.
Click to expand...
Click to collapse
Sorry guys, but your method with BatteryCalibration is useless ....
If you wanna do a correct calibration, look at here http://forum.xda-developers.com/showthread.php?t=1312273
Cheers
Put back the battery on the right side.
8. Turn on the phone.
9. Pray the Battery god
And that post is just nonsense based on the old battery bump method .
jje
mgxplyr said:
The topic pretty much explains it. I've been using different modified stock roms and now I'm on the latest nightly of CM7, and I keep having this issue. After a reboot at around 50%, the battery drops to 15%. The weird part is that while I continue to use the phone, it slowly rises back up to sometimes 30% and then starts going back down. I've always cleared battery stats when flashing and calibrated (which I believe is unnecessary), but I don't know if this is a problem with the battery, the phone, or if anyone else is having the same issue?
Attached is a screenshot of battery usage. You can see I never actually charged the phone.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
i have the same problem when i use custom roms.
i have been using pure stock rom by wannam but rooted for the past week with 12 hours aday syncing and surfing the net and plenty of voice calls via viber and my battery lasts at least 16 to 18 hours.
right now i am using odexed KL3 Kernel KL2Base KL1modem 2.3.6 and it is absolutely amazing interms of battery life and performance.
http://forum.xda-developers.com/showthread.php?t=1292825
http://www.multiupload.com/06I066U6S8
i have gotten rid of all samsung craps through titanium backup. i only have samsung apps application cuz of some paid apps which are for free such as tapatalk and many more on samsung app store.
my free memory is 97mb (original rom free memory is only 27mb)
i dont use any task killers i use 1Tapcleaner pro.
JJEgan said:
Put back the battery on the right side.
8. Turn on the phone.
9. Pray the Battery god
And that post is just nonsense based on the old battery bump method .
jje
Click to expand...
Click to collapse
Maybe, you wanna share a better way to all of us ?
Are you using speeded kernel. If you are then it is because logging and debugging is off.
Sent from my GT-I9100
Completely stock phone never rooted.
Same problem.
Just sayin'
Sent from my GT-I9100 using XDA App
Got the same here, very strange, on CM7
Sent from my GT-I9100 using XDA App
This thing only happens on CM7 for me. It had 40% before reboot and like 15% after. However mine only increased to about 17% then started dropping as usual. This never happened on any stock ROMs I've tried(stock, not themed/modded stock).
Sent from my GT-I9100 using xda premium
did you
did you rsolve the problem ? how? I have the same problem and I tried more stock roms ... I don't know what tot do ....
Its nothing to do with calibration etc, its just how the fuel gauge chip works, it learns and more accurately reports usage over time. For example, if you reboot and (I can't remember the actual voltages for the S2) you have 1200mV, the chip goes, "ah, that is 15% battery." Then as you use it more, it relearns its settings and goes "aaah, my mistake 1200mV is really 30% battery. I'll display that instead."
Its been covered frequently that "calibrating" the battery of the S2 in any way but actually using it, is next to useless.
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
Also just noticed this thread is a year old, but hopefully it will help the poster above.
Sent from my GT-I9100 using xda app-developers app
I'm having this problem too, what did you all do besides get new phones?
Got the same here, after update stock jellybean
Had this problem, when my S2 was half a year old.
I got the original Extended Battery and that solved this issue completely.
The replacement Battery has held up since 2013
soraxd said:
[email protected] looks like a bow and arrow..
anyway guys, you need to recalibrate your battery, its not being read accuracy.
download BatteryCalibration from the market, charge your phone till 100% (not just 100% but when it beeps, that its truely at 100%), then use BatteryCalibration to calibrate your battery, and then drain it to 0.. (crank full brightness, turn on LED flashlight, blast internet radio, whatever makes it drain faster to get this part overwith), then recharge it to max.
so;
charge to full 100%
while still plugged in, run BatteryCalibration
discharge to 0%
recharge to 100%
battery successfully calibrated, you will now have an accurate reading
Click to expand...
Click to collapse
did it but it still there... phone flicks and goes off at or below 40% wont turn on again:crying:
same here and I got the 2000 mAh samsung battery back in the days but now it happens with both of them also when my phone shuts off the screen brightness start flashing weirdly
My stock unrooted 16gb n7 received the 4.2 update this morning, all has been fine until this evening when it needed charge.
It often gets plugged into a htc phone charger, which has worked fine since i bought the tab a few months ago until today, its a 1amp charger so it takes ages to charge, but thats fine as it is plugged in until the morning normally.
So i plugin as normal, and come back after setting up google play music on my desktop pc, and i see the unit rebooting showing the glowing X. The screen goes blank and is unresponsive, eventually the google logo appears and it boots normally (its still plugged in btw), after unlocking the screen goes mental after maybe 5 seconds with random noise on it, then goes black.
So i unplug and use the genuine asus charger and cable, it does the same twice over, reboot, freeze, long wait then reboot.
I have now left it on charge using the asus charger and it seems to be ok now
Have google changed some charging requirements? Anyone else seen this?
Sent from my Nexus 7 using xda premium
Not sure, but my nexus 7 on Android 4.2 charges like 35% slower than did with 4.1.2..... what the hell did they do??
Funny you mention that, i might agree with you there
The N7 seems fine today, i did make a couple of videos of it misbehaving last night, watching back my circle battery widget app jumps from 16% to 0% battery just before it goes blank, indicating it might have simply run flat but thought it still had 16% battery?
Wonder if they have changed the battery meter scaling?
I think i will run it flat and check it shuts down properly like it used to
Sent from my Nexus 7 using xda premium
dexterslab said:
Funny you mention that, i might agree with you there
The N7 seems fine today, i did make a couple of videos of it misbehaving last night, watching back my circle battery widget app jumps from 16% to 0% battery just before it goes blank, indicating it might have simply run flat but thought it still had 16% battery?
Wonder if they have changed the battery meter scaling?
I think i will run it flat and check it shuts down properly like it used to
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi dexterslab,
On a side note when you update to 4.2 were you already rooted and did you have superSU version0.98 installed? I have been reading other posts in this forum that folks have been rooted, superSU installed and the update has completely crashed their N7. ANy info would be greatly appreciated.
Thanks,
JBIRD
Its still as stock, locked and unrooted
Sent from my Nexus 7 using xda premium
I've noticed slower charging since the 4.2 update too - did a quick Google search and landed here. Using the same genuine Asus charger and generic cable that I did before the update, and I would agree with the roughly 35% slower estimate.
dexterslab said:
Its still as stock, locked and unrooted
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks, did you do a factory reset prior to updating?
No, update received ota so just installed it
Sent from my Nexus 7 using xda premium
Been working and charging fine since, guess it was just a random glitch!?
Sent from my Nexus 7 using xda premium
scubastevegk said:
I've noticed slower charging since the 4.2 update too - did a quick Google search and landed here. Using the same genuine Asus charger and generic cable that I did before the update, and I would agree with the roughly 35% slower estimate.
Click to expand...
Click to collapse
Are you using the new Daydream feature (you can find it in the display settings). If yes this may be the cause of slower charging, because it doesn't turn of the display.
Daydream is off.
Tbh, now it seems to have settled down i think maybe charging time is pretty much the same as it was. The whole debacle seems to be a complete non-event in hindsight!
Sent from my Nexus 7 using xda premium
Guhrasoh said:
Are you using the new Daydream feature (you can find it in the display settings). If yes this may be the cause of slower charging, because it doesn't turn of the display.
Click to expand...
Click to collapse
No Daydream for me.
Mine is stock and unrooted. After the update I'm having the same charging issues. Incredibly slower charging. It's been plugged in for 6 hours now and it's at 80%. I did play a bit of pandora for about 30minutes but it was still plugged in. Other than that I haven't touched it other than to check the level. I turned daydream. Let's see if that help though I doubt it.
i think when you install the 4.2 update it does a battery stat wipe. this could produce the battery jumping from 16%-0% i reset the battery stats on my gt-i9003 the other day charged, its went from 100% - 40% instantly after about 2 charge cycles it should go back to normal.
it would also explain the battery seeming to take longer to charge, its just the voltage counter resetting itself. it might even in some cases charge faster....then run out quicker....
charge- discharge about 3 times and it should go back to norm.:good:
example :
dexterslab said:
Tbh, now it seems to have settled down i think maybe charging time is pretty much the same as it was. The whole debacle seems to be a complete non-event in hindsight!
Click to expand...
Click to collapse
still bro i wouldnt use any charger expect the asus one, phones maybe i mean i always use other peoples chargers,or pickup the wrong end from my snake-pit of charger cables hanging under my tv unit. but for tabs....nah lol
chismay said:
i think when you install the 4.2 update it does a battery stat wipe. this could produce the battery jumping from 16%-0% i reset the battery stats on my gt-i9003 the other day charged, its went from 100% - 40% instantly after about 2 charge cycles it should go back to normal.
it would also explain the battery seeming to take longer to charge, its just the voltage counter resetting itself. it might even in some cases charge faster....then run out quicker....
charge- discharge about 3 times and it should go back to norm.:good:
example :
still bro i wouldnt use any charger expect the asus one, phones maybe i mean i always use other peoples chargers,or pickup the wrong end from my snake-pit of charger cables hanging under my tv unit. but for tabs....nah lol
Click to expand...
Click to collapse
Agreed, phones seem to be more universally compatible when it comes to charges.
Charge a tab with the wrong charger n you'll make up with a melted Nexus 7
i think its a part of certain regulations now that mobile phones needs to have an internal capacitor/transformer to make sure of this problem, as people usually run out of charge on the go and use other chargers as long as the connector fits and it begins charging, most of us including me are probably guilty of plugging a charger in, seeing its charging and thinking *yay it works fine* walking away and not really understanding what slow-fast damage can be caused to the device/battery.
for tabs 30% i would say dont have this feature:good: especially the Chinese ones. ? <no racial offence intended> you guys know what im on about.
My Nexus 7 worked great before upgrading to 4.2. Now it can't charge while I'm using it... The battery just goes up and down as I'm surfing the web, if I load a lot of pages, it goes down, if I read a lot, it goes up... But if I try to watch a floating video while surfing the web, it just goes down... There is definitely a problem! Here is a screenshot... I'm using the original charger and cable...
chismay said:
i think when you install the 4.2 update it does a battery stat wipe. this could produce the battery jumping from 16%-0% i reset the battery stats on my gt-i9003 the other day charged, its went from 100% - 40% instantly after about 2 charge cycles it should go back to normal.
it would also explain the battery seeming to take longer to charge, its just the voltage counter resetting itself. it might even in some cases charge faster....then run out quicker....
charge- discharge about 3 times and it should go back to norm.:good:
example :
still bro i wouldnt use any charger expect the asus one, phones maybe i mean i always use other peoples chargers,or pickup the wrong end from my snake-pit of charger cables hanging under my tv unit. but for tabs....nah lol
Click to expand...
Click to collapse
Wiping battery stats does absolutely nothing that affects reported battery charge level. That wives' tale was long ago debunked by a member of Google's Android team. The one and only thing you are wiping is a list of apps that have operated on battery since unplugging after the last complete charge. This in no way, shape, or form affects reported charge or has any effect on battery life whatsoever.
Sent from my Galaxy Nexus using Tapatalk 2
najaboy said:
Wiping battery stats does absolutely nothing that affects reported battery charge level. That wives' tale was long ago debunked by a member of Google's Android team. The one and only thing you are wiping is a list of apps that have operated on battery since unplugging after the last complete charge. This in no way, shape, or form affects reported charge or has any effect on battery life whatsoever.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
LIKE I AM SAYING MY FRIEND,
actually the battery stats ARE WHAT THE GOOGLE DEV SAID is what gives you accurate readings it doesn't increase your battery life . i never said that it will, so please don't police me,.
heres the comment
This file [batterystats.bin] is used to maintain, across reboots, low-level data about the kinds of operations the device and your apps are doing between battery changes. That is, it is solely used to compute the blame for battery usage shown in the "Battery Use" UI in settings. That is, it has deeply significant things like "app X held a wake lock for 2 minutes" and "the screen was on at 60% brightness for 10 minutes."
when you flash a new firmware, the system must calibrate as there are no previous readings from the bstat file right?.,these are the readings that help the system produce the reported battery charge. its what it does to give you those readings, i was guiding the above member to wait and run a few cycles for readings to be more accurate i never said his battery was dead.
kinda why pretty much EVERYONE mentions after flashing a new firmware on most device they have a few days of battery "up-n-downs"= counter reset/data collection/last battstat file wiped.
cheers:good:
chismay said:
LIKE I AM SAYING MY FRIEND,
actually the battery stats ARE WHAT THE GOOGLE DEV SAID is what gives you accurate readings it doesn't increase your battery life . i never said that it will, so please don't police me,.
heres the comment
This file [batterystats.bin] is used to maintain, across reboots, low-level data about the kinds of operations the device and your apps are doing between battery changes. That is, it is solely used to compute the blame for battery usage shown in the "Battery Use" UI in settings. That is, it has deeply significant things like "app X held a wake lock for 2 minutes" and "the screen was on at 60% brightness for 10 minutes."
when you flash a new firmware, the system must calibrate as there are no previous readings from the bstat file right?.,these are the readings that help the system produce the reported battery charge. its what it does to give you those readings, i was guiding the above member to wait and run a few cycles for readings to be more accurate i never said his battery was dead.
kinda why pretty much EVERYONE mentions after flashing a new firmware on most device they have a few days of battery "up-n-downs"= counter reset/data collection/last battstat file wiped.
cheers:good:
Click to expand...
Click to collapse
Read her entire dissertation, and you will see that it does not pertain to reported charge level. She explicitly states that batterystats.bin has no bearing on reported charge level. Interesting that you left out the portions of her post immediately prior to, and immediately following, the part of her post that you quoted... you know, the ones where she states, and then restates, that nothing in batterystats.bin affects the reported charge level? Also, the reason the battery seems more stable a few days after flashing new firmware is the kernel itself settling, not the OS.
Sent from my Nexus 7 using Tapatalk 2