[Nook HD, HD+ Android Development] amaces:
Fixed by pointing to the right location providers (i.e., Play Services/GMS).

Won't FC at all on a clean install (permissions should be enabled automatically).

Odd, since that's a feature that's always been working reliably; hardware issue?

Yeah, my conclusion as well, although it didn't seem to happen anymore in r26/MDB08M.

The first set of kernel messages are fairly harmless, and also happen on Lollipop; just an indication of thermal throttling during the initial CPU-intensive ART re-compilation.

The logcat stuff is definitely not harmless, and had bugged me from the very beginning. I assigned it to ART or bionic weirdness, but it turns out it's just the overachieving toolchain I was using. Once I reverted to the official Android EABI prebuilts in AOSP, those crashes and the associated tombstones stop happening. Kernel is still compiled with a bleeding edge EABI.

None of these should happen though… Well, the SystemUI crash may, mainly because of the current memory management, and the toolchain bug mentioned above. SuperSU 2.52/BETA works, VPN ditto.

Yup, one of the first things I tested; CM12 must have broken it somehow since it never worked there (heads up, [MENTION=3809589]swaaye[/MENTION] and [MENTION=5875485]keshabbhattarai126[/MENTION]).

No need for this. GApps have been fixed since last weekend, and there should be no FCs on a clean install.

It works, but it's wonky. Initially, all is good, but it stops working after a sleep/resume cycle, and the screen gets stuck in the last orientation. After a week of looking into this, only mild success; rotation starts working again after some time, but have yet to figure it out completely.

Good man, this is insanity… how did you end up with this monstrous script? The Android build system does all the heavy lifting already, and you only need a couple of commands once everything is setup properly. I'd just follow the official Google/AOSP or CM build steps, and:

You only repo init once, but from the right repository. You've been using the CM12.1/Lollipop sources all this time, then adding ALL the Marshmallow sources into the local manifest, which doesn't work at all. The sync process must've aborted due to duplicate items, then you ended up with a crazy mishmash of LP/MM code, thus your aborted build.

You don't need a local manifest anymore if you init with my manifest as the main one. I mean you can use one, but everything needed for the Nook HDs is already included. I'd delete everything, switch to a completely clean directory, then do something like repo init -u git://github.com/airend/android.git -b marsh. Sync, then source build/envsetup.sh, and you're good to go.

Keep in mind that breakfast and brunch are CM commands. The standard AOSP way is lunch $PRODUCT-{eng,user,userdebug} (i.e., lunch aosp_ovation-userdebug). Finally, you build everything with make otapackage, possibly add -jX, depending on how much memory and how many cores/CPUs are available.

All the make commands/functions are already optimized for Android, and will output timing information, etc, so the script was probably written for a much older version of CM. Either way, a horribly inefficient build process, if you used this every time on CM12.