yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] HarvHouHacker:
Thanks, [MENTION=3711980]fddm[/MENTION]! :good: Yes, I got that same problem, too. Fortunately, once you get past the initial setup wizard, you can better diagnose problems that surface.

That is, until Android Go is developed. I'm currently using LineageOS 14, comparable to Android Nougat, and it seems okay. I do have several issues that I'm trying to iron out, but nothing critical.

Some of the more irritating quirks:

Some apps don't rotate without crashing. I can start an app, and then rotate my Nook, and then the app crashes. This may be due to the app using a lot of the Nook's resources, requiring more than what is readily available. I suspect the CPU.

Some apps crash while loading activities, or when performing certain actions. For example, scrolling long webpages that are not fully loaded in Firefox can cause it to hang the Nook, and then crash Firefox, returning me to the home screen with no on-screen error (such as "Unfortunately, Firefox has stopped"). One workaround is to make sure the app has finished an activity before trying to do another one. Slow and frustrating, but most of the time effective. Of course, apps can crash anyway, despite using this caution.

Some apps don't work at all, i.e. Super Mario Run. These apps may start up, but before the user can do anything, it crashes. This may be because it requires more CPU and memory than what is available, or it has some kind of bug that I have yet to diagnose.

Apps run S L O W L Y, which since I have swap, suggests that it uses too much CPU.
[Nook HD, HD+ Android Development] ST Dog:
So does or doesn't it have microG configured?

If it's just the ROM after initial setup w/o gapps it wssn't clear.

FWIW, I've never had trouble with first boot/initial setup on LNOS.

---------- Post added at 01:10 AM ---------- Previous post was at 01:03 AM ----------

FWIW, I have that happen on other devices with more processing power, more RAM, and more free internal storage.
[Nook HD, HD+ Android Development] belfastraven:
LineageOS (cm14.1) is bootable after 2/11 repo updates.

[MENTION=4190710]drmarble[/MENTION], [MENTION=3651088]Zippy Dufus[/MENTION] After 2/11 changes, rom is bootable again.
[Nook HD, HD+ Android Development] amaces:
Good detective work ;) Yes, that's the gist of our system-less issues: how do you convince upstream (e.g., SuperSU, Magisk, etc) to add support for unpacking and repacking boot images at custom offset? A very small minority of ancient devices use this custom second-stage approach, and the offsets are not uniform, even amongst various Nooks. In our case, the real abooti happens at 1M, but I can't ask people (in good faith) to add support for our 0x100000 offset. Maybe if there was a reliable, easy way to autodetect the real image, without disturbing the header, that could take off. On the other hand, I can't maintain forked versions of various packages, so what I focused on is baked-in support for the system-mode root addons.

Lineage made some changes to their kernel task (https://review.lineageos.org/195970); the fixes are added in hardware now.

Are you sure you actually got WV L1 working, and not just an L3-fallback like we already do? L1 requires custom blobs that are much more tightly coupled with the SoC, which we haven't had in years. What exactly is the issue with the existing DRM solution? I'll try to take a look at those files.

There has been quite a bit of work out of sight, all depending on the public availability of a few new blobs, but we're still no there yet. Also, all the work done on other platforms is not going to waste.

Any new AOSP tags or significant Lineage developments? Because that's when I work on new personal builds. Anyway, the new Lineage builds in experimental contain kernel changes that happened via Oreo backports and fixes.

It's perfectly OK, at least till if I decide how to group the build information.

UA <-> AOSP should be fine as long as same major version. Clean ideal is always ideal though, and pretty much required with <-> CM/LN builds.

That really is not required since OTAs always erase that partition. As a side note, things are not as fragile as people have described lately, and every problem has a simple explanation that was discussed before, or posted in the OP, FAQ, etc.

To reiterate, only my personal AOSP builds are modified in such a way to allow using the addonsu ZIPs. The UA builds are a lot closer to upstream AOSP.

Just curious, did you run into any signature spoofing issues with microG on these builds?

Please read the selected FAQ (post #3).

The kernel tells you about all memory allocations in great detail; what userland (i.e., Android in this case) decides to report is another issue. There are many layers involved here, and even the core OMAP4 architecture (ICS/JB era) requires certain trade-offs.

We're already using zRAM-based swap, which is barely acceptable as is, but still preferable to swapping on eMMC or SD. Of course, you're free to modify the init scripts any way you need.

Even before LZ4-compressed swap, our CPUs were not thriving on current Android, but we make do.
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION], thanks for a new LineageOS 14.1 build. I will install and test them on hummingbird and ovation, while I am waiting for my laptop to update Windows 10. Keep up the great work. Any chance on our Nook's getting Android 8.0/8.1? Also, any new features in these builds or known issues that have been reported that are in the latest updates? I would like to compile my self, but my hard drive is way to small. Thanks.
[Nook HD, HD+ Android Development] nmyshkin:
I've done work only with Acclaim builds, starting back with CM 11 and on through LN 14.1 (no Unlegacy builds because of the inability to root them). All require a patch for signature spoofing, either by using an Xposed module, or by direct modification of the framework which can be accomplished automatically via a Python/ADB routine called "Tingle". I prefer the latter method and it worked on all the ROMs I tested except for the rather unique AOSP 7.0 of yours from some time back which disappeared from your archives (aosp_acclaim-ota-NBD90Z.161020). That's the only ROM with no shutdown issues and the Python/ADB method ("Tingle") sees the ROM as odexed and so can't deal with it. But the Xposed approach works fine in that case, especially now that there is a stable Xposed for Nougat.

Once the patch is made, it all works as it should. Based on my experience so far I would say that for any ROM which is not a stretch for the hardware (as many are for the 8 GB Acclaim), the actual PlayStore app can be used without issue once things are set up properly. ROMs which are more of a challenge for the hardware benefit from using the YalpStore to access the market once the initial sign-in is accomplished with the actual PlayStore app. There is no way to prevent the auto self-update of the app from one which might not tax the system (like one from a Jellybean GApps) so in those cases the YalpStore would be the better bet.
[Nook HD, HD+ Android Development] secretwolf98:
Review of 2/11 build of LineageOS 14.1

On Ovation, SU fails to flash. On Ovation, the screen goes black and blank for about 5 seconds and comes back when you pull down the ui quick settings thing. Hummingbird, I haven't tested that yet, but I would think that would have the same issue? Anyways, everything else works fine (as far of what I have tested). [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] HarvHouHacker:
[MENTION=4473900]amaces[/MENTION], thanks for including me in your long post! Now, let's see what we got here...

Yes, it actually works. I have crisp clear video playback in both Hulu and Netflix. I had to revert to an older Hulu version, but all the videos output a high resolution picture. It takes some time for the video to fully calibrate into Level 1 WideVine, which causes some initial... "jerkiness", if you will - but when the WiFi signal is strong, I get full HD. For Netflix, I can use the latest app without problems. Before this fix, I noticed that the videos weren't outputting HD quality, so I did some net searching for a solution. I ran across the link I provided here before, and despite my concerns that the steps might not work, it did! :victory: I had to rename and replace some files, though.

Good to know. Not sure what all the abbreviations means, but I'll probably DuckDuckGo it to find out. :D

Thanks, amaces! You rock! :good:

I did! I wanted to make sure that I had enough virtual memory to compensate for the lack of physical memory. My Galaxy S7 has 4GB, so why not my Nook? Maybe that's illogical logic... :silly:
[Nook HD, HD+ Android Development] amaces:
I've patched the AOSP builds in experimental with https://gerrit.omnirom.org/20414, which should hopefully allow microG installations without other changes. You will have to grant this spoofing permission where appropriate, which obviously is a big security risk, and the reason CM/Lineage never merged this.

I've done a clean install on hummingbird, and it seemed fine, but I'll check ovation. Oddly enough, the official Lineage SU addon, as well as my personal build, flashed properly, but failed to work properly, which I'm assuming is what you mean. At any rate, I rebuilt my copy from current sources, and it seems to work fine. Maybe that was the issue people mentioned before?
[Nook HD, HD+ Android Development] secretwolf98:
Ok, I will test hummingbird.
[Nook HD, HD+ Android Development] Zippy Dufus:
All good!

I can confirm that ovation is building fine for me!

As a bonus, I saw [MENTION=4473900]amaces[/MENTION]'s new acclaim build in his experimental folder so I tweaked my build script and now have a build with working WIFI.

Great work [MENTION=4473900]amaces[/MENTION] !!
[Nook HD, HD+ Android Development] mikeataol:
I've only tried the acclaim LNOS latest at this point (lnos_acclaim-ota-NJH47F.180211.zip)

but I can confirm that the old, and the official addonsu-14.1-arm.zip's do not work,

yet the one from amaces' box repository does give root .

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

addonsu-14.1-arm.zip created 2/11/18

Also, for reasons unknown to me, the power off/restart/restart to recovery being a problem has disappeared as well.

Thank you! [MENTION=4473900]amaces[/MENTION] , I know people appreciate your work.
[Nook HD, HD+ Android Development] dbrickg:
I just installed the 20180212 lnos for hd+ and it's looking quite good! While I was installing, I flashed the new twrp 3.2.1-0. Then the 20180212 lnos for hd+, then the new addon su. Thanks much, amaces, for all you persistence in building new stuff for our tablets!
[Nook HD, HD+ Android Development] amaces:
There might be memory management issues with at least the Lineage ovation build. I'll move those builds to obsolete till I figure out what changed.
[Nook HD, HD+ Android Development] dbrickg:
Hah! Well, I don't think I've ever used a computer that didn't have memory management issues :)
[Nook HD, HD+ Android Development] jernyx:
I installed the latest uploaded build from Feb 13. It's running pretty well as usual but when I tried to change my background I noticed the gallery app wouldn't work at all even from the app drawer. I tried deleting the apk via the shell and reinstalling from apkmirror but that didn't work. Not a problem for me really, just curious if anyone else has the same issue.
[Nook HD, HD+ Android Development] nmyshkin:
The ROM seems in pretty good shape, but I did not have luck with the power off/restart. Still hangs on shutdown and restart, leaving a backlit screen.
[Nook HD, HD+ Android Development] mikeataol:
Yeah, me too. actually. The first few boots seemed fine but that power off bug behavior has settled in .

It seemed fine before I configured any wireless settings
[Nook HD, HD+ Android Development] nmyshkin:
Well, now....Isn't that interesting?

So I just tried shutdown and restart a number of times with WiFi turned OFF and what do you know? It worked each and every time! Once WiFi is turned ON, whether it connects or not, shutdown and restart do not work properly.

......OK, take a break and try several more times before hitting "submit"....

Yep. Unfortunately I don't know what it means, but that's the behavior I am seeing. It's kind of like trying to shut down Windows and it says "nya, nya! There is a program running preventing shutdown!"

Try it and see if you can confirm.
[Nook HD, HD+ Android Development] buggage:
Yes, gallery doesn't work for me either, keeps crashing when trying to launch.
[Nook HD, HD+ Android Development] mikeataol:
Yes, it appears to shutdown properly with WiFi off. (acclaim)

For me, with the acclaim, I keep it plugged in nearly all the time so it never was a big deal for me.

If it was off the charger it was in use, and if needed I just went to recovery to shut it down.

I had noticed this sometime around October, and never really worried about it.

I tested a tasker script , I'm sure there's other ways to do it, to turn on WiFi on boot, and turn it off on shutdown, and it works

On Ovation, turning Wifi off , and shutting down still reboots when it shouldnt
[Nook HD, HD+ Android Development] nmyshkin:
Yes, I tested the behavior on a spare HD that is running CM 12.1. It made no difference.

I was thinking about a Tasker routine but didn't know if the timing would be right. I guess it could be!
[Nook HD, HD+ Android Development] amaces:
Oddly enough, the same Gallery2 built into AOSP works fine, so it's not the app itself, the kernel, or device trees since I'm using the same in all ROMs. No idea what Lineage changed that degraded those ROMs to this extent, but you should probably use AOSP till it's sorted out.
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION], I am running your latest build, 2-14-2018 on ovation, here is some feedback: YouTube works 100% fine with no lag, the downloads app doesn't show up, so you can see your recent downloads, and the Gelly browser, if you try to download a .apk file, it fails to open.
[Nook HD, HD+ Android Development] buggage:
Thanks. I actually prefer the AOSP bulids as they are quite a bit more responsive on my Nook HD+. Do we know yet why the wifi connection gets wiped out when wireless is disabled or device restarted? It looks like it either wipes out all saved wifi connection info from the wpa_supplicant.conf file, or just creates a new default file each time. There were a couple of workarounds suggested in the posts, but unfortunately, none of them work for me.
[Nook HD, HD+ Android Development] dbrickg:
Just now rebooted into the lnos ovation 7.1.2 NJH47F 180214 OS. Dirty flashed over the 180212 version. Looks good so far!
[Nook HD, HD+ Android Development] Tacodude89:
I would like to do this but I are not smart enough. Can someone help?
[Nook HD, HD+ Android Development] fddm:
Sure, if you say what ROM you want to test, I'll pre-patch it for you.
[Nook HD, HD+ Android Development] Tacodude89:
I was thinking the AOSP Ovation

Thanks
[Nook HD, HD+ Android Development] fddm:
These are all the current AOSP Ovation pre-patched with Magisk. This is for testing purposes only. You need to install Magisk Manager to get root after flashing. Edit: You need to flash the official zip after flashing a pre-patched rom. It will fail when patching the boot image(which is already patched), just ignore the error as it did install correctly.

amaces AOSP Marshmallow Stable 160820:

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

amaces AOSP Nougat Stable 171206:

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

amaces AOSP Nougat Experimental 180212:

https://drive.google.com/file/d/1rjrbkTU5-wncziLNUSykFisx7w9dyT9-/view?usp=sharing

Unlegacy-Android AOSP Marshmallow Nightly 20180211:

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

Unlegacy-Android AOSP Nougat Nightly 20180215:

https://drive.google.com/file/d/1j-8oHqiV11TpD9_kKiVilUaxjB8M4v6Y/view?usp=sharing

---------------------------

amaces LAOS Nougat Experimental 180214:

https://drive.google.com/file/d/1vN5d15-AQQb4XgxzguwfUtDS0ECME3md/view?usp=sharing

--------
[Nook HD, HD+ Android Development] Tacodude89:
Really any of them would be fine with me. I guess that first one if I have to choose.
[Nook HD, HD+ Android Development] amaces:
This is good. I think a more maintainable approach would be patching the bootimage processing scripts directly (in Magisk, SuperSU, etc).
[Nook HD, HD+ Android Development] fddm:
Thanks! I do plan to try patching Magisk Manager(or at least the binary in the installer zip), I'm a bit of a procrastinator though. I'm thinking it just needs to check for effected devices and then for the presence of a second header following padding.
[Nook HD, HD+ Android Development] HarvHouHacker:
Are you sure you have Marshmallow? Check which version you have by navigating to Settings > About tablet and looking at the Android version. If it is 6.x (i.e. 6.0.1) then it is Marshmallow; if it is 7.x then it is Nougat. I would avoid experimental/beta versions unless you're willing to test unstable software.

Just trying to help, since it looks like you're taking a shot in the dark. :angel:
[Nook HD, HD+ Android Development] secretwolf98:
Can you patch one for Ovation LineageOS 14.1 2-14-2018, made by, [MENTION=4473900]amaces[/MENTION]? https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/277293423354
[Nook HD, HD+ Android Development] Zippy Dufus:
Magisk?

A couple of quick (dumb?) questions:

What's the requirement that Magisk is to meet? Root? Other stuff? (I haven't heard of Magisk until reading this thread.)

Is Magisk relevant to only the ASOP ROMs? (I build the Lineage 14.1 version of this ROM with baked-in root and it has always worked fine for me. However, I'm not so sure about Lineage 15 (Oreo) as one has to explicitly enable the build of su and I am pretty sure that it doesn't work for my phone's ROM.)
[Nook HD, HD+ Android Development] rtarv321:
I dirty flashed the latest ovation & pico gapps. All is working fine. Seems faster. I keep reading about the shut down issue. I use an app called "quick boot pro" from Google Store. My main reason for using it was the ease of rebooting to recovery without any button inputs from me. One of the options is to shut off. It works fine, even with the charger connected
[Nook HD, HD+ Android Development] mikeataol:
Hi, can you clarify which app you are reffering to? There are a million shady looking "Quick REboot" apps, I am not seeing any app clearly labeled "Quick Boot Pro" except on hacked apk sites. Thanks
[Nook HD, HD+ Android Development] rtarv321:
I sorry, the correct name is "Quick Reboot Pro" by AntaresOne. It says #1 reboot manager (Root). I tried several ones and this one works. I started using it because I was having a problem trying to reboot to recovery using the power and center button sequence, it seemed to only work one out of five tries. I am sure it was just me. Let me know how you like it. Again, sorry for the incorrect name
[Nook HD, HD+ Android Development] mikeataol:
no worries, I tried that app, using an earlier version on Ovation, the shutdown still ends up in a reboot....

I've used another one "Advanced Power Menu (root) NOXX"

which works with use of the power button instead of a standalone app

(https://xdaforums.com/android/apps-games/advanced-power-menu-root-t3227214

Playstore: https://play.google.com/store/apps/details?id=com.noxx.apm)
[Nook HD, HD+ Android Development] fddm:
For users trying a Magisk pre-patched rom: I found that we must additionally flash the official Magisk zip after flashing the rom. It will fail on the last step when patching the boot image, you can ignore that as it did install properly.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

It's a root manager and provides a means, through downloadable modules, to modify the system without ever touching the system partition. It's not specific to AOSP, is compatible with Oreo, and should install without error on most devices.
[Nook HD, HD+ Android Development] fddm:
Seems I got lucky with Magisk, there is pre-existing Nook support. Attached is a repacked version of the official zip with the arm 'magiskboot' binary replaced. All I did was change the offset from 0xFFFFF to 0x100000 and the header check from "Green Loader" to "eMMC boot.img+secondloader for ovation". Will have a look at other nook images tomorrow and see about submitting a patch for them.

Edit: See https://xdaforums.com/showpost.php?p=75639041&postcount=2364
[Nook HD, HD+ Android Development] mikeataol:
Thanks for this ,

Would this be for all 3 , Ovation, Hummingbird and acclaim? or just Ovation & Hummingbird you think
[Nook HD, HD+ Android Development] amaces:
Just the Nook HDs; looks like acclaim's starts at 256K (0x40000). No harm testing though.
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION], can you make Lin14.1 for the 8GB acclaim?
[Nook HD, HD+ Android Development] amaces:
Isn't that the version with half the memory? Did CM/Lineage ever work on that board? If so, try installing the current builds.
[Nook HD, HD+ Android Development] secretwolf98:
I think so. CM 13 and under only works, could you build like CM 13 or Lin13, if Lin14.1 won't work? Stock is junk. I would love to get off of NookOS. [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] amaces:
Have you tested the current Nougat images (AOSP, or LN14), and they fail? If so, you'll have to provide more information, logs, etc. In theory, ION and the rest of the kernel supports 512MB configurations, but Nougat probably doesn't work very well.
[Nook HD, HD+ Android Development] secretwolf98:
It installs and boots fine, but bootloops within a day. And then in settings, it says 16GB out of 16GB used. But on stock it says I have 8GB of storage. It won't let me download any apps, because it says, out of space, in the Nougat builds. This was like last summer or so, when I used your Lin14.1 on my acclaim device. [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] amaces:
Try the current AOSP builds since current LN14 is probably worse than what you tested over the summer. I don't even have a regular acclaim, so it's unlikely that we can make progress on the lesser board, especially without logs.
[Nook HD, HD+ Android Development] secretwolf98:
Ok, where can I get a Stock 1.4.3 bootable CWM image for my SD Card?
[Nook HD, HD+ Android Development] nmyshkin:
I tried the LN 14.1 for acclaim in the "experimental" folder on an 8 GB tablet just recently and had no trouble with it--other than lag and the shutdown bug nuisance. I've also tried the LN 14.1 in the acclaim folder. Both "function"

without GApps

(I used microG) but are not satisfying. CM 13 is better IMHO (see https://xdaforums.com/nook-tablet/general/how-to-cm-11-8-gb-nook-tablet-bntv250a-t3667555, but note that the LN 14.1 build I mention there is older).

Best of all is CM 11 without GApps. That ROM sings on the 8 GB tablet and with a little careful choice of older versions of some apps I was able to essentially reproduce my AOSP 7.0 setup from my 16 GB tablet (which

does

run GApps). Both tablets are a pleasure to use.

In the end I've decided that the best experience is had by matching as closely as possible the ROM with the hardware (duh). The rest is interesting and perhaps instructive, but not practical if you actually want to use the device on a regular basis. It may be that the mini-Oreo or whatever will give a new lease on life to the 8 GB acclaim, but I'm not holding my breath. Many challenges there, I'm sure.
[Nook HD, HD+ Android Development] secretwolf98:
Where can I get a cm 13 build?
[Nook HD, HD+ Android Development] nmyshkin:
Follow the link in my previous post. The ROM evaluations are in the second post in the thread (including links to the ROM zips).
[Nook HD, HD+ Android Development] secretwolf98:
any cm 13 newer than 8-19-2016 official?
[Nook HD, HD+ Android Development] nmyshkin:
The one I used was the only one I could locate.
[Nook HD, HD+ Android Development] secretwolf98:
do you recommend cm 13 or cm 11?