yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] belfastraven:
hanks very much for testing. If you find a working January build, I'm hoping it works for me , too. (also hummingbird) . I seem to have been able to eliminate the particular error message that was being reported, but since I get no sound or picture, I can't tell whether I actually "fixed" anything. :) I did also seem to get the wrong screen resultion being reported, although at one point, at least, the nook did seem to get the correct edid from the TV.
[Nook HD, HD+ Android Development] granny smith:
OK, so the build on 1/29 works, but the image is inverted on the TV screen. It was like this on CM12 builds that I tried previously also.
[Nook HD, HD+ Android Development] blue whale:
Since there is a aosp for acclaim [nook book tablet] built by [MENTION=4473900]amaces[/MENTION], I wonder if you can enquiry this oddity of dead soft buttons on the NT:

I have no problem with stock 1.4.2, but I have dead soft buttons with CM10, cm11, cm12, cm13, aosp@amaces. I do not know how to contact people for CM13, so I contact you here. I expose the whole situation here

http://xdaforums.com/showpost.php?p=66842325&postcount=199

With stock firmware for the touch screen, I have no soft buttons near the hard nook-button, nor in vertical mode nor in horizontal mode.

With 10-touch firmware, I have soft buttons in vertical modes, but in horizontal mode, only two areas work, see the picture.
[Nook HD, HD+ Android Development] sasmith-129:
Yes, I experienced that too but I would just rotate the tablet and the video on the monitor would accordingly rotate making it correct. It was mildly annoying but not a big deal.
[Nook HD, HD+ Android Development] blue whale:
By the way, i tried to install superuser 2.65 on AOSP acclaim, but it fails, see here

http://xdaforums.com/showpost.php?p=66845569&postcount=723

Superuser works well in CM13...
[Nook HD, HD+ Android Development] mikeataol:
I have done several AOSP installs using this SuperSU with no errors, and it updates from Play Store with no issue
[Nook HD, HD+ Android Development] ipdev:
Had some problems with aosp_ovation-ota-MOB30J.160503, open_gapps-arm-6.0-pico-20160508 and BETA-SuperSU-v2.72-20160510112018.

I normally run the cm builds and have no problem installing rom and gapps together.

With this build I had to install the rom, reboot into twrp, then install gapps.

I had to drop down to BETA-SuperSU-v2.68-20160228150503 before I could get working root.

Currently running BETA-SuperSU-v2.72-20160510112018 (Updated using FlashFire-v0.33-20160511115223.)

Is this normal with aosp builds?
[Nook HD, HD+ Android Development] ipdev:
Did you try typing in terminal (twrp - advanced) before you install.

echo SYSTEMLESS=false>>/data/.supersu

Try BETA-SuperSU-v2.68-20160228150503 (This has become my failsafe build.)

Sent from my SM-T330
[Nook HD, HD+ Android Development] blue whale:
I installed supersu 2.52 via twrp 3.0.2 on aosp acclaim ! I will try the 2.68 and then the last version.

I updated theough the play store, to the version 2.65, then launch the application which updated the binaries.

I tried then to install version 2.68 and 2.72 through twrp like before, but I get the same errors than before....

In fact, these two attempts destroyed the binaries on the device, so I have to start with 2.52 again !

---------- Post added at 04:13 PM ---------- Previous post was at 03:47 PM ----------

I try to enter your command, but this is what I get :D

I cannot really control the keyboard. Also, when I try to erase only one character, the whole string is erased. I cannot delete only one letter...
[Nook HD, HD+ Android Development] forbiddenlake:
Is tap to wake possible on this device? I do not see it in Display & Lights
[Nook HD, HD+ Android Development] ipdev:
Yeah, the touch keyboard in twrp sucks. ?

So as an afterthought, thanks to you, I wiped my ovation and tried the same way as my older kindles. (Non-sdcard versions.) Worked in one shot..

Currently on my second attempt. Seems to be working so far. Just starting to install su.

This worked for me.

http://pastebin.com/gqdiP1Np
[Nook HD, HD+ Android Development] blue whale:
I tried up to after the gapps. then I go into slideload again, and on windows I do ''adb shell'', but I get ''error: closed'', so I cannot enter the next command.

How do I get adb shell after wiping, then installing the ROM, then gapps?

---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------

Okay so everything works now. I just boot the tablet intot the ROM and get the adb shell here
[Nook HD, HD+ Android Development] MrPerson:
I'm updating my girlfriend's ovation for her, got the newest TWRP and CM13 updates installed just fine. Having issues getting GApps working though. I read through the first posts and thought that I just needed to wipe data/factory reset and then install a GApps nano, but I kept getting error code 70 when trying to flash. After googling that and searching this thread some, I gave pico a shot. That installed just fine without wiping, but the setup wizard force closes nonstop. I searched this thread again and people mentioned a fixed GApps nano in the experimental folder, but it is empty as far as I can tell.

Am I missing a step here to get GApps working? If I need an older one, can someone tell me which older one? I haven't found any mention of a certain date or anything.

Edit:

Never mind... I went into TWRP, wiped data, and rebooted and now it is working perfectly.
[Nook HD, HD+ Android Development] sepehr@teh:
I'm using 7 Apr ovation , works fine. I installed a lot of programs.

What is advantages of new acclim ver ?

Which one is for ovation ( Nook HD+ ) ?

How can I update my current working OS ?
[Nook HD, HD+ Android Development] mikeataol:
the acclaim version is for the acclaim tablet, Nook Tablet , not the HD or HD+

I think things would go very badly installing an acclaim version on the ovation or hummingbird.
[Nook HD, HD+ Android Development] neonleon29:
I'm not aware of tap to wake on our device. But hitting the "n" at the bottom of the tablet or pressing the power button will wake the device. I'm using the AOSP ROM with Gravity Box which allows you to use double tap to sleep if you wanted that feature.
[Nook HD, HD+ Android Development] belfastraven:
Check out new builds in Experimental--I think we have Gello!

Gello seems very "zippy" , thanks, [MENTION=4473900]amaces[/MENTION]. I'm probably imagining things, but the rom, in general seems smoother.
[Nook HD, HD+ Android Development] TBueno:
That's good to know. Browsing heavy sites is one task where our device's dated hardware becomes evident, a lighter app might help with that. BTW I've shuffled through all the major solutions and Opera has been providing a quite decent solution for the sites I visit. That, along with the replacement of audiofx with Viper is keeping me impressed with the HD+ potential and durability. Won't be shelling out US$ 500 for a new tablet anytime soon (that's how much they usually ask for devices with comparable screen quality).

The experimental folder is empty, but there's a "cm-ovation-ota-MOB30J.150519" under "ovation", is that the one you're running?
[Nook HD, HD+ Android Development] ShapeShifter499:
I just got around to dusting off my old Nook HD. I'm currently running the 4/23 build of CM 13 for Hummingbird and I'm noticing a whole lotta quirks with battery. First of all I had to replace the battery because even with stock the battery got to about 59% and then died. But with the new battery CM 13 doesn't seem to detect when the battery is about to die properly. I can go anywhere from 10-30 minutes or so on 1% low battery and when the battery is really dead it just cuts out. The OS isn't properly shutting down the device on low battery and I'm worried that data will get corrupted. Does anyone know of any fixes, workarounds, or know why this is happening?
[Nook HD, HD+ Android Development] simon-edwards:
I'm going through exactly the same sequence with my HD. It reached the point where the dead battery logo would appear after only a few minutes of use.

I followed the advice of using twrp to wipe everything, i even blatted /rom.

Then I installed the old early cwm which allowed me to instal the single stock recovery and 2.2.1 rom. That is currently going through its first charge cycle since the stock rom went back in. So far s good.

I know my cm13 install gave antutu bm above 20000, and stock is down at 16472. But the stock gui feels very nippy compard to the treacle like cm13. I wonder if that could have been a symptom of the failure approaching?

After its settles down I will try AOSP and see how that feels.
[Nook HD, HD+ Android Development] ShapeShifter499:
The battery replacement did work for me, before I'd get around 30 minutes or so of battery even on stock but with the new battery I get 4-5 hours of battery life. The issue I have now is it's just not shutting down properly when it's low.

EDIT: "That is currently going through its first charge cycle since the stock rom went back in. So far s good." So stock IS shutting down properly when low battery time comes around?
[Nook HD, HD+ Android Development] belfastraven:
Yes--the files Have been moved to the respective device folders. I am actually on the hummingbird build. Its possible that audiofx would work for you now, btw. There have been a number of changes to it in the last couple of months.
[Nook HD, HD+ Android Development] TBueno:
Ovation CM May 19

The new Browser (Gello) performs great, but it's still very rough around the edges

Music and screen recording apps have new icons

AudioFX still crashes, unfortunately

There's definitely been some performance improvement, whether it's CM's or AMaces' work. Check out app switcher or Kindle's cold start for confirmation
[Nook HD, HD+ Android Development] Diesen_Dev:
Same problems with battery (all was good month ago), but i'm using cm 11.
[Nook HD, HD+ Android Development] mikeataol:
regarding the ovation cm version 160519, just a few notes....

the permissions for gello (and for com.android.browser 6.01) are not set correctly.

I go into settings/apps and touch them all on for behavior to start working more correctly

for example, video wont load until you set the permissions.

trying to go full screen video in the browser still gives the video in a window (sort of) surrounded by greenish staticy noise.

and in the youtube app, getting the dreaded "there was a problem, tap to retry", not on all videos but I am seeing it on videos thatshould work...

note to amaces: I could get logcats if you think its worth working on... I assumed not at this point. Same version youtube works perfectly on cm 13 acclaim 20160519 after the wl12xx fixes made it in . (and was working prior as well)
[Nook HD, HD+ Android Development] jaset_uk:
Thanks! I had exactly the same problem and tried everything other than wiping data, it never crossed my mind. Now after wiping data, GApps setup wizard ran fine and my HD+ is now up and running.
[Nook HD, HD+ Android Development] Quension:
WiFi failure with cm_ovation-ota-MOB30J.160519

So I finally got around to doing something with my stock Nook HD+, which of course meant a full wipe and flash of all kinds of new things.

cm_ovation-ota-MOB30J.160519 flashed and booted ok, but WiFi doesn't function. It shows a MAC of either 00:00:00:00:00:00 or 02:00:00:00:00:00, the on/off switch is greyed out, and if something like setup tries to turn it on it simply stalls there indefinitely.

Wiped again and tried cm-12.1-20151018-UNOFFICIAL-ovation which is working fine so far.
[Nook HD, HD+ Android Development] braylandon92:
I am having this same issue. I'll try that next. Thanks.
[Nook HD, HD+ Android Development] belfastraven:
weird mac address/wifi problem.

Check the bug reports for an explanation. . I believe now that you have successfully installed cm12.1 you can install (dirty flash) the lastest cm rom and you will have WiFi.
[Nook HD, HD+ Android Development] blue whale:
The last version for acclaim is unstable too. Gapps are no longer working and prevent the use of the tablet, if they are installed, since there is an error message popping up constantly, preventing any use. I returned to the previous version of acclaim by amaces
[Nook HD, HD+ Android Development] mikeataol:
I assume you mean the 0515 version?

to install the acclaim version, install the rom , then let it boot.

reboot to recovery, install the gapps, wipe data, cache and davlik
[Nook HD, HD+ Android Development] simon-edwards:
This sequence worked for me. Thanks for the tip. I did one thng different. Before removing twrp I reformatted /rom as well as the standard factory reset. Then when I had installed the full 2.2.1 with stock recovery zip the battery charging sprang back to life. this single extra step seems to avoid having to go through the initial stock installation sequence twice.
[Nook HD, HD+ Android Development] Trance-M:
Same here, but instead of cm 12.1 I decided to give cm_ovation-ota-MOB30D.160422 a try first. Now Wifi works too.

(Used twrp 3.0.1.0 and open_gapps-arm-6.0-pico-20160521)
[Nook HD, HD+ Android Development] ipdev:
cm_ovation-ota-MOB30D.160422

aosp_ovation-ota-MOB30J.160503

Both seem to be very stable builds.

Currently running..

twrp-3.0.2-0-ovation

aosp_ovation-ota-MOB30J.160503

BETA-SuperSU-v2.74-2-20160519174328 (system mode)

open_gapps-arm-6.0-pico-20160519

Nova+Launcher_4.3.1

NOOK_bn.ereader_4.6.0.234_V688

PS..

The nook app has been updated. NOOK_bn.ereader_4.6.0.234_V688

(Currently only shows the update on my samsungs.)
[Nook HD, HD+ Android Development] TBueno:
I ran out of space in /system and had to switch Gapps versions. Setup wizard neverending error dialogs were preventing me to use the device too.

Wiping everything (including /data :crying:) certainly works, but it's an overkill. Check out this thread, you can simply grant one permission to Setup Wizard and be done. It requires some patience (interacting with the device between dialog pops) but oh boy it's so much better than reinstalling/restoring everything...

p.s. wiped system, cache and dalvik before reflashing too
[Nook HD, HD+ Android Development] pchc_lx:
i'm actually still seeing cm_ovation_ota-MOB30J.160519.zip in the Experimental folder, not in the Ovation folder. were they moved back to Experimental due to instability? don't want to flash until it's a stable build, if possible.
[Nook HD, HD+ Android Development] belfastraven:
Yes, they seem to have been moved back. I don't know why. Only [MENTION=4473900]amaces[/MENTION] would post or move the rom. If you read the last couple of pages of posts you will find that someone was having trouble with youtube videos in the browser or youtube in general, I believe. The rom is a bit larger than normal, probably because it includes the new gello browser, and, also, some people who seem to have been coming from pre 12.1 roms or stock have said they have WiFi mac issues. For me, on hummingbird, the new rom is fine. ( I should note, that for me, HDMI ouput is not working, but I have never gotten it to work...). FWIW
[Nook HD, HD+ Android Development] TBueno:
Based on what I read here, I'd guess ROM size is more of an issue than videos or wifi, wich have have been troubling specific users for a while.

Flashing 0519 on top of 0422 fills up /system partition as in showing zero bits available, and that can lead to several issues.

After switching to pico gapps (not possible to flash nano alongside 0519) though, everything is as good or better than 0422 on my ovation.
[Nook HD, HD+ Android Development] pchc_lx:
thanks for the insight, i think i might sit tight for a bit and see what happens with these issues before flashing again.
[Nook HD, HD+ Android Development] Merazomo:
USED:

twrp-3.0.2-0-ovation

cm_ovation-ota-MOB30D.160422

open_gapps-arm-6.0-pico-20160519

I tried CM13 for a day on my Nook HD+, and I must say it was pretty stable; however, I went back to KitKat for now because my little nephew likes playing SNES Emulator games on my TV through HDMI, and I couldn't get HDMI to work. I'll definitely switch if this problem is ever resolved.

I have some questions though if anyone is kind enough to answer, if would be greatly appreciated:

Does anyone know if CWM can be used to flash CM13 instead of TWRP?

Are the CM13 installation files the same for both Nook HD & Nook HD+?
[Nook HD, HD+ Android Development] BenGman:
CWM Recovery

I have CWM 6.046 recovery on my Nook HD+ coming from TWRP because 80% of my touch digitiser isn't working so I needed a recovery that used buttons for navigation. I used ADB to launch USBHostSwitcher on first boot to use a USB Keyboard/Mouse to go through setup then to enable a BT KB+Mouse.

A CWM boot SD card recovery was used to flash the CWM Recovery. I used CWM to flash the latest Marshmallow 0503 ROM with the micro Gapps (the largest Gapps that could fit and the minimum required to get the mouse cursor, which is a must for my non touch Nook HD+). The ROM is working great with no complaints.

I might downgrade to KitKat though to use this tablet with HDMI as a dedicated TV box.

What is the latest Recovery (CWM or TWRP) that uses buttons only instead of touch?

Are you using the latest CM KitKat nightly (dated this week) with HDMI and SNES?

What is the latest CM/ASOP ROM that supports HDMI properly?
[Nook HD, HD+ Android Development] Merazomo:
Thanks a lot for the info. I made a mess of my perfectly working Nook HD+ because I thought I needed to change from CWM to TWRP to install Marshmallow. I found out the hard way you can't restore a backup image you made with CWM in TWRP. It took me all day to get back to KitKat since my CWM boot SD card doesn't always work for some reason.

Yeah, I'm using these with HDMI output on Nook HD+ with KitKat 4.4.4:

-- cm-11-20160523-NIGHTLY-ovation (added a couple of days ago I believe)

-- pa_gapps-modular-micro-4.4.2-20140426a-signed (older gapps I'm pretty sure, but I didn't feel like looking for newer ones)

-- CWM v6.0.4.6 (same as yours)

Remember though, some applications are copyright protected. When you try to watch live TV (depending on the application) through HDMI, it might give you a warning that HDMI is not supported. This has nothing to do with the Nook, TV, or HDMI cable. It's more of Android and the owner of the application. The Time Warner app has always given me that problem, while Showbox runs great.
[Nook HD, HD+ Android Development] belfastraven:
mousable TWRP

You can find a zip file for building an ovation sdcard recovery with a mousable TWRP 3 here:

https://www.androidfilehost.com/?fid=24459283995314503

You just need to make sure to write the MLO file to the sd card first. The usb mouse needs to be installed before you boot. To make this work, USB Host has been switched on in the recovery. It is easy enough to build an internal recovery this way; I believe that charging doesn't work while USB HOST is forced on; if you are not normally charging while in recovery, that wouldn't matter.
[Nook HD, HD+ Android Development] mikeataol:
regarding youtube errors, it appears to be within the app , I dropped back to an 11.01.56 version , and it plays the videos that are problematic on the newest releases just fine.

I just started at 11.01 to confirm the that the app was the problem

https://youtube.en.uptodown.com/android/old
[Nook HD, HD+ Android Development] blue whale:
I wiped everything and acclaim 0515 works well with gapps!
[Nook HD, HD+ Android Development] belfastraven:
There are new CM roms 5/30 in experimental

Running fine for me on hummingbird. This is, as was the previous cm rom, a large rom. I dirtied flashed over the previous one and have had no issues, except for having to choose my WiFi network after boot.
[Nook HD, HD+ Android Development] TBueno:
Man, how do you detect them so fast? Got some sort of rss tapping right into those folders?

This weekend I tried to flash the 0422 build (CM-ovation) to compare wifi stability but the /data backup I extracted under 0519 wouldn't load on it - it restored just fine, but it wouldn't absolutely let 0422 boot. 0422 boots fine if I wipe data. Is that expected, like some sort of security lock placed there to prevent us from screwing our devices?

Whatever it is, now I'm trapped in the present, since a full 0419 nandroid backup I kept gave me an error 255 when restoring...
[Nook HD, HD+ Android Development] belfastraven:
No--- I actually just have the site bookmarked and check it when I am on the web for other reasons. I do have an IFTTT feed that monitors amaces' public activity on github so I han catch changes he makes. I originally was going to try to come up with a changelog that way, but it really would be very difficult to do that. I build myself, usually at least once a week, because I like to pick up improvements, from CM and google, and because I am trying to figure out why the devices reboot when shutdown, as well as to see if I can help with the HDMI audio problem.

(I have also been a "windows insider" running 10 since it was first released, and have been running Ubuntu 16.04 since its dailies.. Just what I do instead of jumping out of airplanes or heli-skiing, I guess:)

Lately, I have been letting google try to restore for me (through the setup wizard)if I do a clean build--sometimes it has worked, sometimes not, but I've not had a problem specifying all the apps I want reinstalled from the store, and I don't keep "personal files" on the device. Are you restoring from a twrp nandroid backup of data and using a 3.02 verion of TWRP? How was the device failing to boot--did it stop at the bootloader or just keep going in the bootanimation until you stopped it, or something else. Do have have the log from the failed restore?

Is it failing during the restore of the data partition ? If you are happy with the current rom, you might not want to bother figuring out the problem-- I have sometimes found that in order to do a successful restore I actually had to format data--FWIW
[Nook HD, HD+ Android Development] acr123:
Lately, I have been letting google try to restore for me (through the setup wizard)if I do a clean build--sometimes it has worked, sometimes not, but I've not had a problem specifying all the apps I want reinstalled from the store, and I don't keep "personal files" on the device. Are you restoring from a twrp nandroid backup of data and using a 3.02 verion of TWRP? How was the device failing to boot--did it stop at the bootloader or just keep going in the bootanimation until you stopped it, or something else. Do have have the log from the failed restore?

Is it failing during the restore of the data partition ? If you are happy with the current rom, you might not want to bother figuring out the problem-- I have sometimes found that in order to do a successful restore I actually had to format data--FWIW[/QUOTE]

Where is 3.02 version of TWRP for Ovation. I only see 3.01 ?

Al
[Nook HD, HD+ Android Development] vinceweis:
Twrp.me/devices
[Nook HD, HD+ Android Development] TBueno:
Thank you for all the info. Nice tip on amaces github, I'll definitely try and take a look at that.

I'm also excited by the latest and greatest, but I tend to get paranoid and credit all bugs to being on the edge. So running "stable" versions means I trust my devices better.

I know restoring has been made quite easier since Lollipop, but I've been fine tuning my setup for so long that I'll avoid that as long as I can. Also, I've a handful of apps that require device registration, so I'm really not eager to refresh my /data.

I'm running TWRP 2.8.7.4, and usually don't update these things unless I have to (if it ain't broke...). It's the same recovery version I used to install the previous ROM and extract the backup I was trying to restore. Cid just kept wiggling its antennas and flashing his halo forever, until I force rebooted the tablet. And I don't have a log, but really, it's no big deal. I only asked in case there was some common knowledge about backflashing ROMs and restoring data backups.

I'm quite happy with my current build, it's the best I've tried so far (AMaces always move ahead, it's impressive). I'll just try to hold my horses when a new build comes out, because if something goes wrong for me, falling back to the previous ROM might involve a full reset.