yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
Yup, that's the plan, to incorporate improvements that happened in device trees and kernel since mid-October (excluding Marshmallow-specific parts). Actually, I just finished kneading and rebasing my repositories so that the four device tree branches (two AOSP, two CM) are easier to maintain. Otherwise, the AOSP MM builds seem to be as stable as last CM12.1 builds, with CM12 being much better tested, of course. Memory use is the more apparent downside with MM, although we're closing the gap there as well.

Test CM12 builds will probably happen tonight or tomorrow morning, while the CM13, AOSP builds will not change much in the coming week.

If you mean builds before March or April, lots of things got improved since then. Although I never had CM10 on this device, compared to CM11, I always preferred the feel of CM12, even with our chronic memory shortage. It goes beyond saying that you should make a backup of your data partition, should you want to return to CM10. TWRP should work with any of these builds, I think.
[Nook HD, HD+ Android Development] TheDannemand:
[MENTION=4473900]amaces[/MENTION]: Thank you for that excellent update. Hmm, so maybe I should give AOSP MM a try already then. She (my wife who is using the Nook) may miss some of the tweaking of CM, but I saw you added a few things to it. Worth a shot.

Thanks again!
[Nook HD, HD+ Android Development] Monfro:
After another day of testing i can confirm that CM13 runs faster and with best memory management than MM AOSP (probably CM community succeeded to optimize MM).

CM10 is really a blast on Ovation, try it:

I think it could be great to have a CM10 build updated with your last kernel.

Soon we will have new CM12.1 build, or CM12.1 and AOSP Lollipop?

Look forward to test everything that you will compile.

Thanks for the great work!!
[Nook HD, HD+ Android Development] amaces:
Experimental CM12 Builds for Testing

Of course, things couldn't be easy and smooth after ignoring CM12 development for two months, and my initial calculation didn't work out so well… Parts of ART stopped building with my normal 4.9 toolchain, and I needed that for the optimizations I spent weeks testing and organizing back in September. After a couple of days figuring that out, another breakage due to trying to incorporate too many of the changes for Marshmallow. Also, It's funny that all these were sorted out on the 18th, exactly two months after the last stable builds; not exactly my intent, but I appreciate the symmetry.

Anyway, things seem OK now on ovation, although these builds feel somewhat weird to me, possibly due to spending so much time with MM. I'm deeming them experimental until people confirm that they're not major regressions compared to October. After the toolchain, I guess the kernel is the major difference, since I'm reusing the one updated for MM, which includes a different (better?) zRAM driver.

P.S. I'm using the AOSP naming scheme now, but no difference in the way you install them. Also, they're Permissive userdebug builds again, and as we discussed ad nauseam, CM root is baked in.

CM13 builds were generated last weekend, and people say they're usable, so that's an option as well.

Well, there are still good people working on CM10, and that kernel is Jon Lee's baby ;) Generating a CM10 kernel image would basically require redoing the device trees for Jelly Bean, which is lots of work with limited benefits.

The CM12 images were finally updated, and am debating cleaning up the AOSP 5 manifest and device trees as well. Mainly, I'd like to redo the recovery images on an AOSP base.
[Nook HD, HD+ Android Development] Forsquall:
cm_ovation-ota-LMY48Y.151218 is working well for me. No obvious regressions vs. 20151018.

Thanks for your work.
[Nook HD, HD+ Android Development] acr123:
I have CM 12.1 unofficial ovation from 10/18/15. What are the differences in the 3 choices ( cm ovation lmy48y or MMB29M OR the oasp MMB29M choices) listed under experimental and would one of them be a more likely choice for me to upgrade my Nook HD+ to.

Lastly, I assume since similar version would not need to do complete wipe.

Thanks,

Al
[Nook HD, HD+ Android Development] Monfro:
I confirm: no bugs or regressions on Ovation.

Maybe it is placebo but seems a little bit smoother than previous 18/10 build.

- lmy48y: new CM12.1 build

- MMB29M: CM13 marshmallow

- Aosp: aosp marshmallow

If you will flash the new CM12.1 build you will need to wipe only dalvik and cache.

If you choose marshmallow you need a clear installation.
[Nook HD, HD+ Android Development] ajislav:
+1 for the smoothness and no bugs, but I am not a heavy user
[Nook HD, HD+ Android Development] mojoe_24:
So I'm trying to update my mom's Nook HD+. Its currently running 4.3. What would I need to get it updated? Any recommendation on CM12.1 vs CM13?
[Nook HD, HD+ Android Development] digixmax:
If your HD+ is running 4.3 and (presumably) has CWM recovery, you should be able to use your current CWM recovery to flash the TWRP v2.8.7.4 recovery, then re-boot into the newly installed TWRP to wipe /data then flash CM12.1, GApps, and SuperSU. You might want to backup your current ROM (using the current CWM recovery) in case you'd like to revert back from the new ROM.
[Nook HD, HD+ Android Development] mojoe_24:
What is the correct GApps? For my phone I just use Open GApps. I imagine I'd go Arm 5.1 and then whatever package I want. Any recommendation on CM12.1 or CM13? She primarily uses it for Candy Crush, Facebook, and web browsing.
[Nook HD, HD+ Android Development] digixmax:
It's ARM-5.1-xxx for CM12.1 , ARM-6.0-xxx for CM13.
[Nook HD, HD+ Android Development] mojoe_24:
Thanks. Installed the CM12.1 from this link. https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918 Booting it up right now. Had to get the nano package because I got an error with the stock package, but I remember reading that before. I could have sworn I saw a solution to it, but coudln't find it in my brief search. Don't think it will be that big of a deal. As long as she can play Cnady Crush and use Facebook she'll be fine. I primarily use it for comics.
[Nook HD, HD+ Android Development] s0c4:
Updated my Nook HD (hummingbird) from CM12.1 20151018 to 20151218. Done without any problem (boot into recovery, backup, install ZIP, wipe cache&dalvik, reboot) in less than an hour, including download and checking. Nook got hot and display started flickering, but I already know this and everything is okay after a short time.

Very responsive and even smoother scrolling now, in particular very noticeable with Chrome and news sites, which are full of stuff and pictures.

Built-in root is here again and USB-host function now works again. Great!

Thanks a lot, amaces, for picking up CM12.1 again and providing such a usable system.
[Nook HD, HD+ Android Development] digixmax:
I am taking a swat at compiling CM12.1 and hit a snag:

My repo sync:

repo init -u git://github.com/airend/android.git -b cm12
repo sync

runs into an error near the end:

...
Fetching project CyanogenMod/android_external_mksh
Fetching projects: 99% (483/487) fatal: Couldn't find remote ref refs/tags/android-5.1.1_r30
Unexpected end of command stream
error: Cannot fetch platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9

TIA for any help/pointer.
[Nook HD, HD+ Android Development] amaces:
Browsing with Chrome already qualifies as heavy use on these devices ;)

No worries, according to the official wiki, the nano package has support for pretty much all Google features once you install the appropriate apps in /data. With our partitioning scheme, the stock package won't fit even on barebones AOSP, but you can reduce it to a nano installer with a custom config file.

You mean -b cm-12, right? Anyway, I needed to add revision information for Android EABI 4.9 (Lollipop/CM12 was meant to work with 4.8). Anyway, try re-syncing now.
[Nook HD, HD+ Android Development] digixmax:
Got it, thanks.
[Nook HD, HD+ Android Development] digixmax:
I hit a new snag in my stab at compiling CM12.1 -- attached is the output error messages.

TIA for any help/pointer.
[Nook HD, HD+ Android Development] amaces:
Great Marshmallow Migration

After testing the current builds (on a clean slate), I feel comfortable green-lighting Marshmallow as daily driver; all ROMs in the respective device folders are, in my assessment, as stable and usable as latest CM 12.1 builds (and in some regards, better).

Just to be clear, AOSP 6.0/CM 13.0 is not suddenly perfect or frustration-free on these devices, but not less so than Lollipop. This gap was closed only recently, and since I like my device again, I figured that other people might have a similar experience.

P.S. It goes without saying that you should make at least a /data backup before wiping everything for Marshmallow. Also, new CM 12.1 builds, and possibly even AOSP 5.1.1, might happen occasionally (especially if people's mileage with MM is not good).

Got very confused about the missing arm-eabi-gcc, then realized that separating build options based on toolchain version also affects the kernel EABI. Fixed now, so do a quick repo sync build, then re-select the target (e.g., lunch/breakfast/brunch, whatever command you used before starting the build).
[Nook HD, HD+ Android Development] asakurato:
So, just flashed latest cm13 with latest opengapps. Everything flashed good and no fc and crashes on setup. Xposed and supersu both works fine. Performance is also good. Youtube works, but no 60fps video.
[Nook HD, HD+ Android Development] digixmax:
Thanks, [MENTION=4473900]amaces[/MENTION].

The arm-eabi-gcc issue went away, but I still ran into the same genksyms error.
[Nook HD, HD+ Android Development] amaces:
Odd, can you make clean then restart the build process from the top (i.e., source build/envsetup.sh, lunch, etc). Clobbering the previous target binaries is probably a good idea since GCC 4.8 was used before I pushed that change to build. Basically, the version of the two toolchains (kernel and ROM) is linked, and the 4.9 EABI is definitely needed for kernel due to the optimizations I made in that Makefile. One could create an arm-eabi-4.8->arm-eabi-4.9 symlink (and revert the last build system change), but I'd like the manifest to work on its own.

Now, there are additional extensive optimizations for the ROM binaries in the +optim branches, and those definitely require a very robust Android EABI 4.9 to avoid ICEs. Those optimizations are separate from kernel stuff, and are not turned on by default in the lolli/cm-12 branches, but one can easily find and use them if willing to mess with local manifests, third-party toolchains, etc. For now, let me know if you still run into issues with Google's cross-compilers.
[Nook HD, HD+ Android Development] snoozer854:
May I ask which opengapps did you use?

Thank you
[Nook HD, HD+ Android Development] digixmax:
I did "make clobber" then recompiled (source build/envsetup.sh, croot, brunch cm_ovation-userdebug), still no-go with the seemingly same fatal error.
[Nook HD, HD+ Android Development] TBueno:
Try the nano package (for arm processors), the micro one won't fit in /system. I flashed it while keeping all /data from 12.1 and everything is working as it should.
[Nook HD, HD+ Android Development] amaces:
What platform/distribution are you using, and what does gcc -v say? Can you do breakfast ovation; make -j1 bootimage, then attach the output where the errors happen? It seems that the host toolchain is missing support for some of the kernel optimization flags, which usually doesn't happen, unless you have a very conservative GCC 4.8 (Ubuntu LTS?).
[Nook HD, HD+ Android Development] digixmax:
Thanks for the pointer.

I noticed a bit earlier that gcc and g++ were still symbolically linked to their respective v4.8 versions, even though I had v4.9 installed, so I updated their symbolic links and re-initiated the compilation which is still running right now.

FWIW, I am using Linux Mint 17.2 on an old Dell Inspiron laptop.
[Nook HD, HD+ Android Development] digixmax:
The compilation got further along, onto a new issue -- Invalid sepolicy vers specified
[Nook HD, HD+ Android Development] snoozer854:
Thank you
[Nook HD, HD+ Android Development] asakurato:
I always use pico gapps
[Nook HD, HD+ Android Development] amaces:
You cleaned everything after switching the host compiler, right? Pretty odd since I built CM12 on this exact kernel last week, and it looks like Linux Mint is similar to Ubuntu. Let's try something else; I removed the SELinux changes meant to support MM from the lp-12 branch. Update the kernel sources (repo sync kernel/bn/omap), and try rebuilding the boot image again.

SELinux was updated to policy version 30 for Marshmallow, and it looks like the Lollipop/CM12 checkpolicy is confused by that. I also have the Ubuntu checkpolicy installed, which may appear earlier in the path, so maybe that's why my last CM12 builds were OK. Anyway, it was nice having those SELinux additions on Lollipop, but not really essential.
[Nook HD, HD+ Android Development] acr123:
Updated from 12.1 ( 10/18 to 12/18) and wiped Dalvik and Cache. Got frequent reboots, play services, various programs and Go Launcher Z, etc would frequently shut down.

I tried rebooting several times and rewipe, but it was not really usable. Went back to 12.1 from 10/18 and all is well. Just thought this might be useful information.

Al
[Nook HD, HD+ Android Development] digixmax:
Got to nearly the "finish line" -- all requisite *.img files successfully built -- but then bailed out while creating the flashable zip due to "no module named backports" error, so I downloaded/installed the backports.lzma package and re-running again.
[Nook HD, HD+ Android Development] amaces:
Well, not really… If you're the one report of this kind, you should provide logs, or at least some reasonably specific information. Did you try a clean install (after backing up data)? That will at least tell you whether it's a configuration problem or something else.

Based on your edit, you found the missing piece of the puzzle: the LZMA module from https://github.com/peterjc/backports.lzma. Pretty obscure requirement, I know, but you can disable this enhanced compression in your local builds by commenting out WITH_LZMA_OTA := true in device/bn/common/BoardConfigCommon.mk. Net bandwidth is probably not a concern now ;)

Just curious, was it the SELinux stuff or something else that finally fixed building the kernel?
[Nook HD, HD+ Android Development] digixmax:
Thanks, [MENTION=4473900]amaces[/MENTION], for all your help.

Finally ran to successful completion!!! I think it was your removal of the SELinux change that took care of the previous abort.

FWIW, it took 12.5 hours on my ancient Dell laptop with a Pentium T3200 2GHz CPU and 3GB RAM.
[Nook HD, HD+ Android Development] parmar.saab:
I have an HD+ currently running CM11. Could someone link me to the installation instructions for this build?
[Nook HD, HD+ Android Development] digixmax:
See the guide posted at http://xdaforums.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119 for info/pointers.

Since your HD+ is already running CM11, you should be able to shorten the process by using your current recovery to flash the new TWRP recovery (and backup your current CM11 ROM just in case you'd ever want to revert back), then reboot into the new TWRP recovery to flash the new CM12.1, GApps, and SuperSU.
[Nook HD, HD+ Android Development] parmar.saab:
When I try to install the CM 12 zip (https://notredame.app.box.com/shared/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/47826056961/1), it doesn't install. I did format cache, dalvik, data, system, and internal SD to wipe it clean. Maybe that caused the issue? What can I do to fix it?
[Nook HD, HD+ Android Development] amaces:
What about the part where you need to install an updated TWRP, also in that folder? CWM or the official TWRP won't do since CM12 switched to block-based OTAs a few months ago, plus these are LZMA-compressed.
[Nook HD, HD+ Android Development] parmar.saab:
This is the recovery I installed https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/47675558797/1
[Nook HD, HD+ Android Development] amaces:
That's the one… In that case, I'm stumped. It does show that version number (top left), right? What happens when you try to flash a current CM11 nightly?
[Nook HD, HD+ Android Development] parmar.saab:
Just installed https://download.cyanogenmod.org/get/jenkins/139079/cm-11-20151213-NIGHTLY-ovation.zip It installed and booted up just fine...
[Nook HD, HD+ Android Development] amaces:
Then, I don't see any reason why flashing CM12 on top of it would fail… You'd have to send a full recovery log (extract with ADB). Otherwise, you could try the version tagged as 2.8.7.4 as well.
[Nook HD, HD+ Android Development] parmar.saab:
How exactly do I boot into TWRP? It seems the only recovery I can boot into is the CWM on the bootable sd...
[Nook HD, HD+ Android Development] digixmax:
Assumming you had flashed TWRP onto EMMC, just remove the SDcard and reboot, the Nook should boot into TWRP.
[Nook HD, HD+ Android Development] parmar.saab:
That's the problem. When I remove the SD and reboot, it doesn't go into recovery - it boots right up. I even tried using Quickboot for this purpose, but that didn't work either.
[Nook HD, HD+ Android Development] digixmax:
The procedure to boot into the new TWRP is described in section 5a on page 13 of the guide at http://xdaforums.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119:

• Press and hold the Nook Home button.

• Press and hold the Power button.

• Keep both buttons pressed until a second or two after the CyanoBoot universal boot-loader comes up, then release both buttons.
[Nook HD, HD+ Android Development] Ferd Burfle:
I second that. I use Amaces' CM12 build on my HD and HD+, playing all sorts of games and performing countless network tasks without issue.
[Nook HD, HD+ Android Development] tj2003:
Deleted
[Nook HD, HD+ Android Development] starbright_:
Is there a mirror for CM12.1 builds? I couldn't manage to download...
[Nook HD, HD+ Android Development] toplist:
I have been using amaces build from the beginning. The builds are pretty solid for everyday usage. I have experienced a problem with bluetooth connection. My nook hd plus doesn't recognize xiaomi mi band. It doesn't even show up on the bluetooth device list. Has anyone experienced any issue with bluetooth device connection?
[Nook HD, HD+ Android Development] twiztid_:
I just tried to connect my Nook HD+ running 2015/04/22 build to my Phone (Infuse 4G running CarbonRom 4.4.4 2014/11/02) using F-Droid's bluetooth apk/file share and I had no problems. Both devices were in search mode since it didn't pick up my phone right away, but I may not have given it enough time after turning on bluetooth.
[Nook HD, HD+ Android Development] amaces:
Yup, your logcat looks very similar to mine. All things seem to point to an encoder problem, whether due to limitations in the Ducati binary, or due to CM12 misconfiguring the OMX parameters. What cought my attention is the do not know color format 0x7f000789 = 2130708361 message, and I didn't find much information on that…

The "SPS/PPS before IDR" commits are already merged, and based on the log (going to manually prepend SPS and PPS to IDR frames), the encoder seems to recover gracefully at that point.

You mean Trebuchet's AndroidManifest.xml? I use a different launcher, but that permission is included in CM12.

No idea, but that tool seems designed for Nexus 4, which is a completely different platform (Qualcomm Snapdragon). Looking inside, it does extensive modifications to system files, so you'll probably break stuff, but hey, try it out if you have a good backup.

You're probably right, based on the number of people claiming that AOSP 5.1.1 does screen casting just fine on the same device. I would love to be able to test that, but none of my AOSP (or OmniROM) builds go past the boot animation stage, and way too many errors in the logs…

Not sure, but I think AcDisplay's is supposed to work. I haven't ventured beyond the standard one.

Not so much problems with CM12.1, but rather with this old platform on Lollipop… Read the first three posts, plus the original CM12.0 thread linked (specifically, the bug reports in there). Power consumption seems acceptable, although a bit higher than on CM11, totally understandable given zRAM (plus KSM in my case), AOT compilation at every update, etc. About becoming an official highly, that will take a while, if it ever happens… Not only that a good developer has to actively supports these two device ports, but the longstanding buffer-underflow bugs need to squashed, which probably means when K3.4 is usable.
[Nook HD, HD+ Android Development] starbright_:
I did this step and installed the 0502. Looks fine at first glance. Thanks to the devs!

But It miss the superuser functionality. At least TB complains about this. Or do I something wrong?
[Nook HD, HD+ Android Development] mhunt13:
Read posts #64 & #66 -- root access is built into CM 12.1, you just have to enable it in "Developer options",

after you enable " Developer options"!

I don't even use SuperSu, not required. " Privacy" option will let you manage root access by app, and prompts still appear.

Good luck!
[Nook HD, HD+ Android Development] enochpc:
I don't know if it's something to do with certain ovation devices, or some overlooked detail, but I know on my device I never could get root to work, no matter what setting I used under developer options or what version of root I flashed. I also had a lot of delay/lag on change from app to app and screen to screen in apps. Few people seem to have similar issues, at least that post here, so I have been assuming it's something with my device. Strangely it works great on CM11, with both root and little to no lag.
[Nook HD, HD+ Android Development] amaces:
Kernel Update and Quick Survey

So, how about those dreaded screen flickers ;) I think I stumbled upon something good, an old kernel commit that helps a lot with the overlay/underflow issue. It's in my g-3.0 branch, but I also submitted it to the official kernel repo here: http://review.cyanogenmod.org/#/c/97578. Anyway, test out the ovation build from today. In my case, stacked picture overlays (e.g., Sync for reddit) don't cause flickers/reboots anymore, and Google Keyboard is usable pretty much everywhere, with the notable exception of Chrome. Still, even with the occasional glitch, it reboots promptly rather than the prolonged flickers of death…

On a related note, I'm still debating whether to use this 101 kernel as default for all future builds, or to stick with the current CM12.1 repo. Any regressions, or subjective feelings with the builds from a few days back?
[Nook HD, HD+ Android Development] techdudepro:
I have been using the hummingbird 0502 (experimental) build with the 3.101 kernal, and so far it works great! And thanks for fixing the hardware overlays issue... it worked for me :) Now I can do stuff without the top and bottom of my screen flickering!