Database Users

Battery 100% fix by kernal

This kernal will make the nexus s charge to 100% with the screen off, thanks to peter alfonso, I have tried it and it works great with good battery life.
www.peteralfonso.com/2011/11/download-nexus-s-263514-kernel-update.html
Sent from my Nexus S using XDA App

It's not a fix, number is just cosmetic your nexus will still charge to 96%... It's just a tweak

dinuweera said:
This kernal will make the nexus s charge to 100% with the screen off, thanks to peter alfonso, I have tried it and it works great with good battery life.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If I'm not mistaken, the "charge to something about 96%" is a safety measure to increase the lifetime of the battery? Why would one want to push those last few % and lower the lifetime?

dinuweera said:
This kernal will make the nexus s charge to 100% with the screen off, thanks to peter alfonso, I have tried it and it works great with good battery life.
www.peteralfonso.com/2011/11/download-nexus-s-263514-kernel-update.html
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
most the other kernels include it now also. and it is just a cosmetic fix.

I just don't understand if it's such a safety features why does NO other phone do it?
Sent from my Nexus S using xda premium

Other phones should do it... Just like why you shouldn't keep your laptop constantly plugged in... It'll kill your battery a lot faster
Sent from my Nexus S 4G using xda premium

Battery works great but first error is NFC not working ...

lilgrass71 said:
Other phones should do it... Just like why you shouldn't keep your laptop constantly plugged in... It'll kill your battery a lot faster
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
All Android phones have this "charging safety feature".
Unless you plan on using the same battery and phone for the next ten years, you are highly unlikely to notice any degradation in the battery health. I have been using one of my OEM Samsung Nexus batteries for 2 years now (it is the same battery that came with my Samsung Moment and used on an Instinct HD as well). This particular battery has been topped off on all three phones and external chargers probably 100's of times. It still charges to a full 4.19v and stays full even sitting on my nightstand for a week or two.
The "Safety mechanism" in the charging code that has been brought up over and over again is included in all Android phones. It is nothing new. The problem is that in other devices, the battery meter reads 100% when it reaches the safe full level at the batteries temperature (usually between 4.188 and 4.190). The Nexus S has an error in the driver code that causes the meter to read inaccurately(95-98%) even when the voltage reaches 4.19. I don't believe Google did this intentionally, as it would cause many misinformed people to constantly bump charge their batteries in hopes of reaching 100%. It would have made more sense to have the meter read 100% at the safe full level.
In any event, the fix for the issue is here, and already being applied to some Nexus S kernels, including the one in the OP. It's not just "cosmetic".
https://github.com/pawitp/android_ke...cb36c33c2c3234

Bought my nexus s day one and it charges to 93%. I've noticed turning wifi on after plugging it in to charge does boost it to 98. But I always leave wifi off overnight. Don't want pesky google plus emails waking me up lol.
Overall, after nearly a year of use I'm happy with the battery life of my phone. You get used to how far you can push the phone in daily use and which settings to use.
Sent from my Nexus S

N7 JB 4.2 strange charging issue

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

Coming from Galaxy Note I to Note 2...battery life!!

I am astounded as to how much better the battery life is.
With my usage i was lucky to get 6hrs on a full charge. Well.... first charge of brand new note 2 and im on 60% still and its been on battery for over 13hrs up to yet!!!!

It's great isnt it... I thought the same but in my case I came from an S3. Note 2 really is an amazing phone.
Sent from my GT-N7100 using xda premium

It will probably be on 40% by the time i get in bed. Do you think its better to fully charge it again or just let it run down as i will be back from work earlier tomorrow
Matt

For the first charge I let it run down to 5%, then after that I just do whatevers needed.
Its personal pref tho, some people will say you need to, others say it's not necessary.
Sent from my GT-N7100 using xda premium

If i let it go below 5% and it ran out would that be bad?

I dont think its gonna hurt, its just good practice...something I remember reading once.
Sent from my GT-N7100 using xda premium

princepilot said:
If i let it go below 5% and it ran out would that be bad?
Click to expand...
Click to collapse
Just don't let it run out. The first few times you use the phone, you should do a full cycle charge.
Let it run down to 5% or less and then charge it to 100%

initial_k said:
Just don't let it run out. The first few times you use the phone, you should do a full cycle charge.
Let it run down to 5% or less and then charge it to 100%
Click to expand...
Click to collapse
So when I get mine should I fully charge it and let it run out fully a few times?
Andy

http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
No you don't need to fully run down the battery. It is actually a bad practice on lithium based batteries.

MohJee said:
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
No you don't need to fully run down the battery. It is actually a bad practice on lithium based batteries.
Click to expand...
Click to collapse
when they say "fully run down", don't they mean run down till literally zero? on advanced phones like ours, you'll never get a chance to fully run down the phone because it'll shut down way before that happens, unless you keep it turned off and sitting there for a couple of weeks, which should almost never happen to anyone.
so i think you can run down the phone, at least till it turns off by itself, and then charge again till full.

The battery life is beyond words,I never get to drain it more than 30% ,I just charge by bed time,dnt bother about battery calibration unless u change ur rom
Sent from my GT-N7100 using xda premium

battery question

Today i accidentally let my battery get down to 1 percent and my phone shut off but then i plugged it in charger and letting it fully charge. Is this bad for the battery, or did it still have some charge left after it shut down at 1 percent for battery safety.

I let my battery die out all the way for my s3 and s4. I have never really noticed a problem. If you do run into battery problems though, you can always just buy a replacement one for 10-15 bucks off eBay. One of the luxuries of having a Samsung with removeable battery!!
Sent from my SGH-I337M using xda app-developers app

It's generally not good to do on a regular basis, but every now and then shouldn't really hurt it. And, like mentioned, batteries are pretty cheap.

this was the first time i did it by accident but if the phone shut off at 1 percent doesnt mean it was fully drained right?

lilg754367 said:
this was the first time i did it by accident but if the phone shut off at 1 percent doesnt mean it was fully drained right?
Click to expand...
Click to collapse
As drained as it could get with the phone still operating. I'm sure it still had a little juice just not enough to power the screen.

so you think i have nothing to worry about or will see anything different?

Nothing to worry about at all!
Sent from my SGH-I337M using xda app-developers app

pjcordi said:
Nothing to worry about at all!
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
X2

Lithium ion battery can not be charged if it falls below certain charge level. To avoid this, your phone reports zero percent well above the critical charge level. So, even with 1%, you are well away from causing serious damage to the battery. If you do it repeatedly, it will reduce the life of your battery though.
Sent from my SGH-I337 using Tapatalk

[Q] Fault battery indicator [SOLVED]

Hello, :fingers-crossed:
i'm having a lot of troubles with the battery of my Nexus 4. I'll try to explain this strange situation...
Few days ago i noticed a ridicoulous battery drain while i was, as usually, listening to some music with my bluetooth A2DP headset Jabra HALO2. It was something like 1% every less then 1 minute. At first i thought it was due to a recently upgrade to CM10.2M1 (which is a monthly build of Cyanogenmod on 4.3) or due to a 5 minutes fast charge from the 2A charger of Nexus 10 that could have "upset" the battery.
At first i started focusing on the software side problem; i tried CM10.2RC1, CM10.2, stock 4.3, stock 4.4 and now CM11M1, and, while doing all of those wipes, i noticed that not only the discharge was insanely fast, but even the charge! The graph on the setting panel is almost vertical while cahrging, like 3% to 40% in 25 minutes.
But that's not all, sometimes, after rebooting, i noticed a battery level different from the previous boot, so i decided to wait a full discharge and then fully recharge it. I have waited the 0% (not so much time ) putting the screen always on and the LED flash too, then, i tried few times to turn it on and every time, after the boot screen disappeared it immediately started to turning off due to 0% battery.
Moreover, for being certain, i tried to turn it on in recovery and wait how much time it would take to consume the lasting charge on the battery. Surprisingly, after 30 minutes it was still there! I tried a reboot into system, showing me a 10% remaining battery (WTF), which discharged to 0% in like 3 minutes. Now i'm waiting the whole night the real discharge in recovery with screen always on, hoping that a full recharge could fix it. I would like to evidence that the phone do not overheat during both charghe and discharge, so i guess the battery itself may be ok.
I'm still not sure if it's a software problem, and i'm worrid if it could be an hardware related issue. Maybe it could have been the charge from the 2A adapter.
I really don't know what to do next. Someone knows how to help me?
Here 2 screenshoots, I wasn't able to upload it normally so here the links:
https://drive.google.com/file/d/0ByucdM-SwPNnMlFUOGU4bXkzaGs/edit?usp=sharing
https://drive.google.com/file/d/0ByucdM-SwPNnZEtXczNuTXhiMGc/edit?usp=sharing
EDIT:
I've done a full discharge until even the full hybernation has been shutted down, but seems that it hasn't solved anything. I've also noticed that in the battery stat is missing the display consumption (WTF?!?). Maybe it's a CM11M1 bug, it happen even to my Nexus 10. Here other shots:
https://drive.google.com/file/d/0ByucdM-SwPNnazVacUNZeEZkUlk/edit?usp=sharing
https://drive.google.com/file/d/0ByucdM-SwPNnRHU2QlJibk5TVVE/edit?usp=sharing
EDIT:
As happened to the N10, after a while the display appear in the stats:
https://drive.google.com/file/d/0ByucdM-SwPNnMEozbzNRVGdzSHc/edit?usp=sharing
EDIT:
I've noticed just now that while I was waiting a real full discharge of the battery the TWRP couldn't show me the battery percentage. Really strange...
[SOLVED]
In summary, the problem was the combination of kernel+ROM. The CM with his kernel on N4 was consuming tons of electrons. I tried Purity+Hellscore, now i reach few days of low usage and one and half of medium usage

How old is your phone? You might be able to get a replacement from Google under warranty.
Sent from my Nexus 4 using xda app-developers app

I don't think it'd be the 2A charge, I use the 2A charger on my battery all the time.
Sent from my Nexus 4 using Tapatalk

EDITed main post!
sshark said:
How old is your phone? You might be able to get a replacement from Google under warranty.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It have 9 months, and yes is still under warrenty, but I've bought it in Spain, and I live in Italy. I think this will be hard to solve

I have some strange problemi too.
Sometines the phone reboot itself and the battery drops (i tried to flash all stock: recovery, bootloader,ROM ecc..)

It could be a faulty battery.. Read this topic, it looks like you have the same kind of problems.
Do you also have simlocks/loss of network connection?

EDITed main post!
Faeshaas said:
It could be a faulty battery.. Read this topic, it looks like you have the same kind of problems.
Do you also have simlocks/loss of network connection?
Click to expand...
Click to collapse
I've already read this topic, i think the source of the problem may be related with mine, but symptoms are different. It is strange that this happened 9 months later!

Gully discharging the phone, rebooting, discharge again if any, reboot. Connect charger, charge full. Reboot, charge full again if any, reboot. This always worked for me.
You can also try to fully discharge, completely power off the phone and let it fully charge while powered off ( only a white battery should be shown on the display).
Sent from my Nexus 4 using xda app-developers app

I'm having the same issues with my phone.
Sent from my Nexus 4 using xda app-developers app

Oxious119 said:
Gully discharging the phone, rebooting, discharge again if any, reboot. Connect charger, charge full. Reboot, charge full again if any, reboot. This always worked for me.
You can also try to fully discharge, completely power off the phone and let it fully charge while powered off ( only a white battery should be shown on the display).
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Already done, nothing....

Did all of u found the problem? Cause it seems i have the same...
Sent from my Nexus 4 using XDA Premium 4 mobile app

Amiramac said:
Did all of u found the problem? Cause it seems i have the same...
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, no. Probably it is a battery related problem, i'm going to replace it and see what happen. In the meantime not even PurityROM+HellsCore kernel may handle this battery draining...