[Nook HD, HD+ Android Development] amaces:
Not sure about that anymore; the recent changes are digressing a lot from upstream CM, and it already takes a while for simple changes to be reviewed and approved. As of now, there are hundreds of commits that I merged, cherry-picked, or otherwise adapted in our four core device repos. Even rebasing only the zRAM/LZ4 changes on top of Hashcode's CM12 kernel amounts to a few dozens, and I don't think he wants to introduce this kind of instability before lots of testing happens, and I'm still hoping a 3.4 kernel might emerge by then. Basically, the only feasible way to push all the recent changes is to bypass review/Gerrit with official maintainer access rights, which I am not. Not ready to make that jump anyways ;)

Oh, boy ;) Now that you mentioned Lenovo KitKat, there could be many reasons for the app to crash. Does it support Lollipop (given the Dalvik -> ART transition)? Has anyone reported that it works on CM12.1? I'll try to zoom into that screen capture, but it would be much easier if you copy/paste the logcat messages happening during crash. ADB is the easiest option, and it's always a good idea to have it installed, otherwise run logcat in Terminal, directly on device, and copy from there.

Now that pretty much all the new stuff has been pushed to my GitHub repos, you should be able to pull everything with this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project path="device/bn/hummingbird" name="airend/android_device_bn_hummingbird" remote="github" revision="cm-12" />
<project path="device/bn/ovation" name="airend/android_device_bn_ovation" remote="github" revision="cm-12" />
<project path="device/bn/common" name="airend/android_device_bn_common" remote="github" revision="cm-12" />

<project path="kernel/bn/omap" name="airend/android_kernel_bn_omap" remote="github" revision="g-3.0" />

<project path="vendor/bn" name="TheMuppets/proprietary_vendor_bn" remote="github" revision="cm-12.1" />

<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery-twrp" name="airend/android_bootable_recovery" remote="github" revision="cm-12" />

</manifest>

Hopefully, everything is cleaned up and adapted properly, but you get the idea (will maintain this as devices.xml in the root of the shared Box folder). I'm still rebasing my local changes on top of CM upstream, although there haven't been any Nook-specific changes in there for a while.

Can you hear/record stuff with the built-in speakers/mic? What about an echo test (909-390-0003)? It's still broken for me, and got too frustrated trying to fix it a while ago. Also, I still don't understand why there is a camera stub on these devices; will have to look into this again once the bigger issues are fully fixed.

While hummingbird should be in much better shape with regards to the dreaded buffer underflows (on the account of lower bandwidth needed by significantly fewer pixels), we'll need a better kernel if we should ever fully fix them.

The first support for Wiimote also happened in K3.1, and last time I looked into that, it was hard to backport to the HID layer in 3.0; most things are hard to graft onto our ancient kernel. The Nook-as-USB keyboard patch also seems to require 3.1 at a minimum, but maybe the HID dependencies are lighter, and can be ported to K3.0. It's an interesting idea, so I'll keep it in mind.

Bottomline, jumping to any kernel beyond 3.0 is a huge amount of work, and I'd rather focus on 3.4, which I've been doing for a few months now, alas unsuccessfully. That is after smarter people already spent a couple of years trying to make it work on relatively similar platforms (otter, bowser, tuna, etc), so a lot of work that may amount to nothing.