yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] fddm:
I got to try out the latest Marshmallow rom from Unlegacy Android(ua_ovation-6.0.1-20171224-0949.zip). It's still relatively bug-free like the older amaces build(afaict), but a bit better in that you can just toggle the power button off and on after a fresh boot rather than viewing available networks from the drop down to get wifi to connect. I am having a little trouble with su though. The phh zip doesn't seem to work, so I installed SuperSU in system mode as I have done in the past with amaces' marshmallow build. It works fine until I pull up the terminal and try to elevate privileges, bash responds by saying it can't find the su binary. Any ideas why that might happen?

Edit: interestingly, transferring from SuperSU to KingRoot does solve the issue
[Nook HD, HD+ Android Development] asakurato:
I did exactly that even without reading that lol. I'll try it once again today, hope it works
[Nook HD, HD+ Android Development] fire1951:
AOSP Rom

Just installed AOSP ovation 7.1.2 NKG475 171021 on my nook hd plus. I like it pretty well except that on booting up the nook, WiFi is disconnected. I have to turn off WiFi, turn it back on, then select the WiFi I want to connect to in order for it to connect. Is there a fix for this or something I can do. I have tried doing it with Tasker and a couple of apps to no avail. Thanks.
[Nook HD, HD+ Android Development] nmyshkin:
Have you tried booting (with WiFi on) and allowing the screen to turn off before using? I discovered this "fix" by accident on a Marshmallow ROM that I was ready to abandon because of the behavior you describe. It even worked if I was impatient and used the power button to turn off the screen right after boot. On waking up, the WiFi had connected.

Worth a shot?
[Nook HD, HD+ Android Development] fddm:
AOSP Nougat is a bit different. You need two wireless networks you can connect to. Connect to the network you want to use, then the second network. After reboot, you will auto connect to the first network from then on. Currently recommending lnos+gapps if you want nougat, though asop is really solid once WiFi is set up.
[Nook HD, HD+ Android Development] fire1951:
Thanks,guys, for the info, unfortunately neither method works. The two network method.....after I connect to the desired network first, then the other and reboot, it doesn't connect until I get into wireless settings, then it connects without me having to press connect. The next time I tried, the undesired network was offline and I was back to the original situation ( manually connecting).EDIT= I spoke too soon! Actually the two network method is working! Thanks so very much to both responders.
[Nook HD, HD+ Android Development] HarvHouHacker:
I used this guide to override the WideVine Level 3 and upgrade to WideVine Level 1. Seems innocent enough: http://freaktab.com/forum/tv-player...w-to-enable-widevine-on-any-box-android-5-1-1

However, I had to make some adjustments:

After extracting the ZIP, I could not use the widevine.bat file because I'm on Ubuntu, so I attempted a script. I then realized that I knew very little on creating shell scripts. :( So, I decided to perform the task manually.

I copied the files to my Nook, then using Total Commander I copied the files to their appropriate places.

After rebooting, I checked using DRM Info to see if I had succeeded. It told me that Google WideVine was unsupported. However, I tested both the Netflix and Hulu apps, and I was able to see my DRM content in HD. Huh, go figure. :confused:

[MENTION=4473900]amaces[/MENTION], you might want to integrate WideVine L1 in the next release. I'd rather not go through this again!
[Nook HD, HD+ Android Development] HarvHouHacker:
Did a little research myself. I used this guy's script: https://xdaforums.com/showthread.php?t=2359182

...and this Android Enthusiasts answer: https://android.stackexchange.com/q...ting-swap-at-boot-with-an-init-d-script#18135

The files defiant07 made didn't get installed correctly, as I forgot to make /system read-write using adb remount, so, in order to activate it with each boot, I made an init.d script. A tweak here, a tweak there, a prayer, and it works! ...I hope! :fingers-crossed:
[Nook HD, HD+ Android Development] HarvHouHacker:
Oh, I dunno. Perhaps because there's a lack of understanding between geeks and people who speak layman's terms. :rolleyes: Besides, this is true of modern devices, too!

On the contrary, I managed to keep my Nook from crashing, and everything runs smoother.

Mainly RAM. People should stop using the word "memory" for internal storage! :eek:

Well, these are small apps. Less than 100 MB each. Unfortunately, they take up more memory than storage space. :crying:

Already done, my friend. ;)
[Nook HD, HD+ Android Development] ST Dog:
The only issue I have on my Nook HD is due to gapps, but I don't install more than a few dozen apps on it.

I've tried SD card based swap and it was more frustration than helpful. Native Memory management was slow enough, SD card swap made me not even want to use the tablet due to the slow swap access, even for current foreground apps

So instead I reduced background RAM usage by deleting unused/seldom used apps and found alternatives for most of the resource hogs.

I'd love a new Nook HD with modern CPU and 3-4GB RAM, but it is not likely. (The Nvidia Shield was close, but short lived)

Glad you're happy with the SD Card swap. Just surprised you found it useful.
[Nook HD, HD+ Android Development] fddm:
I forgot that you have to disable and re-enable wifi after rebooting to clear the corrupted entry, sorry, still learning myself. Great you got it working!
[Nook HD, HD+ Android Development] NE0HP:
Interesting article about Android Go!

https://www.xda-developers.com/android-go-old-android-8-1-oreo/
[Nook HD, HD+ Android Development] ST Dog:
It'd be great if there was any work on O for the Nooks, but I haven't seen any.
[Nook HD, HD+ Android Development] HarvHouHacker:
Eh, probably would be quite slow... Nougat barely works as it is. I had to do a lot of tweaking to keep things at bay, even before putting less than half my apps back on there. If you want something that works more "out-of-the-box", try Marshmallow or earlier.
[Nook HD, HD+ Android Development] ST Dog:
Then you missed the whole point of the Go optimized builds/apps.
[Nook HD, HD+ Android Development] fddm:
Edit: After playing around with AOSP Nougat, I found that whenever you initiate a connection(new or saved) that connection is set to disabled in /data/misc/wifi/wpa_supplicant.conf and any connection you are connected to at the time will lose that property. Oddly it doesn't show in the system logs when network setting are being saved. Seems like it should be easy to debug, but until I get around to it, removing that line with a root text editor works great.

I use autostarts to selectively disable broadcasts apps use to startup. I use App Ops(or Privacy Guard in Lineage) to override app permissions. I use Greenify(probably overkill) to force close apps that behave poorly. I can install as many apps as I'd like, as long as I manage them I don't experience any performance impact. I think Nougat feels a bit more responsive than Marshmallow and they both have very similar app compatibility. Need to have reasonable expectations for the hardware though.
[Nook HD, HD+ Android Development] HarvHouHacker:
Sorry, I didn't read the article. I understand now.

---------- Post added at 10:06 PM ---------- Previous post was at 10:03 PM ----------

Well, with development of Android Go underway, perhaps these cumbersome issues will be compensated for automatically. I hope it's not too minimalistic.
[Nook HD, HD+ Android Development] secretwolf98:
Did [MENTION=4473900]amaces[/MENTION] stop making LineageOS and other builds for the Nooks?
[Nook HD, HD+ Android Development] ipdev:
Post2143

unlegacy-android

Side Note from Nexus 5 ua thread. Post1265

;)
[Nook HD, HD+ Android Development] ST Dog:
Good to see updates to the 7.1 builds.

Wish the legal issues would get worked out so progress on 8 could happen.
[Nook HD, HD+ Android Development] secretwolf98:
Wait........ There is illegal issues towards our Nooks?
[Nook HD, HD+ Android Development] fddm:
I do like the idea of a smaller system footprint and minimal Google Play, but I bet you'd still have to manage your apps ability to start and run in the background(unless Go breaks compatibility with greater Android). I'd also imagine that it is pretty far off, assuming there is developer will to port it.
[Nook HD, HD+ Android Development] nmyshkin:
Since you use GravityBox I assume you managed to root the unlegacy AOSP ROM? May I ask how? I tried one of the builds on my Nook Tablet and liked what I saw but was unable to root it by any of the usual means.
[Nook HD, HD+ Android Development] king200:
I used addonsu-phh-arm-new.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3220985318 I used the TWRP from that source too.

All the partitions for aosp have to be /ext4. Wipe system. I actually formatted system to ext3 and then formatted back to ext4.
[Nook HD, HD+ Android Development] w1ll1m:
Can i flash the unlegacy builds over the ones from the initial post?

Or do i have to do a clean install?
[Nook HD, HD+ Android Development] ipdev:
I switched from Lineage. So I did a full wipe and clean install. (a few weeks ago.)

Since then I have updated ua a few times without issue. (ovation by the way.)

I'm not sure about the aosp build. To play it safe I would treat it like an unofficial to official update and clean install.

I don't think amaces will mind. (seems to be very involved in unlegacy. ;) )
[Nook HD, HD+ Android Development] ST Dog:
Go back to the post I replied to.

Read the post from amaces quoted in it.
[Nook HD, HD+ Android Development] nmyshkin:
Mmm...I must be mentally deficient. I was pretty sure I had tried that but I tried again anyway. No go. I assume you follow up with an install of the controller apk (me.phh.superuser.1033). I get that done but can't change the root access and, in any case, no root is detected by apps that need it.

I assume (again!) that you don't mean to format System as /ext4. Everything else is, but TWRP takes care of the format of System on its own (can't recall what it says).

Maybe it's an order of operations? I flashed the ROM and then the addonsu-phh-arm.new.zip, then went to first boot. After that I installed the controller apk via ADB. I think I've tried it before by doing a first boot and then flashing the addonsu zip, but whatever I've tried before, none of it has worked.

Maybe the Acclaim builds are just different. I posted about this issue on the Nook Tablet forum and to my surprise amaces himself responded! If I understood his response correctly, his personal builds are designed with the superuser zip packages in mind while the unlegacy builds are more about the purity of the ROM. So the exploit which allows rooting may not be present--at least not always.

Or maybe I've got the process wrong, but I've never had trouble like this before in trying to root a Nook Tablet ROM.
[Nook HD, HD+ Android Development] king200:
. I formatted the system partition. I made it ext3 and then ext4. I did not rely on the install formatting. Sometimes a folder is preserved to survive format. I'm not sure about Selinux permissive, that are in ua builds.

. System partition was not mounted.

. Installed the rom. Today, "ua_ovation-7.1.2-20180125-0517.zip"

. Installed OpenGapps 0125

. Installed the addon phh (I had already installed the controlling app)

booted into system. The 'Android' stayed for >10 min before system came up.

My default on the controller is "grant" and I don't care about notifications. First app I use is Titanium Backup and see if it gets root. I then went into Exposed app and let it install the 89 framework directly.

I don't think you are mentally deficient at all. I had many attempts on 2 different HD+. I was able to install Amace's AOSP build but not the unlegacy builds. Once I did manage to install the ua builds x clean install, I was able to restore /data and things work fine.

---------- Post added at 05:25 PM ---------- Previous post was at 05:03 PM ----------

I am using a Nook HD+. Things to look for that might make a difference:

. Format /system. Do not rely on the rom install to format.

. System is not mounted. Flash the rom, gapps, addonsu-phh-arm-new.zip. It stays on the "Androd" boot ~10 min. All partitions are ext4. my test for root is to bring up Titanium Backup and see if it gets root.

I was able to install Amace's builds but not ua builds before I stumbled on my steps. Once I got the tablet to boot, I was able to restore the AOSP x TWRP data partiton without a problem.
[Nook HD, HD+ Android Development] nmyshkin:
Nope. No joy here. I even updated my TWRP to 3.1.0 to see if that might make any difference. Nada.

There must be something different about the Acclaim builds that prevents them from being rooted. I took a look at the original Unlegacy Android posting on XDA and followed the instructions there (the same as yours essentially) and tried both methods of rooting mentioned there. But to no avail. Too bad, as the Unlegacy ROMs do not seem to have the shut-down bug that plagues all the other ROMs.
[Nook HD, HD+ Android Development] mikeataol:
I tested this quickly using ua_acclaim-7.1.2-20180125-0236 and

as far as root, looks like you are right , using phh superuser and the addonsu-phh-arm-new.zip doesn't appear to work

As far as power issues being better, not for me

I am still seeing the same persistent bugs

restart reboots to recovery instead of rebooting

power off sits on a blank backlit screen until I wait a little bit and tick the power button

edit: also has the fails to remember wifi settings thing

other minor ones , expect to load a different launcher as the landscape mode carat for app drawer doesn't work

changing screen unlock from swipe to none takes at least one reboot to take hold
[Nook HD, HD+ Android Development] nmyshkin:
Whew! LOL, I thought I was losing it :)

Yes, many other minor things (an earlier build seemed to escape the shut-down issue, this one was mostly OK for all the fussing I did with it), but it's all moot without root. The restart going to recovery threw me. I thought that was

my

fault!

Oh well.
[Nook HD, HD+ Android Development] HarvHouHacker:
One probably would need to manage the apps's memory and CPU usage, especially for the Nook HD+ which only has less than 1 gig of usable memory (when I say "memory" in this context, I mean RAM, of course, and not internal storage). Managing zram (compressed memory in RAM) and swap (memory in internal storage) might help increase memory without having to physically hack the device.

As for Android Go development, as soon as Android Go is available, it's quite possible that unofficial work on it for other devices will quickly follow. My guess; I dunno. Just wait and see. :fingers-crossed:
[Nook HD, HD+ Android Development] fddm:
I don't think that's a bug, seems since nougat ua is building with the amaces patches. You can easily correct it by installing xposed and apm+. With apm in nougat, you have remove items from the edit window to avoid a crash. I remove the default items and add a custom reboot with reboot and reboot to recovery enabled. Other options like shutdown and soft reboot do not work.

Edit: after re-reading, hanging at reboot when choosing power off does seem like a bug. Probably worth trying apm, but you might have to change builds to correct it.

I suppose there's the possibility that when an OEM elects to ship it, go gapps could be ripped and installed on other Oreo devices, maybe. Still don't know what android go is at the system level or if/when it source is offered to developers. And the uncertainty of getting Oreo at all if viability hangs on getting updated proprietary blobs with a permissive licence. What we have right now is pretty impressive, imo.
[Nook HD, HD+ Android Development] mikeataol:
I do not think it is correctable. damaces has said it's kernel issues
[Nook HD, HD+ Android Development] fddm:
Only regarding powering off(you should get over a week in standby, and you can still power off by holding the button). Without amaces patches you just have the power off option, the reboot option is added by amaces' advanced reboot patch. Rebooting does normally work though, so it should be correctable.

Edit: make sure your using amaces TWRP and not TWRP official. It gives me issues since nougat.
[Nook HD, HD+ Android Development] buggage:
Had a Nook HD+ sitting around for a while was slow with half non-working apps, this was great to bring new life back to it. Settled on an unlegacy AOSP version as the performance is much better for me than the Lineage builds. Couldn't get the wifi after reboot trick to stick - not a deal breaker, but would be nice to have working if anyone has any other suggestions - hopefully able to get fixed in upcoming build. Found using the power menu: shutdown = reboot, reboot = reboot to recovery, again no big deal - hold power to shut down if needed as other's said. At least the Nook's actually usable again. Thanks to those who made that possible.
[Nook HD, HD+ Android Development] fddm:
For users that want Lineage without gapps, I uploaded this nandroid backup with initial setup completed:

https://drive.google.com/file/d/1h8mZbdAq9wwCTYqp8hVf7asxC_GGVxFg/view?usp=sharing

First make a backup of anything from TWRP, this will create /TWRP/BACKUPS/<your serial number>/ on your emmc or sd card. Then you can extract this backup into that folder and restore the backup. Be sure to clear cache before rebooting.

Edit: Warning - Be sure to backup all your apps, data, and files before trying this as it will wipe your data.

Sorry if you already know both of these methods, both do the same but maybe a different approach will resolve the issue.

1 - After you connect to a wifi network you can open /data/misc/wifi/wpa_supplicant.conf in any root text editor or most root file managers, find the connection you added and remove the line starting with 'disabled'. Then you let auto-connect do it's thing for that network from then on.

2 - The other way is to connect to two new networks(not tested with open networks) in a row and then disable and re-enable wifi twice leaving you with the first one that will auto-connect.
[Nook HD, HD+ Android Development] HarvHouHacker:
If you don't want GApps, don't flash it in the first place! I intentionally avoided flashing any package from the OpenGApps project. I use Galaxy (a fork of the Yalp Store found on F-Droid; you can get it here on XDA) and microG to fake Google Play services. To remove GApps, make sure your device is rooted and use a system app uninstaller. There are several out there, just DuckDuckGo it. :good:

It's not that the backup won't work, but there are better ways to get rid of GApps without potentially losing data.
[Nook HD, HD+ Android Development] twiztid_:
I recently tried out MicroG, and INSTANTLY noticed a huge battery savings, but I'm having one problem... Do you know of a way to get purchased apps to work? MX Player tells me it can't verify the purchase.

I've logged in using my real playstore account, and MicroG Settings Self-Check has all the boxes ticked except "UnifiedNlp do not have Location to test Geocode"

Thanks in advance!
[Nook HD, HD+ Android Development] Zippy Dufus:
Recent build doesn't boot

Hello,

Has anybody attempted to build this recently?

I've made two attempts (01/07, 01/08) and they both freeze at the bootloader (before the boot animation starts).

My last successful build can be seen in my signature.
[Nook HD, HD+ Android Development] drmarble:
My latest build also stops at the bootloader. It does generate a logcat but I haven;t looked at it yet. My jan 2 build works. I will study the logcat and kmsg to try to find the problem.

It is good to have confirmation that I didn't make a mistake. It really doesn't boot. I will investigate.
[Nook HD, HD+ Android Development] Zippy Dufus:
A little off-topic, but while we are confirming builds, have you gotten a working lineage 14.1 built for the Nook Tablet (Acclaim) lately?

Last few times that I tried, I get a bootable build but the WIFI doesn't work.
[Nook HD, HD+ Android Development] belfastraven:
My last build from Jan. 25th (hummingbird) was good. I'll try to build again tomorrow and get logs if builds are still not booting.
[Nook HD, HD+ Android Development] fddm:
I managed to get magisk working on the latest Unlegacy-Android Marshmallow. Our boot images have Cyanoboot at the beginning and the real bootloader at offset 0x100000(found by searching for the header 'ANDROID!'). I copied the data from that offset to the end of the image and inserted it into a new file, patched with magisk manager, and overwrote the original bootloader(leaving cyanoboot alone) with the patched one. After flashing and installing Magisk Manager, I had working root. Seems like it should be fairly easy to patch these systemless installers to work with our devices.

Licensing and IAP is done by com.android.vending, should work if you install the Play Store.
[Nook HD, HD+ Android Development] ST Dog:
I think the point is that microG is setup in the file he provided.

So you don't have to struggle to get all the right stuff configured.

Restoring part of a backup from TWRP (specifically the system partition) doesn't have much risk of losing data.
[Nook HD, HD+ Android Development] sepehr@teh:
Hello everybody,

I'm using marshmallow :

Installation file : "aosp_ovation-ota-MHC19Q.160406.zip" .

Build Number is : aosp_ovation-userdebug 6.0.1 MHC19Q 160406.

But , I'm not OK with speed . It's too slow . . .

The version of OS is not important for me , I'm looking for fast rom for my Nook . So I can use it as "Book Reader" ( of course with a custom Rom )

Do you have any suggestion ? I should continue using Marshmallow ? Or Nougat ?

Or it is better to go back to Lollipop ?

Thank you for recommendation !
[Nook HD, HD+ Android Development] fddm:
Not quite the case. It's entirely random whether you get through LNOS initial setup, and I have no other workaround to reliably get through it.

You want to go backwards for sure. I tested KitKat recently and it certainly felt blazing fast compared to what I'm used to. I did not do workload tests though, I can only speak to relative 'responsiveness', have no idea if it's actually faster. Between marshmallow and nougat though, they are about the same.
[Nook HD, HD+ Android Development] nmyshkin:
My experience with microG (and confirmed partially by one other source) is that the best results are obtained with the most recent update--even if not listed as "stable". Let me qualify that. I recently did a CM 11 install on an 8 GB Nook Tablet. I've never had trouble with the "nightly" builds before, but this time I could not sign in to Google. So I went back to version 0.24 (stable) and had no trouble signing in. Then I replaced that version with the most recent build. Everything worked fine after that, but I hasten to add that I did not try purchasing apps.

I had a similar experience with apps that suddenly started complaining about needing to update Google Play Services and all I needed to do was update the first microG component. Google makes periodic changes and the developer does his best to stay abreast of them.

Anyway, try the most recent build. It's worth a shot.