yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ParadoxGBB:
Sorry for the lull on my part --- and thanks again for the attention --- long time reader here and on the Acclaim boards and so far this is my more engaging post experience. Love seeing folks here that enjoy messing with software as much as I do. ;)

It's more the temperature settings. Changing the day / night sliders do change the hue, but it's as if at night it's never detected to switch to night mode. F.lux seems to have the same problem. I noticed that you could change between modes like I mentioned before by a quick configuration swipe down option which I thought was great at the time on earlier CM builds, but I guess that's gone by the wayside. My past experience with F.lux was that it wasn't that bad, and was even decent on Acclaim.

Again, totally get that this is very minor to something critical like WiFi.
[Nook HD, HD+ Android Development] digixmax:
And here is the wlan-related output from dmesg for connection attempts to open public hotspots at my work place -- it takes quite a bit of time for the device to be able to connect.
[Nook HD, HD+ Android Development] ParadoxGBB:
I ran a quick test yesterday:

1) Set the night slider all the way to the left and the day slider all the way to the right, just to make things obvious.

2) Waited to go to bed a night, keeping the nook plugged in and asleep

3) When I went to bed noticed was still in day settings when I awoke the device.

4) When I restarted the device it had the right night (red) hue.

So I think it has something to do with the feature not checking the time of day when awaking from sleep.
[Nook HD, HD+ Android Development] digixmax:
Some more wlan-related output from dmesg for connection attempts to open public hotspots at my work place -- wlan5.txt: using 04/27 build and, for comparative purpose, wlan6.txt: using 01/04 build just a bit shortly after (< 5min).
[Nook HD, HD+ Android Development] zspeciman:
After clean install of the 4/27 I still have CNN app problem on both my ovation units, but not on my Hummingbird. How do I generate dmesg? Do I need to generate from both the ovation and the hummingbird so this info can be compared?
[Nook HD, HD+ Android Development] pyoungworth:
Is there a build that I can download for AOSP ovation that doesn't have the wifi issue. I upgraded recently and the wifi issues are driving me nuts.
[Nook HD, HD+ Android Development] digixmax:
Assuming amaces' AOSP builds follow the same track as his LN builds, I think you'd need to look for & request the 01/04 build (or older builds) which used the previous WiFi driver.

For anyone who is looking for the LN14.1 01/04 build: I've uploaded my saved copy to http://www.mediafire.com/file/tbhud6i40szd564/lnos_ovation-ota-NMF26Q.170104.zip.
[Nook HD, HD+ Android Development] mikeataol:
not knowing if this is really what is needed, but the 0104 AOSP ovation build is still in the "obsolete" folder...

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3262390066
[Nook HD, HD+ Android Development] pyoungworth:
Thanks. I didn't even realize that folder existed.
[Nook HD, HD+ Android Development] digixmax:
I too gave up on 04/27 build and went back to 01/04 build, as I highly value its instantaneous connect performance.
[Nook HD, HD+ Android Development] amaces:
Root Package Updates

Starting with the experimental builds today, I made changes to AOSP such that same Lineage SU add-on can be used there as well. The CM/Lineage backend is better imo, but also depends on their Privacy Guard changes. Turns out much of the used AppOps plumbing is in AOSP, so I adapted the remaining changes for the Lineage binary.

As of now, either add-on should work on both ROMs. With Lineage's, support is baked in, while phh's requires the companion SuperUser app. Although the official Lineage packages are a bit outdated, they should still work, despite the recovery error, but I also prepared updated packages that should install cleanly.

The current official images should be fine, although there are subtle differences. They have a snapshot of our old CM12 kernel and device tree, which also means that they're building our recoveries in an LP environment. It's the same TWRP situation as with many other devices, but it shouldn't make any difference in practice, and it's more important to have stable reference images.

Can you check this on a clean AOSP build, just in case Lineage root is still lingering somehow? It's also possible that Vue checks for much more than SU for apps, including userdebug build, SELinux mode, even mere shell root access and related props.

OK, so the hardware backend part works as well as before, but there seems to be some sort of issue with the adjustment engine.

Since this affects both Lineage and f.lux, I'm thinking the issue is about location provider. We don't have a real GPS chip, so we rely on coarse Wi-Fi based location , which really needs the location provider from GApps these days. Do you have them installed? Also, is the timezone setting correct?

ADB shell (logcat -d) or using one of the apps for this purpose. I did some more codec configuration changes in today's builds, but your problem might be deeper in the DOMX stack.

Not really, although I guess it could help.

Not really sure what to say; the logs have the same types of errors that we've seen before. The kernel ones are not critical, but shouldn't really happen, yet they do on some combinations of hardware and APs. Have you tested that the same issues occur on a clean AOSP build? Try the new builds in experimental.

I think the current set of builds and next one are my last attempts to make the new WLAN drivers work well for everyone. Otherwise, we'll revert to old ones, but as you remember, those had their own issues, which was the original incentive a couple of months back.
[Nook HD, HD+ Android Development] Zippy Dufus:
I'm running a homebrew 04/27 build and I'm finding that the WIFI connectivity is not as good as it once was - disconnects and limited range.

I planning to build again and see if the WIFI is any better.
[Nook HD, HD+ Android Development] neutronjeff:
0506 Lineage build for ovation running well for me with micro gapps. TWRP 3.1 (Repit)
[Nook HD, HD+ Android Development] dbrickg:
I just installed the lnos_ovation 170506 experimental build on my HD+ and the wifi works just fine. But I've never had any trouble with wifi, so that's not very conclusive :) But the build boots just fine and everything seems to be working as well as always.
[Nook HD, HD+ Android Development] xflier:
Just installed 0506 AOSP, WiFi still has very limited range
[Nook HD, HD+ Android Development] mmnspeed:
WiFi connecting in 170506 seems faster.Seems good as far as my usage is concerned.But I haven't been looking into the issue that much.I have a router in the middle of the house,my cell phone from last year is on Android 6,it is on the ROM it came with,it has similar signal as the nook.
[Nook HD, HD+ Android Development] Zippy Dufus:
WIFI is better

Follow up, I checked again on my 05/06 build and WIFI is much better.

Seemingly faster and maintains a connection at a decent distance (kitty corner the other end of my house through a couple walls) from my router.

Great work, again!
[Nook HD, HD+ Android Development] neutronjeff:
Also agree that 0506 is an improvement over 0422 in my ovation.
[Nook HD, HD+ Android Development] buraksumer7:
thanks for the great effort, you gave a new life to my nook :)
[Nook HD, HD+ Android Development] digixmax:
I dirty-flashed and tried out build 05/06.

When connecting to my home network secured APs WiFi connect performance is, most of the times, nearly on par with that of build 01/04.

When connecting to my work-place open APs, the performance is a hit-n-miss, some times quite fast, other times taking a really long time. Attached is the wlan-related output from dmesg.
[Nook HD, HD+ Android Development] ParadoxGBB:
I flashed the 5/7 build on my hummingbird yesterday and it's pretty good on WiFi --- I had a good experience on the 2/28 build and then a bad one on the 4/15 and 4/27 ones and after those I reverted back to 2/28 until now. It's great to be moving forward. The WiFi did drop once this morning and required me to manually reconnect, but it was able to do so without a restart, so still better.

The timezone settings are correct and the location services are enabled in settings (settings --> personal --> ON / High Accuracy). I'm not sure if there's anything additional I need to install (I have installed GApps pico), I don't see anything in the Google Store and my weather application can detect my location without problems. Since the feature appears to work on reboot, this suggests to me that the settings are correct but they aren't honored until reboot... maybe? If they were wrong I wouldn't have expected any change on reboot.
[Nook HD, HD+ Android Development] pyoungworth:
I tried the May AOSP build but have reverted back again to the January build. Looks like the wifi was better in that build but the January build is much more stable for the wifi. I lost connection a few times and had sporadic reliability (with the may build)
[Nook HD, HD+ Android Development] digixmax:
I agree that WiFi connect performance of 01/04 is consistently better in response-time and, more importantly, reliable.

Additional sample of dmesg output associated with failed connection attempts.
[Nook HD, HD+ Android Development] Merazomo:
I connect my Nook HD+ to an extra TV I have with no internet access through the HDMI adapter. That's the reason I haven't been able to let go of the HDMI feature, which is slowly becoming extinct because of casting and stuff like that, but I'm sure some people with Nooks still use it, and it can be pretty useful at times as an alternative even on newer TVs.

Is there a way of installing the Wi-Fi or HDMI drivers, from the lnos_ovation-ota-N2G47O.170506 (which is perhaps the best recent build I've tested as far as responsiveness and Wi-Fi connectivity) to some of these older builds like 6.0.1 MMB29U 160222, as an APK installation or flashing it as a ZIP file from TWRP? or perhaps adding HDMI capabilities to lnos_ovation-ota-N2G47O.170506?

At this time I'm using build 6.0.1 MMB29U 160222, which is the last build I tested that works with my HDMI adapter. The build is abviously unstable, most of which I can live with; however, the intermittent inability to connect to the internet after Wi-Fi has been disconnected sometimes, and the intermittent dormant state that the tablet stays in, where the only way of waking it up, is by hooking it up to external power, is still a little bothersome.
[Nook HD, HD+ Android Development] ales-76:
I just flashed my ovation with the 05/06 AOSP build, so far looks good, no issues with Wi-fi (although there are warnings produced by wlcore driver in dmesg). What surprised me though was that the system did not recognized my 64GB SD card formatted as exfat and insisted on reformat. Exfat cards worked fine in Marshmallow AOSP builds I was using before (08/20 build recently until today). I am I missing something? I use the ovation mostly as a movie player for my small daughter and since most of the files are over 4GB using vfat is no option. I prefer AOSP builds since they are leaner and feels more snappy. Any advice will be appreciated.
[Nook HD, HD+ Android Development] ST Dog:
Why? Most of the movies I watch on my big TV are under 2GB.
[Nook HD, HD+ Android Development] sasmith-129:
I keep a TWRP backup of the same build just so I can use the HDMI output when I travel. Most of the hotels I stay at have TVs with accessible HDMI ports but not many support casting. So, it is definitely a feature I would use if there was some way to support it again.
[Nook HD, HD+ Android Development] nmyshkin:
Hmm...Build 6.0.1 MMB29U 160222 is that buggy? Darn. My husband's been chugging along on a CM 11 build but we've been planning on updating to this MM build because we're starting to have issues with newer apps not running well. But I'm not sure he wants to put up with that kind of behavior on a daily basis :(
[Nook HD, HD+ Android Development] Merazomo:
I used to do that as well; however, for some reason every time I would restore my MM build, all the settings and repos for my KODI setup, along with other apps would disappear. It was a pain to have to set it up all over again.

It's not buggy all the time. Not on a regular basis at least, but when it happens, it's annoying as heck. A handful of times I've been streaming a hockey, soccer, or football game, and the tablet goes to sleep. Well... I push the power button, home button, nothing. I long press the power button thinking it has turned off... nope, it's not turning on. I connect the charging cable... tablet wakes up. I won't have access to external power all the time, so it's definitely a very annoying bug the times it has happened to me.
[Nook HD, HD+ Android Development] ST Dog:
Maybe a different problem, but I get something like that on humming bird with CM11 too.

Seams related to the screen lock. Power cord doesn't always help either. Often have to force a reboot.
[Nook HD, HD+ Android Development] js290:
Just had wifi drop on N2G47T.170506 build. Was rock solid on the N2G47J.170412 before. Attaching logcat and bugreport.
[Nook HD, HD+ Android Development] andrerz:
Hummingbird - The May build looked promising at first, but after a while it started dropping wifi randomly and more often. It gets to the stage where it would never start up after waking from sleep and it often requires several attempts to get it going, often dropping shortly after.

Tried everything, from reboots, cleaning cache/dalvik, total wipe and reinstall etc etc.

Now abandoned hope and returned to feb 28 build, which has quirks like upside down portrait defaults but at least is stable wifi wise.

All these N builds seem to have a strange recurring problem with Youtube which seems to lose the ability to play videos after a day or so (search still works though) and requires a reboot to fix.
[Nook HD, HD+ Android Development] OrangeFlavored:
Anyone else noticed much shorter battery life on these newer Lineage builds compared to the old CyanogenMod 14.1? Used to go around a week on a single charge if I didn't use the tablet much besides to run some automated scripts (mostly use the thing as a backend for my Amazon Echo to allow more variety of commands for the thing), now I need to recharge it every 2 days or so it seems like. Would have expected the opposite considering the old version didn't support the newer battery saving features like doze. Updated several times whenever a new build came out, I think I first started a few weeks ago.

Can't even really tell what used so much since the battery history isn't showing everything (the stuff it does show only adds up to 21%)

Might move over to AOSP and see if it does better but not looking forward to having to reset all my configurations again, so if anyone had the same issue and found an easy fix would be great.
[Nook HD, HD+ Android Development] amaces:
The current builds in experimental are pretty much my last attempt with the new WiLink drivers. See if any improvement.

It's likely about allocating dynamic tiler memory, or the inability to do so since we're often under high memory pressure. Can't tell for sure without kernel logs.

Same as above, kernel logs would be more helpful for this issue.

I don't think you're the only one with battery issues. My Wi-Fi drain and stability has been great on recent builds, but clearly there's something about the router setup and wireless environment that's different, and keeps the device awake. As above, try the current builds in experimental, which are pretty much the last set before reverting to the old drivers.

Support for exFAT cards was something adapted from CM13, which required forking a couple of additional repositories for AOSP. I tried to avoid doing that in N; if you don't have any option but exFAT, I'll try to bring it back.

Right, sounds like everything works properly, except CM's LiveDisplay engine. I did notice issues there even on my Nexus 5, especially after the first time Battery Saver is enabled. The actual kernel backend for the Nooks works well, but unfortunately no third party app knows how to work with it (only the CMHW plugin). See if the changes in experimental improve it.

On the first one, the whole CM13 ROM would need to be rebuilt with the changes for new drivers, and given that I have limited disk space for a CM13/AOSP M checkout, it's unlikely to happen (all the necessary repositories are available online though). Otherwise, I will try fixing HDMI again, but it's not an easy issue given our JB-era HWC.
[Nook HD, HD+ Android Development] vinceweis:
The 0517 build is working well for me. I have not had any trouble with the last couple of builds either. I don't push the device very hard, just using it for browsing, news, email, and sometimes watching TV through WiFi at home. I had a WiFi problem a while back but I was on the edge of my WiFi range. I moved the router and no problems since. I occasionally move to the edge of the range again and this device behaves about the same as a newer Samsung tablet that I have.

I am more than pleased with the performance, but appreciate the input from others that push the device harder and find issues that can possibly be corrected.
[Nook HD, HD+ Android Development] digixmax:
WiFi Connection Performance on LN14.1 Build 05/18

Yesterday I upgraded from LN14.1 build 05/06 to build 05/18.

When the Nook does sees the WiFi network it appears to take less time than with the previous build to connect up to that network, but now it seems to have some difficulty picking up the network in its scans, and it is also prone to dropping the connection.
[Nook HD, HD+ Android Development] mmnspeed:
I noticed this too.On a dirty flash though.
[Nook HD, HD+ Android Development] amaces:
I managed to break deep sleep on those builds with other changes, so try the current ones in experimental, which should become the next "stable".
[Nook HD, HD+ Android Development] digixmax:
Upgraded to 05/20 from 05/18.

WiFi appears to connect faster (than with previous builds) most of the times, but occasionally still takes quite a bit of time (10's of seconds).

Also, it

seems

to respond better to the WiFi button in Settings than to the various the WiFi toggle widgets.
[Nook HD, HD+ Android Development] NE0HP:
Just to update you further in to this I recently updated official ovation recovery from 3.1.0-0 to 3.1.1-0 and then I dirty flashed the most recent ovation build 05/20 over my existing build 05/18 and it throws error "Kernel does not have support for reading SELinux context" followed by Running boot script.... /sbin/postrecoveryboot.sh process ended with ERROR: 1. It successfully installed the zip though and reboot normally as usual. Don't know is it problem with recovery or with ROM? I'm attaching a picture as well as recovery log for more details if that help you to diagnose possible cause of this problem!

And as far as WiFi connectivity is concern, honesty it is still not connected automatically and needs to turned it off/on to connect. Once connected it doesn't remain stable especially in this 05/20 build! I understand your pain and the time you spend to resolve this issue but being a user and regularly flashing your ROM on my ovation I should be honest to give you feedback and I'm sure all other users here including me really appreciate all your efforts and always look forward to support you in terms of providing you feedbacks that you're always reciprocating with your fixes!
[Nook HD, HD+ Android Development] OrangeFlavored:
Noticed on LNOS 05/18 AutoRemote wasn't receiving messages anymore when the device was sleeping. Already whitelisted it and the relevant GCM stuff, so will go back to 05/06 for now where it does work as it should.
[Nook HD, HD+ Android Development] digixmax:
You should try the latest build 05/20 which has deep-sleep related fixes.
[Nook HD, HD+ Android Development] BultoPaco:
The only version of TWRP that I've been able to use without errors for sometime is 3.0.3-0. I'm curious to know if others are using newer versions without errors
[Nook HD, HD+ Android Development] neutronjeff:
Given the changes do I need a clean flash from 0506 to 0520?
[Nook HD, HD+ Android Development] amaces:
No, although resetting network settings can't hurt.
[Nook HD, HD+ Android Development] neutronjeff:
I just used 3.1 again on ovation, no problem.

---------- Post added at 04:51 PM ---------- Previous post was at 04:45 PM ----------

Network settings reset is needed. It didn't see my Wi-Fi before.
[Nook HD, HD+ Android Development] amaces:
Poll/WLAN Drivers

The coarse poll at the top of the page is about old (cca. Feb) versus current Wi-Fi drivers (May 06/20). Even if we revert to old drivers, I'm curious nonetheless.

How's stability and battery life? Also, when it doesn't respond as expected, feel free to extract/attach kernel logs.

As mentioned before, the official TWRP images have their own device tree and kernel repository, roughly equivalent to early CM12, I think. While that should still be OK for TWRP, there are many potential reasons for things to start breaking. You can test my personal (K3.4-based) images in experimental, if you feel like it.
[Nook HD, HD+ Android Development] digixmax:
I was going to upgrade my TWRP from 3.0.1-0 to 3.0.3-0 but then noticed that the latter newer version was moved into the "obsolete" folder.
[Nook HD, HD+ Android Development] OrangeFlavored:
Yeah, it does seem to be working in 5/20, at least in my tests so far. Though I did notice that the battery optimization whitelist menu is completely gone on this build, but since everything seems to be working without needing to whitelist then I'm not too worried about it for the moment.

edit: Battery drain after leaving it overnight was only like 3% so seems like this has improved significantly as well.
[Nook HD, HD+ Android Development] BultoPaco:
I installed [MENTION=4473900]amaces[/MENTION] 3.1.1 version from the K3.4 folder in Experimental as he suggested and it worked great for me!
[Nook HD, HD+ Android Development] digixmax:
My WiFi connect was great with build 01/04 but started to have issues with build 02/26, so I have assumed the 01/04 driver is the old one and the 02/26 driver is the new one.

I have not had issue with stability or battery drain.
[Nook HD, HD+ Android Development] amaces:
Nope, the new drivers (WiLink 8) only made it into the late March/April builds, spurred by the increased reports about Wi-Fi issues. When we go back (WiLink 6), it should be comparable to February builds, or maybe slightly better given the many little fixes that happened in the meantime.

I still don't know what could have changed upstream between January and February to cause your issues. I for one did not have them, but the new drivers seemed like an worthwhile effort.
[Nook HD, HD+ Android Development] mmnspeed:
Have used the new build for some time now.Seems to work fine and better than the previous build.I think you also have to keep in mind the behaviour of android devices in general.I have a table for studying in the extreme portion of the house.The WiFi signal there is low.Both my cell phone,which is on oem firmware,and the nook HD+ don't auto connect there.Previous build was dropping connection there,this so far seems to have rectified that.The phone exhibits similar behaviour,however once manually connected it doesn't drop the connection,this build also has similar behaviour.Have only been using for around 7-8 hours so other people should share their experiences.

P.S.:Going through the thread I noticed people mentioning the ?01/4 build.I honestly have no recollection of the performance of that build, so I guess I might not be the right person to make an objective assessment.
[Nook HD, HD+ Android Development] dbrickg:
I just installed the twrp 3.1.1-0 from amaces' experimental/K3.4 folder. Seems to work just fine. And I noticed that there's an official twrp 3.1.1-0, dated 5/18. I'll try that one in a minute, see if it does anything different....

OK, installed that one, and it's working well, also. I don't notice any particular differences between them