[Nook HD, HD+ Android Development] amaces:
This is shaping up as a pretty good week for K3.0 on the HDs :) I pursued two different ideas for bettering the video subsystem, plus Hashcode dumped a bunch of interesting commits for Amazon device support (same OMAP44xx family). I added some of this information in the pseudo-log that is post #2, but the really exciting stuff is the DMA-buffered K3.0 in this branch.

P.S. The couple of people who grabbed the 06/04 right away, that was just a regular build, and the truly experimental build is in that folder now, tagged a bit differently. Beware that HW accelerated video is the one thing not working yet in that DMA ION build.

Thanks, [MENTION=4190710]drmarble[/MENTION]. I had thought about this in the past as a quick-and-dirty way of significantly reducing HWC bandwidth, but never implemented it, so I tried your idea. Since we potentially have five display variants, I made the change directly in omapdss_default_get_recommended_bpp(). After trying both 18 and 16, I gave up; CM12 really doesn't like it, and I'd have all sorts of visual artifacts. I had to disable the wallpaper completely to stop it from flickering (different type of glitches from the underflow bug), and I could tell things needed dithering to even look acceptable. Since CM probably makes a lot of assumptions about minimum color depth nowadays (even the cheapest screens are supposed to be 18-bit capable), I'm stashing this idea for now.

Believe me, we're integrating every little tweak that promises better performance really fast ;) The CPU scheduler won't make much difference at this point, and you have to be aware of the limitations of these consumption devices, which were never meant to run Project Butter, or anything beyond ICS. If you want to understand some of these limitations, and the future potential, I'd start reading through Hashcode's previous CM12.0 thread (referenced in this OP), then continue onto what people reported here.

That's not how it works ;) Once the kernel/userland is able to mount /data, /cache, etc, the underlying filesystem, be it ext4 or F2FS, is irrelevant to normal apps. Anyway, do you have an ad blocker installed (e.g., AdAway)? Because of the memory constraints with these devices, applications reload frequently (especially if not in foreground), and when that happens, a host-based blocker plus the latencies introduced by zRAM would occasionally trigger those errors. What happens when you reload the webpage?

So, all good now? Tombstones like what you sent happen even on a "healthy" system. Well, more or less… It's odd that wiping should fix it, but I've had weirder things happen on Android ;) We expect computers to behave completely deterministically, but these very compact, condensed devices, with lots of proprietary components, do have a will of their own…

Normally, I don't comment on GApps, but I've had a bad experience with TKruzze's legacy/pre-5.1.1 PA stuff (and its unmaintained clones). That package eventually worked, but I later discovered my Nook as a duplicate device in Play settings, which hasn't happened before, and is definitely not good… Whichever component is broken (device fingerprinting?), there are better GApps packages out there; may I recommend BaNkS' here?