Develop Bugs

Kaiser Battery Status [kernel mod]

NOTE: I don't post kernels here anymore: look for my changes in the standard kernel now.
This thread is still useful for battery discussion, if you like.
I have gotten tired of seeing my battery go from 90% to 15%.
Why can't it go smoothly from 100% down to 5% or less, and back up again?
Why does nbheditor have to apply a 1.6 multiplier for battery capacity?
Can we get the temperature sensor working?
I'd like to get this fixed, and would welcome discussion.
First, in the new or old kernel, the battery status is managed by the file:
kernel/arch/arm/mach-msm/board-kaiser-battery.c.
I have several proposals:
a) Change the default KAISER_BATTERY_RATING to 1350, since the equations really do work out correctly, that the rating should match in mAh. Note: in the kernel, that's 2160 = 1350 * 1.6.
b) Add a thirty second maximum for voltage and current, before using them to guess the battery level. At first I used averaging, but maximum works better for old batteries.
c) When booting from HaRET, scale the battery level because Windows does it different. I don't understand how Windows does it, but I have figured out a scale factor that works.
d) When the ds2746 reports that it has lost power, assume that the battery may have been changed, and do a coarse recalibration based on voltage and charge current.
e) Eliminate the minimum of 15%: let the meter go all the way to zero.
f) Allow battery level to be set to any value at any time.
g) Report what the kernel thinks the capacity should really be.
h) Use ds2746 units directly since nbh-editor already scales mAh to units.
Also, questions:
1) How to convert the thermistor resistance (I think it is aux0r) to temperature?
2) Would be nice if the dynamically-adjusted capacity could be stored in flash. I don't know how to do that, but I know how to report it.
3) Should we have an option on the boot menu to manually set the battery level?
I have edited the new 2.6.34 kernel to act as I propose.
Since the modules must match the kernel version you are using, I have included modules separately.
Warning though that, although it seems to work properly for me, it might do bad things for you, especially to your phone's battery. In particular, the Polaris needs to be tested since I don't have one.
NBH file: for NAND install. Use nbheditor to edit, but put your battery's capacity under "advanced settings". For attempt #6, you can use the standard setting.
ZIMAGE: for HaRET install. Edit your default.txt to contain:
board-kaiser-battery.battery_capacity=2160 (your true battery capacity in mAh * 1.6)
board-kaiser-battery.haret_divisor=2200 (use a WinMo -> android scale factor of 1000/2200)
CAUTION: The 2.6.25 NBH images probably don't work. I'll have to learn how to make them!
NOTE: Attempt #7 and later are in the standard kernel, so are no longer posted here.

just setting this up on Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS15] [9/3/10]. I will let you know how it goes.

WOW, I´m glad somebody finally took this matter as serious as it is I´m not saying that others guy in here haven´t provided advice on this, it is just that nobody, afaIk hadn´t come with a "downloadable" solution, the only thing close to a real fix to me was to use the nbh editor and put the recommended capacity for my battery, it helped a lot to be honest cuz I used to get no more than 15 minutes of battery life, and after that I can use it for a few hours, unless I turn wifi and bluetooth of course, then it gets down to 15%, well I hope this really works cuz I´v been strugling with this for more than a month and I love android so much that I flashed on nand even though I knew about this problem, and I was about to give up on this, (was I?), thanks for this, I hope we get good results!!!

Isn't it that the latest kernel for froyo is 2.6.32? Is that your own build?
I wanna try your version. So far, how does all features? How is it compared to DZO's kernel?
More power!

Ok so I had lockups with Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS15] [9/3/10], I am loading up dzo's current Froyo and his 9-9-10 kernel for some base testing then I will install your kernel and updates and test again.

So, how do I install this? i mean, do I:
1- flash the new nbh.
2- install theandroidupdate.tar
done? I mean, do I have to do the whole "calibration dance" with it again or something? Or after i do this it will (in theory) perform as normal as it should? btw my battery is about a month old, so I guess if i put 2000 in advance mode, (not mah) it would be ok, right?
ps: I have donut installed, so I guess it might not work, but heck I´ve got to try this anyways, so I´ll go ahead and install it, in case it works, would you be able to tweak a donut kernel for us?. thanks in advance.

zack, how is it?

so far with dzo's latest froyo build and the attached kernel and update things have been very stable, however the battery is at 100% constantly. hopefully this will change as the battery is drained and recharged.

The kernel is dzo's with the experimental battery file.
Not ready for prime time. If your configured capacity is wrong, it gets calibrated as you run, but the calibration is not remembered when you reboot.
Sent from my Full Android on Vogue using XDA App

I'm looking for opinions on the individual questions in the first post. Especially, does anyone know how the kernel can store battery_capacity s it remains persistent after reboot?
If you search dmesg output for ds2746 you can see what the current capacity is.
Sent from my Full Android on Vogue using XDA App

I´ve installed it and after a while of letting both wifi and bluetooth on, it finally died and showed me 1% left and powered down all by itself, I had never seen 1% left on android, so that´s a good thing I guess, but after I connected the charger it started charging just fine, but in the console after typing dmesg it tells me that the battery has 4079mv and 54/3200 units, but I think that if the battery has 4079mv, it means it is fully charged, am I wrong? if anybody reads this please confirm this because I put it is still charging I don´t want my kaiser to blow up on me, lol. thanks.
ps: while charging it isn´t showing the amber led, but it has a red blinking led as when the battery is completely empty and not charger is connected (but in android the battery icon has the charging animation).

elander said:
I´ve installed it and after a while of letting both wifi and bluetooth on, it finally died and showed me 1% left and powered down all by itself, I had never seen 1% left on android, so that´s a good thing I guess, but after I connected the charger it started charging just fine, but in the console after typing dmesg it tells me that the battery has 4079mv and 54/3200 units, but I think that if the battery has 4079mv, it means it is fully charged, am I wrong? if anybody reads this please confirm this because I put it is still charging I don´t want my kaiser to blow up on me, lol. thanks.
ps: while charging it isn´t showing the amber led, but it has a red blinking led as when the battery is completely empty and not charger is connected (but in android the battery icon has the charging animation).
Click to expand...
Click to collapse
Do not worry. Nothing will happen to your phone. Electronic circuits inside the battery takes care of it. You have to repent attention to the current charge (mAh). When the value falls below 200mA, then the battery is full.

I've had two crashes (phone totally frozen, unresponsive) when on charger and full battery. Probably a coding error somewhere in this experimental file.
I'm also wondering which phone models use this source file?
Do some of them perhaps have different resistor values?
Do we have any historical information about why 10M Ohm was chosen as a resistor value, rather than 15 or some other value?

Millence said:
Do not worry. Nothing will happen to your phone. Electronic circuits inside the battery takes care of it. You have to repent attention to the current charge (mAh). When the value falls below 200mA, then the battery is full.
Click to expand...
Click to collapse
Thanks for replying, I know that the battery has some sort of sensor built in that tells the OS when it is full, but since we are dealing with calibration here (a.k.a I don't know when it is full or empty) I kinda freaked out a bit there, but thanks to your answer I feel (a little) relieve, the thing is that it's been plugged for more than two hours (I had to unplugged it cuz I had to return home from work) and dmesg still says something like: 4180 mv 145mah 50/100 (1604/3200 units) so when you told me about the current charge below 200mah you meant the number that appears on dmesg right after the (4180)mv? in this case it is 145mah, if so, does that means that the battery is already fully charged? cuz according to android it is only like 52% full. should I leave connected or should I unplug it (it is already unplugged just in case,lol). thanks.

It depends. It looks like your battery currently has 1002 mAh of charge, out of 2000 mAh. I doubt that you have a 2000 mAh battery. If you really have a 1350 mAh battery, you are more like 75% full.
I chose a lower limit than 200 mA for when the kernel thinks you are 100% full based on charge, since my phone charges at under 200 mA when connected to a computer, regardless of how full it is.
Please include what kind of phone you have. Otherwise I will assume you have a Kaiser.

n2rjt said:
It depends. It looks like your battery currently has 1002 mAh of charge, out of 2000 mAh. I doubt that you have a 2000 mAh battery. If you really have a 1350 mAh battery, you are more like 75% full.
I chose a lower limit than 200 mA for when the kernel thinks you are 100% full based on charge, since my phone charges at under 200 mA when connected to a computer, regardless of how full it is.
Please include what kind of phone you have. Otherwise I will assume you have a Kaiser.
Click to expand...
Click to collapse
I do have a Kaiser, and I do have a 1350mah battery, and as you said on the first post I edited the nbh to 2000 capacity using the nbh editor, so did I misunderstand first post and instead of 2000 capacity in advance mode I should have put 1350mah in simple mode, or should I have put 1350mah in advance mode in order to make android recognize the capacity of my battery? cuz as I see it now it seems it is the other way around now, cuz before android used to think that the battery was full when in fact it wasn't and now even when full android thinks it is not.

Put the battery rated capacity (1350) in the advanced setting, so it won't be multiplied by 1.6.
The conversion from dmesg units to mAh is: 625 x units / 1000 = mAh. Probably dmesg should show mAh so we don't have to calculate.
Sent from my Full Android on Vogue using XDA App

I am trying to use this kernel with cyanogen build, but it does not boot.
When I start haret it hangs. It moves the staus bar to the bottom of the screen and then freezes. (I can only reset via stylus os sim card cover)
The files I have in andboot are:
zImage-2.6.32-froyo-06-09-10_22 - the original zImage
initrd.lzma
zImage - the zimage with the battery fix
androidinstall.tgz - cyanogen install pack
androidupdate.tgz - update for the battery fix
startup.txt - modified for the battery test (zImage name and battery capacity)
haret-for-kernel-2-6-32.exe - haret
my startup.txt file is:
Code:
#alloctest 0x2000
set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=2 board-htckaiser.panel_type=1 hw3d.version=1 board-kaiser-battery.battery_capacity=1350 board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1 clock-7x00.a11=500"
boot
do I need to use another haret or initrd?

yesterday I left the phone connected to the charger all night and when I woke up (about 5hours and 30 minutes later) it had the green light turned on so it means that it got charged full, and dmesg gave something like this: 4180mv 28mAh and 100/100 (2076/2076 units) I gotta tell you, I had never seen such "low" values on units, its kinda strange, anyways I unpluggued it and went to work, so here I am, I´ll report back in a few hours after I stress this thing a bit to see if it really got all the "juice" the battery can take.
ps: I haven´t tried putting the 1350 (MAh) in advance setting, because since it says that it is charged (I know it may still be wrong) I decided to give it a go to see how it works with the current settings, after finishing testing this, I´ll try with 1350.

I don't know the HARET problem, sorry. Everything you are doing looks right to me. Perhaps you need to wait until this experiment is mature enough to be in a dzo kernel. Sorry!
Sent from my Full Android on Vogue using XDA App

HTC Desire Battery Life

I have a question regarding my battery life. Yesterday night at 10:00 pm i played +/- 40 minutes on games like Angry Birds and used my 3G connection for about 10 minutes. My battery dropped from 100% to 61%. When i didnt use my phone (just idle mode) @ 11:46 pm i wanted to check how much battery i had left today in the morning (10:00 am) ..... it whas completely dead 0% .... i have this phone since august but if i knew the battery life whas so crap i would have picked another device.
Is there a way to improve it ??? since i read in diffrent topics people can use their desire for 2 days without a recharge.
- Not rooted
- Froyo 2.2

The HTC Desire is a smartphone running powerful mobile OS and a lot of additional gadgets like GPS, ...
So comparing battery life is impossible.
You can get a battery life of a mobile phone/week if you use it like a mobile phone: No GPS, no data, no playing games, no surfing, just occasional talking. So the battery life is normal and good, compared to mobile phones.
But normally you use it like a smartphone, thus you use it daily, play some games, ... which results in a battery life of a few hours (navigation) up to two or three days (moderate use), with an average battery life of a day (heavy use).
However, one thing for sure: Something is wrong with your phone.
This dosen't mean something is broken, rather you use an app/setting, which causes the battery drain, so you did something wrong, you're the failure, not the device!
Playing a game drains the battery fast. The display is on, probably max. brightness and the CPU and GPU is working like hell. It also gets warm, so you can feel the increased power consumption.
In sleep mode however, it should consume much less than it did for you. Maybe 2% each hour.
So to find what app you've installed or what app you keep in the background running, install a program like Android System Info and take a look at the task list, CPU load should be around 10% if you wait a few seconds and do nothing.
Take a look at the running services (android settings, applications, ...) and check if you really need all of them or if an app is active which you don't use. Then don't force close it, only idiots do this, rather open the app and deactivate the service (like automatic updating)
Next option: Test the battery life again. Maybe an app crashed and caused the increased power draw and now everything is working fine again and battery life is normal again. Then it's impossible to find a culprit with Android System Info.
Also tell us what settings you've activated: GPS/Wifi/Data/BT/...

This is happening because, some process not letting your device to sleep..!!
All you need to do is type *#*#4636#*#*
and check the battery history ,you'll get to know which process is using your battery, and remove that application.

UpSpin said:
The HTC Desire is a smartphone running powerful mobile OS and a lot of additional gadgets like GPS, ...
So comparing battery life is impossible.
You can get a battery life of a mobile phone/week if you use it like a mobile phone: No GPS, no data, no playing games, no surfing, just occasional talking. So the battery life is normal and good, compared to mobile phones.
But normally you use it like a smartphone, thus you use it daily, play some games, ... which results in a battery life of a few hours (navigation) up to two or three days (moderate use), with an average battery life of a day (heavy use).
However, one thing for sure: Something is wrong with your phone.
This dosen't mean something is broken, rather you use an app/setting, which causes the battery drain, so you did something wrong, you're the failure, not the device!
Playing a game drains the battery fast. The display is on, probably max. brightness and the CPU and GPU is working like hell. It also gets warm, so you can feel the increased power consumption.
In sleep mode however, it should consume much less than it did for you. Maybe 2% each hour.
So to find what app you've installed or what app you keep in the background running, install a program like Android System Info and take a look at the task list, CPU load should be around 10% if you wait a few seconds and do nothing.
Take a look at the running services (android settings, applications, ...) and check if you really need all of them or if an app is active which you don't use. Then don't force close it, only idiots do this, rather open the app and deactivate the service (like automatic updating)
Next option: Test the battery life again. Maybe an app crashed and caused the increased power draw and now everything is working fine again and battery life is normal again. Then it's impossible to find a culprit with Android System Info.
Also tell us what settings you've activated: GPS/Wifi/Data/BT/...
Click to expand...
Click to collapse
Brightness is already said to medium, i also turned of those life wallpapers and it still drains like ****. When i look at the battery status it says battery life is good. Maybe a application that is running i dont know, ill try to find it out. So far i have a few apps installed which i rarely use.
harish.awe said:
This is happening because, some process not letting your device to sleep..!!
All you need to do is type *#*#4636#*#*
and check the battery history ,you'll get to know which process is using your battery, and remove that application.
Click to expand...
Click to collapse
Thanks will check it out and see what it does now in idle mode.
Idle mode 01:28 pm starts now, will post results in a few hours.
Edit: It's 02:00 pm here and i already lost 4% battery, its 96% now , i did *#*#4636#*#* and checked battery status and it seems wifi is in full use 99.7%. I will turn this off but what about the 3G connection
Edit2: It's 2:24 pm here and the battery status is 92% now, i reveived +/- 4 emails in that time. I checked the status in battery indicator pro and this is what it says
Android system 37%
Mobile Stand-by 22%
Phone inactive 15%
Wi-Fi 15%
view 11%
nothing else......i am really lost now.

Is my battery damaged/broken ? .... how can i reset/callibrate the battery ? or should i contact the shop where i got this phone from for a new battery ?

don't worry, lots of people are having bad battery lifes, and angry bird drain your battery really quickly, so it is quite normal, especially on AMOLED desires.

h3llb3nd4 said:
don't worry, lots of people are having bad battery lifes, and angry bird drain your battery really quickly, so it is quite normal, especially on AMOLED desires.
Click to expand...
Click to collapse
Yeah i have AMOLED
PS: After 30 minutes without touching it the battery is still 92%.

you could install setcpu and set profiles to save battry life

Might try that.....but after 1 hour the battery is still 92%.....i guess wifi drained my stuff down all the way as i am pretty sure i turned that thing of last time.
i will do some more tests later....
Edit: After 1 and half hour the battery is still 92%, guess the stock rom isnt that bad .

MichelN said:
Edit2: It's 2:24 pm here and the battery status is 92% now, i reveived +/- 4 emails in that time. I checked the status in battery indicator pro and this is what it says
Click to expand...
Click to collapse
Its not 5:09 pm here and the battery is now 91% (idle, not touched)....guess wifi what the bad thing on my phone.

Tested the battery last night and must say i am happy with the results
10:00 pm yesterday the battery whas 60%, today i looked back @ 11:24 am and the battery just dropped with 10% (3G is on), i didn't touch the phone since then.
Stock Rom / Froyo 2.2
The battery drain came from wifi

I wrote HTC about the battery and they just sent me a brand new one So now I have 2 batteries and I think I'm happy DD

You can check your battery usage with a widget called "currentwidget" (search for it on this forum)
Usually on SBY with radio ON my phone drains from 3 to 4 Ma and 2ma in plane mode. (sounds good with a 1400mah battery)
In heavy usage, it can go anything from 150 to 500ma (ie: playing game with wifi ON)!!
For nice graphics, try to install "battery snap" too.

From HTC themself:
“To also help with Battery Life you can do these steps exactly:
1) Turn your device ON and Charge the device for 8 hours or more
2) Unplug the device and Turn the phone OFF and charge for 1 hour
3) Unplug the device Turn ON wait 2 minutes and Turn OFF and charge for another hour Your battery life should almost double, we have tested this on our devices and other agents have seen a major difference as well“
Click to expand...
Click to collapse
also found this on a swedish website (i useed google translate, to lazy to manually translate it)
A known problem with the new update of the HTC Desire to Android 2.2 Froyo is battery life. How users have experienced the change is highly variable. Several said that battery life has improved, some even talk about a major improvement. The others have had problems that the phone charges from a fully charged battery several times in one day. If you have experienced such problems, there are measures, some simple, others more complicated and time consuming. Below I list things you can try, the lightest at the top.
# 1 Look what it's drawing power. Go to Settings> About phone> Battery> Battery usage or enter * # * # 4636 # * # * on the keypad and look around a bit. Is there anything that seems abnormal, or any program that seems to be the culprit, uninstall simply the application and see if that helps. While you can uninstall applications you believe is in the background and drag the cream from the phone's battery. Some applications may slip into the "Android System" in your battery history.
# 2 Uninstall system control and task killers. Advanced Task Killer and similar programs do more harm than they help. It is unfortunately only to realize this and stop using them. Android is an OS made for having many applications driving on the background. The operating system puts himself applications you do not use the idle to conserve battery power. Different programs that measure your performance on the phone, for example, Task Panel never sets in idle and therefore system resources continuously. If you have such software installed it may be time to consider uninstalling it. More on why the task killers and Android do not go hand in hand in to read this article by Android developer Dianne Hack Born.
# 3 Clean your home screen. It can be a good idea to try if it helps to clean up your Home screens from various widgets.
# 4 Do a soft reset. Discharge the battery completely (not that the phone is turned off), turn off the phone manually, remove the battery and reinsert it, restart your phone and put it on charge. This may have some effect and provide an improved battery life. Such a restoration known as a soft reset and should be tested before you do a master reset (hard reset).
# 5 Do a "hard reset". Have you done all the methods above are still not noticed any major difference? Then it's time to do a master reset of the OS. HTC have said they for some users might went wrong during the update to Froyo causing poor battery life, and when it is easiest to do a reset to get to grips with the problem. Although Android automatically sync contacts in the "cloud" so it might be a good idea to make a backup of your contacts (Contacts> Menu> Import / Export). Note that when you do a hard reset resets the entire phone, including messages, settings, themes, installed applications, etc. These are not the contents of your SD card. There are two methods to restore your phone, do a google search on "hard reset desire," so there are many simple guides. After restoration, the idea not to install any applications you had installed before. Install the programs one at a time and not too many at once.
Click to expand...
Click to collapse

Life of a Battery

Hello guys, I am experiencing some troubles with the battery of my beloved Desire. I am using Oxygen 2.3.2 right now. The problem: every time the battery reaches 20% of charge the phone dies. But when I plug it and it start charging it says it's at like 2-3%. Now, one of my friend suggested that since the battery is quite old (I charged it every day since april 2010), it can have problems when it reaches low voltages, so I should change it. Do you have the same opinion or you think it's just a calibration problem?

Calibrate. If there is no change, replace the battery. Isn't that simple enough?
via xda app

Install spare parts . Go to Battery information . Check Battery health . If it doesn't say "Good" then you need to replace the battery .
Also try a calibrate as stankyou suggested .

I'm having the same issue. Tried calibration a few times and my battery health says good. Glad that my new ROM is better on battery so I don't get down there as often, but it is still annoying.

Hello,i had the same problem with my desire's battery,it went down at 20%.
what i did was to follow an tutorial from Oxygen rom forum,an user called paschadee posted this:
Advanced Battery Calibration (tested and verified on Oxygen + bravoGSM)
Intro:
This will actually calibrate your battery, unlike other methods out there. After calibration, empty will be at 0% not some arbitrary value like 18%. For added comfort, you can perform steps 1-5 until you are comfortable with the routine; on the first run stop at step 5, don’t plug in and watch where your battery dies to give you an idea of the time window available – then on the next run you will know when to plug in. This ensures a smooth and error-free routine. You don’t actually need to do this since the app will tell you when to plug in. Once you’ve done a dry run, plug in, charge for a few minutes until the phone doesn’t shut off when you disconnect the charger, and repeat the process.
Caveats:
When entering the values for the battery registers, pay particular attention that the entered values are the correct ones which are shown below. Failure to enter these values correctly could result in your battery being permanently bricked. You have been warned!
Pre-requisites:
• _thalamus kernel >= 2.6.35.14_r2 RC1, installed (check kernels section)
• A functioning brain (ask your parents about this)
• Patience
• Jon Richards’ “Nexus One Battery Calibrator” application a.k.a. NOBCAP (available on android market), installed
• An almost dead battery (that is mis-reporting its capacity) with what you think is about ~2% remaining – i.e. if your battery dies at 18%, get ready at about 20%
• AC battery charger at the ready
Process:
1. Set your screen time-out to 10 minutes.
2. Run NOBCAP
a. If General tab displays fields but no values, kernel is wrong, see pre-requisites
b. If General tab displays fields filled with values, kernel is right, enable airplane mode on the phone
3. In NOBCAP, menu --> settings -->
a. Check: GPS polling, ACR adjustment, advanced options
b. UNcheck: Airplane and Wake lock. Go back.
4. Go to LearnPrep tab
a. Set age: 100% --> save
b. For
i. OEM batteries ; Set mAh: 1452 --> save
ii. Aftermarket batteries ; Set mAh: 1650 --> save
c. Register: 0x66
Value: a4 --> save
d. Register: 0x65
Value: 06 --> save
e. Register: 0x10
Value: 04 --> save
5. Go to LearnMode tab
6. Scroll down and Set Detect Learn Mode to ON.
7. When Real-Time Voltage (µV) <= 3201000, i.e. when the battery is “empty”, the app will prompt you to quickly plug in your charger.
8. If you were successful here, the learn-flag LEARNF will now be lit and your battery charging.
9. LYPTFA - Leave your phone the .... alone.
10. When charging completes, the CHGTF flag will be lit, Battery Status Register 0x81 displayed, your battery calibrated.
11. Unplug. Reboot.
Supplementary:
The application monitors the battery chip registers. As charging nears completion the pulse current (mA) sent to the battery gradually diminishes in amplitude. This will tail off at about -20mA which the battery interprets as “charging complete” and the battery registers are stamped with its newly determined capacity values. Activating the screen, or any function which subsequently draws current pulls the charge current above -20mA and which the battery detects as charge complete – this is why you should LYPTFA. It’s okay to set an extended screen-timeout and occasionally touch the screen to reset the screen-off timer (i.e. keep the screen on) to keep an eye on charging without affecting charge current.
As an additional experiment, install JuicePlotter, run it once, and enable graphing. This will also monitor dis/charge cycles and give you an idea of the memory effect that the battery suffers from.
Click to expand...
Click to collapse
I did everything said there and now my battery dies at exactly 1%.
It also appears to last much longer than it used to.
All credits for what i qouted goes to paschadee
Good Luck!

I just tested it and my learn flag turn of after a couple minute? does it mean that it's not working? Also, in "message" it's telling me " -to re-calibrate your battery..."
Thank for answer.

[Q] Battery percentage bug?

I have this problem since i'm using custom roms, but it happened just a few times, so i wanted to know why. My phone says e.g there's 27% left but then it it says battery empty and turns off, used insertcoin nightly,stable and now Runnymede AIO
. Is there any way to get the real percentage shown? I already wiped battery stats..

Maybe you should calibrate your battery, wiping batery stats only is not always enough.
Here: myhtcdesire.com/tutorials/how-to-improve-your-battery-life-calibration-tutorial
or here: http://forum.xda-developers.com/showthread.php?t=755903

If it says 27% then goes off that definitely needs calibrating. Often its about 15% which is actually when the desire turns itself off to protect the battery

rootSU said:
If it says 27% then goes off that definitely needs calibrating. Often its about 15% which is actually when the desire turns itself off to protect the battery
Click to expand...
Click to collapse
I could hardly imagine such solution would be implemented in such untidy manner. All gb sense roms have that, yet aosp turns off at 1% as it should.
SwiftKeyed from my HTC Desire using XDA App.

Before setting up new Roma need to do full вайп including and batteries.
Try. if not yet the Council will help Ladies! is done through recovery.
(apologize for bad English)
---------- Post added at 05:54 PM ---------- Previous post was at 05:43 PM ----------
Calibration of the battery precise, the instruction:
1. We unload the accumulator up to 0 % (while itself it will not be switched off), having started video, or other ways.
2. We take out the accumulator from a handheld computer, we wait about one minute, we insert back (we do not include the device!!).
4. We put on зарядку. I shall repeat, the device is not included! (network з.у. 220В).
5. We leave to be charged up to a full level (the red indicator will be replaced on green, usually it is hour 3 on time).
6. After зарядки we take out the accumulator, NOT including a handheld computer and we wait about one minute.
7. We insert back. Now it is possible to include!
P.S. Sometimes at performance of this procedure the indicator maybe green it is primary at зарядке, all the same three hours it is charged, then the device I include, I charge while the indicator with red does not become green, I take out the battery, I wait minute, I insert аккум into a handheld computer. We unload the accumulator up to 0 % (while itself it will not be switched off), having started video, or other ways.

Mmmmmm this send interesting and rather typical for you.
https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
Sent with Desire.

you do wipe battery in clockmod

[email protected] said:
you do wipe battery in clockmod
Click to expand...
Click to collapse
You didn't read the post above yours, did you?
You got 10 posts. Now stop posting next to no sense information and get your grip.

I can confirm that the phone should shut off around 15% battery. This happened consistently to me running Oxygen 2.3.2.

Calibrate the battery HTC Desire
(Via USB will not work-do from charging a ROOT and
recovery modificirovanoe)
1. charge the body until the green signal diode.
2. disconnect the charging and shut down the body.
3. connect the charger and charge the vyklûčennomu body before the Green diode.
4. Oklûčit′ charge, include body load to the end, turn off and then charge to green diode.5. disconnect the charger,
, not including the body down the back button (or press the volume down) and press the power (enter in recovery), do wipe battery stats.6. Restart
.

calibrate htc 10 battery

I am running viper rom and i facing some illogical Battery percentage
Any idea how to calibrate it
I ve tried many apps from play store and no results
And i even tried the hard way by pressing the 3 buttons while the phone is off olso no luck
Any idea?

Calibrating the battery on Android devices
Method for rooted devices:
1. Discharge your phone fully until it turns itself off.
2. Turn it on and let it turn off again.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Unplug your charger.
5. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on the screen as well.
6. Unplug your phone and reboot. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
7. You want to repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without being plugged in.
8. Now, install the Battery Calibration app attached below and, before you launch it, make sure your battery is at 100 percent again, then reboot.
9. Immediately launch the app and recalibrate your battery stats.
10. Once you've calibrated your battery, discharge it all the way down to 0 percent and let your phone turn off again.
11. Fully charge the battery one more time without interruption while it's switched off, and the Android system's battery percentage will be reset.
Note that all the app does is wipe the accumulated data from the batterystats.bin file giving you a new clean slate to work with. This method is also called, "training the battery" and should be performed infrequently. Maybe once every four months or so.
References:
https://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
.

Aurelius99 said:
See if this will help you.....
https://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
.
Click to expand...
Click to collapse
I ll give it a try

I would also note that this would be good to do right before installing a battery monitor app like Gsam or BBS. :good:

comstockload said:
I would also note that this would be good to do right before installing a battery monitor app like Gsam or BBS. :good:
Click to expand...
Click to collapse
I haven't calibrated mine in a long time. Getting ready to do it right now.

How successful was this calibration?