yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] fddm:
I fixed magisk support for Lollipop roms and it now works with both HD and HD+. Turns out Lollipop roms use the header "Green Loader" and the offset 0x100000, so I just need to fix the offset in Magisk. I also made it check for the header "eMMC boot.img+secondloader" so it will work with Marshmallow+ roms.

https://github.com/worstperson/Magisk(source)

No Acclaim support though. I added support and flashed an acclaim boot image to my ovation, but Magisk thinks the image has already been patched(so it fails). Will have a closer look later. Edit: Acclaim support has now been added.
[Nook HD, HD+ Android Development] 99x:
Nice job, working great!
[Nook HD, HD+ Android Development] nmyshkin:
I worked with the CM 13 for quite awhile and then got the idea that I should try CM 11 without GApps (I had previously run it with GApps). I don't see myself going back to CM 13 on the BNTV250a.

BTW, the CM 13 ROM I used is likely the final form for acclaim, based on the posting date by [MENTION=361777]chrmhoffmann[/MENTION] for CM 14.1
[Nook HD, HD+ Android Development] HarvHouHacker:
Lag, lag, lag! I'm ready for Android Go! :frustrated: (Oh, wait. There is no such smiley...)

@amaces, do you think you could make a lighter version of LineageOS 14 for the Nook HD+ using the LineageOS versions based on Android Go? Just curious; I don't know if it would make much difference. What would be the differences there?
[Nook HD, HD+ Android Development] secretwolf98:
Rooted stock, flashed cwm, erased stock, flashed cm11, flashed twrp, and when I try to boot to twrp to try cm13, it won't boot, it is stuck at the N splash screen. Any help?
[Nook HD, HD+ Android Development] nmyshkin:
That seems excessive. I have a card made up with TWRP 2.8.6.0 as main recovery and CWM as the altboot recovery. I use the CWM for flashing back to stock, but this step is not really needed unless you have been doing a lot of flashing on the device and are experiencing battery/power anomalies. So my general procedure would be:

1. Boot to SD card TWRP (i.e., boot with power cord inserted--although my tablet does not seem to require this), and press the "N" button when the Cyanoboot screen appears until the Boot Menu heading appears, then release. If TWRP does not start up then there must be an issue with that file or one of the other boot files. You could troubleshoot this by trying the altboot (CWM) instead and if that works, then it's a bad TWRP.

2. Advanced wipe, including System. I almost always do this twice.

3. Flash internal TWRP 2.8.6.0

4. Flash CM 13 ROM
[Nook HD, HD+ Android Development] secretwolf98:
Cyanoboot won't show.
[Nook HD, HD+ Android Development] nmyshkin:
Then you either have a defective card (or one or more defective files on it) or your tablet needs to be plugged in to boot from the SD card and you are not plugged in.

If you're going to prepare a fresh card, just follow any of the many sets of directions found in the Nook Tablet forum. You could follow steps 1-2b in this post: https://xdaforums.com/nook-tablet/general/how-to-installing-aosp-android-7-0-t3578665

Then add to the card the CM 13 ROM as well as a flashable TWRP 2.8.6.0 zip for the internal emmc. Every step in the card prep is important. Leaving out one detail can result in a card that fails to boot the tablet properly. If you're going the fresh card route, I recommend reformating before all else.
[Nook HD, HD+ Android Development] ST Dog:
Biggest things to me is passing Safety Net and hiding root from most apps that check for it.

---------- Post added at 01:39 AM ---------- Previous post was at 12:56 AM ----------

Installed on LNOS14.1 after flashing unSU.zip to remove the LNOS addon.

SafteyNet passes basicIntegrity but not ctsProfile.

Hid root from Google apps and old Netflix.

PlayStore offers to update Netflix. New Netflix (5.13.1) runs and even allows downloads.

Success!

Need to figure out why ctsProfile fails, but the big one works.
[Nook HD, HD+ Android Development] secretwolf98:
Fixed, thanks. :)
[Nook HD, HD+ Android Development] zspeciman:
I've done a fresh install of aosp_ovation-ota-N2G48H.180212, along with the latest twrp-3.2.1-0. The smoothest experience I had from this tablet, a real noticeable improvement. Just looking at the avg memory usage of two identical Ovation tablets, on Aosp it hovers around 550-600mb out of 860mb, where lnos (lnos_ovation-ota-NJH47F.180214 also fresh install) was around 680-750/860. The Aosp at least in my case felt noticeably smoother than the Lineage. Thanks [MENTION=4473900]amaces[/MENTION] for this build. The only problem I have is that trying to Restart the tablet, it goes straight to twrp. Is that a known problem or something I messed on the settings? Any solution on how to fix that?
[Nook HD, HD+ Android Development] mikeataol:
It's a known problem that reboot often goes to recovery, and power off doesn't, it will reboot after a short wait.
[Nook HD, HD+ Android Development] nmyshkin:
Kudos to [MENTION=3711980]fddm[/MENTION] who doggedly pursued Magisk for Acclaim! Details and downloads here: https://xdaforums.com/nook-tablet/help/acclaim-patched-magisk-tester-t3752775

---------- Post added at 05:56 PM ---------- Previous post was at 05:44 PM ----------

Maybe. I've been testing one of the Unlegacy AOSP builds for acclaim. All these ROMs suffer from the shutdown/reboot issues. I once tried an Xposed module (APM+) that was mentioned in a post as a "fix". At the time I was testing a Lineage 14.1 ROM and the whole thing just did not want to work. I chalked it up to the module being outdated (supposedly for KitKat) and gave up.

I decided to revisit it when I began looking at the Unlegacy AOSP 7.1, thinking I could use Xposed to set up microG if I got the power menu thing sorted out.

It seems to work. So far. For me. Xposed was a little rocky and required an additional reboot to kick in (maybe because of Magisk?) but when things settled down I was able to configure the APM+ module. The great thing about it is that you can actually

remove

the wretched "Restart" option from the shutdown menu and replace it with a (advanced) "Reboot" option. You can also add Screenshot to the menu, etc. So far it is working great for me. Your mileage may vary as I tried this on an Unlegacy AOSP ROM.

Here's a link to the module's page: http://repo.xposed.info/module/hk.kennethso168.xposed.apmplus
[Nook HD, HD+ Android Development] ST Dog:
Xposed has a history of causing problems, so much so that RIM devs won't look at issues if Xposed is installed.

It also seems rather heavy handed for a rather minor issue. Do people really shutdown their tablet that often?

Mine hasn't been turned off in over 2 years.

Rebooted, OS changed, etc., but not off.
[Nook HD, HD+ Android Development] nmyshkin:
I'm going to say right off the bat that I'm no expert and also admit that I have a real issue with the shutdown bug. It's my OCD showing, probably. I've avoided Xposed in the past because of statements like yours, but I have to say for the limited use I now make of it (FakeGApps when Tingle won't work and APM+) I have not noticed any negatives. I did not make the decision lightly to try it on my AOSP 7.0 acclaim tablet which is perfect in every respect (

including

shutdown), but I really missed the screenshot option in the shutdown menu (not to mention reboot). So I finally gave in and tried it when Xposed for Nougat became available. I don't regret it. Yet.

And yes, I turn my tablet off every night. If I didn't, I'd be charging it every day. Do androids dream of electric sheep?
[Nook HD, HD+ Android Development] fddm:
Since I haven't seen it mentioned yet, instead of using Tingle, I suggest trying NanoDroid-patcher. It doesn't require anything special and it directly modifies the framework apk jar as you might hope.

https://downloads.nanolx.org/NanoDroid/Stable/
[Nook HD, HD+ Android Development] ST Dog:
I haven't checked standby time on my HD in a while, but it's on charge most of the time I'm not using it. I stream radio all bight and it's my alarm, so it's on the nightstand plugged in overnight.

I haven't seen that line in a long, long time. ;)
[Nook HD, HD+ Android Development] Zippy Dufus:
Interesting. I built this ROM with the Linaro 5.2 toolchain and have the same problem. Something is amiss but I haven't figured it out yet.:(
[Nook HD, HD+ Android Development] belfastraven:
Which rom did you build--cm or AOSP? I have been building and running cm with no problems installing(not sure which toolchain)--I am able to dirty flash since I'm staying on the cm roms.... I didn't try the latest AOSP rom yet, but imagine that [MENTION=4473900]amaces[/MENTION] did, before he moved it from experimental. I did test the cm rom that [MENTION=4473900]amaces[/MENTION] had in the hummingbird folder and had no problem flashing it. IF you wipe system before you flash do you get the same issue? P.S> did you let TWRP keep your system r/w or did you change it to read only?
[Nook HD, HD+ Android Development] KnowledgeBroker:
Let me give feedback. You need to get a newer version of twrp to flash- worked like a charm then.

Everything works great. Like really great. See attached picture.. This was supposed to be a glorified gauge pod- that plays music.. And instead, I've been tethering internet from my phone, and I'm at the beach streaming a movie from my computer at home, using team viewer.

Yes- this $65 tablet with this os is amazing.

If that's a deal breaking bug, I have not found it since Wednesday.

Thanks Dev, where's your papal link, this guy wants to buy you a beer (coffee.. Whatever your vice is!)

Thanks again, happy guy right here :)
[Nook HD, HD+ Android Development] amaces:
You're a funny guy, but man, do I feel like down some sort of rabbit hole ;) Whatever happened to your Bluetooth issue, and did that get fixed somehow?

What kind of mysterious error on AOSP? Also, if anyone had any issues with the AOSP builds, chime in; I don't wan't to leave broken builds in there, and don't have time for the whole TWRP backup dance.

You know, a current 4.9 Android EABI is pretty much the best you can get. The bottleneck is definitely not the bare-metal performance, on the ROM side, at least. You may squeeze some marginal improvements with deep optimizations, akin to what I did on CM12, but those build system changes are a future concern.

For now, UberTC is the best compromise for our sources. At least, that's what I've been using for the past few months.
[Nook HD, HD+ Android Development] Zippy Dufus:
Never mind and sorry. I ran an ASOP build last night and it was successful!

using prebuilt boot.img from BOOTABLE_IMAGES...

boot size (5599232) is 33.37% of limit (16777216)

running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt

running: java -Xmx2048m -jar /home/android/out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmp52gPje /home/android/out/target/product/ovation/aosp_ovation-ota-MMB29T.160109.zip

done.

#### make completed successfully (06:44:55 (hh:mm:ss)) ####​

The "mysterious error" was from my last attempt on 12/15. It may be related to my kludge of copying the proprietary stuff to a location in the library path. Maybe I'll remove this and see if that issue mysteriously goes away too.

Copy: /home/android/out/target/product/ovation/system/vendor/lib/mediadrm/libwvdrmengine.so

make: *** No rule to make target '/prebuilt/etc/media_codecs_ffmpeg.xml.stub', needed by '/home/android/out/target/product/ovation/system/etc/media_codecs_ffmpeg.xml'. Stop.

[0;31m#### make failed to build some targets (03:25:27 (hh:mm:ss)) ####[00m

​

Yup, you pointed this out already and so did this chap. Again, I'm just hacking for fun here to see if I can build the toolchain to build the ROM. BTW, the Linaro 5.2 kernel is noticeably more laggy and less smooth than yours. But, you spoiled my fun by implementing Linaro 4.9 for this ROM ;)
[Nook HD, HD+ Android Development] smileyint:
Hi Amaces,

Its CM13. I remember vaguely about 2-3 release back. How do i get Wi-Fi logs on the phone itself and i can only test connection where there is country free wifi.
[Nook HD, HD+ Android Development] amaces:
More fun can be had still; I prepared a build system branch with the CM12 optimizations ported to CM13 (cm-13+optim, here), specially for your testing. If you're inclined to make your way through that forest of flags, and report what is good, what fails, etc, that could potentially help when development slows down, and we need to squeeze the last bits of performance.

You don't need to grab logs yet; let's just see how the builds later today work. Otherwise, Wi-Fi debug information would be located in /data/misc/wifi, plus the dmesg/logcat combo, of course.
[Nook HD, HD+ Android Development] belfastraven:
Can I play, too? When I tried to init based on cm-13+optim I get

fatal: Couldn't find remote ref refs/heads/cm-13+optim

Do I need to specify a different manifest in the init, or something else? I'm just trying to learn how all of this works, as well as to understand what you have been changing in the kernel. I promise not to whine and to try to debug by myself in the future.
[Nook HD, HD+ Android Development] KyJelly69:
I tried twrp both rw and r only. What do my partition sizes need to be?
[Nook HD, HD+ Android Development] amaces:
Not sure what you're asking…

You'll need a local manifest where you overload the build repo only, or modify the default manifest with one of your own commits. Either way, both involve a bit a of research about the repo XMLs, but it's good knowledge to have as a builder.
[Nook HD, HD+ Android Development] Zippy Dufus:
+1
[Nook HD, HD+ Android Development] KyJelly69:
Tried a different sdcard and the rom installed. Tried aosp and cm both fail to boot to the os but instead go right back into twrp.
[Nook HD, HD+ Android Development] belfastraven:
I think you can change the revision in the manifest.xml file, or delete the project and then insert a build project with the new revision in your local roomservice. I just tried the latter, and I THINK it worked but am not positive (I got a repo sync with no errors, at least) :)

I builtsuccessfully earlier today with the normal cm-13 base, and just had a build fail after rebasing to cm-13+optim. failed making recovery image. so I think something changed :)

Does this help at all?
[Nook HD, HD+ Android Development] leswgnr:
The 1080p landscape one from the referenced thread worked well for my nook hd+, much bettter than the 720p.
[Nook HD, HD+ Android Development] Zippy Dufus:
Are we having fun yet?

Good first try ...

[32mtarget thumb C++:[0m libaudioflinger <= frameworks/av/services/audioflinger/AudioFlinger.cpp

[32mtarget thumb C++:[0m libaudioflinger <= frameworks/av/services/audioflinger/Threads.cpp

[01m[Kframeworks/av/services/audioflinger/AudioMixer.cpp:[m[K In static member function '[01m[Kstatic void android::AudioMixer::track__NoResample(android::AudioMixer::track_t*, TO*, size_t, TO*, TA*) [with int MIXTYPE = 0; TO = int; TI = short int; TA = int; size_t = unsigned int][m[K':

[01m[Kframeworks/av/services/audioflinger/AudioMixer.cpp:1941:6:[m[K [01;31m[Kinternal compiler error: [m[Kin vect_get_vec_def_for_operand, at tree-vect-stmts.c:1451

void AudioMixer::track__NoResample(track_t* t, TO* out, size_t frameCount,

[01;32m[K ^[m[K

Please submit a full bug report,

with preprocessed source if appropriate.

See <http://source.android.com/source/report-bugs.html> for instructions.

build/core/binary.mk:706: recipe for target '/home/android/out/target/product/ovation/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioMixer.o' failed

make: *** [/home/android/out/target/product/ovation/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioMixer.o] Error 1

make: *** Waiting for unfinished jobs....

make: Leaving directory '/home/android'

+ local ret=2

++ date +%s

+ local end_time=1452487274

+ local tdiff=7421

+ local hours=2

+ local mins=3

+ local secs=41

++ tput colors

+ local ncolors=256

+ '[' -n 256 ']'

+ '[' 256 -ge 8 ']'

+ color_failed='\e[0;31m'

+ color_success='\e[0;32m'

+ color_reset='\e[0m'

+ echo

+ '[' 2 -eq 0 ']'

+ printf '\e[0;31m#### make failed to build some targets '

[0;31m#### make failed to build some targets + '[' 2 -gt 0 ']'

+ printf '(%02g:%02g:%02g (hh:mm:ss))' 2 3 41

(02:03:41 (hh:mm:ss))+ printf ' ####\e[0m\n\n'​
[Nook HD, HD+ Android Development] neutronjeff:
Do we need to flash a version of SU for the cm13 build to get root functioning and if so, please recommend a version.
[Nook HD, HD+ Android Development] KyJelly69:
I tried the new cm build from yesterday and still no luck. For some reason it always boots back into twrp after reboot.

edit 1. I tried a flashable bootloop fix zip still goes straight into twrp.

edit 2. flashing the latest lollypop rom in the shared folder works as expected.

edit 3. after flashing cm lollypop i let it get to the setup process for the rom then I booted back into twrp. Then i did a factory reset and then installed cm mm and gapps. looks like it's working so far. will update in a bit.

edit 4. working great so far. Quick question. It did not ask me to install the apps that were installed on a previous device like lollypop did on other devices I have. is this normal or did I miss something? AOSP only maybe?
[Nook HD, HD+ Android Development] twiztid_:
Would you mind giving some more information on which file to use/the steps you need to follow?

I hadn't used Xposed in a long time, lack of need not because of problems, and recently installed it to go microG on my nook. If I could get by without Xposed I'd prefer it, since it's one less thing installed.

Thanks!
[Nook HD, HD+ Android Development] fddm:
You just download the zip on the linked page that starts with 'NanoDroid-patcher' and flash it through TWRP. Once it finishes, you install and configure microg gms and gsf like normal. When you flash a new ROM, you have to patch again.
[Nook HD, HD+ Android Development] HarvHouHacker:
Yeah, that stinks. :( At least with the Galaxy S7, you can choose whether flashing a new ROM will keep data or not. That's true of stock Android; I'm not sure about the likes of LineageOS or other.

By the by, I'm still waiting on LineageOS Go! :fingers-crossed: (See post #2367)
[Nook HD, HD+ Android Development] fddm:
That is specifically a system-mode framework patcher. If you want systemless, it needs to be done through magisk, and if you don't want to patch after updates you have to use xposed. This is because magisk is a systemless interface, not a runtime patcher.
[Nook HD, HD+ Android Development] twiztid_:
Thanks for the info. I wasn't sure if the NanoDroid patcher was like Tingle and something you had to do through PC then copy/push to device.

I uninstalled Xposed and went NanoDroid, and everything seems to be working fine. But needing to reflash every upgrade is a good reason to stick with Xposed, not that it's that big of a deal since you're already in TWRP (or CWM?) anyway.
[Nook HD, HD+ Android Development] amaces:
You probably meant something else, because that's not true; all ROMs preserve data upon upgrades. If you mean preserving parts of system, that not an AOSP feature. CM/Lineage, Omni, and a few other custom ROMs had addon.d/backup support for a long time, but it's not a standard feature. I'd be surprised if Samsung implemented their backup standard. At any rate, keeping selected files on system between block-based updates has many non-AOSP dependencies, and it's complicated to port.

The Go edition is really meant to go with Oreo. We're already using lots of similar things, including VM heap settings, zRAM, etc. The low_ram flag created many other issues in the past, but maybe they fixed it in Oreo. A few of the Go ART settings might be supported in Nougat, but that will require more testing. Either way, the fact that Lineage is in worse shape lately is their doing; AOSP has been consistently usable.
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION], LineageOS 15.1 is released. https://www.lineageos.org/Changelog-16/

will our Nooks be getting Oreo?
[Nook HD, HD+ Android Development] amaces:
Did I not emphasize that the roadblock so far is not Lineage, or even AOSP? We cannot use current DDK UM blobs, and new blobs are not legally available. After quite a bit of work, I've ported all the required parts (e.g., Binder, alarmtimer, timerfd, etc) to our 3.0 kernel (as well as to the unreleased K3.4); as soon as I'm able to use the new UM blobs (or somehow fix the current 1.9 DDK), Oreo builds can happen fairly quickly.
[Nook HD, HD+ Android Development] secretwolf98:
Ok, I understand about kernels. But what you said above, is beyond me, at this moment.
[Nook HD, HD+ Android Development] digixmax:
I just switched from LNOS to AOSP, and ran into this problem of WiFi auto reconnect after reboot or after turning WiFi off + on .

Removing the line "disabled=1" in wpa_supplicant.conf does not work for me (sometimes there is no such line in the file).
[Nook HD, HD+ Android Development] HarvHouHacker:
Well, this is a little off-topic, but I can explain what I have read and experienced. When you download a ROM from SamMobile, you get five .tar.md5 files. Two of them are CSC and HOME_CSC. If you flash the file with CSC in the name, it wipes your data like a factory reset. If you flash the HOME_CSC, it saves your data while installing new stuff around it. I found that out here on XDA Forums and on Reddit. I flashed HOME_CSC, and it kept my data, so I figure that it must be true. I'm afraid to test this theory in full, as I usually have a lot to back up, and the back up process is time-consuming. :( I'll see if I can find more info on this, but anyway, it's nice to know that flashing LineageOS updates will keep data.

As for preserving system, I suppose you mean whatever appears in the /system folder. I'm not so worried about that, unless I have turned user apps into system apps (i.e. Yalp Store from F-Droid), which I have. If I want to salvage those, I can either change them back into user apps, or save data associated with them, reinstall, and then restore the data.

So, you're saying that Android Go is only for Oreo, not Nougat and earlier? Just guessing; I'm not really sure what you mean by what you first said here. Anyway, it's good to know that you have optimized the LineageOS ROM to where it works well enough to work on the Nook, however it still has a few lag and app crashing issues like I have described before. I hope it can be worked out by implementing Go modules once they become fully available. Perhaps you could inject it into all your other ROMs, even the older CM ROMs that have various issues still. :fingers-crossed:
[Nook HD, HD+ Android Development] fddm:
I just tested this on amaces stable and UA nightly, the behavior is the same and both workarounds still work for me. I only have Ovation units to test on, past that, I have no idea why others have failed to reproduce this.

Here's a quick capture of the workaround:

http://www79.zippyshare.com/v/Mfpid3Km/file.html

You have to do this with each new network, but as long as you leave it alone, it autoconnects from then on.

Or you can just wait a bit. Once I get a successful build, I'm going to setup whatever android's equivalent of a ring0 debugger is and use it to find and nuke the offending code.

He's saying that we are already using a bunch of features that google is flaunting as 'new'. Got to temper those expectations or your just going to be disappointed if/when Oreo is ported over.
[Nook HD, HD+ Android Development] ST Dog:
[MENTION=3711980]fddm[/MENTION] any plans to update your Magisk changes for 16.0?

Have you considered a script to extract/combine the proper image so that it can be patched using Magisk Manager?
[Nook HD, HD+ Android Development] fddm:
[MENTION=5320537]ST Dog[/MENTION] I updated the original post with 16.0 when acclaim support was added:

https://xdaforums.com/showpost.php?p=75639041&postcount=2364

You can also check out this pull request for official support:

https://github.com/topjohnwu/Magisk/pull/375