yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] mikeataol:
I saw the same thing

2 Ovations, one EXT4 has had no problems, one F2FS crashed within a few minutes of use, and wouldn't boot

logcat showed /data as a ReadOnly file system.

Edit: just remembered,

I had used this with no gapps for several days, even with /data as F2Fs

the problems only showed after I resized /system, and installed nano gapps
[Nook HD, HD+ Android Development] xecutionkrk:
while doing oreo 8.1 twrp encounters errors

error 7
[Nook HD, HD+ Android Development] mikeataol:
Did you update the recovery to the TWRP in damaces folder?

twrp-3.2.3-0-ovation.img

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

I tried attaching but it's too large
[Nook HD, HD+ Android Development] secretwolf98:
Ovation - Latest LineageOS 14.1 release

[MENTION=4473900]amaces[/MENTION], your latest release of LineageOS 14.1 for ovation isn't working. On the setup wizard... It freaks out towards the end. What I mean it freaks out, it glitches and it crashes the whole device.
[Nook HD, HD+ Android Development] twiztid_:
That's been happening for a while now. amaces mentioned that the cause is due to certain blobs (I think), and that updated versions would fix it but he wasn't sure of an exact ETA.

A workaround is to go into TWRP, Mount the /System partition with Write permissions, and go into the File Manager and delete go into the /System/Priv-App (I think) folder and delete SetupWizard.apk. This will let you skip the Wizard and go straight to the Launcher.
[Nook HD, HD+ Android Development] ST Dog:
I'm reminded how much I hate IP lawyers.

They almost never actually understand the IP they are dealing with.
[Nook HD, HD+ Android Development] bzz11g:
Any chance to see Android GO build for our device? it seems good for low memory Nook HD...
[Nook HD, HD+ Android Development] twiztid_:
It's been discussed before, but the majority of the improvements for Android Go have already been applied to our existing builds for a while now.

There IS a build of Android 8.1 in the Experimental folder, however the UI was a bit sluggish in the 09/04 build, and a bit better in the 9/14 build. I haven't tested the 10/01 build yet but in my experience amaces is pretty darn good at tweaking the settings to get as much performance as we can get out of our devices, so even if it's still a bit slow now in a few builds time it should be fine. There's a bit of distortion on the icon drag top bar due to the new DDK (I'm guessing it stands for Damned Donkey Kong, but I'm probably wrong), I *think* that only the icon image is wonky and the text is still fine.

While the 8.1 builds are in the Experimental folder, I used 9/04 and 9/14 builds for about 3 weeks total. And aside from a bit of a hiccup with the way Oreo handles installing APKs (You no longer 'allow unknown sources', but have to give permission to an app in order for it to install APKs), and rebooting always going into Recovery (a common problem that pops up frequently across all versions), I didn't have any issues relating to the ROM itself.

While I wouldn't recommend installing it as your 'default' ROM, so far I haven't seen anything that would prevent it from being used that way. Stability was a non-issue, battery life was fine (I used MicroG and Galaxy Store, I can't vouch for any GApps packages), and no issue with app compatibility once I figured out how to allow apps to be installed outside of the default file manager. I plan on trying the 10/01 build sometime soon, but with my luck amaces will have another build out by the time I get around to it.
[Nook HD, HD+ Android Development] mikeataol:
One thing about the 9/14 build ( I never tried the earlier one, will try the 10/1 today)

I found that If you unplug the charger cable while in use, and then replug it in, charging doesn't happen.

also the connectivity to a computer seems to be the same.

start the tablet connected and everything is fine, unplug it and replugging it in to a charger or computer doesn't work the way you would expect.

Neither is a big deal to me, I leave it plugged in 99% of the time, but it might confuse you why battery is being drained.

I'll test the 10/1 build and report back.
[Nook HD, HD+ Android Development] mikeataol:
===============

Running the 10/1 experimental build. full wipe . had to repair /system a few times manually in TWRP terminal (e2fsck /dev/block/mmcblk0p7 , answer Y to all... ) as it had inode issues that evidenced as an Issue 7 during the install.

Build seems fine, the USB strangeness and reboot means "reboot to recovery" still the only glaring things. Not sure what exactly was tweaked as I haven't asked amaces.
[Nook HD, HD+ Android Development] Nemesis1278:
Which repit did you use to resize? I got an error code stating that it was for a different device.
[Nook HD, HD+ Android Development] ipdev:
[MENTION=804003]Nemesis1278[/MENTION]

The current REPIT downloads.

All - hummingbird - ovation

General instructions. Link

A little extra space for Nook. Link

Note: Might be better to add the extra space to system instead of data.

I haven't had much time for my ovation lately, so I just used the default for now.

-factory=same-system=1G-cache=112M+wipe-data=same-ovation

When I have some time, I will remove the factory.zip and use the extra space for system.

or I might pull some from userdata since I have a 32GiB version.
[Nook HD, HD+ Android Development] Nemesis1278:
[MENTION=7280276]ipdev[/MENTION] thanks this worked really well. I was able to adjust the system size and get Gapps installed. I adjusted the system to about 2.5G probably more than I need but it leaves a good buffer.

[MENTION=4473900]amaces[/MENTION] Thanks for working on the Oreo. It is working pretty good for an experimental version. Although you may know this already here are things I noticed not working so far the file transfer over USB. The video works in youtube for the beginning but then the video stops and I only get audio. Probably a driver issue.
[Nook HD, HD+ Android Development] mikeataol:
I can confirm the YouTube issue, hadn't noticed it because I rarely use YouTube on this tablet.

Installed vanced YouTube and changing the Codec Override appears to work.

(Search xda for vanced YouTube, I usually use the "dark" option. )
[Nook HD, HD+ Android Development] ajislav:
no boot

Hi,

I have used the 9/14 experimental build (no gapps )on my ovation for some time and all was good. Then recently, when I turned it on, the boot proceeded directly to TWRP, where it is stuck on the TWRP logo ( I am on the 3.2.3 from the experimental folder). Now this happens on every attempt to boot. My guess is that this caused by data corruption.

1) any suggestions what I should do (e.g. a particular key combo during boot..)

2) I guess I need to boot from the SDcard and fix the problems. Any suggestions for an SDcard-based recovery or similar tool?

Regards

ajislav
[Nook HD, HD+ Android Development] ipdev:
It's been awhile since I made one.

I have three. Two CWM and a multi-boot.

Since the one I currently use is a muti-boot card, I think I made it from here. Link

Thanks to the links posted in the OP of this and the CM12 thread.

Looking at my card, I probably used [MENTION=5672278]belfastraven[/MENTION] 's files.

Save for digging back further, this how-to is also linked in the OP and is a very complete guide. Link

Granted you will probably want to use updated files.
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=4473900]amaces[/MENTION] has provided an sdcard recovery image in the ovation folder linked from the OP. If you want a zip of the necessary files instead , you can get it https://www.androidfilehost.com/?fid=24459283995300762. Still based on amaces work of course, just packaged differently. If you get the files from zip, write the mlo file onto the (clean) sdcard first. The rest of the order doesn't matter. I suggest you use the sdcard TWRP recovery to write the new TWRP recovery image and then use that to write the experimental rom. You can also use the sdcard recovery to do any fsck, reformatting , etc. that you feel is necessary.... before writing the new files. Before the nook became unusable, did you, by any chance, look at logcats or dmesg? I wonder what is causing this. Also, did you repartition the nook or are using the initial partitioning?
[Nook HD, HD+ Android Development] Wizkid:
Just hit reboot system within TWRP to boot into OS. Mine also reboots in TWRP when restarted....
[Nook HD, HD+ Android Development] amaces:
October Oreo Updates

I'm testing automatic system resize on latest AOSP builds. While I'm not ready to change partition layout (need to think about cache size, separate vendor, etc), lots of people already resize system, so hopefully it works well.

I empathize with everyone who runs into this particular bug; also have to refrain from using F2FS on my ovation. It's something about the MMC layer in K3.4, the buggy eMMC chips on some ovations, and the newer F2FS backports. For now, anyone testing my experimental builds should keep an SD recovery handy to reformat to ext4, whenever the bug happens.

Current builds have even newer F2FS backports, and I plan to rebuild recovery images with the same kernel. Maybe F2FS mileage on ovation will be better afterwards.

We mostly lost zRAM on the experimental K3.4 builds, so that's something that I plan to re-add. We did gain CMA, and other modern memory management features. Anyway, I'll look into the Go Makefiles again, but full Go builds do have their own trade-offs, and my goal is some middle ground.

Odd, have you selected the transfer files option from the USB notification?

I really hope that's different than the memory allocation issues we had in the past with old DDK. I only tested that HW-accelerated playback works, a couple of movies in Gallery, but no GApps yet. It's possible that increased memory pressure and YT's large allocations break DOMX, but we'd need logs and time to investigate. If you close YT and restart it, or say Gallery, does video playback resume? Also, are the new builds any better here?

Their issues were different. About unplanned recovery boots, please test current builds. I really thought that bug was fixed.
[Nook HD, HD+ Android Development] Nemesis1278:
[MENTION=4473900]amaces[/MENTION] I have chosen the files transfer from notification. I have also changed to mtp in developer options. Still no transfer of USB when in system. TWRP works fine for usb transfer. I am using AOSP 8.1.

I have started using vanced youtube and the video is working from there with the codec 9 settings. The video is a little jittery but it does play.

I do notice the system running smooth at some parts. For instance once XDA loads from app it the to work smooth. Going into settings is smooth.

I have restarted from Android system a few times and have yet to reboot into recovery unless I pressed the buttons down to get into recovery.

I just reinstalled Netflix and that is working again. It was not working at first I think since I didn't wipe the previous install I just installed 8.1 on top of 7.1. This may also be why transfer over USB is not working. I may try a full wipe and see if that fixes the issue.
[Nook HD, HD+ Android Development] Nemesis1278:
So when I closed youtube and cleared it from recent apps and then restarted it. It seemed to play videos again. I have attached the catlog. around 11:28, 11:29 is when the video from youtube crashed.

I have started to notice that the system is restarting randomly.
[Nook HD, HD+ Android Development] ajislav:
ovation recovered!

Thank you [MENTION=5672278]belfastraven[/MENTION] and [MENTION=7280276]ipdev[/MENTION] for your tips for the sdcard recovery image. I have used the one built by [MENTION=4473900]amaces[/MENTION] and successfully recovered my ovation. Surprisingly, it was the CWM recovery using which I was able to format /data. Both 2.8 and 3.0 TWRPs included in the image failed to handle my corrupted /data and refused to load (both were stuck on the initial screen with a flicker about every minute or so). In CWM I had to use the ¨format /data and /data/media ¨ (i.e. a a true format) which converted the /data partition to ext4.

Happy my ovation is alive, I have upgraded to the October08 release and was successfull in installing OpenGapps pico (I have resized /system)
[Nook HD, HD+ Android Development] ParadoxGBB:
Random reboots

First off, thanks so much everyone for sticking with the Nook HD (especially amaces). The longevity of this device is truly amazing. I'm going to be hard pressed to find something to replace it with when it finally bites the dust.

I attempted to upgrade to 8.1 yesterday (aosp_hummingbird-8.1.0-20181008.zip). For me, it doesn't appear to be stable, causing random hangs and then reboots, about every 1-2 minutes. Attached is a dsmsg I was able to grab but it may not have the problem captured, the FS errors are probably side affects.

During initial setup I also saw a few complaints about google play and other services stopping, which usually isn't a good sign... I attempted to just reflash Oreo without Gapps and I think things might have been a bit more stable, but it was hard to confirm. I tried to install a different date release of pico gapps and then tried Nano, but that didn't provide different results.

My basic steps:

1) Updated TWRP to 3.2.3.0

2) Wiped

3) Ran RePit with defaults (1G system), realized I had data and system partitions as f2fs and converted, ran again

4) Resized, confirmed size, wiped again for good measure

5) Flashed Oreo

6) Flashed addonsu-15.1

7) Flashed Gapps pico

I reverted back to 7.1.2 and things are real stable (and much faster --- new installs seem to get a boost).

I'll definitely try again for a future Oreo build, but if there's something I did wrong that'd be great for me to know.
[Nook HD, HD+ Android Development] Nemesis1278:
[MENTION=4473900]amaces[/MENTION] so I turned off auto orientation/rotate and the rom seems to be stable now. It is not freezing/restarting randomly for a couple of days now. Hopefully this info can help.
[Nook HD, HD+ Android Development] amaces:
Pretty odd, since it never happened on a plain Oreo install (no GApps). I now wonder if increased memory pressure interferes with the Tiler or VRAM allocations needed during screen rotation. This event completely crashes UI on my GApps-less Pie builds, so maybe current Android expects much more room for these UI operations.

That might be due to CWM not supporting F2FS, and not attempting to mount the broken filesystems. Whatever corruption happens, it results in an infinite loop upon mount, but only TWRP would run into that. Still, it's possible to format manually even under semi-functional TWRP with make_ext4fs.

Your steps seem fine, except maybe that my current builds are made to work with addonsu-14.1-arm.zip, not the 15.1 stuff, which wasn't available when I was porting my changes in frameworks. Still, that wouldn't explain your crashes, but I do suggest a clean ROM-only install to test basic stability. I'm mostly testing browsing, video playback, and other basic operations for now. I suspect things go downhill fast with increased memory pressure.

Sadly, it's likely Nougat on the legacy 3.0 kernel will remain the most usable builds.
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION], when can we see another LineageOS 14.1 build again for our Nooks?
[Nook HD, HD+ Android Development] KostasR:
Switched from lollipop. Latest CM 13 made my tablet usable finally! Thanks a lot.

sent from my ovation
[Nook HD, HD+ Android Development] amaces:
That's the part where you either use a more robust toolchain for ROM (e.g., UBER, SaberMOD will finish compilation), or you start editing the flags that I changed. Sometime it's the Graphite stuff, or maybe the vectorization, alignment flags, etc. Basically, a lot of detective work, followed by carefully testing supposed improvements, but it sounded like you were itching for it ;)

As all current builds are userdebug (and SELinux Permissive), you can stick with CM SU (enabled in Developer options). As always, AOSP doesn't come with any SU, and if you flash SuperSU, systemless probably doesn't work with this kernel, so you need the old style beta (2.52?).

Glad it worked eventually; no idea why you had to jump through so many hoops, certainly not without TWRP logs. The device backup selection happens in Setup Wizard, assuming you have any linked to your Google account. If the Wizard doesn't pop up during first boot, you need to flash GApps on a clean system, immediately after wiping/before first boot.

Yup, a decent amount of Nook-specific improvements cobbled during the past week.
[Nook HD, HD+ Android Development] KyJelly69:
I am flashing gapps to a clean system right after flashing rom before rebooting. So far I have tried pico. currently trying nano. anything else is too big to fit in system. from open gapps project.
[Nook HD, HD+ Android Development] amaces:
Not sure that pico OpenGApps includes all that support, but nano definitely does, so maybe that's the issue. No reason to use packages larger than nano since it contains support for everything Google once you install the appropriate apps in user data. Still, you can customized micro, mini, etc packages with a configuration file, should you need to fill /system to the brim.
[Nook HD, HD+ Android Development] KyJelly69:
Having same issue with nano.

Edit: tried Slim_zero_gapps.BETA.6.0.build.0.x-20151228-1845 also, same issue.
[Nook HD, HD+ Android Development] neutronjeff:
Nano worked fine for me. I flashed in the same TWRP session as the ROM, as usual. (Ovation, clean, cm13)
[Nook HD, HD+ Android Development] smileyint:
Hi Amaces,

The latest CM13 did not worked also and I had attached the logs. Thanks. The Readme.txt is showing the type of wifi connection that I used.

Bluetooth cant pair my garmin vivofit in this release. Error "Can't communicate with vivofit." Will try other Bluetooth devices when I have a chance. Pairing with my phone is ok though.

Great work mate.

Cheers,

BP
[Nook HD, HD+ Android Development] mikey williams:
Dirty flashed cm_ovation-ota-MMB29T.160110 over the previous one and then the open_gapps-arm-6.0-nano-20160105.

No problems at all and it definitely feels snappier.
[Nook HD, HD+ Android Development] KostasR:
60 fps video youtube don't work in MM build. Lollipop build used to have this problem too.
[Nook HD, HD+ Android Development] acr123:
I also dirty flashed the 1/10/16 MM build over the previous build w/o changing gapps and I agree it does feel slightly more responsive.

Al
[Nook HD, HD+ Android Development] KyJelly69:
nano works I just don't get the option to install the apps from my previous device. system setup runs but after logging into gmail it seems to just skip this step.
[Nook HD, HD+ Android Development] williamlaw:
update TWRP to 2.8.7.5 and install CM13 or AOSP, but it keep loading LOGO only....

Please advice.

Thanks !!
[Nook HD, HD+ Android Development] vinceweis:
It takes about 5 to 10 minutes on first boot. Did you wait long enough?
[Nook HD, HD+ Android Development] extrem0:
Clean install cm13 + gapps then delete using twrp file manager the following file (you may need to mount system partition):

/system/priv-app/CyanogenSetupWizard/CyanogenSetupWizard.apk

Don't boot unless you've done it.
[Nook HD, HD+ Android Development] williamlaw:
i was waiting for over 30 mins ....

Any things I missed ?

1) Flash TWRP

2) Wipe cache, D cache, system

3) flash rom

4) flash gapps

5) flash super-su

6) wipe cache, D cache

7) Reboot
[Nook HD, HD+ Android Development] vinceweis:
What TWRP version? Use the one amaces provides in his files. If you flashed a new TWRP, you should reboot into recovery, then install rom, nano gaps, super su 2.52. I don't wipe again after that. Just reboot to system.
[Nook HD, HD+ Android Development] KyJelly69:
That worked amazingly. thank you so much. MAybe that should be done by default?
[Nook HD, HD+ Android Development] neutronjeff:
The restore function was working on the previous LP CM version. During and after installing (without removing that .apk) I didn't see a way to add my CM account in the MM build. Does that have something to do with it?
[Nook HD, HD+ Android Development] KyJelly69:
what's the deal with not being able to wake the device with either the power button or the "U" button? Unless of course it is plugged in.

Edit: weird, just rebooted and now it works. ???
[Nook HD, HD+ Android Development] williamlaw:
I used TWRP 2.8.7.5.
[Nook HD, HD+ Android Development] IndiaBhai:
Hi amaces, thanks again for your great work on the device! I wanted to add my experience here as well. I'm receiving the same constant crashes every minute or two. Sometimes it happens when I'm using the device, it lags for a second and then restarts (soft reboot). Other times, it'll just keep on doing it by itself. I tried the auto-rotate thing, and it fixed stability for maybe about 15/20 minutes, but then the problems returned. I followed the same steps, except that I additionally nuked the factory image and did not install addon-su. Do you want us to reflash without gapps? On a side note: standby battery seems awesome haha; I've left it in TWRP for about 2.5 days now.

Two other things I noticed: From TWRP (your latest), I used to be able to do a complete shutdown of the device. In fact this was the only way I could do it, because all the ROM's have had the weird shutdown bug. Shutting down from TWRP now also causes the shutdown bug, where it never shuts down, because it just starts up again about 10 second after the screen goes dark.

The other thing is that on Google Play, the icon for the Nook used to show up next to my device name when I used unlegacy (I assume this is because the nook has been Google Play Certified by B&N on the stock ROM), but it didn't show up when using this ROM. Nothing major, just thought it was an interesting change.

EDIT: Flashed the ROM without Gapps, and I am still getting the hangs + reboots. Let me know if we can provide you anymore information!
[Nook HD, HD+ Android Development] qwert940:
Is there a way to use Nook HD in OTG host mode and charge it simultaneously? I tried to look for some ideas but I could not find a solution.
[Nook HD, HD+ Android Development] twiztid_:
Is there any way to remove the 'built-in' root/su and replace it with Magisk? My cable co's TV app (which use to only check ADB) is now checking for super user binaries, and from my searching on the matter Magisk can only hide it's own su.

I could be mistaken on some things or some information, I never delved too much into root/su... it's always 'just worked' for me. The TV app works if I rename /sbin/su to something else but it fails even on a clean install without Magisk, which leads me to believe that it's the built-in root.

Would uninstalling Magisk, deleting the su-related files, then reinstalling Magisk (systemlessly?) work?
[Nook HD, HD+ Android Development] ipdev:
If you rooted with magisk, uninstall and restore the stock boot image.

As far as removing su, or bits left behind, check here. Link

Normally I would do a clean install; Wipe, Flash rom, UPDATE-unSU, Magisk, Gapps, anything else and reboot to system.

If you are not passing due to SafetyNet, there are options to try using magisk.

Did you try hiding apps or magisk manager?

Side note: Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory, since some apps search for this directory and used it to determine if the device is rooted. If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
[Nook HD, HD+ Android Development] belfastraven:
No, I don't believe there is. In OTG mode the nook is providing current to the attached device I think it would require hardware changes to the nook (like another USB port ...). The Nooks are actually missing a physical pin in their rather strange usb sockets that would allow this automatically, by the way, which is why [MENTION=3654172]verygreen[/MENTION] wrote an app that tells the system that the connection has been made.