yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] simon-edwards:
Yes, search this thread for battery woes. which essentially boils down to the advice given above in post #977. You need to re-build the hidden system files which manage the battery. This is achieved by flashing stock recovery and using that to do a factory restore. It seems to cure most odd behaviour which comes on after a long time.

---------- Post added at 03:08 PM ---------- Previous post was at 02:39 PM ----------

Those with long memories may remember my comments back in March about any sd card larger than about 64Gb not being usable in our Nooks with CM13 installed. Looking around XDA I've seen other roms with the same issue.

I had thought it had to be moved to start at the first sector of the disk to be useful, I was wrong.

I've just been testing a newly delivered SanDisk card which refused to work. This is the partition info on the card as delivered from the factory as seen by Easeus' Partition Manager.

Disk type MBR

* Unallocated 16.00MB Logical

E: Other 183.33GB Primary

CM13 displays this as an unrecognised card and refuses to use it.

If you let Windows format this disk it will re-apply ExFat. However after that Windows format the disk partitioning is now hidden and the system displays it as a "superfloppy" which prevents further partition watching/modifying.

CM13 still displays this as an unrecognised card and refuses to use it.

To recover the ability to do anything with the card you need to remove the existing contents completely, including the master boot record content. The easiest was to achieve this is to run a sector by sector flash drive test in a destructive write-read-test cycle. I used Flashtester v1.14 for about 15seconds to do this. You could of course prove that the card is not faulty/fake at this stage if you wish.

Now, with a fully blank card, Partition Manager will let you experiment with different partition start points and other MBR flag settings.

It turns out that our CM13 problem is caused by that "Primary" partition flag. Set this partition to "logical" and the Nook will recognise FAT32 and ExFAT formats, with or without Windows doing the formatting.

Experimentation showed that when given cards with multiple partitions the Nook "sees" only the first logical partition with a valid file system. All other partitions are ignored.

This only seems to affect large cards. Although I have not done any recent testing with small cards to check their partition table content.

So, problem solved, and its quite simple to do too.

BTW This is what the partition table looks like in working form:

Disk type MBR

* Unallocated 7.84MB Logical

E: Other 183.33GB Logical
[Nook HD, HD+ Android Development] mikeataol:
unplug the cable from the unit....

press and hold the power button in for AT LEAST 30-45 seconds...

let it go , plug in the charging cable , walk away from the unit and give it an hour.

it will likely boot when it realizes it has sufficient charge.
[Nook HD, HD+ Android Development] duke7553:
Unfortunately, that did not do the trick. Thanks for your help, dedication, and input.
[Nook HD, HD+ Android Development] TBueno:
Thanks a lot for the walkthrough. I haven't used a external SDcard for a while on my HD+. Have you ever tried consolidating external and internal storages (that android 6 feature)? Wonder if it would work on our devices.
[Nook HD, HD+ Android Development] simon-edwards:
Yes it does work, or at least it does work on my Nook HD, I didn't try on my HD+ but there's no reason that it shouldn't work. When you first mount a card that the system has not seen before it asks if you want to use it to transfer content between devices or to integrated it into the system storage. I can't recall the exact phrasing.

It was a long time ago, but I recall that having selected the internal storage option the storage pool appeared as a huge seamless area.

IIRC Access to that pool then must be done through the Nook to manage the merged file systems. Which means doing it at USB2.0 speeds. Which is a bit of a problem when it comes to populating the content.

Its becomes a bit like an iPad then. You either fill it using Apps on the device to download network based content. Or you tether it to a PC and push content down the cable. It takes a long time to switch the content of that amount of storage when you can only use USB2.0 speeds.

I can copy 90GB of card content to a second card in about an hour using USB3.0 readers. I suspect that would take a day or so using USB2.0 speeds.

Having said that my Nook HD+ has a 32GB internal store, I have a 200GB (at least that was what was written on the packing - pre formatting) card to hand. So I could have a system that behaved as if it had 232GB of internal storage. Now that you have made me think about it I may do that for a while "just because" :).
[Nook HD, HD+ Android Development] mikeataol:
I think you couldn't possibly have done the part that said

"walk away from the unit and wait at least an hour"

The CPU needs to sense a minimum battery capacity to start the unit.
[Nook HD, HD+ Android Development] lath19:
I flashed AOSP last night and it's really smooth. Seems I have lost root though. Anyway to regain root without going back to stock?
[Nook HD, HD+ Android Development] games906:
Still have TWRP? Just flash SuperSU zip (an earlier one, though)
[Nook HD, HD+ Android Development] lath19:
Yeah, I can still get to twrp. Downloaded SuperSU from play store last night, guess I should have flashed instead. Thanks for tip.

Edit: Flashed SuperSU 2.52 and that fixed root. Thanks again.
[Nook HD, HD+ Android Development] gwisch:
I just flashed the CM13 version of May 30 on my HD+ (dirty) and now constantly receive the message that Google Play Services closed.

I seemed to remember from somewhere that uninstalling any updates of them and let the system reapply the updates again will fix the problem, however the buttons for deinstalling (and task closing) Google Play Services are greyed out - so no luck there. And when I open Google Play, the screen becomes blank and stays that way, so no uninstall via this route either.

Has anyone had the same problem and by chance found a solution (other than a new flash completely from scratch - I did this with the May 16 version and hoped the problem would be solved now) ?

Also something very strange: Among other players I use VLC.

CM13 for the Nook HD+ does not seem to register VLC as a player that can be used for streaming from remote sources (LAN/WiFi). It does so for MX Player and a couple of others, though. My other devices (Samsung Galaxy Note 4 with rooted 6.01 stock firmware and Samsung Galaxy SII with CM13) do not show this behaviour, i.e. I can stream without any problems from any device on my network using VLC.

Problem is, I can't let go of VLC as it is the only player I know that can interpret AC3 audio (and basically plays anything I throw at it).

Thanks in advance for any help.
[Nook HD, HD+ Android Development] ajislav:
Try this

1 go to recovery

2 backup

3 format system

4 flash ROM and gapps (try the gapps you flashed initially)

5 reboot
[Nook HD, HD+ Android Development] gwisch:
Thanks.

Did as described above - without any change in the behaviour of the system.
[Nook HD, HD+ Android Development] ajislav:
I am actually having the samé problem since updating last night.. I will let you know once I find the solution
[Nook HD, HD+ Android Development] gwisch:
Again: Thanks.

Edit: And one more problem. When trying to flash the current nano open gapps version I get the message that there is insufficient space on the system partition which is hard to imagine considering that that selfsame version was already on that partition.

Installing the pico version instead results in "Setup Assistant closed." and the screen remains dark.
[Nook HD, HD+ Android Development] marc70:
If Nook is not charging. Green light all the time or no light with Nook charger on. Solution that worked for me: Unplug Nook cable. Press power button and n button Nook for 10s. Nook swiches off from stand by mode. Plug back on charger.Then press power button. Light goes from green to amber then back to green. but quickly, Unplug cable and put it back. Amber light back and steady! Charging at last!:D Maybe it will work for you.
[Nook HD, HD+ Android Development] gwisch:
After a complete reset and installation from scratch (with the May 30 version) everything runs again as it should.

The problem with the nano/pico installation of Open Gapps remains, though - the nano installation claims not to have sufficient room on the system partition. Pico went through without a hitch.
[Nook HD, HD+ Android Development] ipdev:
I normally format data, reboot into recovery, advance wipe all except external sd. Then reboot into recovery and install from external sd. (Lately I've been using the adb sideload option in twrp.)

When I run into persistent problems, I restore nook os, update and deregister. Then reinstall twrp and start again.
[Nook HD, HD+ Android Development] gwisch:
Yep, that's exactly what I did (except the latter part, no nook os involved anymore).
[Nook HD, HD+ Android Development] ipdev:
I'm curious if it would help? I have flashed stock os on a few devices to fix/update firmware, partitions, ect.. The last time I had issues with wifi on my ovation, flashing nook os, running two updates, then deregistering the device, since then I've had very few problems.
[Nook HD, HD+ Android Development] mrhanky89:
Hi. I have followed your suggestions. Now I am wondering what else I can do speed up my nook hd+ with this AOSP rom?

Things I did

formatted those partitions as f2fs

disabled services that were not relevant to me

flashed supersu

disabled UI animations

installed nova launcher

Is this the best rom right now? I stopped using my nook for a while and I last had slimbean installed. Are there any other more modern roms I should try for performance?
[Nook HD, HD+ Android Development] mikeataol:
I haven't seen any difference in performance between the AOSP and CM versions....
[Nook HD, HD+ Android Development] hajkan:
Not awake

Hi

I insstaled the latest cm13 on my Nook HD. Everything is working as far as I can tel exceptt that I cant make the screen stay awake when it is plugged in (which I selected it under dev options). It seems like the screen goes blank after 30 mins(which is the max value under the display settings)

thanks
[Nook HD, HD+ Android Development] Technosquid:
I've been having the wake problem on hummingbird as well. I decided to go back to a build from February I had backed up. You might want to try an earlier build from the "obsolete" folder until it's fixed.
[Nook HD, HD+ Android Development] belfastraven:
New AOSP 6/14 roms in Experimental

Running well on hummingbird. I am running with open gapps 6/14 pico and superSU 2.74 (SYSTEMLESS=false). This is very subjective, but it felt like the initial compile/"optimization" of apps on first boot was faster. WiFi comes up immediately and the rom is very smooth.
[Nook HD, HD+ Android Development] pchc_lx:
noob question, but could you explain this?

i thought superSU was just an .apk used for rooting a device, and would be unneeded on a rooted ROM. clearly I'm missing something. also, what is the SYSTEMLESS option for?

thanks. been loving the latest stable OVATION build.
[Nook HD, HD+ Android Development] belfastraven:
The cm roms come with the ability to be rooted (it's an option in developer options). The AOSP roms require SuperSU to be rooted. If you do a clean install (I did, because I had been testing a bunch of changes on a nook running AOSP, the rom needs to be rooted. To root it, you need the zip, not the apk. The 2.52 zip will work--later versions of SuperSU will try NOT to modify the system partition (so that devices can receive OTA updates). We do not need that facility and it doesn't currently work for us. You can , for example, go into the terminal in TWRP and enter

export SYSTEMLESS=false

before installing the zip. If you already have superSU installed and do a dirty flash of the AOSP rom (over another AOSP rom) you should still have root.
[Nook HD, HD+ Android Development] TBueno:
I'm not an expert, but I've heard since android 6.0 some device makers are setting up a /system partition check at boot: any changes from stock (such as root) would prevent device start or OTA updates.

So Chainfire came up with a way to circumvent this, enabling users to achieve root privileges without tinkering with /system.

So the systemless=false flag probably means ROMs such as ours won't punish any user for doing whatever they want with their system partition.
[Nook HD, HD+ Android Development] ieatabiscuit:
SuperSU is there to manage root privileges on a roted device. There's other options for this same purpose also. The systemless=false means it is not installed using systemless method, but the old school method. You install a rooted ROM without something like SuperSU, and it just won't have the rooted goodness available. Still rooted, but not managed. Ant yes systemless is an effort to get around things like Knox and others. Not sure if it still works like it was meant due to updates and such, but it hardly matters on a device like ours.
[Nook HD, HD+ Android Development] Erkdajerk:
Wow, what a difference. I was a regular user of successive CM builds back when they were labeled as "final" or "stable". I ended with the last stable 10.2.1 and stuck with it. Over time, it has gradually become slower and virtually unusable, to the point where I actually bought a Windows tablet...oh, the shame. Due to the positive reviews here, it was time to dust off the HD+ and apply the MDU (Marshmallow Defibrillator Unit) as per the instructions in these forums. I am happy to report that the patient is now healthy and rejuvenated with a new lease on life. "it's alive, it's alive!" This thing still has a lot going for it and I think my Windows tablet will gather some dust for a while. Many thanks!
[Nook HD, HD+ Android Development] neonleon29:
Not sure this will work for you guys, but I also would get green static when going full screen when watching a video. To fix this, I installed MX Player. When watching a video on Youtube and going full screen, I tap on the video and get 3 vertical dots to show. I tap on the dots and it gives me the option to open an app. I pick MX Player and the static goes away. You will probably notice the audio will now be out of sync with the video. By choosing the option "SW" instead of "HW" for the decoding will bring the audio and video in sync. You should now be able to watch the video full screen without static.
[Nook HD, HD+ Android Development] eng3:
I installed TWRP 3020, then flashed CM (5/31). Couldnt flash Gapps nano, had to use pico. Had to set SYSTEMLESS=false to get supersu flashed.

Everything seems to be working although the whole system seems rather sluggish, like lag when clicking.
[Nook HD, HD+ Android Development] TBueno:
Sounds awesome, MX is arguably the best player out there.

However I can't find the option to open the video with an external app. Three dots gives quality settings, cardboard and something else, no "open with". And MX is not included among sharing options.

I've tried web and YouTube app. In what app exactly you've found the open with option?
[Nook HD, HD+ Android Development] BultoPaco:
So maybe this is a good time to consolidate knowledge of what works well from recent (and not so recent) posts in the thread.

1. CM builds have a version of SuperSU built into the ROM. Only flash Supersu with the AOSP builds.

2. CM builds are probably best for most routine users because they require less customization to obtain a pleasant user experience -- unless you absolutely need the screen cast feature.

3. Steps to get a smooth operating CM experience -- used on both HD and HD+

a. Nandroid backup in TWRP

b. Backup all apps and data -- I imagine most folks use Titanium Backup

c. Take screenshots ( saved to SD card) of your home screens so you can reestablish the environment you like

d. Reboot to recovery (TWRP) and do a normal wipe plus wipe System. -- your judgement if you want to wipe more or less

e. IMPORTANT -- at this point reboot to recovery before you flash anything

f. Flash CM160530 and Pico version of Open gapps

g. Reboot and go through device setup -- do not let Google restore your apps and data.

h. Download Titanium Backup from the app store and navigate to your backups on the SD card and restore same

i. Consult the home screen screenshots to reestablish your environment.

I apologize to advanced users for the length of this post but I hope it helps some folks get the most out of these still very capable devices.
[Nook HD, HD+ Android Development] ipdev:
SuperSU is not needed in cm but, works very well.

You need to disable built-in su on cm build for best results.
[Nook HD, HD+ Android Development] mrhanky89:
Is the network adapter on the nook able to handle more than 30mb/s. That seems to be the cap on speedtest. Are there any like tcp/ip fixes? Or a power saving setting that is doing this?
[Nook HD, HD+ Android Development] BultoPaco:
No doubt you are correct. We have a community here of a wide range of knowledge and skill levels. I keep reading posts of people fumbling the installation and I wanted to give an approach that will likely result in getting the joy out of [MENTION=4473900]amaces[/MENTION] amazing work. As we learn more, we can tinker more and that's where the fun is[emoji4]
[Nook HD, HD+ Android Development] eng3:
I also thought that SU was built in on CM builds. However after flashing, and trying to run Titanium Backup, it complained that it could not obtain root. Thus I went and installed SuperSU.

Yep, this is pretty much the procedure I usually follow when flashing on anything.

I flashed the ROM, then Gapps.

After that I rebooted and tried to restore using Titanium Backup.

If you want to avoid people asking questions/fumbling, I suggest that those steps get added to the original post. Although, I certainly appretiate all the hard work put into the ROM, it did take alot of reading of the original posts plus in the thread just to figure out which rom file to use. Then some searching to find some answers. I think it is very reasonable to expect someone to read the original post, but I don't think it is uneasonable to expect one to sift through 100 pages of posts to find an answer. I've installed CM11 and CM12 on the nook and ROMs on all of my previous phones so I'm not quote a novice but I'm not an expert either. So I knew enough to know what to search for. Someone more novice might not.
[Nook HD, HD+ Android Development] BultoPaco:
No offense intended -- just trying to help. As [MENTION=7280276]ipdev[/MENTION] pointed out, you need to set Root Access to Disabled in Developer Options when you flash the SuperSU zip. Then you can use the SuperSU app from the app store to keep the binary update.

I'm in the the same boat as you -- no expert. I don't expect [MENTION=4473900]amaces[/MENTION] or any of the more knowledgeable folks to hand me anything more than they have graciously provided. Like you, I read everything and make plenty of my own mistakes. I contend that is one of the best ways to learn.
[Nook HD, HD+ Android Development] hajkan:
Hi

WHen I installed the latest aosp on HD+ I get android phone something stopped message after startup and I could not pass that message pop up. Is there a solution to that?

Also any tweak recommendations to speed up CM13 on HD+?
[Nook HD, HD+ Android Development] TBueno:
Check out this thread, you can simply grant one permission to Setup Wizard and be done. It does requires some patience though (interacting with the device between dialog pops).

As for snappiness, you can try tweaking animation and transition speeds in developer settings.
[Nook HD, HD+ Android Development] neonleon29:
I think I ran into the same problem you are having without getting the option to open an app to choose which video player you want to use. It was a while ago, but I think what happened was when I side loaded Flashplayer, I made that my default video player. So I never had the option to choose a different video player when watching a video. By removing Flashplayer as my default player, it now gives me the option to select MX Player when I'm watching a video using the method I described previously. Any chance you have a video player already selected as the default player? If so, try removing it as the default and see if that works.
[Nook HD, HD+ Android Development] hajkan:
Hi

How do I keep connection alive with HD and HD+? HD keeps disconnecting after sometime even though it is on charger at all times and the screen is kept alive.
[Nook HD, HD+ Android Development] pchc_lx:
Just want to chime in as a long-time user of MXplayer (it's almost exclusively what I used my Ovation for)- you should know using SW playback is forcing Software Playback - i.e. disable Hardware Acceleration for video playback. This will drain your battery very fast while playing video.

The absolute best is go into the settings, find the setting for "custom codec" and follow the link to download the custom codec for the player. Then change settings to always try HW+ playback- this will be the smoothest, best looking video while taking advantage of full hardware acceleration- getting you many more hours of playback on a single charge.

It's a few steps but it's worth it. In general HW+ playback > HW > SW. I can't speak on this specific issue of Youtube playback however.
[Nook HD, HD+ Android Development] eng3:
I have just been using HW+ playback. Never sure if it is really using HW. I'll try the custom codec. Thanks

I have noted the DirecTV app will force close whenever I run it. Not sure if anyone here uses that.
[Nook HD, HD+ Android Development] sww84:
Dose it work?
[Nook HD, HD+ Android Development] HarvHouHacker:
Hmm, I didn't see this thread before, and I've already commented on amaces' previous project of CM 12.1. Oh, well!
[Nook HD, HD+ Android Development] sepehr@teh:
Hi,

I'm using AOSP ovation MHC19Q.160.406 . It's few months.

Is there new update ? I saw a new version in experimental folder .

Is it OK to update ?

If yes so how I can update it without need to install everything?
[Nook HD, HD+ Android Development] starbright_:
How to installiert an APP in aosp? At least TitaniumBackup or fdroid. Don't want Google store. There is not even a filemanager. Using download i can select an apk file, but geht the response: can't open the file.

Aosp seems really naked vs. CM, but is snappier.
[Nook HD, HD+ Android Development] lmacmil:
Took the plunge and installed CM13 on my HD (Hummingbird) today. I used Belfastraven's SD card image and it booted right up. First time using TWRP. First screen had me stymied a little so I picked the default (I think) and forged ahead. Had forgotten how long the cache formatting operation took (about 10 minutes). About halfway through the screen started flashing every 5 seconds or so. I had read about that but had forgotten.

Loaded the TWRP 3.0.1.0, the latest MM build (MOB30J.160530), and pico GAPPS from OpenGapps.org. The only hiccup was when I had pretty much finished the setup, I set it down and when I came back, it had shut itself down. Booted back up and seems fine. I was using the latest CM11 nightly. Too early to tell if CM13 will be an improvement and if so, how much of one. I do like being on the latest version of Android, official or not. Thanks to all those who contributed to this project and for keeping our Nooks alive! :o
[Nook HD, HD+ Android Development] vinceweis:
The experimental folder shows it has 1.2 GB size but when I go there, it is empty. Am I missing something or doing something wrong?
[Nook HD, HD+ Android Development] lmacmil:
I think it just means there are no current experimental builds. All builds are in the appropriate device folder.
[Nook HD, HD+ Android Development] sepehr@teh:
Hi,

I'm using AOSP ovation MHC19Q.160.406 & it's stable ! There is new updates in experimental folder .

Anyone using ? Is it OK to replace ?

How can I replace it & keeping installed apps ?

Thanks ~
[Nook HD, HD+ Android Development] lmacmil:
After one day I'd say it is a definite improvement over the CM11 nightly. I did have to reflash SuperSU. It would update the binary on its own.