yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] js290:
No, I just did an in place update., wiped cache, and rebooted. I did not factory reset.
[Nook HD, HD+ Android Development] TBueno:
0726-ovation is running really great. Setting animations etc. to 0.5x doesn't make transitions janky anymore, meaning the device can now respond faster and look good doing it. Bluetooth performance seems improved. Once again, thank you AMaces! :good:

I can confirm recovery (TWRP) cannot be triggered through software in this build. Too bad, TWRP Manager just got updated and is quite handy. I wonder if enforcing SELinux has something to do with these interactions, we'd already lost the ability to shut down device from within the OS interface before...
[Nook HD, HD+ Android Development] belfastraven:
Can confirm no recovery through software also on Hummingbird. It worked with same version of TWRP on 6/23 rom.
[Nook HD, HD+ Android Development] TeutonJon78:
What's new in the 2.8.7.X version of TWRP?
[Nook HD, HD+ Android Development] andtron:
I am using the ovation and I also have issue booting my HD+ into recovery, I am using enforcing too. I am using my own July 26 build.
[Nook HD, HD+ Android Development] Nevermindthelabel:
Worked for my hummingbird

I just tried it using the TWRP manager from play store with no issues. Dirty flashed the 7/26 over 7/20. Another great build, running great
[Nook HD, HD+ Android Development] krustyzy:
Hi, how would I enable device encryption with this ROM? When I tried the CM dmcrypt way, something in the boot area was overwritten and the tablet wouldn't start at all any more ...
[Nook HD, HD+ Android Development] TBueno:
In TWRP Manager, have you tried "boot into recovery", "shut down devices" under "Reboot" section? Are you sure they all work?
[Nook HD, HD+ Android Development] SteveCoops:
Yep messed around with the GPU rendering and overlay settings and turned screen off and on and it seems OK now. Not exactly sure what bit fixed it :)

By the way, latest build as of last night installed on my HD and HD+ and all seems good - big jump from Android 4.x from about a year ago.
[Nook HD, HD+ Android Development] Nevermindthelabel:
The only thing I had tried was the boot into recovery. The shutdown just does a reboot as it does via the power menu. In the advanced power menu reboot to recovery does work, and I did successfully power off the device in terminal with "su" and "poweroff" but I could only turn it back on by plugging in the charger. Mild inconvenience for me, as I have only rebooted when needed with the xposed framework.
[Nook HD, HD+ Android Development] pastordl:
7/26 running like a Swiss watch. No problem rebooting to recovery from power button, ROM Toolbox, flashify, or TWRP app. TWRP app doesn't do full backup while in ROM though. I have 3.2 to 3.3 gig backup with over 200 apps and data. It only does first 1.5g of data. Will stick with flashify or work in recovery directly. Thanks again @amaces.
[Nook HD, HD+ Android Development] tnckd13:
Thank you for this information. I just bought Nook HD+ and I am planning to install this CM 12.1. Is cm 12.1 version good for daily use? Is there any review on this rom?
[Nook HD, HD+ Android Development] Nevermindthelabel:
Works great on my hummingbird

Ran the official cm11 on my hummingbird for a year or so, it was pretty smooth. With a few weeks use of this cm12.1 it's awesome. No issues with any apps, my girls play games all day on it and battery life has been great. Assuming the HD+ would be about the same
[Nook HD, HD+ Android Development] TBueno:
ROM Toolbox and Flashify don't cut it for me either (Ovation 07-26). Guess I'll just disable advanced reboot options (out of sight, out of mind) and be happy with physical buttons. After all, these latest builds are so nice I probably won't be flashing that often anyway!
[Nook HD, HD+ Android Development] rpadula:
I was on 0723 build and dirty flashed to 0726. it didn't worked out so well as i was expecting.

had to wipe and now it's restarting.

i' have some issues when trying to power off, it always reboots, so how can i shutdown my hummingbird?

But other than that it's great, i've tried cm12.1 in may and now it's so much better.

I see you guys talking about twrp where i can download? i'm using cwm
[Nook HD, HD+ Android Development] Nevermindthelabel:
TWRP

Tried to post the url but I'm not cool enough....yet :crying:

It's on the twrp.me site though, just search for hummingbird

Don't believe you can do a simple shutdown on this build. I have powered mine off in terminal with "su" and "poweroff", but had to plug it into the charger to get it to turn back on. Power key wouldn't do it
[Nook HD, HD+ Android Development] rpadula:
found a way to shutdown.

just hold the power button when it's restarting (still in cyanoboot)

now i'm having issues with gapps failing. will try others.
[Nook HD, HD+ Android Development] agantai:
why on the latest build i can't turn off my nook hd tablet ? not that it's a deal breaker i much prefer lollipop but i would like to know why & if it's fixable in a future build thanks
[Nook HD, HD+ Android Development] TBueno:
You can shut it down as per rpadula's tip or by booting into recovery (vol+n+power) and selecting shut down from there.
[Nook HD, HD+ Android Development] rman500:
Can't change the brightness

Hi, the ROM works pretty good except for the fact that I can't change the brightness. It is stuck at max brightness and whenevve I try to change it, nothing happens. Also, Google play services cannot seem to connect to the internet to update. I previously had cm 11 and I updated through CWM. Did I make a mistake? Any help is appreciated.
[Nook HD, HD+ Android Development] sutty86:
Great update ,works fine dirty flashed over cm11, anyone know any volume mods,I have Dolby atmos app on my phone its great just wondering would it work
[Nook HD, HD+ Android Development] Nevermindthelabel:
Absolutely no issues with mine, connects fine and brightness slider works great. Perhaps using TWRP would make a difference? Seems to be the recommend way to do it. Just used flashify myself and put the latest TWRP over CWM. Seems to be doing a great job
[Nook HD, HD+ Android Development] twiztid_:
Ever since the 7-15 build, with the 7-16 kernel (I think), I've had quite a bit of instability with Browser, like freezing and force reboots, and rendering glitches on 7-26. It wasn't so bad on 7-15, but seems to be worse, more frequent, on 7-26.

I realize this may not be a priority since Google/AOSP in its infunite wisdom abandoned Browser in favor of pushing Chrome, but I can hope a solution won't be too involved.
[Nook HD, HD+ Android Development] tnckd13:
Thank you for this information~~!
[Nook HD, HD+ Android Development] jaydeedid:
Shutdown/Reboot

I've experienced shutdown/reboot issues with every flavor of CM I've ever used, from 10 to 11 to 12. I assumed it was unique to my HD+ since I hadn't read any posts from others reporting similar problems. I'm currently using the 7/26 build of this fantastic ROM and am still having the problem. I've never been able to shutdown without the tablet just starting back up on its own. Sometimes a "Shutdown" app from the play store will work and I'll probably look into installing one soon. Usually, I just hold the power button until the device shuts off.

Now I also seem to be unable to reboot to recovery also. Hardware buttons work for both issues and neither bother me much.
[Nook HD, HD+ Android Development] Nevermindthelabel:
Amplify

Anyone else having issues with the xposed mod Amplify? Installed it and rebooted a few times, but it just gets hung up on the checking to see if xposed is installed. Only module I'm having any trouble with
[Nook HD, HD+ Android Development] asakurato:
It probably doesn't support 5.1.1
[Nook HD, HD+ Android Development] amaces:
Not really sure why people have issues booting to recovery again. I tested both the UI menu and adb reboot recovery, and they generally work well. I say generally because, once in a blue moon, things fail for random reasons. If SELinux Enforcing had something to do with it, this change would affect everyone consistently since SELinux denials are pretty deterministic… Otherwise, no reason for brightness control issues all of a sudden; search the thread for that one case where it was solved with a thorough cleanup and reinstall.

Pretty odd that this should happen on hummingbird, but not on ovation… This kind of flickering never happened on my HD+, but I can look through logs if you can capture them while the issue happens.

Are you doing your own thing again, with CMUpdater? I really didn't want to open that box, but these builds are tagged UNOFFICIAL for good reasons (e.g., different signatures, etc). As I said before, just because the recovery allows automated flashing scripts, it doesn't mean you should rely on that feature all the time. And if you do, use something like Flashify, which discriminates between TWRP- and CWM-style scripts. I'm not sure about the state of CMUpdater, but I would bet it's optimized for the CM recovery, and not for TWRP… Bottomline, never had issues with properly written TWRP scripts.

The official stuff (https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html), plus special sauce that I talked about a while back.

I'm not sure that Lollipop-style encryption is setup properly in our device trees. Each fstab would need to have support for encrypted /data, plus the updated flags in TWRP. How important is this feature for you? Off the bat, you should expect potentially massive slowdowns, as the CPU is already busy with zRAM stuff, and it's not like we have bandwidth to spare… I personally wouldn't enable it, so testing would be all on you, but yeah, I can attempt to update the encryption support.

You did a clean install, right? What you're describing sounds more like configuration issues… Like above, search the thread for that one case where the brightness control issue was solved with a thorough cleanup and reinstall.

Can't say that I've noticed more issues with Browser. Even using it a lot less, now that Chrome runs decently, I do use WebView all the time with in-app rendered webpages. Browser is basically a thin shell on top of WebView, so not sure why you'd suddenly experience instability. Maybe clean the Browser settings? Let's hope that CM is messing with the code again (they do their own Chromium thing from time to time), and things will be sorted out in the future builds.

Amplify is one of the two Xposed modules that I've been using for a while on ovation, and have yet to run into any issues. Look through the logs (both Xposed's and Amplify's).
[Nook HD, HD+ Android Development] yapyisoon:
newbie instructions

Hi, I need a bit of help, apologies for my ignorance.

I have problems finding the instructions to install CM12.1 on my nook. Thanks and much gratitude to amaces!
[Nook HD, HD+ Android Development] agantai:
[MENTION=4473900]amaces[/MENTION]

would you be able to fix the broken shut down function in the next build ? at the moment it's not working every time i turn my tablet off it restarts again by itself so i have to leave it in sleep mode all the time.
[Nook HD, HD+ Android Development] ieatabiscuit:
Flash custom recovery to device (if coming from stock, you need to make a bootable SD card, there are tutorials in the forum; if coming from CWM and want TWRP just use Flashify. TWRP is officially supported, so it's on their websight, or get the custom brewed version from link in OP)

Download ROM from OP for your device, and move it to your SD card then reboot to recovery (hold N button during boot or use a boot option found in some custom ROMs)

Install CM12.1 goodness

???

Profit

Note: There are other options like F2FS that can be set, but if you need this quick run through, you don't need to be messing with that stuff, you can effectively format your Nook, and [MENTION=4473900]amaces[/MENTION] might poke you in the eye for asking how to unbrick a device.:D

Also, if you are still getting stuck finding the bits and pieces for making a bootable SD card, just PM me, I don't mind helping in more detail.
[Nook HD, HD+ Android Development] Sus_i:
hello amaces

Is the kernel from ovation / cm12.1 20150726 compiled with cifs support? If yes, where can I find the right kernel module "cifs.ko"?

Best regards and thanks for your work on cm12.1 :good: :)
[Nook HD, HD+ Android Development] amaces:
No idea whether it can be fixed… People have been reporting it for a very long time, but no relevant logs, and this issue doesn't happen on my device, so where do I start? I'll make a poll to get a better idea about its prevalence, about the kind of devices affected, etc, and we'll take it from there.

I certainly will ;) especially that clear rescue instructions are in several places, including the OP… Thanks for helping.

I think CIFS has been builtin (i.e., no need to load a module) since forever. If you're curious about kernel build configuration, just look through the zcat /proc/config.gz output.
[Nook HD, HD+ Android Development] twiztid_:
I feel like a newb for asking... but what kind of log? And how do I make it?

I've glossed over it in the past, but none of it ever stuck. :/
[Nook HD, HD+ Android Development] agantai:
ok thanks, my device is nook hd 7 inch tablet.
[Nook HD, HD+ Android Development] echoedge:
I am also getting the fail to shut down error.. It always starts right back up.

Yesterday I noticed, though, if the hd+ is plugged into power source it shuts down fine.

One more thing I wanted to add/ask about, haven't browsed through all of thread so idk if this has been brought up yet, after like 24 hours or so left on (set, I think it depends), but after its left on for extended, the screen goes berserk. The touch calibration goes way off.. Touches are interpreted as swipes, and usually I can't even restart normally because I can't get screen to press the restart button on screen.

Is there a fix?

Other than these two issues I'm loving the ROM.. Fast, current, works great.

I am on 07 19 build, btw
[Nook HD, HD+ Android Development] amaces:
Heads up, poll is open for your voting pleasure.

http://xdaforums.com/showthread.php?t=1520508

That sounds worse than anything I've experienced, even in the CM11 days, and really, it shouldn't happen that often, but when it does, a quick suspend/wait a sec/resume cycle fixes the touch controller. BTW, the July 26th build has enough updates to warrant installing it, so test it out.
[Nook HD, HD+ Android Development] echoedge:
Okay I will update ASAP.

Also what do ya mean by quick suspend then do a resume cycle. Where is that function/how would I perform that?

Thanks

Edit: where is the link to the poll?
[Nook HD, HD+ Android Development] amaces:
I mean power button to turn screen off, wait a bit, power button to turn it back on ;) Poll should appear at the top of the page, or above the OP, although probably only in desktop view.
[Nook HD, HD+ Android Development] ieatabiscuit:
Just something I noticed, might help, might be a waste of a post. The screen is very sensitive to fingerprint oil buildup. Without fail, if my screen starts to get twitchy, if I clean all the remnants of fingerprints, or streaks from the screen it stabilizes and works perfectly again. I doubt it is anything that can be addressed ROM side, it's just a finicky screen. It HATES not being flawlessly clean.
[Nook HD, HD+ Android Development] belfastraven:
Just making sure I understand the poll question properly: Are you asking specifically about the 7/26 rom? My answers would definitely vary by rom. e.g. reboot to recovery normally works for me, but has never worked on the 7/26 rom, whereas power off has normally caused a reboot and , indeed still does with this rom.

Also, fyi, several people on this thread have reported flickering on nook hd . i will send you logs after next update, but I believe this to be some kind of power management issue. It happens when installing a new rom most of the time, sometimes after a normal reboot. Turning the screen off and on always fixes this for me. I definitely have seen power related messages in logcat.
[Nook HD, HD+ Android Development] twiztid_:
You turn the screen off, clean it, then back on, right?

I think the off/on part plays a bigger role. I have a screen protector on mine and I still get that issue. I thought wiping it fixed the problem, but it is indeed just off/on that fixes it.
[Nook HD, HD+ Android Development] ieatabiscuit:
You may be right, I tend to habitually clean my screen on both my phone and my nook. They just feel better, but like I said, it might be a waste to say it, but it doesn't hurt either way.
[Nook HD, HD+ Android Development] mhunt13:
Agree with [MENTION=5672278]belfastraven[/MENTION], reboot to recovery from power off menu is rom specific. Always worked for me in previous roms, but 7/26 rom just reboots android. I'm using your TWRP recovery.

Power off from power menu hasn't worked in a long time on any rom version. Just reboots ... I have gotten used to just holding the power button until the HD+ shuts down.
[Nook HD, HD+ Android Development] G_P082:
I'm a noob at this. What version do I download forma Nook HD+ BNTV600?
[Nook HD, HD+ Android Development] jaudio:
Ovation
[Nook HD, HD+ Android Development] G_P082:
Thanks! Got it.
[Nook HD, HD+ Android Development] 3c57x9:
Ok so I originally dirty flashed 7/26 SELinux enforcing over 7/23 with little fanfare. Everything seemed to work except for booting into recovery from the power menu. I had a bit of downtime and decided to see if how I installed it had anything to do with why booting to recovery wasn't working.

1. I backed up Apps/Data and System Data with Titanium Backup to external flash

2. I used finger gymnastics to boot into recovery

3. I Factory Reset, Advanced Wipe - Dalvik Cache, Data, Cache, system, and format Data, Cache

4. I installed 7/26 on a clean system. Booting into recovery from power menu still did not work

5. I boot into recovery again and did a full wipe, and flashed 7/23 on a clean system. Booting into recovery works.

6. I shut down and boot into recovery and dirty flash 7/26 over 7/23. Booting into recovery from the power menu does not work. In addition I experience major glitches with touch not responding or responding erratically. It would appear, for those of you who are experiencing touch issues, doing a clean install of 7/26 should help.

I am back on 7/26. Everything works except for booting into recovery from the power menu. I did a Logcat to flash which I am attaching to this post if you would like to take a look amaces. I do see an error in there.

Oops! Apparently I'm too noob to attach a file or include a link to pastebin. Here are the bits toward the end:

07-30 19:47:03.092 E/ShutdownThread( 425): Unable to find class com.qti.server.power.ShutdownOem

07-30 19:47:03.092 I/ShutdownThread( 425): Rebooting, reason: recovery

07-30 19:47:03.148 I/uncrypt ( 2538): no recovery command file or no update package arg

07-30 19:47:03.148 I/uncrypt ( 2538): rebooting to recovery

07-30 19:47:03.154 I/ActivityManager( 425): Start proc 2539:com.android.externalstorage/u0a8 for broadcast com.android.externalstorage/.MountReceiver
[Nook HD, HD+ Android Development] jaydeedid:
Ditto
[Nook HD, HD+ Android Development] agantai:
[MENTION=4473900]amaces[/MENTION]

i have voted (hummingbird: power off fails most of the time) it fails all the time & even when i reboot into recovery if i choose power off from recovery instead of restart the tablet will still restart on it's own !!
[Nook HD, HD+ Android Development] lonecanislupus:
Ovation CM12.1 flash successful, gapps flash unsuccessful

Hello,

I just flashed TWRP, wiped everything but the microsd, and then I went to install the CM zip, and added the arm gapps for 12.1 that I got from the CM gapps page. Both zips flash, but it appears that only CM was successful because the Nook HD+ automatically downloaded google apps that should have already been installed. I haven't noticed anything out of the ordinary. Apps took a little while to install but I figure that's because of the move from dalvik to art. Otherwise the performance is good. Is there anything to worry about? Should I reflash?
[Nook HD, HD+ Android Development] G_P082:
Nevermind. I feel like an idiot. Figured it out and its upgrading now.

Works great! Fast and it has brought new life to an old tablet. One issue though, I too cannot shut down. It just restarts. It wont go into recovery mode either unless I use hardware buttons. Other than that it is excellent.
[Nook HD, HD+ Android Development] G_P082:
Ok, big problem.

I tried to shut down and it just rebooted. Now I cant even use the tablet because of a constant error that pops up "com.google.process.gapps has stopped" If I tap "OK" it just immediately pops back up. it prevents me from tapping anywhere but the "OK" button. Google play store Icon is also gone and it keeps telling me youtube has stopped even though I never opened it.

What do I do now?
[Nook HD, HD+ Android Development] N0he:
try to reflash gapps
[Nook HD, HD+ Android Development] G_P082:
Ended up having to wipe everything and re flash and now it's working. But I don't have root. It's checked under developer option but apps that need root don't work. Strange.
[Nook HD, HD+ Android Development] maxaurelius:
Survey

Firstly, I want to thank Amaces for his dedication and tireless efforts in improving our nook devices. Now about the survey, I just clicked on the choice where it says both reboot to recovery and poweroff work. But I have to mention that I am on the CM12.1 Ovation 0720 build with CWM 6.0.4.5 and power off works 50% of the time. Also, when it goes to restart after pressing powering off, I use CWM to poweroff my nook. After poweroff from CWM, I have to use charger to get it to start. I am guessing there's a power drain or the poweroff from CWM didnt work and nook restarted and then power drain. Its a minor thing for me. I'm just amazed that our Nooks are able to function well with Android 5.1 under the hood. Many thanks to those who are behind the scenes building and testing.
[Nook HD, HD+ Android Development] twiztid_:
In Developer Options, disable root, then set it back to Apps or Apps and ADB.
[Nook HD, HD+ Android Development] belfastraven:
On the 7/31 build for hummingbird, with your latest TWRP recovery, shutdown from power menu now works for me.

re "flashing" on rom installation/booting. I'm attaching two sets of logs, one from immediately after I installed new rom last night , on from this morning after I rebooted a couple of times, trying the reboot to recover(still not working for me) and shutdownfeatures.

My own feeling is that the flashing is not a big deal since the fix is just to turn the screen off and then on again. The device gets pretty warm and I believe to make it stop flashing there would have to be more pauses in the boot and or recompilation code.

Also, I remember from the previous thread on 12.0 that the HD'S have two different panels--I wonder whether this is a problem only for one .

Thanks again.
[Nook HD, HD+ Android Development] PeteInSequim:
I have a Hummingbird that exhibits the unexpected reboot after shutdown nearly every time. If you are considering investigating this problem I'd be pleased to donate it to you for your research. Just PM me a shipping address.

It has your build 20150720 (appears in About tablet as 20150719).

Many thanks for your CM-12.1 accomplishments. I and several of my friends are enjoying the fruits of your efforts.