yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ieatabiscuit:
Could it be possible that a setting in your router isn't playing nice with the nook? I'm using the 02/04 AOSP ROM currently, and TRYING to make something break... So far my wifi has been perfect.

Also, [MENTION=4473900]amaces[/MENTION], so far, I have done a factory reset from the stock recovery, flashed your 2.8.7.5 TWRP, and then with nothing more than a very basic wipe, I installed the AOSP ovation build with pico gapps immediately. So far it's been flawless. Did some updates, put super su on it, and have just unplugged it as it reported a full charge with the LED. I'm going to run it ragged burning SOT, and constant wifi interactions for a full charge cycle, and then recharge. I'll update tonight or tomorrow with any findings. All goes well, my partitioning corruption theory is true, and the battery issue some people have can be fixed, and I'll make a thread to cover it that we can direct people to that wash up here.
[Nook HD, HD+ Android Development] acr123:
under wifi -> advanced do you have keep wifi on during sleep as always?

This helped me but I still occasionally have to reconnect wifi under settings.

I'n using CM13 from Jan
[Nook HD, HD+ Android Development] DE-Nooker:
I don't see any problems with the router config. Stock B&N ROM has worked fine with same router for more than two years.

---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------

Yes, I do. I first thought that this setting might not be active and plugged in the charging cable -> still disconnects.
[Nook HD, HD+ Android Development] veekay:
I had a similar issue with mine. The build runs so perfectly, better than CM12, but the battery life is horrid. I rarely use my tablet so it is mostly in sleep mode, but I am barely getting 2 1/2 days of sleep time, whereas before I could get 30 days out of a charge.
[Nook HD, HD+ Android Development] snoozer854:
Does Titanium Backup work with CM 13 Hummingbird ?

I have tried setting up my ext sd card as both portable & internal card & Titanium Backup shows that card is not writable, but I am able to transfer files to it in ES File Explorer & QuickPic.

Thank you

Mark
[Nook HD, HD+ Android Development] ieatabiscuit:
That could be a side effect to some apps running in the background. I will have to see long mine runs while asleep from a full charge. To date, I can't find a single thing about the ROM its self that seems off to me. Bad apps, however, are plentiful. The FB app for example, will slaughter a battery without mercy.
[Nook HD, HD+ Android Development] TheHamPimp:
I switched mine to disable wifi during sleep, and now I get an easy week out of mine, where without that setting, I got about what you're seeing on light use.
[Nook HD, HD+ Android Development] veekay:
I tried all combinations and even the same app I had to use with CM12 that disabled wifi when the screen was off since the builtin one didn't work. I basically only use mine as a web browser so there are no draining apps on it. As the other user mentioned, wifi would go down and never come back up unless I went into settings and had it manually reconnect.
[Nook HD, HD+ Android Development] belfastraven:
I just now tried to backup one app (right now I have sd card adopted as internal storage--just testing) and the app backed up with no problem. When exactly are you getting the message, and what version of cm-13 are you running? . I think another version will be available soon..
[Nook HD, HD+ Android Development] vinceweis:
I have used Titanium Backup with every build and it always works fine for me. I do use the paid version. Don't think that should make a difference though.
[Nook HD, HD+ Android Development] DE-Nooker:
[MENTION=4473900]amaces[/MENTION], I did create a Bug Report for this issue.
[Nook HD, HD+ Android Development] sasmith-129:
Yes, but you may need to use the folder Android/data/com.keramidas.TitaniumBackup/ (from the root of the sdcard).

I saw this in a Titanium Backup help FAQ when I first moved my ovation to CM13 and it works for me with my external SD card used as portable storage using the free version of TB.

IIRC, it had something to do with the current version of TB not being fully compliant with the MM API access/privilege process/protocol so this version of Android allows access to this app-specific directory for legacy reasons.
[Nook HD, HD+ Android Development] snoozer854:
Thank you very much for your assistance, this old guy really appreciates it.

I found a solution.

I followed the instructions from this video on YouTube & TB backups to a folder I made on my ext card.

https://www.youtube.com/watch?v=DrOuUtlqz9w
[Nook HD, HD+ Android Development] ieatabiscuit:
I did notice some wifi connections issues this morning. Nothing to break out the torches and pitchforks over though. I think it has to do with doze actually. When it's been left to sit (without charging) and the screen is off, or in my case cover is closed, for a long period of time it brings everything up as expected, but wifi does not automatically log onto my network, I have to go into the wifi settings, and tell it to connect manually. Not really a problem for me, but to bring more light to the issue [MENTION=7260824]DE-Nooker[/MENTION] is having here:
[Nook HD, HD+ Android Development] DE-Nooker:
I have the same issue with the AOSP build but it is also present when the screen is off for just 10-15 minutes and this is not a long period of time. The issue is also present while the Nook HD+ is charging and/or in use. E.g., I had a disconnect while setting up my email account and later while checking emails.

With the CM build, I had the same issues with screen off/doze and I also had the issue while the tablet was in use, e.g. when browsing the web using the CM web browser. I don't think the issue has to do with doze mode only, it seems to be a more general one.
[Nook HD, HD+ Android Development] bkerensa:
Any plans for new cm13 hummingbird bill? Last one is from last month and the latest AOSP is newer?
[Nook HD, HD+ Android Development] ieatabiscuit:
I think my instance was a false positive. I had other hardware doing the same thing. After a router reset I have not seen the issue repeat.

Update on battery experiment: After resetting to stock, booting to stock recovery, and doing a factory reset from there, and then flashing the desired recovery and ROM with nothing more than a basic swipe to wipe; I can not reproduce the battery glitch.
[Nook HD, HD+ Android Development] dbrickg:
TWRP 3.0.0.0!

I see there's a TWRP 3.0.0.0 in the experimental folder! Has anybody had a chance to try it yet? Any particularly notable changes? I'll give it a shot as soon as I get home, and report back to the group....
[Nook HD, HD+ Android Development] games906:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html

I don't know if it's the same for nook but I don't see why it wouldn't be
[Nook HD, HD+ Android Development] dbrickg:
Just tried twrp 3 on my nexus 6, and it works quite well. I'll put it on my nook hd+ when I get home later today and report back to the group.
[Nook HD, HD+ Android Development] belfastraven:
It's fine on hummingbird, but may not allow you to see files on adopted storage, if you are using adopted storage. I think it may allow getting logcats through adb, but I haven't tried that yet.
[Nook HD, HD+ Android Development] dbrickg:
Thanks so very much, amaces. I'm heading home now and will download your twrp 3 and report back to the group. Cheers!

OK! I flashed twrp 3, and rebooted into recovery. I'm backing up the current rom to my external sdcard. I'll check back in to the group later and let you know if there's any remarkable stuff, good or bad
[Nook HD, HD+ Android Development] uberchoc:
I flashed the new AOSP build and the behaviour persisted. I just now reverted to stock to see if the behaviour still persisted, and it did. I did a factory reset within stock recovery twice, and that didn't fix it. So it's not a software thing either, I suppose. Now I'm confused. I'll continue to run CM because it's awesome--Cheers!--but I'll have to sigh deeply whenever I want to wake my screen. I imagine it's a defective unit. I'll see if I can replace it. Again, thank you for your help.
[Nook HD, HD+ Android Development] amaces:
So it's a hardware issue after all; sorry to hear that. I was worried it's something in the current kernel, which is pretty different compared to CM11 or stock. Just curious, what's the latest version of the stock firmware?
[Nook HD, HD+ Android Development] belfastraven:
re TWRP

[MENTION=4473900]amaces[/MENTION], using your code, but changing the recovery-twrp/Android.mk so that TW_INCLUDE_CRYPTO := true ( I stuck a line TW_INCLUDE_L_CRYPTO := true in the file before all of the tests-not elegant, I know) and rebuilding allowed twrp to read the adopted storage works and also seems to be fine with no adopted storage. (alpha tested--i.e. I tried it once each way and it worked. ) I don't really know why anyone would need adopted storage, but in case they do :)

Also, I will try to set up a "changelog" system for our roms filtered from your activity feed. Right now I just have an IFTTT recipe emailing them to me, but I think I can set up a news feed and filter it..... will let you know if/when I succeed.

You seem to have been working on this stuff 24 hrs/day--I hope it's still fun...
[Nook HD, HD+ Android Development] uberchoc:
Ha, it's fine. The latest version is 2.2.1
[Nook HD, HD+ Android Development] amaces:
Right, adopted storage is indeed encrypted, and that support was never enabled in recovery. I was planning to look into the various legacy flags (e.g., TW_INCLUDE_JB_CRYPTO, TW_INCLUDE_L_CRYPTO), but looking through the code, they all spill into the TW_INCLUDE_CRYPTO flag. Based on your testing, we just need to add it to the BoardConfig in bn/common. I'll make this your change; if you have an email handle that you plan to use with Git, send it my way for proper attribution/authorship.

Making changelogs, with my current workflow, will be hard since I constantly rebase, mainly to remove cruft and reorganize, but also for the eventuality of merging upstream, or at least into more official repositories. Normally, with collaborative repositories, pushed commits and their history are never changed so it's easy to generate incremental changelogs. You would have to run diffs between different heads, then interpret the differences. That's why you probably get lots of notifications, even when I simply rearrange things.

GitHub can be misleading like that, for the above reasons. Still, it remains my hobby, and there were some promising developments recently, alas they haven't led anywhere yet.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Root access not working properly

Not sure. How to make root access to work properly on cm13 builds. Any suggestions.
[Nook HD, HD+ Android Development] belfastraven:
If you are using the built-in root access, go to Developer Options "Root Access", switch it to disabled, and then switch it back to whichever root you want, e.g. apps, or apps and adb. I think some flag or buffer is not always populated correctly on some initial flashes, and changing the setting seems to fix it.
[Nook HD, HD+ Android Development] ieatabiscuit:
Still going strong with the 02/04 build on my ovation. Nary a problem in sight. Just wanted to put an update out there one last time. Battery reading is normal, wifi is not being problematic, and any apps I have used so far have been playing well also. Thanks again [MENTION=4473900]amaces[/MENTION]!
[Nook HD, HD+ Android Development] games906:
I've been playing Hearthstone (really GPU/CPU heavy game). It's a little choppy but it's still pretty good ??
[Nook HD, HD+ Android Development] Monfro:
I am really happy with AOSP MM build.

It is fast, smooth and has really good multitasking.

It is probably the best rom I had running on my Ovation.

Since Google Play Music is never shut up while running in the background, I can't desire more.

I have to confess I am intrigued by Pixel C navbar layout, it is better also than old tablet layout.

Thank you for your great work Amaces!!
[Nook HD, HD+ Android Development] games906:
I think I might switch back to go ahead a switch back to aosp because cm is a little choppy
[Nook HD, HD+ Android Development] DE-Nooker:
I tried the latest CM build 20160208 and I still have the same issue with disconnects; wifi signal is strong all the time (Nook and wireless router are 2-3 meters away) and rebooting the router/AP doesn't change anything.

One thing that works better now is reconnecting by just choosing a known SSID in the notification shade (this didn't work before but it is really fixed now) and this makes it easier to reconnect after unlocking the device.

I did capture a bug report today and while uploading it to Google Drive I had another disconnect (and Drive uploading error). I then captured a 2nd bug report and can send it to you [MENTION=4473900]amaces[/MENTION] if you are interessted in analyzing it.

Thanks for the fabulous work on the ROMs so far [MENTION=4473900]amaces[/MENTION]. I think, the wifi issue is in the Marshmallow code because other users have similar problems.
[Nook HD, HD+ Android Development] amaces:
Encrypted Storage & Wi-Fi

This was on my mind, and also stumbled on changes that may fix encrypted storage in CM. Anyway, [MENTION=7260824]DE-Nooker[/MENTION], before delving into logs (we'd need Wi-Fi specific ones as well), can you test the current experimental kernel? The changes therein fix all my wireless issues, even with rebooting the AP while connected.

On the other note, people who were set on encrypting your device, can you test again after flashing the respective experimental kernel? I don't recommend slowing the device with encryption, but it would be nice to know that it works.
[Nook HD, HD+ Android Development] belfastraven:
My issues seem to have been fixed in the latest rom, but everything is fine with the new kernel. I am testing encrypting now(just to see what happens) --. I have TWRP set up to deal with encryption. Should people wanting to try encryption be using your latest-TWRP -will there be a problem if they encrypt and are running TWRP without it?

I was able to run encrypt and to run encrypted--I could boot into recovery also and TWRP would also ask for my password. I think encryption is working normally.
[Nook HD, HD+ Android Development] Monfro:
I suggest you to use F2FS filesystem for all partitions (system, cache, data).

This is my actual configuration.
[Nook HD, HD+ Android Development] justwondering:
I have just picked up a used Nook HD7 with stock B+N rom , I had a Nook about 18months ago and install Cyangenmod....worked great !! but sold it in the end and bought a Windows tablet , but need a Android tablet for use around the house...Anyway !!

I've got a quick question or three !!

I was reading the PeterInsequim PDF , Can I install "AOSP 6.0/CM 13.0, ROM for the Barnes & Noble Nook HD, HD" From CWM or do I need TWRP ?

What is the difference between the CM , AOSP and Twrp downloads ? is CM for Clockwork mod installs ?

Which version do I need to use for a stock B+N Nook HD7 ?

notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332708110

Would this be a good rom , to use for day to day use , surfing , email etc and is it in a pretty reliable functioning state ?
[Nook HD, HD+ Android Development] amaces:
Good, it means that it works. The encryption process would fail very early on. Also, if you're using a TWRP image compiled from latest code (or one in experimental) the proper support should be there, since it was added for adopted storage.

Wait, /system should remain ext4; assuming that you somehow maintained F2FS after flashing ROMs, fstab only knows about ext4 there. You could check your current filesystem in recovery (or run mount| grep system). Otherwise, totally agree about F2FS on /data and /cache.

Sigh… Thousands of people found the the link in the first paragraph; the few times folks asked this question, my automatic response is, better stay on stock firmware. Your follow-up questions only reinforce this recommendation… I'm sorry, but these basic questions are answered over and over again, and certainly you shouldn't venture into changing your device without some grasp on how to use recovery.
[Nook HD, HD+ Android Development] justwondering:
Hi Thank you for reply, I have changed roms on a nook previously, once I know which rom to download and which one is appropriate for cmw or twrp, it's just nice to start off on the right foot, rather than go round in circles with the wrong rom.
[Nook HD, HD+ Android Development] KyJelly69:
system gets formated as ext4 when the ROM is flashed.
[Nook HD, HD+ Android Development] belfastraven:
I just mentioned the recovery because I think people should make sure that they have the latest recovery from experimental if they encrypt. Also, at least with the cm rom, the only way to "decrypt" is to perform a factory reset or to completely wipe data, so if you don't REALLY want to use encryption, you might not want to try it, or at least you might want to have an unencrypted backup of data. before you do.:)

Also, just a suggestion: Perhaps if at the very top of the OP you added a line in a large font in red or something that stands out : "READ THE FIRST THREE POSTS BEFORE SUBMITTING QUESTIONS" or some such verbiage, you could avoid some irritation and feel free not to answer what you feel are inappropriate questions. In some cases, I think people are looking for others opinions (like AOSP vs. CM) or don't understand what they are being told--perhaps ,then, others will jump in to help. FWIW..
[Nook HD, HD+ Android Development] Mac Hosehead:
I have tried recent experimental ASOP and CM+kernel. Both are pretty solid. I am seeing two occasional issues with both.

One is that certain youtube videos will fail to play after playing once and going back. Sometimes will say connection to server is lost. Can get video to play by closing youtube and rebooting.

Another is on a rare occasion at lock screen I can tap on the screen and it will say to swipe for unlock but swiping does nothing. I can swipe on the camera and it will unlock after dismissing camera.

I don't know if anyone else has seen these, could be an obscure problem with the operator.
[Nook HD, HD+ Android Development] Mac Hosehead:
After more trials, this seems to be limited to one video I was using frequently as a test. The lost connection to the server message seems to be an anomaly. My apologies.
[Nook HD, HD+ Android Development] TBueno:
Feb. 08 CM13 ovation build runs CMFM just fine. Colored artifacts around full screen videos in Chrome are still there though.

Flashed the experimental kernel and WiFi stability seems improved. However, a soft reboot or prolonged interval between uses still make it drop. A very minor hassle since tapping the usual SSID on WiFi's drop down menu reconnects it immediately, as someone already pointed out a few posts ago.

After spending more time with CM13, I can say overall responsiveness is actually significantly better than 12.1. Impressive work as usual.
[Nook HD, HD+ Android Development] games906:
How do I get the pixel C layout? It's on amace's aosp marshmallow, right?
[Nook HD, HD+ Android Development] steavis00:
Wow

I have to admit, I'm shocked at how well Marshmallow (08 Feb 16) version works.

No lag and you can switch contexts in an instant.

Now if some of my apps can catch up. THank you.
[Nook HD, HD+ Android Development] Monfro:
I confirm: it gets formatted as ext4 during install.

Data and cache partitions as f2fs for best performances

Experimental aosp dated 03 February
[Nook HD, HD+ Android Development] extrem0:
I agree with amaces. If you're doing this you must be very careful and read other threads before doing anything.

Since you only asked about which recovery and rom to be used, I'd suggest using experimental TWRP 3.0 and CM roms (Cyanogenmod).

This 6.0 is already in a good state and I'm using it as a daily driver.

REMEMBER: Only flash hummingbird files since ovation ones are for Nook HD+.

CM means Cyanogenmod which has some extra features that AOSP doesn't. Aosp is kinda naked Android, used in Nexus devices.

Latest Recovery (TWRP 3.0 experimental) for Nook HD (7")

https://m.box.com/shared_item/https...bygh9vbaw7jjq08xr5evomvaw5ww/view/52472014541

Latest Cyanogenmod Build (MM 16/02/07) for Nook HD (7")

https://m.box.com/shared_item/https...bygh9vbaw7jjq08xr5evomvaw5ww/view/52570206345

I have the HD+, but HD might run a lot better since it has a lower resolution and similar hardware (only a lower clock soc).
[Nook HD, HD+ Android Development] justwondering:
Thank you ,that is perfect ,I just like too know the basics ,grab the correct files ,then my mind will not wonder too much with regards if I have the right tools for the job , hopefully my nook will be with me tomorrow and then I shall have a go and treat it to lots of marshmallows ☺
[Nook HD, HD+ Android Development] herges:
Hi All,

I've now tested these cards in the latest AOSP ROM and there they work fine. I've not tried them in the latest CM ROM yet and as too many of my games are not working on the AOSP build I've gone back to the CM11 backup. I think I wait a bit longer :)

Many thanks for all your hard work though!
[Nook HD, HD+ Android Development] antebr:
Anyone knows why I cant install nano GAPPS on latest AOSP 0204.

Factory reset in twrp, then install aosp and gapps nano.

But after boot, there is no gapps installed.

I am on TWRP 2.8.7.5.

If I install latest CM and nano gapps everything works ok.

Thanks
[Nook HD, HD+ Android Development] DE-Nooker:
I did have same issue wuth nano and pico open gapps on same AOSP build 160204. TWRP 2.8.7.5. installs them but after booting AOSP there was no trace from Gapps.

---------- Post added at 09:12 PM ---------- Previous post was at 09:01 PM ----------

I did flash the experimental kernel (from Feb 9 16:09:03 EST) yesterday and I still have wifi connection drops where only a manual reconnect (or a Nook HD+ reboot) helps. I would also say that this happens more often with the experimental kernel but this might be due to more frequent checks (wake the Nook and see if it is still connected or not) I have been performing over the past 24 hours.
[Nook HD, HD+ Android Development] games906:
Halp (aospFeb 08)! What is miscellaneous?!
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm running the 0204 AOSP ROM with pico gapps with no problem, had it with the 2.8.7.5 twrp, and even installed with the official 3.0 twrp just fine. Got xposed, gravity box, and v4a going too.
[Nook HD, HD+ Android Development] antebr:
For me on experimental twrp 3.0.0 won't install at all (AOSP 0204), error code 7.
[Nook HD, HD+ Android Development] games906:
Same. I had to switch back to 2.8.8.0
[Nook HD, HD+ Android Development] dbrickg:
Installed just fine for me. I'm running the 2/8 cm13 ovation build on my nook hd+
[Nook HD, HD+ Android Development] :
Amazing rom.
[Nook HD, HD+ Android Development] antebr:
CM 0208 build working ok for me to, with twrp 2.8.7.5 or 3.0.0.
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I installed the 29T CM for ovation. The link came from the instructions peteinsequiem put together. I thought it was a more finished release than it apparently is and I must say despite that it runs great and I'm using it as a daily driver. I've run custom ROMs in the past but am not a developer, so I have some kind of noob questions. Everything works great except for just two issues. TWRP manager says it needs root, I've installed SuperSU but it says it can't download binaries. In addition I can't watch purchased videos from google, either through the play movie app or YouTube, it says it failed to fetch license. I downloaded your 29u but haven't installed it yet. Any chance it addresses either issue or is there something I did wrong? Otherwise thanks for the work on this, its more than functional enough for my daily driver and much better than stock.
[Nook HD, HD+ Android Development] DE-Nooker:
Don't install SuperSU from the PlayStore and uninstall it if it's already/still installed. Then download one of the zips from here and install it from TWRP. This (installation in System-Mode) should always work.