yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] netcsk:
My battery usage on ASOP ovation is kind of disappointing (ASOP runs a bit quicker/lighter for me). On standby, I'm seeing about 2 days. Its a relatively light install when it comes to apps. Unfortunately, I can't say what apps are using it because there is no real breakdown when looking at battery usage (I.e. 50%+ shows as miscellaneous).

Anyone else seeing different results?
[Nook HD, HD+ Android Development] amaces:
That's totally not normal. Even on the old/current WLAN drivers, standby should be at least 7-10 days.

Just curious, is Vue working better on latest builds?

Well, that was odd; one of the kernel modules meant for BT comms stopped loading properly, but only on AOSP ovation, and only with the full build. If I recopied the same module manually, everything was fine, which is a very weird issue given that all HD builds are generated from the same trees.

I moved some of the BT modules back inside kernel, so all current builds should be OK. I have not seen the Wi-Fi issue you're describing, but I have one other similar report on a different device (with different drivers). Are current builds broken too?

Yes.

Starting with the 5/30 builds, we're back to the old WLAN drivers as promised, while keeping some of the improvements that happened for the new drivers, which I kept only for the experimental kernel branches.

No need to install anything on the current builds. The old builds (pre 05/30) and WLAN updates were moved to obsolete, should anyone be interested to test the newer drivers.

The YouTube app, or in browser? Does slowed down mean out of sync, or consistently slower playback?

It probably goes to the lowest brightness allowed by driver and overlay settings. Most other devices have pretty high minimum brightness, which can be annoying at night. I'm not familiar with this setting, but maybe you can use the Daydream feature while charging.
[Nook HD, HD+ Android Development] neutronjeff:
Amaces:

The YouTube app, or in browser? Does slowed down mean out of sync, or consistently slower playback?

It was in the YouTube app. It was definitely out of sync, I thought it was slowed as well.

The Disable hardware overlay setting seems to have fixed it.
[Nook HD, HD+ Android Development] netcsk:
Any suggestions on battery? Is it normal for so much of the battery usage to show as miscellaneous?

Example as of now:

Miscellaneous: 32%

Android OS: 6%

Screen: 2%

Android System: 1%

Etc.

Unfortunately still a no-go for Vue on either lineage or AOSP. I'm not sure what it is looking for because I'm rooted on SuperSU (no custom rom) on a fire 7 and it doesn't care as long as root access is turned off.

As always, thank you for everything.
[Nook HD, HD+ Android Development] Mac Hosehead:
I was having issues with the WiFi not reconnecting after sleep. I am reconnecting without issue with the "old" drivers on experimental release.

lnos_hummingbird-ota-NJH47B.170609
[Nook HD, HD+ Android Development] netcsk:
Quoting myself with more information from an app that gives more info (gsam battery monitor).

21hrs from full charge with zero tablet usage, 61% usage, 40% of that was the kernel. Netflix was next and has now been uninstalled.

Says deep sleep was only 3hrs 38min.

Kernel wakelocks were dominated by musb_autosuspend_wake_lock at 6hrs 47mins. Googling that gives old results of battery usage issues resolved by a ROM change.

WiFi was a big user but that's probably because of Netflix. I'm going to turn off WiFi testing tonight.
[Nook HD, HD+ Android Development] king200:
Setting that helped WiFi

I installed aosp_ovation-ota-NKG47L.170606.zip and was having WiFi interruptions. I tried nookhd-wlan.zip and got no WiFi. I remembered WiFi problems with Nook HD+ from ~3 years ago. I set a fixed IP instead of Static ip. The WiFi connection has stayed stable and I have speedtest is excellent. Someone else please try to confirm.

My router is g/n/ac and 2.5 ghz. ISP line speed is measured 100. I rarely use the WiFi outside home. I'm guessing that I'd have to use Static IP in other locations.

I actually had minimal WiFi problems with Lnos 0530 Ovation. For some reason I could not clean install 06/09 LnOS. I couldn't not even reinstall 05/30 and could only install System and Boot from recovery of 05/30 install. I won't detract from this message of almost killing the HD+. Thanks for sdcard-reco-ovation.img.xz,

;
[Nook HD, HD+ Android Development] xflier:
Same issue here with 0609 lnOS build too
[Nook HD, HD+ Android Development] digixmax:
I dirty-flashed & updated my HD+ LN14.1 from 05/30 to 06/09 build -- WiFi continues to work great.
[Nook HD, HD+ Android Development] ShapeShifter499:
I may have asked this before. Is there any way to get Magisk installed on the Nook HD ?
[Nook HD, HD+ Android Development] amaces:
That's odd since the A/V sync issues usually happen with content in browsers. Is it something that started happening recently? I've been working on HWC fixes, trying to make some progress on HDMI output. Flash nookhd-hwc-old.zip in experimental with HW overlays enabled, and see if it makes any difference. I'd rather have working composer and overlays.

These wake locks and Wi-Fi drain are likely connected. Can you try flashing nookhd-no-wowlan.zip in experimental, or just removing the wowlan_triggers=any line in /system/etc/wifi/wpa_supplicant_overlay.conf manually)? After that, you also need to reset your network settings (basically, make sure that line didn't make it into /data/misc/wifi/wpa_supplicant.conf after reboot). My hunch is that some wireless environments just don't play well with the WoWLAN filtering in these drivers, so let's see if this change removes those wake locks.

There's a reason files get moved to obsolete. The nookhd-wlan.zip was/is good only with pre-5/30 builds (and post mid-March or so).

That implies the issue happens after the MAC layer handshake, and has to do with your DHCP setup. The drivers themselves don't deal with the latter part.

Unfortunately, that won't be an option with networks that you don't control. Try resetting network settings only, then re-adding the SSID with DHCP.

All builds since 5/30 (including) have the same WLAN drivers, and can't think of a reason for dirty-installs to fail, unless there are issues with recovery itself.

Sure, it's possible, but you'll have to tweak the boot image pack/repack scripts inside. As discussed before, these Nooks (including acclaim) have a second loader and weird offsets for the real boot image, so all the system-less installers (SuperSU, phh's, Magisk, etc) will fail after extraction. Someone would need to modify the image processing scripts to account for offsets, and to preserve the headers that allow the real boot image to load. This part is not terribly hard, but it would need to be adapted for each third-party installer. Then the bigger issue would be who maintains these parallel ZIPs (that is if the prospective project owners don't mind modified installers floating around). That's why we were pretty much forced to have system-mode SU packages, with all the effort that entailed.

I may look into preparing patches for some of these installers, which people would need to apply themselves, but it'll take time.
[Nook HD, HD+ Android Development] king200:
Near ruin an HD+ (2!) TWRP 3.1.1.0 or 3.0.1.0.

In doing a clean install I wanted to be very clean. I didn't just wipe data but changed to from f2fs to ext4 and then back to f2fs. DON'T DO THAT. I then proceeded to clean install or maybe restore a backup. I could not boot into system and TWRP did not boot either. SDcard CWM did boot. Data and internal storage had to be formatted. Formatting just data failed. I was then able to boot and install TWRP,

You can FORMAT data in TWRP but you have to follow the instruction after to reboot recovery. If you don't do that, and write to data, you'll get a almost dead HD+.

I now have an HD+16 x Lnos and HD+ x AOSP.
[Nook HD, HD+ Android Development] netcsk:
I installed the zip but the drain didn't change. I didn't really know what you meant by resetting network (I've been losing config for WiFi after reboots or long times with it off anyway).
[Nook HD, HD+ Android Development] neutronjeff:
I'm back home with my device now.

So, I'll try your 0609 build, and if I don't see improvement, I'll flash the patch.

I'll report back as soon as I'm done.
[Nook HD, HD+ Android Development] neutronjeff:
OK, Ovation on 0609 with latest gapps my YouTube looks fine.
[Nook HD, HD+ Android Development] amaces:
Turns out that resetting network settings wouldn't be sufficient anyway. Did any of the past builds have normal battery drain, and if so, can you remember roughly the timeline?

Plain 0609, without extra patching, is OK, correct?
[Nook HD, HD+ Android Development] netcsk:
The standby drain goes back to what I had before if I turn off wifi before letting it sleep (5+ days).

What I can't really say is if there was a difference in the older builds because I always turned on the auto wifi off when sleeping without charging. I stopped doing that with the driver change because it resulted in losing configuration when waking back up.

I can flash an old build and leave wifi on when sleeping if that would help compare apples to apples.

It's really not a big deal, turning off wifi and reentering the password when using it the next day doesn't kill me.
[Nook HD, HD+ Android Development] amaces:
Are you able to do a clean install of a late-January/early-February build (from the obsolete folder)?

It's not right though, since it shouldn't happen, unless there's some other underlying issue. It definitely doesn't happen on my devices, but I have exactly two reports related to this, and it still doesn't make sense.
[Nook HD, HD+ Android Development] neutronjeff:
[MENTION=4473900]amaces[/MENTION]

Plain 0609, without extra patching, is OK, correct?

Correct.
[Nook HD, HD+ Android Development] danj88:
Flashing nookhd-hwc-old.zip has fixed the YouTube issue (audio desync/low framerate?) I was having on lnos_ovation-ota-NJH47B.170609.zip. Many thanks for the fix.
[Nook HD, HD+ Android Development] netcsk:
I, in my laziness, did it with a dirty flash to a February build which obviously didn't work great. I reflashed to the latest build and the WiFi configuration issues are no longer there (off while sleeping and the recovery works perfectly). It did not fix the drain while WiFi is left on, but I'm perfectly happy at this point.
[Nook HD, HD+ Android Development] ZorgeZorge:
Thanks for release and support, btw

My device experiences odd freezes and very low framerate in Youtube (LN 14.1 0609, fresh GApps)

Disabling HW overlay did not solve this issue.

As far as this thread goes, possible solution is flashing old HW control with this file "nookhd-hwc-old.zip"

Sorry for the noobish question, but where can I download it?
[Nook HD, HD+ Android Development] digixmax:
I've been using LN14.1 build 06/09 for about two weeks during which I frequently experienced "system freeze" incidents, most often shortly after the HD+ comes out of sleep. Diagnostic dmesg immediately following one of the incidents is saved at http://www.mediafire.com/file/w54wn59493mrvh0/dmesg-lnos0609-freeze.txt.

As a result, I reverted back to build 05/30 for now.
[Nook HD, HD+ Android Development] mikeataol:
On Ovation, I also reverted to the LNOS 05/30 after about 3 weeks of use. I would see the WiFi do strange things, not just to the Ovation, but it seemed when it was crashing it was causing interference or bad packets on the WLAN as a whole.

I swear this is the case... When the ovation WiFi was about to drop, my 2.4Ghz mouse nearby , AND a Nook tablet nearby would also lose connectivity.

I would see my mouse stop moving, the Ovation WiFi would drop( and reconnect after 20-30 seconds) and simultaneously the nearby NT WiFi would lose its WiFi and have to reconnect.

It happened very regularly, and I am not seeing it on the 05/30. I don't recall seeing it on whatever older (December?) version I had been running.
[Nook HD, HD+ Android Development] HarvHouHacker:
I've been putting off working on the Nook HD+ for well over a year, but no more. I've been studying some programming techniques, and now I'm about to tackle these problems on my own. I've forked the repo so I can mess around with it and see how it ticks. I also will report any issues I run across. Hopefully, we can make one of the best stand-alone tablets of the 21st century work better than stock!
[Nook HD, HD+ Android Development] games906:
So i just charged my nook hd+ after being left alone for about a year, booted and had Marshmallow installed. I just wiped system, data (not internal), and cache so I can install Nougat lineageOS. But the device is stuck loading the boot animation. Any ideas?
[Nook HD, HD+ Android Development] NE0HP:
Do clean install (wipe internal storage as well). And before flashing LNOS14.1 ovation I'm sure you must have updated TWRP to the latest one, if not then update it first from this link https://m.box.com/shared_item/https%3A%2F%2Fnotredame.box.com%2Fs%2F26a4bygh9vbaw7jjq08xr5evomvaw5ww/browse/24717651525

Reboot the device to the latest TWRP,

Wipe everything except external storage,

Flash ROM followed by GApps(PICO is recommended)

And if you rely on Root then flash addonSU-14.1-arm-new from this link https://m.box.com/shared_item/https%3A%2F%2Fnotredame.box.com%2Fs%2F26a4bygh9vbaw7jjq08xr5evomvaw5ww

Wipe Dalvik/cache and reboot the device. That's it.

Be patient as first boot will take some time!
[Nook HD, HD+ Android Development] games906:
Ah! I did everything except wipe internal. But if I have to, I have to. Thank you
[Nook HD, HD+ Android Development] mikeataol:
I would just add, after flashing the rom, I always reboot to recovery before flashing the gapps. It seems to help IMO....
[Nook HD, HD+ Android Development] ShapeShifter499:
I just set up my Nook HD Hummingbird with the LineageOS 06-09-2017 build. The launcher I've been using on all of my other devices is "OpenLauncher" and that launcher doesn't rotate. I suppose there isn't any issue holding the tablet upside down but its weird having the home button opposite side of the screen.

Is there a solution to the rotation issue?

And how come the screen is flipped? I could have sworn it was fine in a much older build
[Nook HD, HD+ Android Development] belfastraven:
for a partial explanation of screen rotation, see post #1437 in this thread. This rotation change began in November of 2016.

I have been using one of the force-rotation apps available in the play store to solve the problem. I downloaded OpenLauncher and tried it, and it worked for me. IN my case I am using Ultimate Rotation which is a paid app, but I believe some of the free apps will work. According to their github, Open Launcher uses the default rotation of the device--Someone has already requested that rotation work on the device--perhaps you could second their request?
[Nook HD, HD+ Android Development] Merazomo:
Browsing through the thread, I'm glad HDMI output still hasn't been forgotten, and it's still being worked on. It's incredible how much this tablet has endured over the years, and it's still being modernized.
[Nook HD, HD+ Android Development] ShapeShifter499:
Thanks! I found a free and open source rotation helper that works great called "Tap 'n' turn" over at F-Droid https://f-droid.org/packages/com.gabm.screenrotationcontrol/ You can set it up to force rotation and it shows an icon in the corner when it detects rotation which you tap to rotate. This app doesn't require root neither.
[Nook HD, HD+ Android Development] js290:
Screen Touch Oddity

After several days of uptime, the screen touch fails to respond or behaves erratically. Reboot seems to fix the problem. Attaching logcat, dmesg output, and bugreport.
[Nook HD, HD+ Android Development] js290:
duplicate post, sorry.

duplicate post, sorry.
[Nook HD, HD+ Android Development] mikeataol:
Thanks for mentioning this. I had completely forgotten that in addition to the wifi issues I saw on the 0609 build, I had seen this as well and was one of the kickers that made be revert to the earlier version.
[Nook HD, HD+ Android Development] dbrickg:
just downloaded and installed the lnos ovation 170706 version on my nook hd+. all seems to be working well so far!
[Nook HD, HD+ Android Development] brenyoka:
So, no wifi/connection problems on lnos ovation 170706? Planning on doing a clean install of it.
[Nook HD, HD+ Android Development] vinceweis:
Everything working very well for me also on the 0706 build.
[Nook HD, HD+ Android Development] amaces:
Based on other reports, that fix isn't really needed, but if you wish to test again, the file is in obsolete.

HDMI is not forgotten, but there are so many other things constantly happening with these devices, so progress there is not happening very fast. Also, I'm in the middle of a big move, plus the whole summer thing...

After two weeks of use without reboot? Are you able to test if AOSP behaves similarly?

So, these only started happening with the 0609 Lineage build? No relevant changes in kernel or device parts since the last May builds, so hopefully it's coming via Lineage. Does it happen on the July builds?
[Nook HD, HD+ Android Development] wpp105:
June 6 LNOS clean install from CM11.

No gapps

After 1st boot and its going through the preliminary setup question, it gets to the LineagOS features page and the screen starts flashing and eventually crashes/reboots.

I tried several clean installs, wipes, etc, nothing fixes it.

I'll try the ASOP next to see if it has a similar issue.
[Nook HD, HD+ Android Development] wpp105:
ASOP works.

But I found a bug in that Launcher 3 crashes if you try to change the wallpaper.

My big issue is not having GAPPS, not even nano fits..

And REPIT always gives me an error. Anyone else have a issue resizing the system partition??
[Nook HD, HD+ Android Development] sasmith-129:
I also saw that flashing issue on a clean install of the ovation LNOS 170706 build (including on a repeat installation).

I got around it by installing the latest (pico) open Gapps *before* rebooting. I've been using a custom gapps-config file for a while now so there was no problem with it fitting without resizing partitions.
[Nook HD, HD+ Android Development] wpp105:
A custom gapps may be the right way to go.

I think that I figured out the repartitioning issue I was having, but I'm not keen on resizing after every update unless we write a 1 click type of program.
[Nook HD, HD+ Android Development] digixmax:
I had to reboot (usually soft restart) most of the times when the device freezes up.

It happened on 05/30 and 07/06, but very infrequent (so far once on 07/06).

A peculiar thing is during some of the freeze-ups the device would go into landscape mode (ignoring my forced-portrait mode setting), then my (Nova) launcher would revert to its default wallpaper.
[Nook HD, HD+ Android Development] ajislav:
I can confirm Nova launcher reverting to default wallpaper after freeze-ups on 05/30, I gave up on using my wallpaper in later builds.
[Nook HD, HD+ Android Development] digixmax:
I should add that the switch to landscape-mode is temporary (e.g., till next restart) whereas revert to default wallpaper is persistent (till manual change).
[Nook HD, HD+ Android Development] wpp105:
So, I decided to repartition once I realized that I had to manually unmount the partitions before running repit. Interestingly, twrp has issues resizing partitions after a system install on a 1gb system partition. I could "fix" the partition size by converting the partition to f2fs but the system wouldn't boot LNOS or AOSP with F2FS. So, if I converted back to ext4 I could install gapps and boot LNOS, but gapps would not install on AOSP without an error code 20.

I stumbled on a simple work around that works on both AOSP an LNOS. After installing the operating system, don't resize the partitions. Simply install gapps. It will fix the partition size. But it will need to be installed twice to actually install gapps.

After that, simply root and enjoy.

With gapps installed, every bug I mentioned goes away. But if i convert to f2fs the system refuses to boot and I need to reinstall to fix. I need to do more homework here.
[Nook HD, HD+ Android Development] king200:
I had no problem with either of 2 Ovation using Pico Gapps.

I gave up on resizing system partition. I did have a problem a couple of months ago but not with current builds.
[Nook HD, HD+ Android Development] wpp105:
So, after testing an entire night, I settled on the AOSP version for my daily driver.

-I stripped out, camera, email, and all launchers.

-Running with Arrow launcher now.

-Started deactivating all non critical google play services. But something I deactivated interfered with Google Maps. So I'll have to do more trial and error until I figure out what process caused that.

Overall, AOSP is really stable, ZRAM is active and keeping memory use in check. Adds a ton of stability over the kitkat builds I use to run. But, Google Now really taxes the system. I'm leaning to remove it.

I can tax the system to crash using my favorite test. Go to a CNN and play a video clip on the site through the browser (Opera mini and VLC). If I can get it to launch the video, it will not be long before I have issues with stability. But that is true on any 1 gb memory device I use.

Besides the F2FS issue (which I'm sure that I'll figure out), the one bug in AOSP that bothers me is the recent app list. It works, I can scroll through my open apps, but the cards in the flip deck are distorted.

But for right now, this is a massive upgrade vs kitkat roms and stable enough for a daily driver.
[Nook HD, HD+ Android Development] ze7zez:
Unlegacy Android

Since recently I have Nook HD, I'm looking for an opinion about Unlegacy Android.

Does anyone use it?

I have UA on Nexus 4 and it works smoothly.

aosp-6.0 hummingbird

aosp-7.1 hummingbird
[Nook HD, HD+ Android Development] mikeataol:
I don't have a hummingbird to try, but on the Nook acclaim , all the UA builds so far are unable to save WiFi settings properly. You must reset each boot.

Other than that, it runs fine.

(They also need addons for SU capability, phh superuser binary and Superuser APK)

edit: I switched one from UA to LNOS today and the LNOS acclaim runs better in my opinion, the interface feels laggy on the UA version.
[Nook HD, HD+ Android Development] ze7zez:
Do you compare UA/CM 6.0.1 or UA/LNOS 7.1.2?
[Nook HD, HD+ Android Development] mikeataol:
My comments are about the Nougat 7 builds. I have not tried any of the UA Marshmallow builds
[Nook HD, HD+ Android Development] Tonto87:
Bluetooth 4.0/LE support.

Apparently the Nook HD(+) has hardware (WL1271L chipset) capable of Bluetooth 4.0. Is it possible to get this working?

More info here:

https://xdaforums.com/showpost.php?p=46780280&postcount=980

https://xdaforums.com/showthread.php?t=2452553

https://xdaforums.com/showthread.php?t=2623388
[Nook HD, HD+ Android Development] belfastraven:
I do not have any devices with which to test this, but I believe the firware was upgraded to the proper version over a year ago and I know that the BLE Checker app says that BLE is supported on my Nook (HD). Which build are you running, and what is happening when you try to use a BLE device with the nook?
[Nook HD, HD+ Android Development] Tonto87:
Ah great, thanks. I have a Mi Band 2, but has a non-standard way of pairing (i.e. you need the app), so I'm wary of messing up the connection with my phone. I'm running the latest version of lnos and the app you mentioned says that LE is supported, so that's good news. I will have to get another LE device to test it out for sure.
[Nook HD, HD+ Android Development] digixmax:
FWIW here is the link to the typical dmesg log captured immediately following such freeze incident. It's filled with "avc: denied ..." security-warning and "lowmemorykiller: Killing ..." messages.