yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] belfastraven:
thanks. that fixed it and I successfully built again.

When I lunch and then make bacon, I get two zip files when I build, one with a normal cm name, which has an md5 file associated with it, and one with an otapackage name. They seem to be exactly the same size; I'm just curious as to why both are generated.

Also, I am now running your 12/24 cm hummingbird build and the 2.8.7.5 recovery, and everything is fine so far. I had lost the ability to software boot to recovery on my 12/22 build, but it is back now. My 12/22 build fixed WiFi dropping for me, also, so I imagine this will fix it for person having problems on ovation--I hadn't reported it because I had a new router and wasn't sure where the problem lie.

Can you tell why we have lost the ability to update permission sdcard ? I haven't tried updating permissions on a USB stick yet.
[Nook HD, HD+ Android Development] amaces:
According to this, the bacon target simply creates a hard link to the otapackage ZIP, with the customized CM file name, then calculates the MD5 sum. No space is wasted due to the bacon ZIP, but digesting the OTA takes some time. Since I don't use MD5 sums, using the same build target as in AOSP keeps things consistent. I already customized the otapackage file name slightly to include the important versioning information, although bacon behaves exactly like upstream.

Our reboot to recovery needs support in system/core, which doesn't look like it'll be accepted upstream very quickly. Anyway, I forked that repository as well, so that fix is in the manifest now. Haven't noticed Wi-FI dropping on CM13, but that did happen on AOSP, so they must've fixed it in the CM supplicant (the WLAN drivers are identical).

Are you trying to change permissions on files/folders, or some other type of permission? If the former, are you using shell/terminal commands, or some file manager app? I haven't really tried changing Linux permissions in Android since I assumed it wouldn't be consistent/reliable across different filesystems (e.g., VFAT, exFAT), with various extended attributes, plus the whole SELinux layer, but if it's something that suddenly stopped working, we should look at it. Also, do you mean internal eMMC (/sdcard), or the actual external SD?
[Nook HD, HD+ Android Development] andtron:
The sdcard is mounted on the MM as 9C33-6BBD, so a lot of app failed. Like belfast, I was trying to change the permission to rename it to sdcard1 with no luck.

Note: the build.prop did use the right name but ended up with 9C33-6BBD.
[Nook HD, HD+ Android Development] belfastraven:
Sorry--I wasn't being very clear.

On both the internal and external sdcard, using file manager or rom toolbox root browser (and I imagine other file managers) you are no longer able to change the Unix file permissions of a file, e.g. from rw-rw to rw-r--, etc. You get a message that you can't do that on an sdcard... . From file manager:

"The change of permissions operation failed.

For security reasons some file systems , like SD cards, do not allow the changing of permissions"

From Rom ToolBox Root Browser:

" Changing permissions was not successful.. Please note that some file systems do not allow permissions changes. "

I didn't think to try it from the terminal.I tried and you can do it on a mounted USB drive. I didn't remember not being able to do it before, but I might be hallucinating (I've been looking through the code and trying to figure out how certain things get built--is there a map someplace? :confused:) . I found it rather amusing that with root, I could change permissions of system files, but not MY files. ( I was doing this to get the bootanimation.zip to run) I assumed it was an SELinux issue at first, but since we are running permissive, I didn't see how that would happen.

By the way, the File Manager app saw the USB stick(with a hex address, like external sdcard) but did not see the files on it, but the system did (little USB icon in notifications allowed me to list and move files) and Rom Toolbox root explorer let me manipulate them and change permissions. I just include that information in case it helps others. I haven't tried to see what would happen if the usb stick were formatted as NTFS, e.g.

I'll see if I can find any further information on the web. Just thought you might know off hand. Thanks
[Nook HD, HD+ Android Development] neutronjeff:
Hi Amaces, is the new TWRP 2.8.7.5 needed for Android M or is it just general improvements usable for L or M?
[Nook HD, HD+ Android Development] andtron:
I used it for LP, so it is for either.
[Nook HD, HD+ Android Development] neutronjeff:
I installed the new TWRP with Flashify and did a clean install of CM13 with OpenGapps nano with no issues so far. Thanks Amaces!
[Nook HD, HD+ Android Development] Monfro:
I am on holiday until 10/01/2016: I hope these new builds bring improvements to the good CM13 base I tried...I hardly wait to test
[Nook HD, HD+ Android Development] digixmax:
Unless I choose to turn WiFi off, my WiFi would stay on just fine. My issue with WiFi is slow-connect (see https://xdaforums.com/showpost.php?p=71653104&postcount=1758).

Others have reported this same issue with powering off, but I have yet to encounter it.

That circle button by default functions as the "Home" button.
[Nook HD, HD+ Android Development] js290:
Wifi disconnects on N2G47J Ovation

Wifi disconnects with new aosp_ovation-ota-N2G47J.170404.zip build. Attaching logcat and adb bugreport.
[Nook HD, HD+ Android Development] tj2003:
WiFi is fixed in today's aosp_ovation-ota-N2G47J.170412 build.
[Nook HD, HD+ Android Development] rpadula:
why there aren't new Lnos builds?
[Nook HD, HD+ Android Development] wally333:
I'm unclear as to why one is better than the other. I installed lnos. The "stable" builds both had dates of Feb 26 2017 -- basically I "flipped a coin" and picked lnos over aosp. This lnos version has some quirks but seems to work well for my wife, Only the HBO Go app is unusable, but the reviews in the Google Play store strongly suggest she is not the only one having issues with the current version.

Which one should we be using?

It doesn't seem like there are enough developers to maintain two competing versions for this obsolete hardware. (The Nook HD+ may be obsolete, but you'd have to spend a lot of money to get a screen as large and as good). One solid version would be way better than two versions with different problems.
[Nook HD, HD+ Android Development] BultoPaco:
Just dirty flashed new lnos for hummingbird that showed up in the experimental folder today. Watched some video on YouTube and the Big Ten Network. Also tried Kindle app and Nook 4.6.1.35 app. Everything ran very smoothly and no lag in switching apps. Oh, WiFi connected instantly on the initial boot? Haven't tried any casting yet but new release looks good so far -- thanks again [MENTION=4473900]amaces[/MENTION]!!!
[Nook HD, HD+ Android Development] dbrickg:
Just now flashing it on my ovation .... And there it is. Looks good. Wifi is doing well. Many, many thanks to amaces, indeed!
[Nook HD, HD+ Android Development] NE0HP:
New build lnos_ovation-OTA-N2G47E.170415

Dirty flashed this New build lnos_ovation-ota-N2G47E.170415 over lnos_ovation-ota-NOF26W.170226 and as always it just boot perfectly fine and on top of it wifi immediately connected and works flawlessly without any disconnection. Also great to see Android Version updated to the latest 7.1.2 with 5th April security patch.

Thank you [MENTION=4473900]amaces[/MENTION] for all your hard work :good:
[Nook HD, HD+ Android Development] dk1keith:
can anyone tell me which gapps work with the latest Inos version?

thanks
[Nook HD, HD+ Android Development] digixmax:
open_gapps-arm-7.1-pico-2017[mmdd] at http://opengapps.org/#
[Nook HD, HD+ Android Development] dk1keith:
thanks for the reply. Yeah that one works. Having a weird issue with wifi though. I'm on the latest lnos version. It seems to randomly disconnect. I'll do a search and see if its a common issue or if there is a fix.

thanks
[Nook HD, HD+ Android Development] amaces:
Since the new builds contain much newer Wi-Fi drivers that took some time to adapt, do report any unusual issues with connectivity, battery life, etc. In related news, I'm starting to collect answers to FAQs, which I should've done a long time ago. Restructuring the OP and following posts will happen gradually.

Pico should still work, and are better on N anyway.

You're an old timer; as you probably inferred, they weren't ready… Lineage finished merging their 7.1.2 just a couple of days ago.

Yup, picking randomly is good enough before forming a preference.

You're half correct, but that's not how this works… at least not my trees. I commonized pretty much everything that could be, same kernel, etc. Thus, remaining issues are pretty much the same, and well known. Eliminating them is an ongoing effort.
[Nook HD, HD+ Android Development] digixmax:
Just dirty-flashed LN 14.1 04/15 build -- I still have the WiFi slow-connect issue which I had previously reported (https://xdaforums.com/showpost.php?p=71653104&postcount=1758).
[Nook HD, HD+ Android Development] amaces:
That's unusual, but once connected, it should stay connected. Also, these new drivers should scan and associate much faster… Have you tried the AOSP builds, or a clean Lineage install?
[Nook HD, HD+ Android Development] NE0HP:
It is stay connected with my ovation after dirty flashing new build lnos 15/04 over 26/02. In fact I watched online movie of about 2 hours using Amazon Prime app yesterday and not experienced wifi drops a single time. I tried and connected device on different wifi hotspots and it not just connected quickly but it stay connected flawlessly!

UPDATE 1: WiFi doesn't automatically connected at two different hotspots today. I tried to turned my saved wifi "off" and then "on" but it still doesn't connected and eventually I've to manually connect it to work. Don't know what happened overnight...I will check again wifi stability at my previous wifi hotspots where it connected quickly and remain stable and update accordingly.

UPDATE 2: Again I've checked WiFi stability today at WiFi hotspots I connected yesterday in which I experienced stable wifi connection and surprisingly it connected automatically and quickly as soon as I opened Nook HD+ and it remains stable as well! I tried and forget that WiFi hotspots, then reconnected, turned "off" then "on" again and it quickly connected automatically. Don't understand this strange behaviour of WiFi connections as some wifi hotspots device connected automatically and remains stable and on other WiFi hotspots it doesn't works!

This are just my observation so thought to share here....
[Nook HD, HD+ Android Development] biowaht:
Hi everyone. I am having a small issue - more cosmetic than anything, but nonetheless is bothering me. I have tried the latest, at least as of last week, builds of AOSP, CM, and Lineage (all Nougat) on my Nook HD+, and with each of them, when I have any apps running and I tap the recent apps button, the windows (not sure if that's the right word) for the apps appear normal, but the previews, shown within those windows, are squished horizontally. This seems to only happen when in portrait orientation, which is mostly how I use my tablet - when in landscape orientation, the previews seem to show normally.

Is this a known issue? And if so, is there any fix for it? Like I said before, it's really just cosmetic, but it's seriously bugging me regardless.

Thanks,

Will
[Nook HD, HD+ Android Development] amaces:
If you can extract logs (dmesg & logcat) after it happens, and attach them here, that could help narrow down the issue. I have a fairly standard WPA2/AES network for testing, but there are countless different setups out there.

I definitely noticed it, but haven't found a solution yet. We're forced to use screenshot workarounds with our old GPU drivers, but this particular bug only started with Nougat.
[Nook HD, HD+ Android Development] jernyx:
There is one minor annoyance I've had with the lnos builds every time I flash a new one. The default browser keeps crashing. Fixing it by deleting Browser.apk with the terminal is easy enough, but I'm wondering if others are experiencing this and if there's another method to fix this or remove the app without root.
[Nook HD, HD+ Android Development] vinceweis:
Wi-Fi is solid for me when the signal is strong. My problem is that most of the time, I use this outside my house on the fringe of signal strength so it often loses the signal. The HD+ used to reconnect pretty quick. The current drivers rarely reconnect and usually require me to move back into a stronger signal area to get it to find the router at all.

Otherwise, this new build is working great.
[Nook HD, HD+ Android Development] digixmax:
Indeed, once connected it does stay connected (no connection drop), but it takes a long time to connect -- even much much longer than with the previous build 02/26. The WiFi connect issue also makes it hard to get on the network to complete the initial setup after a clean install.

I downgraded back to the 01/04 build and WiFi instant-connect is back:). FWIW my home WiFi setup is Asus RT-N16 running Shibby TomatoUSB firmware using WPA-Personal/AES authentication.
[Nook HD, HD+ Android Development] starbright_:
Can you give us some details, how usage of greenify speed it up?

My nook HD+ has been again suffered from a very special disease: After a while of usage (mainly mupdf for reading pdf magazines) the touch screen seems not to work anymore in the proper way. It is still recognicing actions, but seem to interpret them wrong. So I can't even reboot in the normal way, as I can't hit the On/Off menu button for Shutdown/reboot.

I have to reboot the hard way (by long pressing power).

This has been observed also in previous versions CM13, CM14, LOS. Don't have gapps installed - so not much other load ...

The only other "problem" is that I can't power off. It is rebooting instead. This has been reported also by other users. This is also not working in TWRP.

Beside this I am very, very satisfied and happy, that this device still is up to date.

I've seen a new version of LOS is out, so I will use this. Thanks [MENTION=4473900]amaces[/MENTION]!
[Nook HD, HD+ Android Development] NE0HP:
Please find attached files containing logs. This are the logs that I've fetched at one of WiFi hotspot where I'm facing issue with WiFi connectivity. Strangely It doesn't automatically connected even after it is one of my saved hotspot but once I connect it manually it stay connected. I hope I've fetched the correct logs that you're looking for to narrow down the issue!
[Nook HD, HD+ Android Development] mmnspeed:
I used to use greenify app an older device.Started using on Nook HD+ recently.Basically you need a rooted device.I had noticed that while using PDF files ,opening some other apps like instapaper and browsing through chrome,my device would at times become unresponsive due to lots of apps and services running in the background.It was frustrating. I had bought the paid version of the greenify app in the past,so installed it.What it does is that it hibernates the apps that you add to a list.Once the device goes into sleep,it automatically hibernates those apps.Also you can add a shortcut to manually hibernate the apps anytime you like.It is far superior to a task killer.The result is that I am able to multitask without any issues.The paid version allows you to hibernate system apps too.It also used to improve the battery life,but haven't found any noticeable difference on ovation.I have added system apps(except the extremely critical ones,the app will warn you) as well as all the apps I have installed to be hibernated.Basically there isn't much running in the background on my device and this is achieved without breaking any functionality.You can start any app you like instantly.

Edit:It seems to work on non rooted devices too,but that is pointless in our case.:)
[Nook HD, HD+ Android Development] webman2k:
Thought I'd post my experience going from Stock on Ovation (Nook HD+) to the latest of amaces' builds.

Coming from stock, I used his boot sd image, and flashed TWRP 3.0.1-0, then the 4/15 Lineage build, then the latest pico gapps. Everything seemed to install fine, but on reboot, during the setup wizard, the wizard would crash every time when choosing to setup as a new device. I had found some issues regarding this, and advice about adjusting permissions in between dialog boxes, but they didn't work. Tried the same process (after complete wipe) with AOSP 4/15, with the same results. Next, I wiped and just flashed the AOSP build. That rebooted perfectly, so after some initial setup I booted from the SD again and flashed the pico gapps. That worked wonderfully. Props to amaces for getting up to date software running on this aging device. My only issues are as follows:

1. Launcher3 crashes when choosing wallpaper, and it looks like settings are missing. Replaced with Nova (for a better experience anyway)

2. Stock browser crashes when trying to download (think stock browser crashing issues is known). Replaced with Chrome.

3. Search bar on home page (launcher3 or stock Nova config) doesn't do anything, but I'm guessing that's because I don't have the "Google" search app installed? Removed in Nova.

Other than that, no issues to speak of, except the power off issue that's already been reported. Everything seems stable, but understandably sluggish at times. Fantastic work.
[Nook HD, HD+ Android Development] mikeataol:
for a long time now the stock browser has been shipped in ROMS (I think its every CM based ROM for the last year or so) without the permission set properly.

I usually just set the permissions to everything and downloading works

What I've also seen is that it fails to save history and bookmarks.

I guess it's assumed people will use chrome
[Nook HD, HD+ Android Development] webman2k:
Thanks - figured it was something like that. One other issue I forgot to mention. The app switcher (multitasking pane) shows screenshots that are squished slightly. Everything functions properly, just weird. Wondering if anyone else had noticed that. Don't know if it's exclusive to this build, AOSP or what.
[Nook HD, HD+ Android Development] zspeciman:
I also had the setup wizard crash each time and was stuck on that step. But then I noticed that the drop menu on from the top works, so I enabled/connected my wifi to my network and that solved my problem and let me continue the setup.
[Nook HD, HD+ Android Development] webman2k:
Huh - I got access to the settings menu in-between prompts, but I hadn't thought to do some basic setup in there and try again. Good to know if I flash again. Thanks!
[Nook HD, HD+ Android Development] amaces:
This used to happen with the original B&N touch driver fairly often, but not really with the drivers I adapted from hammerhead/angler a few months back. It may be that built-in firmware in certain hardware revisions is buggier than on others. A long time ago (before CM12), firmware was updated at boot, if I recall correctly, but we're not doing that anymore.

Have you tried turning screen off, waiting a few seconds, then back on? That should power-cycle the touch driver, and used to fix it.

The truth is that I looked at this from various angles for the past two years, yet it's unlikely to be fixed before we switch to the 3.4 kernel.

Do you know if these are roaming APs, and whether authentication is different with the failed ones (e.g., WPA*/AES vs. EAP vs. open)?

The logs are good, but I'm confused about the errors that I see therein. It's as if FW scan commands are sent while the hardware is shut down (which could happen after connectivity loss). So, it's not that scan or connect commands are slow, but rather that it keeps rebooting itself, until the hardware starts responding properly.

Likely same as above. I've uploaded experimental Lineage builds with same drivers but old firmware, and a few background scan tweaks. I'd be surprised if old FW blobs fix it, but let's give it a try.

The background scan changes might help with your issues. I made it scan every five seconds when signal drops below -70 dBm, and 60/120 seconds otherwise.

That should be fine, although our TI WiLink 8 firmware might not play well with BCM chips. We'll go back to old WLAN drivers if these issues persist.
[Nook HD, HD+ Android Development] digixmax:
In my case, the slow-connect behavior applies to both my home router WPA-P/AES and the public open hotspots in the building at my work place.

I had not gotten around to capturing any log, but I did notice that the entry on the list of hotspots in Settings->WiFi that corresponds to the hotspot that my HD+ was trying to connect to would repeatedly bounce/flicker which I assume to be indicator of connection being attempted unsuccessfully.
[Nook HD, HD+ Android Development] NE0HP:
Dirty flashed this new lnos ovation 04/18 build over 04/15 and again WiFi doesn't connected automatically at the same WiFi hotspots where i was facing connection issues. But I've RESET NETWORK SETTINGS and re-connected to that same WiFi hotspots and as usual It just connected.

I turned WiFi "off" and then "on" to check if it's automatically connects and recognises this device or not....And BOOM! It quickly recognised and connected automatically! I did this several times to check the stability of connection and it works perfectly fine and it stay connected as well!

I will again check this tomorrow as well when I will come back to this WiFi hotspots to see wether it still recognises it and connects automatically or not and update here accordingly!

Thank you [MENTION=4473900]amaces[/MENTION] for the quickly responding to this matter and providing possible fixes! Would be great if other members whose facing WiFi issues also shares their experiences if they have clean flash/dirty flashed this new lnos ovation build!
[Nook HD, HD+ Android Development] webman2k:
Battery Life

Can anyone comment on battery life with these new AOSP and Lineage builds, as compared to CM 11-12 on the Nook HD+? I'm on the AOSP 7.1 build and I lost about 10% while idle overnight - Wifi disabled during sleep.
[Nook HD, HD+ Android Development] zspeciman:
I have both the nook hd 7" and the nook hd+ 9", two of each, and all on the 4/15 build. For some odd reason, the CNN app runs smoothly on the 7" but struggles or won't get beyond a black screen on the 9" devices. The difference is night and day when it comes to this particular app. This occurred on earlier builds as well. It has become a problem ever since CNN updated this app few months ago. Has anyone else experience this issue? is this a hardware limitation on the 9" device?
[Nook HD, HD+ Android Development] digixmax:
I have only used LN14.1 01/04 and 02/16 builds -- battery consumption seems much better with 01/04 than with 02/26.
[Nook HD, HD+ Android Development] dbrickg:
I'm not having any WiFi issues, but the only place I use my nook hd+ is at home, so it could just be an issue with certain wifi hotspots or simply changing from one to another.

Anyway, I concur with neohp in thanking amaces for his attention and dedication!
[Nook HD, HD+ Android Development] amaces:
Can you try the latest builds? I redid some of the WLAN power hooks, which hopefully fixes those firmware recovery events. Once those stop, connections should be pretty fast and consistent. But yeah, I wasted too many weeks on the new drivers to go back now.

That's definitely not the goal; I think close to two weeks of (only) standby from full charge should be doable (Wi-Fi always on/no GApps). Can you try the new builds, w/o disabling Wi-Fi during sleep (although I saw three-four weeks estimates with it disabled)?

Maybe the app sends HD video based on the 1080p resolution, and the DOMX codecs fail somehow. That is much more likely to happen after the dynamic tiler changes last winter, which are very useful otherwise. Can you attach dmesg output after it happens?