yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] pavlos46:
Ok also tryied latest built 1208 with opengapps pico 1210, full wipe no SU.

Few things I noticed.

A) At first install when tried to flash gapps although it appeared to have worked when booted play store wasn't there. So next time flashed it twice and it worked, does this make any sence ??

B) After that everything worked great no fc's or anything, only problem is embeded video in chrome wouldn't work, statering and sound completly distorted. Youtube app nevertheless works great.

C) Also the kindle app fced.

Hope this helps.

Pavlos
[Nook HD, HD+ Android Development] starbright_:
It sometimes take some time to appear. Maybe you just was too impatient ;)
[Nook HD, HD+ Android Development] amaces:
Bug Reports Seem to Be Working Now

So, if you have a pet issue, that's the place to report it.

That's how I feel about the current state too, so I'm calling them beta-ish now. Memory management will take a while to bring to even Lollipop levels, so no point holding our breath for that ;) It's just the reality of Marshmallow using more memory, then having to switch to jemalloc, while hardware remained the same…

All my testing is on ovation, so no reason for your issues unless some stale setting remains somewhere. Again, you have to at least wipe data whenever switching from CM to AOSP or vice versa, even if both are Marshmallow. The next batch of CM13 builds will probably happen in a couple of days, if you stick with that.

Well, that's a problem… Even if the linker found them where you copied them, this may indicate the blobs aren't copied to the system image, and if they are, then the build system is somehow broken. I'll look into this again, but I don't see an obvious reason for it not working. I'm assuming you haven't changed anything about the Android EABI toolchain in arm-linux-androideabi-4.9 (the kernel EABI in arm-eabi-4.9 should't affect this).

This other issue is probably my bad; I had to make a small change to MediaProvider for non-FAT SD cards, and forgot to fork that repository as well. Anyway, I did that, plus updated the manifest, so you'll have to repo sync --force-sync packages/providers/MediaProvider (no need to re-sync everything; --force-sync is required because of forking). Otherwise, your JDK should be OK; Android requires Java 7.

It doesn't really make sense since even the pico package should include Play Store. This first time installing GApps was a clean install, right? If so, did the Setup Wizard appear?

Haven't checked video in Chrome; does Browser behave similarly? Also, what about video in MX Player?

I thought that was fixed; [MENTION=5672278]belfastraven[/MENTION] is the point person on this ;)
[Nook HD, HD+ Android Development] belfastraven:
I had similar weird things happening when switching to Marshmallow. (Disappearing gapps, eg.) For me what helped was FORMATTING data. (just make sure you have copied everything you need from the internal sdcard before doing that!). I think that certain apps which used the internal sdcard (amazon being one) don't clean up after themselves properly. I found that wiping system , cache, and formatting data, and then flashing the rom, gapps, (and supersu if you want root), with no wipes or reboots between, then rebooting solved those problems for me.

Amazon has indeed been working for me on the 11/27 and 12/08 AOSP builds and the 11/29 CM build. I think it's always helpful to log onto Amazon and make sure that you clear out unused devices--unfortunately, everytime you clear data and logon again, the kindle app seems to determine that you rae loggin in from a different device...

I too have stuttering with audio on video --it happens in chrome_dev, browser, nytimes app, and youtube, for me, on the 12/08 rom. (this is hummingbird) I haven't tried mx player yet (need to find a video to try...)
[Nook HD, HD+ Android Development] pavlos46:
Hey Amaces yew wiped everything before flashing,

On case A) yes no setup wizard came up, on B it actually did.

On C) yes browser behaved the exact same way, tried Firefox and was working better, no sound problems but playback would stop after like 5 minutes. For me YouTube app worked just fine.

Now for formatting I have a problem, on TWRT if I choose data format in wipe menu it crashes as it tries to format in f2fs, something probably wrong with my data partition.

Pavlos
[Nook HD, HD+ Android Development] Monfro:
I am testing a couple of workarounds used on Galaxy S (512MB ram) Lollipop and Marshmallow builds.

These 2 build.prop lines will not improve memory management, but will steal some mb of ram to the beautiful interface, so we have them available for apps.

https://source.android.com/devices/tech/config/low-ram.html

ro.config.low_ram=true

(it makes interface look uglier, but give a little ram boost)

dalvik.vm.jit.codecachesize=0

(it breaks 16bit transparency...at this moment I don't know if it is effective as first line)
[Nook HD, HD+ Android Development] amaces:
Right, you had that unusual problem where partitions became broken… Before that's fully fixed, weird issues like this will keep happening. To reiterate what I said before, one fix is using verygreen's external recovery to dd the raw TWRP image onto eMMC.

You're late to the low_ram party, mon ami ;) We have this commit in the common device tree; I adapted it from otter (old KFire) and Hashcode committed it. Yet, very soon after, we discover that it creates all sorts of problems (e.g., weird blocky rendering and reloading in apps, particularly in Chrome, etc), so it's been fully reverted in my builds for a while. Over time, I tested only parts of those build.prop modifications, and all created undesirable effects. If you discover that Chrome, YouTube, etc work perfectly on Marshmallow with those flags, we'll give it another try. As of now, I expect them to be even more detrimental since AOSP pretty much stopped caring about low RAM devices.
[Nook HD, HD+ Android Development] pavlos46:
OK gotta a Verygreens CWM SD card ready how do I dd the raw image of twrp? Thanks.

Trying googling the process and it appears quite complex.

Thanks

PS. Using the stock recovery I did the 8 times failed boot system restore, shouldn't that fix my partitions ?
[Nook HD, HD+ Android Development] amaces:
I thought I mentioned that instructions are in the OP of the CM12 thread. You just need to extract recovery.img from ZIP, and get it on the recovery SD card (or push it there). Actually, you should first try flashing the TWRP ZIP in that CWM recovery since it might work, and does pretty much the same thing, albeit with much less hassle. You could try flashing a CM11 nightly as well, to make sure system, other core partitions are totally working. Afterwards, you can clean/format, and flash everything needed in TWRP.

I wouldn't rely on anything stock at this point (unless, of course, you're returning to that).
[Nook HD, HD+ Android Development] pavlos46:
Hi,

I have actually tried all this to no success.

Flashing TWRP from CWM or CM11, whatever I do when I run TWRP from emmc it does creat those errors.

I simply don't get it, is there a version of TWRP I can run directly from my very-green sdcard ? Also for some reason CM11 runs a lot better than CM12.1.

I thing I am gonna wipe everything flash CM11, and then CM12 on top.

Pavlos
[Nook HD, HD+ Android Development] ShapeShifter499:
Seems to work, I was able to flash the latest 08-19-2016 Cyanogenmod build that was stored on the adopted storage SD card. The one thing I noticed though, it did not seem to detect the charger, no plus sign next to the battery percentage in the TWRP status bar. It appeared to be charging though as the status light was golden-yellow.

I also have a separate issue that seems unrelated to TWRP. I'm unable to encrypt my tablet, choosing the feature under "settings->security->encrypt" it shows the encrypting droid logo but ends up looping back to the Cyanogenmod blue bot logo then back to the lock screen without any indication it has been encrypted, this was on the 08-19-2016 build.
[Nook HD, HD+ Android Development] mmnspeed:
Has anyone been able to root the android N experimental build on ovation?I wasn't able to do it myself.
[Nook HD, HD+ Android Development] belfastraven:
I will check the charging issue.

I haven't tried encryption since 12.1, I believe. I may be able to free up a "test" nook, in a couple of week, in which case, I'll give it a try.

Is anyone else here on the forum using encryption with a marshmallow rom? If so, which rom are you using.

---------- Post added at 07:54 PM ---------- Previous post was at 07:44 PM ----------

Not me-this is a known problem, right now. I've tried with 2.76 and 2.77, doing a "system" install. SuperSU will indeed install, but then the nook (hummingbird for me) will hang while booting.
[Nook HD, HD+ Android Development] ShapeShifter499:
I hope someone can figure out and fix encryption on the Nook HD/HD+. From what I see when searching this thread for "encryption", it's been a long standing issue. I might not be trying to keep top secret Snowden levels of information on my tablet but it's nice to know if I ever lost it or had it stolen, my information wouldn't just be out in the open read for whoever gets a hold of my tablet.
[Nook HD, HD+ Android Development] mmnspeed:
Tried Helium backup , but couldn't restore the apps.Going back to MM till there is at least a way to restore aps.
[Nook HD, HD+ Android Development] third_degreee:
On the experimental Nougat, anyone else getting choppy video and audio after a few minutes of smooth video/audio?
[Nook HD, HD+ Android Development] mmnspeed:
Didn't test that,but I did try youtube videos in the default browser.On maximising the video would get stuck.
[Nook HD, HD+ Android Development] starbright_:
I am on the previous CM13 build (May like that). I am not aware of installing more apps lately, but I found that response becomes worse and worse. A clean Cache/Dalvik could'nt improve this. I am mainly reading pdf or browse with firefox.

Is this a known effect (of becoming slower)? What can I do - just reinstall? Try the current CM build? But as I have read (because of its size) it is also not easy to go.

In former time I read about trimming. Can this be a cause of it?
[Nook HD, HD+ Android Development] flieswithhawks:
SD Maid. That's the app you want mate.:cool:
[Nook HD, HD+ Android Development] PeteInSequim:
CM Marshmallow releases 160519 through 160819 fail to enable WiFi on boot.

In case anyone is interested, I have confirmed that the following releases always fail to enable WiFi on boot:

cm_hummingbird-ota-MOB30J.160519, cm_hummingbird-ota-MOB30J.160530, cm_hummingbird-ota-MOB30Z.160819

ovation-ota-MOB30J.160519, cm_ovation-ota-MOB30J.160530, cm_ovation-ota-MOB30Z.160819

Testing was done across four Ovations and five Hummingbirds at my disposal and the results were unanimous.

This said, some conditions will mitigate and conceal the failure. Here are two that I found, but there could be more.

1. Tablet enters sleep. A few seconds later WiFi becomes enabled and will be available when wake occurs.

2. Google Location Service is turned on. This works for both normal boot and safe mode boot.

At least one of these conditions is pretty likely for most users, which is probably why I've seen no reports about this phenomenon. I discovered it right away because my Nooks are used as process monitors around the house to present greenhouse conditions. They are set to boot to an unlocked home screen, they never sleep, and are mounted on walls so no need for Google Location Service. I was motivated to track down the recalcitrant WiFi nuisance, and fixed it by turning ON the location service.

If you would like to witness this in action, go to Settings > Location and turn off Google Location service. Then reboot the tablet and watch for the WiFi icon when the home screen opens. It should be dark. In less than a minute if you booted to a locked home screen, or in about a minute if you booted to an unlocked screen, the tablet will begin to enter sleep. Let it do so, then wake it after a half-minute or longer. The WiFi icon should show active and will remain so until the next startup.

Now turn Google Location Service ON and reboot. The WiFi icon should show active shortly after the home screen appears; actually right after the time widget appears.

Please post a reply if your experience differs.

A quick test revealed that this problem did not exist on the CM-12.1 releases, but I didn't test many of them. Nor did I test any of the CM-13 releases earlier than 160519.

The attached pdf file presents details of my confirmation with excerpts from time-synchronized tcpdump and logcat logs, along with a few operator-observed event times and comments. The tablet under test was a 16 gB Nook HD with cm_hummingbird-ota-MOB30Z.160819 ROM. Screen lock was set to none so it boots to an unlocked home screen. Results are the same if screen lock is set to swipe except transition to sleep occurs sooner after the locked screen appears.
[Nook HD, HD+ Android Development] starbright_:
Not sure if this is connected to the described issue.

In my CM13 ovation from May it doesn't automatically connect to my WiFi network. It is recognised but I have connect manually (which is sometimes a bit nasty).

But I didn't make test with boot. To save energy I only sometimes enable WiFi to browse and download a new pdf.

(After connecting manually it complains to have no network - but it has - , which just means here, that some services are blocked by Firewall to keep some more privacy).
[Nook HD, HD+ Android Development] brenyoka:
I am on cm_ovation-ota-MOB30Z.160819 and do not have this problem. WIFI stays on (i.e connects automatically) after reboot. I have location setting as OFF (that is the default) and screen lock security set as "Swipe". However, I do get the wifi disconnect issue when I change the lock screen to "None". It seems to me that for some reason, the wifi connects automatically after reboot only if there is some screen 'security' enabled, like swipe. A few months ago I had wifi not connecting after reboot issue, but not with the latest builds.

Currently, I noticed only 2 issues on CM Ovation:

- power down gets random reboot (very old issue) - not as bad as used to: 4-5 times out of 10 I do get a successful shut down whereas previously it was maybe around 2 or 3.

- connecting to computer via USB always gets to set to "Charging", regardless of device setting. You manually have to change connection to "file transfer" or "media transfer", or something similar. But even if you set that, after reboot, it goes back to "charging" mode again.

- (also): maybe the comcast issue is still there too, but I never use that so cannot comment on it.

On a different note, I recently started using Dolphin browser instead of Chrome and was pleasantly surprised how much better and faster it was. Worth a try!
[Nook HD, HD+ Android Development] rpadula:
[MENTION=4473900]amaces[/MENTION]

what happens that sometimes you build aosp and not CM for hummingbird?

issues?
[Nook HD, HD+ Android Development] PeteInSequim:
Thanks for the feedback. When your screen lock is set as "Swipe", the time from home screen rendering to sleep is pretty short. Do you notice an active WiFi icon during this short period? For a while I didn't watch closely for the end of the boot animation, then looked a little later at a dark screen. By this time WiFi has already been activated during the sleep session.

But if I actually watch the home screen being rendered, WiFi is not active during this short period before the screen goes dark. If I unlock before it sleeps WiFi will remain inactive. But if ever allowed to sleep, WiFi will be active when it wakes.

Could you please try capturing the logs, and perhaps a tcp dump? It would be really interesting to see how they differ from the ones I captured for the same release. There is a nifty free utility on the Play Store named Syslog that will capture the logs at any time you launch it, then zip them up and upload to a cloud service or even E-mail them for you.

If you are not familiar with capturing logs I could coach you through it. You would have to run tcp dump on your router or wireless access point, and to do so would have to SSH into it from you desktop computer. But the command syntax is pretty simple, then all you need to do is copy and paste the results.

There are some tcpdump binaries for Android that could run on your Nook. I've never tried one, but might be a good alternative if you don't have access into your router or wireless access point. I might try one out later today.
[Nook HD, HD+ Android Development] Famineuk:
Could the reboot/power off issue be connected to the wifi driver? When the Nook is not connected to wifi mine shuts down correctly everytime.
[Nook HD, HD+ Android Development] flieswithhawks:
I don't use WiFi on mine at all and still am affected from this bug, so for me this is not the case.
[Nook HD, HD+ Android Development] toplist:
Which supersu version can root experimental ovation nougat build? I tried flashing 2.78 and 2.78 SR1 and it gets stuck on android logo screen?
[Nook HD, HD+ Android Development] flieswithhawks:
Try 2.56 I believe that's the one that worked for me on an older build when a newer SuperSU wouldn't.
[Nook HD, HD+ Android Development] mikeataol:
my understanding is that there is NO superSU that will work on these nougat builds at the moment.
[Nook HD, HD+ Android Development] lentm:
It's really great to have Marshmallow on my Nook HD+.

Appreciate your work!!!
[Nook HD, HD+ Android Development] mmnspeed:
Tried the latest android 7 build for ovation.Realized there is an issue with audio on the build.It must have been on the previous build as well,but I didn't get time to check it that time.Going back to MM as I have still not been able to restore my backed up apps on this ROM.

Video issue in browser seemes to be rectified, at least in portrait mode(Didn't check peoperly as my primary reason to flash the build was to check if I could restore the apps by any means).

If anyone is able to restore backed up apps or root the build please do share.
[Nook HD, HD+ Android Development] farhanjigar16:
Experimental Nrd90u ovation giving error on twrp recovery 3.0.2.0 that zip file is corrupt.
[Nook HD, HD+ Android Development] ShapeShifter499:
Any updates on this?
[Nook HD, HD+ Android Development] belfastraven:
Since I was running an Android 7 build on my test nook hd, just for "fun" , I tried encrypting. It worked just fine, although the sequence of events was a bit different from what I remember from February. I switched to unlocking with a pin, then chose "encrypt" from the security setting tab. Thel ittle android showed for a second, then the nook rebooted and quickly rebooted once again. It stayed on the bootanimation for a while, and then when it came up showed the android and its encryption progress. When it finished, it asked to be unlocked, then brought up boot animation and came up...

This is using the same kernel, I believe, that is running in the cm-13 builds. I am building cm-13 ( and TWRP) and will test encryption tomorrow, assuming the build succeeds.
[Nook HD, HD+ Android Development] kingsBlend:
Thank you very much for this. I just got everything up and running with one hiccup on error 70 with gapps flash but the config txt fixed that.

I am hoping you do not mind a noob question here..

Once I have cm13 installed with gapps, can I remove and set aside the boot SD and use a different SD for merging storage while still being able to boot into cm?

Edit: only asked because last time I tried this it wouldn't boot back into cm. Wasn't even showing the n when powering up. Turned out that was the low charge issue.

Now I cannot get it to charge in cm and whenever I power off it just restarts.

Also strange, when I do hard power off, it turns on whenever I plug the cable back in. I'm trying to charge while off. If I power off with cable In, no lights show until I unplug then back in and it just boots. Using the stock charger and cable.

Edit edit: flashed 12.1 and charge is working as intended. Will just keep that on for now. Again, thank you all for your hard work on making this possible.
[Nook HD, HD+ Android Development] belfastraven:
I just tried encrypting cm-13. It works for me. The activity on the nook looks a bit different that it did in February.

I have used a pin for security, in case that is making a difference. I did this before installing gaps, if that makes a difference, and was able to install gapps afterwards--TWRP will ask for your password when coming up in order to unencrypt data. I did not try this with adopted storage.

Everything seems to be running fine; I notice that the boot animation is now much s l o w e r :)
[Nook HD, HD+ Android Development] ShapeShifter499:
Is this with one of [MENTION=4473900]amaces[/MENTION]'s builds?
[Nook HD, HD+ Android Development] belfastraven:
no--it's with a build I just made from his sources. I don't see anything that would differ from the 8/19 build though.

This is what I used(it's up on Android File Host): you can try it if the 8/19 build doesn't work for you.

https://www.androidfilehost.com/?fid=312968873555001608

Once again, let me re-iterate. I changed the screen lock to use a pin before I started the encryption, and I am NOT using adopted storage.
[Nook HD, HD+ Android Development] ShapeShifter499:
I've been dirty flashing everything. Maybe the 8/19 build needs a clean flash, I'll give it a try in a few hours.
[Nook HD, HD+ Android Development] belfastraven:
Tcpdump is already installed on our roms, I believe. I know I can use it (through the terminal) on the cm roms, and,probably best for this purpose, you can use it through adb. This write-up

https://wladimir-tm4pda.github.io/porting/tcpdump.html

is a few years old but has a good explanation of using tcpdump through adb.

I think the issue for us is to make sure that is it started as soon as the device connects through adb so as to capture packets when the system initially tries to connect. Otherwise going through the router might be the only option. What are your preferred flags/settings for tcpdump?.

I know that my logcat and dmesg don't show the same activity as yours. It would be really useful, I think to have several more data points. I wonder whether it might also be useful to know what the routers/access points are, and what version of software is running on them. E.g. I am running asuswrt-merlin 380.62 beta on my ap (asus5300) and repeater(aususac66u) now.

Perhaps some other network savvy nook users would like to weigh in here?