yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] PeteInSequim:
About a millisecond after posting the reply that you quoted it struck me that tcpdump on the Nook couldn't be started until the non-traffic period was over. So ADB would be a necessity.

My router is built into the Ubiquiti Networks NanoBridge M5 subscriber unit that brings my internet service. But the same functionality is in the Ubiquiti Networks standalone Edge Routers, of which there are several model variations. They all use the same firmware though so should deliver comparable TCP dumps.

I actually got my tcpdump from my Ubiquiti Networks NanoStation M2 wireless access point, thinking that would be the closest I could get to the Nook. So given this, here is the tcpdump syntax and some examples of what I used:

-lni - line buffered, no DNS resolve, interface follows

-leni - the "e" adds display of ethernet headers, so you'll see mac addresses etc.

wifi0 - The name of the NanoStation's wireless network interface. Find it with the command ifconfig.

58:67:1a:e2:30:10 is the MAC of Hummingbird-2-P.

00:27:22:1f:5a:a2 is the MAC of NanoStationM2.

192.168.1.201 is the previously leased IP of Hummingbird-2-P.

192.168.1.4 is the fixed IP of NanoStationM2.

tcpdump -lni wifi0 ether host 58:67:1a:e2:30:10	show packets TO or FROM 58:67:1a:e2:30:10

tcpdump -lni wifi0 ether src host 58:67:1a:e2:30:10	show packets FROM 58:67:1a:e2:30:10

tcpdump -lni wifi0 ether dst host 58:67:1a:e2:30:10	show packets TO 58:67:1a:e2:30:10

tcpdump -lni wifi0 host 192.168.1.201	show packets TO or FROM 192.168.1.201

tcpdump -lni wifi0 src host 192.168.1.201	show packets FROM 192.168.1.201

tcpdump -lni wifi0 dst host 192.168.1.201	show packets TO 192.168.1.201

I have lots of Nooks around here to try. But they all behave identically regarding the recalcitrant WiFi on boot problem so I'll be very surprised to get different logs. I don't think you mentioned if you've seen this problem; is your Nook immune to it?
[Nook HD, HD+ Android Development] Peter4732:
I tried the latest experimental build for hummingbird(16-9-19) and everything seems to be working: speakers working, wifi working, bluetooth working, everything else is working as far as I know. The only thing I noticed was that when it was turning on showing the android logo it was displaying upsidedown which isn't really a problem.
[Nook HD, HD+ Android Development] ShapeShifter499:
DELETED
[Nook HD, HD+ Android Development] toplist:
I tried first experimental nougat ovation build and had audio issue. While listening to music (Phonograph music player) if I switched to audio functionality on another app (ex. youtube), while resuming playback on Phonograph, the music doesn't play properly.

I tried Supersu version 2.46, 2.78, 2.78 SR1 and all of them resulted in bootloop. So, no rooting and restoring with titanium backup.

I'm using twrp 3.0.1 and even though I backup data, system, and boot, while restoring it only shows one option, data. After clean installing nougat build, I restored data partition fine. I should note that I experienced error while backing up and restoring. I don't recall now what the error message was though.
[Nook HD, HD+ Android Development] ShapeShifter499:
Erm maybe I don't quite understand, old post removed

---------- Post added at 02:11 AM ---------- Previous post was at 01:38 AM ----------

Ok now I have it. [MENTION=4473900]amaces[/MENTION] [MENTION=5672278]belfastraven[/MENTION] This pull request I made should contain the fixes for encryption https://github.com/airend/android_device_bn_common/pull/1 It's a simple edit to the fstab and only effects devices with a ext4 formatted /data partition as opposed to a f2fs formatted one.

---------- Post added at 02:52 AM ---------- Previous post was at 02:11 AM ----------

Update, now that I formatted /data to f2fs encryption works for me with the 8/19 build. I'm able to make use of a alphanumeric password, both TWRP and Cyanogenmod decrypt with this password just fine. Also bonus, adopted storage works with encryption enabled in TWRP and Cyanogenmod! For anyone new reading this, adopted storage in TWRP only works with newer builds, in my case I'm using the TWRP build [MENTION=5672278]belfastraven[/MENTION] posted a few posts back http://xdaforums.com/showpost.php?p=68564966&postcount=1180
[Nook HD, HD+ Android Development] starbright_:
Maybe you can give me a hint, what is going in here.

My Nooks CM11 gots slower and slower. After reinstalling (complete wipe) of CM13 it was much faster. But only 2 month after it was slow again. Almost unusable. Update to latest CM13 (08/19) doesn't help. Wipe Cache/Dalvic doesn't help.

Looking at RAM, which was my first supect for beeing so slow, doesn't show much difference. Around 220...250MB free.

But after factory reset it was snappy again.

I am not 100%, which partition is cleaned in factory reset. Data?

Recovered now a few of the apps with Titanium Backup, it is still responsive. What the hell keeps NOOK busy or slows it down so much. Do I really have to to factory reset every once a while? Is there a method that can help me to find the reason?

Did you make same observation?
[Nook HD, HD+ Android Development] belfastraven:
Good catch. I know amaces has already made the update, so the next-time cm13 is built, encryption should be fixed for everyone. In the meantime, people can use your interim solution. I think I have been running f2fs for cache and data for so long that it didn't occur to me that could be the issue. :).

---------- Post added at 08:53 PM ---------- Previous post was at 08:17 PM ----------

I have not noticed this issue, but I update roms very frequently, so I might not see this. From your own observations, it seems there may be some problem with the data partition. When you factory reset, it does clear data also (you've already tried clearing dalvik and cache), although not your personal files unless you are telling it to do that. If you are not clearing your personal files and a factory reset fixes things, it seems very likely that some app or app data may be causing the problem. Do you have anything that creates a database, for example, or does a lot of logging?
[Nook HD, HD+ Android Development] ShapeShifter499:
I have a new question, is there a reason why I'm not able to install SuperSU as systemless on Cyanogenmod? I've been doing this over a week now on a Moto X Pure running Cyanogenmod 13.0 by flashing a newer nightly, removing /system/bin/su /system/xbin/su and going to flash SuperSU SuHide. to make Android Pay work. I wanted to do the same for my Nook HD to prevent some other apps from throwing a issue over root but every time I try SuperSU just flashes in 'system mode' and not 'systemless mode'. I've even tried to run "echo 'SYSTEMLESS=true' > /data/.supersu" to no effect.
[Nook HD, HD+ Android Development] twiztid_:
Incorrect information, removed.
[Nook HD, HD+ Android Development] belfastraven:
From a response by amaces to a bug report in March:

"Developer Response Mar 9th, 2016

Although we have all the other requirements in place, SuperSU doesn't know how to unpack/repack our boot images for systemless install. "

BY the way, Chainfire has an experimental app called SUhide, but it only works with systemless, so it seems that even with systemless root, apps know that the rom is rooted.
[Nook HD, HD+ Android Development] ShapeShifter499:
SUHIde was what I was talking about.
[Nook HD, HD+ Android Development] starbright_:
Device gets slower until factory reset:

There is nothing creates loggin imho. But good point. I will notice RAM and Flash usage at the moment and check the changes.

I did the factory reset out of TWRP. This is complete. Can you explain howto do a factory reset and keeping personal data. That seems to be contradictionary. And where to do this? As this is what I would try to do next time as a first step.

Is there something like a "top" or "ps" where I have a chance to catch these brakes?

From my limited understanding this can be either a limit of CPU or RAM. Or can it deal with less Flash Memory too?
[Nook HD, HD+ Android Development] flieswithhawks:
You can wipe all cache, and system in two without wiping data and external SD and then re-flash your ROM and your apps and settings will remain.
[Nook HD, HD+ Android Development] starbright_:
Sorry for asking. What do you mean with "wipe all cache, and system in two" ?

Wiping Caches defintily not help. Not sure what whether wiping of system makes a difference before installing system (CM13 and GAPPS) again. But it is worth a try. Thanks
[Nook HD, HD+ Android Development] ShapeShifter499:
I poked around and I see in the kernel config we are using XZ, any reasons why it's not GZip? https://github.com/airend/android_kernel_bn_omap/blob/mm-13/arch/arm/configs/android_omap4_defconfig

SuperSU and Suhude requires a GZip formatted boot.img for auto patching systemless mode from what I find.
[Nook HD, HD+ Android Development] starbright_:
It is still ext4. Are anything else (TWRP, Titanium Backup) works if the ext4 partitions get a new format? Are both files based backups?

I found that system (even with my very limited apps and older gapps nano) is filled up to 97%. Doesn't it make sense to change size (make data smaller and system bigger?). I know that this change is done once in the Moto Defy.

Other question: data and storage/emulated have same size. It looks as this would be identical partitions. But I can wipe data and keep the files in storage/emulated (internal sdcard), right? How does it works?

And what does this mean if I change filesystem? How to this change to f2fs best in practice.

Sorry for asking so many questions, but this seems to be rather a big step.
[Nook HD, HD+ Android Development] justwondering:
Which Gapps Should I be downloading for the CM version , Micro , Nano or mini ?
[Nook HD, HD+ Android Development] justwondering:
Okay , I have the latest CM version install with Nano GAPPS .....but often the tablet will fail to wake if it has been left for say longer than 10 minutes , if you reboot and use the tablet , all is fine , but then once again if left for a while , it will fail to wake , any settings I can change to remedy this problem please.

I did have a older version installed for some time and all was fine , I have since formatted the tablet and performed a full fresh install as detailed above ...Help please :) TYI :)
[Nook HD, HD+ Android Development] amaces:
The kernel zImage (untouched by SuperSU) is XZ-compressed, but the RAM disk is still GZipped. Anyway, the issue is our custom second loader, and having the true Android boot image at an offset (see boot.mk in the common device tree).

System-mode install might never be fixed on N, and system-less is better, but we'd need to tweak the SuperSU scripts, which I've avoided so far.
[Nook HD, HD+ Android Development] flieswithhawks:
Oops, I meant wipe in TWRP.:silly:
[Nook HD, HD+ Android Development] ajislav:
Try this in TWRP

1 backup all (always do a backup)

2 wipe/advanced/system, cache,dalvik,data

3 change filesystem to f2fs for data And cache (this should also format the partitions)

4 restore/advanced data

5 install ROM And gapps

I might not remember all the option names correctly but if you look around long enough in TWRP, you will find it.

Not sure whether to restore Android secure as well or not..
[Nook HD, HD+ Android Development] starbright_:
So just "Data" and "Cache" to f2fs - did I get this right? System keeps at ext4?

I will do that if it gets slow next time. Right now I am happy that it works well. Thank you.
[Nook HD, HD+ Android Development] belfastraven:
Yes, that is correct. Just data and cache to f2fs.
[Nook HD, HD+ Android Development] ShapeShifter499:
I see, well at this moment I don't know of any applications I would want to run on the tablet that block root so I'll just leave it here and use the default Cyanogenmod 13 root binary.
[Nook HD, HD+ Android Development] starbright_:
Another observation. Since quite a while I see at /settings/battery that sum of all listed consumers is not even close to the used battery.

As an example: Battery is 30% so, 70% is used. But all listed consumers together give just around 40%. What is the problem with that?

If I leave Wifi on it seems to consume a lot of power even if it is just unused. I guess it is connected to gapps. They are installed but I have not setup an account til now (as I recovered my apps with just TB). Honestly speaking, I am not sure where in TB are stored the settings for the google account to recover it. There is so many google stuff ....
[Nook HD, HD+ Android Development] dully79:
Thanks for your work [MENTION=4473900]amaces[/MENTION], you've brought my nook back from the dead. :)

Is there any chance of adding oms commits to your AOSP branch to enable theming with substratum?

http://review.projektsubstratum.com/#/q/status:open

Regards.
[Nook HD, HD+ Android Development] belfastraven:
I had started to look into the root setting issue a while ago, but dropped it because of it being easy to "overcome'. I have not noticed the issue you have with the stay awake option, but had often wondered about the USB selection of connection options, the setting of which seems to make no difference. Only the pull down menu from the notification area makes a difference.

It seems that all development setting are not handled in the same way.

For root, the issue is tha what you see in the developer options, with Apps and ADB being selected, is what you will find in the build.prop file

persist.sys.root.access=3 . which is set from device/bn/common.mk file in the build directories.

However, the code that actually checks for access(for which the source is found in /system/extras/su/su.c in the build system) is looking for a file called

"persist.sys.root.access" in the /data/property directory. That file is not present until you make a different choice in developer options. There is a property service that seems to write files for other persistant properties at boot time, but not this one .

I have not been able to figure out why yet.

The stay_awake code seems only directed at keeping the screen on or off. This does work for me without my changing anything.

FWIW
[Nook HD, HD+ Android Development] twiztid_:
Yeah, I may have jumped the gun on that...

I changed the setting, rebooted (I think I cleared dalvik/art and cache) and my battery drain was gone, and the Nook would go into Deep Sleep. But then I tried it again after a clean install (not sure why I wiped), and have not been able to get Deep Sleep back yet, and it is really frustrating me along with the screen not coming back on.
[Nook HD, HD+ Android Development] scabbard1:
I feel like an idiot and I've searched everywhere. I cannot get PICO GAPPS to install with this ROM. Any help is appreciated. It gives me the insufficient storage message. I have wiped everything and started from scratch with no success. Looks like a problem with CM version as AOSP installed fine
[Nook HD, HD+ Android Development] twiztid_:
You need to remove something from the System folder. I personally like to delete /system/media/bootanimation.zip, it's big enough alone to make room for GApps. Plus I prefer the 'default' animation, feels more sleek and refined than some of the flamboyant bootanimations I've seen, stock or otherwise.
[Nook HD, HD+ Android Development] belfastraven:
Check out post 1171

http://xdaforums.com/showpost.php?p=68364817&postcount=1171

for the use of a .gappsconfig file.
[Nook HD, HD+ Android Development] BultoPaco:
My experience is a simpler solution. I have found that, if you load the ROM only and then immediately reboot to recovery, you can then load gapps and SuperSU successfully and get set up to run cleanly. You should at least try this first before taking more extreme measures -- nothing to lose?
[Nook HD, HD+ Android Development] belfastraven:
What hardware are you on? If you are on an HD (hummingbird) which panel do you have (orise or novatek?)
[Nook HD, HD+ Android Development] js290:
Installed twrp-3.0.2-0-ovation_3.4-N.img. But when sideloading aosp_ovation-ota-NRD90U.160929.zip (or just about any other zip), I get the following error:

E3003: Can't install this package (Thu Sep 29 18:32:05 EDT 2016) over newer build (Fri Sep 30 12:38:26 EDT 2016).
Updater process ended with ERROR: 7
[Nook HD, HD+ Android Development] Nevermindthelabel:
What I did on my hummingbird after upgrading twrp is unzip rom, go to the updater-script -- META-INF>com>google>android and open updater-script with notepad ++. Delete entire line 1, save and zip files again. Flash new zip. No more errors about newer build
[Nook HD, HD+ Android Development] tj2003:
Installed twrp-3.0.2-0-ovation_3.4-N.img. Then installed aosp_ovation-ota-NRD90U.160929. I had a lot of trouble installing. Had to do factory wipe then internal storage wipe to get anything to install. I now have everything loaded but I cannot do a backup get lots of errors. Any help would be appreciated. Attached log.
[Nook HD, HD+ Android Development] toplist:
I also had the same issue. Factory reset didn't solve the problem.

I can report that today's build, 161003, installs fine. The build includes Superuser. Root is working fine. I used Titanium Backup to restore my apps. Thank you to amaces for solving root problem :good:. I need root for restoring apps and setting and for advanced reboot.

While I was typing on the stock AOSP browser on the new build, I had frequent black screen flashing/flickering.
[Nook HD, HD+ Android Development] surfdday:
Thanks. This really helps. I use the File Manager within TWRP to delete the file. Personally, I prefer the stock boot animations. :D
[Nook HD, HD+ Android Development] hemeboy:
same error 7 message with E1001 when I try to clean install aosp_ovation-ota-NRD90U.161003; no problem with build from 09-05.
[Nook HD, HD+ Android Development] Uldiniad:
[MENTION=4473900]amaces[/MENTION] will there be cm-14.0 for this device? or only aosp_nougat builds?

btw, what is the difference between the aosp builds and cm (I only have ever used cm so...)
[Nook HD, HD+ Android Development] js290:
AOSP is the vanilla Google android build. CM is cyanogenmod.
[Nook HD, HD+ Android Development] Uldiniad:
ok, then I know why I prefer cm. No bloatware, more configuration, etc. I can wait, or I can make my own port (worst case scenario).
[Nook HD, HD+ Android Development] dully79:
I don't know where you've got the idea of aosp having bloatware. You'll find neither of them are but i find there is less bloat in aosp.

CM has a heavily modified framework for the cmte where as aosp uses native rro(6.0) or OMS(7.0) for theming.

Also one man's useful app is another man's useless app.
[Nook HD, HD+ Android Development] Uldiniad:
Just replying to this, but it is somewhat subjective and unimportant. Not criticizing AOSP, just a preference of mine. My experience of AOSP is very limited (I think it was Android 5.0.1) as I believe I said before. From that little time spent with it I didn't feel like I could configure things as much as with CM13.0 and the size of the ROM was larger on a clean basic flash (because it had more apps included). I usually start disabling all the apps that I don't use in CM when I flash it but for some reason either I couldn't figure how to disable them on AOSP (the button was greyed) or it was not possible. That's all. Really no biggie. Not looking to debate anything.

Summary: I love Android, I prefer CM.
[Nook HD, HD+ Android Development] megawayne:
For anyone having trouble flashing GAPPS, pull Pico from March 10th, works fine.
[Nook HD, HD+ Android Development] PRODIG4L:
[MENTION=4473900]amaces[/MENTION] I was unable to get gapps to load (kept getting error 70) with CM 13 and the AOSP version of android 6 so I went back to your CM 12 and was able to load gapps. I used your TWRP and open gapps ARM 6.0 pico, (plus i tried TK and A-gapps). I appreciate your support of this device and just wanted to let you know my experience. If you have any suggestions give that a go too.
[Nook HD, HD+ Android Development] mikeataol:
my experience with a lot of recent ROMS is that TWRP seems unable to properly handle flashing the ROM and GAPPS in a single session

what I do is usually a full wipe, (system,cache,davlik and data), install the rom

power off, then reboot to recovery

then install the gapps

this is just my experience with what seems to work best
[Nook HD, HD+ Android Development] t12icky0:
i went through alot of gapps. found this one to work but still get play services stopped http://d-h.st/zdE3
[Nook HD, HD+ Android Development] PRODIG4L:
I'll give that a shot, thanks for the input. Also to be clear I was getting the same error when I used clockworkmod recovery as well.
[Nook HD, HD+ Android Development] ajislav:
Posts 1241-3 have some solutions for your problem. Did you search for a solution before asking?
[Nook HD, HD+ Android Development] tablord:
AOSP 7 Nougat: No Wi-Fi

[MENTION=4473900]amaces[/MENTION], [MENTION=4243514]Hashcode[/MENTION], [MENTION=3654172]verygreen[/MENTION]: Thanks for all your efforts and keeping our good ol' Nook HD+ alive!

Unfortunately, Wifi does not work for me at all with the Android 7 Nougat AOSP ROM. :(

I tried the current version aosp_ovation-ota-NRD90U.161003.zip from October 3rd - which at least does not have the ERROR 7 issues during installation! - as well as previous builds from 19th and 29th September. The Wi-fi does not turn on at all regardless of where you try to enable it from. Neither from the quick launch bar nor from the settings. It acts as if it was trying to enable wi-fi but nothing happens, not even after waiting an hour or so.

Is this a common issue? Anyone else having the same issue? Is there a way to solve it?

Thanks in advance :)
[Nook HD, HD+ Android Development] Uldiniad:
I haven't tried AOSP. I know that what I am about to say is not an answer if you are looking to stick to AOSP, but I wanted to suggest for you to try out cm instead. CM13 is currently quite stable but he will have a cm14 branch (based on nougat) if that interests you.
[Nook HD, HD+ Android Development] vimaster:
My Wi-Fi does work on the October 3 build, but it is flaky. Sometimes it will disconnect and will not reconnect again until I turn off the screen and turn it on again.
[Nook HD, HD+ Android Development] tablord:
I would love to use CM14 instead of AOSP! Unfortunately, it is not available yet. Do you have any info on when to expect a first CM14 release? I know that CM13 is working really well (albeit the enoying self-restart issue), but I wanted to deploy and test Android 7 Nougat already :)

Then you are quite lucky under circumstances. Mine never manages to turn Wi-Fi on and even if it pretends to do so it never finds any SSID which I could try to connect to. I wonder if anyone else is facing Wi-Fi issue with the AOSP Nougat builds?
[Nook HD, HD+ Android Development] IndyRoadie:
I am running a build I dont see in the Experimental Folder any more..

aosp_ovation-ota-NRD90M.160905.zip

It says is is Android 7 in my About screen. I am running Pico gapps, and everything is working great.
[Nook HD, HD+ Android Development] tablord:
Hey [MENTION=2801032]IndyRoadie[/MENTION]!

So you are saying that you don't have any Wi-Fi issues with this build?

Could you please upload it somewhere, e.g. androidfilehost.com? That would be great :good:

In fact, could you [MENTION=4473900]amaces[/MENTION], make it available in the experimental folder again please!? Thank you :D
[Nook HD, HD+ Android Development] IndyRoadie:
No WiFi issues at all, it even stays connected with no drops. However, I cannot use AFH because I am not a Dev, from what I understand. And I am not sure if there are Rules against reuploading a Dev's work. Hopefully amaces will do so.