Hi, I have a red lense Defy and have just flashed latest Quarx nightly per http://forum.xda-developers.com/showthread.php?t=1432100 but everytime I reboot the phone it takes about 90s to start, and all my settings (wifi, baseband, email etc) have been forgotten - the phone start as if it's a brand new install. Can anyone please point me in the right direction? I have tried reinstalling a few times with no luck. otherwise the rom works perfectly.
bluballe said:
Hi, I have a red lense Defy and have just flashed latest Quarx nightly per http://forum.xda-developers.com/showthread.php?t=1432100 but everytime I reboot the phone it takes about 90s to start, and all my settings (wifi, baseband, email etc) have been forgotten - the phone start as if it's a brand new install. Can anyone please point me in the right direction? I have tried reinstalling a few times with no luck. otherwise the rom works perfectly.
Click to expand...
Click to collapse
I'm having the same problem. Anybody has any clue to fix this?
You may have to flash your stock SBF using RSDLite as upgrading to Cyanogenmod ROMS only writes the system partition. Maybe the other partitions have got corrupted.
I'm not sure though.
Dear all,
Today I bought a defy+ original battery for my defy. I am running quarx's cm10. As I know, defy won't charge defy+ battery past 80%. Is there a bugfix I have to install, how, and where do I find it?
Best Regards
So, battery is stuck at 87%. Tried installing battery fix. Any ideas what I can do? :/
Hi Buddy.
Try reseting the Battery Stats from ClockWorkMod.
To do this -
Hold Power and Volume Down to enter 2ndInit.
Go to Recovery then Custom Recovery.
Go to Advanced and then Wipe Battery Stats.
Good Luck,
neiljain
Using latest nightly (CM10 - 11/5), Defy+, my battery will not charge past 80%, and it is dropping at an alarming rate. I tried to wipe battery stats, but it do not exist anymore (or I did not found it, in this case, please tell me where it is located, because it is not where it used to be).
Hi
I have regular defy with red lens.
I have flashed some time ago new Quarx rom with custom kernel from WIUI JB rom.
After that I am unable to flash any non custom kernel builds. Even when I did a full wipe and flashed Froyo kernel with CM7, I got stucked in boot-loop. I even can't go to Stock recovery.
Now I am running recent Quarx build, but during the boot my led light is red. Also the rom is quite unstable, and crashes quite lot whitch I think is not the problem of the rom, but problem with the phone.
I also tried to use different custom kernel with no success. Also I searched this forum for some answer with the same result.
I have never flashed any SBF to my phone, I have ever used nandroid backup.
(I got my phone with Eclair, but after I got my phone from warranty repair I got Froyo)
I'll probably try to solve this problem by flashing Froyo SBF and try it again.
Thank you for help.
EDIT:
When I tried to flash WIUI JB again, strange thing happen. It flashed normally but ROM did not see internal memory and crashed after RAM got full. Also recovery had listed some errors.
Another custom kernel roms also work, but with the same problem as CM10.
I have also set correct setting for rom in bootmenu (2nd boot or 2nd init).
Hi guys.
I came here to solve a problem with my device. I have a Defy Plus (Mb526) and accidentally i have installed the wrong ROM (BL7, 2.3.6, I think) and it causes many problems.
Problem 1: My Defy don't have the same performance and fluidity as before.
Problem 2: The battery icon was replaced to a question mark.
Problem 3: The device don't charge with charger, but the PC recognize it.
The only way to charge it's a Universal Charger.
I have tried to install so many ROM's (stock and custom) and fixes, but the only stock ROM what works it's chinese and taiwan. Others don't start.
I tried too install a backup of CyanogenMod but isn't sucessful and the problems just keeping.
So, please, anyone can help me?
I've had the trouble described in
http://forum.xda-developers.com/showpost.php?p=49962954&postcount=1775
What's worse, more recent builds have a kernel that bootloops for me. This thread has a solution.
Originally I was unsatisfied with CM11 nightly, because the camera crashed with a hard reset - heavy use of the gallery or taking a photo after a long time had triggered this hard reset reliably. So this problem was reproducable.
I upgraded CM11 nightly to latest 2014-03-30, just to find out recent kernels won't start at all or bootloop the green lense defy.
After that I wiped anything - flash SBF, Framaroot, 2ndinit, twrp_recovery_2.6.3.0.zip.
To confirm the device was working I flashed a couple of roms (CM9, CM10) builds from October 2013, they worked.
While testing I realized that these roms were a lot snappier than the CM11 one I was dissatisfied with, noticing that besides hard reset on camera usage I also had a lagging UI. I assume that SELinux might be one of the reasons for the camera hard resets I experienced, but have no proof for this..
Then I spent a couple of days debugging the problem and it turns out, that all of the problems arise indeed from the kernel used.
Atm, I run a butter smooth CM10.2 nightly rom dating 2014-03-31, but running on a kernel dating 2014-01-20 (ripped out of CM11-nightly!).
For this to happen, simply exchange zImage under /system/bootmenu/2nd-boot/
Extract zImage from 2014-01-20 rom beforehand, put it on sdcard.
After installing the latest rom, before rebooting, do
- Mount /system with TWRP
- Go to Tools > Filemanager
- Select the 2014-01-20 zImage in TWRP Filemanager
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
- Wipe cache/dalvik
- Reboot
I have tested this setup and it runs amazingly! I tested GPS turning on an off, Camera works (except video with stock app), Wifi works - no reboots and the UI is a breeze. It simply behaves as it should. Neither zRAM or zCache is activated, battery consumption is low, as is CPU usage.
Conclusion: The latest nightly kernels suck hard for green lense defy, but I still do not know exactly why.
Fazit: Can confirm that zImage from 2014-01-20 is tried and tested.
===================================
How solution was found: I read in the forums, that update-recovery.zip contains a kernel. Since after flash of CM10.2-2014-03-31 I had bootloop problem, I went to TWRP recovery on blue led, which still worked, and installed update-recovery.zip AFTER rom. Normally, you do not do this, since this DOWNGRADES kernel. But if latest kernel does not work, there is a chance succeeding with this method.
Ok, after flashing update-recovery.zip zImage dating 2013-11-07 was in place and phone booted with CM10.2-2014-03-31 image. I thouhgt I had found the solution, but soon noticed, that this kernel had issued with GPS (it would hang and not turn off, once activated). The immediate next step was to look for a kernel built after 2013-11-07 - I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
http://defy.bytekiste.de/cm11-nightly-defy+/
Since, on defy.bytekiste.de CM10.2 listing stopped at 2013-10-30, and with update-recovery.zip I already had a kernel from 2013-11-07, I jumped to CM11 roms, as I did not know about existence of defy.svolkov.name at that time.
defy.svolkov.name lists CM10.2 nightly builds from 2014-01-09 on. One could probably try the kernels directly from these roms. However, I think the difference in kernels between CM10.2 and CM11 is neglectible. What matters is the timestamp of the builds - different timestamp, different kernel config and that seems to decide whether it's working on defy green lense or not.
===================================
I did not further bisect the problem yet, i.e. trying each nightly kernel built after 2014-01-20 in succession to see which build first caused the bootloop problem. However I've checked some of the roms and the file structure on quarx2k.ru and defy.bytekiste.de (you can find complete structure of both on http://defy.svolkov.name/), it's borked:
versions for cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
versions for cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
6e05a8e9205f30a212be5aafc6e4bc01 http://defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/cm-11-20140117-NIGHTLY-mb526.zip
now, from the above, if you thought
"defy.bytekiste.de/cm11-nightly-defy+" and
"defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+"
were mirrors wrt same-named files, think again.
versions for cm-11-20140120-NIGHTLY-mb526.zip
0602c6090ffa169dcf249b49f3c1d2be http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip (appears to have a different ramdisk-recovery, other files in 2nd-boot dir are identical to rom below)
d9a88dde07c06474d60dc353c53babc8 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip
also note,
"defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/"
holds the most recent list of nightlies, while the listing starts with
20140109 version, and continues until
20140117 version (see versions above)
it omits 20140120 completely, and then continues from
20140123 version.
===================================
I actually wanted to post this in dev forums CM10.2 on defy thread, but do not have more than 10 posts on xda-dev, so are not allowed to. This is why I post it here.
Thanks!
cmuelle8 said:
...
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
...
I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
h t t p : / / d efy.bytekiste.d e/cm11-nightly-defy+/
...
Click to expand...
Click to collapse
Thanks for posting your findings. I first thought "it will be fixed soon" when my camera didn't work after a update. Then, because no one was complaining, i thought the camera in my Defy is broken.
I have almost done the same and now the camera is working again
1) extracted the zImage from 2014-01-20
2) "adb push" it to the sdcard
3) mount -o remount,rw /dev/block/mmcblk1p21 /system/
4) cd /system/bootstrap/2nd-boot
5) cp /sdcard/zImage .
6) reboot
7) happy
Any later kernels that show the same stability?
Edit: My Defy will not boot after replacing the kernel. I'm on cm-11-20140611 now.
I think you are refering to camera bug #44?
I have the same with my Defy green lense (MB525). I've found out that the bug was introduced in CM11 with the ROM from 2014-03-15. So the camera worked for me without problem until the ROM from 2014-03-13. Since then I have to set the minimum frequency at least to 600MHz. Below that value e.g. 500MHz I get indeed bootloopss when using camera or gallery. Disabling the HWA settings for the most apps (besides the camera) delayes only the unavoidably bootloop for some seconds.
Do you think it's possible to use the newest CM11 nightly ROM together with the last working ROM from 2014-03-13?
The camera-bug #44 still exists since the ROM_2014-03-15. But I think I could narrow down the problem a little. It seems to be the kernel, means the file "zImage" under /bootstrap/2nd-boot. When I took that file from the last working ROM_2014-03-13 and apply it to a later problematic ROM, then the bug #44 is gone (for me). I've successfully tested this workaround until the ROM-version from 2014-03-25. Since ROM_2014-04-01 and later this doesn't work because the phone wont start, maybe to much has changed within the ROM. The replacement (camera2.apk, MediaProvider.apk) or the deletion (wallpapper, etc.) of some system-apps leads to no success. Deactivating the autofocus-function or the GPS-tagging for the pictures doesnt help either. However, until now the phone reboots fairly fast when I scroll the taken pictures within the camera-app. Maybe it has something to do with my sdcard (read performance, whatever)?!?!? But the chance is very small, because it had worked outstanding until the ROMs before 2014-03-14 ;-(