Related
i'm having battery consumption issues, and somewhere on the forum the guys talked about a widget that shows current battery discharge amount in ma (miliamps). so i installed the widget and it shows 44ma no matter what i did, i turned on everything, and then all off, changed radios, changed roms(was using leedroid2.2f then flashed opendesire4.0.36)...
what ever i did, 44ma was the number showed by the widget. i installed another widget, and it gave the same number...
any one has any clue about this?
also yesterday i charged the phone to the point where the lock screen said it was "Charged". but i didn't unplug the charger, 30 minutes later "CurrentWidget" changed the number from 44ma to 8ma, so i thought, maybe now its fully charged.
used the phone for a while(maybe used up 10% or a bit more), and then "CurrentWidget changed back to 44ma, and its been the same since then.
now my battery's at about 40%, and its the same still...
anyone??!!
BumpbumpBumP.
search for power tutor in market
mariosraptor said:
search for power tutor in market
Click to expand...
Click to collapse
I installed it and it gave the same reading (44mah).
The problem is i want to know what it means for the reading to be the same at any given point. Whether the screen is on or off, or the cpu is at 1Ghz or at 652Ghz(using setcpu).
Can someone shed some light here please?
mean no disrespect!! do you wipe when you flash roms? try to wipe battery stats also. do you use a task killer that somehow prevents the system from reading correctly? i know that this might sound dumb but you never know, i have seen alot of weirdness from the last expected.
edit:do you use setcpu profiles? if yes try and deactivate profiles or change governors.
jaikat said:
I installed it and it gave the same reading (44mah).
The problem is i want to know what it means for the reading to be the same at any given point. Whether the screen is on or off, or the cpu is at 1Ghz or at 652Ghz(using setcpu).
Can someone shed some light here please?
Click to expand...
Click to collapse
mariosraptor said:
mean no disrespect!! do you wipe when you flash roms? try to wipe battery stats also. do you use a task killer that somehow prevents the system from reading correctly? i know that this might sound dumb but you never know, i have seen alot of weirdness from the last expected.
edit:do you use setcpu profiles? if yes try and deactivate profiles or change governors.
Click to expand...
Click to collapse
i really appreciate the help you guys are offering... thanks.
alright, i'll tell you what i did:
1- i wiped everything (data, cache, ext, dalvik)
2- flashed the rom (defrost 6.1a)
3- after everything was up and running i charged the phone to the point where clarus battery(battery info widget) showed the phone was charged, also current widget changed the reading from 44 to 8 mah at this point.
4- rebooted into recovery and wiped battery stats
after i used the phone for a while and the battery lost about 10% or more, current widget went back to showing 44mah, all the way to the moment my phone turned off by itself cause the battery was empty (this was almost 18 to 20 hours later)
i use setcpu, the cpu speed is set to 245-728 using the On-demand governor. and there's one profile set for when the phone is on standby(screen is off), that one is set to 245-530(approximate) using either the conservative or the On-demand governors.
another thing is autobrightness, which i have turned OFF.
and lastly, i don't use a taskkiller, and i advise anyone not to use one as i got better battery life without one...(anyone who reads this, try it and see for yourself)..
the amount of the mah current being used by my phone is whats bugging me, i'v read another topic where people who were using Desire phones and the current widget were getting 25-40 when using the phone, and 3-8 when the phone was idle. but in my case, the number is always the same...
too much talking i know, forgive me, but this is in case anyone who wants to help has other questions ...
hello mates,
I have rooted my htc desire and installed redux 1.2 ROM(gingerbread) with a ManU kernel...When charging the LED changes to green precisely at 90% (which i dont have a major problem with as it will go all the way to 100% if kept on charge)..also the phone will die at 10-15% of battery...I have read other threads regarding this same problem and am wondering if its a calibration error or is the problem with gingerbread ROMs as someone pointed out...Otherwise the battery is fine...and gives me a decent 1-2 days of use with moderate usage...its jus the problem abt the 15% n going dead which is a lil troublesome as the fone has died on me many a time for that last important msg, call or IM...any help appreciated...cheers..
That's not really a problem. The green LED at 90% is normal for android (try to fix it with battery calibration, helps sometimes) and the shutdown at 10-15% is also normal. Just take the last one how it is, all batteries are different. Some phones shut down at 5%, others at 20%.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
noticed this on ICS dev rom too but also had it on my old G1
wipe cache,battery stats try diffrent kernel
stupidflanders1 said:
hello mates,
I have rooted my htc desire and installed redux 1.2 ROM(gingerbread) with a ManU kernel...When charging the LED changes to green precisely at 90% (which i dont have a major problem with as it will go all the way to 100% if kept on charge)..also the phone will die at 10-15% of battery...I have read other threads regarding this same problem and am wondering if its a calibration error or is the problem with gingerbread ROMs as someone pointed out...Otherwise the battery is fine...and gives me a decent 1-2 days of use with moderate usage...its jus the problem abt the 15% n going dead which is a lil troublesome as the fone has died on me many a time for that last important msg, call or IM...any help appreciated...cheers..
Click to expand...
Click to collapse
You should try calibrating your battery for the 10-15% dying problem.
And as for the 90% LED changing to green, all AOSP ROMs do that, so no worries there
What worked for me was charging it while the phone is on, when the LED turns green, power it off and charge it again till it turns green.
Repeat this twice and then reboot.
galdel said:
What worked for me was charging it while the phone is on, when the LED turns green, power it off and charge it again till it turns green.
Repeat this twice and then reboot.
Click to expand...
Click to collapse
This is to calibrate the battery. Some people find it useful to run a program called BatteryRepair, in my case I noticed a clear improvement on battery performance.
To avoid calibration problems with the battery, remember to unplug your phone when you flash a new rom!
Tapatalking
Turning off at 15% of battery with Supernova 2.4 ROM
I am using Supernova Xtreme 2.4.0.0 ROM, and my phone turns off at 15% of battery. My battery is freshly calibrated and this problem did not occured with LeeDroid ROM and with the stock ROM neither. On the Droidzon page I have found some info in FAQ section, which says the following:
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.
So it seems to be normal, connected to the ROM, and NOT connected to my battery (it is calibrated).
My question is (which goes to Droidzone firstly), what should I do, if I want to use this ROM, but I do not want it to turn off at 15% rather I want it to turn off my phone at 2%?
Sofokles_ said:
I am using Supernova Xtreme 2.4.0.0 ROM, and my phone turns off at 15% of battery. My battery is freshly calibrated and this problem did not occured with LeeDroid ROM and with the stock ROM neither. On the Droidzon page I have found some info in FAQ section, which says the following:
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.
So it seems to be normal, connected to the ROM, and NOT connected to my battery (it is calibrated).
My question is (which goes to Droidzone firstly), what should I do, if I want to use this ROM, but I do not want it to turn off at 15% rather I want it to turn off my phone at 2%?
Click to expand...
Click to collapse
I'm afraid this is not similiar to the issue in the FAQ. Your issue is that phone shutsdown at a level earlier than expected. The Data corruption issue is because the phone did not shutdown at the expected level and went down to as far as zero level of the battery, which resulted therefore in an untidy shutdown with no sync or clean unmount of data2sd partition, and hence ext4 errors. The 15% shutdown level is a normal soft shutdown prompt (which was missing in case of the issue reported by the user). The shutdown at 2% is the normal forced shutdown by OS.
As I said previously, your issue seems to be due to a poorly calibrated or defective battery, and it would help to do a calibration as per guides on XDA. If this fails, have the battery checked. To reiterate, it's not a rom issue and not something like a bug in the rom.
Thanks. So normally the phone with Supernova ROM should turn off at 15%. After that I have to be able to turn it on again, and use it till it drains to 2%, and shuts down finally.
For me it just shuts down at 15% and then when I switch it on and it boots up, the battery level shows 0% and it shuts down immediately.
Sofokles_ said:
Thanks. So normally the phone with Supernova ROM should turn off at 15%. After that I have to be able to turn it on again, and use it till it drains to 2%, and shuts down finally.
For me it just shuts down at 15% and then when I switch it on and it boots up, the battery level shows 0% and it shuts down immediately.
Click to expand...
Click to collapse
No, a normal rom would popup a warning at 15%, asking the user to shutdown. If he doesnt, it would continue, and then give additional warnings, and finally do a forced shutdown at 2%. If it shutsdown before that forcibly, it's something peculiar to your hardware.
Ooops, so Supernova ROM should behave exactly the same way as a stock ROM (or any other) does in terms of warnings and shutdows.
I might try to do something with battery calibration. Should I do it before or after flashing Supernova? Or it does not matter? If I flash a new ROM, does it delete battery logs or it stays as it was before flashing?
Sofokles_ said:
Ooops, so Supernova ROM should behave exactly the same way as a stock ROM (or any other) does in terms of warnings and shutdows.
I might try to do something with battery calibration. Should I do it before or after flashing Supernova? Or it does not matter? If I flash a new ROM, does it delete battery logs or it stays as it was before flashing?
Click to expand...
Click to collapse
Correct. For all intents and purposes, Supernova is exactly like a Stock rom. Difference is only in where internal apps are stored.
The so called calibration is just a file at /data, which means it will be wiped when you do a wipe for rom install.
[Update] Problem solved. I flashed UOT battery MOD after first boot (not before). Now it works perfectly.
A flashed the ROM again, did the battery calibration several times, but the phone keeps turning off at 15%. I checked battery voltages at different levels of battery, and I experienced that at 16% it is 3635 mV, then it turns off below 15%. When I turn it on, battery level is 0% and the voltage is 3390 mV, and when it is charged up to 1% it is 3723 mV, which is higher than it was at 16%. What is wrong here? Actually I use UOT kitchen battery MOD, can this confuse the system somehow?
can someone share with me the safe and effective ways to calibrate battery after flashing new custom rom,i love flashing rom,so i think my battery stat become weird,already try many method from internet,but still not satisfied,please someone help me..
Sent from my LT18i
I only use the app BatteryCalibration available in the market. It's simple and easy to use.
Sent from my LT15i using xda premium
is it usefull to use a Battery Calibrator?
I have done almost always battery calibration with all my androids.
-Battery Calibration from Market
-Load battery full, do calibration
-Use battery till phone shutdown
-Load battery full when its turned off
After these steps regular use and battery acts like it should
In CWM go to advanced - batery calibration
do this with 100 procent batery
let the phone run dry
charge 100 procent while phon eis still turned of.
You can repeat this until it is good again
good luck
i try latest doomkernel,from the review it said that battery use just average 1%per hour,but when i try it,my battery drain faster,in 6hour my phone dead,so i think maybe i miscalibrate,ok i will try all the method above,thnx for help
Sent from my LT18i
bumax said:
I have done almost always battery calibration with all my androids.
-Battery Calibration from Market
-Load battery full, do calibration
-Use battery till phone shutdown
-Load battery full when its turned off
After these steps regular use and battery acts like it should
Click to expand...
Click to collapse
Same advices from me.. I quote...
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
I've i9195 with stock battery and rom, all was normal. Then I replaced it with double sized battery+new back cover. Not a microUSB batterycase. After many cycles and weeks of use it still didn't calibrated to new capacity. Fully charged battery lasts about a day and phone shuts down. If I switch it back ON after couple of minutes - I see 50% charged and can use phone another day.After second 'full discharge' I'll have about 15% more. All techniques for 'calibrating' battery with deleting batterystats doesn't work. Charge, off, remove bat, wait, place it back - either. /sys/class/power_supply/battery/uevent have string POWER_SUPPLY_ENERGY_FULL=1940000000 and it is always the same. So phone simply downcount from this level and tells that charge is 0% while voltage is about 3.7v. Interesting that "energy_full" file has number of 3880000000 but it seems that it's not used in calculations.
After all I installed CWM, root, cyanogenmod 11 and used it for about a week. SAME problems, except that "energy_full" is 1940000000.
I want to solve this very much, I can program or recompile kernel, if needed. It's pm8921 charger ic there. Maybe this number was programmed in it in factory mode or smth. Maybe threis a way to correct it. Thanks in advance.
Same here with stock-rom, CyanogenMod and MoKee's rom.
I think the only way will be to recompile the used kernel with the correct value of 3880000000 instead of 1940000000 in file "drivers/power/pm8921-bms.c" in kernel sources (function "calculate_fcc_uah", part "scalefactor". Scalefactor has to be change into scalefactor *= 2.
Huge work for a little problem...
Instead of making any advanced config, have you tried this little app (needs root privileges)?
https://play.google.com/store/apps/details?id=com.nema.batterycalibration
After migrating to CM11 my battery was draining very fast. I used this app and it apparently fixed a part of the issue (battery still drains fast, but not as fast as before).