yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] belfastraven:
I know you'd need to use the7.8 something rom for cm12 , but you are probably better off with the cm3+TWRP for the new builds. At some point, you might want to try it. You can see cm rom changes, too, that might affect us by monitoring the changelog for acclaim https://www.cmxlog.com/13/acclaim/. Except for the inclusion of gello, I haven't seen anything lately that is very interesting.

If you do look at amaces' github, be aware that he is constantly rebasing and creating new branches and testing things, so that you will probably not be able to tell what is actually happening in a particular build; If you are not building, yourself, it may not be very useful.

personally (probably becuase I am an older retired person) find it kind of creepy that the world can see all the changes you are making to your code :)
[Nook HD, HD+ Android Development] ipdev:
I had to restore nook os, update nook os, then deregister the device.

Ignore. (Not nook apk issue. - I shouldn't post when tired. [emoji17] )

This was for a WiFi issue I had a awhile ago.
[Nook HD, HD+ Android Development] long2ski:
Thank you ipdev, I ended up going back to stock and reflashing anyway since I have had so many other lingering annoyances. By reflashing twrp, aosp, and the latest nook apk from my phone, I got everything to work!
[Nook HD, HD+ Android Development] rcprcp:
Great rom

I just want to give a quick feedback, but I have two ovation devices, and on the last years I've tried many rooms, none was really convinving to me, as there was always some big thing that didn't made my device good (hangs, keyboard that disapear, etc). Last month I've flashed both devices with the aosp from 160503, and even that sometimes I still have some small problems, this rom is still the best one I've tried.

And just to report, on my device (nook hd+ 32gb) the only problem that I have is that this room consumes much more battery than ever. If a give a full charge to my tablet and just don't use it, the battery will last about two days, before it lasted almost a week without use. And on my wife's device (nook hd+ 16gb) sometimes the device just hangs, and we have to do a hard reboot, but the battery last much more than mine.

I'm waiting for new roms to do some testing. And thanks for this great rom.
[Nook HD, HD+ Android Development] djcsurf:
I am thinking of installing this aosp variant on my HD+ as CM gives me screen unlock/locking issues but reading the 3rd OP is says gapps will not work well with aosp. Is that still the case as i really need play store?
[Nook HD, HD+ Android Development] mikeataol:
I don't think you'll have any problem if you use a newer open gapps http://opengapps.org/

I always use the smallest (pico) version, and have loaded these roms many times now...
[Nook HD, HD+ Android Development] djcsurf:
Currently on a CM11 ROM, would you recommend this aosp. The current ROM I use (unless its hardware related) has screen issues.
[Nook HD, HD+ Android Development] mikeataol:
I prefer the aosp version on ovation and hummingbird because it has native screen casting, cm doesnt.

to install the aosp version i would do a full wipe

convert cache and data to f2fs

you must installSU for root, I have used the one I attached to this post and it works fine http://xdaforums.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269/post66861041#post66861041

I flash rom, gapps and supersu in one session

the quick settings tiles are a little different than what you might be used to in CM

before you disable all animations in developer options enable the ui tuner module for settings to be able to rearrange the quick settings tiles

I add the app Custom Quick Settings to enable the Volume Panel in quick settings https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings&hl=en

I also add chainfire's recently app just because I like having a clear all button, even though I am aware its use is frowned upon https://play.google.com/store/apps/details?id=eu.chainfire.recently&hl=en

known issues for me:

power off doesnt work, it just reboots. if I really need it off I let it reboot and then press and hold the power button on the cyanoboot screen

Newest version of youtube doesnt work for all videos, I dropped back to an 11.1 version as I said in post#951 above

playing you tube videos in the browser, and trying to go full screen doesnt work as expected. The video isnt full screen and theres green static artifacts surrounding it

aside from this its a great rom

---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------

It's way better than a CM11 rom.

however you need to get the latest TWRP and massage your partitions to f2fs for the best results.....

I have found that anytime I do anything to partitions in newer TWRPS I must reboot before installing

(after wiping I reboot to TWRP, after changing partition file systems I reboot to TWRP before flashing)
[Nook HD, HD+ Android Development] ominousnimbus:
I'm seriously impressed with the latest AOSP ROM for ovation. Been using this device sparingly (mainly as a car media player via BT) for a few years now, and it's been painfully laggy with most CM ROMs. In particular, any sort of system animation would stutter beyond belief due to the infamous "buffer underrun" issue, as I recall.

Well, after running some CM12.1 iteration from last summer for almost a year, I decided today was the day to attempt an upgrade. Lo and behold, the AOSP build offered here not only installed smoothly, but my ovation performs like a whole new device. It's still not snappy or anything, but it finally behaves more like you'd expect of a typical 3-4 year old smartphone, rather than the over-the-top, soul-crushing laginess I've known with all previous ROMs. Plus, the main issue that spurred me to bother upgrading this old dinosaur -- constant screen flickering on CM11-12, which eventually would end in the screen going black and requiring a reboot -- appears to be gone, from what I can tell.

I'm not sure what miracle the maintainer worked in here, but it probably just extended my use of the device by another year or two!
[Nook HD, HD+ Android Development] pchc_lx:
seeing a lot of praise for the AOSP versions of these ROMs- can anyone speak on choosing these amaces AOSP vs his CM builds (not vs older/other ROMs), and why?

I see there is a screencasting issue w CM but are there large differences beyond that? I have very limited use for my OVATION- literally only 2 or so apps- so my main focus is on speed / responsiveness / stability etc. Should I move from the CM builds to the AOSP builds?

looking forward to flashing once these two ROMs move out of experimental!
[Nook HD, HD+ Android Development] ipdev:
cm_ovation-ota-MOB30J.160530 seemed stable for the day or three I ran it.

I jumped back to aosp_ovation-ota-MOB30J.160503 to try to recreate a problem.

As far as cm v. aosp, try them both. Only you can decide what you like best. Both roms have positives and negatives.

Most of the roms I run, if not cm, are influenced by cm. (rr, bp, ect.)

I try the aosp ovation builds and find I run them longer than I thought I would. (Mind you part of that is due to xposed and gravitybox.)
[Nook HD, HD+ Android Development] vinceweis:
AFAIK, CM has extra tweaks to play with. I run CM because I like to play around or push the limits of my device. I have not run asop, but my sense is from reading here is that would be best for you for basic functionality and performance. We have a n old device with limited hardware. Keeping it simple is probably best if you only have simple needs for the device.
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm rolling AOSP on my ovation, and CM on my hummingbird. CM does have a lot of built in tweaks and a more polished feel due to those tweaks. AOSP is more bare-bones, and requires you to do more to personalize it, but requires a bit less resources. Both run about the same IMO, because of how the RAM is used in Android the resources are not really wasted on CM, it's more like you just see less of it standing around idle. It really boils down to preference mostly. One major difference though, casting does not work on CM, but does in AOSP. That's the major deal breaker for some people.
[Nook HD, HD+ Android Development] guchito9:
If you really want this tablet to feel snappy, you can try this:

http://xdaforums.com/dell-venue/general/how-to-change-dell-venue-8-7840-t3326869

It's to change the drawing resolution of the display, I'm using 640x960 and 130 dpi. Of course it looks bad, but it feels nice :P
[Nook HD, HD+ Android Development] ipdev:
Thanks.

I've been looking for a way to change my fire 7 screen size. This worked. (Haven't played with my ovation yet.)
[Nook HD, HD+ Android Development] 19IG79:
I installed AOSP several months ago and it started to hang up on me. Have TWRP, cleared cache and then restarted. Nook screen comes up, Cyanoboot screen comes up, then boots to TWRP screen and stops. I didn't even boot it to recovery! Tried a few things and gave up. What do I do? Did I brick it? Want it back :crying:
[Nook HD, HD+ Android Development] ieatabiscuit:
make a recovery disk, flash back to full stock, do factory reset from stock recovery, then reflash custom goodness.
[Nook HD, HD+ Android Development] Merazomo:
Tested with Nook HD+:

cm_ovation-ota-MOB30J.160530.zip

aosp_ovation-ota-MOB30J.160503.zip

cm_ovation-ota-MOB30D.160422.zip

Tested with Nook HD:

cm_hummingbird-ota-MOB30J.160530.zip

aosp_hummingbird-ota-MOB30J.160503.zip

cm_hummingbird-ota-MOB30D.160422.zip

So I've tested most of the builds that everybody is talking about, and all CM builds have ran very stable on both my Nook HD+ and Nook HD; however, I've had some problems with AOSP on both devices. On a few occasions, my wifi signal has tuned off, and only rebooting the Nook seems to get the signal back. Also, the file manager seems to hide my files every now and then, mostly on my Nook HD; not so much on the Nook HD+. HDMI output is absent in all builds; at least in my case. Casting is enabled on the AOSP builds, but latency issues can sometimes be a problem on older devices. CM just feels a little bit smoother than AOSP right now in my case.

Please let us know if there's ever an update for HDMI output, because as far as I've seen, that's the only thing that's keeping me from moving to CM13 right now. Casting is OK, but I can charge my Nook at the same time I'm mirroring a movie with the Barnes & Noble HDMI adapter.
[Nook HD, HD+ Android Development] digixmax:
See http://xdaforums.com/showpost.php?p=55582281&postcount=1459 and http://xdaforums.com/nook-hd/help/help-nook-hd-cm11-m12-cyanogen-boot-loop-t3213327/post64079243 for a potential cause/solution to the "boot-loop to recovery" problem.
[Nook HD, HD+ Android Development] duke7553:
Nook HD Running Unofficial Cyanogenmod 12.1 Not Booting Up After Battery Died...

The battery on my Nook HD running Unofficial CM 12.1 died, so I plugged it in to charge, but after this, it is not booting up. The only indicator I get that the device is still alive is the charging light, which lights up when I press the power button, but then goes out after about 5 seconds. Can anybody solve this problem?
[Nook HD, HD+ Android Development] belfastraven:
Thanks , Minshter, for checking on the time issue. I disabled then re-enabled the system UI tuner and time is back to normal. Thanks for the heads up on Simple Reboot. I notice that with this 11/27 build we are back to being able to boot into recovery from terminal, flashify, etc. , and apps like Simple Reboot--very helpful for the digitally (as in fingers) challenged like me:)
[Nook HD, HD+ Android Development] belfastraven:
EGL errors

Things are running well for me on 11/27. The only tombstones I have gotten (2 so far) all seem to be because of the same EGL error

: 8990, tid: 9082, name: RenderThread >>> com.nytimes.android <<<

signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

Abort message: 'Encountered EGL error 12299 EGL_BAD_NATIVE_WINDOW during rendering

and one from com.android.systemui

THese errors don't cause rebooting or even app hanging, as far as I can determine.

I saw a few from nytimes in the previous build...--don't remember any from systemui.

I imagine you may see the same things, but if not, I can send logcat and tombstones. if it is helpful.
[Nook HD, HD+ Android Development] amaces:
Can people keep an eye on auto-orientation/rotation? It used to stop working after the first suspend or so, but it seems stable with the recent changes.

Yup, fixed here: https://github.com/airend/android_system_core/commit/a772f4580904c78f908aa68f2fbfbdab0a940f77. The actual UI for the advanced reboot menu is not as easy to port, but it'll happen eventually. As of now, the plumbing is ready at least.

I only have few apps installed here beyond GApps, so haven't noticed SystemUI tombstones, although I'm sure they'll happen given how memory constrained we are. I noticed that devices supported in AOSP now have a whole section of HWUI properties set, so I'll look at those again. It's hard to choose the right settings when even the Nexus 7 (2013) is a 1920×1200/2 GB device.
[Nook HD, HD+ Android Development] sjavvaji:
I must be missing something. Where do I actually download the 11/27 build or any build for that matter?

nvm found it. didn't realize it was in experimental
[Nook HD, HD+ Android Development] pavlos46:
Hey, loaded up M, successfully. (Ovation)

Refgarding auto-rotation a strange thing happened, although it did work whenever I switched to landscape any downloads would freeze, could be isolated.

Pavlos
[Nook HD, HD+ Android Development] amaces:
Added CM13 Builds

Now that most of the deal-breaker bugs were solved on AOSP, I'm starting (more or less) regular CM13 builds, which attempt to incorporate all the progress so far. The CM13 manifest/repos should be usable now as well. I didn't have a chance to test these exact CM builds, but I don't expect major surprises beyond additional sluggishness.

Obviously, clean install is needed if switching from AOSP or CM12. Personally, I'm sticking with AOSP till it gets closer to a daily driver state, but all progress will be mirrored in the CM builds.

P.S. You could try editing your /system/build.prop by adding the hwui settings below (after current line 81 in the AOSP builds; CM has them already):

ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.r_buffer_cache_size=4
ro.hwui.path_cache_size=24
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=5
ro.hwui.texture_cache_flushrate=0.5
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024

It probably won't solve your SystemUI tombstones, but it's worth a try.

Interesting, do you know whether only the progress bar froze, or the actual download process as well? Didn't have a chance to run into this bug, but I'll keep an eye on it.
[Nook HD, HD+ Android Development] pavlos46:
Actually only the download and only restarted when I tryied to redownload the same file.
[Nook HD, HD+ Android Development] js290:
Just wiped clean and installed cm_ovation-ota-MDB08M.151129.zip. AOSP Keyboard incessantly crashes. Attaching bugreport and logcat.

I also installed aosp_ovation-ota-MDB08M.151127.zip which did not have any AOSP keyboard problems.

Updated: Looks like the AOSP keyboard crash may be related to open_gapps, not with the cm13 build.
[Nook HD, HD+ Android Development] andtron:
Just tried out the 1129 ovation, and for me the show stopper was my 64g sd card was no longer working, it claimed it was corrupted and need to be reformatted. Restored back to the lollipop and it is well again.
[Nook HD, HD+ Android Development] belfastraven:
Going back to AOSP 11/29

I had been running on the cm13 build for hummingbird with pico 11/27 gapps. After not touching my device for the past 36 hours or so, it had lost internet connectivity, froze in apps, and then started to boot loop when restarted. I will try cm again after next build--

Jusr curious--I noticed that the boot animation was the same as for lollipop on the CM build. Is that cm or just our builds?

To recap: I got constant dex2oat errors on initial compiling, and some rebooting/recompilng in further boots until, after leaving the device along for a day it refused to boot properly at all. On the good side, Amazon worked, location worked, programmatically booting into recovery (including from the power-off menu) worked,graphics and rotation worked...., and you have the ability to clear all of the "recent" screens at once.

thanks again, [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] amaces:
Did it actually say corrupted, or it asked to choose between portable or adopted storage? Of course, if the card has a non-AOSP filesystem (e.g., exFAT, NTFS, etc) it may think it's corrupted, but I'm working on that support as described in the OP.

You mean that it looks like the CM12 boot animation? It looks like this, right? I haven't made any changes there.

Yeah, I don't like the current state of CM13 either… They made extensive changes to ART for example, thus new dex2oat crashes, cache corruption, etc (at least on our devices). Otherwise, Kindle, location, advanced reboot plumbing were fixed for AOSP already, but you do get the other niceties of CM13.
[Nook HD, HD+ Android Development] smileyint:
Hi Amaces,

With regards to the SD card, i remember from one of the previous built that it asked to format for use. It only reads fat32, and not exfat as well as ntfs. Not sure on the current built though, but it may be the same if there is no changes.

Cheers,

smileyint
[Nook HD, HD+ Android Development] belfastraven:
escribed in the OP.

Yes, that's what I meant--Obviously. it's not a big deal--just was curious.

Since there are nightlies now for a few devices, I'm hoping that others have run into art issues and that they will be fixed soon. Since it's easy enough to restore a good build from a nandroid backup, I always interested in trying new builds.

The 11/29 AOSP build still seems pretty solid. I think the build.prop changes helped.
[Nook HD, HD+ Android Development] andtron:
Hi amaces,

Yes, it did say it was corrupted, then did what you said to choose the type, both types called for reformatting. And I panic and removed the card :).
[Nook HD, HD+ Android Development] Mac Hosehead:
Running aosp hummingbird 1206, open gapps 1208. Auto-rotate seems to work, at least I didn't see it stop working. Video streaming from Google Play that worked with 1127 now fails.
[Nook HD, HD+ Android Development] Monfro:
AOSP Ovation build 06/12/2015 is nearly a daily driver.

Rotation works well and no particular bugs found.

The only thing that needs to be improved is memory management.

For sure in a few months this will be the best ROM for this device: Marshmallow has lot of potential, and in short time Amaces made really a great job!!

EDIT

Video are not working, both YouTube and video players
[Nook HD, HD+ Android Development] amaces:
6.0.1 (r3/MMB29M)

There were rumors of 6.0.1 being released early this week, so I was prepared to rebase onto the new AOSP sources. The updated images are still in experimental, although I like this release so far, and we might be close to betas/daily drivers.

Now, I was hoping there would be some time to test the highly experimental (more so than usual) December 6th builds. I went back to work on the DMA-buffered ION in K3.0, and was pleased enough with the progress to include it in those builds. Alas, the communication between OMX/rpmsg/remoteproc/Ducati is somehow broken, and YouTube worked maybe once. For today's builds, we're back on the normal kernel with the older TI ION, so YouTube, other video players should be fine.

Otherwise, I adapted the build system to use the native exFAT driver from here. It's being built as an external module, and loaded during boot; better track their updates and the manifest has been updated accordingly. Anyway, that means large SD cards (likely exFAT) work properly now, and I think FUSE-based drivers are fixed as well, although that's untested. NTFS (write support at least) would require proper mounting of FUSE-based filesystems, but that's not as much of a priority compared to exFAT. If NTFS write support is essential to you, leave gentle reminders on the thread ;)

Following on the above, do let me know if exFAT support is still broken for you.

I'm curious now too; how is the CM13 animation supposed to look like?

I think so too, and we're definitely approaching daily driver builds. Memory management will improve, but it's always the big shortcoming of these devices. Now that Nexus 7 (2012) was left behind, none of the AOSP-supported devices have less than 2 GB of RAM, and I get the feeling that MM stopped caring about 1 GB devices :(

Should be working again, as described above.
[Nook HD, HD+ Android Development] belfastraven:
check here...

http://xdaforums.com/android/themes/bootanimation-android-marshmallow-t3180984

For me on hummingbird, on 12/6 rom, as noted, video wasn't working--but it was very smooth otherwise.

On 12/8 audio is stuttering.... rom is not as smooth.

Thanks agtain so much for "advancing our devices. I'm sure I'll we'll have a beutifully functioning system on our HD's long before I see one on my Verizon Samsung Galaxy 6 Edge+ ;)
[Nook HD, HD+ Android Development] amaces:
That's artwork that I've only seen on Nexus devices, neither AOSP nor CM13, albeit the best looking imo. I may attempt to customize ours at some point.

Yeah, that's why I pored dozens and dozens of hours for the K3.0 with DMA-buffered ION, which is just one, albeit major feature or K3.4. The one major bug is complete breakage of OMX-based video playback (YouTube, and basically every other app). MX Player HW-accelerated playback does work, probably because it uses it's own codecs. Oh well, I keep hammering at it since K3.4 still boot loops.

Still, these latest builds should be pretty close in usability, and a definite improvement over the last November ones.