[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)
- Thread starter Quarx
- Start date
Battery Drain!
I'm on the 27032015 build. It's quite fluid compared to most other builds I've used recently. However, I'm having a pretty horrible battery life, with frequent battery drops as well. It might well be time to get a new battery, but i don't know if it's worth it.
In the meanwhile, I thought I'd play around with the frequencies and the governor, to see if there is any change.
Any suggestions for good settings?
Thanks in advance.
I'm on the 27032015 build. It's quite fluid compared to most other builds I've used recently. However, I'm having a pretty horrible battery life, with frequent battery drops as well. It might well be time to get a new battery, but i don't know if it's worth it.
In the meanwhile, I thought I'd play around with the frequencies and the governor, to see if there is any change.
Any suggestions for good settings?
Thanks in advance.
With the last Gaaps (2015 03 29), the Android Keyboard (Aosp) Stopped...I had to return to the previous version
Last edited:
Hello guys. I just disappeared for big time due work.Sorry for this. 
Now i got some free time.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
Now i got some free time.I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
Last edited:
Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
Do 5.1 because it would be funny :V...
@Quarx You're totally right. I'm using my Moto G LTE ( peregrine) with CM12 and even though it has 1Gb we suffer redraws everytime. In my case, Defy's only been used as alarm clock and to listen music ^^
I have two defy, one with the good old gingerbread 2.3.7 CM7 and one with the bleading edge provided by quarx. Both are primarily used for GPS navigation...
To see the newest android at my defy would really be fun!
To see the newest android at my defy would really be fun!
Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
In my personal opinion, it would be best to focus on fixing the remaining bugs (if there are any) on 4.4 and then be done with it. Thanks to you our Defy(+) has already had a much longer lasting software support than most of the devices on the market could dream of.
I also think that the Defy really reached its limits with 4.4 (if not broke them) and 5.0 would be too slow to be usable anymore. I've seen a few side-by-side benchmarks comparing 4.4 with 5.0 where 4.4 nearly always performed faster, no matter what runtime (ART or Dalvik).
tl;dr: Bring 4.4 to perfection (if your time allows it) and then move on to more recent phones... or just have some spare time for yourself
Many many thanks to your hard work. Without you the defy would have been worth much much less. You made it a better phone. You and all the other contributing devs.
Just my 2 cents.
@Quarx +1 for stable 4.4 if you get Kernel 3.10 working.. (Any news about this project?)
But it would also be nice to see some 5.1 nightlys..
But it would also be nice to see some 5.1 nightlys..
Last edited:
Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
5.1
Having 5.X on the Defy would of course be fun, bit i think its time to move on to other phones, just like i did last week to the Moto X 2.
Focus on the last remaining bugs and then be done with it.
U have made great work on the Defy and I think we all are glad for it, but as said, time to move on
Maybe to the Moto X 2?
Sent from my XT1092 using XDA Free mobile app
Focus on the last remaining bugs and then be done with it.
U have made great work on the Defy and I think we all are glad for it, but as said, time to move on
Maybe to the Moto X 2?
Sent from my XT1092 using XDA Free mobile app
I've been using a ****ty samsung core 2 (5mpx, quad-core, no 720p WTF) since it is running 4.4.4, and my defy is there as secondary phone, if it gets android 5 i'm gonna use it as main phone for sure, I can't understand why samsung released a 5mpx quad core phone without hd recording capabilities.Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
@Quarx
I'm using Defy as my main phone. I do not like phones with big screens(today you cannot find phone with good specs under 4.5 inches. Maybe Xperia Z1 Compact, but its too expensive for me) and old good Defy has everything that i need. I'm using your KitKat rom since months, and with some small modifications it's running pretty well. If you have time, it would be better to get stable KitKat with 3+ kernel. You can count on me if you need testers.
Thank you for your amazing work!
Поздрав из Србије!
I'm using Defy as my main phone. I do not like phones with big screens(today you cannot find phone with good specs under 4.5 inches. Maybe Xperia Z1 Compact, but its too expensive for me) and old good Defy has everything that i need. I'm using your KitKat rom since months, and with some small modifications it's running pretty well. If you have time, it would be better to get stable KitKat with 3+ kernel. You can count on me if you need testers.
Thank you for your amazing work!
Поздрав из Србије!
Last edited:
Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
My main Phone Is Defy+ and i will want defy 5.X more you can give to us and tnx for the hard work:good:
Last edited:
Hi master Quarx! It's great to have you back here! :victory:
I personally still use my Defy+ as my main and only Android phone.
Because of this, I would rather like to have a more stable Android 4.4.I remember that when Android 4.1 became stable, I easily could reach uptimes of more than two weeks without random reboots. Under 4.4 I usually just have uptimes of 2 to max. 4 days before a random reboot happens. I have the feeling that there are still too many memory leaks under 4.4, because the available memory gets less after some days of usage and e.g. Android-System and System-UI processes increase in size.
I was hoping that a 3.x kernel could bring us some performance improvements and also could help to get rid of those memory leaks, so it would be great if you could get a 3.x kernel fully working.
Anyway, If you decide to go for Android 5.1, I would also follow this with interest, even if I might not use it (until it would be fairly stable) because I need a well working OS on my Defy.
Do you think that 5.1 can be good for daily usage on a 512 MB device as the Defy? Would ART run better than it did under 4.4?
Thanks again for your steady commitment for the Defy! :highfive:
Edit: Wow, there have been 7 or 8 replies from other users while I was typing my reply. Respect! This community is still alive!
Last edited:
Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
I use Defy as the only phone, as for me, I'd like something to be stable....I am currently on cm-11-20150310-NIGHTLY-mb52x...
One day I'd like to come on 5.x but mainly I wanted something that would be the best so far, no problems and bugs.
I would not be explicit but what is easier to become a stable and useful. :angel:
in any case, thanks to the sky Quarx.
Хвала брате руски! :good:
Hello Quarx,
Thanks for your outstanding work! I'm still using my Defy+ as main phone and probably will for another 1 or 2 years; some apps require much resources from this "tiny" phone, so I hope there will be better roms. But if not, your time and work, thanks again for the contribution!
Hello guys. I just disappeared for big time due work.Sorry for this.
I know many want 5.0 for defy. But after look to 1gb and 512mb devices with lollipop..They all got big problems due memory leaks in android code. And it will not good, if very big time spent for nothing...Only if just for fun.
So, 5.1 fixed many memory problems of 5.0. And i want ask, are there someone who use Defy as main phone and really want update to 5.1? Because as i read this thread, most use it just for fun or as second phone. Android 5.1 wll take not little time to get it fully working..
Or better focus on 4.4?
What you think about it?
Hi Quarx!
I'm from Argentina. In my case, I use Defy as main phone. And I think I'll use it for the rest of the year, at least (Here, new phones are expensive lol). Soi, it would be great to upgrade to 5.1!, but if you think that it would be better to focus on 4.4, it would be great for me too!
By the way, thanks for your great great work!!!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
862Android 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
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-12176Update 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:
Apps on SD card disappear:This has been solved by courtesy of Juansheng and struq.
- 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.
The app switcher previews sometimes don't work correctly:This bug has already been solved for CM10.2 and CM11, as struq wrote here.
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.
Torch tile is missing in Quick Settings:This bug has been solved by courtesy of czechop and struq.
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.
Mute button is not working:This bug has been solved by courtesy of Quarx.
Mobile network stays off after reboot:This bug doesn't occur anymore since 12-10 nightly.
Network mode switch (2G/3G) doesn't seem to work:This bug doesn't occur anymore since 12-10 nightly.
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.
Self-hot-boot after booting:This bug doesn't occur anymore since 12-10 nightly.
Dialer doesn't go into landscape mode when Defy is in car holder:This bug has been solved by courtesy of nadlabak.
Changing baseband doesn't work:This bug has been solved by courtesy of czechop, cyrusct82 and codeseven58.
Wifi tethering is not working:This bug has been solved by courtesy of Quarx and struq.
Opening downloaded files, especially apks, from the notification pull down list doesn't work:This bug doesn't occur anymore since 12-10 nightly.
Camera preview shows just a black screen in panorama mode:This bug has been solved by courtesy of Quarx.
TWRP sometimes crashes:This bug doesn't occur anymore since 01-20 nightly.
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.
FM radio is giving no sound:This bug has been solved by courtesy of Quarx.
Camera force closes when trying to record in SD or HD:This bug has been solved by courtesy of Quarx.
- 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).
Booting to recovery from power menu doesn't work:This bug has been solved by courtesy of Quarx.
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.
Missing Wi-Fi MAC address under Phone Status:This bug has been solved by courtesy of Quarx.
USB tethering stops working after installing the update from 2014-01-03:This bug has been solved by courtesy of Quarx.
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.
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.
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.
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.
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.
Screen is half blacked out while getting incoming calls:This bug is fixed since 02-11 nightly.
Setup wizard crashes:This bug has been solved by courtesy of Quarx.
ART runtime isn't working after 02-21 nightly:This bug has been fixed at least since 02-25 nightly.
- 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.
Power-off charging isn't working:This bug has been fixed by courtesy of Quarx.
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.
Camera crashes when saving video files:This bug has been fixed in CM repo since 03-18 nightly.
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.
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.
The phone is indicating 100% battery after more than 4 hours of use out of charging:This bug doesn't occur anymore.
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.
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).
SystemUI sometimes freezes or crashes:This bug has been solved by courtesy of CM dev Clark Scheff.
For some green lens camera users, camera operation leads to reboots:This bug has been solved by courtesy of Quarx.
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.
Phone gets stuck when rebooting after telephony layer problem:This bug has been solved by courtesy of Quarx.
Whatsapp is unable to play voice message and then FC:This bug was fixed in 05-24 nightly.
- 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.
Camera force closes when trying to record two succeeding videos:This bug has been solved by courtesy of Quarx.
CPU stays at 2nd highest frequency (800 MHz) while charging):This bug has been solved by courtesy of Quarx.
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.
Playback of recorded 720p videos doesn't work with built-in player:This bug has been solved by courtesy of Quarx.
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.
- 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.
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.
- 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!
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: :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.
- 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.
115Some 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:/ #73
Thanks for problem list@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!
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.
