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

[bhupatib]

I cant confirm this for the 10-27 nightly, which feels very snappy and is performing well here.

I second that. The only problem I've run into is that the clock app force closes every time an alarm is set.

 

[sevenrock]

The only problem I've run into is that the clock app force closes every time an alarm is set.

Upstream bug which I also saw in my self-compiled ROM. I fixed it by reverting this commit:
https://github.com/CyanogenMod/andr...mmit/09ca6d3073e343d48bfb99d1c68c005042b7c272

I have yet to leave a note/logcat here: http://review.cyanogenmod.org/#/c/74312/

 

[okij]

What version should it be? I have 2.6.32.9-AeroKernel

"2.6.32.9-AeroKernel" in the first line of Kernel Version of course is OK.

I'm talking about the third line, which e.g. is "Mon Oct 27 03:02:06 CET 2014" in my case, having currently installed the full 10-27 nighty (which one can see under CyanogenMod Version under Phone Settings).

If you do an incremental update, the two dates differ, i.e. the kernel isn't updated because of a bug in the incremental updater script that @Quarx has yet to fix. After installing the incremental update, the contents of /system/bootstrap IMHO have also to be copied to /bootstrap/bootstrap.

I second that. The only problem I've run into is that the clock app force closes every time an alarm is set.

Upstream bug which I also saw in my self-compiled ROM. I fixed it by reverting this commit:
https://github.com/CyanogenMod/andr...mmit/09ca6d3073e343d48bfb99d1c68c005042b7c272

I have yet to leave a note/logcat here: http://review.cyanogenmod.org/#/c/74312/

Thanks for this info! :good:

Could you inform us here when this bug is fixed or the offending commit is officially reverted?

In the meanwhile, I think we could replace DeskClock.apk in /system/app with a version from before 10-09 (e.g. from 10-02 nightly) as a workaround, am I right?

 

[bhupatib]

In the meanwhile, I think we could replace DeskClock.apk in /system/app with a version from before 10-09 (e.g. from 10-02 nightly) as a workaround, am I right?

Or use this aosp port from play store:
https://play.google.com/store/apps/details?id=com.nemesis.deskclock

 

[bone101]

No problems with deskclock (alarm) here running 20141020 date nightley

newlife-defy bl.7 stock

 

[leandeganis]

For those complaining about performance of latest nightlies, I suggest a clean install if 02sep14 build, which is, IMO, the best nightly so far. Ive been testing others but this is for my daily usage, the best one.

 

[bhupatib]

No problems with deskclock (alarm) here running 20141020 date nightley

newlife-defy bl.7 stock

It's on 27th

 

[Coodarah]

2014-10-27 - FC when Alarm is set?

Mmmmh? ... (Edit: I didn't have any FC at all with it.)

Edit: Only thing I changed (beside using another ringtone) is to use the libstagefright.so from 2014-09-02. - Could this be relevant?

Edit 2: I reverted the library to the original, rebooted and re-did the alarm setting test: no force closes.

Edit 3: Try to fix permissions.

I second that. The only problem I've run into is that the clock app force closes every time an alarm is set.

 

[banjoe4711]

Thank you. I've replaced ramdisk-recovery from 03.10 build, and now can boot into recovery
My broken ramdisk-recovery was 3.4Mb too, and has right rights. So, I think, broken one have same size.

I have the same problem: I can not boot into TWRP recovery since last update. 3 seconds black screen, then reboot.

I tried to replace the ramdisk-recovery from several builds,but no luck. My last update was to 20141021 build a week ago. Main system is working fine...

Any ideas what to do?

 

[sevenrock]

No problems with deskclock (alarm) here running 20141020 date nightley

Maybe it is related to a custom ringtone (mp3 file from sdcard) I activated using Apollo.

 

[Vicsa]

I have the same problem: I can not boot into TWRP recovery since last update. 3 seconds black screen, then reboot.

I tried to replace the ramdisk-recovery from several builds,but no luck. My last update was to 20141021 build a week ago. Main system is working fine...

Any ideas what to do?

Just be sure that you are replacing it in the right folder /system/bootstrap/2nd-boot/ (because there are three different folders called bootstrap ) and set the right permissions..

Edit: Thanks @okij for correcting me: right folder has to be /bootstrap/bootstrap/2nd-boot.

 

[masbitxo]

Report concerning the bug # 51

Hi! In the last rom of the day October 28 I see that the bug # 51 repeats frequently, so I tried using logcat to make a record, I do not know if something will serve. After check, the phone has been turned on by itself after two minutes. It is a MB525 connected to the internet via wifi and a non-active sim.

https://drive.google.com/file/d/0B00F9XnJ4G3eaVpEM0pSVkpoaGM/view?usp=sharing

This is my first post in this section and I want to take this opportunity to thank all who make this forum and especially developers and Okij for having supported private messages that I had to send him for not being able to post here.

Thanks and regards.

 

[banjoe4711]

Thank you. I've replaced ramdisk-recovery from 03.10 build, and now can boot into recovery
My broken ramdisk-recovery was 3.4Mb too, and has right rights. So, I think, broken one have same size.

Originally Posted by banjoe4711

I have the same problem: I can not boot into TWRP recovery since last update. 3 seconds black screen, then reboot.

I tried to replace the ramdisk-recovery from several builds,but no luck. My last update was to 20141021 build a week ago. Main system is working fine...

Any ideas what to do?

Just be sure that you are replacing it in the right folder /system/bootstrap/2nd-boot/ (because there are three different folders called bootstrap ) and set the right permissions..

I think i used the right folder. I renamed the original file, inserted the new one and set file permissions to (-rw-rw-rw-). Please see the screenshots below (aahh sorry, i am not allowed to add pictures here).

Actual file is from 20141027-build. Because i do not have ramdisk-recovery from 20141003-build i started with 20141007-build. Will any file do or should i try from a certain build date?

P.S. Sorry for the strange quoting. I clicked on 'reply' but my own text from before was not shown so i inserted it manually...

 

[okij]

I think i used the right folder. I renamed the original file, inserted the new one and set file permissions to (-rw-rw-rw-). Please see the screenshots below (aahh sorry, i am not allowed to add pictures here).

Actual file is from 20141027-build. Because i do not have ramdisk-recovery from 20141003-build i started with 20141007-build. Will any file do or should i try from a certain build date?

P.S. Sorry for the strange quoting. I clicked on 'reply' but my own text from before was not shown so i inserted it manually...

IMHO @Vicsa's advice to replace ramdisk-recovery in /system/bootstrap/2nd-boot is wrong, because with the resized partitions it now must be /bootstrap/bootstrap/2nd-boot, because the system is booting now from there. If this doesn't work, you might also have to replace zImage-recovery with one of the latest nightlies. Which version doesn't matter, just be sure that it's after the 10-13 nightly!

Besides this, from what you wrote, I assume that you installed new_bootstrap.zip before 2014-10-13 and didn't update yet. If this is the case, it is likely that the buggy old new_bootstrap.zip has caused some partition corruption on your /bootstrap partition, leading to the not-working TWRP.

So it is strongly advisable that you also follow my post "For everyone who installed an early version of new_bootstrap.zip (before 2014-10-13)", otherwise you will run into problems with booting TWRP and/or system again sooner or later!

If you want to make a backup of your /data partition before touching your system, you can do this with Online Nandroid Backup ap. It can make TWRP compatible backups without having to reboot to recovery.

---

Hi! In the last rom of the day October 28 I see that the bug # 51 repeats frequently, so I tried using logcat to make a record, I do not know if something will serve. After check, the phone has been turned on by itself after two minutes. It is a MB525 connected to the internet via wifi and a non-active sim.

https://drive.google.com/file/d/0B00F9XnJ4G3eaVpEM0pSVkpoaGM/view?usp=sharing

It's great that you can now also participate in this forum.

Thanks for the log file for bug #51! I don't know if it's of any use, but I hope that @Quarx and @sevenrock will have a look at it.

 

[measel]

I have to say again: The Defy subforum still has the nicest most helpful users!

 

[Vicsa]

I think i used the right folder. I renamed the original file, inserted the new one and set file permissions to (-rw-rw-rw-). Please see the screenshots below (aahh sorry, i am not allowed to add pictures here).

Actual file is from 20141027-build. Because i do not have ramdisk-recovery from 20141003-build i started with 20141007-build. Will any file do or should i try from a certain build date?

P.S. Sorry for the strange quoting. I clicked on 'reply' but my own text from before was not shown so i inserted it manually...

Thanks @okij for correcting me about the right folder. This is ramdisk-recovery from 20141020 build I'm using at this time. Unzip it and put in the right folder (now you know for sure which one ). File permissions seem to be right, owner and group is 'root'.

 

[ilmcgee]

I'm using the motorola bravo, mb520, and trying to upgrade to new cm11 builds but can't get there. I was on cm7 build and tried upgrading to cm10.2 to get twrp to flash new bootstrap. After flashing bootstrap, when loading recovery I can't access the sdcard. I sbf'ed to stock and then rooted and then used adb shell to flash bootstrap img and still no access to sdcard. Without access to sdcard I'm stuck. Any help is appreciated.

Edit, just flashed sbf again, root and bootmenu, non quarx cm7, cm10.2, then update recovery file to try to get old cm11 builds again and after update recovery flashed, again no access to sdcard. Why won't it mount the sdcard, can I force mount it?

 

[YetAnotherForumUser]

I'm using the motorola bravo, mb520, and trying to upgrade to new cm11 builds but can't get there. I was on cm7 build and tried upgrading to cm10.2 to get twrp to flash new bootstrap. After flashing bootstrap, when loading recovery I can't access the sdcard. I sbf'ed to stock and then rooted and then used adb shell to flash bootstrap img and still no access to sdcard. Without access to sdcard I'm stuck. Any help is appreciated.

Edit, just flashed sbf again, root and bootmenu, non quarx cm7, cm10.2, then update recovery file to try to get old cm11 builds again and after update recovery flashed, again no access to sdcard. Why won't it mount the sdcard, can I force mount it?

Did you try to manually mount it? Start TWRP, open a shell through adb and try to mount the card. Do you get an error message, possibly about the filesystem or maybe even about the card itself? Check dmesg for errors as well.

The card can be found at /dev/block/mmcblk0p1 and /dev/block/vold/179:1 on Defy, I assume this to be the same on Bravo. To mount the card manually you can try one of the following:

 $ su
 # mount /sdcard

If that does no work, try:

 # mount /dev/block/mmcblk0p1 /mnt/media_rw/sdcard0

If this does not work, check dmesg for errors. Does it say anything about the filesystem being corrupted? If so, run fsck_msdos on it:

 # fsck_msdos /dev/block/mmcblk0p1

If this shows loads of errors, you might want to break off the check and restart it using '-y' (which means 'answer Yes on all questions').

If (or after) the card checks out OK, try the first command again (mount /sdcard) and check for errors. If any, report them.

 

[banjoe4711]

Besides this, from what you wrote, I assume that you installed new_bootstrap.zip before 2014-10-13 and didn't update yet. If this is the case, it is likely that the buggy old new_bootstrap.zip has caused some partition corruption on your /bootstrap partition, leading to the not-working TWRP.

So it is strongly advisable that you also follow my post "For everyone who installed an early version of new_bootstrap.zip (before 2014-10-13)", otherwise you will run into problems with booting TWRP and/or system again sooner or later!

If you want to make a backup of your /data partition before touching your system, you can do this with Online Nandroid Backup ap. It can make TWRP compatible backups without having to reboot to recovery.

Ok, i followed your advise and it worked perfectly fine in the end!

And yes, i installed the buggy version of new_bootstrap.zip on 2014-10-12. Then i read about the new version so i downloaded the new version on 2014-10-14 and installed it again via TWRP. But that did not gave me a correct system i assume...

Yesterday at first i extracted ramdisk-recovery, zimage-recovery and bootstrap_ext3.img and copied them onto the sd-card. Then i opened 'ES Explorer', went to /bootstrap//bootstrap/2nd-boot and renamed ramdisk-recovery (3.41MB) to ramdisk-recovery.org.

To my surprise a different ramdisk-recovery file showed up (585kB), i renamed that also. But that gave me a hint that the file system was corrupted as you said earlier.

After copying the new ramdisk-recovery into place and setting the permissions i tried to boot into TWRP recovery. It worked, hooray!

I rebooted into Android, started a Terminal session and cat the bootstrap_ext3.img into mmcblk1p1. No problem here. After rebooting again i booted into TWRP recovery and installed 2014-10-28-build. That runs without problem again, no data loss, everything is fine and running.

Do you think the system is in a stable state now?

Thank you very much for your help to all of you!

P.S I tried Nandroid Backup, it worked fine. But i saw backup option only. How do i perform a restore if necessary?

 

[Thobwa]

download links

Does anyone have a link to the 20-10-14 nightly or any other stable nightly not the latest ones?