Hi Guys,
I am facing a strange issue with battery stats indicator. When I charge the battery it does not go beyond 85%. Mt vitals are as under
CM 7.0.2-buzz
Radio 13.55.55.24H_3.35.20.10
Kernel 2.6.32.39-nFinity arcotuxbox #1
I have already tried to wipe the battery stats and after rebooting i am able to charge upto 100%. However, on my next charge-up the battery stats get stuck at 85%.
any help is appreciated.
Get the battery calibrator app from the market. (Made by a dev from xda).
I would recommend turning device off charge for 5-6hours. Turn device on(PWR+VOL DWN+TRACKPAD). Let it charge for another hour with the battery calibrator app open then wipe the stats and unplug. Use device til it goes flat and recharge.
I'd recommend wiping dalvik cache before you start and cache partition.
Sent from my HTC Wildfire using Tapatalk
Thanks f0xy for the help.
Battery calibrator solved the problem. All I did was to charge the battery fully, reeboot into recovery, wipe the battery stats, charge to 100%, run battery calibrator and reboot. Problem solved.
Sent from my HTC Wildfire using XDA App
Was taking a look at my battery info this morning, when I noticed something very strange (see attached picture).
As you can see, the battery usage graph is there as normal - but there's no info displayed below it with regards to what apps are consuming the battery. Most annoyingly, there's also no obvious way to check the screen-on time.
Any ideas? Anyone seen this before?
I'm running MiNCO v4 with Franco's latest nightly 246, but flashing back to Milestone 5 didn't help. Neither did wiping cache/dalvik, fixing permissions or reflashing the ROM.
I guess the next step is to do a factory wipe, but I'm reluctant to do so because it's a real pain in the behind.
Try to wipe only the battery stats in recovery
Just had this happened to me on Moto Atrix HD running JB 4.1.1ATT original ROM on T-mobile service, rooted, bootloader unlocked. All aforementioned configurations put in place well before loosing batter stats. The only other "fix" I've seen for this was a ROM restore. Did you have any luck fixing this by factory wipe or other method?
D'oh! The per-application battery stats came back at the next full charge. On thing that can throw this off is that some battery meters report 100% at a point when the android system does not yet consider it full and if you stop charging at that point the stats may not refresh.
Sailor Saucy said:
Was taking a look at my battery info this morning, when I noticed something very strange (see attached picture).
As you can see, the battery usage graph is there as normal - but there's no info displayed below it with regards to what apps are consuming the battery. Most annoyingly, there's also no obvious way to check the screen-on time.
Any ideas? Anyone seen this before?
I'm running MiNCO v4 with Franco's latest nightly 246, but flashing back to Milestone 5 didn't help. Neither did wiping cache/dalvik, fixing permissions or reflashing the ROM.
I guess the next step is to do a factory wipe, but I'm reluctant to do so because it's a real pain in the behind.
Click to expand...
Click to collapse
I would gohead with the factory wipe. Do the job right the first time I say
Before going through all the trouble of a factory wipe, if you have not done this already:
Charge the phone until the native battery information screen says 100% and "Full" (or something other than"Charging"). In my case the native battery information screen and 3rd party battery stats app would react to the event of battery reaching 100% but, at that point although the battery screen said 100% it also said charging (as in attached pic). At this point the battery is not at maximum charge until battery screen says 100% and Full.
That it may be better for the battery not to reach maximum charge each time is another story.
View attachment 2699174
Hi there.
After a day of usage with the purpose of testing Greenify benefits, my battery usage does not reset after putting it on charge or reboot.
What i've tried for fixing:
Disconnect the battery from the phone.
Using a different battery - Different percentage but same usage time.
Wiped cache and dalvik cache.
Performed a fix permissions.
Deleted batterystats.bin from /data/system - For strange reason i no longer have "wipe battery stats" on CWM recovery.
I am using AK Kernel (Pirates) but when i first discovered that battery issue i was using AK Kernel (Purity) - So i assume it's not the kernel?
Trickster MOD: Stock settings.
ROM: Paranoid Android 3+ 4.2.2
So, as i said before, the only new App i installed before that issue was Greenify, but i hardly doubt it's its fault.
Any suggestions before i perform a factory reset?
Meanwhile i'll see what happens once i disconnect the phone after a full charge.
R: [Q] Battery stats NOT resetting after charge
Update: a full charge actually resets battery stats, but not anymore on partial charge/reboot/battery remove.
» Tapatalk 2 on Paranoid Nexus
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
TiTAN-O-One said:
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Well, try to discharge your phone until it fully drained, and charge your phone until it reaches to 100%, should be powered of,unplug, then use it the normal way, until it fully discharge and do the same, for at least 3 charging cycles.
Or charge your phone to 100% then before unplugging, go to /data/system and removed batterystats.bin.
I hope it will help, the first step is I think the most accurate, than using such apps.
Thank you,
TiTAN-O-One said:
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
jakelq said:
Well, try to discharge your phone until it fully drained, and charge your phone until it reaches to 100%, should be powered of,unplug, then use it the normal way, until it fully discharge and do the same, for at least 3 charging cycles.
Or charge your phone to 100% then before unplugging, go to /data/system and removed batterystats.bin.
I hope it will help, the first step is I think the most accurate, than using such apps.
Thank you,
Click to expand...
Click to collapse
honeyx said:
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
Click to expand...
Click to collapse
Good stuff here! thanks! Gonna try these stuffs out!:thumbup:
Sent from my GT-S6500 using xda app-developers app
honeyx said:
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
Click to expand...
Click to collapse
thanked for the info on latest cm9 battery performance
TiTAN-O-One said:
Good stuff here! thanks! Gonna try these stuffs out!:thumbup:
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
You might take a look on this one too when speaking of battery calibration:
http://forum.xda-developers.com/showthread.php?t=1460553
Calibration with apps by wiping battery stats is useless.
Battery in cm9 eol and cm9 rc3
Does battery of cm9 eol same like battery of cm9 rc 3 with honeyx's kernel and also how long the battery can last from 100% to 0%?
Bcoz I feel like my battery drop frm 100% until 87% in about 1 hour use cm9 rc3 with honeyx 's kernel...
Sorry my English so BAD
w4nkh4iri said:
Does battery of cm9 eol same like battery of cm9 rc 3 with honeyx's kernel and also how long the battery can last from 100% to 0%?
Bcoz I feel like my battery drop frm 100% until 87% in about 1 hour use cm9 rc3 with honeyx 's kernel...
Sorry my English so BAD
Click to expand...
Click to collapse
It´s nearly the same. Not exactly the same, but nearly the same, so it will not become better if you switch to CM9 EOL but probably a little bit worse. All depends to your battery health and how you are using your device.
I find the 2.6 kernel still a little bit better when it comes to battery life than the one in the final CM9, but since the differences are really small I´m already using the final release with a modified kernel.
This kernel has a few more optimizations for battery life and I will launch it quite soon after some more tests are done.
Don´t know how you are using your device and what apps are installed on your phone, but if your WiFi and Mobile Data is always on, there are a lot of apps running in the background and you are very often using your phone, your results are still very good.
Else better replace your battery with a new one, as there is no kernel that will turn a bad battery into a shiny new one.
honeyx said:
It´s nearly the same. Not exactly the same, but nearly the same, so it will not become better if you switch to CM9 EOL but probably a little bit worse. All depends to your battery health and how you are using your device.
I find the 2.6 kernel still a little bit better when it comes to battery life than the one in the final CM9, but since the differences are really small I´m already using the final release with a modified kernel.
This kernel has a few more optimizations for battery life and I will launch it quite soon after some more tests are done.
Don´t know how you are using your device and what apps are installed on your phone, but if your WiFi and Mobile Data is always on, there are a lot of apps running in the background and you are very often using your phone, your results are still very good.
Else better replace your battery with a new one, as there is no kernel that will turn a bad battery into a shiny new one.
Click to expand...
Click to collapse
Ok,mybe i install all of apps that i use...Can i use ur kernel that ur modified with final cm9?? ..just wanna use it...and thanx
Sorry my English so BAD
w4nkh4iri said:
Ok,mybe i install all of apps that i use...Can i use ur kernel that ur modified with final cm9?? ..just wanna use it...and thanx
Sorry my English so BAD
Click to expand...
Click to collapse
Sure, you just have to wait a bit till I release it as i need to test it for stability before launching it and am doing this for a couple of days to be 100% sure.
honeyx said:
Sure, you just have to wait a bit till I release it as i need to test it for stability before launching it and am doing this for a couple of days to be 100% sure.
Click to expand...
Click to collapse
Great,thanx u for share ur kernel..i can't waiting to using it
but i dont understand to battery life extender
" Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions."
Mean that change value before flash kernel??
Sorry my English SO BAD
w4nkh4iri said:
Great,thanx u for share ur kernel..i can't waiting to using it
but i dont understand to battery life extender
" Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions."
Mean that change value before flash kernel??
Sorry my English SO BAD
Click to expand...
Click to collapse
No problem, but wrong thread. You can´t change this value before flashing the kernel as it doesn´t exist before flashing a kernel that supports battery life eXtender. So only possible to change this after flashing it.
honeyx said:
No problem, but wrong thread. You can´t change this value before flashing the kernel as it doesn´t exist before flashing a kernel that supports battery life eXtender. So only possible to change this after flashing it.
Click to expand...
Click to collapse
Sorry bcoz ask u in wrong thread. Mean that, after i flash kernel,go to rootexplorer and change it and last reboot...if i wrong please correct to me
Sorry my English so BAD
w4nkh4iri said:
Sorry bcoz ask u in wrong thread. Mean that, after i flash kernel,go to rootexplorer and change it and last reboot...if i wrong please correct to me
Sorry my English so BAD
Click to expand...
Click to collapse
Just change it without rebooting afterwards. If you reboot after changing this value, it will be reset to the default value (100).
So to permamently change this value on each reboot you need to use a tool that will do this for you at each booting. Don´t remember which app is actually supporting BLX, but there is one that will do this for you.
honeyx said:
Just change it without rebooting afterwards. If you reboot after changing this value, it will be reset to the default value (100).
So to permamently change this value on each reboot you need to use a tool that will do this for you at each booting. Don´t remember which app is actually supporting BLX, but there is one that will do this for you.
Click to expand...
Click to collapse
So flash kernel and reboot.After that,go to rootexplorer and change value...but how about after flashing the kernel whipe your cache and dalvik cache and fix permissions???
w4nkh4iri said:
So flash kernel and reboot.After that,go to rootexplorer and change value...but how about after flashing the kernel whipe your cache and dalvik cache and fix permissions???
Click to expand...
Click to collapse
No. Go to CWM recovery. Flash kernel. Stay in CWM Recovery, whipe cache, whipe dalvik cache and fix permissions. Reboot. Then you can use root explorer to change the BLX value once it has booted.
honeyx said:
No. Go to CWM recovery. Flash kernel. Stay in CWM Recovery, whipe cache, whipe dalvik cache and fix permissions. Reboot. Then you can use root explorer to change the BLX value once it has booted.
Click to expand...
Click to collapse
Mean that,that BLX exist when after flash kernel and whipe cache,whipe cache, whipe dalvik cache and fix permissions.
Now,I feel like i see that how to use BLX. Thanx u.
So my English Bad
Guys please help me out...
I'm facing serious battery drain since yesterday. Was previously on ARHD 21 till yesterday...but observed increased battery drain during the night...battery reducing by 1% per minute in idle conditions...found the phone completely discharged in the morning...i thought maybe something has gone wrong with the ROm so wiped clean my phone using ARHD script...then flashed new boot image and installed ARHD 22....
unfortunately...the problem still exists...another important symptom...excessive overheating of the phone, especially near the camera...
in the battery stats section, Android System, Android OS are the top two with combined consumption of more than 70%...i have no clue why this is happening and hasn't stopped even after a superwipe and fresh rom installation....is there a more stable kernel that i can flash? please help me
Update: I moved to Blade ROM and the problem still persists...can it be that there's a problem in my sd card content?
Android System covers a lot of processes, use an app like better battery stats or gsam battery monitor to determine which services/processes exactly are causing the drain. If you've flashed a new kernel then the most important thing to do is wipe the dalvik cache, failing to do that can cause drain/fc errors in its own right.
sinkster said:
Android System covers a lot of processes, use an app like better battery stats or gsam battery monitor to determine which services/processes exactly are causing the drain. If you've flashed a new kernel then the most important thing to do is wipe the dalvik cache, failing to do that can cause drain/fc errors in its own right.
Click to expand...
Click to collapse
I went to recovery and cleared the dalvik cache but the problem still exists...the phone is constantly hot and battery is draining like anything...i'm installing better battery stats...can you guide me as to how do i locate the problem using the app?
The app will give you options to check battery usage either by app, process, or partial/full wakelock i.e. what process wakes the phone up from deep sleep. If it's constantly hot then it seems like some process is constantly running or unable to stop, for example if you restore an app like facebook from a previous rom it may be constantly trying to sync without authorisation, etc.
Check out proccess and i happen same problem, but i see its problem with wifi receive signal, its forced the battery wifi have bad receive signal.
I think its related at problem hardware (wifi with bad signal), battery is very hot and turn off wifi and come normal temp.
Enviado desde mi HTC One X usando Tapatalk 2
same problem here
I am having the same problem after upgrading to ARHD 31.2 battery drains quickly while I am using internet.