[Q] CM9 Battery problem - always 100% - Defy Q&A, Help & Troubleshooting

I flashed the lastest CM9 build (from http://forum.xda-developers.com/showthread.php?t=1432100 ) on my Defy+
I follow the instructions (Full Wipe, Flash CM9, Flash CM9 kernel, Flash Gapps and reboot)
and I have a quite embarrassing problem :
the Battery stays always at 100%
When i try to charge it, the icon with a flash appears but LED does not shine
Someone should have an idea to help me? Please

Flash this battery fix from cwm.
http://www.4shared.com/zip/UR1QUISz/...ttery_Fix.html
Sent from my MB526 using XDA App

thank you !

Related

[Q] Battery Life on CM7.1 Stable

Hello,
Using CM7.1 jordan stable on my MB525 Red Lens. Everything is working perfectly, but i have some pretty nasty battery uptimes. I charged the phone to 100% last night, the moment i unplug it i already have 99%, and after 8 hours spent with the phone unplugged while i was sleeping overnight, it went down to 46%. Any ideas as to why this happens and what i can do to tame it?
Thanks.
This is nasty.did you calibrated the battery after you installed cm7?
I too have red lens and running 1403 quarx defy + build with Walter 4.5.3-109 kernel which gives best battery life. The same kernel is used in ms2 ginger 3.0 which is known to have best battery.
Sent from my MB526 using XDA App
Running kernel 2.6.32.9-gb08c3c8, EPU93 baseband. I have not calibrated, but after reading around on the forums it looks like it's not much use. Or is it? I installed the calibrator, i will let the phone power down completely and then will charge up to 100% and recalibrate. Any other advice that might be useful?
Thanks.
Since your defy is red lens I would suggest you to flash defy + builds. You can use latest quarx 0316 cm72 defy + build and flash walter79 4.5.3.109 kennel.that would give awesome battery life and at the same time you are on beauty of cm7.
For quarx builds, get it from http://quarx2k.ru/cm7-nightly-defy+/
For kernel just see the ms2 ginger thread, there you would find 4.5.3.109 and zip file which can be flashed by cwm.
Btw, earlier releases had problem in booting with that kernel which quarx fixed on 0316. If you flash earlier cm72 releases, then flash 4.5.2.109dht22 kernel, which you can find in the same ms2ginger thread.
Sent from my MB526 using XDA App
Can i flash the Kernel you suggested on my current CM7 without flashing CM7.2 for Defy+? If i can, what will the effects be? Will it mean any changes in my settings, applications or any other thing, or will it just improve certain computing aspects?
Luppertazzi said:
Can i flash the Kernel you suggested on my current CM7 without flashing CM7.2 for Defy+? If i can, what will the effects be? Will it mean any changes in my settings, applications or any other thing, or will it just improve certain computing aspects?
Click to expand...
Click to collapse
No don't flash that kernel which leads to boot loop on cm7 stable which uses froyo kernel. I assume you have froyo kernel now correct.
Kernel won't change any computing aspects nor will change any settings, you don't find any noticeable difference as far as the system goes.
Sent from my MB526 using XDA App
Correct. 2.2.2 CEE as base. Any other kernel you might recommend for this base and CM7.1 stable? Or any other battery calibration suggestions, way to make it last longer?
Well on froyo I don't have one to recommend. GB builds give better battery life and we have alternatives.
I was with cm7 fire quite some time but didn't like battery life. Then I moved to ms2ginger, battery life was awesome but then it's stock, missing cm7.
Now finally I have mix of cm72 with ms2ginger kernel, loving it.
If you have nandroid backup of original stock froyo and gives better battery life then try restoring it's 'boot' through cwm recovery, please nandroid backup the existing 'boot' before you do this, just in case if you stuck in boot loop, you can restore it back.
Sent from my MB526 using XDA App
premaca said:
No don't flash that kernel which leads to boot loop on cm7 stable which uses froyo kernel. I assume you have froyo kernel now correct.
Kernel won't change any computing aspects nor will change any settings, you don't find any noticeable difference as far as the system goes.
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
I was using the MS2Ginger 3.0 based rom by walter79 and I got wifi issues with my office wifi not working.. I then flashed to cm7.1 and though battery life is not that good, wifi works smoothly...
I will try the cm7.2 with ms2ginger and see if I get wifi issues with that as well.

Help green lens battery is (?) bootloader 7

I have a Defy MB525 FUll Flashed DFP231 (GB Kernels) does not work charging the battery (the question mark is displayed on battery icon). I tried to install CM9 (for Defy MB525) - the system will not start. I tried to install CM9 Defy MB526 - it works, but not charging the battery (the battery icon is displayed properly, when you connect the charger is displayed if started charging, but in reality the phone not charging
. I tried to put the GB Kernels for CM9 - bootloader error. I tried to put the Battery fix for Red Lense - does not help.
THE DREADED INVALID BATTERY!
i have the '?' and nothing works to fix it, although mine is caused by macgyver.
can anyone tell me if this would work on a defy? and post pictures?
http://www.mod2xtreme.com/showthread.php?t=10487
Froyo kernel for green lens bootloader 7 ?
any news?
You can flash eplsy's defy+ build. Or use battery fix (search a bit)
No hopes for camera.
Sent from my MB525 using XDA
I Flash CM7 & CM9 Build For Defy+ .
Didnt Worked battery and camera.
Froyo CM7 and GB kernel CM9 kernel --> Bootloader Error.
I want just my battery back!
For CM9, use the builds from epsy (they suppose to have the right files for the defy). Or use the search function (something like 'battery fix').
For CM7 there are also zip files. You should we able to find them (maybe with Google).
Sent from my MB525 using XDA
Why people don't read before flashing sbfs?
walter79 said:
4.5.1-134-DFP-231 - retail, vodafon, tmobile, O2, full Blur ROOT? downgrade no! Maybe MB525(Defy) battery did not work!
Click to expand...
Click to collapse
someone told me maybe my battery dead when i try mcgyver .
that true?
i buy new battery Hf5x for DEfy green lens.
and again no charge!
what i can do Now?
jalal-jap said:
someone told me maybe my battery dead when i try mcgyver .
that true?
i buy new battery Hf5x for DEfy green lens.
and again no charge!
what i can do Now?
Click to expand...
Click to collapse
The only way I got the HF5X Defy+ Battery to get fully charged on the Defy(Green Lens) was to flash a GB Kernel like 4.5.3-109_DPP-11 an install Defy+ "battd" & "libbattd.so" like in this thread.
Only problem I got was no working camera. Tried Greenbread mod which brought me back camera but do not work with HF5X batttery.
So maybe try the 4.5.3-109_DPP-11 kernel with battd patch.
Kind Regards,
mpeg
if i try any kernel I have bootloader error!
i think boot.img from froyo kernel solve my problem.
but when try that on Defy Green 2.3.6-231 bootloader 7 --> Bootloader error!
if you already flash bl7 sbf onto your phone, then the only stock firmwares will work /dfp231, dfp188 = bl7/
I buy new battery put in on phone and again Invalid Battery !
wipe data
wipe cash
flash ic redlens battery fix
flash battery fix for white rabbit eddition
NOT WORKED
I test in CM9 & Stock Firmware (rooted 2.3.6). Battery always (?)
I am going to crazy!
First you must know that you are stucked in bl7 and can not downgrade to froyo at the moment. But I am convinced that if you use the battd & libbattd.so from defy+ stock rom, set the permissions like the old ones and delete everything in /data/battd the HF5X will be charged full.
I brought the Hf5X fully charged on MS2Ginger 3 and 4 on 4.5.3.109 kernel and files mentioned above. I am using a defy (green lens). Camera not function at this kernel.
Kind regards
mpeg
Thanks for replay .
I gust I need boot.img from froyo kernel.
I cant use any kernel in BL7 ---> bootloader error.
I use both of Battery (BF5X & HF5X ). Not Worked.
Maybe my battery IC DEAD!?
If your battery ic would be dead than you could not power on your phone without power cord.The battery charge process is handled though software. I think it is a software/kernel incompability.
Because you are stucked in bl7 try to flash defy+ stock sbf. Maybe try some battery fixes for gb kernel.
Don't forget to wipe data/cache, dalvik cache. If this doesn't work try Motorola build in factory
reset.
Kind regards
mpeg
Maybe this helps you http://forum.xda-developers.com/showthread.php?t=1413214
that bootloader is 5.
i am on bootloader 7!
not worked.
no way for solve battery problem for bl7?
On witch rom are you now?
Verstuurd van mijn MB525 met Tapatalk

Answer : How to custom Kernel ´Defy+ JB Quarx

Everything for testing!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I wrote this for maybe less confusion
Works with my Defy - red lense Bayer cam - on Defy+(gingerbread Kernel) Jelly Bean Quarx 24.8 Rom
I´ve
1. Flash test_2ndboot_6.10.zip from http://quarx2k.ru/ or my 2ndboot_06.10.zp from attached dropbox (search for 2ndInit recovery if you dont have and root your defy)
2. Boot into Recovery
3. Set 2ndboot as default
4. Go to tools/adb daemon and klick it and then reboot
If you want to go back to stock gb kernel flash stock kernel -like gb-234-451-134-signed.zip from dopbox i´ve attached
Remember everything is for Test the custom kernel
OT - Multiboot is ok with CM7 but akku is always 100%
https://www.dropbox.com/sh/4fg71wuehyibzzx/oanepGgaRR
BIGNOTE: Green lens users who flashed redlens builds please dont try using flash, you will end up burning it like me and many others
Big thanks to our great DEV´s Quarx as porter :good: , Walter for fixing :good: and MS2 Dev czechop who made this possibile :good:
Great works men !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11
Hi, i tried all the methods without sucess... Alldays the same: blue led then red and stuck at moto logo. Any ideas?
Sorry for my english and thanks in advance
Redhotero said:
Hi, i tried all the methods without sucess... Alldays the same: blue led then red and stuck at moto logo. Any ideas?
Sorry for my english and thanks in advance
Click to expand...
Click to collapse
Defy or Defy+ ?
bone101 said:
Defy or Defy+ ?
Click to expand...
Click to collapse
Defy red lens with defy + build gb kernel
Sent from my MB526 using xda premium
I have done it in such manner
1. Prepared on SD card:
- CM10 ROM 24/09 for MB526,
- gapps for JB
- Qkernel 2ndboot_06.10.zip (with improved 2ndboot.ko)
2. Done factory reset and viped caches
3. Installed CM10 and gapps in normal manner
4. Flashed Qkernel
5. Went to bootmenu and choosed 2nd-boot (there was no chance to set it as default... i think, because phone immediately reboots)
And achieved "half success". All is working but with extremely lags... Was said so after first bootup system suppose to be laggy and needs to wait some time on sleep state with WiFi switched off. I was waiting whole night.
So now I want to know, if my procedure is right.
Nobody mentions gapps during instali of ROM - i suppose it's so trivial so nobody count it on...
Another problem - is there need of factory reset or cache wipe?
After installing Qkernel i went to boot menu to set 2nd-boot as default, but when i choose 2nd-boot phone reboots and I don't know what now with this setting up deafult 2nd-boot...
I am trying to fond any reason of system lagginess. Maybe something was done wrong. What's your opinion? To change ROM build? Or something else...
Redhotero said:
Defy red lens with defy + build gb kernel
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
You can try it with the kernel from my drop box
I nerver wiped anything
For me it works as I've done
http://forum.xda-developers.com/showthread.php?t=1542956
bone101 said:
You can try it with the kernel from my drop box
Click to expand...
Click to collapse
Of course I can try, but does it make any difference? Well, will see...
So I'm supposed to flash your kernel "as is" without much deliberation over existing installation?
If you are on boot loader ver 7 i cant say that it would work
Some peoples in this
http://forum.xda-developers.com/showthread.php?p=32535395
Wrote about problems with custom kernel . Look around page 67 if your defy+ was stock bl7
I am using regular Defy with Bayer module and as first owner I am sure so there was not flashed any full sbf except once when I was forced to flash stock Froyo, so there is no case of BL7 I think...
So if I try can I flash this kernel over existing system or should I reflash ROM too?
bone101 said:
You can try it with the kernel from my drop box
Click to expand...
Click to collapse
Tried without success. Ill have to flash sbf rigth? Which do you recommend?
what are the advantages of using this kernel?
I don't know the advantage, for me it works as i do.
I started with stock cee European gingerbread which I've flashed after offical update comes out
New nightley from quarx cm10-2ndboot-nightly-defy(+)
Is out & works a bit faster
bone101 said:
I don't know the advantage, for me it works as i do.
I started with stock cee European gingerbread which I've flashed after offical update comes out
New nightley from quarx cm10-2ndboot-nightly-defy(+)
Is out & works a bit faster
Click to expand...
Click to collapse
Flashed new nightly and problems are gone
Redhotero said:
Flashed new nightly and problems are gone
Click to expand...
Click to collapse
thank to quarx
trurl3 said:
I am using regular Defy with Bayer module and as first owner I am sure so there was not flashed any full sbf except once when I was forced to flash stock Froyo, so there is no case of BL7 I think...
So if I try can I flash this kernel over existing system or should I reflash ROM too?
Click to expand...
Click to collapse
In General section http://forum.xda-developers.com/showthread.php?t=1909242&page=84
they talk about BL5 and BL6 is supportet by quarx not BL4 and BL 7
Some say it works on BL7
But better read there for your self.......beforr you flash anything and think about warrity/garantie
For every booting i had to umount and mount again the battery.
And no Deep-Sleep in about 12 hours
Anyone else with this problems?
---------- Post added at 09:37 AM ---------- Previous post was at 08:49 AM ----------
Now Deep-Sleep is ok. Dont know why .... But ... Quarx said in the xda-developer thread,
that with no usb-cable and with wifi disabled the defy should go 10-15 sec. in deep-sleep.
Before i have had usb-cable on or wifi enabled. Maybe that has been the reason.
After 3 hours 14 % battery drain ... not good ...
Quarx edited a new Rom today.
But after getting more and more slow reactions from the defy+ i flashed the 24.09 version.
All tips didn't really work in a good way.
And I need my defy+ functionabel this days.
But next time again ...
And today again a new kernel for update as *.zip ...
quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_11.10_v2.zip
13.10 Kernel update:fix wifi tether(reboot), reduce battery drain, compiled with linaro 4.5, fix charge only mode, cleanup unused drivers.

Reverting to CM7 from CM10/Jelly Bean ROMs on Defy MB525

Hey guys, I'm currently running CNA 3.6.6 with the JellyX kernel (5-12 bfs) by Blechd0se. (Great combo, BTW :good
I would like to revert to the official CM7 builds because I admire the stability and battery life offered.
Now to my problem,
I know that I have to flash a froyo kernel in order to install CM7 successfully.
But on this thread (http://forum.xda-developers.com/showthread.php?t=1432100) it is mentioned Latest Froyo kernel by Epsylon3: 16 May 2012
Latest Froyo kernel by Quarx: 8 Mar 2012. I was not able to locate these kernels on the respective servers (quarx2k.ru and defy.wdscript.fr)
Moreover,these links are dead: CM7 (froyo) Kernel http://m.cfa.aero/misc/CM7_Kernel-signed.zip
CM9 (GB) Kernel http://m.cfa.aero/misc/CM9_Kernel-signed.zip
However, I was able to find this one (kernel-froyo-222-179-4-signed.zip) on epsylon3's sever. It is dated June 13 and so I'm assuming it is the latest and should work properly. So will it? I plan on flashing the 9-12 official nightly of CM7. Also I read somewhere that CM7 comes bundled with the kernel, so is flashing the kernel even neccessary? I have also seen a test CM7 kernel by blechd0se, does anyone recommend it for stable daily use and will it be compatible?
I plan to follow these steps in flashing, someone please please correct me if I'm wrong..
CM10 recovery-wipe data-wipe cache-wipe dalvik-install cm7-install gapps-install kernel-wipe cache-wipe dalvik.
Should the kernel be flashed before or after the ROM?
I'm trying my best not to be a n00b here (my first thread here, and you might notice I have just one post and zero thanks ), but I really am confused because on a different thread I read that flashing an SBF via RSD was the only way to do this , and I think this thread will help others who might like to go back to CM7 if they are facing issues with Jelly Bean. I have done my homework reading and am not posting without searching. So Any help will be greatly appreciated , and if I'm being a complete bumbling idiot, please feel free to tell me so. :silly:
Waiting for replies from the awesome folks at XDA,
Cheers and have a great day! :highfive:
-Viki
PS: Off-topic, has anyone tried the V6 supercharger by zeppelinrox on our Defys (JB/ICS/GB) ? If you have, please share your experience I'm really curious, that's all
Cheers
You're confusing 2ndboot kernels with regular kernel. No kernel flashing is required, because they do not interfere and/or replace each other(2ndboot custom and stock Motorola).
You're better off with the regular kernel(Motorola one), the test one(the one for cm7) is in early development.
You will have to convert data from ext4 to ext3 via boot menu. Select tools, file system tools and convert to ext3.
So, the process is: Convert to ext3, flash Rom(You may wipe system before this for good measure), boot the phone, reboot and flash gapps(you may flash it directly after the rom, but this method works for me)
EDIT: Flashing directly works(just tested) for quite a lot of combinations
Sent from my MB526 using xda premium
i may add that you could either flash a stable cm7 + nightly bcs kernel is missing in the nightlies or you just flash one of maniacs... they come with a kernel and are the most cutting edge (the only cutting edge). good luck.
Again, the kernels above are 2ndboot and do not replace the stock; it's a misconception. So, either way the process remains the same; there is absolutely no need to flash anything else unless mentioned on the rom thread.
Sent from my MB526 using xda premium
thekguy said:
Again, the kernels above are 2ndboot and do not replace the stock; it's a misconception. So, either way the process remains the same; there is absolutely no need to flash anything else unless mentioned on the rom thread.
Click to expand...
Click to collapse
Okay..Thanks guys! XDA forums are really helpful And so quick to reply too!
On the ROM thread, they say flash froyo (http://forum.xda-developers.com/showthread.php?t=1033654)
I'm not sure what they mean..
Do I need to change the default boot to 2ndinit as well?
And can someone elaborate on what differences can be found between the official CM7 nightlies and maniac's ones?
Cheers and have a great day!
No change, no nothing. I'm not really sure about maniac builds, perhaps they use the newer kernel(custom), whereas official uses stock Motorola
Sent from my MB526 using xda premium
http://forum.xda-developers.com/showthread.php?p=21686557
Differences:
LTO download. (not sure if merged to official)
panic daemon against RIL bug
cant remember what else.
NO custom kernel yet
but things get merged to official sooner or later because maniac is an/the official maintainer for cm7-jordan.
thekguy said:
You're confusing 2ndboot kernels with regular kernel. No kernel flashing is required, because they do not interfere and/or replace each other(2ndboot custom and stock Motorola).
You're better off with the regular kernel(Motorola one), the test one(the one for cm7) is in early development.
You will have to convert data from ext4 to ext3 via boot menu. Select tools, file system tools and convert to ext3.
So, the process is: Convert to ext3, flash Rom(You may wipe system before this for good measure), boot the phone, reboot and flash gapps(you may flash it directly after the rom, but this method works for me)
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
thanks thekguy. i wasted half a day wondering if my defy had finally bricked and all it is was the ext4 causing the problem. with a quick google found this thread and your solution works perfectly. i only wished that they have sticky your solution as i'm sure many ppl are looking for it...
I do have a big problem. I followed all the steps (coming from latest nightly of CM10) with formatting to ext3 and the other steps. I tried to install CM7.2 and everything went well. But now I stuck at the Motorola Logo.
I even tried the sbf-flash but that didn't work because after RSD-Lite-Flash it stucks at rebooting. Anyone knows how to fix that?
And another problem is, that I cant charge my battery anymore :crying:
Stock recovery-> data wipe
Sent from my MB526 using xda premium
thekguy said:
Stock recovery-> data wipe
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
That didnt work. I tried to flash the sbf by Quarx (4.5.2-109-DHT-22-fixed.sbf) and RSD Lite says "Please manually powerup this phone". But the Defy stucks at the Motorola Logo (Blue and Green Light and the softkeys are flashing up).
PS. At least I managed to reinstall CM10 in 2nd-Boot and now can charge my phone
EDIT: Now I did all the steps again and installed CM7.2. But now I stuck not at the Motorola Logo but the Bootanimation is looping... It's strange but I dont get a confirmation that I wiped the Dalvik Cache successfully....
How about full sbf flash
Or try this:
Cm10 bootmenu format to ext3 and flash cm7 zip. Reboot and enter custom recovery and wipe data+ dalvik + cache
Sent from my MB526 using xda premium
My boot profile is 2ndinit (not 2ndboot), does this mean that I am using Motorola stock Kernel?
Yes
Sent from my MB526 using Tapatalk 2

[Q] RED led blinks which is the CM10 Nightlys latest build for MB525 Green lens?

RED led blinks and it is in a bootloop when i upgrade my defy with CM10-20121128-NIGHTLY-mb526.zip ? can anyone give me the link for the CM10 Nightlys latest build for MB525 Green lens and the correct jellyx kernel for MB525 Green lens?
Reply
The one you are flashing is an old nightly.
You can find the latest CM10 here- http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/ or here-
http://www.uncledan.it/android-files/CM10/
jellyx here-
http://forum.xda-developers.com/showthread.php?t=2017329
wipe cache and dalvik.... You can upgrade without wiping data but that could cause problems
please use the search function next time
hotdog125 said:
The one you are flashing is an old nightly.
You can find the latest CM10 here- http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/ or here-
http://www.uncledan.it/android-files/CM10/
jellyx here-
http://forum.xda-developers.com/showthread.php?t=2017329
wipe cache and dalvik.... You can upgrade without wiping data but that could cause problems
please use the search function next time
Click to expand...
Click to collapse
Dude, i used the search function ...but i am confused which is the kernel for my defy green lens to download and if i upgrade it to .. i am not able to see any changes in kernel... and i think the nightly is present in the given link
don't flash the kernel, it's better without
pochopsp said:
don't flash the kernel, it's better without
Click to expand...
Click to collapse
between how to know if the kernel flashed was a success... because if i flash the kernel too... in my ABOUT PHONE it shows the kernel which came along with rom :cyclops:

Categories

Resources