yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
That actually is an interesting question. While some blobs are needed at build time, they could be stripped out before packaging. Of course, the system would be unusable without re-adding them before booting. Still, the main legal issues remain; a separate package would still run afoul of previous commitments. Also, it'd irrational to burn lots of bridges and good will, just for some updated blobs.

Everything not GPLed is usually closely guarded IP, especially in GPU land… ImgTec doesn't build blobs; they give the integration package to certain parties under strict NDAs. Our main issue is that nobody really builds the userland stack for our particular hardware. Prebuilts are readily available for their current products, but those are useless to us.

Anyway, the likelihood of new UM blobs (and Oreo) is much higher now. Hopefully, there will be good news in a couple of weeks ;)

We've always had a critical bug with changing it once BFQ is enabled. This only happens on the 3.0 kernel; 3.4 is fine, if we ever switch to that. Unfortunately, we need BFQ for its CGroup integration, and IO scheduling.

Unfortunately, this is part of those GFX starvation issues that we suffer mainly on ovation. New DDK will fix them for good.

These shouldn't happen, at least they don't on AOSP. Have you tried current builds?

Hmm, the fact that they've started happening on UA builds as well points to security patches merged recently. I still use last October's security level in 7.1.2_r36 for my personal builds, and I haven't encountered these issues.

Unfortunately, the 8GB eMMC acclaim has lower specs (half the memory, etc), and there hasn't been much effort to make it work. It's probably not usable on modern Android, even if it booted.

What about the AOSP builds? Also, have you tried clean install?

They should work, but you need to resize system after every flash to access the whole thing. Lineage builds should have support to do this automatically, but it needs to be done in recovery with AOSP.

I'll look into that. The UA device trees have slightly different Wi-Fi overlays than my personal builds, and I have yet to fully resolve bugs with the newer WiLink drivers. Oreo work will probably force me to look at them again, but the priority is new DDK for now.

It's safe. The experimental folder is more of a staging area for things that I'm unsure about, or haven't personally tested.
[Nook HD, HD+ Android Development] ifGeny:
My Tablet is freezes while switching off :(
[Nook HD, HD+ Android Development] ST Dog:
Release of the blobs (binary objects) shouldn't matter. Not saying release the IP used to build the blobs.

It's no different than the stuff already released.

I just don't see what they would loose. Especially with such old, obsolete hardware.

Hoping for the best then.
[Nook HD, HD+ Android Development] twiztid_:
The problems haven't happened to me on any AOSP build, and I've tried almost all of them. And UnLegacy builds seem fine, but I've only tried a few due to the battery seeming to drain while sleeping.

Glad to hear about the possibility of new blobs and thank you for continuing to support the device, amaces!
[Nook HD, HD+ Android Development] nmyshkin:
I did a survey of various ROMs beyond CM 11 on the 8 GB model: https://xdaforums.com/nook-tablet/general/how-to-cm-11-8-gb-nook-tablet-bntv250a-t3667555

All really need to run GApp-less (you can use microG and the Yalp Store as an alternative) but the most satisfying experience for me (after running CM 13 for awhile) has been CM 11 without GApps (and using microG but with the PlayStore app).

Choosing older versions of apps also helps a lot since so many tend to become really bloated in later versions and demand more and more RAM and CPU that just isn't in that hardware.
[Nook HD, HD+ Android Development] hacknoob:
Thanks for developing these builds! I have used them successfully for a couple of years. I'm having some difficulty now, getting past the Checking for updates screen on the AOSP build.

I have recently initiated a clean system install of the latest AOSP build using the steps listed on this thread: https://xdaforums.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810

I boot from the SD card created from sdcard-reco-ovation.img.xz from amaces' repo, and install the following zip files from the repo, in order, from TWRP:

- twrp-3.0.1-0-ovation.zip

- aosp_ovation-ota-N2G48H.180711.zip

- open_gapps-arm-7.1-pico-20180731.zip

It all seems to work well, up through:

- Welcome to your Nook HD+ => I select: Set up as new

- Select wireless network => I select the appropriate network and enter credentials - the screen indicates that the Nook is connected to the network

- Checking for updates =>

Stuck indefinitely

- I have even let the Nook attempt to update overnight with no luck

I have successfully bypassed this using the steps from this thread: https://xdaforums.com/2015-moto-g/help/reset-stuck-checking-updates-t3571496

(On the TWRP Terminal: echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop). However, using this method I cannot get the Nook logged in with my Android account to get gapps to work. I tried to add an account, but it would only allow for setting up an email account, not a Google Play account.

I have also attempted to get this to work at two different places (different wireless networks) with no luck. I have also attempted to use an earlier version of AOSP aosp_ovation-ota-N2G48H.180319.zip, but the same behavior exists.

Thanks in advance for any assistance you can offer!

UPDATE - Nook HD+ up and running!

I tried again and this time installed lnos_ovation-ota-NJH47F.180713.zip instead of aosp. The Getting Started pages for LNOS were brutal - lots of crackling on the screen (and completely blank screens) once I got to the page requesting permission to use info to improve LNOS; after that all I could do was hit the bottom right corner of the screen rapidly where the NEXT button appears (it occasionally flickered into view). Somehow the intro was completed and LNOS became operational.

I did have to manual set up my Google Play account under the Setting menu. Setting it up was a bit clunky as well, and had to try twice, since Google had crashed.

I'll work with the new system for a few days to see how its performing.
[Nook HD, HD+ Android Development] l33boy:
Latest build has solved everything

Hi peeps, just like to say that installing the latest recovery & lnos_ovation-ota-NJH47F.180713 with Gapps micro has made my HD+ 16GB very usable.

The reboot wifi issue has now gone, it now remembers my wifi and connects + holds perfectly

Apps appear to work at a good speed, certainly no hang-up's there.

Battery drain seems to be OK, will update if not.

Brilliant work :good::good:

edit:

I also (previously) re-partitioned using this post:https://xdaforums.com/showpost.php?p=71387219&postcount=1722
[Nook HD, HD+ Android Development] drmarble:
Andrei Măceș

I am still impressed by the work you are doing on these devices. I do hope for success in getting oreo running. I assume you know about the publicly available ti code at: http://review.omapzoom.org/gitweb?p...e;f=jacinto6;hb=refs/heads/d-oreo-mr1-release

It seems to contain the ddk source 1.17 in the sgx.tgz file. I expect that I am (it is) missing something important. It only contains the POWERVR_SGX544_116.so files and I think we need a different version (SGX540).

When I built for acclaim I had to use the unlegacy kernel code because your 3,0/acclaim branch doesn't compile because of wifi driver errors. It runs just fine, but not much different from my stockish lineageos version. My emmc is dying on mine (block 679) and it spends most of its time in iowait so I mostly just build for this out of curiosity, I take a similar to my Encore builds; it isn't really usable but 14.1 on such an ancient device is a fun challenge.

I do love this on my HD+. It makes the device into a great comic book reader and video watcher. Netflix even updates when you set selinux to enforcing (adb shell setenforce 1). Its speed makes it somewhat limited for web browsing. I like it so much that when my screen stopped reading touches I bought another.

Keep up the good work. Thanks for all you are doing.
[Nook HD, HD+ Android Development] mmnspeed:
One major issue that I've encountered in these ROMs is that WiFi direct doesn't work.I flashed the new build based on lineage os for ovation today.Surprisingly the WiFi direct worked once,I could change the name of my device in the WiFi direct settings as well.However the process failed finally and now it is non functional.One ROM that I remember having functional WiFi direct is the jellybean 4.2.2 official build.If anyone has a workaround,please share it.I am willing to provide additional info or logs if it might help resolve the issue.The functionality eases sharing between devices especially if you use a file explorer like fx that has a WiFi direct option in built [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] twiztid_:
Anyone know how to install 7.1 after you've had 7.1.2 installed? I get this error even after a full system wipe:

E3003: Can't install this package (Thu Apr 27 14:08:23 EDT 2017) over newer build (Thur Jul 12 11:54:57 EEST 2018).
Updater process ended with ERROR: 7

----------

The workaround that I know of is to turn wifi off then back on, you can then click your access point name and re-enter your password to connect.

I thought there was a more "permanent" fix, something like turn wifi off and reboot after that wifi should work as normal, but I can't find it or figure it out myself.
[Nook HD, HD+ Android Development] ST Dog:
That's not WiFi direct.
[Nook HD, HD+ Android Development] twiztid_:
Thanks, that did it.

I r gud at reeding :silly:
[Nook HD, HD+ Android Development] ElsaReyes:
Yes hi, I'm hoping someone can help. I've been on the tab s for several years now. But it broke and it's gonna be awhile till I can have it repaired, so I'm going back to my Nook HD+ during that time.

I have TWRP as my recovery and I've flashed the newest nougat Lineage and Open Gapps 7.1 Pico.

Everything seems to be working fine, except for my wifi, the speeds are extremely slow, like to the point where it takes 5 minutes to download a 7 mb file.

Does anyone know what the problem may be? How I might fix it?
[Nook HD, HD+ Android Development] pcspecialistpdx:
My HD+ powers back on about a minute after I power off. Doesn't matter if it is on the charger or not. I've tried every "fix" I could find with no luck.

I tried aosp_ovation-ota-N2G48H.180711.zip, lnos_ovation-ota-NJH47F.180713.zip, and lineage-14.1-20171216-UNOFFICIAL-ovation.zip. I tried several versions of TWRP (as suggested), I even tried replacing TWRP with CWM.

If I reboot (from Lineage or AOSP) into recovery/TWRP and try to power off, it does the same thing, but, if I boot into recovery (using the 3 buttons), power off stays off.
[Nook HD, HD+ Android Development] exhausted2:
I've experienced the same usage pattern. To quickly unlock the tablet, tap the lock, the text switches to "Device will stay locked until manually unlocked" then swipe up. Works 100% of the time.

I think that feature functionality is there to prevent accidental unlocking.
[Nook HD, HD+ Android Development] bruman:
Thanks for the tip. I'm experiencing the same thing.

I try to shut it down, boots right back up.

Reboot to TWRP, shut it down... Boots back up.

Not looking to drain/kill my HD+ by having it forced to be on 24/7 because it won't shut down. Kind of sad wanted this to be my daily rom but if I can't shut it down without going through some hoops I don't see how I can.

Are there any fixes?
[Nook HD, HD+ Android Development] Zippy Dufus:
A workaround is a "hard shutdown" which is to hold the power button down until it shuts off.

Works for me and I have never had any deleterious effects. Normally, though, my 5 year old HD+ is always on and the battery still seems OK.
[Nook HD, HD+ Android Development] bruman:
It's weird that it's happening when I shut down from TWRP too is it not? Must be a kernel or a boot image issue?

Surprised no one has figured out and fixed this issue yet, seems pretty imperative to be able to shut down your device :)

Thanks for the tip I wonder if I can add a "hard shutdown" option on my rom via button click or something. Still hoping for a fix.. fav nook rom by far besides this really annoying issue.
[Nook HD, HD+ Android Development] fanoush:
For me it helps to turn off wifi before shutdown. Then it stays off.
[Nook HD, HD+ Android Development] drmarble:
I usually leave mine on and charging. The battery life is good so it can go 10 days without use without charging. If I want to turn it off, I do so from TWRP.

I just checked, and turning off wifi before shutting down didn't work. It rebooted again after about a 1 minute delay.

I will look at the code. I fixed the shutdown for the little brothers acclaim and encore. Maybe similar methods will work here. I had to write a particular string to special partition. With some crucial skipped blocks at the beginning. It was somewhat awkward, probably more so with selinux.
[Nook HD, HD+ Android Development] Zippy Dufus:
Broken build

Hello,

Has anybody tried to build this lately?

I'm getting the following errors.

...

CC init/version.o

LD init/built-in.o

LD .tmp_vmlinux1

/home/android/prebuilts/gcc/linux-x86/arm/arm-eabi-7.2/bin/arm-eabi-ld: error: no machine record defined

arch/arm/mach-omap2/built-in.o: omap_gcxxx.c:function usb_musb_init: error: undefined reference to 'omap4430_phy_init'

arch/arm/mach-omap2/built-in.o: omap_gcxxx.c:function usb_musb_init: error: undefined reference to 'omap4430_phy_init'

drivers/built-in.o:rpres_dev.c:function omapdss_dsi_display_enable: error: undefined reference to 'omap_is_board_version'

drivers/built-in.o:rpres_dev.c:function omapdss_dsi_display_enable: error: undefined reference to 'omap_is_board_version'

drivers/built-in.o:rpres_dev.c:function omapdss_dsi_display_enable: error: undefined reference to 'omap_is_board_version'

drivers/built-in.o:rpres_dev.c:function omapdss_dsi_display_enable: error: undefined reference to 'omap_is_board_version'

drivers/built-in.o:twl6030-usb.c:function twl6030_usb_worker: error: undefined reference to 'omap4430_phy_no_suspend'

drivers/built-in.o:twl6030-usb.c:function twl6030_usb_worker: error: undefined reference to 'omap4_charger_detect'

drivers/built-in.o:twl6030-usb.c:function twl6030_usb_worker: error: undefined reference to 'omap4430_phy_no_suspend'

make[1]: *** [/home/android/kernel/bn/omap/Makefile:901: .tmp_vmlinux1] Error 1

make: *** [Makefile:134: sub-make] Error 2

make: Leaving directory '/home/android/kernel/bn/omap'

[ 12% 4389/34185] bc: libclcore.bc <= frameworks/rs/driver/runtime/rs_sample.c

...​

I see a commit after my last successful build which may have something to do with this: https://github.com/airend/android_device_bn_common/commit/24fd8cbf12dc318ba9b186e93d6f9aa8d77cbf85

== EDIT #1 ==

Doesn't appear to be the commit mentioned above. I reversed it and still have an issue. Maybe my nonstandard toolchain is the culprit. Investigating ...

== EDIT #2 ==

Same problem with a straight, unadulterated build using the default toolchains.
[Nook HD, HD+ Android Development] drmarble:
Our dear maintainer, Andrei Măceș (airend) fixed this today: https://github.com/airend/android_device_bn_common/commit/dee51f6349c5f71337451a1a5342fa23efbdf639

Just resync the source and rebuild.

I am still anxiously awaiting the revised ddk version and a working go variant for this tablet. 16.0 would be nice but 15.1 would still be great.

Thanks for all the development on this.
[Nook HD, HD+ Android Development] fanoush:
I have two hd+ tablets, one with lnos, one with aosp. The one with AOSP N2G48H 180212 stays off for many minutes, just tried twice. I'll keep it off over night just to verify. The one with lnos did power on like you said.

However my issue with both nooks and both recent roms is that I get some phantom touch(es) always when resumed by power button and then first real touch is also wrong and then it is ok. Two different nooks bought in different years, one 16, one 32GB. Is it just me? I don't use lock screen so maybe people don't notice this so much with lock screen on?

EDIT: Now I tried with AOSP again and kept wifi on and indeed it powers on again after few seconds.
[Nook HD, HD+ Android Development] dbrickg:
lnos ovation 180713 zip

i know i'm way behind the times, but i just noticed there's an lnos ovation 180713 zip and a twrp 3.2.2-0 img. i dirty flashed both of them over an earlier lnos installation, and my hd+ seems to be quite happy with both of them.

thanks much, again, amaces!
[Nook HD, HD+ Android Development] Zippy Dufus:
Good build!

A saw that commit quickly show up and it is now building normally.

Thank you [MENTION=4473900]amaces[/MENTION] for the swift response!!

== EDIT ==

The build completed and was bootable. Appears to be working fine. Thanks again!
[Nook HD, HD+ Android Development] secretwolf98:
Thank you [MENTION=4473900]amaces[/MENTION] for Android 8.1.0 Oreo. :)

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/24717651525
[Nook HD, HD+ Android Development] fanoush:
Verified and it is not good, it stayed off for like half an hour at least (maybe more) but after I went to bed I noticed bright light and it powered itself on spontaneously when just lying on the table. But still turning off wifi affects it somehow but probably is not the single source of wakeups.
[Nook HD, HD+ Android Development] xMandy:
Great! Will lnos for ovation follow? :confused::good:
[Nook HD, HD+ Android Development] ST Dog:
I'm sure it will in time.
[Nook HD, HD+ Android Development] secretwolf98:
I would think so.
[Nook HD, HD+ Android Development] drmarble:
I flashed 8.1 using the 3.2.3 twrp. It works. No crashes. Since I am coming from LineageOS, I did a factory reset and formatted /system. I didn't install gapps yet. I did sideload some apps and they seem to work fine. Wifi connected right up. The recent app shows corrrectly proportioned images. No more distortion. dmesg doesn't show any interesting errors. Logcat is spammed with :

09-05 00:11:14.460 162 195 E IMGSRV : :0: DeferFlushOpWorker: Timed out waiting for ops to flush

09-05 00:11:16.312 252 1782 E IMGSRV : :0: DeferFlushOpWorker: Timed out waiting for ops to flush

Most importantly, PerfectViewer allows me to read my comic books. That is my main use for this tablet.

I am very impressed.

Thank you Andrei Măceș, a.k.a. airend, this is great work.
[Nook HD, HD+ Android Development] hemeboy:
Also flashed 8.1 successfully; however, there was not enough space to install pico open gapps 8.1; any suggestions ?
[Nook HD, HD+ Android Development] drmarble:
Some years ago I flashed a zip that enlarged my /system partition. It is natively supported by airend's lineage builds. I don't recall the thread. I'll look...

Found it:

https://xdaforums.com/nook-hd/development/nook-hd-repit-enlarge-data-partitions-t3503615

I even switched data to f2fs but it really isn't needed.
[Nook HD, HD+ Android Development] belfastraven:
Also doing a factory reset and formatting system, on hummingbird, I had one slight problem. I had to change the partition identifier in the block_image_update command to /dev/block/mmcblk0p8 -- I have no idea why, since i could see the symlink to the "byname/system" that was was there originally, but kept getting an install failure from the block_image_update command.

Using the original partiioning scheme of the device, I could not get pico gapps to install even removing several apps with a .gapps-config file. -- I was about 92M shy of having enough space, just fyi.

The system will actually shutdown now without restarting--a feature of the 3.4 kernel. Haven't had a chance to test USBOTG yet.

Once again kudos to [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] twiztid_:
I've found that Gapps is just too bloated to work well on the Nook. Switched over to MicroG and been happy since: https://microg.org/download.html

Copy Services Core (com.google.android.gms) to /system/priv-app/ and reboot.

Install Services Framework Proxy (com.google.android.gsf) and Store (com.android.vending) normally.

Install Aurora Store https://xdaforums.com/android/apps-games/galaxy-playstore-alternative-t3739733

If you have any issues, try moving Store (com.android.vending) to /system/priv-app/ and reboot.
[Nook HD, HD+ Android Development] nmyshkin:
Depending on the remaining system resources, you might be able to run the actual PlayStore app with microG. That's what I ended up doing on an 8 GB Nook Tablet running CM 11. Works fine, but you may not be able to purchase apps.
[Nook HD, HD+ Android Development] zspeciman:
Big thanks [MENTION=4473900]amaces[/MENTION] for continuing supporting these devices. On a nook hd+, I've also done a factory reset, and run into the same no space left error when installing pico as mentioned above. Despite having a gapps-config file, it didn't seem to help, as it has in the past. I wonder if there is a gapps-config file that is more complete in excluding stuff that are not needed. The MicroG requires appears to require more steps, and is definitely an option. But open gapps pico with the exclusion list seem so much easier. Lets hope someone out here can figure something out.
[Nook HD, HD+ Android Development] belfastraven:
I have been playing with this a bit, but have not been successful yet. it seems that google core services are more than 100M. I image if one used repit to increase the size of the system partition, one could install core services. I wonder how much smaller a userdebug build would be than this engineering build. Probably it would still not give us enough space.

I have tested USBHost switcher, which works fine with an older Dell mouse and a Sandisk flash drive.

The build seems a bit zippier than AOSP nougat, testing with a couple of apps I've sideloaded .
[Nook HD, HD+ Android Development] zspeciman:
Belfastraven, I have a question. Without google play, I understand you have to sideload apps, but how do you install them? ES explorer I recall lets you install apk, but how do you get ES explorer app or similar apps installed without google play. Maybe I'm missing something. Does twrp or any built-in aosp feature lets you install apk?
[Nook HD, HD+ Android Development] drmarble:
I just clicked on the .apk file from the stock built in file manager. It installed them. I had to tell android that it was OK for file manager to install.

You can use adb install myprog.apk or adb install multiple *.apk.
[Nook HD, HD+ Android Development] twiztid_:
Does anyone else on 8.1 have trouble installing some/most APKs?

I'm unable to get it to install the Amazon store and Plex/emby players as well as a few others I've tried.

I did get an older version of MiXplorer to install, but not a new version.
[Nook HD, HD+ Android Development] belfastraven:
I didn't have a problem with the 3 apps I initially installed, and I just did mange to install the Amazon store apk with no problem. Are you getting any message in logcat when these apks don't install?. What happens when the install fails? I have had an issue where no app would open and stay open, but clearing cache and dalvik and restarting fixed that for me.
[Nook HD, HD+ Android Development] belfastraven:
aS [MENTION=4190710]drmarble[/MENTION] said, the AOSP rom has a built in package manager. However, just to clarify, you will need to find a copy of the .apk file you want outside of the play store. You can search for the app with the browser. You do need to be more careful that you are not downloading from a problematic site; The Amazon app store is safe. I think something like fdroid or apkmirror is probably safe, but I can give no guarantees. As menioned a few posts ago, there are apparently ways of of "unofficially" getting to the playstore.