Database Users

Post your Battery mA consumption. This may help solve battery problems...

The idea of this post is to make a statistic research about the battery drain problem. Maybe this will make us understand the cause of the battery problems -since I couldn't find something that solved the battery problems of all users.
I have checked these posts (and some others)
http://forum.xda-developers.com/showthread.php?t=295191
http://forum.xda-developers.com/showthread.php?t=287165
and the "Battery SOLVED" topic
There are 3 solutions (they are post in Faria Wiki)
-One is mess with the keys
[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
...
-Another is mess with the key
HKLM/Drivers/SDCARD/ClientDrivers/Class/SDMemory_Class/DisablePowerManagement
-And a third solution is to Flash a ROM with FULL battery & let it drain comletelly afterwards.
---------------------------------------
Using the "battery status"today add-on I can say this:
The first time I installed faria 3.3 ROM I had huge memory drain problems
I notised that even in stand-by my phone "ate" about 124mA
The registry memory tweaks didn't change this much - maybe 118mA.
The battery in this codition lasted at most 18hours...
I reflashed Faria3.3 with the mobile FULLY charged,let it discharge fully and now I have 84mA consuption if phone goes to sleep and 97mA when not used. Now battery lasts about 48hours without much usage.
With the [HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms] etc keys changed and with manually shutting down the Wireless Monitor Service(WMS7) was 42mA .
Note: I have Faria3.3 ROM & GSM 2.19 .
In another mobile phone I checked, with 2.17 OS rom & GSM 2.06.10 radio, I see that the when phone is not used the battery drain is 24mA !!!!!
This phone does NOT have the registry tweaks enabled and even with backlight it still stays in 24mA..
Please, post your mA consumption here and say what you have enabled.
Btw, anyone knows why Wireless Monitor Service(WMS7 was enabled (started) even though I have turned off WiFI,bluetooth & IRDA?

152mA, was ALOT higher when i had 5+ programs running, around 200

I have Faria's WM6 and run about 57mA in standby, 125 during normal operations.

Here is my first contribute to this outstanding forum.
Hope this is usefull insearch of the power drain on some devices.
Note:
My phone does NOT have the powermanagement registry tweaks enabled.
And is an clean install with the Faria WM6 (The real Thing) rom.
So there ain't much running.
Just ordered Wisbar Advanced + desktop so hope to see more readings later this week after fully fine tuning my device.
My device
Orange SPV - M3000 Faria WWE WM6 (G3 Unlocked)
IPL/SPL: 2.26
Radio: 2.61.11
ROM: 2.18.0.0
OC: CpuScaler - 130<->273mhz By BatteryStatus
Startup Services
CapNotify
SIPChange (Resco Keyboard)
Startclean
Today Plugins
BatteryStatus incl Tray applet
Running Hardware
Bluetooth= off
GPRS= off
Radio= on
WiFi= off
IR= off
Power drain Bat= 100% charged
Wakeup: 70mA (after 5 <-> 10 minutes)
Softreset: 258mA
Hardreset: 350mA
Standby + 50% backlight: 302mA
After charging: (and pulling the plug out) 180 -> 250 mA
All readings do not change until i manualy interrupt the current status off my device.
I mean if my device after wakeup says 219mA the reading does not change even when i run different software apps.
Even if the CpuScaler clocked 130mhz the reading will not change.
I think that BatteryStatus is broken or something else is interfearing with the readings.

i went from 175mA to 125mA... just by going from 0 to 1 with the next tweak:
HKLM/Drivers/SDCARD/ClientDrivers/Class/SDMemory_Class/DisablePowerManagement
i use Fario's rom..
trying other tweaks now..
ok:
so without doing anything it just suddenly dropt back to 64mA.... :\
ok:
booting takes 280mA
I recommend not to use these ::: they sucked out my battery even more.. from 125 to 247
[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\Irsir1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\PPTP1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\L2TP1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0

Today i did made two changes on my device and noticed the following.
First i updated my Radio rom from 2.19.11 to 2.61.11. (No errors everything works fine)
I just wanted a better radio because the signal strengh overhere is verry bad.
This update has on my device an nice site effect.
Powerdrain dropped by several mA.
Wakeup: 61mA (after 5 <-> 10 minutes)
Softreset: 201mA
Hardreset: 299mA
Second i messed with the key
HKLM/Drivers/SDCARD/ClientDrivers/Class/SDMemory_Class/DisablePowerManagement
I did not notice any effect on this reg tweak

I am using Wizard 100 ( Cingular 8125)
EDGE ON 24x7
Fetch mail using poutlook every 10 minis
Notification & Task Running
WiFI OFF
decient battery life: fully charged battery comes to 1.5 days..
--tux

i dont know what i did.. but its at 42mA right now.. and sins my last post.. it was @ 76% battery.. and right now its @ 75%... that means more then 12 hours have passed.. and its only down by 1 %...
last post was @ 01:30 PM...

WOW!!!!!!!!!!~!!!!!!!!!
like i said.. it took a really long time for 1 %..
but the moment i sent an sms message... it went from 75% to 71%..!!!
damnnn

Seems as if batterystatus is broken: my readings dont update either: it seems stuck at the same mA-value all the time, no matter what I do, or which clockspeed I use...
Also: the powermeter keeps at 99% (had been 83% as well); it never changes : (

My battery from 100% to drop to 99% might take 8-12 hours , then from 99% to 90% might take few hours (maybe 1-3 hours).
This seems to be normal.
I'm using the mA consumption because if you have an 1250mA battery I think this is the best unit to measure battery.

My apologies, but which program are people using to measure battery life consumption and how does one tell which program is causing the problem? In the past week, I have noticed my battery life take a nose dive and I'm wondering if it is pRSS Reader that causing my problem. I installed a power saving cab found on this forum site and I will test it tonight. Thanks for the help.

It might also be worth considering usage of GPRS, Push email, WiFi, BT, etc.

Curious D said:
My apologies, but which program are people using to measure battery life consumption and how does one tell which program is causing the problem? In the past week, I have noticed my battery life take a nose dive and I'm wondering if it is pRSS Reader that causing my problem. I installed a power saving cab found on this forum site and I will test it tonight. Thanks for the help.
Click to expand...
Click to collapse
Be careful of power saving cabs. Some of them actually increase battery consumption.
I think most people are using battery status to check consumption.
BTW:
At wake up: 24-30 mA
When the phone has a signal, the consumption rate is low 24-30 mA throughout the day. When it is searching for a signal (normally at my work), the consumption is substantially grater. When I get back home the consumption goes back down to the normal 24-30 mA (I always have a signal at home).

calouro said:
BTW:
At wake up: 24-30 mA
When the phone has a signal, the consumption rate is low 24-30 mA throughout the day. When it is searching for a signal (normally at my work), the consumption is substantially grater. When I get back home the consumption goes back down to the normal 24-30 mA (I always have a signal at home).
Click to expand...
Click to collapse
Did you ever perform the antenna hack(i.e. adding xtra piece of foil) on your Wizard?

MethodMan said:
Did you ever perform the antenna hack(i.e. adding xtra piece of foil) on your Wizard?
Click to expand...
Click to collapse
No,
I never applied the fix.
I haven’t done enough research on the fix to justify applying it. Maybe when I get some extra time.
The signal goes in and out at work, so it's not a big deal for me!

Running an 8125 with Faria's WM5 3.3 ROM.
When I wake it up it's usually 51, or somewhere in the 50's anyway.
I just tried those powermanagement reg tweaks and had terrible results too :\

My wizard can last 3 days with moderate usage of wifi, phone calls, and movies. This happened after I followed the Battery Solved thread and reflash with official ROM and then I installed Xplore1.1. And for the first cycle after first time after fully charging overnight, I can get the 3days of continous battery life..
Since then, I have been monitoring CPU usage and it hovers around 1-5% (Battery status) when idle... Bear in mind that the current consumption value can be around 33mA to 150mA and still battery life seems to be good...
Weird but through...

calouro said:
Be careful of power saving cabs. Some of them actually increase battery consumption.
I think most people are using battery status to check consumption.
Click to expand...
Click to collapse
Thanks for the warning. I used the power saving cab that was posted from a link at the beginning of the thread.
http://forum.xda-developers.com/showthread.php?t=295191
(Second post)
Is that one okay? I'm not sure if it worked since I used my phone alot this evening. I have the standard ROM that came with the phone back in October. Thanks.

I get the solution for Battery Performance
jtrash said:
The idea of this post is to make a statistic research about the battery drain problem. Maybe this will make us understand the cause of the battery problems -since I couldn't find something that solved the battery problems of all users.
I have checked these posts (and some others)
http://forum.xda-developers.com/showthread.php?t=295191
http://forum.xda-developers.com/showthread.php?t=287165
and the "Battery SOLVED" topic
There are 3 solutions (they are post in Faria Wiki)
-One is mess with the keys
[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
...
-Another is mess with the key
HKLM/Drivers/SDCARD/ClientDrivers/Class/SDMemory_Class/DisablePowerManagement
-And a third solution is to Flash a ROM with FULL battery & let it drain comletelly afterwards.
---------------------------------------
Using the "battery status"today add-on I can say this:
The first time I installed faria 3.3 ROM I had huge memory drain problems
I notised that even in stand-by my phone "ate" about 124mA
The registry memory tweaks didn't change this much - maybe 118mA.
The battery in this codition lasted at most 18hours...
I reflashed Faria3.3 with the mobile FULLY charged,let it discharge fully and now I have 84mA consuption if phone goes to sleep and 97mA when not used. Now battery lasts about 48hours without much usage.
With the [HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms] etc keys changed and with manually shutting down the Wireless Monitor Service(WMS7) was 42mA .
Note: I have Faria3.3 ROM & GSM 2.19 .
In another mobile phone I checked, with 2.17 OS rom & GSM 2.06.10 radio, I see that the when phone is not used the battery drain is 24mA !!!!!
This phone does NOT have the registry tweaks enabled and even with backlight it still stays in 24mA..
Please, post your mA consumption here and say what you have enabled.
Btw, anyone knows why Wireless Monitor Service(WMS7 was enabled (started) even though I have turned off WiFI,bluetooth & IRDA?
Click to expand...
Click to collapse
Dear,
I have upgraded my HTC Touch from WM 6.0 to 6.1. I have faced the big problem of Heavy Battery Drain. I was confused. I try to find out the solution over XDA Forum.
My problem was, "after charged 100%, then after 5-10 menutes it goes to 80%. and then it start draining very fast."
I have changed the registry for :
[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\Irsir1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\PPTP1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\L2TP1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
and Set the Wireless Monitor Service from Automatic to Manual.
But, I still have the same problem, why after 100% charged & after unpluged it goes to 94% thereafter 88% and within 5 menute it goes to 80%.
Thanks to the XDA Forum Members, help me out.
Mehul Patel

[RESEARCH] Improving Work Time of Battery

Please report here voltage, percentage and base rom every time you receive LowPowerWarning. look thru sktools for example.
example
3600mV
5%
X1 R2 based rom
thanx
addon: you must use original battery.dll or fixed 1% original battery.dll of XPERIA
as you know battery will dead at 2.500mV, but we can switch phone off at 2900 for example instead of current low value - now we research for it, and i think phone autoOff at about 3200-3500mV.

3610mV
5%
Touch-It v7 Final (with 1% battery dll)

thanks, i think i can fix it for 3100mV

Ethermind said:
thanks, i think i can fix it for 3100mV
Click to expand...
Click to collapse
Yeah, as long as you stay above 2500, you're ok. If you build in a safety measure, I'd say 0% at 2700 would be just fine!

3510 -5%
X1 R2+R3 based rom

[Q] battery driver issues

i currently own 3 units of s200 and have flashed them with cooked roms. however i have discovered a very disturbing fact about almost all the ccoked roms here - the battery driver is screwed up. i ended up changing 2 of the 3 phones battery because it only charges till 55% and 74% respectively, the 3rd phone charges to 95% and is stuck there
2 of the devices came from a same build september 2009 and the third phone is from jan 2010( i guess because it only says on the service receipt).
am i the only one who is experiencing this or there are more of you who had been infected by this bug?
i finally flashed all three phones with 3.03c official for malaysia/singapore
one more thing i noticed, all the roms effected were using somekind of tsowens taskbar icon as well as using non acer dialer.

bevoc said:
i currently own 3 units of s200 and have flashed them with cooked roms. however i have discovered a very disturbing fact about almost all the ccoked roms here - the battery driver is screwed up. i ended up changing 2 of the 3 phones battery because it only charges till 55% and 74% respectively, the 3rd phone charges to 95% and is stuck there
2 of the devices came from a same build september 2009 and the third phone is from jan 2010( i guess because it only says on the service receipt).
am i the only one who is experiencing this or there are more of you who had been infected by this bug?
i finally flashed all three phones with 3.03c official for malaysia/singapore
one more thing i noticed, all the roms effected were using somekind of tsowens taskbar icon as well as using non acer dialer.
Click to expand...
Click to collapse
Which Custom ROM did you used?

used a couple of kubino's
arto's latest
one of yours. (if i remembered correctly... i have to check my download folder)
additional info, the battery will get stuck on the last maximum charge before flashing... lets just say i have 55% batt and i flashed a custom rom... after flash, the battery will not charge more than that.
(it is safe to say that you must flash the phone in 100% batt... my bad, i flashed as soon as the charge goes over 50%... pardon my obsessive flashing disorder)
i even have left the phones connected to the charger overnight and in the morning it is still displaying the same level of charge (+ over heating = almost dead battery = buying 2 mugen 1500mAh's)... at first i thought it was a minor battery update lag bug, but the phones will die within 5 to 6 hours. sometimes they will be switched off for no apparent reason
i seriously want a 6.5.x rom running on all 3 devices because of the touch friendliness but the fact that it gives me battery errors turns me off.
just hope i can use custom roms like i used to on my previous htc devices.

bevoc said:
used a couple of kubino's
arto's latest
one of yours. (if i remembered correctly... i have to check my download folder)
additional info, the battery will get stuck on the last maximum charge before flashing... lets just say i have 55% batt and i flashed a custom rom... after flash, the battery will not charge more than that.
(it is safe to say that you must flash the phone in 100% batt... my bad, i flashed as soon as the charge goes over 50%... pardon my obsessive flashing disorder)
i even have left the phones connected to the charger overnight and in the morning it is still displaying the same level of charge (+ over heating = almost dead battery = buying 2 mugen 1500mAh's)... at first i thought it was a minor battery update lag bug, but the phones will die within 5 to 6 hours. sometimes they will be switched off for no apparent reason
i seriously want a 6.5.x rom running on all 3 devices because of the touch friendliness but the fact that it gives me battery errors turns me off.
just hope i can use custom roms like i used to on my previous htc devices.
Click to expand...
Click to collapse
Well your battery is broken.
I have already flashed with only 30 % of battery and nothing happened. Have also flashed my Phone over 200 Times in the last 6 months, in the last 3 days over 50 times - and the battery is still functioning without any problems.
On my Sencity ROM it holds for 2 days without loading.

thanx for feedback
i think i'll experiment on a few more roms. as far as my devices go, the problem was rom specific where flashing the stock rom eliminated the issue.

bevoc said:
used a couple of kubino's
arto's latest
one of yours. (if i remembered correctly... i have to check my download folder)
additional info, the battery will get stuck on the last maximum charge before flashing... lets just say i have 55% batt and i flashed a custom rom... after flash, the battery will not charge more than that.
(it is safe to say that you must flash the phone in 100% batt... my bad, i flashed as soon as the charge goes over 50%... pardon my obsessive flashing disorder)
i even have left the phones connected to the charger overnight and in the morning it is still displaying the same level of charge (+ over heating = almost dead battery = buying 2 mugen 1500mAh's)... at first i thought it was a minor battery update lag bug, but the phones will die within 5 to 6 hours. sometimes they will be switched off for no apparent reason
i seriously want a 6.5.x rom running on all 3 devices because of the touch friendliness but the fact that it gives me battery errors turns me off.
just hope i can use custom roms like i used to on my previous htc devices.
Click to expand...
Click to collapse
In my opinion, it is the issue of your battery, not the driver. If you use the original battery, you will find it works fine! The high capacity battery maybe need the special charger. Maybe just because the phone can not recongnize the battery's capacity.

By the way, I found that the battery does not work well with the new style roms. The battery always exhausts faster than the old style rom. For instance, the rom 23140 exhausts battery faster than rom 21057. My battery can stand by for neary 4 days with rom 21057, more than 3 days with rom 21895 or 219xx. But it can only stand by for about 2days with rom 23140 or 28xxx.

well the drivers are just ****ty
i searched thru the forums to find out what is missing... and i find then post that says new roms = new base drivers = recalibrate battery
guess what, i recalibrated my battery even the "broken" ones. now all are working perfectly.
the catch
1. recalibrate all batteries
2. delete any battery icons / taskbar enhancement (can be reinstalled after all this)
3. use any regedit find string "state" without the quotes. find "battery", and change all values to 0
4. charge batteries without turning on device, wait till light is green.
5. turn on device, make sure battery % is showing 100%
6. take off batteries, wait 10 seconds, reinsert battery
7. push vol+ and vol- and press power button (hard reset device)
8. voila... perfect charging battery
tested for 1 day already. the broken battery were not broken after all, its the battery driver. it will not make changes or detect changes from the battery because its from a different base driver (even if the drivers were said to come from official 3.03c bla bla bla.
sorry mates.. its not my batteries. if just one device its understandable. its from 3 seperate devices (one is actually my girlfriend's) so i made a conclusion that even roms cooked from same base will actually have a flaw that can kill your devices......... slowly
bottom note - only flash your phone at 100% batt and reflash stock rom in between flashes.

@ sinocreate
BTW the mugens were bought to replace 2 ORIGINAL batteries that had been damaged by the roms. do read the post carefully.
i think you are competent enough to understand my simple english.

bevoc said:
i searched thru the forums to find out what is missing... and i find then post that says new roms = new base drivers = recalibrate battery
guess what, i recalibrated my battery even the "broken" ones. now all are working perfectly.
the catch
1. recalibrate all batteries
2. delete any battery icons / taskbar enhancement (can be reinstalled after all this)
3. use any regedit find string "state" without the quotes. find "battery", and change all values to 0
4. charge batteries without turning on device, wait till light is green.
5. turn on device, make sure battery % is showing 100%
6. take off batteries, wait 10 seconds, reinsert battery
7. push vol+ and vol- and press power button (hard reset device)
8. voila... perfect charging battery
tested for 1 day already. the broken battery were not broken after all, its the battery driver. it will not make changes or detect changes from the battery because its from a different base driver (even if the drivers were said to come from official 3.03c bla bla bla.
sorry mates.. its not my batteries. if just one device its understandable. its from 3 seperate devices (one is actually my girlfriend's) so i made a conclusion that even roms cooked from same base will actually have a flaw that can kill your devices......... slowly
bottom note - only flash your phone at 100% batt and reflash stock rom in between flashes.
Click to expand...
Click to collapse
In your step1:recalibrate all batteries. I just want to know how to recalibrate the battery?
I remember that the system can recalibrate the battery automatically from maybe WM6.1 or newer core...

recalibrate
set backlight to maximum
turn off powersaving
let the device run until it dies by itself
take out battery for 10 seconds
put it back in
turn on device
if device turns on - let it alone until it dies again
if the battery have fully discharge, hold the power button red led will blink
once you know battery is fully empty, you can
a. charge using the original acer desktop charger
b. charge using a phone with stock rom
c. charge using your phone (make sure phone is off until fully charge)
wait till green light. then you're done.
the premise of this.
1. every battery has a chip that tells the phone and power management system that either it is empty or charged (voltage level, temperature etc)
2. Flashing custom roms abrupts this transaction of info from battery to power management causing innacurate reading.
3. new base driver will detect different battery level, some are ok and some are not, unfortunately in my case it has a serious error.
4. recalibrating is just a remedy to make sure that both phone and battery starts reporting on power drain from 100 - 0
one more thing, if you think your phone is affected, charge at a minimum of 8 hours (sometime the green light will come out earlier due to the fact that it is not accurately reporting the battery charge)

bevoc said:
i searched thru the forums to find out what is missing... and i find then post that says new roms = new base drivers = recalibrate battery
tested for 1 day already. the broken battery were not broken after all, its the battery driver. it will not make changes or detect changes from the battery because its from a different base driver (even if the drivers were said to come from official 3.03c bla bla bla.
sorry mates.. its not my batteries. if just one device its understandable. its from 3 seperate devices (one is actually my girlfriend's) so i made a conclusion that even roms cooked from same base will actually have a flaw that can kill your devices......... slowly
bottom note - only flash your phone at 100% batt and reflash stock rom in between flashes.
Click to expand...
Click to collapse
Where did you find that? Because that is for the HTC Devices. The ROM's for the HTC's use different battery drivers.
For our Acer device there are drivers 2.002 and 3.003. None of the kitchen Chefs use the old battery drivers or replace something in the OEM package.
So, if I say to you that my ROM has 3.003 drivers then be shore - there is no difference between my ROM and the official Acer one.

sinocreate said:
In your step1:recalibrate all batteries. I just want to know how to recalibrate the battery?
I remember that the system can recalibrate the battery automatically from maybe WM6.1 or newer core...
Click to expand...
Click to collapse
well these roms are not recalibrating automatically as they should

brainmaster said:
Where did you find that? Because that is for the HTC Devices. The ROM's for the HTC's use different battery drivers.
For our Acer device there are drivers 2.002 and 3.003. None of the kitchen Chefs use the old battery drivers or replace something in the OEM package.
So, if I say to you that my ROM has 3.003 drivers then be shore - there is no difference between my ROM and the official Acer one.
Click to expand...
Click to collapse
yes there is a difference. new builds brings new improvements/change towards many features including power management. i am sure you have been around long enough to have experience improvement in kernel and memory management as well as power management.
driver 303c was specifically made for the old builds. not 6.5.3. so i guess the best way to be sure about the battery issue is to recalibrate. it is safe and it is free.

bevoc said:
yes there is a difference. new builds brings new improvements/change towards many features including power management. i am sure you have been around long enough to have experience improvement in kernel and memory management as well as power management.
driver 303c was specifically made for the old builds. not 6.5.3. so i guess the best way to be sure about the battery issue is to recalibrate. it is safe and it is free.
Click to expand...
Click to collapse
Yes, you are right. If the battery isn't functioning as it should - then it is best to recalibrate the battery.
But normally this won't happen if you first full charge the battery when you buy a phone and then turn it on.

thanks
brainmaster, nice rom by the way, thanks for cooking. i'm using one of your rom now, i recalibrate and getting a good battery life good battery life.
next order of business - waiting for someone to compile a linux kernel!!
hahaha

bevoc said:
set backlight to maximum
turn off powersaving
let the device run until it dies by itself
take out battery for 10 seconds
put it back in
turn on device
if device turns on - let it alone until it dies again
if the battery have fully discharge, hold the power button red led will blink
once you know battery is fully empty, you can
a. charge using the original acer desktop charger
b. charge using a phone with stock rom
c. charge using your phone (make sure phone is off until fully charge)
wait till green light. then you're done.
the premise of this.
1. every battery has a chip that tells the phone and power management system that either it is empty or charged (voltage level, temperature etc)
2. Flashing custom roms abrupts this transaction of info from battery to power management causing innacurate reading.
3. new base driver will detect different battery level, some are ok and some are not, unfortunately in my case it has a serious error.
4. recalibrating is just a remedy to make sure that both phone and battery starts reporting on power drain from 100 - 0
one more thing, if you think your phone is affected, charge at a minimum of 8 hours (sometime the green light will come out earlier due to the fact that it is not accurately reporting the battery charge)
Click to expand...
Click to collapse
I m testing this method right now,then i ll report results.I m in Arto 3.9.2 rom now and battery with a good use last to me one day and half

I ve tried with no success...Nothing changed here

@axel85
what are you trying to change?
READ THE THREAD CAREFULLY.
DON"T JUMP INTO CONCLUSIONS.

Possible battery trick addressing improper charge issue in 7720 after ISVcleanup

Using Battery Tool, my HD2 on Mango 7720/ISV cleanup regularly charged pretty much 3/4 of total battery charge or in terms of HTC Battery Tool the charges were as follows:
FULL 1230
ACR 935
With that being said I 'd previously run NODO on 2.12 with great reception and the same charging issue. Update to 2.15 with Mango degraded my reception, battery life and preserved the charging issue. Then I started seeing posts claiming that flash to 2.12 in Mango improves the overall experience and one of them literally mentioned the charging issue which allegedly disappeared. Knowing what to expect from 2.12 due to prior NODO experience, I decided to roll it back and see what happens...
First flashed 2.12 over 2.15 with battery approx. quarter down its charge and despite better reception my battery constatly charged only three quarters of total charge. Sooo, after reading couple posts on 2.12 radio, and how the battery charges fully all the way to 100% (using HTC Battery Tool to check this), I finally decided to charge my battery in external charger and than once again reflash 2.12 this time with fully charged battery and...
No more three quarter charge . Will do some repetitive charging to test and confirm but so far it's always charging all the way! .
Hope this helps someone who's suffering the same half ass charging annoyance .
PS: Drawback to this is need for external charger or properly charging phone
To download CustomRUU and radios click link below:
http://forum.xda-developers.com/showthread.php?t=611787 (tnx user Kholk for useful post)
Hope this will work also for some other people .

Uhm... WP7 might be considering a theoretical maximum, just like android does with it's battery calibration.
Difference is, Android has on-the-go battery index recalibration. If it reaches the theoretical maximum (100%) and the charge is nowhere near 20/10 mAh, it keeps charging and set's the new maximum to the new charge (i belive it has a arbitrary battery units, at least Android on HTC Kaiser does).
What you're saying is, only flash WP7 if you're charge is at, or near 100% on WM6.5/Android Otherwise WP7 will waste battery charge

daedric said:
What you're saying is, only flash WP7 if you're charge is at, or near 100% on WM6.5/Android Otherwise WP7 will waste battery charge
Click to expand...
Click to collapse
Even better... In case that your battery does not charge properly there is no need to repeat WP7 install, only reflash your radio .
Yes, you may ask how device radio rom could have any effect on WP7 installation which comes with it's own radio drivers after all, but today I can attest that it does. My phone is regularly charging all the way to 1190 out of 1230 all the time as opposed to post Mango Rom flash value of 935 and all I did was reflashed device radio with fully charged battery .
Appreciate the Android analogy .
PS: I presume that it does not charge full 1230 due to phone not charging in USB flasher mode and during flashing process

Question, on what wp7 phone is our version based ?

daedric said:
Question, on what wp7 phone is our version based ?
Click to expand...
Click to collapse
I suppose it's HTC HD7 based as far as drivers for individual device components go. After all, people who are getting their new WP7 Roms activated (on HD2) literally tell Microsoft customer service reps that the activation is for HD7...

LuckTR said:
Using Battery Tool, my HD2 on Mango 7720/ISV cleanup regularly charged pretty much 3/4 of total battery charge or in terms of HTC Battery Tool the charges were as follows:
FULL 1230
ACR 935
Click to expand...
Click to collapse
Eh ... i have tried but i can't this battery tool you're talking about Where is it?

ToddeSwe said:
Eh ... i have tried but i can't this battery tool you're talking about Where is it?
Click to expand...
Click to collapse
Hi.
Click the below link (tnx xboxmod), and download the zip file attached to the first post. HTC Battery Tool is one of the utilities in that archive....
http://forum.xda-developers.com/showthread.php?t=896104

Have I missed a post somewhere, how are you reflashing only the radio? I have been wanting to change my radio to one better suited to Australia. I was loathe to go through the entire process of WP7 install again, when essentially I have a bug free functioning install.

Speedn said:
Have I missed a post somewhere, how are you reflashing only the radio? I have been wanting to change my radio to one better suited to Australia. I was loathe to go through the entire process of WP7 install again, when essentially I have a bug free functioning install.
Click to expand...
Click to collapse
Hi.
There is no other way then complete WP7 Rom reflash if you'd like to switch actual WP7 radio but hardware level radio driver (OS independent) can be upgraded/degraded without resetting or reflashing your phone . Note, I am talking about radio e.g. 2.12 and more as made available via the link in post #1.
With that being said, if there's any radio on that list that suits you or if you're in possesion of Australia compatible radio then all you have to do turn of your phone, next hold volume down --> power on your device and wait for the rainbow screen to appear (kernel flash interface ). Once your phone is connected to PC, your interface type will change from serial to usb and do your thing as instructed under the radio rom link in post #1. Let us know how do you and if there's anything else that could possibly prove helpful
Regards to Australia

Interesting.....
I was only getting a 75% charge with Mango and 2.15 so i flashed my radio back to 2.12.
After an immediate restart the battery charge graphic then showed 100%. Weird.
As the amber light was on I left the device charging into it changed to green. I then reflashed back to 2.15 and I have been getting a more accurate battery charge graphic ever since.
Ooh and the bonus, my battery is lasting longer between charges. Yey

Are you supposed to charge the device until green before flashing?
How long does your batt. last? On the worst day I had 4 hours batt. time (with BT on and WIFI on).
Today without WIFI and BT on the batt. seems to be lasting something around 15 hours.

I fully charge to green before I do anything nowadays.
I rarely use WIFI but I do have two email accounts set-up which check for mail every 30 minutes. With moderate talk time and two hour train surfing time I'm getting about 20 hours between charges. Which is considerably more than before.

my battery loses 10% on 30 mins, that's so LOL..
I have 7720 with 2.15.. with camera trick..
i'm gonna try the 2.12.. just a question, DO i need to HARD-RESET(by phone7 about screen) after the radio flashing?

luxxa said:
my battery loses 10% on 30 mins, that's so LOL..
I have 7720 with 2.15.. with camera trick..
i'm gonna try the 2.12.. just a question, DO i need to HARD-RESET(by phone7 about screen) after the radio flashing?
Click to expand...
Click to collapse
Hi...no, do not hard reset your phone at all. Whenever CustomRUU completes the ROM flash procedure, simply close RUU on your computer screen and your phone will restart (you will be exiting the rainbow/kernel USB interface). Mango install will be fully functional just as before you shut it down prior to flashing new radio .
Srry to hear about your battery drain issues...hope this will help to decrease it by a lot.
Let us know

The only solution that worked for me amongst all the options (based on my experience)
1. Tried the camera trick - NOT WORKED
2. Followed the steps below - NOT WORKED
* Boot the phone to MAGLDR
* Select "Reset" option from the menu
* Phone reboots normally
3. Hard reset the phone - NOT WORKED
4. Charge the phone in magldr USB storage option - NOT WORKED
5. Finally, flashed the 2.12 radio, did the camera trick (not sure if its relevant). The battery life has improved dramatically. It lasts more than 24 hours and still running (26% left) - WORKED.
Follow the thread below to download the 2.12 radio
http://forum.xda-developers.com/showthread.php?t=930578

[Q] Question about the Battery

Hey folks,
I got a question about the battery life of the Defy......when my phone is discharging it jumps from 62% to 50% and from 33 to 19%.
Is this a sign that the battery isn´t working properly ? So maybe I need a new one ?
Hope someone can help me.....
I also tried different roms and everytime I get this "problem".
Best Regards

If you switch between the ROM and does not at least 1 o 2 charge-discharge cycle, the battery will not calibrate...
Try calibrate with die hard battery calibrator when your charging the phone : http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021

this didnt change anything
still the drops:crying:

same here, I think my battery might be broken, will buy a new one next week. I will post if its ROM issue or my battery was damaged

would be fantastic if you could give me a short note:good:

Well, I've the same issue with 2 different ROM and 2 different batteries (the original and a new one which I buyed few weeks)...

weird....so nobody know how to solve this problem
bought a new battery today....let´s see

GeForce06 said:
weird....so nobody know how to solve this problem
bought a new battery today....let´s see
Click to expand...
Click to collapse
At default the phone received information from the batt by division of 10% and the software estimate the discharge. For some reason this estimation is eronate and the new batt value determine the system to recalculate the discharge and make those abrupt value. Anyway you can find in "general" thread a topic which resolve that situation.