yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] pastordl:
[MENTION=4473900]amaces[/MENTION] Installed newest rom using TWRP 2.8.7.3 installed fine. Did notice the .zip is about 38 meg smaller. Reboot to recovery works fine. Poweroff works with variations. CM reboots, ROM Toolbox turns off, SManager if plugged in goes into deep sleep and continues to charge (lights on and turns to green), if unplugged turns off. When using the SManager plugged in must hold power button 10 seconds to turn fully off the start normally. [MENTION=4473900]amaces[/MENTION]

New kernel just shuts off with SManager plugged or not.
[Nook HD, HD+ Android Development] Zippy Dufus:
Yes, I followed that guide originally.

However, with [MENTION=4473900]amaces[/MENTION] changes, I wondering if lzma-devel.x86_64 has to be installed on my Fedora 22 build virtual machine.
[Nook HD, HD+ Android Development] amaces:
That was the point ;) Once I got all worked up about the CM OTA changes that broke TWRP, I decided to add the XZ/LZMA compression for block images. A roughly 20% size reduction is not too shabby, but it now takes much longer to decompress things.

See ieatabiscuit's report below. I don't think they're moving away, or breaking things on purpose, at least I hope so. I'm assuming that they want a recovery that's guaranteed to work with their builds, incremental OTAs, etc, and obviously, under their control. Until their recovery reaches TWRP-like quality, or the latter stops working, falls apart, I'm not even looking at the CM recovery.

Yes, I had read about ovation being overclocked even higher (1.7 GHz?), but wasn't planning to go there anytime soon. Overclocking hummingbird is a lot more reasonable, so I will put it on my list. I may be wrong, but I would say normal tasks, like web rendering, etc, are limited by memory and associated buses/bandwidth at this point, although you may see an indirect gain from faster zRAM compression/decompression. I'll let you know when it's ready for testing.

About SELinux, I forgot to re-enable it after moving parts of the code, and builds were already underway when I noticed. No biggie, the plumbing is still there, and you can flash the additional kernels in experimental to switch it on. About power off, reboot to recovery issues, those will probably still happen sporadically. To my knowledge, the same APIs/system calls are used, regardless of the source of the commands, so I'm still puzzled why it would make a difference. As before, I'm pretending it's not specifically the software, but something esoteric about the hardware. Does Chrome Dev also stop?

You're probably missing the backports.lzma Python module from here (see http://review.cyanogenmod.org/#/c/100826).
[Nook HD, HD+ Android Development] dbrickg:
I believe this is an upstream problem. The CM 8/26 nightly for my Nexus 6 broke Chrome, too.

The http://www.cmxlog.com/12.1/shamu/ changelog says 'Fix "Select correct 12 or 24 time format" breaking Chrome'

There's a commit in the 8/27 that fixes it:

http://review.cyanogenmod.org/#/c/107747/

sad that fixing the time format would be enough to completely break the browser

---------- Post added at 01:04 PM ---------- Previous post was at 12:59 PM ----------

Thanks for the alternate kernel test. I think I'll leave it alone, too. I really like being able to boot into recovery without having to do the multi-button thing. I always forget, and then it's doing a regular reboot, so then I wait and retry with the button trick, only I almost invariably hold the buttons down too long, so it just turns off again... etc. I wonder if it's just because twrp doesn't have adequate admin rights. I know some of my tablets, everytime I flash a new nightly, ask, when I'm rebooting the system, if I want to fix "su" (which, I think, is broken because of SELinux...?)
[Nook HD, HD+ Android Development] dbrickg:
amaces: just wanted to say explicitly, Thank you so very much for all the time you've spent replying to posts in this thread. I wish other devs were as considerate.
[Nook HD, HD+ Android Development] ieatabiscuit:
Ok, idiot time. I'm used to flashing the images for the TWRP updates, and to get any of the new goodness available I have to flash a zip. XDA's search function is down, and I can either ask, or search through the whole thread for the answer. Someone please save me from having to go over so many thread pages with no search functionality, and tell me how to flash the TWRP zips.
[Nook HD, HD+ Android Development] belfastraven:
If you are running a TWRP recovery now, just get to the recovery, and using the install feature, flash the Zip...

hope this helps
[Nook HD, HD+ Android Development] ieatabiscuit:
I must not be holding my mouth right then. That's the first thing I tried. I'll check over and make sure everything is DLed right, and try it again then. Thanks [MENTION=5672278]belfastraven[/MENTION].

Update: As I suspected, I had a crap download. Now let's try this once more... WITH FEELING!
[Nook HD, HD+ Android Development] ieatabiscuit:
Ok, latest TWRP flashed, and latest ROM flashed. Runs smooth as usual, and I did successfully reboot to recovery! Got it all themed up with Nova Launcher at the wheel, and nary a flaw in sight. Installation went smoothly, and my hickup earlier was indeed due to a bad DL, and not realizing it due to a monster headache. All is well now, and for the record Open Gapps has been great on my ovation.
[Nook HD, HD+ Android Development] belfastraven:
Are you running SELinux enforcing or permissive ?
[Nook HD, HD+ Android Development] ieatabiscuit:
Permissive at the moment, so I can easily install V4A (it won't install if SELinux is enforced, but can be put to enforcing after installed). I'll tinker with the enforcing kernel tomorrow, and update how it performs.

Also, before I forget: [MENTION=4473900]amaces[/MENTION], your 8/19 ROM on my daughter's hummingbird was put to a test as she used it at school today. She mentioned to me that her hummingbird was smoother than the schools own iPads, and that hers was also a bit better at doing what she needed than other people that had stock devices. Well played sir, well played.
[Nook HD, HD+ Android Development] js290:
I switched to it on my HTC Droid DNA dlx when I was running the 12.1 nightlies. It's the only recovery that the update script ran reliably on. Other devices that have been super reliable updating with TWRP includes tate, evita, and d2att. But, now I'm running the cm12 snapshot for dlx, so I reinstalled TWRP.

Some of the custom CM recovery builds may support F2FS, such as the one for acclaim. But, the others seem to stick with basic ext[34].
[Nook HD, HD+ Android Development] leswgnr:
0826 rom

Just installed the ovation 0826 ROM with the experimental 0827 enforcing kernel, using the 2.8.7.3 TWRP. Everything seems to be working not just well, but very well-audio, video, Bluetooth, and every app I've tested. Device is not getting hot upon continuous use. Haven't tested booting into recovery yet, but that and battery life just aren't that important for the way I use the tablet. ( Update... Boot into recovery still doesn't work for me. )

Thanks amaces, super job!
[Nook HD, HD+ Android Development] Zippy Dufus:
Working build!!

I was able to build and install 08/28.

Thanks for your hard work!
[Nook HD, HD+ Android Development] ieatabiscuit:
Flashed the enforcing kernel. Reboot to recovery worked reliably with permissive, does not work at all with enforcing. I would compare the two, and see if there's something in there to answer for it. Other than that minor thing, all is well.
[Nook HD, HD+ Android Development] dbrickg:
Does Chrome work on 8/28?
[Nook HD, HD+ Android Development] leswgnr:
Not for me. That and boot to recovery are the only 2 things I've found problematical so far with 8/28 with the enforcing kernal also installed.

Update...Oops - sorry, I was using 8\26!
[Nook HD, HD+ Android Development] Zippy Dufus:
Yes - Chrome (Beta).

I have always used Chrome (Beta) without a problem but I only use it for looking at a limited number of online news sites and other light surfing.
[Nook HD, HD+ Android Development] dbrickg:
Excellent. Thanks for the reply. That's what I suspected. I think it must have just been the cyanogenmod "fix" of the 12/24 hour clock that broke Chrome in the 8/26 builds. It seems to have broken them, both Chrome and Chrome Beta, on all platforms, not just Nook. The "fix" was reverted the next day, so 8/27 and onward have no problem.
[Nook HD, HD+ Android Development] amaces:
Yup, you were spot on; looks like I had synced repos right after the bug was introduced, and it broke all flavors of Chrome. The builds this afternoon should be good.

OK, I'll focus on SELinux as potential culprit. It just doesn't make sense based on my current understanding… I mean SELinux denials are as black and white as can be, so they should affect all of us, all the time. Power off/reboot to recovery have been OK on many devices (including my ovation), so I rejected this explanation so far, but maybe it's some sort of insidious race condition that happens with specific configurations. Either way, since Enforcing kernels are available, I'll keep Permissive as default while we investigate this, which means you should send me dmesg output (post mortem). I think something like /proc/last_kmsg after a bad reboot might work (since we're looking for denials happening just after issuing the commands).

That's TWRP's convenience check for the SuperSU binary, and unrelated to SELinux. If you flash the SuperSU zip to replace CM's root solution, that warning will go away. It's actually a life saver on devices with very little empty space in /system (e.g., Nexus 5) as it allows installing the main SuperSU APK in userdata.

It's my only thread :) I'll ignore answered stuff, but new weird issues are different, and it feels like we're having a renaissance of those… Also, I hate writing, so this is good practice for me.

P.S. The raw images are still inside the respective ZIPs for users inclined to use them. I'm wrapping them inside ZIPs with device asserts now, after folks got soft-bricked by flashing ovation over hummingbird and whatnot :(

Aww, this is great. I'm certain our OMAP platform is still quite capable, but it's held back by the archaic support from TI and BN, plus inefficiencies in Android. Marshmallow should squeeze a bit more performance out of these devices, and it doesn't look like porting from L will be very difficult.

Something that I had forgotten to include in the custom repo list: the android_hardware_ti_omap4 fork, which has a few good changes. That device.xml is updated, and anything important that I fork will be on GitHub.
[Nook HD, HD+ Android Development] belfastraven:
From event log,

08-29 19:29:37.835 I/auditd ( 142): type=1400 audit(0.0:3): avc: denied { read } for comm="setup_fs" name="mmcblk0p9" dev=tmpfs ino=4181 scontext=u:r:setup_fs:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file

08-29 19:29:37.835 I/auditd ( 142): type=1400 audit(0.0:4): avc: denied { open } for comm="setup_fs" name="mmcblk0p9" dev=tmpfs ino=4181 scontext=u:r:setup_fs:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file

kmsg and locat have pretty much exact same message. I have attached zip with logs, taken shortly after installation of new rom and reboot to recovery.

Sorry for terseness here,-- not a good left-handed typist :)

Thanks again.
[Nook HD, HD+ Android Development] robak1965:
Just another data point [MENTION=4473900]amaces[/MENTION] . I have never had an issue exiting or booting to recovery in any of the builds, and I have both HD and HD+ models.

I suggest users report thier eMMC version when reporting an issue.

My HD has eMMC chip MAG4FB

My HD+ has eMMC chip MBG4GA
[Nook HD, HD+ Android Development] neutronjeff:
I extracted and flashed the twrp 2.8.7.3 image ( Flashify) onto my ovation and now I can't seem to get into Recovery. Power menu or Flashify command. Any suggestions?

Nevermind, I got it with the hardware keys method.
[Nook HD, HD+ Android Development] leswgnr:
8/28 ROM

Just want to confirm that Chrome non-beta also works fine with the 8/29 Ovation ROM as does boot to recovery without the seLinux enforcing kernel.
[Nook HD, HD+ Android Development] euqilobaid:
Can someone please verify upgrade procedure, just to avoid possible problems i'm usually lucky to stumble upon :)

I'm currently using latest CM nightly on the Nook HD+ (cm-11-20150824-NIGHTLY-ovation) with dated CM Gapps (CM11 20140606) and their also dated CWM v6.0.4.6.

To upgrade the ROM i should (please confirm the following):

1. Update recovery by flashing twrp-2.8.7.3-ovation.zip from CWM.

2. Reboot back into recovery (now TWRP instead of CWM) and flash cm-12.1-20150829-UNOFFICIAL-ovation.zip + kernel-ovation-enforcing.zip + GAPPS

3. reboot and enjoy the ROM :)

Do i have to install the kernel-ovation-enforcing.zip?

Which GAPPS work with the ROM? Do i have to use CM GAPPS or do ie. Open GAPPS (arm 5.1 stock 30 August 2015) work as well?
[Nook HD, HD+ Android Development] Nevermindthelabel:
Pretty much. Think I used flashify to install TWRP, and you only need to flash the kernel if you need enforcing i believe. Love the open gapps, works great on my hummingbird. Might want to factory reset before flashing the new rom just to be safe
[Nook HD, HD+ Android Development] Minshter:
I noticed your version of twrp, in the reboot section, does not offer the option to reboot into recovery. Instead it offers only system and power off.

Would it be possible to include the reboot to recovery option in there?

Otherwise, like others I'd like to express my gratitude for your work on this ROM, breathing new life into our NOOK tablets (ovation for me).

Terrific stuff.
[Nook HD, HD+ Android Development] euqilobaid:
I went forward and flashed the ROM. As expected i've encountered several issues which i needed to resolve. I'm sharing my experience for anyone coming from previous builds so they don't have to struggle with how-to's and testing.

Since i couldn't install TWRP with CWM (resulted with error code 6 - whatever) i tried with Flashify but the app couldn't get superuser access so this is what i did:

1. Downloaded SuperSU from GooglePlay which replaced stock SuperUser. With it i could grant superuser access to Flashify.

2. Used Flashify to flash TWRP recovery, but only to v2.8.7.0 (doesn't offer later version).

3. Booted into TWRP and flashed twrp-2.8.7.3-ovation.zip.

4. Reboted again into (now updated) TWRP and wiped everything and than flashed ROM + GAPPS.

For GAPPS i went with OpenGapps but MICRO version since STOCK is too large to fit into the partition (resulted with error code 7 i think). Now downloading the apps and setting up the tablet. So far so good :good:
[Nook HD, HD+ Android Development] amaces:
Sounds like you mangled your right hand pretty well; almost feel bad for joking about it last time… These logs are plenty good (dmesg/kmsg is sufficient), but they don't reveal any extra denials. The two that you noticed happen in the beginning, from the init scripts; setup_fs will always complain about missing block_device:blk_file read permissions, and Android doesn't allow this major permission in the init domain (or in other generic domains). Hashcode was even suggesting removing setup_fs completely as it cannot work early enough in the boot process. If it's SELinux, it'd be different denials, right after issuing powerctl commands, although I'm more confused about not finding /proc/last_kmsg… Oh well, I ran adb shell cat /proc/kmsg while rebooting to recovery, and although it works correctly, and no SELinux denials in sight, there are some troubling kernel warnings (see attached kmsg_reboot.log).

The option can be enabled in the TWRP UI, but I'm not sure it can work with the current scripts and bootloader. At least, reboot recovery has never worked for me in a recovery shell. I had a few other changes queued up, so what I call TWRP 2.8.7.4 is in experimental now.
[Nook HD, HD+ Android Development] euqilobaid:
So far the ROM is amazing - smooth and stable. The only two smaller issues i've found so far are:

1. When one disables the phone shortcut (bottom left corner) in the lock screen setting it actually enables the phone shortcut.

2. When i turn off the device it automatically powers back on within several seconds. Than i have to hold the power button for ~10 seconds to turn it off. Than it stays off. Same issue i had with some of the previous CM11 builds.

Also i had to flash SuperSU via recovery (ZIP file) because for some reason it didn't want to install from ROM.
[Nook HD, HD+ Android Development] belfastraven:
On hummingbird, reboot recovery from TWRP 2.8.7.4 recovery just boots to rom, as you suspected. BTW, my eMMC is 016G4A--it has a 2011 date.... Did anything else at all change in the kernel when it went from Permissive to Enforcing? This whole reboot recovery/poweroff does seem to have something to do with the kernel change. It seems to me to have something to do with power states, too; I've never had a problem soft rebooting. Perhaps someone running the enforcing kernel who has the problem could get a log as you did,and you could compare them. It would be difficult for me right now.

Only time I've gotten last_kmsg was when I interrupted the system while it was booting.

p.s. teasing re wrist --fine, not having any use of right hand/arm for another month-- not so good
[Nook HD, HD+ Android Development] mmnspeed:
Hi..I am running cm10.1.3 on my nook HD+...used cm11 but that was not stable and my device would reboot often...I use the device mostly for reading...would love to try this ROM...but I depend on the device a lot and can't afford it not working properly...how stable is this rom compared to cm11 official?...also I am running cwm recovery that I used for installing cm 10.1.3...read in the thread that I have to use flashify to install twrp..is that correct?...thanks

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] twiztid_:
I'm currently using the 8/19 build of this ROM and I'm amazed at it's smoothness, battery life, and stability. I would say it is easily faster, and more stable than CM11, and while I have not compared the two directly it does feel as fast as Jon Lee's CM10 "Yellow Kernel".

I believe CWM will be fine to install (up to the 8/19 build, after that CyanogenMod requires an updated recovery), but I would recommend upgrading your recovery anyway. TWRP is newer, and still maintained so bugs can be fixed, as well as having more features and options.
[Nook HD, HD+ Android Development] ieatabiscuit:
You will need to install tarp, yes. As for stability, it's been better than cm11 in several areas for a while now. I use these bills on my daughter's hummingbird, and she uses it for school. Only prevailing issues with nothing so far have been booting to recovery, and it looked to reboot when you cook too turn it off through the power menu. Booting too recovery works with the hardware button method, just not software method. There is also issues with screen casting, other than that most other little issues are native cm issues that are upstream, and not fixable here. If you're curious, I would install tarp (from amazes, as stock can't flash can yet), do a backup, then try it. If you don't like it, restore your backup, and it'll be like old times again.
[Nook HD, HD+ Android Development] mmnspeed:
Thanks...will backup the current installation and then give it a try....:)

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] steavis00:
Wow, this is the best version (29 Aug) yet. Haven't tried recovery, but switching from app-to-app is like 5x quicker. Thanks again.
[Nook HD, HD+ Android Development] TBueno:
0829-ovation running smooth so far. Boot to recovery is working again!

Thanks once again, AMaces.
[Nook HD, HD+ Android Development] mmnspeed:
Installed the ROM...it works really fine thanks to the developer...no issues going into recovery or turning off the tablet in the 08/29 build that I installed....just a question...haven't used twrp before...is it compatible with cm11 and cm10 ROMs or are there different versions just like cwm?

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] twiztid_:
It's compatible with the ROMs (what you use to install), but not the backups.

Misread that, TWRP is compatible with CM10/11/12/12.1. TWRPs backups only work in TWRP, the same goes for CWM, and CM Recovery (I would assume). It would be nice to see recoveries use compatible backups, but I think that's just a dream.

I just tested on my Nook HD+ on 8/29 with SELinux permissive, reboot to recovery works, power off does not.

With SELinux enforced, from the 8/27 kernel both do not work.
[Nook HD, HD+ Android Development] mmnspeed:
Yes,I realized that...

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] snoozer854:
Going from CWM recovery to TWRP

Currently on Nook HD I am running CWM recovery & CM 11. I would like to switch to TWRP, I like it better, then install CM 12.1 on this tablet.

I downloaded the hummingbird TWRP from your link & thought I could just flash it through CWM, but it aborted the flash.

Is it possible for me to do this before going with CM 12.1?

If so what should I do?

I really want to make these changes on 2 tablets

Thank you for everything

Mark
[Nook HD, HD+ Android Development] TBueno:
Try flashing TWRP with Flashify or TWRP Manager.

Although folks usually recommend a full wipe, I "dirty flashed" CM12.1 on top of CM11 without major issues.

[edit] Don't forget to flash a android 5.1-compatible Gapps pack along with the ROM or Google stuff will break
[Nook HD, HD+ Android Development] mmnspeed:
I used flashify app from play store for the purpose,but on nook HD+...would most likely work with your device as well...also flashify doesn't have the latest twrp recovery but once it has installed the old one,you can flash the latest one downloaded from the link in the op...you will require the latest twrp recovery for the most recent cm12.1 build...

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] snoozer854:
Thanks guys

Have TWRP installed. Kind of forgot all about Flashify.

Now to put 12.1 on.

Once again thanks a million for your quick response.
[Nook HD, HD+ Android Development] swaaye:
It looks like there is something wrong with OpenVPN or TUN. I'm not sure if this is a problem with CM12.1 or with this particular build. I can't connect to my home VPN. Both OpenVPN Connect and OpenVPN for Android say they connect but no traffic will go through the connection. I've tried experimenting with manual routes but no go. I had this VPN working with CM11 though.

Searching the web for CM12 / Lollipop and OpenVPN brings up quite a few problem help requests though.
[Nook HD, HD+ Android Development] LBurdick43:
I'd like to point out that when using a USB mouse on Ovation, I can't get a cursor to show up. The functionallity is there, everything works correctly, there's just a lack of a cursor on screen. I'm using the 8/29 build, and haven't looked at the others to see if this is a new issue. I realize this is a pretty insignificant problem, but I figured I shoud bring it to your attention anyway. Thanks for the great work amaces, this is a great ROM.

Then again, I might just be doing something wrong. I don't think so, though. ;)
[Nook HD, HD+ Android Development] ajislav:
Hi,

having followed this thread for quite some time, I finally decided to leave CM11 behind and try the latest 8/29

It really is smooth on my ovation.

Thank you amaces!

ajislav

p.s. Got one reboot when plugging in the charger while the tablet was in deep sleep. Will provide logs if reproducible
[Nook HD, HD+ Android Development] dbrickg:
Just installed 2.8.7.4 on my Nook HD+. Looks good so far. Thanks!
[Nook HD, HD+ Android Development] snoozer854:
Just put 12.1 on my Nook HD today & it seems to be working great so far.