[Motorola Droid RAZR] stargo:
Hi,

Let's get to the current status of CM-11:

11/07 is more or less (probably a bit less) stable than snapshot M12 which is deemed the final release of CM11. :)

An M-snapshot is not just a nightly built a week later, it is the codebase of about a week earlier with stability fixes added and questionable features removed (and tested during the week). So IMHO for anyone who wants a really stable phone, M12 should be the best bet.

Or if you are happy with 11/07, then stay on that build. :)

After the beginning of november, no real new features have been introduced into CM11, only some things which have caused breakage (like the SMS thing which is still causing com.android.phone crashes).

The OMAP4 device-tree is more or less identical to the one from M12 / 11/07 since I reverted a problematic commit on 11/25: https://github.com/CyanogenMod/android_device_motorola_omap4-common/commits/cm-11.0

The only difference to the previous state is a fix for GSM/UMTS devices which have problems with CellBroadcasts causing the modem to crash and needing a reboot to recover.

There are a few kernel-changes:

https://github.com/CyanogenMod/android_kernel_motorola_omap4-common/commits/cm-11.0

Most of these fix real kernel-bugs which were uncovered when building the kernel with the newer (Lollipop) compiler and caused havoc there. These fixes also improve stability on the older compiler which is used on KitKat builds (on KitKat the compiler-version for the omap4-kernel is forced to an old one exactly because of the problems now fixed).

The other patches just fix a few corner-cases of modem-bugs and enable kernel-side zram-functionality (which is not used since 11/25 anymore).

So from the Omap4-side everything should be as stable and fast as in the beginning of november.

The problem with slow wakeups is mostly caused by IO performance problems. Due to our special construct with image-files on a fat partition on the internal sd-card there is no way to tell the flash-controller which blocks are no longer used (TRIM) so flash-performance gets worse as time goes by. There is not much we can do about it, as trim on ext3 looped on fat is not implemented in linux. The only chance to "fix" this is by installing the ROM to the stock-slot where trim works (no intermediate image-files on other devices).

I'm actually running 12/23 and can't see any big problems (yet). The only known problem (to me) is the com.android.phone-crash on VZW in some special cases (like [MENTION=5362796]Dwillian[/MENTION]).

But to reiterate: If you want a stable phone, use the last and final CM11 release: M12

And I still stand by this. CM12.0 is in no shape to be a daily driver and I currently doubt that I can actually get it to work good enough on the Omap4s. This is mainly due to memory management problems in L (5.0) which will (hopefully) be addressed by Google in 5.1.

L isn't even usable on the (2012) Nexus 7 in the version distributed directly by Google. They tried to fix it, but it's still unbearably slow (or so I'm told). And the Nexus 7 has a much more powerful processor (Nvidia Tegra 3 quad core ) than our devices.

Cheers and merry christmas,

Michael