Hey,
Charged my phone today and its only charged up to 83%. I seen some one had a link in there signature I read few days ago about fixing something like this but I cannot find it.
Does any one know a way to fix it??? I have battery monitor and battery calibrator but have not tried to calibrate it yet as the other day it charged to 100% so not sure why it hasnt today.
I am not sure if its the phone stopping it or if its the battery stats are out. it says its got 4167mV and the battery is a defy+ MB526 1650mAH.
Cheers
the defy+ battery goes up to 4320mV so u're battery does not charged. which rom are u using?
I am using ICS 4.0.4
The rom is made for froyo kernels. The battery stat file in those roms are the ones for the normal Defy. Replace the Battd folder in /etc with the folder from a Defy+ ROM.
Explanation: Defy's have a 1700mAh battery, so do froyo kernel battery stats files. That's why you must "tell your phone" that your battery is 2200mAh
Motorola Defy, CM7 @ 1Ghz + CM9 multiboot
[Guide] Install double boot CM7 + CM9
[Guide][Root needed] Unsimlock your Defy
why after I installed it and the battery was at 75% did it recharge to 100% ???
But when I went to recharge the second time it only went to 83%? I am going to run my phone dead tomorrow (I know its not good for the bettery but they should have a fail safe in to save memory loss) and then charge it up full with not stopping and see what happens.
I cant figure out why it would charge to 100% once then the next time it wont.
Well I replaced the battd.bin with a cm7 version and it charges to 100% but it stops at 4200mV I guess this is a failsafe so you dont over charge the battery???
I did not have battery monitor on any of the other versions I flashed so I am not sure if this is what it stops at or if it is still under what is capable.
You say the battery goes up to 4320mV? is that its max imput as it says its 1650mAH but has 1700mAH on the battery so I guess the 1700 is the max but it cuts off at 1650 as a failsafe?
Ok maybe that didnt work as I had it off charge for 4 hrs and on the phone for 1 hour and its still at 100% and 4200mV lol Will have to try copy another one over. Sure I will find one that works.
Ok got it sorted.
I found a CM7 battery fix for the defy plus and flashed that. It now charges to 4308mV so thats close enough for me and it shows when it was using battery. Was on 64% when I started charging as the other battd.bin files kept showing 100% and they where not draining.
I have the exact same issue, MB526 with CM9 and doesn't charge beion 83/84 percent.
Do you have a link to the battery fix?
I cant find where I got it from and the download link from the downloads does not work.
I have uploaded the one I used here so you can download that.
1.Put the zip into the root of your SD card.
2. reboot into recovery (cant remember if I used CM recovery or 2nd init.) Think it was CM recovery so hit reboot then hit reboot recovery.
3. Go into advanced and wipe battery stats
4. go back select apply update.zip from SD
5. flash the CM7 defy+ batt zip
6. once done go back and wipe the battery stats again (not sure if this was needed but I done it so keep to what I done)
7. select power off.
8. when power is off hook up battery charger
9. fully charge with the phone off (not sure if this is needed but this is what I done so maybe follow it)
If all went well when you put the charger in it should say the battery level leave it for a while hit the volume buttons should bring it back up if your curious if its charging!
It might have a green light at like 97% and say charged when you are in CM9 but leave it and it will keep charging upto 100% even though it says this.
Hope it works report back
Found the fix on a different thread, looks like the fix is working for me too, it's on 95% and charging.
It's on 4308mV with 95% and says charged. Before the fix it was on 4160mV with 84%.
I'll try your method and see what it will do.
Edit: it charged up to 100% and end up on 4313mV.
yeah I got a cm7.2 one to work but it only got to 95% which is alot better but it was not perfect but this one got to 100%. From what I have been reading different things work for different people but if this works for a few then we might be able to put it into the defy+ thread but I guess there would need to be a few people to test it out.
Few people said the CM7.2 one just copying the battd.bin over works but it didnt for me. The epsylon one got to 95% and the quarx ones the battery had a ? when off and always said 100% 4200mV even though the battery was at 65-70%
Mine charges to 4311mV with the fix applied not 4320mV some one said it should be but its a heap better then what it was
let me know of your finds coas as I would like to know what is working for other people so we can all help each other to make this work!
Sorry see your edit. So you experience the same as me?? it comes up charged with green light but 95% but it will still keep charging anyway and work its way up?
I am glad this has worked for you as I spent alot of time copying battd.bin files into my phone with no such luck. Please update here if this keeps working threw every charge as I have only done 1 charge so far. I may be able to write up a thread or tack it onto the all in one defy + thread if this is a proven way!
does this work for MIUI or just cyanogenmod?
Sent from my MB526 using XDA
I am not sure. you can try but I would copy your original battd.bin into your sd card so if it does not work you can copy it back over.
use root explorer. go to system/bin and copy the battd file. Go back into the sd card folder and paste it there.
then follow my instructions from the previous page and tell me how you go. It only flashes the battd file.
If it does not work you should be able to copy it back over push the mount/rw button in system/bin folder so you can paste the old file back.
You will then have to reboot into recovery and wipe the battery stats again.
Don't work
Stopped at 80% I complied a fix and need to sign it, can anyone sign it for me? It is from walter's kernel battery stats
I tried the cm7 battery fix on WIUI. Battery icon shows a question mark. So reverted to original battd.
You guys flashed on froyo based cm9 or gingerbread kernel cm9??
Sent from my MB526 using XDA
gingerbread CM9 kernel
Seems there is alot of conflict and no real true fix for this problem as quarx versions didnt work on mine I think maybe becoase I used epsylon CM9 but epsylon CM7 one worked but only charged to about 95%.
Its just a matter of finding the battd.bin file that works with yours it might take a few trial and error. copying them over from different versions.
I compare using BeyondCompare some of those fixes over there( the one in this post and those on white rabbit rom)
and the thing is that is only 2 fixes,
Example:
FIX a ->WhiteRabit fix 1 == WhiteRabit fix 2
FIX b ->WhiteRabit fix 3 == WhiteRabit fix 4
FIX b ->and the cm7 fix in this post == WhiteRabit fix 3 == WhiteRabit fix 4
If someone have some other fixes post it so i can compare it to know if is a new posibility or not
kelbygreen said:
gingerbread CM9 kernel
Seems there is alot of conflict and no real true fix for this problem as quarx versions didnt work on mine I think maybe becoase I used epsylon CM9 but epsylon CM7 one worked but only charged to about 95%.
Its just a matter of finding the battd.bin file that works with yours it might take a few trial and error. copying them over from different versions.
Click to expand...
Click to collapse
Gingerbread kenel? Then that fix of yours will work!! It doesn't work on froyo kernel . Battery will show a question mark if you apply that on froyo kernel
Related
I rooted my Hero a long time ago and installed Cyanogen's Recovery Image 1.4 on at the same time.
Over the last couple of days I've finally got hacked off waiting for an official 2.1 ROM to be released and decided to have a play with some of the Custom ROMs. The problem I've run into is that all of the guides talk about erasing data from different directories and partitions but none of them discuss how to do it !?
All I really need to know is if this is something that must be done via adb and what/where the directories are that need to cleared out.
I have searched and trawled but I get the feeling that this step is something that is done antomagically by the newer Recovery Images. If that's the case, would you suggest I upgrade mine ? And to what ?
Thanks for the help
(Really looking forward to playing with VillainROM 6 )
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
[Recovery ROM] [07-Mar-2010] RA-hero-v1.6.2
Thanks ddotpatel, I guessed it might be due to the age of the Recovery Image I've got
I'll upgrade this evening
ddotpatel said:
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
Click to expand...
Click to collapse
Any idea exactly what stats are erased by the battery stats & rotation settings options?
No idea pal,... but if Im flashing a new ROM without having 100% battery I leave the battery settings wipe.
I assumed that wiping battery stuff makes your phone think your battery is full after the wipe,...
So say its actually at 50%, then you wipe stats and flash a new ROM, then your phone thinks that battery is at 100% so will only charge upto that level.
The only thing I'm basing this on is I have read people say that when flashing a ROM when battery is not 100% they seem to lose battery capacity. But who knows, it could be psychological?
AFAIK battery stats deletes stuff like which programs have been using your battery as well as the currently stored battery figure. I assume that on next boot it checks the battery capacity afresh and goes with that figure.
Rotate one - i assume is to do with application rotation and the g-sensor.
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
Lithium Ion batteries don't have the "memory" problem of older batteries where they forget any charge that is left in the battery when it is put on charge and assume when its removed from charge that it is 100%. They should always stay the same capacity for their entire life duration. Again this is all AFAIK
Aahaaa,...
I always take what you say as gospel BTDAG.
Might have a read up on batteries later,... If I remember,... If I can be arsed!
Do you ever flash ROMs without having 100%?... No problems?
btdag said:
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
[snip]
Again this is all AFAIK
Click to expand...
Click to collapse
I took the same cautious view as ddotpatel. I figured if it's important enough to store in it's own private flash, it's probably holding data related in some way to the physical state of the phone, or an estimate thereof. I'm wary to touch them without ever having seen any solid info on what's there.
I've noticed one or two new ROM threads where the user is told to wipe these stats. I hope no one gets burned as a result.
BTW Also all afaik. It's just that in my case that isn't very far.
Ok last night I just flashed the latest epic experience and phoenix kernel .49. Had no issues with it last night. Put it on the charger and got to work this morning. Now twice this morning when letting my phone set, it just goes off all by itself. I have to pull the battery to get it to come back on. On the epic experience there are a lot of add ons and stuff that can be flashed. I have all those on my memory card as well. They were there last night. I am restoring my phone right now to prior to the install of epic experience and phoenix kernel.
does anyone know what the problem may be?
Thanks.
mynewepic10 said:
Ok last night I just flashed the latest epic experience and phoenix kernel .49. Had no issues with it last night. Put it on the charger and got to work this morning. Now twice this morning when letting my phone set, it just goes off all by itself. I have to pull the battery to get it to come back on. On the epic experience there are a lot of add ons and stuff that can be flashed. I have all those on my memory card as well. They were there last night. I am restoring my phone right now to prior to the install of epic experience and phoenix kernel.
does anyone know what the problem may be?
Thanks.
Click to expand...
Click to collapse
I'm having the same issue and trying to get to the bottom of it-- has happened on and off charger, where I just notice that my phone is off. I'm running the latest MixedUp Kernel with Andromeda ROM 1.1.1a (not the most recent). Other than the newest Mixedup, the only mod I've applied is the 'reboot option android policy.zip' grabbed from this thread.
Anyone know the best way to restore to stock android.policy.jar to see if the mod is maybe causing it?
side note: I still haven't found an easy way to get into my clockwork backups (browse contents, or mount), if anyone knows.
But that's the only thing I can think of that might be causing it.
This is a known issue with the reboot mod. Try flashing the newest Epic Exp OP.
Sent from my SPH-D700 using XDA App
id_twin said:
This is a known issue with the reboot mod. Try flashing the newest Epic Exp OP.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did flash the newest epic exp. I do not have the reboot mod installed, that second person does. I have reflashed the epic experience. I did change the wall paper to an all black one and that could be the cause. I also had a stop watch running in the background, so that could be a culprit as well. Right now I am trying to do the battery callibration, so I am charging to 100%, to be able to erase battery stats, re drain, and charge again. So we shall see.
Ok tried to reflash and still have issues. Using EE and Latest phoenix kernel, after phone just sits for about 10 minutes, the phone turns itself off. Someone anyone know what the issue may be?
Thanks.
Ok I can confirm that it must be epic experience causing problems. I can run Phoenix Kernel .49 with 2.1 and it runs fine and does not shut down. When I install the latest EE with Phoenix kernel .49 it shuts down. I have a lot of stuff on my memory card, but I can not see how that would affect the phone to just shut down.
Running andromeda galaxy rom and phoenix kernel .49 does fine. Anyone know why I would have an issue with EE making my phone just turn off.
the phone is freezing often
slow touch responce
programs force closing
yahoo mail doesnt work anymore
its shutting down on its own randomly
and some other problems i cant remember.
its a nand CMYLXGO stock desire HD v1.1.3
is this a common problem, if so where can i find info aout it i searched for dead battery and didnt show much.
Maybe some data got corrupted. So you should reflash or flash another build. Maybe even your radio to be sure.
why does it happen? i thought we wouldnt have this problem with nand builds.
fuzzysig said:
why does it happen? i thought we wouldnt have this problem with nand builds.
Click to expand...
Click to collapse
well, lot of roms use the data2sd method for storing data on SD, for me its pure nonsense (app2sd is fine). With data2sd the risk is very high that you get data corruption and then all the weird force close madness begins. Now if you run out of battery your device doesnt shut down properly/cleanly, its the same as you would just pull a cable to shut down a pc. So running out of battery is the same as pulling the battery.
wow
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
kiki_tt said:
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
Click to expand...
Click to collapse
That's what it does for everybody.
the phone also started to have SOD.
i plug it in at night to charge, in the morning it would not wake up.
the alarm would go off but the screen is blank.
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Been there. The only solution that worked for was to flash it from scratch once again.
Dunno why the phone is acting this way but now I always charge or turn off my phone when my battery is down on 10 %. Better to be safe than sorry.
I'm using MDJ's CM7 v. 2.6 so I think this is an issue on many builds if not on everyone.
fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Since u are aware u can reinstall it again then simply do so...Yeah its a real pain but just tk time out n do it...I've been using CMY's builds for so long and have never encountered such an issue..but dats just me...
i see u r still using V 1.1.3, CMY has released a much more better build (but then u already know that), so go download dat...perform a Task 29 ,install MAGLDR ( u know d works) etc...
As 4 y a dead battery will cause this on a custom build and not on a factory installed ROM? ...Me thinks u already know d answer (stick 2 stock WinMo if u think its better)..
P.S. Remember charging ur battery to 100% b4 starting..gives u a fairly calibrated battery.
you could also try to wipe the battery information via magldr?
you choose recovery in magldr > clockworkmod recovery > advanced > wipe battery stats.
tried that didnt work
isnt there another way besides reinstalling everything over and over?
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
fuzzysig said:
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
Click to expand...
Click to collapse
?! it has been answered in this thread...
I have a Droid Pro running 2.2.1 version rooted with superoneclick (had to turn anti virus off as it was picking up a false positive)
running rom manager
titanium backup
droid2 bootstrapper working great
installed 808 and gapps on sd
wiped all data and cache even dalvik
installed 808 and gapps
but when trying to reboot system got stuck on moto m screen and had to get back into recovery via comp and restore and reboot system without rom
i need any suggestions
just a note i let phone try to reboot for about 30 minutes
idk if you did or not but in the things you posted that you did you did not say you did a factory reset before installing. Did you do a factory reset after installing CM7
CrackMonkey91 said:
idk if you did or not but in the things you posted that you did you did not say you did a factory reset before installing. Did you do a factory reset after installing CM7
Click to expand...
Click to collapse
i did a backup and wiped everything
i did no reset until i got it out of bootloop and back in recovery to reboot to stock with root
I don't have an answer but I would like to say that if you manage to fix the problem, do keep in mind there is a 902 version for our phone
Sent from my DROID Pro using XDA App
dutchbastard said:
I don't have an answer but I would like to say that if you manage to fix the problem, do keep in mind there is a 902 version for our phone
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
i have fixed it and successfully installed gingerbread and rooted
am curious about new cm7 for this phone as a custom rom would be nice because battery life is terrible
Well battery life already greatly improved with GB on both my own and my sons phone.
I have cm7 on mine and now its even better.
I had to folllow a tip to delete batterystats.bin after a full charge but itt lasts well over a day now.
Of course using the phone heavily will deminish that life but with moderate use you should be good for your day to day stuff.
Sent from my DROID Pro using XDA App
dutchbastard said:
Well battery life already greatly improved with GB on both my own and my sons phone.
I have cm7 on mine and now its even better.
I had to folllow a tip to delete batterystats.bin after a full charge but itt lasts well over a day now.
Of course using the phone heavily will deminish that life but with moderate use you should be good for your day to day stuff.
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
please elaborate on batterystats.bin action
where can i find cm7 that will work and instructions link
The link for the 902 download is http://www.mediafire.com/?cwignib2ksgwuev
Posted by jackpotclavin on droidforums: http://www.droidforums.net/forum/droid-pro-hacks/154369-gonna-build-cyanogenmod-7-pro-59.html
There is a nice blog by him with instructions here: http://clavinsup.blogspot.com/
Though I don't see the 902 download there so the instructions are a bit outdated, but still apply.
Just use the 902.zip from that mediafire link (4th post on second link) and the instructions from that blog.
When it comes to batterystats.bin I was told to google it, which I did.
I came across various instructions about letting the battery run dry, then charge til full, delete batterystats.bin though filemanager, then charge for 2 more hours....other instructions said something different.
Basically I got: Charge til full, delete file, run dry until phone turns off, then use normally.
CM7 gives us the option to delete the batterystats in there. (recovery/advanced/wipe battery stats)
So that's it.
Now I don't know if I did it wrong, all I know is it gave me longer life.
ho hum
and boo
I'm not sure where to start, so if there's anything i left out, I'll be glad to clarify.
phone: Motorola Bravo MB520
stock: 2.2.1
current: CM7 V5
i made the mistake of pulling the battery during a clockwork restore from CM7 for Bravo to a rooted stock nandroid, then the battery died before completion, corrupting the flash.
i hotwired the phone, and flashed the above linked 2.2.1 SBF and did a factory reset, all caches wiped and the phone is alive!... kind of.
from this point on, the phone will start up while hotwired, but I get an error that the battery is not recognized as a genuine Motorola battery (it is), and there is a question mark in the battery indicator in status bar and in the charging startup screen (phone off, plug into wall, moto logo, battery charge image).
"/sys/class/power_supply/battery/uevent" reads:
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_PRESENT=0
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CAPACITY=100
POWER_SUPPLY_VOLTAGE_NOW=3753000
POWER_SUPPLY_TEMP=340
POWER_SUPPLY_CHARGE_FULL_DESIGN=0
POWER_SUPPLY_CHARGE_COUNTER=100
I bought a new battery, same issue.
I baleted the contents of "/data/battd/" and "/data/system/batterystats.bin" with no change.
The battery is seated properly, with no corrosion on terminals.
Is there anything more than can be done?
Just for sh**'s and giggles did you try to do another flash with the 2.2.1 sbf? Might help. Or just try flashing the CM7 rom, turn it on and just play around a little then flash back to 2.2.1. Post an up date please! Others might do this too.
Junkyardjames87 said:
Just for sh**'s and giggles did you try to do another flash with the 2.2.1 sbf? Might help. Or just try flashing the CM7 rom, turn it on and just play around a little then flash back to 2.2.1. Post an up date please! Others might do this too.
Click to expand...
Click to collapse
i've flashed the 2.2.1 SBF 2-3 times now. after encountered this, that was my first thought, having been unable to get RSDLite to give me a success response. the only CM ROM's available are ports of the Moto Defy. This one just has the working cameras. Stock factory reset gives same error as does another CM port by rdanner/josuearisty as well as bandroidx's ROM.