yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Zippy Dufus:
Bad luck building

I built a 04/18 ROM and the WIFI would not connect.

So I built a 04/20 ROM and the setup wizard crashes at the second step Set up as new.

The only thing that I did differently (that I am aware of) is build with the environmental variable WITH_SU=true

I'll keep trying when I notice change in the repos.
[Nook HD, HD+ Android Development] webman2k:
Thanks for the reply. I flashed the latest TWRP and your 4/19 build this morning. I'll let the battery run down and charge it up, and let you know if I see a difference.

Weird thing occurred - I rebooted into recovery 3.0.1, then flashed recovery 3.1.0 (official ovation release from the TWRP site), rebooted into the new recovery and flashed the 4/19 build, followed by a wipe cache. After I rebooted, I found Launcher 3 enabled (previously disabled), and I can no longer disable it (I do have Nova set as the default, so that's fine). I tried Power > Restart, and it booted me into recovery (?). Restarting from recovery put me back into AOSP. Did something change with the power menu in this build?
[Nook HD, HD+ Android Development] dbrickg:
Can't speak for the AOSP build, but I just flashed the 4/19 lnos build, and Power > Restart gave me the usual options (Power off, Restart, Airplane mode), and touching Restart got me a further menu with Restart, Soft restart, and Recovery. Are you saying that touching "Restart" after pressing the power button immediately booted you into recovery, without any further options?
[Nook HD, HD+ Android Development] webman2k:
That's what happened. In AOSP, there are no nested options in the power menu, just Reboot and Power Off. Both are supposed to just restart the machine, due to a bug causing the Power Off not to work properly. It did reboot, just went right into recovery. I then rebooted in recovery and it went to AOSP. Tried reboot again and it went as expected into AOSP. Just wondering if it's because I have just flashed a new recovery/ROM/cleared cache that this happened. Not too worried about it, but it was odd to see.

A note to anyone interested, because believe it or not I couldn't find this, you can boot into recovery from a power off using the hardware home button and the volume down button on the Nook HD+
[Nook HD, HD+ Android Development] digixmax:
Does AOSP have a "Advanced Restart" option setting menu in Settings->"Developer Options"?

You should be able to boot into recovery by pressing and holding the Nook Home button and Power button until a second or two after the Cyanoboot Universal Bootloader appears.
[Nook HD, HD+ Android Development] rtarv321:
I use an app called "quick reboot". Tap the app & you can boot to recovery or reboot normal, & a couple of other choices. I never use the buttons
[Nook HD, HD+ Android Development] Zippy Dufus:
Good build luck, rather!

The trick was to flash the ROM only first. Reboot and setup, then flash GApps. The Google setup dialogue will appear the first time you access PlayStore.

WIFI is working great too!

Great work again, [MENTION=4473900]amaces[/MENTION]!
[Nook HD, HD+ Android Development] webman2k:
No. That's a feature from CM/LN. OP stated that it may be brought over in the future.

Confirmed. Guess I didn't need the volume down. When I tried it alone the first time I probably got the timing wrong, thanks.

On that note, I can confirm that the odd reboot menu issue persists. I'm running TWRP 3.1.0-0, and the 4/19 AOSP amaces build. When I bring up the power menu, pressing "Restart" reboots and takes me directly into TWRP. Rebooting system from TWRP takes me back to AOSP. If I choose "Power Off," The tablet reboots into AOSP (due to the known bug). I must say, it's convenient to have this function, but surely it's not desired ;)

Any ideas?
[Nook HD, HD+ Android Development] drmarble:
I am encountering build errors. I have lots of experience building LineageOS and cm. I am currently building for encore (NookColor, the HD+'s grand father). My system is a fairly standard ubuntu 14.04 system with updated java for LineageOS-14.1 building. I started new repos, Lineage and AOSP in new directories, ran: . build/envsetup.sh; lunch ???_ovation-userdebug and build (mka bacon or make -j9 otapackage). I get an error:

FAILED: /bin/bash -c "make -j4 -C kernel/bn/omap O=/home/david/SHARED/AOSP-Nook/out/target/product/ovation/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/usr/local/bin/ccache /home/david/SHARED/AOSP-Nook/prebuilts/gcc/linux-x86/arm/arm-eabi-4.9/bin/arm-eabi-" headers_install"
make: Entering directory `/home/david/SHARED/AOSP-Nook/kernel/bn/omap'
CHK include/linux/version.h
HOSTCC scripts/basic/fixdep
gcc: error: unrecognized command line option ‘-fdiagnostics-color’

I patch the kernel make file to remove -fdiagnostics-color and I get the error:

scripts/genksyms/lex.o: In function `yy_scan_bytes':
lex.c:(.text+0xdc4): undefined reference to `GOMP_parallel_start'
lex.c:(.text+0xdd3): undefined reference to `GOMP_parallel_end'
scripts/genksyms/lex.o: In function `yy_scan_bytes._loopfn.0':
lex.c:(.text+0x2b96): undefined reference to `omp_get_num_threads'
lex.c:(.text+0x2b9e): undefined reference to `omp_get_thread_num'
collect2: error: ld returned 1 exit status

I feel that I am missing something obvious (compiler version or some such thing) but I can't figure it out. I read all this thread and googled extensively and have not found any solution.

Otherwise, flashing your rom is working great.
[Nook HD, HD+ Android Development] belfastraven:
I have not had this problem building--I know that that color option is supposed to work with gcc 4.9 and later, which is the cross compiler you are using according to the code. I don't know what Encore uses to build, but is it possible you are picking up code from your Encore builds, maybe from an uncleared ccache, if you are using a "global" ccache? I would try building without ccache before doing anything more drastic.

Oh--how soon I forget: I had a problem like this when I first started to build, and it turns out that the host gcc needed to be updated to at least 4.9 https://xdaforums.com/showpost.php?p=64429909&postcount=166
[Nook HD, HD+ Android Development] NE0HP:
Sorry for the delay in updating you about lnos ovation 04/19 build as I was occupied in some other works!

I dirty flashed 04/19 over 04/18 today and the WiFi connectivity seems to giving trouble again and couldn't connect automatically even after Resetting Network Setting. I've took back up of 04/18 so I restored back the device to the 04/18 build and faced no WiFi connectivity issues! For me 04/18 build works much better than over 04/19 build If considered WiFi connectivity!
[Nook HD, HD+ Android Development] drmarble:
Thanks, it was my gcc4.8. I updated to gcc-4.9 using these instructions: https://askubuntu.com/questions/466651/how-do-i-use-the-latest-gcc-on-ubuntu . It gets past both build errors. The build is still failing at the end with some odd busybox error. That sort of error I understand. I wouldn't expect the host gcc version to have any effect since the build provides its own gcc version, two of them, in fact.

Thanks for your help. I am refilling ccache as I type.
[Nook HD, HD+ Android Development] amaces:
Interesting, it seems that in your case the previous WiLink 6 firmware works better with the new drivers than the dedicated WL 8 fw-5 from here. Since both sets seem to work equally well in my testing, and are at same revisions, I will use the previous blobs with the new drivers, which was the main change in the 04/18 builds. Now, you were keeping Wi-Fi always on in both cases, right? I guess we'll know for sure if firmware is indeed the main culprit once people have a chance to test the refreshed builds.
[Nook HD, HD+ Android Development] starbright_:
Regarding the not behaving touch and slow response:

Probably never waited long enough ;)

Interesting - thanks for this feedback. It happens only once a while, so it is hard to trigger. I am not sure if this is just the touch driver. The device becomes slow too. It feels a bit like a memory leak or a mixed issue - as I run only a very limited number of apps.

The few times I have observed it, was after a while of using.

Has it become to risky or why the firmware is not updated anymore?

Regarding to power off issue. Right now it has worked fine. Usually I switch it only off (or better say try this) if the power is already low - to avoid I get wake up by an power alarm message.

Would it possible that power off doesn't work as good if power is low? I have to check this mor often.

---------- Post added at 08:23 AM ---------- Previous post was at 07:36 AM ----------

I observed something funny, not sure whether bug or feature. I did my last complete wipe and reinstall with upcoming LOS build. Maybe I did it in other orientation as usually. But from that time the screen orientation is rotated 180°.

To make it clear - automatic screen rotation works fine. Usually I limit this to 0 and 90° for either portrait or landscape mode. But I have to limit it to 180° and 270° as otherwise the portrait mode is overhead ?!?

Its not that this bothers me much, but at the begin I was estonished ...

Is there a configurtion file for the default orientation, what might be set wrong?
[Nook HD, HD+ Android Development] myjess:
Apologies, but there is no way I can drill through 183 pages, so if someone would be so kind to point me in direction of installation instructions coming from cyanogenmod already installed, I would be most grateful.

Thank you.
[Nook HD, HD+ Android Development] starbright_:
Fairly simple if you have TWRP already onboard. Difficult to describe, as we don't know your knowledge level.

Download TWRP and LOS image (ovation) from the link in OP - don't forget gapps if you like and sudo plugin from LOS download homepage (to find under extras/general).

Flash newest TWRP as a Zip, reboot into recovery again. You can try just to flash over (depening on CM version) or make a clean install (preferred - but you have to reinstall and configure each and everything again).

Flash the newest LOS image linked in OP. If you want to flash GApps, reboot into recovery again and do it.
[Nook HD, HD+ Android Development] digixmax:
See https://xdaforums.com/nook-hd/general/how-to-updating-nook-hd-internal-emmc-t3562818 and https://xdaforums.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810 for guides on process for installing LN14.1 coming from CM and from stock ROMs.
[Nook HD, HD+ Android Development] webman2k:
Netflix video quality

on 4/19 AOSP - Netflix videos play perfectly, but the quality is less than I'd expect (not 1080, not sure if it's even 720). I can confirm video from other sources play HD and crisp, like Youtube and Kodi. Is this just Netflix limiting playback on this device due to the specs? This is the latest version from the Play Store. Thanks for any help you can provide.
[Nook HD, HD+ Android Development] amaces:
I have a hunch that it's not about touch driver, but rather about tiler allocation issues, which tend to happen often after switching secure input to dynamic tiler. I guess I should revert those changes, but we'll lose 48MB of general memory. Hopefully, zRAM will be able to hide that loss well enough.

The new touch driver doesn't have the sysfs interface for uploading new firmware, but we weren't using that even with B&N's old driver, so nothing lost.

Yes, once battery voltage drops below a certain threshold, bad things are much more likely to happen. Still, that shouldn't be a worry above 15-20%.

Not sure I'm understand your issue correctly, but the only time screen is locked in that weird upside down orientation is during boot animation. It's only noticeable on hummingbird, but incorrect panel mounting affects both devices. Anyway, the accelerometer will reorient screen properly once lock screen comes up, and sensor events should be much snappier after recent HAL fixes.

If that's not your experience, you should describe what happens on your device.

Is this a recent change you noticed? I did make some codec changes trying to address tiler allocation failures, but I thought those are only in the 4/21 builds.
[Nook HD, HD+ Android Development] webman2k:
I've only tried Netflix on this build, so I can't comment on that. It's clearly lower than 720p after some recent tests. Would your changes only affect Netflix?

---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------

General question: if you have gapps installed, and you flash an update rom, should you flash gapps again as well after flashing the update? I found that after I flashed an update by itself I lost gapps. Flashing gapps fixed it.
[Nook HD, HD+ Android Development] amaces:
Generally no, but in this particular case, at least a couple of issues are possible. I imagine that Netflix asks OS to report capabilities, then serves stream it deems optimal, so codecs with weird properties might not get handled well. And unfortunately, our HW-accelerated codecs lack adaptive playback, which we've worked around since LP at least. If Netflix added more software (lower quality) codec fallbacks recently, it's possible those get selected rather than our Ducati-backed ones.

It would be interesting to see if any differences with the CM/Lineage builds, where additional FFMPEG-based codecs are supported.

Another difference between AOSP and custom ROMs such as Lineage, which have backup (addon.d) support. Normally, you always re-flash anything that modifies /system after updating ROM, but addon.d scripts will restore GApps if proper support is there.
[Nook HD, HD+ Android Development] webman2k:
Thanks for the replies. I would see if there's a modified Netflix app floating around that forces hardware hd playback.
[Nook HD, HD+ Android Development] starbright_:
In fact this is an minor, minor issue, so I just posted this for curiousity, and maybe my first conclusion was wrong.

I again checked that and come to the conclusion, that just the default orientation is moved from portrait (CM) to landscape (LOS). Maybe it is not dependend on OS but on TWRP, no idea. For those who enable all angles in automatic screen orientation this is not noticable at all. I think there is really no action needed.

Don't understand much of the internal details about this "switching secure input to dynamic tiler". Let me know I you'll give this change a chance. Usually it is no issue to reboot (while reading pdf - which is main job), only if we play Carcassone it is really bad if it becomes slower and slower and touch

Than I have to stick to this version for longer time to observe it.
[Nook HD, HD+ Android Development] myjess:
thanks to those that told me how to install nw roms.

Screen upside down is issue fir me but goes away when i use it because screen rotates.
[Nook HD, HD+ Android Development] neutronjeff:
I'm having a problem on a clean install of the 0422 LnOS on ovation. "Setup Wizard keeps stopping". I can't get past the Import or setup as a new device? screen. TWRP 303

Any suggestions?

--------

OK, I seem to have gotten around it. I was able to get to the settings from the drop-down menu and add Wi-Fi and my Google account, then the next time through the setup wizard went through.
[Nook HD, HD+ Android Development] mikeataol:
Hi,

you have to enable wifi.

swipe from the top when given the chance and get into settings to connect to wifi, and then setup will continue

(oops didn't see your edit. )
[Nook HD, HD+ Android Development] NE0HP:
Sorry again for being late in updating you to above subject due to weekends as I was not able to went at my office WiFi hotspots where I experienced connectivity issues. Tested the new 04/21 ovation build today but again I will have to say No WiFi connectivity and again it fails to connect automatically to my saved hotspots so I will have to stick with 04/18 build as far as WiFi connectivity is concerned! And "Yes" I'm keeping WiFi always "On" on all three last build 04/18, 04/19 and 04/21 respectively which I've tested and I found 04/18 build is the best if considering WiFi connectivity!

Wondering it just me or what!!! Can't see comments from other users experiences such WiFi connectivity issues in 04/19 or 04/21 ovation build....
[Nook HD, HD+ Android Development] myjess:
Ditto for me with same workaround on my HD
[Nook HD, HD+ Android Development] wally333:
Is there a place to download the 4/18 build? I'm currently running 4/22 and plan to update. I caught 4/19 and 4/21 builds and have downloaded them, but I missed getting 4/18. Being an optimist I plan on doing a "dirty upgrade" to 4/21 so I don't have to re-install all the apps.

If I have problems then I'd try rolling back to 4/19 and then 4/18 and finally doing clean install if necessary. Part of the reason I (and others) may not see connectivity issues is I don't move around to different access points. Sometimes wifi doesn't work when 4/22 wakes up and I have to reboot (easiest to tell my wife to do, but stopping and restarting did seem to work when I tried it). This doesn't happen all the time, it might be related to the DHCP lease expiring on the access point as it seems to need to be asleep at least overnight for it to happen.
[Nook HD, HD+ Android Development] amaces:
It's definitely something about the interaction with those APs, but the old drivers were working, so it's not a hardware issue. I'm more puzzled about the 04/18 builds being the only ones that work well since I incorporated the major changes therein. Anyway, I did other changes in the builds I uploaded today, so let's keep testing.

I restored those Lineage builds in experimental.

Have you tested that app on the recent builds?
[Nook HD, HD+ Android Development] churks:
Video Accleration

Hi there,

i am running LineageOS 0418 on my ovation Device without gapps. Works fine so far. My only problem since LineageOS is video accleration.

When i try to watch a 1080p h264 videofile in VLC with video accleration, VLC crashes. When i try to play a video without video accleration, the video playback doesn't run smooth.

Same with the normal Android Videoplayer and Kodi. Is it a LineageOS problem or do i need the gapps for video accleration?

Playing Youtube Videos (720p) with the App NewPipe (from F-Droid Store) works fine.

Greetings,

Churks
[Nook HD, HD+ Android Development] wally333:
I never had any success with VLC on the Nook HD+ with the stock ROM -- crashes/lockups, jerky playback, out of sync or no audio, etc.

The current Kodi in the Play store has not work for me on a One Plus One with CM Marshmallow or the 4/22 lnos build on the Nook HD+.

An older Kodi version I've side-loaded from an apk does seem to work on an old LG Volt running KitKat(4.4) but its got only about 1/4 the pixels of the Nook HD+ I'm trying to play files form the UPNP server built into my ASUS router. Kodi (LibreELEC) on the Raspberry Pi2 plays these fine at full 1080 resolution (h.264) so I don't think its a UPNP server issue. If I can find the apk again I'll try it on the NookHD+
[Nook HD, HD+ Android Development] jernyx:
I use MX Player and it works fine with 720 h264 files, although it takes some configuration. You have to download the custom codec labeled "neon" here: https://xdaforums.com/devdb/project/?id=19112#downloads and if that stutters at all turn on hw+ decoding in the menu and then there's a button to change it on the top left while a video is playing. And set max cores to two in the menu as well, because I believe the hd+ processor has two cores(correct me if I'm wrong.) I haven't tried any 1080p videos since upgrading to lineage but I was able to play some on stock with MX player. I can't recall if they were h264 or not.
[Nook HD, HD+ Android Development] weitau:
Thank you Amaces!

I was previously running cm_hummingbird-ota-MOB30J.160530 on my Nook HD and the battery kept draining because of the won't-power-off bug. It also had issues with some Android apps.

After putting off fixing it, I finally found and installed cm_hummingbird-ota-MOB31K.161125 from your Dropbox site. This ROM is awesome and it's compatible with my previously incompatible programs (ie. Dungeon Boss). Thank you very much!
[Nook HD, HD+ Android Development] starbright_:
[MENTION=4473900]amaces[/MENTION]:

I highly appreciate your attempts to improve our old HD+! There was quite a few versions out now 18, 21,22, 24.

Get a bit lost without a little changelog and can't follow testing. Did you changed in any of this version the "tile - z ram - stuff", that makes it slower and touch not working?

Or do you busy with Wifi stuff? (Don't want to push, just afraid to miss a version).
[Nook HD, HD+ Android Development] myjess:
Files no longer in box from the links in this link.

https://xdaforums.com/nook-hd/general/how-to-updating-nook-hd-internal-emmc-t3562818
[Nook HD, HD+ Android Development] digixmax:
The files are occasionally temporarily unavailable, probably due system maintenance.
[Nook HD, HD+ Android Development] myjess:
Thanks for the quick reply, how can I get access to the other roms like the one for 04/18/2017?
[Nook HD, HD+ Android Development] mikeataol:
when you got to the box folder , their is a whole hierarchy of folders.

if you clicked on only the "download" folder link you wont see the other folders unless you click "Android"

the experimental folder has the 418

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918
[Nook HD, HD+ Android Development] amaces:
Idle Battery with Current Wi-Fi Stack

Let's have an informal survey about battery drain in deep-sleep on the current Nougat builds. If your connection is stable, do post if battery life is much worse, better, or about the same as with old wl12xx drivers.

Am still looking into the connection/roaming issues reported.

The flurry of recent builds was focused on Wi-Fi issues, but I did remember to revert the secure input stuff in the local kernel tree. Next set of builds (should happen in a couple of days) will have that change and others. Linear changelogs would be difficult to create automatically given how I rebase/amend my changes, but everything gets synced up to the public GitHub repos pretty quickly.
[Nook HD, HD+ Android Development] drmarble:
For those of you who build yourself and have resized your system partitions I have made a pull request ( https://github.com/airend/android_device_bn_common/pull/2 ) to amaces device/bn/common repo. You can apply it to your builds and the system partition will automatically resize before restoring gapps.

My builds are working fine. I did have to update gcc to 4.9. It didn't impact any of my other builds. For some reason I can't run brunch ovation. The mka command fails at the end of the build trying to build parts of busybox. If I do a make -jx bacon the build works just fine. I have not seen that problem before. brunch encore, acclaim, etc work just fine.

Thanks for your good work.
[Nook HD, HD+ Android Development] netcsk:
I sincerely apologize if this is a stupid question.

I'm running the lineage ROM and have playstation vue. Even with root access off, the app recognizes root and refuses to launch. Fixes I've found aren't nougat compatible (xposed). Does anyone have any suggestions?

Of course I'd rather keep the awesome work by amaces than have Vue, but it's the only minor issue I have.

Thanks!