Note won't go into deep sleep after USB charging - AT&T Samsung Galaxy Note I717

I've posted a comment in a few other threads, but I think this is worthy of its own thread now to track if this is a common issue. Here's is the situation:
Good:
I charge the phone using the wall charger, take it off, reset CPUSpy stats, check it an hour later and find that it has been deep sleeping as expected.
Bad:
I charge the phone using a USB charger (computer, USB to cigarette lighter adapter in car, etc.), take it off, reset CPUSpy stats, check it an hour later and find that it has NOT been deep sleeping as expected.
I have let the phone sit for hours and it never goes into deep sleep, it just sits at the lowest stepping (384 mhz). If I reboot the phone, it's fine, and it deep sleeps immediately. It continues to work until I plug it into a USB charger again.
Some people were reporting this issue with the overclocked kernel, but this is happening to me completely stock. I'm on my second Note and it's happened on both.
Here are some things I have tried to fix it that have not helped:
1. I have rooted using the system partition ODIN method (meaning I am still on stock kernel) and frozen all the bloatware. This has had no effect.
2. I plug it into a wall charger for a few minutes, then take it off, reset CPUSpy, check it a bit later and it is still not deep sleeping.
My next step is to see if it is a third party background app that is keeping it awake, but I doubt that is what it is. I'm going to try killing them one at a time to see what happens. It's probably a core OS process which is why only a reboot fixes it so far. As a separate test I will try flushing the RAM out with the task manager, and seeing if that fixes the issue.
I've also installed Better Battery Stats, so hopefully it will show me a wakelock of what is causing the issue.
More to come....

Hmmm, looks like plugging into a wall charger may have fixed the issue but had a delayed effect. I checked it 5 minutes after and no deep sleeps, but now 20 minutes later and it is starting to deep sleep. I just reset CPUSpy again and will continue to monitor it.
Unfortunately I have no way to plug into a USB charger until tomorrow to cause it to mess up again, so if this fixes the issue I won't be able to test any other workarounds. I don't consider plugging into a wall charger a good workaround because we don't always have those handy.

So before it started to deep sleep I checked Better Battery Stats. After having my phone unplugged for 6-7 minutes, I have a kernel wakelock on sdio_al for 5 minutes. I'm not having much luck finding out what sdio_al is....

Update: It looks like plugging into a wall charger only half fixed my issue. It is now doing about 50% deep sleep and 50% 384 mhz. I now have an 11 minute wakelock on sdio_al and an 8 minute wakelock on PowerManagerService. The phone has only been off the charger for maybe 20 minutes or so and these are the stats since then.
Both of these numbers keep climbing as time goes on.

So after some googling I believe SDIO_AL has something to do with the SD card, specifically with a type of sd card called SDIO. Since this is only happening after a USB charge, that kind of makes sense. When you plug into a USB charger you have the option of presenting the SD card as mass storage to the computer, whereas with a wall charger that obviously isn't the case. So maybe some process that's sitting there waiting to mount the SD card if needed is stuck and keeping the device awake?

I am experiencing the same thing. I am Rooted but haven't loaded DG's kernel.
What I am doing is a battery pull following a full charge and no USB connection to confirm its the USB connection. Checking my wake locks turned up nothing. Even with the deep sleep issue I am getting 16 hours with 50% brightness and 3 hours screen time 2 hours talk time.

I experienced about 5% deep sleeps pre-root, but mostly it sat at 384. That pretty much confirms what you've been finding. Last night I rooted and installed Da_G's non-oc kernel and now my phone deep sleeps usually within 30s of setting it down.

Earthsdog said:
I am experiencing the same thing. I am Rooted but haven't loaded DG's kernel.
What I am doing is a battery pull following a full charge and no USB connection to confirm its the USB connection. Checking my wake locks turned up nothing. Even with the deep sleep issue I am getting 16 hours with 50% brightness and 3 hours screen time 2 hours talk time.
Click to expand...
Click to collapse
I had an old version of Better Battery Stats that only showed partial wakelocks, and mine was empty as well. I had to download the newest version and look at "kernel wakelocks" to see the SDIO and PowerManagement ones.

Irishwake83 said:
I experienced about 5% deep sleeps pre-root, but mostly it sat at 384. That pretty much confirms what you've been finding. Last night I rooted and installed Da_G's non-oc kernel and now my phone deep sleeps usually within 30s of setting it down.
Click to expand...
Click to collapse
After you installed Da_G's non-oc kernel, have you done a USB charge since then? I suspect you have not. I don't think the kernel fixed your issue so much as the fact that it was rebooted.
If you have USB charged it and his non-oc kernel DOES deep sleep, then his kernel fixes a bug that is present in stock.

I'm using Non-OC kernel from Da_G too. My phone is about 3% deep sleep. 97% is at 384Mhz. Not sure what happened

sweetboy02125 said:
I'm using Non-OC kernel from Da_G too. My phone is about 3% deep sleep. 97% is at 384Mhz. Not sure what happened
Click to expand...
Click to collapse
Have you done any USB charging? If so, reboot and see if deep sleep gets better.

EvoXOhio said:
Have you done any USB charging? If so, reboot and see if deep sleep gets better.
Click to expand...
Click to collapse
Did both wall and USb charging. Same thing, probably wakelocks somewhere

So everything I tried wouldn't stop the wakelocks nor the failure to deep sleep, so I rebooted the phone. And as expected, it is now deep sleeping the entire time and no wakelocks.
I'm hoping someone knowledgeable of this SDIO-AL process can figure out what is going on. does anyone know how to report this bug to Samsung?

I can confirm this is true on mine. Lots of sleep all day long after coming off of the wall charger last night and then cold starting it this morning. Charged it from my combo car bluetooth/charger (which acts as a USB host so it can play songs right from a USB drive) on the way home, unplugged it and reset the timers in CPU Spy. After 10 minutes it was over 90% @ 384 with no sleep at all. Plugged it into the wall charger for a few minutes, unplugged it, reset the timers, after just 5 minutes it was back to mostly sleeping again.

I do not have this problem with Da_G's rooted kernel - I only have this problem with Da_G's O/C kernel. I beleive he is working on this problem - some amazing work he has turned out so quickly.

sdimezq8 said:
I do not have this problem with Da_G's rooted kernel - I only have this problem with Da_G's O/C kernel. I beleive he is working on this problem - some amazing work he has turned out so quickly.
Click to expand...
Click to collapse
I am running the O/C kernel and the deoxed rom. I was having the exact same issue as everyone is having with usb and sleep. I wish I would have written down what I have done this evening but, fumbling around in the system, I have fixed it.
What I can tell you for sure if I have it set at 192 / 1.76 using Rom Toolbox and also uninstalled EVERYTHING at&t related except wifi sharing, and EVERYTHING Samsung except S-Pen apps and the Samsung keyboard and swype.
Using CpuSpy, 5 seconds after power / screen off, it will go from 1.7 to 192, then into deep sleep a second later. I let it sit for 15 mins and it stayed in DS until I woke it. i wish I would have made specific notes. But I can confirm that mine will DS using the OC kernel, but I have UN-Installed a lot of stuff that was in rom (and possibly running in the background). Everything still functions, Wifi / Gps, etc and I haven't observed any negative effects yet.
If someone can tell me how to dump my config so you guys could compare and see what I did, if it might have been some rogue process that was causing issues i'll be glad to help. BTW, I am no developer just a geek with a lil linux knowledge and not afraid to tinker..
I can't imagine I could hard brick the device uninstalling services anyway, since I imagine the recovery routine is in with the boot-loader which i'm not messing with, but tell me if i'm wrong...
Edit: one thing I have noticed, that even though the Note is still connecting using MTP, it no longer does the media scan, but I can still access both storage areas fine from the pc. Before my tinkering, no matter how I charged my phone, via wall charger, or computer that media scan would run no matter what, now its not... That's one change I DO like.. usb access seems quicker too.

Ok, I would like to see if I can have someone confirm my test.
Test 1:
1. Charge VIA computer USB or charger to 100%
2. Remove from cable, cradle etc...
3. Immediately open CPU Spy and Reset the Timers and close CPU Spy.
4. Place into Sleep Mode by pressing the Power/Standby Button
5. Wait 10 minutes and go into CPU Spy and note Deep Sleep time.
Please provide the following
1. Charging Type USB to PC, Samsung Cable and Outlet Charger or Third Party Charger.
2. Deep Sleep Time 0 if none.
Test 2:
1. Charge VIA computer USB or charger to 100%
2. Remove from cable, cradle etc...
3. Hold Down the Power/Standby and choose Power Off
4. Immediately boot completion open CPU Spy and Reset the Timers and close CPU Spy.
5. Place into Sleep Mode by pressing the Power/Standby Button
6. Wait 10 minutes and go into CPU Spy and note Deep Sleep time.
Again please provide the following
1. Charging Type USB to PC, Samsung Cable and Outlet Charger or Third Party Charger.
2. Deep Sleep Time 0 if none.
Now try this ;-)
Test 3:
1. Charge VIA computer USB or charger to 100%
2. Remove from cable, cradle etc...
3. Pull Battery for 1 minute and then replace and power on.
4. Immediately after boot sequence open CPU Spy and Reset the Timers and close CPU Spy.
5. Place into Sleep Mode by pressing the Power/Standby Button
6. Wait 10 minutes and go into CPU Spy and note Deep Sleep time.
Again please provide the following
1. Charging Type USB to PC, Samsung Cable and Outlet Charger or Third Party Charger.
2. Deep Sleep Time 0 if none.
It bet I know what you will find but lets see.

Ran another test today. Yesterday after doing a cold start after disconnecting from the charger I went many hours with barely a percentage point drop on the battery. Had lots of sleep time.
Today I intentionally charged from my car charger on the way to work to trigger this problem, its a USB host and not a dumb charger. Phone uptime is 2 1/2 hours and my sleep state is right where it was when I unplugged, about 9 minutes (the amount of time it was on before I plugged it into the car charger). Time at 384 is 2 hours 16 minutes.
My battery is already down to 93% with most of that time sitting in my pocket (wifi and GPS forced off) so that's about a 3% drain per hour just because it won't sleep. Over a 12 hour day that would take away a third of the battery's life!
---------- Post added at 09:47 AM ---------- Previous post was at 09:32 AM ----------
Just put it on a wall charger for a few minutes, and unplugged, now it is sleeping.

Earthsdog said:
Ok, I would like to see if I can have someone confirm my test.
Test 1:
1. Charge VIA computer USB or charger to 100%
2. Remove from cable, cradle etc...
3. Immediately open CPU Spy and Reset the Timers and close CPU Spy.
4. Place into Sleep Mode by pressing the Power/Standby Button
5. Wait 10 minutes and go into CPU Spy and note Deep Sleep time.
Please provide the following
1. Charging Type USB to PC, Samsung Cable and Outlet Charger or Third Party Charger.
2. Deep Sleep Time 0 if none.
Test 2:
1. Charge VIA computer USB or charger to 100%
2. Remove from cable, cradle etc...
3. Hold Down the Power/Standby and choose Power Off
4. Immediately boot completion open CPU Spy and Reset the Timers and close CPU Spy.
5. Place into Sleep Mode by pressing the Power/Standby Button
6. Wait 10 minutes and go into CPU Spy and note Deep Sleep time.
Again please provide the following
1. Charging Type USB to PC, Samsung Cable and Outlet Charger or Third Party Charger.
2. Deep Sleep Time 0 if none.
Now try this ;-)
Test 3:
1. Charge VIA computer USB or charger to 100%
2. Remove from cable, cradle etc...
3. Pull Battery for 1 minute and then replace and power on.
4. Immediately after boot sequence open CPU Spy and Reset the Timers and close CPU Spy.
5. Place into Sleep Mode by pressing the Power/Standby Button
6. Wait 10 minutes and go into CPU Spy and note Deep Sleep time.
Again please provide the following
1. Charging Type USB to PC, Samsung Cable and Outlet Charger or Third Party Charger.
2. Deep Sleep Time 0 if none.
It bet I know what you will find but lets see.
Click to expand...
Click to collapse
I've basically already done all of this and provided the data above, and others have done the same and confirmed. If you use a USB charger, it will not sleep at all until you either power cycle it or plug it into a wall charger for a bit. The wall charger seems to kill whatever USB charging process is keeping it awake.
Does anyone know how to report this bug to Samsung, short of calling the generic Samsung support line?

EvoXOhio said:
I've basically already done all of this and provided the data above, and others have done the same and confirmed. If you use a USB charger, it will not sleep at all until you either power cycle it or plug it into a wall charger for a bit. The wall charger seems to kill whatever USB charging process is keeping it awake.
Does anyone know how to report this bug to Samsung, short of calling the generic Samsung support line?
Click to expand...
Click to collapse
Well I my case I haven't had the same experience AC to USB charing also causes the issue. I am searching for similarities and data. This is much more than a hung bit in the code. Before we assume it code we need to confirm there are no hardware issues such as....
Non-Samsung Cable
Third Party AC Charger
DC Charger
PC verses AC
So perhaps you have isolated for yourself if we want a manufacturer to address an issue you have to have replaceable data. So I am just trying to help facilitate that.

Related

For tabs with battery drainage problem... or how to calibrate

I've got this problem with my tab (quick battery drainage). Symptoms would be your 100% charged tab would go down to 0% in unusual shorter time ( like 2-4 hours). You put it on charger and tab would be charged back to 100% again in substantial short time like 2-3 hours instead of 6-7 hours.
Well, after looking at this issue I think I have come up with solution.
At least, my tab looks like it's back on track... though, to say for sure I would need another couple days of testing.
The problem is not runaway wild application on a background but battery control circuit. This chip reports to OS much smaller battery capacity as it is for some reason. I will not go into details but here is what you need to try:
Flash stock kernel (may be custom kernel is not the reason for bad chip calibration and I'm 90% positive but just to be on safe side). You don't need to do factory wipe in OEM recovery for our purpose.
You also don't need to wipe batterystats.bin or use "Battery Calibration" apps from market (which does exactly the same wipe just in more end user friendly way). This wipe serves no other purpose then refreshing your usage statistics.
You also don't need to drain your battery all way down... nice, this way you don't have to wait for too long.
Well, here we go:
charge tab somewhere in between 80 and 100%.
edit: remove charger
shutdown tab (not put in hibernate/sleep) for 1 hour.
edit: turn tab on and run it for 30-40 min. or whatever it takes to drop charge to 40-50%.
shutdown tab again for 5 hours (overnight).
turn tab again and check... you should be fine now, charge it again 100% and use as usual.
That should do correct chip calibration.
PS: the reason why this chip calibration went bad at the first still remains open.
EDIT: just want to give a shortcut for those who does not feel like reading through the thread.
http://forum.xda-developers.com/showpost.php?p=16771651&postcount=41
Edit: here is calibration procedure which was modified down this thread ...
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour.
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour.
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
Edit: if you physically disconnect battery (you have to disassemble tablet) and keep it for couple min. that would trigger FG chip to start with default SOC curve.
Any follow up? Did this fix work for you since yesterday or anyone else?
yup, this is it...
This is how properly calibrate sg tab's batteries. There are some variations to the process but essentially battery will be calibrated in two measurements which stand apart by minimum 40% when battery is at rest on time intervals 1 and 5 hours.
No need to do factory reset, wipe batterystats, use battery calibrator apps from market or dance around with rain stick... all this will give same result as woodoo magic... though if by some reason battery calibration conditions are met then one may claim a miracle.
*sigh of relief* looks like this worked. More people that have this issue should now about this. Thank you for the fix.
Sent from my DROID2 using XDA App
Is this the same as the Sleep on Death (SOD) syndrome? that while charging it dies overnight and then you have to long press the power button and/or charge it to get it back?
Worked for me so far all good thanks
Sent from my GT-P7510 using XDA Premium App
Thanks will try this after flashing many custom roms I've been suffering from fast drainage which is not normal from when I had it on stock.
hyann said:
Is this the same as the Sleep on Death (SOD) syndrome? that while charging it dies overnight and then you have to long press the power button and/or charge it to get it back?
Click to expand...
Click to collapse
How long your tab usually works on one charge? if 8 and more hours - then no, I would think that there is a bug in Android charger control.
Vlad_z said:
yup, this is it...
This is how properly calibrate sg tab's batteries. There are some variations to the process but essentially battery will be calibrated in two measurements which stand apart by minimum 40% when battery is at rest on time intervals 1 and 5 hours.
No need to do factory reset, wipe batterystats, use battery calibrator apps from market or dance around with rain stick... all this will give same result as woodoo magic... though if by some reason battery calibration conditions are met then one may claim a miracle.
Click to expand...
Click to collapse
May I ask what do you mean by rest time intervals of 1 and 5 hours?
Does it mean that the calibration will only take place when the tab is off for 1 hour, then switch on and used till battery depleted by a further 40% minimum and the switch off for another 5 hour. Correct?
Also , is this 40% refer to value before or after calibration? I asked this because when I restart my tab the value changed (ex: 36% before restart to 53% after restart)
wlighter said:
May I ask what do you mean by rest time intervals of 1 and 5 hours?
Does it mean that the calibration will only take place when the tab is off for 1 hour, then switch on and used till battery depleted by a further 40% minimum and the switch off for another 5 hour. Correct?
Also , is this 40% refer to value before or after calibration? I asked this because when I restart my tab the value changed (ex: 36% before restart to 53% after restart)
Click to expand...
Click to collapse
Yes that's correct.
Fuel gauge chip will take 1 measurement of open circuit voltage and internal resistance only when battery is at rest (no charge/discharge) for at least 40min. - so I say 1 hour just to be sure...
Consecutive measurements, from which gauge chip can derive capacity of the battery have to be at least 40% and 5 hours apart.
Technically speaking, that 40% difference can be in either directions. Say you have 40% as of now, leave it in rest for 1 hour, then charge it to 100% and leave it at rest for 5 hours and you will have same result.
Condition "at rest" means voltage change less then 4mV (or mkV) per sec. - I don't remember.
When tablet is in sleep some background processes may awake tablet briefly and reset the 1 hour counter - so to make it work for sure, simply do shutdown.
if you want additional reading on my findings then look here:
http://forum.xda-developers.com/showpost.php?p=16615800&postcount=517
I tried this method...
1.Charged tab t0 80%, then shut down (removed charger) for 1 hour.
2.Turned on tab and played games for about 45min till battery was 49%.
3.Turned off tab and let sleep for 5 hours (charger still removed).
4.Turned tab back on and battery reads 79%, used for about 20min and battery reads 68%... Seems battery drain is still happening?
Right now i'm charging the tablet back upto 100% then perhaps try this method again... Did I do something wrong?
jzen said:
I tried this method...
1.Charged tab t0 80%, then shut down (removed charger) for 1 hour.
2.Turned on tab and played games for about 45min till battery was 49%.
3.Turned off tab and let sleep for 5 hours (charger still removed).
4.Turned tab back on and battery reads 79%, used for about 20min and battery reads 68%... Seems battery drain is still happening?
Right now i'm charging the tablet back upto 100% then perhaps try this method again... Did I do something wrong?
Click to expand...
Click to collapse
same problem im facing. This is why im wondering is the 40% value of before or after calibration. Because although it might drop 40% before calibration is done, the real drop value might be less then that. Which means to the chip it might just see a drop of example 20% of real drop and hence it didn't perform the calibration because conditions of 40% is nt met.
I did forget to flash back to the stock kernel (using pershoot's).
I just flashed to doc's slim 6.5 which has a modified stock kernel (couldnt find just the stock kernel and my internet is too slow to download the entire stock rom.). Going to try this method again but starting at 40%
1.Battery at 40%, shutdown tablet for 1 hour.
2.Charge tablet to 100% (while shutdown)
3.Leave tablet shutdown for 5 hours
4.Pray to droid gods, find my rain stick and begin dark resurrection ritual while watching true blood.
My only question now is... Should I turn the tablet back on after the 1 hour shutdown? Or should I leave it shutdown and just plug in charger till its 100% charged, then let it stay shutdown for 5 hours?
This is what worked for me:
1. Charged tab to 100% removed from charger.
2. Power down for 1 hour.
3. Power on (tab at 96%)
4. Drain to 46%
5. Power off for 5 hours
When I powered the tab back on after the 5 hours, i used it for a while and rebooted and the battery reading stayed the same which it wasn't doing before the calibration. It has been draining and charging at a normal pace since then and has remained the same after reboots and ROM flashes since the calibration.
FillTheVoid said:
This is what worked for me:
1. Charged tab to 100% removed from charger.
2. Power down for 1 hour.
3. Power on (tab at 96%)
4. Drain to 46%
5. Power off for 5 hours
When I powered the tab back on after the 5 hours, i used it for a while and rebooted and the battery reading stayed the same which it wasn't doing before the calibration. It has been draining and charging at a normal pace since then and has remained the same after reboots and ROM flashes since the calibration.
Click to expand...
Click to collapse
I'm going to go ahead and try this method right now! But for me... sometimes my battery will not charge unless the unit is shutdown (ever since battery issues started.). I hope this time it will charge while its on.
Also the instructions say to flash the stock kernel before trying this method... Did you do this? And were you able to flash back to pershoot's without issue?
*Update:
It doesn't look like its charging, (system on). Should I just shutdown and charge it to 100%? Then continue with said method? Anyone know if this method will work while tablet is shutdown through the entire process?
jzen said:
I'm going to go ahead and try this method right now! But for me... sometimes my battery will not charge unless the unit is shutdown (ever since battery issues started.). I hope this time it will charge while its on.
Also the instructions say to flash the stock kernel before trying this method... Did you do this? And were you able to flash back to pershoot's without issue?
Click to expand...
Click to collapse
My tab was charging while on, sometimes it wouldn't show it till after a reboot. I did mine from stock 3.1. (A backup I made before I took the TW OTA) I have not re-flashed pershoot's kernel and probably wont till the bug is worked out. I did however flash the deodexed stock TW and flashed a theme and have had no issues.
Edit: if its not chargin while on, i would charge it all the way while off then turn it on so it can read the battery then start the 1 hour power down.
Correction guys...
I was sure that our p7510 model was using TI bq20z75 fuel gauge chip but with new information looks like it's Maxim 17042 chip... It's embarrassing but I have to stay corrected. TI chip would calibrate itself in procedure outlined above as for Maxim - I don't know yet. I'm looking at it.
These are good and bad news. Good one - with this new fact, it's very possible that the reason of chip's SOC counter corruption is in software. Driver for Maxim is pretty messy and complex (because it's messy). In contrast driver for TI is simple and straight forward (because TI chip is smart). Software can be fixed but problem in hardware design not so easy.
Well, I will report back when I find something.
So, will FillTheVoid 's method work with my GT-p7510? :x
Vlad_z said:
Correction guys...
I was sure that our p7510 model was using TI bq20z75 fuel gauge chip but with new information looks like it's Maxim 17042 chip... It's embarrassing but I have to stay corrected. TI chip would calibrate itself in procedure outlined above as for Maxim - I don't know yet. I'm looking at it.
These are good and bad news. Good one - with this new fact, it's very possible that the reason of chip's SOC counter corruption is in software. Driver for Maxim is pretty messy and complex (because it's messy). In contrast driver for TI is simple and straight forward (because TI chip is smart). Software can be fixed but problem in hardware design not so easy.
Well, I will report back when I find something.
Click to expand...
Click to collapse
A lot of this is way over my head, but my battery calibration seems to be accurate, although I can't be absolutely sure because I have no stats from the previous calibration to compare it to. I do know for sure that after this process the bug of it draining then after reboot going back to what it should be is gone.
so i guess we need to flash back the stock ROM w/o TW for this procedure to work? I was trying the same steps with StarBurst + pershoot kernel it seem that it doesn't work. Anyone manage to calibrate with pershoot kernel?

[Q] Battery is burning FAST !

First of all it wouldnt charge past 99%, And then, after one hour of standby it went down to 88%!!
Cm7 official stable release.
Me too no pass 99% :S
Try to download a "battery caliberation" app and do that, also burn it to 0% and charge to 100% while the phone is off..i heard that this might help.
Now i will flash Nottachtrix and do what i wrote Good luck man !
Velcis Ribeiro said:
Me too no pass 99% :S
Click to expand...
Click to collapse
The charging thing is something that is (seemingly) well known throughout the community. I have tried to do the calibration, but it doesn't seem to work that well (at least for me). There is a thread around here somewhere for fixing the issue. I just have never tried it due to work reasons.
The charging past 99% is a known issue with most of the ROMs. There is a thread in here that takes you step by step to get it to display 100%. Basically....
Charge the phone long enough to where you know it should be at 100% even though it is still displaying 99%.
Power the phone off while it is still connected to the charger and then pull the battery.
With the battery pulled, power the phone back on until you see the battery indicator with the "?".
Put the battery back in and reboot.
You will then see the display of 100% with the phone still connected to the charger. The only downside is that as soon as you disconnect the charger, it will drop back to 99%. I have done this multiple times.
You can try the latest nightly: update-cm-7-20120508-NIGHTLY-olympus-signed.zip
I read good things about it.
First of all, use Wipe Battery Stats function at recovery.
1 - Discharge all your smartphone battery;
2 - Connect it to the wall charger and don't turn it on;
3 - Wait till it shows you 100%;
4 - Remove the battery, wait 10 seconds, put it again and keep it turned off;
5 - Wait 30 minutes, keep it connected to the wall charger and press power button till it turns on;
6 - Wait 30 minutes, keep it connected to the wall charger and use Battery Calibration App to calibrate it;
It doesn't make any sense, but sometimes, after step 5, i prefer connect it to usb port in a laptop or computer and wait one hour. It always worked with me.
It might solve your problem .
Wiping battery stats does nothing. it just takes a few charge cycles. If it's a new rom and it's draining fast it's also cause you are probably playing with it a lot
Sent from my Galaxy Nexus using Tapatalk 2
nathan96 said:
after one hour of standby it went down to 88%!!
Click to expand...
Click to collapse
It could be a bluesleep problem... Install CPU Spy App and look if it goes into deep sleep mode. If not, there is a fix for it.
Aside from the OP's issue with the battery draining quickly, why does it matter if it doesn't show 100%?
Nothing can ever 'really' be 100% charged because as soon as you take it off mains it is instantly on the battery at lets say 99.9999%...
As long as the battery doesn't drain quickly I couldn't care less if its showing 99 or 100%.
The problem was that it was draining very quickly to smt like 50% and then it would hold longer...I just wiped everything, restored a neutrino 2.7 nandroid backup i had, flashed the jug fix v2 and now it shows 100%

CPU Usage

Hi, I have currently upgraded my Xperia Neo to CM9. I have been experiencing a bit lesser batter life.
Also when i use CpySpy app it doesnt show the time spent by the processor in the specified frequencies. It always shows 0 for all
states. that is definitely not correct. The system can't be idle when i use right? So i'm wondering is there any issue with CM9 or my phone particularly. Also i have already used CM7 and CpySpy was giving me right numbers. I need help to figure out why my battery drains even when my phone is in idle and why there are no numbers in CpuSpy.
Thanks in advance
I can't guarantee, but cpu usage/phone turning to be hot after a while of use/short battery life is something common with most of androids. On my HTC HD2 battery life is twice as short since I started to use android.
If, after rooting or more likely the case after flashing a new rom, you often have battery reporting errors, and re-calibrating the battery along with some steps I will outline for you below will ensure that your battery is getting a full charge, and the battery reporting accuracy is right on. I run my device in performance mode all the time, and with a CPU overclock of 1.25GHz and various tweaks, I have about a day an a half to a day and a quarter of full runtime from my battery. This is with moderate to heavy usage (calls, emailing, text, gaming, web browsing, etc.) so you should have no problems getting acceptable battery performance after following these steps:
1. Take the case off your device (one of the latter steps involves taking the battery out from the phone while it's plugged in. Make sure your case won't stand in the way.)
2. Install Battery Calibration app from the market
3. Plug in your device to charge while it's on, wait till it gets to a 100%
4. When the charge is 100%, open the BatteryCalibration app and lookup what the charge is in MV while at 100%. Write it down.
My Atrix 2 was showing ~3400MV while at 100%, which is definitely not the maximum capacity.
5. Discharge your device completely until it shuts off.
A good way of doing this quickly is by turning on wifi, and a video player.
6. Without turning on the phone plug it into a wall charger and let it get to 100%
7. When it's at 100%, without unplugging it from the wall charger, take off the battery cover, and take the battery out.
Your phone will "reboot" and show a Missing Battery icon.
8. Without unplugging the phone from the wall charger or turning it on, put the battery back in and wait until the phone recognizes the battery.
9. Your battery should now be recognized by the phone, and showing a charge % significantly lower than 100%.
Mine showed only 5%.
10. Let it sit there charging for 2-3 hours (or more).
My phone wouldn't charge past 10%, but yours might. The numbers don't matter much as the phone is definitely getting additional charge that could have been lost while flashing ROMs, etc.
11. After 2-3 hours (or more), turn the phone on while holding the volume down button and get into CWM.
Do not disconnect it from the charger still!
12. Wipe battery stats in CWM, reboot.
Do not disconnect it from the charger still!
13. When the phone turns on, go into Battery Calibration app again and look up your MV numbers -if you were like me, they should be significantly higher than before. After this whole process I had 4351MV at 100%, comparing to 3400MV before calibration.
Do not disconnect it from the charger still!
14. Before going to sleep - Install Watchdog Task Manager Lite from the market. Go into it's preferences, set CPU threshhold to 20%, check "Include phone processes", check "Monitor phone processes", check "Display all phone processes", set system CPU threshhold to 20% as well.
Do not disconnect it from the charger still!
15. Make sure your wifi and data connections are off. Now finally unplug the phone from the charger.
Go to bed, let your phone sleep too.
16. Success! Next morning check where your battery % is at and if you followed the instructions correctly / got lucky like me, your battery life should be 90% or more.
I went to bed with 98% and woke up to 94%. So, I consider this mission a success.
Sent from my MB865 using xda's premium carrier pigeon service
Apex_Strider said:
If, after rooting or more likely the case after flashing a new rom, you often have battery reporting errors (as mentioned above), and re-calibrating the battery along with some steps I will outline for you below will ensure that your battery is getting a full charge, and the battery reporting accuracy is right on. As far as power cycling, I don't know that it does much good. I run my device in performance mode all the time, and with a CPU overclock of 1.25GHz and various tweaks, I have about a day an a half to a day and a quarter of full runtime from my battery. This is with moderate to heavy usage (calls, emailing, text, gaming, web browsing, etc.) so you should have no problems getting acceptable battery performance after following these steps:
1. Take the case off your device (one of the latter steps involves taking the battery out from the phone while it's plugged in. Make sure your case won't stand in the way.)
2. Install Battery Calibration app from the market
3. Plug in your device to charge while it's on, wait till it gets to a 100%
4. When the charge is 100%, open the BatteryCalibration app and lookup what the charge is in MV while at 100%. Write it down.
My Atrix 2 was showing ~3400MV while at 100%, which is definitely not the maximum capacity.
5. Discharge your device completely until it shuts off.
A good way of doing this quickly is by turning on wifi, and a video player.
6. Without turning on the phone plug it into a wall charger and let it get to 100%
7. When it's at 100%, without unplugging it from the wall charger, take off the battery cover, and take the battery out.
Your phone will "reboot" and show a Missing Battery icon.
8. Without unplugging the phone from the wall charger or turning it on, put the battery back in and wait until the phone recognizes the battery.
9. Your battery should now be recognized by the phone, and showing a charge % significantly lower than 100%.
Mine showed only 5%.
10. Let it sit there charging for 2-3 hours (or more).
My phone wouldn't charge past 10%, but yours might. The numbers don't matter much as the phone is definitely getting additional charge that could have been lost while flashing ROMs, etc.
11. After 2-3 hours (or more), turn the phone on while holding the volume down button and get into CWM.
Do not disconnect it from the charger still!
12. Wipe battery stats in CWM, reboot.
Do not disconnect it from the charger still!
13. When the phone turns on, go into Battery Calibration app again and look up your MV numbers -if you were like me, they should be significantly higher than before. After this whole process I had 4351MV at 100%, comparing to 3400MV before calibration.
Do not disconnect it from the charger still!
14. Before going to sleep - Install Watchdog Task Manager Lite from the market. Go into it's preferences, set CPU threshhold to 20%, check "Include phone processes", check "Monitor phone processes", check "Display all phone processes", set system CPU threshhold to 20% as well.
Do not disconnect it from the charger still!
15. Make sure your wifi and data connections are off. Now finally unplug the phone from the charger.
Go to bed, let your phone sleep too.
16. Success! Next morning check where your battery % is at and if you followed the instructions correctly / got lucky like me, your battery life should be 90% or more.
I went to bed with 98% and woke up to 94%. So, I consider this mission a success.
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
Great, what should be. :good:

[Q] Charging taking too long

Hi as stated my question is NOT to know how many of you experience charging that takes too long, but is there a SOLUTION for it?
I am using a desire s, it used to take 2hours 30min(from 15%-100%) but now a days it takes close to 5 hours to fully charge.
I've read many thread with similar problem but non seem to be able to find the solution.
I doubt it is battery related issue as i got this phone together with my friends and theirs has no issue like this.
I've tried :
1)full wipe
2)different rom(s)
3)different kernel
4)battery stat wipe
5)different charger(both are htc)
ps : I've post this in DesireS Q&A but did not get any solution.
How are you charging your phone: USB to PC it via wall charger? If it's taking longer than usual turn off the phone. I've found that this sped up the charge dramatically! By doing so, you can also see a battery simulation on the screen showing the charging process.
Also, if you're charging vis USB, the requirements are 5 volts from a USB connector. But the problem is amperage. Wall chargers can supply up to 1 amp (some will supply more, but you don't want more for a phone), while many computers will only supply 500 milliamps out of a USB connector. Thus the phone (battery) will charge faster with a higher amperage. If that doesn't do any good, you may have a bunk battery or some kind of hardware issue...
Sent from my MB865 using xda's premium carrier pigeon service
I am using wall charger. It seems consistent to charge slower at around 70% then speed back up at 90%. Are u sure that this is a symptoms of a spoiled battery?
To me(an accountant not a technicians) it seems like the "smart" phone is tell it to charge slower at 70%.
Sent from my Desire S using xda premium(nah dun have the money to buy premium)
Same problem
I have the same problem, first when I bought my SE x10 mini pro. It charged in 1.5 hours but nw it takes about 3 hours. I don't know the reason but I'm trying to find out how to solve this problem.
I'm not entirely certain its a case of bad battery, but it does sound a bit suspicious. If you're feeling up to it, you can try this: (it's worth a shot.)
If, after rooting or more likely that case after flashing a new rom, you often have battery reporting errors and re-calibrating the battery along with some steps I will outline for you below will ensure that your battery is getting a full charge, and the battery reporting accuracy is right on.
1. Take the case off your phone (one of the latter steps involves taking the battery out from the phone while it's plugged in. Make sure your case won't stand in the way.)
2. Install Battery Calibration app from the market
3. Plug in your phone to charge while it's on, wait till it gets to a 100%
4. When the charge is 100%, open the BatteryCalibration app and lookup what the charge is in MV while at 100%. Write it down.
My Atrix 2 was showing ~3400MV while at 100%, which is definitely not the maximum capacity.
5. Discharge your phone completely until it shuts off.
A good way of doing this quickly is by turning on wifi, and a video player.
6. Without turning on the phone plug it into a wall charger and let it get to 100%
7. When it's at 100%, without unplugging it from the wall charger, take off the battery cover, and take the battery out.
Your phone will "reboot" and show a Missing Battery icon.
8. Without unplugging the phone from the wall charger or turning it on, put the battery back in and wait until the phone recognizes the battery.
9. Your battery should now be recognized by the phone, and showing a charge % significantly lower than 100%.
Mine showed only 5%.
10. Let it sit there charging for 2-3 hours (or more).
My phone wouldn't charge past 10%, but yours might. The numbers don't matter much as the phone is definitely getting additional charge that could have been lost while flashing ROMs, etc.
11. After 2-3 hours (or more), turn the phone on while holding the volume down button and get into CWM.
Do not disconnect it from the charger still!
12. Wipe battery stats and reboot.
Do not disconnect it from the charger still!
13. When the phone turns on, go into Battery Calibration app again and look up your MV numbers -if you were like me, they should be significantly higher than before. After this whole process I had 4351MV at 100%, comparing to 3400MV before calibration.
Do not disconnect it from the charger still!
14. Make sure your wifi and data connections are off. Now finally unplug the phone from the charger.
Go to bed, let your phone sleep too.
The next morning, use your phone as normal throughout the day. Then when it comes time to charge again, see if that does anything for your battery life and/or charging times...
Sent from my MB865 using xda's premium carrier pigeon service
I liked your current charge curve..
bump
ps : i did try out #5 but no success
best way is shut down device when charging
Sent from my GT-I9300 using xda app-developers app
Yes is charges quickly when the phone is off, but what if i am expecting a call or some sort. Could it be a script some where to tell the phone when should it start slow charge or something similar?

charging issue on Cm7.2

hi guys! i'm running cm7.2 on my su660 (it's a kang build which is ported from p990 official CM build). and i have a problem on charging the phone. when the phone have 10% of battery left, i plug in the charger, the phone show the charging symbol . but when i leave it sleep and come back after 'bout 3 hours, it still show 10%. but the voltage in sparepart is aproximate 4200 mV. so the battery is fully charged but the rom didn't regconize it. but then after some minutes turning the screen on, the rom show that phone is fully charged. so i guess that the battery percentage counter doesn't work why the phone is pluged in and sleep. so this is a rom issue? can i fix it myself?
PS: sorry for my poor English because i'm not a native English speaker. i'm from VietNam. i tried my best to explane my case. hope u can understand me!
If, after rooting or more likely that case after flashing a new rom, you often have battery reporting errors, and re-calibrating the battery along with some steps I will outline for you below will ensure that your battery is getting a full charge, and the battery reporting accuracy is right on. As far as power cycling, I don't know that it does much good. I run my device in performance mode all the time, and with a CPU overclock of 1.25GHz and various tweaks, I have about a day an a half to a day and a quarter of full runtime from my battery. This is with moderate to heavy usage (calls, emailing, text, gaming, web browsing, etc.) so you should have no problems getting acceptable battery performance after following these steps:
1. Take the case off your device (one of the latter steps involves taking the battery out from the phone while it's plugged in. Make sure your case won't stand in the way.)
2. Install Battery Calibration app from the market
3. Plug in your device to charge while it's on, wait till it gets to a 100%
4. When the charge is 100%, open the BatteryCalibration app and lookup what the charge is in MV while at 100%. Write it down.
My Atrix 2 was showing ~3400MV while at 100%, which is definitely not the maximum capacity.
5. Discharge your device completely until it shuts off.
A good way of doing this quickly is by turning on wifi, and a video player.
6. Without turning on the phone plug it into a wall charger and let it get to 100%
7. When it's at 100%, without unplugging it from the wall charger, take off the battery cover, and take the battery out.
Your phone will "reboot" and show a Missing Battery icon.
8. Without unplugging the phone from the wall charger or turning it on, put the battery back in and wait until the phone recognizes the battery.
9. Your battery should now be recognized by the phone, and showing a charge % significantly lower than 100%.
Mine showed only 5%.
10. Let it sit there charging for 2-3 hours (or more).
My phone wouldn't charge past 10%, but yours might. The numbers don't matter much as the phone is definitely getting additional charge that could have been lost while flashing ROMs, etc.
11. After 2-3 hours (or more), turn the phone on while holding the volume down button and get into CWM (if installed) or use Rom Manager (is device is supported).
Do not disconnect it from the charger still!
12. Wipe battery stats in CWM, reboot.
Do not disconnect it from the charger still!
13. When the phone turns on, go into Battery Calibration app again and look up your MV numbers -if you were like me, they should be significantly higher than before. After this whole process I had 4351MV at 100%, comparing to 3400MV before calibration.
Do not disconnect it from the charger still!
14. Before going to sleep - Install Watchdog Task Manager Lite from the market. Go into it's preferences, set CPU threshhold to 20%, check "Include phone processes", check "Monitor phone processes", check "Display all phone processes", set system CPU threshhold to 20% as well.
Do not disconnect it from the charger still!
15. Make sure your wifi and data connections are off. Now finally unplug the phone from the charger.
Go to bed, let your phone sleep too.
16. Success! Next morning check where your battery % is at and if you followed the instructions correctly / got lucky like me, your battery life should be 90% or more.
I went to bed with 98% and woke up to 94%. So, I consider this mission a success.
Sent from my MB865 using xda's premium carrier pigeon service

Categories

Resources