yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
Our roms have a built-in root, I believe. So even a full wipe and fresh install causes the app to detect Root.

I'll try the unSU, thanks. I think that's what I was looking for originally.

It's not using SafetyNet, it is finding the file (symlink) "/sbin/su" which is used to initiate super user permission.

I've tried to hide using MagiskHide, as well as the rename Magisk option, but it is still detecting Root (the file "/sbin/su"). If I rename that file I can use the app, but then I no longer have permission to rename the file back.
[Nook HD, HD+ Android Development] neutronjeff:
Can someone please remind me of the right keys to hold / sequence to boot to TWRP?

Hi I'm having a problem with a flash and need to get back to recovery. I'm holding "N" and volume "down" (away from the headphone jack) and it isn't going to TWRP.

Thanks Mike, I forgot we have to do power, not volume!
[Nook HD, HD+ Android Development] mikeataol:
yeah , the timing is a PITA

"just after" you press and release the power button, like just as you see its turning on, press and hold the Nook "N"/home button.

option 2 which I use more often:

I have found this works better if you have working adb

as soon as computer recognizes the system, while the LNOS or android logo has just started,

"adb reboot recovery" works
[Nook HD, HD+ Android Development] LBurdick43:
Just want to say thanks for the continued development after all these years. Great work!
[Nook HD, HD+ Android Development] rfrazier:
Build for 14.1 fails with current tree. About 70% of the way through.

nothing matches overlay file view_pager_tab_background.xml, for flavor v21
ninja: build stopped: subcommand failed.
make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1

[MENTION=4473900]amaces[/MENTION], if you're inclined to spend your available time working on newer versions, fair enough. I just thank you for the work you've done. I update for android security updates mostly, but none of my nooks connect much outside the lan these days. And, if I were really keen on building a new version of 14.1, and that is the only error, I could, I suspect, get it to work.

Best wishes,

Bob
[Nook HD, HD+ Android Development] belfastraven:
Its actually helpful to realize that the build failed before the lines that you gave us. If you search the output with an editor, you will see FAILED before a long command string and then usually the error message, prefaced by "error, after the long multiline command. The build stopped about 11 days ago, for me, This seems to be the commit that broke it: https://github.com/LineageOS/android_packages_providers_DownloadProvider/commit/715c24acbe82ab1cc0dfe6be60dd0487d111dc46. Note the proposed fix in the comments. The fix works for me. I don't understand why more others have not come across the problem Maybe [MENTION=4473900]amaces[/MENTION] can shed some light on this.

I can't tell whether that is the same problem you are having, but using that fix, I just synced and built with no problem. FWIW
[Nook HD, HD+ Android Development] Nemesis1278:
[MENTION=4473900]amaces[/MENTION] I finally gave in and did a fresh install. Wiped everything and so far day 4 and its working well. An app crashing here and there, but the system is holding steady so far and it is smooth. I'm guessing installing over the old system kept something in memory that was really screwing with the system.
[Nook HD, HD+ Android Development] amaces:
Will take a better look at it, but I've been working on redoing manifests and preparing to integrate some of the good O/P bits into the N builds. My 14.1 builds don't fail, which suggests that current GH manifests have fallen behind again. Hopefully, I can push the new manifests before the weekend.

Didn't give up on Nougat; pretty much all improvements go back into the "stable" 7.1/14.1 builds. I'd like to cleanup sepolicies, and enable Enforcing (to be able to pass SafetyNet) before the next set of builds (with new SGX drivers).
[Nook HD, HD+ Android Development] Zippy Dufus:
Kernel change?

Did something change with the kernel?

I build using my build-it-yourself Linaro toolchain which has worked for as long as I can remember. But now I have a problem.

I did some snooping and see that the 'stable' branch is used while I thought that it used ng-14, so I remember.

HOSTCC scripts/genksyms/lex.o

UPD include/generated/utsrelease.h

Generating include/generated/mach-types.h

CC kernel/bounds.s

cc1: warning: switch -mcpu=cortex-a9 conflicts with -march=armv5t switch

cc1: warning: target CPU does not support unaligned accesses

/home/android/kernel/bn/omap/kernel/bounds.c:1:0: sorry, unimplemented: Graphite loop optimizations cannot be used (isl is not available) (-fgraphite, -fgraphite-identity, -floop-nest-optimize, -floop-parallelize-all)

/*

make[2]: *** [/home/android/kernel/bn/omap/./Kbuild:36: kernel/bounds.s] Error 1

make[1]: *** [/home/android/kernel/bn/omap/Makefile:1013: prepare0] Error 2

make[1]: *** Waiting for unfinished jobs....

HOSTCC scripts/genksyms/parse.o

CC scripts/mod/empty.o

cc1: warning: switch -mcpu=cortex-a9 conflicts with -march=armv5t switch

cc1: warning: target CPU does not support unaligned accesses

/home/android/kernel/bn/omap/scripts/mod/empty.c:1:0: sorry, unimplemented: Graphite loop optimizations cannot be used (isl is not available) (-fgraphite, -fgraphite-identity, -floop-nest-optimize, -floop-parallelize-all)

/* empty file to figure out endianness / word size */

make[3]: *** [/home/android/kernel/bn/omap/scripts/Makefile.build:306: scripts/mod/empty.o] Error 1

make[2]: *** [/home/android/kernel/bn/omap/scripts/Makefile.build:441: scripts/mod] Error 2

make[2]: *** Waiting for unfinished jobs....

HOSTLD scripts/genksyms/genksyms

make[1]: *** [/home/android/kernel/bn/omap/Makefile:516: scripts] Error 2

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

make: Leaving directory '/home/android/kernel/bn/omap'
​
[Nook HD, HD+ Android Development] amaces:
New 7.1/14.1 Builds

The new builds in experimental incorporate the new SGX drivers, have sepolicy changes for Enforcing, plus other smaller fixes. If you don't install the root addon, it should pass SafetyNet. If you do install it, you need to temporarily disable the SU daemon (with setprop persist.sys.root_access 0 on AOSP, or from UI on Lineage) to still pass SafetyNet. The kernel hides the SU binary if it's not running. Basically, triggering SU with persist.sys.root_access of 1 or 3 (default) will make SafetyNet fail (and any app that uses this API). Having the addon installed, but not active, will not.

Magisk works differently, and in practice it might be simpler. If I'm not mistaken, there are modules that hide SU even when it's running.

There's no built-in SU for apps; the binary you find on a clean install is only usable in an ADB shell, and shouldn't break SafetyNet (likely used by your app). The kernel hides SU binaries when not loaded. What we were missing until now was SELinux Enforcing and CTS-compatible build fingerprints. Read above if you decide to install the root addon.

Even if your app is doing its own thing (not checking SafetyNet), it should still be OK for the reasons mentioned earlier.

I've redone the two Nougat manifests as a less intrusive layer on top of the respective upstreams. Not sure if they fully work (I'm forced to use a slightly different setup), but either way, you need to re-sync, or maybe even better, repo init after deleting old checkout (assuming you haven't made changes that you'd like to keep).

Nothing changed in kernel for a while, except a few tweaks for video playback with the new SGX drivers (and those happened after you posted, I think).

We've been using one stable branch for a long time. Maybe it's related to the recent manifest changes. I used to fork a lot more repos, including the arm-eabi- toolchain. It's now back to the Google 4.8 default, but the current device trees and kernel should work nonetheless. You might need to adjust how you're forcing your own kernel toolchain.
[Nook HD, HD+ Android Development] belfastraven:
I have the new buildfir lineage hummingbird build installed. It runs fine except that for the initial install, 1. initial setup is "upside" down (no biggie :) ) and rotation doesn't work until after setup

2. the wifi connection is lost at a reboot (but can be reset).

I have installed magix, and am happy to see if SafetyNet applications run, if anyone can tell me what app to try.. I know that Netflix will at least start and ask me to log in....

I will try rebuilding later--last night I reinited and resynched, but although I could build, the build stopped at the bootlader. I will delete all source and reinit/resync tonight and try again.

This is all very exciting. Thanks !
[Nook HD, HD+ Android Development] rfrazier:
Thanks. I sign with my own keys, and use a local OTA server. In any case, it doesn't build after --force-sync, even after making clean. I'll try a new init later.

Best wishes,

Bob
[Nook HD, HD+ Android Development] belfastraven:
after deleted my local copy of repo, re-initing and resyncing, build fails here:

device/bn/common/overlay/cm/frameworks/base/packages/SettingsProvider/res/values/defaults.xml:26: error: Resource at def_accelerometer_rotation_angles appears in overlay but not in the base package; use <add-resource> to add.

hummingbird, of course :)

Build will complete if I comment out problem section. ( I wasn't sure with <add resource> what to call the "app" that the resource to which I was adding)
[Nook HD, HD+ Android Development] amaces:
AOSP or CM/Lineage?

Ah, was trying to avoid forking f/base in manifests, and I forgot about this dependency. I removed it for now since it can enabled from UI on Lineage, and AOSP should be fine.

Otherwise, are your homemade builds fully bootable with the new manifests?
[Nook HD, HD+ Android Development] rfrazier:
Thanks. I'm using the Lineage version. It builds now, but doesn't boot. This is just with a --force-sync. I'll try it again with a new tree this later.

Best wishes,

Bob
[Nook HD, HD+ Android Development] drmarble:
I reverted the offending commit from frameworks/base (zwlieu? I think) and got a build. It failed to boot. I didn't get any boot animation. adb logcat said nothing. I lost twrp somehow from that but my trusty bootable sdcard and restored boot and system. I resynched with your modified bn/common and am building now. I will flash this and will try to see if adb will tell me something.

I flashed your rom. It seems to work fine. logcat isn't whiney. Netflix is visible on Play Store. Seems fine.

Thanks for your work on these devices. You are keeping them useable. I finally gave up on Encore. 14.1 was barely useable without gapps. My Acclaim is loosing its emmc and spends all its time in i/o.

The ovation is still a great comic book reader. Thanks again.
[Nook HD, HD+ Android Development] belfastraven:
Lineage not bootable (cm-14 branch right?).

I have attached a logcat and dmesgy. Seems to be complaining about pvrsvr stuff.. and audioserver, cameraserver, etc.

I will try AOSP, but if these are device or hardware issues, I imagine their will be the same problems.
[Nook HD, HD+ Android Development] neutronjeff:
New 10.1 ?

You guys have been doing a fantastic job keeping us alive, but I gotta say I'm tempted.

BRAND	Nook

MODEL	BNTV650

PLATFORM	mt8167

API	8.1 (27)

WIFI	CONSYS_MT6630

CPU	MT8167A

CORES	4

FAMILY	Cortex-A35

CLOCK_SPEED	598 - 1500 MHz

RAM	2 GB
[Nook HD, HD+ Android Development] amaces:
Great, and if you need to test SafetyNet, look for a tester such as https://play.google.com/store/apps/details?id=com.atominvention.rootchecker. Also, the dreaded GFX underflow situations should be gone for good.

P.S. For people who resize system, it now happens automatically on AOSP as well (TWRP tested, other recoveries might lack some dependencies).

Hmm, in my quest to keep forks at a minimum, but also do my thing locally, I missed something in the PVR KM build. It should be fixed now, and theoretically only hardware/ti/omap4 needs to be re-synced.

I also reverted the extra overlay symbol from device tree, so f/base can be kept pristine.

I need to look at updated acclaim builds as well.
[Nook HD, HD+ Android Development] Zippy Dufus:
Completed build but unbootable

I've sorted out my previous issue. You were correct that the change back to 4.8 messed up my deployment of my tool chain. I should have spotted this before posting, duh.

I did get a complete 11/21 Lineage 14.1 build with my toolchain but it hangs at the cyanoboot screen. In don't know if I am master of my own misery or if there is an issue with the program code.

Oh well, I'll monitor this thread and try again later.
[Nook HD, HD+ Android Development] belfastraven:
Yup -- this pvr-km/init: [FIXUP] Conditionally load PVR KMs from root seems to have fixed build. I have built and am running. thanks.

P.S. I am unable to sync nougat-- even with --force-broken.

lots of meesages like

atal: not a git repository: '/home/mlp/nougat/.repo/projects/external/libphonenumber.git'

fatal: not a git repository: '/home/mlp/nougat/.repo/projects/external/lld.git'

error: Cannot fetch platform/external/lld
[Nook HD, HD+ Android Development] drmarble:
I resynced to get your latest pvr changes. I rebuilt, flashed and it works fine now. Color me impressed.

Thanks again.
[Nook HD, HD+ Android Development] rfrazier:
I too resync'd, and hummingbird built and booted just fine. Building ovation now. Both Lineage OS. Many thanks!

Best wishes,

Bob

PS Ovation built as well.

RLF
[Nook HD, HD+ Android Development] belfastraven:
Just inited and synced nougat, built successfully (aosp_hummingbird) and am running successfully on nook. Interestingly, though, magsdk's safety check fails for ctsProfile. It was successful on the lineage rom. ...
[Nook HD, HD+ Android Development] secretwolf98:
:Thinking:

I need one now.
[Nook HD, HD+ Android Development] amaces:
You're running your own AOSP build, whereas you tested my Lineage build maybe? I haven't pushed the fingerprint override commits in the two device trees yet. I did notice that the test can fail occasionally on legacy devices (hammerhead included), even with all dependencies met. Retries are usually fine.
[Nook HD, HD+ Android Development] belfastraven:
Actually, I thought I had tested my own lineage build, and both tests were passed, but having tried 4 roms in the last 24 hours I could be confused..:). I'll wait until you have pushed the changes to the repos and try again.
[Nook HD, HD+ Android Development] ales-76:
Not able to become superuser

Hello, I did clean install of latest AOSP Nougat for Ovation (aosp_ovation-ota-N2G48H.181120.zip) along with OpenGapps pico and addonsu-14.1-arm.zip from Amaces site. It works fine, but I am not able invoke su from terminal and I have no clue how to unhide it. The addon installed successfully, persist.sys.root_access is set to 3. Can somebody hint how do I unhide su binary for terminal app?
[Nook HD, HD+ Android Development] mikeataol:
This may or may not help, in developer options, set root access to off, exit settings, and go back and set it back on for apps and ADB.

I do that out of habit on install because at one time it needed to be done for root to work correctly.
[Nook HD, HD+ Android Development] ales-76:
Thanks, but on AOSP there is no such an item in Developer options. From what I can remember this was only LNOS thing.
[Nook HD, HD+ Android Development] belfastraven:
Using [MENTION=4473900]amaces[/MENTION] AOSP build but with magisk, root and root hiding seem to work fine. You might want to try that.
[Nook HD, HD+ Android Development] Zippy Dufus:
A working Lineage 14-1 build?

Anybody been able to build a working Lineage 14.1 ROM lately?

I see recent comments that such ROMs are not bootable but it is unclear with intermingled discussion of the AOSP builds if this issue is resolved for Lineage.

I built a 11/24 ROM with my own Linaro gcc built and it was not bootable. So I did built a 11/25 unadulterated ROM and it booted but it crashed at the startup screen and I could not proceed forward (perhaps I should have tried without flashing gapps). Both attempts were clean installs where I explicitly wiped (reformatted) the caches, data, and system partitions.

So I did a clean install of by last good build, Linaro 09/26, and it is working fine.

However, I am suspicious that my old nookhd, which has been flashed countless times, may have a hardware issue:

I originally was motivated to do a new build because root on my 09/26 build mysteriously stopped working. It is working again after a clean install.

A dirty flash of my 09/26 build over the failed flashes of the new builds was not bootable. I needed to do a clean flash with the wipe described above.

TWRP 3.2.1 is unable to restore either 3.1.1 or 3.2.1 backup to a bootable state.

Anybody ideas?
[Nook HD, HD+ Android Development] rfrazier:
I have ovation and hummingbird Lineage OS 14.1 builds from Nov 22nd, which both work. (Nothing to do with me, gov. All down to [MENTION=4473900]amaces[/MENTION]' work.)

I'm using the standard build toolchain (Lineage instructions for building). It is also the toolchain I use for LG g5 (lineageos 15.1), Samsung Tab S 10.1 (lineageos 14.1), Samsung Note 8 (lineage 14.1), and Samsung Note II (lineage 14.1, which is only used as a music player).

The only changes I make to the Nooks' ROMs are signing them with my own keys. Although I run my own OTA server (on my LAN), I don't even have to change the build tree to do this (I discovered). The address for my OTA server is put in /data/local.prop, which is persistent. The only ROM to which I make any significant changes is the phone one (LG g5). But, I thought that since I'm building that, I might as well build everything. In addition, I like the idea of them being signed with my keys.

Best wishes,

Bob

PS. The recipe for the OTA server is at the following URL

https://github.com/julianxhokaxhiu/LineageOTA.

RLF
[Nook HD, HD+ Android Development] belfastraven:
I've successfully built and booted both lineage and nougat for hummingbird (using the standard tool chains) a couple of days ago. I did bring up the roms before flashing gaps or magisk. Can you get a logcat or run dmesg from the system while it is trying to boot (that will of course depend where things are failing)? If the EMMC is going, you may be able to tell from the logs. II will try again today to pick up the latest repo change but don't expect any problems.
[Nook HD, HD+ Android Development] amaces:
Took a while, but remembered to do it :)

Hmm, we may be missing some sepolicy bits required to run the addon under Enforcing. Honestly, I forgot to install it during testing, but I will work on it this week. The Lineage builds should be fine since they have those sepolicy changes commonized already, so I just need to port them to AOSP N.

Are you changing only kernel toolchain, or userlang GCC and Clang as well? The kernel tree itself is ready for GCC 4.8 through 8.2, but the manifests don't include the many changes required for newer userland compilers; those are scattered throughout my other GH forks. Otherwise, my builds use 8.2.0 for kernel, and GCC 7.2.1/Clang 8.0.4 for userland.
[Nook HD, HD+ Android Development] Zippy Dufus:
I'm doing both, I've built both the gcc linaro 7.2 arm-eabi for the kernel and arm-linux-androideabi for the rest of the ROM. I removed your gcc prebuilts and created links to my toolchain which resides elsewhere. Additionally, I have a few patches which change TARGET_linux-arm.mk and your BoardConfigCommon.mk to point to the swapped-in toolchains. I've been doing this since gcc linaro 4.8 and building for each new version is always a (fun) challenge.

Interestingly, I believe that clang now is used to compile most of the non-kernel part of the ROM but a few bits may still be compiled by gcc. I don't touch the default clang compiler.

I've only managed to re-flash my last working linaro 7.2 build while even a straight, non-adulterated build would boot but crash tying to load the setup program. I've been having other weird issues with my nook so I'm very suspicious that it now old and is having hardware issues.

Meanwhile, I pivoted back to building my phone with a newer 7.3 linaro build which worked fine. I'm going to swing back to the nookhd and try another straight build and see if I can catch a logcat if it is bootable but misbehaving. If it does work, maybe I build a 7.2 or 7.3 kernel and flash that separately to see what happens.

Regardless, thanks for all your efforts with the nookhd (and acclaim - my last acclaim build was yours or unlegacy). Both have generally been working fantastically!
[Nook HD, HD+ Android Development] hemeboy:
Wifi

Latest LNOS build for Ovation working really well. is there any fix for losing wifi connection on reboot & having to manually reenter password each time?
[Nook HD, HD+ Android Development] mikeataol:
i recall something like connecting to a second wifi fixes the remembering, but i havent tested lately.

what i do is put it in airplane mode before rebooting or shutting off, taking airplane mode off when it restarts, and that seems to be working
[Nook HD, HD+ Android Development] ales-76:
It is annoying, but there is a fix. Somebody in this thread before recommended to disable Wi-Fi scanning in Settings>Location>Scanning and manually editing /data/misc/wifi/wpa_supplicant.conf, putting disabled=0 in the network section. I am not sure if both are absolutely required, but I do both after each clean install and then the Wi-Fi reconnects after each reboot.
[Nook HD, HD+ Android Development] hemeboy:
That worked; I needed to do both change the settings and edit the wpa_supplicant file. Thanks,
[Nook HD, HD+ Android Development] Merazomo:
I'm using LineageOS 14.1 at this moment on my Nook HD+, and it's been running great so far. I don't know if it's something that only happens with my Nook though, but whenever I turn off WiFi overnight, the first 3-4 minutes after I turn it on the next day, the tablet is very sluggish and laggy to a crawl; only for the first 3-4 minutes or so. I never have issues connecting to WiFi, loosing connection, reboot issues, etc. It's only the first few minutes after a long time of turning the WiFi off that I have this annoyance.

Does anyone have the same issue on their Nook? Or is it just me?
[Nook HD, HD+ Android Development] twiztid_:
Is this only for after reboot?

I'm looking for a fix/workaround for the Wifi being "dead" after sleeping (when you turn off Always keep WiFi on), forcing you to turn off WiFi then back on and have to re-enter your password.
[Nook HD, HD+ Android Development] MYEUHD:
Are there new available DDK blobs for PowerVR SGX540?

Or are the new ones just for SGX544?
[Nook HD, HD+ Android Development] amaces:
Another Try with Updated WiLink Drivers

The updated Wi-Fi drivers should work better than in the past, and are included with today's Nougat builds. These are based on the K4.4 cfg/mac80211, and R8.7 SP3 wlcore/wl12xx. Our previous K3.2-based drivers are falling apart, so I'm hoping we can drop them permanently.

The updated Wi-Fi stack might help, but it's also possible that your transient issues are due to the avalanche of network requests that happens upon reconnecting. There aren't many reasons to turn Wi-Fi off overnight; the drain directly caused by it is pretty small, and the system still wakes up every few hundreds of seconds to check on things.

The current blobs and matching KM in the hardware repo cover both series, so all OMAP4 GPUs (4430/60/70). Beyond our 4470-based Nook HDs, they were tested on tuna (4460/K & N), as well as acclaim (4430), so I'm reasonably confident that other OMAP4 devices can use them.

To use a 7.x arm-linux-androideabi, you need some of these bionic patches: https://github.com/airend/android_b...~3...e2397ad393678a536654287b81099213fbe4630d, and possibly others in the repos that were forked before.

Yep, much of the userland is built with Clang even in Nougat.

You can always check with the builds published here.

Kernel should be fine with any 4.8-8.2 GCC (the bare-metal/none EABI at least), so try reverting to the official 4.9 arm-linux-androideabi.