yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] belfastraven:
Just curious here: I believe recommended way of building these roms is to run build/envsetup.sh, then lunch (not brunch) e.g. lunch lineage_ovation-userdebug, then " make otapackage " or "make bacon" (for lineage, if you wish) . (I usually run with j at twice the number of threads i have). I have not run into the busybox issue. I haven't looked at your pull request, but I just wondered if you had checked it for the AOSP builds as well as lineage?

---------- Post added at 11:20 PM ---------- Previous post was at 11:05 PM ----------

Just curious here: I believe recommended way of building these roms is to run build/envsetup.sh, then lunch (not brunch) e.g. lunch lineage_ovation-userdebug, then " make otapackage " or "make bacon" (for lineage, if you wish) . (I usually run with j at twice the number of threads i have). I have not run into the busybox issue. I haven't looked at your pull request, but I just wondered if you had checked it for the AOSP builds as well as lineage?
[Nook HD, HD+ Android Development] amaces:
This does look like a good idea, and a decent compromise that should be AOSP-compatible. Since GH's PRs bring extra cruft, I'll pick a version of this manually, hopefully for next builds.

Pretty odd since brunch is just a wrapper around breakfast and make, although I don't recall ever using it in Nougat. I generally use lunch on AOSP and breakfast on CM/Lineage, followed by otapackage, or other smaller targets, but will test brunch now. I see that both Lineage and Omni made changes in their respective BusyBox repos, but nothing very consequential.

Definitely not a stupid question; the root situation is fairly complicated now. Both AOSP and Lineage have some sort of SU included, and on the latter, I had also enabled its manager on clean builds (without that Developer settings toggling weirdness). That makes it trivial for apps to detect root, so I need to rethink how SU should be incorporated.

I need to test if SuperSU has fixed its system-mode on N. If so, I will stop incorporating SU by default (system-less will never work out of the box with our boot images). Ideally, people should be able to choose if they want root access enabled.
[Nook HD, HD+ Android Development] nsfgp:
Yes it works now!!! Sorry for late reply as I didn't have chance until just now. Loaded up latest your 4/24 LN and that stupid KTSF app works now!!! Thanks for helping with that really appreciate it.

Great ROM and super support. Thank you again Amaces!!!
[Nook HD, HD+ Android Development] drmarble:
I'm glad you like the patch for resizing system. It seems useful. I understand how ugly git pull merges are. I had the main working HP tenderloin cm-10 tree and had lots of pulls to merge in. That double commit looks strange and makes the history hard to read. I figured it was the easiest way to get the code for the patch to you.

The problem I have with brunch is the mka command it contains. It is supposed to be similar to a make -j(#threads) bacon. I don't know why the make command works and the mka doesn't. Building still works fine. I don't blame busybox, I blame something lurkingin vendor/cm/build/envsetup.sh. Specifically: mk_timer schedtool -B -n 10 -e ionice -n 7 make -C $T -j$(grep "^processor" /proc/cpuinfo | wc -l) "$@" .I'll investigate it just because it intrigues me. Using make instead of mka is fine.

Keep up the good work. You make this into a useful tablet with an excellent (but underpowered) display.
[Nook HD, HD+ Android Development] NE0HP:
At first I thought, reporting WiFi connectivity issues repeatedly could annoyed you but thanks for understanding, encouraging and providing possible fixes in form of providing new build to keep on testing and to rectify possible cause. I've dirty flashed new 04/24 build ovation over 04/18 build and this time WiFi doesn't connected automatically to even my non problematical WiFi hotspots and moreover it disconnected and reconnected automatically so often and completely unstable! I've even tried and RESETTING Network Settings but still no improvement. I've fetch the fresh logcats of 04/24 build right after WiFi got disconnected if that could help you to narrow down the issue.
[Nook HD, HD+ Android Development] dk1keith:
I know its in the thread as far as which build has stable wifi....is 04/18 still the only stable wifi build? My wifi issue was weak wifi...where it would be too weak and would disconnect. I'm on the nook hd+

thanks
[Nook HD, HD+ Android Development] amaces:
The devil is in the details as always; turns out that the specific OTA script facilities used are CM/Lineage extensions, and not easily adaptable to AOSP for the reasons here. Thus, I made this a Lineage-only feature, so AOSP will still need manual partition resizing after every ROM update, and before flashing extra stuff (that is, if you decide to enlarge /system). I haven't tested this change; hopefully it doesn't break anything.

That makes sense; it may be something they missed with older shells, Ubuntu distributions, etc. All in all, there are many benefits to dist-upgrading to current LTS.
[Nook HD, HD+ Android Development] myjess:
is there a cwm recovery for latest roms. personal preference.
[Nook HD, HD+ Android Development] myjess:
Apologies for posting again, and I know there is a lot more code from kitkat times, but the nook hd is real slow with lineage Nougat installed. Is it likely to be faster if I go back to lollipop?

Thank you.

---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------

last one tonight, I promise. Is there any app that will make the screen swing 180degrees on bootup?

In fact I see a line in /system/build.prop hashed out

#ro.sf.hwrotation=180

If I unhashed this line, would it help?

Thanks yet again.
[Nook HD, HD+ Android Development] drmarble:
Your version of this change works fine. My system partition went back to it's correct size.

My problem with using mka instead of make -jx is the make -C $TOP command. The -C modifier causes me problems with busybox. Maybe I should update from 14.04 to 16.04. I just stopped using mka.
[Nook HD, HD+ Android Development] zspeciman:
playing hayday or just surfing the net, the 4/18 flash does work flawlessly, as mentioned previously. The rest including the latest 4/24 loses connection. Thank you [MENTION=4473900]amaces[/MENTION] for the time and work you've put into this.
[Nook HD, HD+ Android Development] ajislav:
Ovation 20170415 build:

2% over 7 hrs with WiFi on (always on)

Edit: 7% over 22 hrs..

seems excellent to me as I usually switch WiFi off when device not in use
[Nook HD, HD+ Android Development] myjess:
Any information on the amount of RAM each of the installation uses by default with the pico gapps installed?

Thanks.
[Nook HD, HD+ Android Development] digixmax:
WiFi Connect Issue with LN 04/18 Build

Given two positive reports of WiFi connect performance of the 04/18 build I decided to give that build a try.

Unfortunately, 04/18 is a no-go for me:

- on my home network, the HD+ does connect but the connect response times vary widely, sometimes very fast other times quite slow but not quite as bad as 02/26 build

- on my work open network, the HD+ simply totally fails to connect.

So back to the 01/04 build I went.

A couple of observations from this attempt:

- Looking at the WiFi setting's display while the device attempt to connect, I noticed that the WiFi connect process following the establishment of connection to the WiFi AP tests for access to the Internet. This seems to be a new "feature" on the Nook, in past ROM builds only the apps can detect lack of Internet connectivity.

- I could not dirty-flash my way back to 01/04 from 04/18, luckily I had a backup of 01/04-based install to avoid a tedious restoration of my apps.
[Nook HD, HD+ Android Development] amaces:
Root on Current AOSP and CM/Lineage Builds

To avoid issues like above, and to have some flexibility, current builds don't include a real SU binary anymore, but I made it easy to restore it, as described in the FAQ:

On AOSP, I adapted phh's OSS backend for system-mode install (phh-su-arm.zip). You need the matching manager to control access. The binary needs to be flashed after every ROM update, same as GApps.

On CM/Lineage, you can install their official add-on (addonsu-arm-signed.zip); it will use the baked-in manager, so no extra APK required. Or, you can install phh's SU and manager, like on AOSP. Neither needs to be flashed more than once here given the existing addon.d support.

The odd thing now is that I don't know what makes those 04/18 builds special anymore… I incorporated pretty much all those changes, certainly in today's builds. Actually, those older builds had a mild kernel bug, although it made no difference with the default Wi-Fi always on. Thanks for the logs; nothing suspicious kernel-wise, and the logcat looks pretty much like mine, so am still confused.

That should never fail… Just tested an open network without any issue, which makes me wonder whether some hardware configurations are problematic. I can see one Wi-Fi setup for hummingbird, and three possible for ovation. Can people experiencing these connection issues post the output of adb shell dmesg | grep -i wifi\ configuration? Full logs are even better, of course.
[Nook HD, HD+ Android Development] netcsk:
You're awesome. Thank you! I'll give it a shot when I have some time to start from scratch (assume a format would be best to clear anything out).

By the way, my wifi connection is fine with no issues when it is strong, but does drop and has trouble reconnecting when it is slightly weak (well within range of any of my other devices). No big deal for how I use it.
[Nook HD, HD+ Android Development] ParadoxGBB:
Hello, Hummingbird user here.

I had the same WiFi connectivity issues with the LOS 3/21 and still for the 4/15 build (I initially connected fine but after reboot I couldn't at all) so have reverted back to the 2/28 build and I'm thinking about trying again with the flurry of builds mentioned recently. I can send logs if folks think it would help.

Not to derail too much from that discussion but I have a few questions that'd I'd love folks to weigh in on if they have the time (I suspect a lot of these have to do with LOS more than the specific device):

1) Does anyone have adaptive brightness working on LOS? It doesn't for mine and I seem to remember it working nicely with CM builds.

2) There's so much good work going on here, and there might have been a past discussion on this topic I haven't bumped into, but is there a reason why Hummingbird and Ovation (and maybe Acclaim) are not supported official builds of LOS? I understand that comes with a lot of scrutiny, but it seems like a lot of those here are doing really great work and debugging work that the rest of the community could benefit from. I'm not mentioning to criticize, but I'm curious what the reasons are from someone who has been reading about the behind the scenes changes that the collapse of CM and the rise of LOS has caused --- I'm sure I don't have the full picture.

3) Anyone else notice that Incognito mode doesn't seem to work in LOS's stock browser?

And of course it still must be (re)said that it's really awesome that these builds are awesome and does a great job of extending the life of old devices! Thanks so much amaces!

Thanks!
[Nook HD, HD+ Android Development] NE0HP:
Greetings!

Dirty flashed 04/27 ovation build over 04/18 and right after normal boot the device quickly recognised my all previous WiFi hotspots and connected automatically(No manual inputs needed to connect) and remain stable!

Now I can happily say....Finally WiFi connectivity is even much better than 04/18 build and much more stable. Thank you [MENTION=4473900]amaces[/MENTION] for all the hard works that you put into this issue!

Would be great if other ovation users can share their individual experiences of WiFi connectivity if they did dirty/clean flashing of new 04/27 build.
[Nook HD, HD+ Android Development] amaces:
A complete system format would do that, but I think deleting /system/addon.d/51-addonsu.sh (or the whole addon.d folder) and dirty flash should work equally well on Lineage. They also have an SU removal tool at https://download.lineageos.org/extras.

Logs are always welcome if these issues persist.

Adaptive brightness, or did you mean Live Display? We don't have a light sensor for the former, but the latter should be functional.

I added an attempt to explain the current situation in the FAQ.

Is the menu entry gone? Am using the same APK on AOSP, and Incognito seems to work.
[Nook HD, HD+ Android Development] zspeciman:
Haven't had much time to play with the 4/27 flash, but so far it looks smooth. When I install Greenify It no longer has root access. In the developer option in 4/18 there was root access and 4 options:disabled,apps only, adb only and apps and adb. In the 4/27 there are only 2: Disabled and ADB only. So Greenify on 4/18 when selecting devices is rooted proceeds, but in 4/27 doesn't.
[Nook HD, HD+ Android Development] myjess:
Guys, just want to thank you so much for all the help you have given me this past week. I am sticking with Lollipop for the meantime cos MM and NT are just too slow.

My 3 HD's and my HD+ thank you.
[Nook HD, HD+ Android Development] mikeataol:
on the ovation LNOS 427 build, I found after I installed phh-su-arm.zip, and the phh superuser apk, all the root stuff went back to normal. Apps and ADB was back.

I had been on a December build for a long time, this build so far has been flawless.
[Nook HD, HD+ Android Development] joefidler:
I did a bit of quick testing this morning on the April 27th LineageOS build:

- Wifi connection establishment is noticeably faster. Nice!

- I do see incognito mode in the default browser.

- For me the Live Display mode doesn't work. I have it configured to show a night color temp of 4900K, but it never seems to switch to this mode.

Didn't know there was that so much overhead in getting a device added to the "official" LineageOS device lists. Can well understand why Amaces took the path taken.

Considering that we may possibly never get online "repo" style updates we will be relying on flashing updates. In case anyone finds it useful I thought it might help to document a way to flash updates without swapping SD cards, which for me is more convenient. The first partition on my SD card contains the bootable image for ROM flashing, etc and the second is used by LineageOS for data storage. Not sure if this is already documented elsewhere or if this is not a recommended thing to do, but I have used it for the last couple of months and several ROM updates without issues. I am using Hummingbird and LineageOS but I think it will work for others.

Briefly:

1] I mount a blank micro SD card on a computer, and use a disk image tool creation tool (Fedora Image Creator, StartUp Disk creator, Rufus, etc ) to create a bootable SD card from the SDCARD-RECO img file for your device that A Maces has posted. I think this is the "normal" documented way to setup for ROM flashing on the Nook. This partition uses about 860M space on the SD card and this method only makes sense if you use an SD card bigger than this.

2] On the SD card there will (hopefully) be remaining space which can be allocated to data storage for the Nook/LinageOS. With the SD card still mounted in the computer, create a EXT4 partition using the remaining space, after the bootable image from step 1. I used the Gparted tool, but there are many disk tools that can do this. I do not know what other formats can be read by Android, and ext4 format may require a Linux computer to create.

3] Move the SD card to the Nook and start it. Use the Cyanoboot bootloader to select either: TWRP or Normal Boot (eMMC). The default on this menu is TWRP so you have to keep an eye on it and hold the "n" key to get a normal boot. Fortunately I don't have to restart of often as the device is becoming very stable. After the Nook starts normally it should see two external storages, the second which can be used for general use by the Nook's apps.

4] When flashing a ROM, the ROMs to be flashed go into the ROMs directory in the bootable first partition on the SD card, where TWRP can find them. I connect the Nook by USB cable to a computer to download and then copy the ROM to the NOOK, leaving the SD card in the Nook. Reboot the Nook and use Cyanoboot to select TWRP from the boot menu using the arrow keys and the "n" Nook button.

cheers.
[Nook HD, HD+ Android Development] ParadoxGBB:
This is the setting that looks at time of day and locale to change the brightness and color settings, basically replacing applications like f.lux. In earlier builds you could swipe down from the top to also manually toggle between day / night / candle, etc. When I install f.lux to try to replace this functionality that doesn't really appear to change the display either.

Thanks for this, very interesting.

I'm using LOS, and I do see the option, but there's a specific site that seems to remember my state between incognito vs. regular tabs (useful for when you need to log in via multiple accounts) --- I had assumed that meant incognito was broken, but it appears to be only that site, so never mind. In any case Chrome doesn't seem to have that problem.
[Nook HD, HD+ Android Development] zspeciman:
Both the addonsu-arm-signed.zip and the phh superuser seem to give an error from the TWRP side, saying zip failed. HOWEVER once you boot up and go to root you see all four option, they work!!!!
[Nook HD, HD+ Android Development] xflier:
Anybody could provide the link for phh-su-arm.zip, had trouble to find it in the FAQ. THX
[Nook HD, HD+ Android Development] mikeataol:
It's in the same box container as all the builds, just up one level

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww
[Nook HD, HD+ Android Development] digixmax:
Alternatively, one can create a bootable recovery SD card with one large boot partition to hold bootloader & recovery files, ROM/GApp updates as well as backup snapshots of system/data partitions -- see https://xdaforums.com/showpost.php?p=71339668&postcount=7. This alternative is especially useful for users of Win PC which by default can only mount the first partition of SD the card.
[Nook HD, HD+ Android Development] xflier:
Thanks a lot! Found another issue, Browser's history doesn't work.
[Nook HD, HD+ Android Development] mikeataol:
Yeah, that's been an issue for a long time
[Nook HD, HD+ Android Development] amaces:
To reiterate post 1873, and the FAQ, on Lineage, the lighter solution is their add-on, which can work with the built-in Privacy Guard manager. The other SuperUser backend and manager is pretty much the only OSS option on AOSP, and while it does work with Lineage, seems wasteful.

Lineage's ZIP does have that minor bug, but I thought I had fixed mine, at least it seemed fine with current TWRP. In any case, as you discovered, everything still gets installed.

In LiveDisplay settings, does forcing Night mode, or playing with the sliders do anything? While I haven't tested current Lineage builds, I didn't notice any changes to that feature that would affect us. As a side note, I don't expect f.lux or other third party app to work well (or at all) on these devices. For us, LiveDisplay works with an OMAP4 plugin that offloads the color temperature adjustments (TI's CPR in DSS), which is the only efficient solution on current GPU drivers. Anything based on GLES 2 or overlays will bring everything to a crawl (at least on the HD+).

Yes, the AOSP Browser has always been quirky (read unreliable) like that. This is the Browser app that was brought kicking and screaming from Marshmallow (with CM/Lineage enhancements); the Browser2 shell in AOSP N is not even a real browser anymore. They really want you to use Chrome.
[Nook HD, HD+ Android Development] neutronjeff:
Which TWRP are you currently using /recommending for your builds?
[Nook HD, HD+ Android Development] rtarv321:
The zips are working for me. I get error "4" in TWRP. I am going back and reread and try to figure it out. I perplexed, I have been flashing roms on this nook hd+ since early kitkat days with no problem with root.

---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------

---------- Post added at 08:55 PM ---------- Previous post was at 08:53 PM ----------

Sorry, should "are not" working for me
[Nook HD, HD+ Android Development] vinceweis:
I had some problems getting root without errors. I tried several things so I am not sure exactly which one fixed it, but I was using twrp 3.1 and went back to 3.0.1 that is in the ovation folder and root installed fine.
[Nook HD, HD+ Android Development] digixmax:
Which version of TWRP did you use?
[Nook HD, HD+ Android Development] nsfgp:
Please excuse me for asking Acclaim questions here but seems Amaces only comes here and most of the helpful posters are here and eager to help.

Please go to this thread and take a look and see if you can offer me any help with the Acclaim situation with Amaces's ROM:

https://xdaforums.com/showpost.php?p=72096266&postcount=5

Thanks and sorry again for cross posting here.
[Nook HD, HD+ Android Development] mikeataol:
replied there: https://xdaforums.com/showpost.php?p=72097460&postcount=6
[Nook HD, HD+ Android Development] NE0HP:
When flashing phh.su.arm using TWRP 3.1.0-0, its throwing error. So I downgraded TWRP to 3.0.3.0 and flashed phh.su.arm again and flashed ended successfully without any error! Root Access is back with all four option under developer options!
[Nook HD, HD+ Android Development] netcsk:
Thanks for the guidance and for doing this. Unfortunately even after trying a complete format, Vue still complains about root. It must be looking further into mod space rather than just root access/files. Adding root per your instructions from lineage worked fine for me (error that seemingly made no difference).
[Nook HD, HD+ Android Development] rtarv321:
I was using version 3.1.0-0. I flashed 3.0.1.0 and started as a new install. Still getting error 4 when flashing phh.su.arm. I tried several install methods, with no luck. I restored a backup from the 18th with TWRP. I guess at this point I will watch the forum for new builds & solutions. Thank you amaces & the rest of the team for all of your hard work!
[Nook HD, HD+ Android Development] digixmax:
I too got error messages flashing addonsu-arm-signed.zip using TWRP 3.0.1-0, but addonsu actually got installed just fine.

Did you check to see phh.su got installed?
[Nook HD, HD+ Android Development] rtarv321:
Thanks for the response, after the install, ran root check. It stated that the binaries were not installed. Couldn't figure out what & how at that point. Root check also shows busybox was installed correctly. I downloaded the phh- app from Google play, but that was useless. At that point I was trying anything
[Nook HD, HD+ Android Development] digixmax:
WiFi Connect Issue with LN 04/27 Build

I dirty-flashed build 04/27 -- WiFi connect performance improves significantly over that of build 02/26 but still inconsistent -- some times quite fast (but never as lightning fast as with build 01/04), other times still rather slow (but not as slow as with 02/26). Attached is the wlan-related output from dmesg for connection attempts to my home router.
[Nook HD, HD+ Android Development] NE0HP:
[MENTION=4473900]amaces[/MENTION] has added new addonsu-14.1-arm.zip http://bit.ly/amaces

I flashed it on my ovation using TWRP 3.1.0-0 without getting any error! Root access is back with all four option under Developer options!
[Nook HD, HD+ Android Development] rtarv321:
Thanks for the tip neohp! It worked perfectly. Amaces, you are brilliant. I deleted the addon folder within system folder. I dirty flashed the 4/27 Ovation build, today's pico gapps & the new addonsu-14.1-arm.zip. Installed with -0- errors & fully rooted. Thank you everyone that helped me, especially amaces for your hard work & continued support.