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

Search This thread
By:
Advanced…
L

L3vYad1n

Member
Mar 11, 2012
41
19
0
sevenrock said:
http://forum.xda-developers.com/showpost.php?p=50547301&postcount=2820
http://forum.xda-developers.com/showpost.php?p=50617966&postcount=2903
http://forum.xda-developers.com/showpost.php?p=51019403&postcount=3314
Click to expand...

haha, okay man i think i got it :p
Thanks for your help!

---------- Post added at 03:17 PM ---------- Previous post was at 02:37 PM ----------
sevenrock said:
http://forum.xda-developers.com/showpost.php?p=50547301&postcount=2820
http://forum.xda-developers.com/showpost.php?p=50617966&postcount=2903
http://forum.xda-developers.com/showpost.php?p=51019403&postcount=3314
Click to expand...

unlucky me, it's still pops out with the error..
 
T

topperdoggle

Member
Dec 27, 2011
33
6
28
Hi all,

I was on the verge of selling my Defy Plus as I find it so slow and laggy. Apps I tend to use: Waze / Amazon MP3 / Google Play Music / Browser - no games, but still it's a drag. Currently running Quark's CM7.x (Gingerbread).

Would I likely benefit from a better user experience with Kitkat? People seem to be happy but in my experience newer software of any sort is generally more bloated and slower than the previous version, hoping that people won't notice as new hardware will be out.
 
B

bhupatib

Senior Member
Nov 28, 2011
387
427
93
okij said:
I'm not completely sure about this, because - while AOSP KitKat always had the arrows disabled - the CM team had decided to keep them in CM11, so they had been working both for Wifi and 2G/3G until about 2 weeks ago.
Click to expand...

I think that was a bad move. Such performance gains wouldn't have bothered a snapdragon 800 phone but might be significant on our ancienty omap defy.
Also, is it just me or the data connectivity on CM11 (1503 clean) feels more 'lazy' than on CM10.2? It sometimes refuses to connect but comes back after a while... might it be that the 'arrow override' is causing some conflict?

I know, logs or didn't happen! Purely subjective...

---------- Post added at 08:50 PM ---------- Previous post was at 07:56 PM ----------

 @okij
Bug #35 is fixed for me on 20140315. I drained my battery then plugged it in and the phone booted correctly to the charging screen by itself. I'm on a clean install.
One thing I noticed is that YouTube (latest) is FCing frequently and non-hq (240p) stream shows glitches. HQ stream (360p up) working properly.
a7e3upum.jpg


I'll try to get logs of the FC and try with previous versions/other apps to see it's really ROM related.

Update: YouTube glitch is app specific :mad: Viral works fine.
 
Last edited:
  • Like
Reactions: frozenwaverider and okij
H

Hasuris

Senior Member
May 13, 2013
280
152
0
topperdoggle said:
Hi all,

I was on the verge of selling my Defy Plus as I find it so slow and laggy. Apps I tend to use: Waze / Amazon MP3 / Google Play Music / Browser - no games, but still it's a drag. Currently running Quark's CM7.x (Gingerbread).

Would I likely benefit from a better user experience with Kitkat? People seem to be happy but in my experience newer software of any sort is generally more bloated and slower than the previous version, hoping that people won't notice as new hardware will be out.
Click to expand...

I think while 4.4 is considerably faster than any 4.x-rom before it, it's not quite as fast as CM7. I am happy with 4.4 (not using CM though, prefer roms that stay closer to AOSP) You can't compare the defy with mid to toprange phones from today. It will never be as snappy and responsive as any of those. But CM7 laggy? Hm. Maybe your phone has a lot of apps running in the background, there is no greenify on Gingerbread after all and to me greenify makes a whole lot of a difference.

So yeah, try 4.4 + greenify and see how it goes.
 
H

htto

Senior Member
Feb 12, 2014
99
194
0
gist.github.com
YetAnotherForumUser said:
Code: 
[email protected]:/ $ df /system                                                      
Filesystem               Size     Used     Free   Blksize
/system                325.1M   236.5M    88.7M   1024
No gapps, running ART.
Click to expand...

Code: 
  >> ssh [email protected] /system/xbin/df -h /system
Filesystem                Size      Used Available Use% Mounted on
/dev/block/mmcblk1p21
                        325.1M    249.5M     75.6M  77% /system

g'apped :p

And just to quote myself:

"
[..]
did you ever notice that there are three apps the kitkat defy rom bundles, that set LOCAL_AAPT_INCLUDE_ALL_RESOURCES to true?
[..]
This results in inclusion of drawables for all display sizes. Which is nice for unbundled apps, but those four are always bundled and this wastes some space on system. Diffed bytes (old <, new >)

< 1534794 02-29-2008 03:33 system/app/CMFileManager.apk
> 637937 02-29-2008 03:33 system/app/CMFileManager.apk
< 8079911 02-29-2008 03:33 system/app/LockClock.apk
> 1096082 02-29-2008 03:33 system/app/LockClock.apk
< 15577925 02-29-2008 03:33 system/priv-app/Settings.apk
> 3262870 02-29-2008 03:33 system/priv-app/Settings.apk
< 460128 02-29-2008 03:33 system/bootstrap/2nd-boot/ramdisk
> 354116 02-29-2008 03:33 system/bootstrap/2nd-boot/ramdisk
< 3403455 02-29-2008 03:33 system/bootstrap/2nd-boot/ramdisk-recovery
> 2942884 02-29-2008 03:33 system/bootstrap/2nd-boot/ramdisk-recovery
"

The ramdisk contains SuperUser.apk, which also used to set LOCAL_AAPT_INCLUDE_ALL_RESOURCES.
 
Last edited:
  • Like
Reactions: hotdog125, sevenrock, frozenwaverider and 1 other person
O

okij

Senior Member
Oct 24, 2012
1,685
3,656
143
Düsseldorf
List of known bugs updated for 03-15 nightly

I decided to update the list of known bugs for today's 03-15 nightly, because the overall feedback has been good both on xda and on the German android-hilfe forum. :D A big thanks to @Quarx! :good:

bhupatib said:
[/COLOR] @okij
Bug #35 is fixed for me on 20140315. I drained my battery then plugged it in and the phone booted correctly to the charging screen by itself. I'm on a clean install.
Click to expand...

Thanks for reporting. I tried it myself and can confirm that power off charging is working again, so I marked bug #35 as fixed. :) On a side note: Before the charging screen appears, you first see the red Motorola logo and then the new safestrap menu. Just wait a few more seconds and it will boot further to the charging screen.

frozenwaverider said:
Regarding bug 2f, ph speaker not playing ringtones/notifications after using Bluetooth: I had that but after a couple of reboots it seems to be fixed, I'm now on just over 70hours up time, ph audio works perfectly & I make many bt calls per day
Can anyone else confirm this?
One thing I did was a cache/dalvik wipe when I flashed the fix
Click to expand...

Thanks for reporting! :)

It would be great if someone who uses bluetooth (e.g. YapFas, @sevenrock and @AcnapyxoB who reported this bug) can confirm that bug #2f is fixed now, so I can also mark it as solved...
 
Last edited:
  • Like
Reactions: arod81, hotdog125, Proverbs2 and 6 others
AcnapyxoB

AcnapyxoB

Senior Member
Mar 17, 2008
107
94
58
okij said:
I decided to update the list of known bugs for today's 03-15 nightly, because the overall feedback has been good both on xda and on the German android-hilfe forum. :D A big thanks to @Quarx! :good:



Thanks for reporting. I tried it myself and can confirm that power off charging is working again, so I marked bug #35 as fixed. :) On a side note: Before the charging screen appears, you first see the red Motorola logo and then the new safestrap menu. Just wait a few more seconds and it will boot further to the charging screen.



Thanks for reporting! :)

It would be great if someone who uses bluetooth (e.g. YapFas, @sevenrock and @AcnapyxoB who reported this bug) can confirm that bug #2f is fixed now, so I can also mark it as solved...
Click to expand...

About bug #2f: after using bt hands-free and reboot it's seems to be OK... will see in the future:rolleyes:

Meanwhile I find (maybe) another bug: when press restart from power menu phone isn't restarted!

2014.03.15 build
 
Last edited:
P

portsample

Senior Member
May 13, 2009
111
33
48
Better connectivity...

portsample said:
Is anyone else having problems getting a signal with the most recent build? I've been getting regular "Emergency Calls Only" messages, in locations (like my residence) where I had no problem connecting with this phone when it was running CM10.1 last week.
I'm on the AT&T network.

I have done the following to my new CM11.0 install,
1) gone to Settings-->Wireless & networks-->Mobile networks, and selected "search for available networks", selected "choose automatically". ATT was shown, I then selected and registered as ATT.
2) contacted ATT and was told that their frequencies where I live (rural Alaska) are the same as in many other places: 850 and 1900mhz.
3) went to Settings-->Advanced-->Baseband Selection, and chose a country that has these two bandwidths...currently using "Argentina, Personal 3.4.2-107-7" . It does seem odd to do this, however none of the (3) T-Mobile bandsets listed include both of the bandwidths ATT provides.

Is there something else that I'm not doing? TIA
Click to expand...

Okay- I appear to have drastically improved connectivity. I did the following,
1) Installed the most recent 11.0 build after doing a tear down to stock Nordic ROM.
2) Go to Settings-->Advanced-->Baseband selection. Specify the appropriate bands for your cellular carrier. I use ATT in Alaska on 850/1900 mhz and searched until I found a country with these two bandwidths. I'm currently using settings for TIGO/Movistar in Columbia, South America. Go figure.
3) Reboot your device fully TWICE. Do it. After the first boot I did not get a signal. After second reboot I got full bars in the signal icon. Don't know why, it just appeared to work that way.
4) Now, go to Settings-->under Wireless & Networks, click "More..."-->select "Mobile Networks"-->"Network Operators". Hopefully at this point your phone will respond with the cell networks in your area. I selected "Choose Automatically" because only one ("ATT") was shown.
5) Reboot again.
Good luck.
 
Last edited:
  • Like
Reactions: Alka-Seltzer PLUS and noideaforaname
L

Lightis

Senior Member
Mar 8, 2012
94
55
0
Upgraded from 11.03 to 15.03. (Full download). Im running art and 15.03 seems much more fluid than 11.03.. Very cool!!



Sent from my MB526 using xda app-developers app
 
  • Like
Reactions: 2rgman
Proverbs2

Proverbs2

Senior Member
Feb 1, 2012
291
319
0
YetAnotherForumUser said:
I use the ART runtime, maybe you should try this as well? I make the switch at install time (by editing build.prop) so Dalvik never runs.
Click to expand...

overclockthesun said:
I did use the build. Prop method and found that it was more stable. Unfortunately I ran out of space on /data so switched back to dalvik.
Click to expand...

@YetAnotherForumUser, @overclockthesun, or anyone else who knows how to do this: could you please explain what lines need to be added or changed in build.prop to make ART run at install time? I've already tried searching the XDA forums and Google, but I wasn't able to find clear instructions.

Someone on another forum indicated that
Code: 
persist.sys.dalvik.vm.lib=libdvm.so
must be changed to
Code: 
persist.sys.dalvik.vm.lib=libart.so

Is that the only thing I need to do, or must other lines be changed as well? Thanks in advance.
 
  • Like
Reactions: frozenwaverider
A

andycore

Senior Member
Apr 2, 2009
83
86
0
Sydney, Australia
www.wogasink.com.au
okij said:
It would be great if someone who uses bluetooth (e.g. YapFas, sevenrock and AcnapyxoB who reported this bug) can confirm that bug #2f is fixed now, so I can also mark it as solved...
Click to expand...

I'm not sure if it's relevant because it wasn't a phone call, but I use a set of Bluetooth headphones for music (Motorola S10-HD) that also double as a handsfree -- powered them off when I was done training this morning and didn't have any trouble with the phone playing notifications or ringing afterwards.
 
  • Like
Reactions: okij and frozenwaverider
leandeganis

leandeganis

Senior Member
Feb 4, 2012
300
170
0
Buenos AIres
topperdoggle said:
Hi all,

I was on the verge of selling my Defy Plus as I find it so slow and laggy. Apps I tend to use: Waze / Amazon MP3 / Google Play Music / Browser - no games, but still it's a drag. Currently running Quark's CM7.x (Gingerbread).

Would I likely benefit from a better user experience with Kitkat? People seem to be happy but in my experience newer software of any sort is generally more bloated and slower than the previous version, hoping that people won't notice as new hardware will be out.
Click to expand...

I think you would definitely benefit from using Greenify, and Xposed Framework with "BootManager" and "ReceiverStop" modules (use it wisely, search and learn), rather than just from a ROM.

Also try V6 Supercharger. Search XDA for that too.
 
Last edited:
  • Like
Reactions: topperdoggle
G

Gulia

Member
Sep 25, 2013
21
10
0
Re: [Kitkat] CM11 Android 4.4 for the Defy(+)

Proverbs2 said:
@YetAnotherForumUser, @overclockthesun, or anyone else who knows how to do this: could you please explain what lines need to be added or changed in build.prop to make ART run at install time? I've already tried searching the XDA forums and Google, but I wasn't able to find clear instructions.

Someone on another forum indicated that
Code: 
persist.sys.dalvik.vm.lib=libdvm.so
must be changed to
Code: 
persist.sys.dalvik.vm.lib=libart.so

Is that the only thing I need to do, or must other lines be changed as well? Thanks in advance.
Click to expand...


I few days back I PM YetAnotherForumUser and got his reply. Many thanks to him


YetAnotherForumUser said:
All you have to do is set/edit the following line in build.prop before booting the phone:

Code: 
persist.sys.dalvik.vm.lib=libart.so

Either edit build.prop from within an adb shell in TWRP or run a script to do the same. I use something like this after installing, from within an adb shell in TWRP:
Code: 
#!/system/bin/sh

sed -i -e 's/persist.sys.dalvik.vm.lib=libdvm.so/persist.sys.dalvik.vm.lib=libart.so/' /system/build.prop
My normal script changes more settings (dpi, low_ram, supplicant_scan_interval, etc).
Click to expand...
 
Last edited:
  • Like
Reactions: Proverbs2 and frozenwaverider
You must log in or register to reply here.

Similar threads

Quarx
[JB] CM10 Android 4.1.2 for the Defy(+)
Replies
18K
Views
7M
U
ujos
mauroaraujo
  • Locked
[ JB++ ] For Defy and Defy+ (Quarx based)
Replies
7
Views
4K
wedgess
wedgess
Quarx
[DEV][ROM] CyanogenMod 7.2.0 (Android 2.3.7)
Replies
18K
Views
6M
vai0
vai0
N
Quarx【BUG BIG BUG】of the ClockworkMod Recovery 3.0.2.8 of Quarx
Replies
0
Views
1K
N
[email protected]
Quarx
[JB+] CM10.2 Android 4.3 for the Defy(+)
Replies
2K
Views
764K
9Lukas5
9Lukas5

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 862
    Quarx
    Quarx
    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]
    Click to expand...

    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
    View
    176
    O
    okij
    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.
    View
    149
    Quarx
    Quarx
    Just some news:)
    View
    115
    Quarx
    Quarx
    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]:/ #
    View
    73
    Quarx
    Quarx
    okij said:
    @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! ;)
    Click to expand...
    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.
    View

New posts

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