[Nook HD, HD+ Android Development] amaces:
You can't just rename mount points… Some of these are system generated, some are legacy symlinks; apps need to query the proper APIs rather than rely on legacy paths, which may or may not work in MM.

There you go; it sounds like a recent security change. Even if the underlying ext4 or F2FS would support it, Android's adopted/portable/multi user stuff probably interferes and supersedes normal permissions.

The system files are completely different and behave pretty much like on a normal ext4 partition (including the SELinux layer, that is).

Not needed, but a good thing to have. While even 2.8.7.3 has the proper support for CM block images (plus LZMA support), the latest TWRP is always built on the latest kernel, plus 2.8.7.5 improves ADB behavior and removes SuperSU checks. The world is moving to systemless SU, and until all that is sorted out, having that prompt can create more problems for people unaware of the changes.

You might get super fresh builds then, including the good progress in our repos this week.

What about reboot to recovery? If that's also broken, test the next builds (hopefully tomorrow), since I completely changed how our custom BCB is handled.

So, the approach is right, and as I mentioned to you, I was working on adding this Nexus-like artwork in vendor/bn, but it had to be AOSP and device-specific (i.e., 1080p vs 900p). That commit is done here and the latest AOSP builds should include the new animations.

It wouldn't be appropriate however to replace the artwork in public CM13 builds, since that animation is part of their branding. Of course, anyone can install whatever theme, but having Nexus/AOSP artwork as CM default feels awkward…

Just tested with a super basic BT mouse, and the cursor works as expected, so not sure what to say. I do know that some of our proprietary blobs (i.e., gralloc) were fixed specifically to support cursor layers in MM.

That sounds frustrating, to say the least…

That's probably not it since keyboard and mouse support is as good as on KitKat or earlier.

Now I'm just confused… Anyone using the AOSP builds without GApps, can you test the BT mouse cursor stuff?

That's not good. Has it ever worked on any Marshmallow build (AOSP or CM13)? If so, when exactly did it stop working? It's not simply about auto-connecting, but complete failure to do so with WPA2/Enterprise only, right? If the issue persists with the Sunday builds, I'll ask you for specific Wi-Fi logs.

You can pair, and use the Bluetooth connection with at least the A2DP profile, correct?

Sounds like you selected adopted rather than portable storage; did you mean to do that? Portable is the normal/legacy way to mount external storage, which preserves the content and filesystem on SD card (if supported). Adopted storage is a new Marshmallow feature, which attempts to merge external storage with internal, transparently. I'm not familiar with the minimum SD-class requirements; I just went ahead and enabled it.

So, all this boot animation stuff is great, but there's a whole thread dedicated to it. Since the discussion is ROM rather than device specific, I'm sure they have tons of information there.

Good, it's likely that you repo synced while I was pushing changes, or they were making changes to the forked repositories before I had time to push them. Everything has been working OK here, but maintaining the forked repositories (e.g., build, system/core, etc) can create temporary mismatches. I guess I could un-fork some of these; whoever needs the latest build, bionic optimization can probably overload them with a local manifest after all.

P.S. I had reverted their attempt to kill the busybox repo in the manifest; TWRP hasn't even started to migrate to toybox in earnest…

Wait, you mean that you compiled the kernel with a 5.2 EABI, or the whole ROM? I though that many ROM components fail with > 4.9, and given the deprecation of GCC/the switch to clang upstream, Android will probably never fully work with the newer toolchains.

Anyway, once you venture into fancy toolchains and whatnot, you're pretty much master of your own issues ;)

Umm… I didn't actually have a chance to test the latest AOSP builds, but took the lack of negative reports as a good sign after a hundred downloads. No reason they shouldn't work well since it's only android-6.0.1_r3->android-6.0.1_r10, and I'm using the same unified device trees as for CM13.