[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)

Search This thread

lucasfpaixao

Senior Member
Jun 9, 2013
91
27
38
Investigating RIL problems

As mentioned a few postings back, I also have those RIL related reboots on my green lense Defy, but from what I can tell they are not related to GPS usage.
Erdnuesse mentioned in his post, that after a few days those reboots were gone, as long as he sticked to a certain baseband version and did not install the nightlies on a daily basis...
So I am curious how it turns out, if I let my Defy run without changing anything system related for a few days.

About the RIL reboots (telephony layer problems). Using february, 25 ROM on Defy+ (MB526) with core Gapps.
They continue to happen for me and I cannot find any situation that should be related to this condition. It's happening in every situation.
- Along the night when I'm sleeping and I wake up with a bright light on my side: the device it's under the boot process (twice times in the same night with no usage);
- this also already happened twice during a phone call (this is very annoying situation, the call mute, phone layer problem on the screen and I need to reboot);
- and also happened when using the internet;
- Other users reporting about GPS usage.

So, no specific condition can be related to this.

Ten minutes ago my phone cannot connect to the carrier. I switched to airplane mode and some android process freezes showing an error but I even cannot hit OK and the screen blacked out and I cannot wake it up again forcing me to take the battery off.

I already switched my baseband to the correct place (as I thought this could be the reason of this problem) but it still happening as before.

I'm getting a lot of reboots, I check in the AeroControl app that somethimes the deepsleep mode is working and sometimes is not working.


I installed Catlog and I'm recording a log right now. I will save this log and post here as soon as it has a telephony layer problem (save just before a RIL reboot). I think this could be useful to the developers.

I'm still happy with th 1 or 2 seconds of screen call delay. It is strange that some users still reporting this problem. Right now I make a test while recording the log with Logcat, I called my own number and the screen wakes up instantly, zero delay, immediately when rang!!!

I will post the log as soon as it crashes again.
 

okij

Senior Member
Oct 24, 2012
1,685
3,656
143
Düsseldorf
@Quarx: I just read the comments on your commit "Don't use symlink for start bootmenu" and I think that there still is one typo left that pipcet wrote about:

I think that line 8 in bootmenu/binary/logwrapper

Code:
+/system/bootmenu/binary/busybox chmod 755 /system/[B]bib[/B]/bootmenu

should be

Code:
+/system/bootmenu/binary/busybox chmod 755 /system/[B]bin[/B]/bootmenu

:)
 

overclockthesun

Senior Member
Jul 29, 2011
431
270
93
Mumbai (Bombay)
About the RIL reboots (telephony layer problems). Using february, 25 ROM on Defy+ (MB526) with core Gapps.
They continue to happen for me and I cannot find any situation that should be related to this condition. It's happening in every situation.
- Along the night when I'm sleeping and I wake up with a bright light on my side: the device it's under the boot process (twice times in the same night with no usage);
- this also already happened twice during a phone call (this is very annoying situation, the call mute, phone layer problem on the screen and I need to reboot);
- and also happened when using the internet;
- Other users reporting about GPS usage.

So, no specific condition can be related to this.

Ten minutes ago my phone cannot connect to the carrier. I switched to airplane mode and some android process freezes showing an error but I even cannot hit OK and the screen blacked out and I cannot wake it up again forcing me to take the battery off.

I already switched my baseband to the correct place (as I thought this could be the reason of this problem) but it still happening as before.

I'm getting a lot of reboots, I check in the AeroControl app that somethimes the deepsleep mode is working and sometimes is not working.


I installed Catlog and I'm recording a log right now. I will save this log and post here as soon as it has a telephony layer problem (save just before a RIL reboot). I think this could be useful to the developers.

I'm still happy with th 1 or 2 seconds of screen call delay. It is strange that some users still reporting this problem. Right now I make a test while recording the log with Logcat, I called my own number and the screen wakes up instantly, zero delay, immediately when rang!!!

I will post the log as soon as it crashes again.

RIL problems started for me again today almost randomly. I guess the problem is in the telephony layer. Selecting a proper baseand helps. Also using BBS, I repair the baseband and restart and again select the proper baseband for my region. This unfortunately has to be done on every update ...including incremental or else RIL bug shows up again.

So for anyone wondering, apparently flashing a higher bootloader does not help.

Also, the screen delay still exists for me. It is next to nothing when using ART though.
 
  • Like
Reactions: okij

sevenrock

Senior Member
Nov 27, 2012
660
1,095
123
@Quarx:
frameworks/base/media/jni/android_media_MediaRecorder.cpp: In function 'void android_media_MediaRecorder_pause(JNIEnv*, jobject)':
frameworks/base/media/jni/android_media_MediaRecorder.cpp:360:42: error: 'class android::MediaRecorder' has no member named 'pause'
frameworks/base/media/jni/android_media_MediaPlayer.cpp: In function 'jboolean android_media_MediaPlayer_suspend(JNIEnv*, jobject)':
frameworks/base/media/jni/android_media_MediaPlayer.cpp:824:13: error: 'class android::MediaPlayer' has no member named 'suspend'
frameworks/base/media/jni/android_media_MediaPlayer.cpp: In function 'jboolean android_media_MediaPlayer_resume(JNIEnv*, jobject)':
frameworks/base/media/jni/android_media_MediaPlayer.cpp:840:13: error: 'class android::MediaPlayer' has no member named 'resume'
Please merge upstream commits from https://github.com/CyanogenMod/android_frameworks_av/commits/cm-11.0 to fix the compile problem.
 
  • Like
Reactions: frozenwaverider

jountha

Senior Member
Sep 18, 2012
95
9
0
Installed 22-02 build n now my camera is not working properly. C d pic
I tried to go back to 24-01 but again I saw d same prob but it was not der with this build before.
Even any camera app take d same kind of pic

Sent from my MB526 using XDA Premium 4 mobile app
 

Attachments

  • 1393445287031.jpg
    1393445287031.jpg
    255 KB · Views: 464

okij

Senior Member
Oct 24, 2012
1,685
3,656
143
Düsseldorf
Installed 22-02 build n now my camera is not working properly. C d pic
I tried to go back to 24-01 but again I saw d same prob but it was not der with this build before.
Even any camera app take d same kind of pic

Sent from my MB526 using XDA Premium 4 mobile app

I like this picture, it looks as if your Defy smoked dope... :D

(Sorry for this inappropriate comment. ;) I don't have a clue what may cause your problem, but please post at least if you have a green or a red lens Defy, so that the community can help you. If nothing else helps, I would recommend to start from SBF.)
 

frozenwaverider

Senior Member
Dec 9, 2012
251
154
0
Auckland
Anyone with RIL problems: Firstly, make sure you are on the correct baseband for your phone, not your location, i.e. I am in NZ but my proper baseband is China
A long time ago I tried every one in bbs but still had problems, the best solution for me was to extract my original bb from my factory sbf using 7zip
Secondly when you have applied the bb reboot, then reboot in to recovery clean cache/dalvik, this was suggested by another user & works for me, don't believe me? Try it ;)
Good luck

MB525 Red lense
 
Last edited:

sa3e1

Senior Member
Jan 18, 2010
253
77
0
Budapest
I realized, that baseband itself, and only baseband can't be the cause for telephony reboots.
I was on mb525/bl7/default cpu/bb 3.4.2--145 on The 20140120(or so) build. Had reboots the first few days, tried different bbs, stayed on the one mentioned, fewer reboots, until they disappeared after few days.
I updated to 20140220 with the same settings. Telephony problems reappeared.
This time I did not change basebands, because I knew that I already have found a good one. After 3 days maybe, the telephony problems were never seen again.
If you upgrade to every single nightly, you won't recognize that.
This may be helpful for someone.
Regards.

Can confirm this behaviour!

Sent from my Defy green lense using xda-developers app
 
  • Like
Reactions: erdnuesse

2rgman

Senior Member
Apr 15, 2012
202
90
0
@Quarx: I just read the comments on your commit "Don't use symlink for start bootmenu" and I think that there still is one typo left that pipcet wrote about:

I think that line 8 in bootmenu/binary/logwrapper

Code:
+/system/bootmenu/binary/busybox chmod 755 /system/[B]bib[/B]/bootmenu

should be

Code:
+/system/bootmenu/binary/busybox chmod 755 /system/[B]bin[/B]/bootmenu

:)

Already fixed by quarx I think...
https://github.com/Quarx2k/android_...mmit/b49d67203084c7c7f2694baf93b5e1ade5bda586
 

bone101

Senior Member
Jan 6, 2012
692
137
0
No telephone layer problems here...

I've did a clean (system&data wipe) install , since i updated from 17.1.2014 build , where i had some problems with wifi wont connect , to 22.2 build & now to 25.2 build w.o data wipe .

No ril bug here...

Sent from my MB525 red defy bootloader 4 (Stok froyo 2.2.2
German retail .SBF
 
Last edited:

lucasfpaixao

Senior Member
Jun 9, 2013
91
27
38
About the RIL reboots (telephony layer problems). Using february, 25 ROM on Defy+ (MB526) with core Gapps.
They continue to happen for me and I cannot find any situation that should be related to this condition. It's happening in every situation.
- Along the night when I'm sleeping and I wake up with a bright light on my side: the device it's under the boot process (twice times in the same night with no usage);
- this also already happened twice during a phone call (this is very annoying situation, the call mute, phone layer problem on the screen and I need to reboot);
- and also happened when using the internet;
- Other users reporting about GPS usage.

So, no specific condition can be related to this.

Ten minutes ago my phone cannot connect to the carrier. I switched to airplane mode and some android process freezes showing an error but I even cannot hit OK and the screen blacked out and I cannot wake it up again forcing me to take the battery off.

I already switched my baseband to the correct place (as I thought this could be the reason of this problem) but it still happening as before.

I'm getting a lot of reboots, I check in the AeroControl app that somethimes the deepsleep mode is working and sometimes is not working.


I installed Catlog and I'm recording a log right now. I will save this log and post here as soon as it has a telephony layer problem (save just before a RIL reboot). I think this could be useful to the developers.

I'm still happy with th 1 or 2 seconds of screen call delay. It is strange that some users still reporting this problem. Right now I make a test while recording the log with Logcat, I called my own number and the screen wakes up instantly, zero delay, immediately when rang!!!

I will post the log as soon as it crashes again.


Ok, here's the log. The problem happened when I was walking and listening to music.

https://www.dropbox.com/s/fo159rbq26j3o5v/2014-02-26-16-23-21.txt
 
  • Like
Reactions: ssefrgr

Jarod42

Senior Member
May 8, 2012
76
37
0
Cannot make backups with TWRP

A few days back I installed cm-11-20140222-NIGHTLY-mb526.zip starting from SBF with framaroot 1.9.1, sndinitdefy 2.3, defy_twrp_recovery_2.6.3.0.zip + update-recovery.zip.

From that day on I could not do a Backup from TWRP anymore. The wim image files for data and system were always 0 bytes long even though it took the phone over 350 seconds to backup the data. I first thought that the sdcard might be full, or the FS corrupted, but the FS is ok and there are 4GB free space left.

And on top of this... After trying to backup my data partition today, my phone booted up and showed this warning.
I should mention that I just spend 3 hours in restoring the system and my app backups after I re-installed the Feb 22nd nightly again.

Has anyone else experienced those kind of problems?
 

Attachments

  • Screenshot_2014-02-27-09-41-09.jpg
    Screenshot_2014-02-27-09-41-09.jpg
    37.7 KB · Views: 559
Last edited:
  • Like
Reactions: leandeganis

jouwheld

Member
Aug 7, 2009
20
6
0
I disabled cLock this morning, because it was eating a up my battery. Since then, a couple of hours, I haven't had any telephony layer reboots! And battery isn't empty as it was before after 5 hours.
Nightly 25-2 fresh install from a bl4 sbf done two days ago.

Sent from my A1_07 using xda premium
 

AGDC04

Member
Oct 8, 2008
8
0
0
Salto
I have this problem, when i live the quality of signal is poor, and if i in a call and lose the signal, the error telephony layer occur, after update to 2014-02-25, i don't have this problem using internet, and before the same problem occur on internet. I don't make test with call. But the rom is stable for me and fast. when boot has free 180mb of ram.
 
Last edited:

Jarod42

Senior Member
May 8, 2012
76
37
0
Just carefully read instructions :
Where did you read trw_2.6.3.0 + recovery.zip? :banghead:

I downloaded the defy_twrp_recovery_2.6.3.0.zip from here: http://d-h.st/users/tejus.k.v

I read this post about flashing the Defy from SBF: http://forum.xda-developers.com/showpost.php?p=50621131&postcount=2906

I even tried installing CM11 without the update-recovery.zip, but the installation finished within a second and without an error, but nothing was installed. So I figured I had to install the update-recovery.zip in order to be able to install CM11. As it turned out... After installing update-recovery.zip, CM11 installed flawlessly(from what I could tell).
 
  • Like
Reactions: leandeganis

measel

Senior Member
Jan 13, 2011
984
541
113
Lockscreen question

Here's what I'm not able to accomplish:

I want to use the standard slider shortcuts with the lockscreen. I asked before but with no avail.

I disabled Sim PIN but enabled Lockscreen PIN and after that the PIN pad instantly opens when pressing the lock symbol. I can't longpress it to get to the slider shortcuts.

Any idea or is it an inteded behaviour?

Thx.
 

Attachments

  • device-2014-02-27-133633.png
    device-2014-02-27-133633.png
    61.7 KB · Views: 399
  • device-2014-02-27-133721.png
    device-2014-02-27-133721.png
    39.6 KB · Views: 401
  • device-2014-02-27-133732.png
    device-2014-02-27-133732.png
    39.8 KB · Views: 396

Top Liked Posts

  • There are no posts matching your filters.
  • 862
    Android 4.4 Kitkat for Defy/Defy+ and Bravo

    Links:
    http://quarx2k.ru/motorola/defy/bravo.7z
    http://quarx2k.ru/motorola/defy/defy.7z
    http://quarx2k.ru/motorola/defy/cm-11-20161124-NIGHTLY-mb52x.zip

    Recommended GAPPS: http://forum.xda-developers.com/showthread.php?t=2779598

    How to install ROMs after 1 October:
    0. Need sdcard and ~30mb free space.
    1. Download defy.zip or bravo.zip (depend on your phone)
    2. Boot into TWPR, install new_boostrap.zip.
    3. Reboot.
    4. Boot again in TWRP, install resize.zip
    5. Reboot
    6. Install latest CyanogenMod 11 build.
    7. Be happy :cyclops:

    How move from stock directly to new boostrap.(Guides)

    List of known issues
    F.A.Q

    If you liked this project, you can donate :)
    Donate to Quarx
    PayPal: [email protected]
    AliPay ID [email protected]
    New Dnate App in Google Play: https://play.google.com/store/apps/details?id=cyangendefy.donatedefycm11
    ---------------------------------------
    Donate to Blechd0se
    PayPal: [email protected]

    Experimental 3.x Kernel

    About Android L: Waiting for sources:)

    XDA:DevDB Information
    [Nightlies] CM11 Android 4.4 for the Defy/Bravo, ROM for the Motorola Defy

    Contributors
    Quarx, Blechd0se
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 2.6.x
    Based On: CyanogenMod 11

    Version Information
    Status: Nightly

    Created 2014-10-10
    Last Updated 2017-08-12
    176
    Update to known bugs for the 01-24 nightly of CM11 (kernel 2.6.32.9) for Defy(+)

    Here is my updated list of the known bugs for the 01-24 nightly (download mirror here) together with jajb's GApps Minimal Edition for Android 4.4.x [240 DPI], as an information both for the Defy users and for @Quarx, @Blechd0se, @SlugZero, @struq, @htto, @m.ksy, @YetAnotherForumUser, @CBongo and the other devs for the further development of CM11.

    FYI: I keep a history of known bugs of one older nightly here for reference purposes (as some now solved bugs contained links to other posts which might still be useful for the devs).

    To distinguish the solved bugs from the others, I decided to mark them in three different ways:
    • Bugs that are written normally are not solved yet.
    • Bugs that are written in brackets have already a fix (e.g. a flashable zip) which hasn't made it into the current nightly yet. Please note that some of these fixes still need some more approval.
    • Bugs that are struck out and are written in light grey are already fixed in the current nightly.

    Now for the bugs:
    1. Apps on SD card disappear: This has been solved by courtesy of Juansheng and struq. :)
    2. Several Bluetooth related bugs (2a. BT-headset has problems; 2b. BT will not work, if FM is enabled; 2c. Handset mic, earphone and speaker all muted during calls if BT enabled even when not connected to any BT device; 2d. Connecting to a BT keyboard works, but writing with it is not possible; 2e. BT tethering to another device with internet access is buggy; 2f. After using BT, the phone speaker isn't working; 2g. Song name and other information is missing when playing on car stereo via BT, 2h. Voice is weak and sometimes distorted on some BT audio devices): SlugZero posted here that the usage of the BlueZ stack (when its finished) might solve the BT issues. Bugs #2a and #2c have been solved by courtesy of Quarx and SlugZero. :) SlugZero found some documentation for .bts file format of the TIInit file here which may help with further improvements. :) Here I collected some information that might be useful for fixing bug #2b. Bug #2d is fixed since at least 07-24 nightly. :) Bug #2e has been solved by courtesy of Quarx. :) Bug #2f has been fixed. Bug #2g has been fixed. Bug #2h has been solved by courtesy of Quarx. :) Volume is somewhat lower than under CM10 or under stock ROM, but - as frozenwaverider wrote here - this is the same on other devices running on CM11 and not Defy specific. Here you can find a list of BT headsets that were reported to work well.
    3. The app switcher previews sometimes don't work correctly: This bug has already been solved for CM10.2 and CM11, as struq wrote here. :)
    4. Sometimes the IMEI isn't present after booting: This bug seems to be fixed since about 01-20 nightly. In some rare cases it might still occur, but we shouldn't distract our developers with it. ;) If it occurs, usually a reboot or a hot boot (e.g. with a Rebooter app) helps to get the IMEI back quickly.
    5. Torch tile is missing in Quick Settings: This bug has been solved by courtesy of czechop and struq. :)
    6. Apps like CPU Spy, No-frills CPU Control and Aero Control don't show the correct CPU frequencies and their usages: This bug has been solved by courtesy of Blechd0se in v1.2.0 of his Aero Control app. :)
    7. Mute button is not working: This bug has been solved by courtesy of Quarx. :)
    8. Mobile network stays off after reboot: This bug doesn't occur anymore since 12-10 nightly. :)
    9. Network mode switch (2G/3G) doesn't seem to work: This bug doesn't occur anymore since 12-10 nightly. :)
    10. Battery drain / no deep sleep: I found the culprit for this bug (which was not caused by the ROM), as reported here. Besides this, a new WiFi battery drain bug which started with the 02-08 nightly has been fixed again by courtesy of Quarx. :)
    11. Self-hot-boot after booting: This bug doesn't occur anymore since 12-10 nightly. :)
    12. Dialer doesn't go into landscape mode when Defy is in car holder: This bug has been solved by courtesy of nadlabak. :)
    13. Changing baseband doesn't work: This bug has been solved by courtesy of czechop, cyrusct82 and codeseven58. :)
    14. Wifi tethering is not working: This bug has been solved by courtesy of Quarx and struq. :)
    15. Opening downloaded files, especially apks, from the notification pull down list doesn't work: This bug doesn't occur anymore since 12-10 nightly. :)
    16. Camera preview shows just a black screen in panorama mode: This bug has been solved by courtesy of Quarx. :)
    17. TWRP sometimes crashes: This bug doesn't occur anymore since 01-20 nightly. :)
    18. The statusbar sometimes is flipped out when a call ends and the phone is taken away from the ear: As a workaround, Quarx disabled the status bar in InCallUI. :) Sometimes this bug still happens even with the workaround, though very rarely. If you want to have a look at the status bar (e.g. for checking the signal strenght), you can still swipe it down, as Pecan-fan explained here.
    19. FM radio is giving no sound: This bug has been solved by courtesy of Quarx. :)
    20. Camera force closes when trying to record in SD or HD: This bug has been solved by courtesy of Quarx. :)
    21. Charging sometimes doesn't work after using USB OTG: This bug has been confirmed by sevenrock as an already known OTG bug here (which affects changing the USB connections in general), along with instructions by SlugZero for a manual workaround (i.e. unplugging and replugging the cable at least once more). :)
    22. Booting to recovery from power menu doesn't work: This bug has been solved by courtesy of Quarx. :)
    23. Interactive governor uses 600 instead of 300 MHz when device temporarily wakes up from deep sleep: This bug has been solved by courtesy of Blechd0se. :)
    24. Missing Wi-Fi MAC address under Phone Status: This bug has been solved by courtesy of Quarx. :)
    25. USB tethering stops working after installing the update from 2014-01-03: This bug has been solved by courtesy of Quarx. :)
    26. Screen needs about 5 seconds to wakeup when a call is received: This bug has been solved by courtesy of pawitp and htto. :) Additionally, to have the device wake up quickly, it can help to disable suspend for Interactive governor and change hispeed_freq to 1200000 (or whatever maximum frequency you use) in Aero Control. Also please keep in mind that running heavy apps can lead to a longer wakeup time due to memory management. As frozenwaverider wrote here, disabling all call lookup in Phone app also helps to reduce call delay.
    27. Wifi does not return after long sleep (> $timeout minutes) when configured to sleep when screen is dark: This bug doesn't occur anymore since at least 04-09 nightly. :)
    28. CM updater doesn't work: This bug has been fixed. :) If you still encounter problems with incremental updates (which might occur if your system files have been changed), download the full build here and install it manually via TWRP over your working CM11 installation as a workaround.
    29. zRAM option in performance settings is missing: This is not a bug. :) As Quarx wrote here, users reported about problems with zRam, so this option is not available since Android 4.4.
    30. Random reboots: This bug doesn't occur anymore at least since 03-15 nightly, as has been reported by several users for the stock frequencies an Vsels. :) Please note that overclocking and undervolting can lead to random reboots and that CM11 is more sensitive for this than e.g. CM7 (using the same OC/UV settings), as several users have reported. Also overclocking the CPU to 266 MHz can lead to random reboots or telephony layer problems, so Quarx set back GPU to default 200 MHz since 06-09 nightly. If it's stable for you, you can still overlock GPU to 266 MHz via Aero Control.
    31. Screen is half blacked out while getting incoming calls: This bug is fixed since 02-11 nightly. :)
    32. Setup wizard crashes: This bug has been solved by courtesy of Quarx. :)
    33. ART runtime isn't working after 02-21 nightly: This bug has been fixed at least since 02-25 nightly. :)
    34. In some rare cases, Wifi authentication isn't working: This bug has reported by J.R. here and confirmed by clément here. It seems to have started with the wl12xx.ko drivers that have been introduced after CM10-20130307 nightly, as clément confirms here. J.R. posted dmesg logs of two Defys here with the same bootloader and SBF, running on the same software configuration, of which interestingly one shows the bug and the other doesn't. J.R. posted another dmesg log here. As sutter.cane wrote here, his AP's log shows no attempt of his defy's mac trying to connect. As sutter.cane wrote here, this bug got fixed for him by flashing his AP (Netgear WG102 FW 5.0.3) to an older (v5.0.0) firmware. Still, as J.R. writes here, he doesn't think this is dependent from the used AP, but only a few MB525 with green lens in combination with the specific used wifi driver are affected from this bug. J.R. posted a new log file here. User sunnysays mentioned the culprit commit here. As Saturnal wrote here, he managed to leave it stable after unchecking the "Wi-Fi Optimization" option under Settings > Wi-Fi > Advanced. Quarx suggested here to change MTU to 1492, but as J.R. wrote here, it didn't help, including log file. As Arathon wrote here, using Connectify helped him to establish a connection, including log files.
    35. Power-off charging isn't working: This bug has been fixed by courtesy of Quarx. :)
    36. For some users, TWRP backup just produces files with zero filesize: This bug has been solved by courtesy of Quarx. :) However, I still recommend Online Nandroid Backup, which can make TWRP compatible backups with the advantage that you can make the backups while your Defy is running, so you don't have to reboot to TWRP.
    37. Camera crashes when saving video files: This bug has been fixed in CM repo since 03-18 nightly. :)
    38. Pulling down the status bar doesn't always work in expanded desktop mode: This is no bug, as explained here. :) Remember to make the swipe (sort of) straight downward, because if it's too diagonal (e.g. when using your thumb), the status bar doesn't get pulled down.
    39. Defy doesn't boot up (battery pull needed) when rebooting from advanced menu or via a 3rd party app: This bug has been solved by courtesy of Quarx. :)
    40. The phone is indicating 100% battery after more than 4 hours of use out of charging: This bug doesn't occur anymore. :)
    41. Barcode Scanner app force closes: For green lens Defys, this bug has been solved by courtesy of Quarx and m.ksy. :) For red lens Defys (including Defy+), this fix was in conflict with their 720p video recording capabilities, but newer versions (> 4.7.0) of Barcode Scanner were reported to work again.
    42. CM Updater stopped working after 04-17 nightly: This bug has been fixed again. :) Please note that sometimes the update server can't be reached (which isn't a bug on the software side).
    43. SystemUI sometimes freezes or crashes: This bug has been solved by courtesy of CM dev Clark Scheff. :)
    44. For some green lens camera users, camera operation leads to reboots: This bug has been solved by courtesy of Quarx. :)
    45. Telephony layer problems: This generally is a hardware bug which can't be fixed because we have to use Morotola's proprietary driver. Since about 07-24 nightly, this bug doesn't seem to occur more often than in stock firmware or other CM builds. If you still have problems, you can try those hints and workarounds:
      • As a workaround, until this bug is solved, you can explicitely register to your provider's network through Settings > Mobile > Choose Network, as has been reported by domokos here and confirmed to me by mmerlone via PM.
      • As dc239 wrote here, disabling high end graphics, wiping cache & dalvik and fixing permissions solved this issue for him.
      • Replacing the SIM card can help, as kan4 and domokos wrote here and here.
      • In my experience, cleaning the contacts of the SIM card and the battery, as well as the corresponding contacts on the phone can help.
      • Also having set the Vsels too low can lead to this bug, as e.g. reported by Codeseven here.
      • As lak2004mi described here, here and here, manually replacing bp_nvm_default files with suitable file solved this issue for him.
      • Turning off location can help, as has been reported by fede_arg's here and confirmed by btwin here.
      • Using a different baseband can help, as has been reported by a couple of users.
      • Also letting the system settle for 12+ hours after installing a new nightly can help, as reported by lucasfpaixao here, as well as by users on android-hilfe.de
      • Disabling the GPU driver via Aero Control or limiting GPU frequency to 200 MHz can help, as bbllaazzee and domokos wrote here and here.
      • As gbossley wrote here, this bug gets stopped for him when calling his Defy from another number.
    46. Phone gets stuck when rebooting after telephony layer problem: This bug has been solved by courtesy of Quarx. :)
    47. Whatsapp is unable to play voice message and then FC: This bug was fixed in 05-24 nightly. :)
    48. MMS function isn't working properly: This bug has been reported by hendrikmerkel here and confirmed by Lord_Flaya here. User jsoi wrote here that false editing (just saving) the MMS APN settings in mobile network settings serves as a temporal workaround. As frozenwaverider wrote here, changing authentication type to PAP (from none) for both internet & MMS APN's fixed this issue for him. :) As hendrikmerkel wrote here, this bug might be provider / network dependent, although this problem doesn't exist under CM7. Here and here hendrikmerkel and Avesi gave summaries of what they tried to get MMS to work. As Quarx wrote here, he did some changes for MMS, so maybe this bug got better. As jsoi wrote here, now sending and receiving MMS is at least working with Wifi for him, but not with mobile network yet. As I, ooo and hendrikmerkel wrote here, here and here, MMS still isn't working in 09-08 nightly. x53 wrote here about his test results for this bug. hendrikmerkel wrote here, here, here and here some new infos concerning this bug.
    49. Camera force closes when trying to record two succeeding videos: This bug has been solved by courtesy of Quarx. :)
    50. CPU stays at 2nd highest frequency (800 MHz) while charging): This bug has been solved by courtesy of Quarx. :)
    51. When switching off via power menu, the phone powers on by itself after some minutes: This bug has been solved by courtesy of sevenrock, dmasu and CBongo. :)
    52. Playback of recorded 720p videos doesn't work with built-in player: This bug has been solved by courtesy of Quarx. :)
    53. When doing an incremental update, the kernel isn't updated, i.e. copied to /bootstrap/bootstrap: This bug has been solved by courtesy of Quarx. :)
    54. TWRP sometimes gets lost when doing incremental updates: This bug has been reported by several users. As granazis wrote here, it even occurs when the fixed new_bootstrap.zip from 13.10.2014 is used. Here I described a way to get TWRP back. As starbright_ wrote here, the automatic trim mechanism (which becomes active while charging) might also lead to TWRP getting corrupted.
    55. Recent builds are slow and have spontaneous reboots: This has been marked as solved, because it rather is a problem of the newer Google Play Services 6.x which are more resource-demanding than before, as sevenrock wrote here. With the help of 1ceb0x, here I collected a list of Google services, receivers and providers that can be disabled with My Android Tools. :) Additionally, using RAM Booster helps to keep the system responsive, as masbitxo reported here. :)
    56. Force High-End Graphics / Low Memory Option is missing / buggy since 01-10 nightly: I reported this bug here and it was confirmed e.g. by RT567 here. Beware that after turning on the Low Memory Option via Aero Control, CM11 won't boot anymore until you re-flash the nightly!
    Besides these bugs, some of the CM-features might not work correctly yet. For these we shouldn't bother Quarx but just wait for the CM developers to fix them.

    So this is my summary. Please feel free to add other noteworthy bugs to it and also please report if bugs have been fixed. :cowboy:
    If you want to help by providing logs, here you can find a very good tutorial by measel. :)


    Wish List: :fingers-crossed:
    • Please re-enable the zRAM option in performance settings, as I requested here.
    • Please fix the red colour text messages during installation that x53 summarized here, because they might scare off some less experienced users.
    • It would be interesting to have the list of bad blocks be scaled-down according to CBongo's findings here, freeing up an extra ~3MB for either /system or /data.
    • As leandeganis wrote here, it would be great if the 20s timeout of touchscreen lectures could be changed/removed.
    Here I keep some information that is worth mentioning:
    • If you have problems with GPS fix, you might try gps_lto_patch-signed.zip from here which automates long term orbit data download, as further described here. Also GPS Status app can help to get or keep GPS fix, as was described by Male_zvire here. GPS Status can also be used to manually download A-GPS data for faster fixes.
    • YetAnotherForumUser wrote here how to check whether device is "provisioned" or not and here how to manually set the provisioning bits. This solved some severe problems of Saturnal, as you can read here.
    • To stop Themes to always run in background and occupy RAM, you can disable its Notification Access (via Settings > Security), as vishal.kulkarni30 wrote here.
    • cLock (a.k.a. LockClock) has been removed by Quarx since 07-08 nightly, which is benefical for bugs #26, #30 and #45! If you are looking for a similar widget as a replacement, beware that both Crius and Chronus are based on the same code and lead to the same bugs (as I tested), so better use WeatherLove, Easy Weather or DashClock.
    • If you have problems with custom batteries (always 100% or not chargeable, or if the battery level is shown with a question mark, as DiegoxG wrote here), you can switch to Quarx's battery driver, as he explained here. Beware that this is not recommendable if you don't have problems with your battery, as the battery level tends to jump up and down with this driver.
    • It is possible to record 848x480 videos (which work with ~20 fps in comparison to 720p with ~12 fps) with MIUI camera, as was reported by dc239 and bhupatib here and here and with Open Camera, as dmasu wrote here.
    From my experiences, CM11 (kernel 2.6.32.9) runs smooth and stable and is a great daily driver, if you can live with the known bugs.
    149
    Just some news:)
    115
    Some good news :)
    After 2days and 15+ times reflashing sbf, i finally resized partitions on defy nand! With locked bootloader! All works fine, sdcard not used at all:)
    Code:
    [email protected]:/ # mount
    rootfs / rootfs ro,noatime,nodiratime 0 0
    tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
    devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
    proc /proc proc rw,noatime,nodiratime 0 0
    sysfs /sys sysfs rw,noatime,nodiratime 0 0
    none /acct cgroup rw,noatime,nodiratime,cpuacct 0 0
    tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
    tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
    tmpfs /mnt/fuse tmpfs rw,noatime,nodiratime,mode=775,gid=1000 0 0
    none /dev/cpuctl cgroup rw,noatime,nodiratime,cpu 0 0
    tmpfs /storage tmpfs rw,noatime,nodiratime,mode=050,gid=1028 0 0
    /dev/block/mmcblk1p1 /bootstrap ext3 ro,noatime,nodiratime,errors=continue,barrier=1,data=writeback 0 0
    /dev/block/mmcblk1p5 /system ext4 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
    /dev/block/mmcblk1p6 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
    /dev/block/mmcblk1p7 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
    /dev/block/mmcblk1p8 /pds ext3 rw,noatime,nodiratime,barrier=1,data=writeback 0 0
    ramfs /tmp ramfs rw,noatime,nodiratime,relatime 0 0
    /dev/block/vold/179:1 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    /dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    /dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
    [email protected]:/ # df
    Filesystem               Size     Used     Free   Blksize
    /dev                   239.5M   140.0K   239.4M   4096
    /mnt/asec              239.5M     0.0K   239.5M   4096
    /mnt/obb               239.5M     0.0K   239.5M   4096
    /mnt/fuse              239.5M     0.0K   239.5M   4096
    /storage               239.5M     0.0K   239.5M   4096
    /bootstrap              49.2M    18.6M    30.6M   4096
    /system                617.1M   286.3M   330.8M   4096
    /cache                  47.2M     4.3M    43.0M   4096
    /data                    1.0G   640.1M   433.8M   4096
    /pds                     3.9M     1.1M     2.8M   1024
    /mnt/media_rw/sdcard0     1.8G     1.6G   205.1M   4096
    /mnt/secure/asec         1.8G     1.6G   205.1M   4096
    /storage/sdcard0         1.8G     1.6G   205.1M   4096
    [email protected]:/ #
    73
    @Quarx: Thanks a lot for todays nightly, which is running very stable and smooth so far! :victory:
    For your next nightly, could you probably look after bugs #3 and #5? Both should be easily fixable, because in my bug list I already pointed to the necessary patches, and some of us are really missing the torch tile - after all, this would bring a light to all of us in the wait for Christmas! ;)
    Thanks for problem list:)
    I forgot include torch fix:( WIll be in next nightly.
    About next nightly, i'm not sure when i release it, next two weeks i'll be very busy with my diploma.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone