FORUMS
Remove All Ads from XDA

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

1,318 posts
Thanks Meter: 18,847
 
Post Reply Email Thread
9th December 2013, 07:17 AM |#1031  
mihovil13's Avatar
Senior Member
Thanks Meter: 292
 
Donate to Me
More
Guys what do I need to do when updating to a newer nightly?just wipe cache and dalvik (even though I use ART), and do I need to reflash gapps aswell?

Sent from my Nexus 7 using XDA Premium HD app
The Following User Says Thank You to mihovil13 For This Useful Post: [ View ] Gift mihovil13 Ad-Free
 
 
9th December 2013, 07:24 AM |#1032  
overclockthesun's Avatar
Senior Member
Flag Mumbai (Bombay)
Thanks Meter: 270
 
More
Quote:
Originally Posted by mihovil13

Guys what do I need to do when updating to a newer nightly?just wipe cache and dalvik (even though I use ART), and do I need to reflash gapps aswell?

Sent from my Nexus 7 using XDA Premium HD app

If using ART don't wipe anything. It will work just fine

Sent from my MB526 using Tapatalk
9th December 2013, 07:37 AM |#1033  
ScratMan38's Avatar
Senior Member
Flag Grenoble
Thanks Meter: 462
 
More
Using ART require compiling apks to make it native CPU code, so it takes more space on the system partition.
So it is faster to execute, but it will be longer to install apps, and it requests more storage space.

So if you want to use ART, you absolutely need to remove unwanted ringtones, languages, apps, etc...
9th December 2013, 08:52 AM |#1034  
Senior Member
Thanks Meter: 151
 
More
Quote:
Originally Posted by ScratMan38

Using ART require compiling apks to make it native CPU code, so it takes more space on the system partition.
So it is faster to execute, but it will be longer to install apps, and it requests more storage space.

So if you want to use ART, you absolutely need to remove unwanted ringtones, languages, apps, etc...

That's what I thought too BUT on my Nexus7 there is no difference in /system between dalvik and art. Enabled ART on my defy too and it's the same. Either /system is excluded somehow when enableing ART or the extra code is stored elsewhere.

Also I am having a hard time to see any performance gains from ART. It should speed up the process of first opening of an uncached app, especially on a slow phone like our Defy. To me it feels like this takes even longer than with DALVIK. Opening of cached apps on the other hand is very fast. Could be just as fast with DALVIK though, hard to tell.
The Following User Says Thank You to Hasuris For This Useful Post: [ View ] Gift Hasuris Ad-Free
9th December 2013, 10:31 AM |#1035  
Member
Thanks Meter: 0
 
More
my wifi still doenst work. I have installed the lastest cm11. Any help?
9th December 2013, 02:13 PM |#1036  
overclockthesun's Avatar
Senior Member
Flag Mumbai (Bombay)
Thanks Meter: 270
 
More
Well, flashed the rom again today. Clean. Baseband switcher sitll does not work. It ends o\up on Central Europe baseband again.
9th December 2013, 02:19 PM |#1037  
YetAnotherForumUser's Avatar
Senior Member
Thanks Meter: 1,654
 
More
Quote:
Originally Posted by Hasuris

That's what I thought too BUT on my Nexus7 there is no difference in /system between dalvik and art. Enabled ART on my defy too and it's the same. Either /system is excluded somehow when enableing ART or the extra code is stored elsewhere.

Also I am having a hard time to see any performance gains from ART. It should speed up the process of first opening of an uncached app, especially on a slow phone like our Defy. To me it feels like this takes even longer than with DALVIK. Opening of cached apps on the other hand is very fast. Could be just as fast with DALVIK though, hard to tell.

From my experiments with art I assume that the compiled code lands in the cache (usually /cache), not in /system. Check the contents of /cache after switching to art, pull some of those files to a PC and run the file command on them (assuming you use Linux) and you'll find that those files are ELF executables - the compiled code produced by art.
The Following 3 Users Say Thank You to YetAnotherForumUser For This Useful Post: [ View ] Gift YetAnotherForumUser Ad-Free
9th December 2013, 05:00 PM |#1038  
sepp.'s Avatar
Member
Thanks Meter: 48
 
More
Quote:
Originally Posted by struq

For those who are missing AOSP, here is a fresh new build.
This is based on Quarx's repo (seems abandoned?), build with recent updates.

Very nice indeed !
All I need is working (the BT sound is none of this build)
ART: no hassle at all: just works (install - switch - install core GApps - install further apps)
Very energy aware - Thank you
Had only one little issue (and this once so far) with dialing app

-- have to update my signature
The Following User Says Thank You to sepp. For This Useful Post: [ View ] Gift sepp. Ad-Free
9th December 2013, 05:56 PM |#1039  
Senior Member
Flag Düsseldorf
Thanks Meter: 3,051
 
More
Info 2 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.
If you want to help by providing logs, here you can find a very good tutorial by measel.


Wish List:
  • 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.
The Following 176 Users Say Thank You to okij For This Useful Post: [ View ] Gift okij Ad-Free
9th December 2013, 06:01 PM |#1040  
overclockthesun's Avatar
Senior Member
Flag Mumbai (Bombay)
Thanks Meter: 270
 
More
@okij,

I don't know if this is a bug but have you noticed that if your phone is plugged into the computer, charging is sort of random. Unless usb debugging is enabled it won't work.... and if you restart your phone while it is still plugged in, you need to remove and re-attach the usb cable to the phone again for charging to work.

2) opening anything you download from the notification pull down list won't work. Especially apks....
The Following 2 Users Say Thank You to overclockthesun For This Useful Post: [ View ] Gift overclockthesun Ad-Free
9th December 2013, 06:05 PM |#1041  
Senior Member
Thanks Meter: 544
 
More
Quote:
Originally Posted by measel

first impressions for 13-12-01 (sure most of the bugs are already mentioned):


big bugs:

  • USB problems (apparently charging, massstorage, detection by computer in general even after driver update
  • mobile network OFF after reboot. Have to toggle flight mode. (not reproducable but twice so far)
  • BT completely broken (no FM no BT activation)
small bugs:
  • Sim-PIN pad screwed
  • localization not complete as stated already
  • Recovery via power menu doesn't work
observations:
  • Xposed Framework seems to slow down system
  • overall speed is impressive! but not tested with tons of apps installed
  • wifi seems to be stable

solved since 13-12-01:
USB problems (apparently charging, massstorage, detection by computer in general even after driver update
BT completely broken (no FM no BT activation)

more observations/problems for 13-12-05 (please confirm/deny):
  1. OBackup doesn't work because it's not able to update (root problem I guess) (see image for info text) > any help?
  2. BetterBatteryStats only shows "Kernel Wakelocks" not Partial or Processes...
  3. AndroidOS battery drain: 50% in 6h > rx_wake 1h11m, after toggeling flight mode back to normal.
  4. Slider Shortcuts are missing after setting Screen Lock. After deactivation there is no slider whatsoever.
  5. Charging LED still on after setting it to OFF.
  6. Graphical glitch in lock screen pad: some letters don't fit next to the numbers. (see image)
  7. Graphical glitch in Calibration tool: Arrow is off. (see image)
  8. Graphical glitch in Settings > Display & Lights > Notification lights > ADD: The icon sizes vary! (see image)
Findings:

I had this question: "Any idea if it is possible to get back the good ol' checkbox for "Default app"-question? For certain actions I don't want a Default, so I always have to click twice." and just found out that you could TAP TWICE for instantly open in chosen app! Wohooo.

Maybe something for your list @okij. Didn't see you entered your post just now. Btw. sorry for the yellowish tint of the images. It was the app Twilight...


I think it is already good enough for daily usage. Thank you @Quarx and @Blechd0se.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2013-12-08-10-27-17.png
Views:	842
Size:	114.6 KB
ID:	2444220   Click image for larger version

Name:	Screenshot_2013-12-08-21-34-55.png
Views:	829
Size:	182.0 KB
ID:	2444221   Click image for larger version

Name:	Screenshot_2013-12-09-17-19-35.png
Views:	806
Size:	82.6 KB
ID:	2444222   Click image for larger version

Name:	Screenshot_2013-12-09-18-24-43.png
Views:	815
Size:	115.5 KB
ID:	2444223   Click image for larger version

Name:	Screenshot_2013-12-09-18-51-22.png
Views:	754
Size:	34.4 KB
ID:	2444224  
The Following 5 Users Say Thank You to measel For This Useful Post: [ View ] Gift measel Ad-Free
Post Reply Subscribe to Thread

Tags
baseband switcher, led, quarx for world emperor, quarx is still a god

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes