yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] andrerz:
I can confirm that although the lnos experimental (17 feb) builds work on Ovation (hd+) they do not work on Hummingbird (nook hd) where it just sits at the Lineageos boot animation (once did briefly see full lineage logo but with mirror image writing before returning to the animation!). Tried many times/ways clean/dirty etc. Furthermore when I flashed experimental twrp 3.03r3.4? (now gone see below) and tried installing a number of ways eventually it just bricked the hummingbird when I tried to wipe the system partition, the partition became unmountable/ non existent and twrp could not fix it.

In the end I used verygreens sd card with CWM method and reinstalled CM11 (26-aug-2015), which now runs as smooth as butter, much better than any cm14 build I've tried both on Ovation and Hummingbird.

I notice that the old experimental twrp builds that I used have been removed and replaced with new dated 3.03 build, any info about that?
[Nook HD, HD+ Android Development] starbright_:
So your recommendation is CM11, even for Ovation (HD+)?

I was just wondering, whether it is time to step to Lineage ...
[Nook HD, HD+ Android Development] andrerz:
My comment about cm11 was for hummingbird.

Ovation has always had sub par performance with every cm build, I think the gpu is just not up to the job of driving a hd+ screen. Plus I know there are bugs in the proprietary omap drivers (at least thats where I think the bugs are), the most frustrating being the scroll issue that occasionally turns scroll into zoom and requires a quick off/ on to fix.

For now I am still hopeful for Ovation, the 17 feb build shows promise. I will give the new 28 feb builds a shot and compare them all side by side with cm11 (yes I have several nooks ;))

and post some feedback in a day or two.
[Nook HD, HD+ Android Development] belfastraven:
The new builds fix the problems (which were actually with the lineage build) which caused boot looping, etc.

I have tried them both and they installed with no problem for me.
[Nook HD, HD+ Android Development] rpadula:
My hummingbird is working again.

used the newest recovery in experimental and it's working flawlessly, flashed the img thru the bugged recovery that i had, rebooted and voila.

Alive and kicking
[Nook HD, HD+ Android Development] digixmax:
FWIW, I upgraded to lnos_ovation-ota-NMF26Q.170104 from CM11 (which I had been using for nearly two years until about two months ago when its responsiveness started to degrade) and I am very happy with it.
[Nook HD, HD+ Android Development] andrerz:
The latest 28 feb build for hummingbird now working fine.

Its also seems almost as smooth/quick as cm11.

Only points of note, on initial boot, the Lnos logo when it finally appears is mirror image text and the initial screen thereafter is upside down. Some app crashes occur "process.app??" and pico tts during setup, but only once.

Possibly a bug though, when waking the tablet it seems that the accelerometer is delayed or ignored, in that if the screen rotation is incorrect, it will not self correct until you vigorously spin the tablet a couple of times.

Good progress though!!
[Nook HD, HD+ Android Development] neutronjeff:
FYI for anyone installing the latest Ovation LnOS 0226, after a full wipe using the latest TWRP in the experimental folder, the flash took unusually long, my opinion, but finally completed after a few minutes of no activity on screen.

In other words, don't panic, give it a few.
[Nook HD, HD+ Android Development] zspeciman:
I'm trying to upgrade from cm_ovation-ota-NMF26Q.161222. The twrp was always in zip format, so quick question the twrp-3.0.3-ovation.img, when asked "select partition to flash image" Boot or Recovery. Which one do I select?
[Nook HD, HD+ Android Development] mikeataol:
that is a recovery image... so you would flash the recovery partition....
[Nook HD, HD+ Android Development] andrerz:
Yes, flashing the new builds often takes several minutes, I think it hangs somewhere in the script as the progress bar finishes normally then it waits 3 or 4 minutes.

To flash the recovery image, I use the flashify app in the play store, very easy.

If upgrading from cm11, cm12, cm13 you need to do a clean flash i.e. wipe the data partition as well as dalvik cache and cache partitions. You'll need to reinstall your apps in that case.
[Nook HD, HD+ Android Development] memphismage:
I flashed the new lineageOS rom that you provided on my nook HD+ but it wont show the main screen its just black, its like i have no launcher installed or something, can get to settings from the top bar and the recent used apps button works, i am going to try to reflash it and see if that works.....reflashing did not work, I upgraded from cm_ovation-ota-NMF26Q.161222.zip build you provided if that helps any and I did not wipe my cache or dalvik before flashing either time
[Nook HD, HD+ Android Development] andrerz:
I think you need to wipe dalvik cache and cache whenever you install a new build.
[Nook HD, HD+ Android Development] neutronjeff:
I think the performance of the 0226 Ovation Lineage build is really great.

Thanks again [MENTION=4473900]amaces[/MENTION] !
[Nook HD, HD+ Android Development] kdejong2012:
LineageOS 0226 build is best build I've ever had on my Nook tablet. I did a factory reset, then wiped most everything else, then did a clean install followed by Pico GAPPS. Smoothest and most stable of any ROM I've tried.

Thanks [MENTION=4473900]amaces[/MENTION]! Excellent work.
[Nook HD, HD+ Android Development] pyoungworth:
How is the performance of lineage compare to AOSP?
[Nook HD, HD+ Android Development] kdejong2012:
I was going to compare the two and installed Lineage first since I always preferred CyanogenMod over AOSP. I'm happy with the performance so not even going to try AOSP.
[Nook HD, HD+ Android Development] NE0HP:
High memory usage on Nook HD+ (ovation)

Currently running LineageOS 14.1-20170227-UNOFFICIAL-ovation on my NOOK HD+ device and noticed very high memory usage and left hardly 100MB free which makes device slowing down. Attaching screenshot for more details! Anyway to fix and reduce memory usage or it's just me facing this issue?
[Nook HD, HD+ Android Development] digixmax:
My HD+ (running LN14.1 010417) memory stats shows 835MB average, 40 apps active in the last hour (even though I only use half a dozen apps, so most of the rest probably are installed apps auto-running in the background).
[Nook HD, HD+ Android Development] neutronjeff:
[MENTION=6518796]NE0HP[/MENTION], where is that 0227 ovation build from?
[Nook HD, HD+ Android Development] NE0HP:
It is actually lnos_ovation_ota_NOF26W_170226.zip build (which was earlier available under experimental folder but now available in ovation folder) but once flashed, it is showing LineageOS Version 14.1-20170227-UNOFFICIAL-ovation under settings --> about tablet.
[Nook HD, HD+ Android Development] joefidler:
For what it is worth I did some testing on the Feb 28 Build - LinageOS 14.1-20170228 Hummingbird on a Nook HD. For me its working very well.

As far memory as I am averaging 57% usage (of .89Gb). I don't have a lot of apps running however.

Android OS = 324Mb

Android system = 71Mb

System Ui = 46Mb

As far as some of the older issues:

* Auto-rotate works better but some apps still don't respond to a rotation.

* Never had the choppy sound issue so can't test that one.

* Still powers itself on about 30 seconds after a power down.

* The Wifi looses its settings if "keep WiFi on during sleep" is not set to "Always". In fact just restoring the tablet to an "Always" setting is enough to restore the WiFi settings and connect to a network. Is it an upstream issue?

Wondering what is the path to getting the Nooks as Official build status?
[Nook HD, HD+ Android Development] digixmax:
I dirty-flashed the 0226 build on top of 0104 build, the reboot seemed to take a really, really long time: the boot animation kept going on and on, seemingly forever. Afterward I realized that, unlike previous versions of CM in which the boot animation stops running after the system boot completes and the apps' "re-optimization" begins, the boot animation now runs until the whole system + app update process is completed. So don't panic if the first reboot after the upgrade flash takes a long, long time.
[Nook HD, HD+ Android Development] newhoa:
Hey, thank you very much for all your work! This is really awesome!

I'm coming from an Android 4.3.1 CM Rom, wiped everything, flashed lnos_ovation-ota-NOF26W.170226.zip, booted up fine. Then I replaced CWM with TWRP 3.0.1 which worked great. The Cyanoboot logo still pops up, not sure if this is normal?

I can't tell if it's just the tablet (it is quite old) but it seems a bit laggy, even more so than the 4.3.1 Rom I came from. I tried browsing youtube and button pushes, typing into the search took several seconds to respond to the key presses. Even sometimes going through the menus it takes an few seconds once you tap something. Scrolling works flawlessly, there seems to be no lag when scrolling up and down menus. The recording app crashed on me on first use, not that I'll ever use it.

Looking through the apps, especially when you show system apps, there seems to be a lot of things running that the Nook can't make use of. I'm not a developer, so maybe they're essential to the running of the OS. But there are a lot of Call Management, MMS, SMS, Mobile Data, Print Services, and things like that. Also the camera app since the Nook doesn't have a camera. Using CM12.1 on my phone, there are options to disable almost everything, and even edit the wake permissions, but here I can't disable almost any of these services, and the wake permissions seem limited.

I've only had it installed for the last day -- I had it asleep for 7 hours and it seems to be waking up a lot, looks like every 5-10 minutes or so. Android System is at the top of my battery usage, and it's kept it awake for 2 hours while the screen was off for 7. That was with restricted background data on, location and other automated services off, and no additional installed apps (no Gapps either) and no apps running. It was after the first boot, so I've since reset it and I'll let it go till tomorrow and see if it's any different.

Here is the battery usage of my CM10.1 Nook install. Sometimes I'll go very long periods without using my Nook, and the standby was incredibly good. 130+ Days of standby time, it never woke or anything when sleeping. Is Doze a part of Lineage or is that a special Google feature?

Anyway, thanks very much for all the hard work. It's really cool. I'm going to play around with this more. Hopefully input like this is helpful and if there's any more I can help test please let me know. Thanks again!
[Nook HD, HD+ Android Development] digixmax:
WiFi Connect Issue Following Upgrade to NOF26W.170226

Following the update to the LN newest build ovation-ota-NOF26W.170226 my HD+ started to have intermittent but frequent problem connecting to WiFi:

- The Nook takes much, much more time to connect, after coming out of sleep-mode or after I turn on WiFi access. But following a soft-restart it would connect nearly instantaneously.

- The device seems to be more prone to dropping connection.

These new problems occur both at home as well as at work, so the WiFi APs/routers can be ruled out as the problem source.

I would be interested in hearing if anyone else has experienced these same problems, and would appreciate any suggestions/pointers of potential fixes.
[Nook HD, HD+ Android Development] NE0HP:
Can ovation get new official TWRP 3.1.0.0 ?

Since this thread and unofficial TWRP both maintained by [MENTION=4473900]amaces[/MENTION] I just wanted to share this that, TWRP has released new TWRP version 3.1.0.0 to many devices and since [MENTION=4473900]amaces[/MENTION] (airend) is also official maintainer of TWRP for ovation on Team Win Recovery Project, I'm sure we will soon receive official TWRP version 3.1.0.0 to our device ovation....
[Nook HD, HD+ Android Development] joefidler:
I have to keep the WiFi on all the time (Keep WiFi on During Sleep = Always) or else it cannot access any of the network information (network list etc) so I do not see this issue much. If I turn WiFi off/on it mostly reconnects quickly (about 10 -15 seconds). Sometimes - not often - it can take about a minute, which maybe the same issue you are seeing. Build = LineageOS 20170228-hummingbird.
[Nook HD, HD+ Android Development] ajislav:
Thank you for the excellent post which nicely summarizes all the steps to use REPIT on our Nooks. Would you mind editinig it to include the information that

1) you will have to redo step 5 after every ROM flash (as written here https://github.com/Lanchon/REPIT/issues/56 )

2) that REPIT should work on 3.0.2 as written here https://xdaforums.com/showpost.php?p=71030164&postcount=38

Thanks
[Nook HD, HD+ Android Development] e.mote:
Thanks for the corrections. I edited as needed. However, I'm sticking with twrp 3.0.1 as that's the version available in amaces' folder, aside from 3.0.3.

Hopefully, amaces will still look in at this thread at some point and correct some of the obvious bugs/deficiencies mentioned here and earlier. The resize step could be made superfluous if it was included as part of the OS install.
[Nook HD, HD+ Android Development] NE0HP:
Official new TWRP version twrp-3.1.0-0-ovation.img is live now!

So finally official new TWRP version for Nook HD+(ovation) ---> twrp-3.1.0-0-ovation.img is live now. Those who is interested can download from this link https://dl.twrp.me/ovation/twrp-3.1.0-0-ovation.img.html

I've flashed it over unofficial 3.0.3.0 and it works perfectly fine but still waiting for new build so that can dirty flash using the newer one.

One humble request to [MENTION=4473900]amaces[/MENTION] to include/add a small feature in TWRP by adding option "Reboot in Recovery" from recovery itself.

Thank you.
[Nook HD, HD+ Android Development] jernyx:
In TWRP after you flash the rom you can go into Wipe > Advanced Wipe then select the system partition and press "repair or change file system." Doing this I was able to install OpenGApps nano.
[Nook HD, HD+ Android Development] newhoa:
Just an update on my post about battery life the other day on lnos_ovation-ota-NOF26W.170226, and the waking during sleep mode. It was the Wifi. Even though I hadn't set any accounts up or downloaded any apps, the wifi was still waking the device during sleep every few minutes. If I set Wifi to turn off when the screen turns off this doesn't happen, it properly goes into Tablet Idle mode.

It still is sluggish compared to my 4.3.1 CM10.1 from a few years ago. I thought it was only in the browser and apps, but even the UI is effected more than I thought. A high percentage of the time (60%ish) there is a several second delay after tapping. It makes things difficult because you're not sure if it registered so you tap again and end up somewhere you didn't want to be, then the same thing happens trying to get back.
[Nook HD, HD+ Android Development] e.mote:
[MENTION=6518796]NE0HP[/MENTION]: I flashed the 3.1.0. The new version works with REPIT.

[MENTION=8073543]jernyx[/MENTION]: Thanks for the info, which I've verified. It simplies the process a bit. I've updated the guide above.
[Nook HD, HD+ Android Development] ShapeShifter499:
What's the current reason why Hummingbird and Ovation haven't been added to the list of official supported devices on LineageOS?
[Nook HD, HD+ Android Development] rtarv321:
I have the same question as NEWHOA, POST 1718. Should the "cyanoboot" logo still show up after the updates?
[Nook HD, HD+ Android Development] mikeataol:
Yes, the NOOKs use a 2nd bootloader to bypass the stock Barnes and Noble software, and AFAIK this is still the same as was used years ago in the first versions of CM or other roms ported to the NOOK's

The Cyanoboot screens are the bootloader, not the boot or rom files that have been updated.
[Nook HD, HD+ Android Development] Tight Git:
If you've installed LOS then the cyanoboot logo does show. Sorry edited as I was thinking of the CM logo.

Apologies!
[Nook HD, HD+ Android Development] rtarv321:
I have installed LOS and the cyanoboot logo shows briefly before the Los logo begins. The cyanoboot has been showing since rooting & installing Kitkat several years ago. I originally used cwm before switching to TWRP. I'm not sure if that has any effect on the cyanoboot logo.
[Nook HD, HD+ Android Development] digixmax:
FWIW, a technical overview of the boot sequence used by the HD+/HD OMAP 4470 processor can be found at http://omappedia.org/wiki/Bootloader_Project.
[Nook HD, HD+ Android Development] mmnspeed:
What would be the battery life at which one should consider replacing the ovation battery?I am right now getting around 6+hours of screen on time with xodo app,while reading books.WiFi turned off.I have other devices to consume media on.Main purpose of nook being reading PDF texts,because of its screen size.

The screen on time is without WiFi and heavy usage.I guess it would go down a lot if I use an app like YouTube with WiFi on.
[Nook HD, HD+ Android Development] drmarble:
Just installed, replacing my old self-build cm-11. I preferred that to cm-12 and cm-12.1. I had to factory reset because of various settings changes but it is working smoothly. Netflix plays well. It is good for reading comic books and slowly browsing web pages. It works surprisingly well for a slow processor and a huge, high resolution screen.

Using pico gapps it would have fit without repitting and changing system size. Gapps and rom installed in one pass without resizing the partition in between. We have no microphone (right?) so pico has all the functionality I need.

Excellent work Andrei Măceș.
[Nook HD, HD+ Android Development] e.mote:
>We have no microphone (right?)

It does have a mic, hence my decision to go to nano, which entails REPIT. It's a big deal to be able to say words vs having to type them out. Moreover, I wanted to get rid of the deadweight factory ROM and reclaim the space anyway. Result: More space, more functionality.

>Gapps and rom installed in one pass without resizing the partition in between.

That may matter if there were frequent updates that the extra step becomes a chore. Realistically speaking, the Nook now probably gets an update every few months, if that. So it's a non-factor. In fact, I wouldn't be surprised if this is the last update for Nook. amaces' experimental folder stands empty.

>Excellent work Andrei Măceș.

Yes, thanks to amaces for sharing his work. With the latest ROM, the Nook works well enough. It's a great reader, can play 720p videos smoothly, and is a workable web browser albeit a bit slow. Most apps work. I also use the Nooks (I have 3) as wifi phones with GV and Hangouts.

Edit: Spoke too soon; looks like amaces' work is still continuing. Experimental folder has new AOSP builds.
[Nook HD, HD+ Android Development] rpadula:
just dirty flashed the latest experimental, and booted up just fine.

LNos Hummingbird
[Nook HD, HD+ Android Development] dbrickg:
Likewise, but lnos for ovation. Boots just fine. No problems so far. Yeehaw!
[Nook HD, HD+ Android Development] mmnspeed:
Regarding the aosp build,haven't used aosp in a while.Yesterday,before the lineage os build was up,I flashed the aosp build.I kept pattern lock on it and found out that it would get stuck at times while waking the device up from sleep.Have flashed the new lineage os build now,which is working flawlessly.

I am talking about ovation.
[Nook HD, HD+ Android Development] NE0HP:
Dirty flashed lnos_ovation_ota_NOF27B.170321.zip over lnos_ovation_ota_NOF26W.170226.zip and everything works fine except WiFi.

Anyone with new lnos ovation build facing WiFi issues.

In my case, on new lnos build WiFi doesn't automatically connect and have to manually connect each time.

On WiFi settings I tried changing "Keep WiFi on during sleep" from "Always" to "Never" and back to "Always" again but still it doesn't work.

Would appreciate if anyone can suggest any fix or work around to over come this issue or if it's a build problem then it's better to wait till new build is up!
[Nook HD, HD+ Android Development] rpadula:
i believe it's a build issue.

facing the same problems in my hummingbird.
[Nook HD, HD+ Android Development] joefidler:
Same here (170321 experimental build on Hummingbird) have to hit the Wifi setting button to get a connection - even with wifi active.
[Nook HD, HD+ Android Development] king200:
With mine, I try to turn wifi off and then on. Toggle shows on but no scan of WiFi. Takes a reboot to get WiFi to connect.
[Nook HD, HD+ Android Development] hideokuze:
Question: How do I get back to CWM so I can flash another ROM?

I flashed the latest AOSP and it keeps booting instead of loading CWM off of the SD card. I've tried reseating and rebooting the Nook HD several times, and each time I see the it load to the "android" loading screen after briefly displaying the cyanoboot flash screen.

I should have flashed the TWRP zip file first, but I figured I didn't want to brick the device before attempting to see if the ROM itself works. I'm getting phantom touches all over this AOSP and it's basically unusable at this point unless I can flash something else like CM.

EDIT: Disregard. I figured out what to do.

For anyone else experiencing this issue, here's what I did (using Linux):

1. I downloaded the sd-reco-hummingbird.img.xz file from amaces' NotreDame Box account.

2. I used gparted to delete all partitions off of my sd card.

3. I ran this command to write the recovery image to the sd card: xzcat -v sd-reco-hummingbird.img.xz | dd of=/dev/sdb

(NOTE: Replace /dev/sdb with your actual device, which can be found in gparted or by using the 'df -h' or 'lsblk' commands).

4. I inserted the sd card into my nook and started it up.

5. TWRP 3.0.1-0 loaded up =)

It was fun doing all of this at work by tethering a Raspberry Pi from my OP3 lol
[Nook HD, HD+ Android Development] neutronjeff:
Looks like [MENTION=4473900]amaces[/MENTION] pulled the new builds down.
[Nook HD, HD+ Android Development] hideokuze:
Yeah, I see that too now. Amaces had NOF27C up there but now it's removed.

I have to agree with the posters before me, the wifi seems to be broken on it though. I kept getting intermittent connections, and everytime my hummingbird slept it'd disconnect. Changing the settings to always keep wifi on during sleep didn't make a difference. So now I wiped and flashed back to NOF26W.
[Nook HD, HD+ Android Development] mmnspeed:
Is there any difference in ram management between the aosp and lineage os builds?I am using lineage os on other,more recent devices and it is consuming more than 1.5 GB on them.Wonder if aosp is better ,considering it has less features.If anyone has some idea,please do reply. I would switch to an older aosp build then.Thanks.
[Nook HD, HD+ Android Development] nux7osx:
Hi, maybe I'm being stupid here, so sorry in advance. Where is the link for me to download amaces' ASOP and Lineage builds? I can't seem to find a working link or anything here.

I understand the latest build is broken with Wifi issues, but at this point in my case, I could use anything that isn't lagging and unstable like build I'm using now.

Sorry if I'm being dumb again, thanks.
[Nook HD, HD+ Android Development] belfastraven:
Read the first post: at the end of the first paragraph, where it says "here" is the link to all of the builds. The AOSP and Lineageos builds for your device will be in the device folder. Brand new builds are often in Experimental--that means they are not necessarily thoroughly tested.
[Nook HD, HD+ Android Development] drmarble:
Save you the trouble of looking:

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww

Still, you should read much of this thread before installing. There are some tricks that are well described.
[Nook HD, HD+ Android Development] jernyx:
Also you should know the build that people are referring to with wifi issues was in the experimental folder for a day or so before being removed. As far as I can tell the current builds in the ovation and hummingbird folders have not been having the same problem. Wifi off on sleep and quick toggle have been working fine for me on ovation.