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

Search This thread
By:
Advanced…
O

okij

Senior Member
Oct 24, 2012
2,028
3,934
Düsseldorf
Samsung Galaxy S10e
Theory: Recent GApps lead to freezes / Bug #51 / Question about MIUI Camera / etc.

x53 said:
As mentioned here I may have found a freeze bug. After 2 days of operation the phone freezes and is unusable. When I plug the charger, nothing happens (LED doesn't start to flash). When I call the phone nothing happens, too. Besides the caller hears the ring ton. ADB isn't possible, too.
I could track the bug in the following ROMs: CM11-20141010, ...1024 and ..1102. I'm sure in CM11-20140923 the bug wasn't there.
Click to expand...
Click to collapse

I also have/had the feeling that the October + November nightlies are not working as stable as the 09-23 nightly.

However, currently I am on 11-02 nightly but since a couple of days I am not using one of the latest jajb's Minimal GApps, instead I am using the older 2014-10-05 Minimal GApps. So far it seems that my system is running more stable this way.

The reason for this is that I got the feeling that the new v5.0.x Play Store that has been introduced in the 2014-10-12 Minimal Gapps (which was a v4.9.x version before) and/or that the Play Services which made a jump from v6.1.11 to v6.1.71 in this period could be responsible for system freezes and reboots on our Defys.

So could you please check if using 2014-10-05 (or older) GApps helps you too with the recent nighties, or if using the recent GApps together with the 09-23 nighly does provoke freezes too on your device? :fingers-crossed:

---

dmasu said:
as an info for the devs @Quarks, @Blechd0se, @sevenrock and the like:

I identified cm-11-20140702 to be the first Nightly affected by the bug! I hope checking the log will show the responsible change and will make it easy to fix it.
Click to expand...
Click to collapse

@dmasu: Many thanks for your report, it should indeed be very useful for fixing bug #51! :good:

@sevenrock: Since you have been following the same approach, could you (as well as @Quarx) have a look which commit between 07-01 and 07-02 nightly is responsible for bug #51. :fingers-crossed:

---

bhupatib said:
* Stock Camera doesn't focus on 0211 and Google camera is a memory hog. Use MIUI camera (very fast & has 848x480 video as well).
Click to expand...
Click to collapse

Stock Camera is focusing fine here on my Defy+ on 02-11 nightly.

Anyway, I tried your tip to use MIUI camera for 848x480 video recording and it works well, with decent frame rates. :)

However, I have just a quite old version of MIUI camera (downloaded from here) and I don't like about it that an almost intransparent bar hides about 1/6 of the right screen area when using video mode. :(

A more recent version of MIUI camera from here doesn't work on my Defy (it just force closes).

So which version of MIUI camera are you using? Does it also have this almost intransparent bar on the right side?

---

Edit / addition 1:

masbitxo said:
Hello everyone!
In green lens Defy not working the video camera on the last ROM (11/05), however, the camera works properly.
Here I leave the link to the log.
https://docs.google.com/file/d/0B00F9XnJ4G3eZHJwME5IclluYWc/edit?usp=docslist_api
Click to expand...
Click to collapse

Can other green lens Defy users confirm this?

Should I put it on the bug list or is it rather caused by some faulty or incomplete CM commit that will be fixed again in one of the next nightlies?

---

Edit / addition 2:

@Quarx: I added a new (minor) bug #53 to the bug list: When doing an incremental update, the kernel isn't updated, i.e. copied to /bootstrap/bootstrap.
 
Last edited:
  • Like
Reactions: ThomasAH, Casteleugim, fadeinn and 1 other person
X

x53

Senior Member
May 8, 2013
126
90
freezed bug

@vai0: A download link would be very nice (apk, Playstore or ROM for extraction).
@okij: Thanks for reply, but I don't use GApps at all. Like I wrote, clean ROM installed and no settings changed besides:
* SIM inserted
* W-LAN and mobile-data turned off
* 2G only turned on
 
  • Like
Reactions: okij
D

dmasu

Member
Jul 3, 2014
16
31
x53 said:
@vai0: A download link would be very nice (apk, Playstore or ROM for extraction).
Click to expand...
Click to collapse

Just installed MIUIcamera_v17_Fixed2.apk from here as user app and it works fine - 848x480mode @20 fps, Camera focuses all right at 5MP. Haven't tested more so far.
But unfortunately, @okij, there is also this nearly intransparent bar in widescreen mode (but just some 8 mm of height, so just 1/10 of the screen).

@vai0: Did you installed it as system app and if so, which zip you used?
 
Last edited:
  • Like
Reactions: bhupatib, okij, Casteleugim and 1 other person
S

sevenrock

Senior Member
Nov 27, 2012
664
1,097
Motorola Defy
Moto G
dmasu said:
The testing showed that the old Nightlies 20131229, 20140518, 20140615, 20140630 and 20140701 are not affected by the bug.
Click to expand...
Click to collapse
My current assumption is that the power-on bug results from jordan-kernel, but using
a jordan-kernel tree dated June 29th (334e028eec48150d772999d3a8b54d3bcbedf20c)
my phone still switched itself on after power-off from within Android. So if your findings
are correct the bug results from a different package...

Currently I am scrolling through the commit logs from that time
Code: 
repo forall -c git --no-pager log --since="JUN 30 2014" --until="JUL 2 2014" --oneline
Maybe other users can join the bug hunt now ;)
 
  • Like
Reactions: leandeganis, dmasu, hrk and 2 others
O

okij

Senior Member
Oct 24, 2012
2,028
3,934
Düsseldorf
Samsung Galaxy S10e
eduardoeae said:
Could you provide link to that GApps?
The oldest one I have is 2014-10-12 :(
Click to expand...
Click to collapse

eduardoeae said:
I meant that old GApps version. @jajb doesn't keep old versions online. At least none I could find.
Click to expand...
Click to collapse

You are right. I just re-uploaded them for you to test:

gapps-kk-20141005-minimal-edition-gps034-240dpi-signed.zip

Please give us some feedback, if it makes a difference for you in comparison to the newer GApps versions. :)
 
  • Like
Reactions: retikulatus
B

bhupatib

Senior Member
Nov 28, 2011
395
434
Motorola Defy
LG V20
okij said:
Stock Camera is focusing fine here on my Defy+ on 02-11 nightly.

Anyway, I tried your tip to use MIUI camera for 848x480 video recording and it works well, with decent frame rates. :)

However, I have just a quite old version of MIUI camera (downloaded from here) and I don't like about it that an almost intransparent bar hides about 1/6 of the right screen area when using video mode. :(

A more recent version of MIUI camera from here doesn't work on my Defy (it just force closes).

So which version of MIUI camera are you using? Does it also have this almost intransparent bar on the right side?
Click to expand...
Click to collapse

For me the focus ring on the stock camera doesn't turn green. Maybe the reason you don't have it is because I clean installed whereas you might have gone the CMUpdater route. Anyways, I don't use stock cam so not an issue.

I use my themed version of MIUI Camera app to fix the ugly settings screen. You can download it here (uninstall the old one first) and see if it fixes the "intransparent bar" issue (I don't understand what it is though).
Someone with programming skills should try to build it from source and update the UI/minor glitches.
 
Last edited:
  • Like
Reactions: okij
H

HamsterX

Member
May 12, 2014
10
6
older gapps with current nightly

okij said:
..... So could you please check if using 2014-10-05 (or older) GApps helps you too with the recent nighties ........
Click to expand...
Click to collapse

hi okij (aso... )
i'm on 141105-nightly and the rom works approximative fine with the "old" gapps from quarx "GAppsForDefy*...... " from 05-2014. :)
also tested these rom with the recommended gapps from op and "gapps-kk-20141005.zip" with a lot of reboots and freezes each time. perhups, the changed PrebuiltGmsCore.apk could here be the reason?
 
  • Like
Reactions: okij
D

dmasu

Member
Jul 3, 2014
16
31
sevenrock said:
My current assumption is that the power-on bug results from jordan-kernel, but using
a jordan-kernel tree dated June 29th (334e028eec48150d772999d3a8b54d3bcbedf20c)
my phone still switched itself on after power-off from within Android. So if your findings
are correct the bug results from a different package...
Click to expand...
Click to collapse

I have installed (clean) and tested the 0701-nightly three times, with four, three and three on/off-test cyles to make shure that there is no reboot. Where as 0702, 0703 and 0704 all restarted during the first on/off-test cycle, after approx. 5, <1 and 7 min resp.

I won't be able to do more test cycles on the 0701-nightly this weekend, but if still necessary I could do more on this (or other) during next week. Please let me know.
 
Last edited:
  • Like
Reactions: okij, Badwater55 and bhupatib
vai0

vai0

Senior Member
Aug 21, 2009
87
16
Port Jupiter
Xiaomi Redmi Note 7 Pro
Redmi Note 10S
@dmasu : installed as normal app, in internal memory.

here is the screen shot of miui camera.
(it takes better pics in daytime :D)
 

Attachments

  • Screenshot_2014-11-07-23-40-41.jpg
    Screenshot_2014-11-07-23-40-41.jpg
    30.6 KB · Views: 2,110
G

granazis

Senior Member
Sep 3, 2009
665
460
Loutraki
Message to devs and members

granazis said:
Its known to me for 1st of october, so i decide to follow your opinion about the build that i am running now,MANY THANKS for your quick responce and the gapps site. i will try and inform you.
Best regards from Greece.
Click to expand...
Click to collapse
My experience on cm11 roms on my device mb525,bl,09.10,green lens,micro sd 16gb class 10

wifi ok-bt ok-gps ok-playstore ok-Adb ok-OTG ok(connect devices with max 150ma consumption)- camera ok-video rec no-incoming call normal without any change such aerokernel control.. etc(cpu min freq 300mhz max 1ghz),deep sleep of cpu ok(checked with wakelock full app)-when the phone is closed(turned off) suddently in few minutes boots up without reason(its a reported known bug)-trebuset launcher stops working,before stops when the phone coming from off to on state two pages got lost on the way? now i use the apex pro without problems- adaway app not work because of not enough space in system(may be its depended on gapps, i need less than 27mb),so iam trying to find a compatible build of gapps-battery state good for kkat rom-bup via online nandroid app ONLY,restore via this app or TWRP-and what i am going to find.

At the end of story my opinion is to dont try builds after 1st of october.Two roms
are better for my device 2-9-14 and 23-9-14 and stay with known bugs,or return to gb 7.2 or miui v4 ics,(stable roms for daily use and without such bugs)

Congratulations to new generation dvlprs and THANKS to devs such as quarks, Blechd0se, and the others for their hardworks
and in their seat i would never be in.Dvlpr its not only a profession,its hobby and passion in relationship.

Poor English?I am Greek.
My devices?Defy mb525,moto g xt1032 16gb,iphone 4s 16gb(that i hate),MINI 819T,Bberry 9520,Nokia N95 8gb,Htc HD.
My profession?Electronic engineer.My hobby now is to try roms,writting programs in c lang for arduino to make projects for frients and myself(already 64 years old).
The Americans says it worth what is going in your pocket,the Greek says its better to know than you have.-
 
Casper1982

Casper1982

Senior Member
Mar 20, 2013
575
137
La Pampa
I just want to know something!!

Lollipop Android 5.0 source code is fully available to build! :eek:
Anyone know if Quarx is already working? Thanks...
 
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
Sankyuuro
Sankyuuro
Quarx
[DEV][ROM] CyanogenMod 7.2.0 (Android 2.3.7)
Replies
18K
Views
6M
vai0
vai0
Epsylon3
[ICS] CM9.1 Android 4.0.4 for the Defy - now with 2ndboot kernels
Replies
8K
Views
3M
mick711
mick711
Quarx
[JB+][3.0.8/2.6.32 kernel] CM10.1 Android 4.2.2 for the Defy(+)
Replies
3K
Views
1M
M
mmbytes
Quarx
[JB+] CM10.2 Android 4.3 for the Defy(+)
Replies
2K
Views
794K
raphaelgamer981
raphaelgamer981

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://xdaforums.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: agent00791@gmail.com
    AliPay ID agent00791@gmail.com
    New Dnate App in Google Play: https://play.google.com/store/apps/details?id=cyangendefy.donatedefycm11
    ---------------------------------------
    Donate to Blechd0se
    PayPal: alex.christ@hotmail.de
    Click to expand...
    Click to collapse

    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: 
    root@mb526:/ # 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
root@mb526:/ # 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
root@mb526:/ #
    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...
    Click to collapse
    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