[Motorola Droid 4] Septfox:
Nightlies for the 21st and 22nd were horribly slow compared to the unofficial release from 01/28 (which I'd been running up until now), at least for me. I'm talking slow as in "phone is softlocked for up to a couple minutes at a time" slow. I did dump a several-minute catlog earlier before updating, glancing through it seemed to suggest problems with memory management...I'll see if I can find and post it to be helpful for once.

Today's (24th) nightly reverts a bunch of changes to the lowmem killer, which seems to have fixed the issue. At least, I haven't managed to get it to choke again.

No serious glaring issues come to mind. Even little things like HDMI are reported to be working (with audio, even, after a recent commit to fix it). There are two things you need to watch out for: random slowness (which is partially addressed by the tweaked kernels that joojoobee is kind enough to build for us), and the Recents menu taking its sweet time coming up. Neither of these are really crippling, though.

By all means, spin up a new ROM slot and give it a try. It's pretty good stuff so far, and several devs are working on both it and omap4-common stuff daily to make it even better.

---

Hey, [MENTION=1070688]joojoobee666[/MENTION], have you thought to mess with the settings on the CPU governor? I didn't think to check before for some reason, but it is tweakable. I've played with it a bit, with some limited results, using guidance from here. Current settings:

---

Edit: in case anyone is wondering, the ROM is installable in the Stock "slot", and runs seemingly without issue. To accomplish the installation in a somewhat clean fashion (SBFing isn't currently an option), I

Backed up everything and made nandroids of Stock/SlimKat and Slot1/CM12, put them all on a spare spindle drive

wiped the Stock slot completely

restored a stock JB nandroid to it courtesy of sd_shadow; this was to ensure the stock kernel files were in place (probably unnecessary, it appears Safestrap's safeties were fixed since the last time I wiped stock around v3.5)

wiped Data

used Safestrap's file manager to manually delete the contents of /system/app and /system/priv-app (on the second attempt actually, the first attempt found CM12 trying to use JB apps because...*shrugs*)

flashed CM12, joojoobee's kernel, and Gapps

re-edit: this is probably not the best way to go about a clean install, it's just what I thought the best idea at the time was. A better/cleaner flash path would probably be SBF>JB>CM11 (or some other AOSP KK variant specifically noted as installable over JB, as they clean up before installing)>CM12.

Simply completely wiping Stock and jamming CM12 straight in might work as well, be prepared to SBF and start over if you try in case the wipe deletes anything vital.

Be warned that CM12+Gapps is a very tight fit in the stock system partition; I actually ended up with no space free. The Gapps flash still "completed" somehow, but I wouldn't be terribly surprised if one or more of the apps I don't use didn't get copied in properly and I simply haven't missed it. People installing to stock may want to use one of the smaller PA Gapps packages, and manually install additional stuff they need from the Store.

You also lose the ability to resize the Data partition to store more apps; ART precompiles take up a lot of space. This problem might be alleviated by using symlinks to internal MMC or the SD card (an easy way to accomplish this would be Link2SD or similar), but I haven't yet looked into it.