yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] TBueno:
Another winner

I second brenyoka's first impressions on ovation-1004: Chrome flickering and artifacts are gone, reboot to whatever you want works just as it should. SuperSU survived "dirty flashing" from 0921 smoothly.

Overall responsiveness and app performance (Chrome, Newsstand, task switcher, Inbox) seem just as good as before. However, I've experienced a major improvement in a few specific apps' performance, such as Spotify, YouTube and Firefox 41 : I'm impressed by how much faster I can start getting things done within those apps after launching them. Maybe it's related to better RAM management?

In sum, a welcome improvement to an already awesome rom. Thanks, AMaces.
[Nook HD, HD+ Android Development] belfastraven:
Everything working well on Hummingbird 10/04, also. Tablet seems much more responsive with faster task switching. It's very noticeable with Chrome_Dev, e.g.

Thnx, [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] twiztid_:
Still having a problem with words getting 'eaten', even after a clean install. I have some more details of how/when it happens and its cause. Example:

When I click here| in a sentence and then hit space (or any key), it will remove the word "here".

Turning off the "Show correction suggestions" setting (Language & input -> Android keyboard (AOSP) -> Text correction) eliminates the problem. I'm not sure if its a keyboard issue or CM issue, I moved the keyboard files to my phone (CM10) and it does not have the issue.

Speed is a bit better on 10/04 over the last Sept build, but I still get an occasional 2 second lockup when opening an app, pulling down menu, and switching tasks. Only thing I have open most of the time is Chromium (most often 1 or 2 tabs, XDA forum and another page) and Settings, but it happens sometimes with nothing in my recents
[Nook HD, HD+ Android Development] amaces:
Booting off SD card is one of the great features of these devices, and I'd love to have at least modern SD recoveries available. It's a matter of learning, maybe by dissecting verygreen's old ZIPs. It doesn't look trivial (different kernel, ROM configuration, in addition to packaging, installation scripts, etc), so I never got into that, but hopefully it'll happen. Now, keep in mind that an SD card-based ROM will have even more bandwidth issues, and is bound to be slower than eMMC, plus B&N stock is, umm… not great? As of now, we still have all these stubborn performance issues on the normal ROM, which is my focus.

More important, Marshmallow/CM13.0 repositories are getting lit up, so you can guess what'll keep me busy in the near future ;)

Chrome is one of the worst offenders in terms of thrashing memory. I don't think it's designed for less than 1 GB of *real* memory (on a 1080p screen), and all the things that we do to fake a more capable device result in those frustrating lockups. I'm constantly trying to reduce them, especially since, overall, I haven't found a better browser than Chrome.

During the past month or two, upstream CM12.1 has made lots of strides towards a balanced system, where installing things, basic UI operations, etc, don't visibly bog down the active app. The details (e.g., cgroups, BFQ, I/O priorities) have been discussed here briefly, but the bottom line is that upstream assumes a more capable baseline device. On the Nooks (particularly, on ovation), just having Chrome in foreground throws a wrench into all these optimizations, and I can't just revert the many core changes in CM12.1.

Do try the kernels currently in experimental; my hope is that by carefully tweaking things, we'll get to a sustainable setup, where using Chrome leaves just enough breathing room for the OS stuff. Many of these tweaks have been dead ends, as you're probably aware, but I still see progress. Bottomline, I'm using my ovation in similar ways, so what bugs you, definitely bugs me as well (albeit, my issues don't seem as critical as others described here).

I'm sure you understand the difference between kernel, ROM, and a keyboard app; as long as touches are registered properly, kernel is definitely fine, and InputFlinger/ROM likely too. It sounds like you're using the built-in AOSP keyboard; I don't know whether this is a new bug, or simply an idiosyncratic feature of the AOSP version as I've always used Google Keyboard. It shouldn't be like this, but the reality is that AOSP core apps (e.g., Keyboard, Browser, etc) have steadily fallen into disrepair, especially compared to the proprietary counterparts. If you're willing to switch to Google's version (or another third-party keyboard), that'll probably fix your issue. Otherwise, we'll have to wait for upstream fixes.

PS, [MENTION=3651088]Zippy Dufus[/MENTION], I tracked down that GCC 4.9 ICE to -floop-parallelize-all, and after reading some more, I don't think our dual-core setup benefits from it. Now that I removed it, you can use your previous 4.9.x EABI (Linaro & UBER tested).
[Nook HD, HD+ Android Development] twiztid_:
You tease you... ;)

I will try them shortly. Could you put a date on them please?

I do greatly appreciate the work you do, ringing every last drop of performance out of this device :D Don't take my comments about performance as complaints, just hoping they help you narrow down any changes that help, or tip the scales too much in one direction or another.

Update: I've been using the experimental kernel for a few hours now, and with my typical usage (Chromium, Team Viewer, ES File Explorer, and MX Player) it subjectively feels faster.

There is still some delay with the task switcher, about half a second for the response to start, but it feels a lot smoother. I get that this isn't going to feel as fast as a CM10 build that has had its optimizations optimized, but I have felt some of your builds that lived up to the phrase "liquid smooth". Hopefully we can get that again at some point, but I'm happy with how it is currently.

I replaced the 10-04 keyboard (/system/apk/LatinIME.apk, both versions have the same /system/lib/libjni_LatinIME.so file, verified by SHA-1) with the one from 9-06 which I know worked, and the problem still exists. I could very well be wrong, but that leads me to think its not a keyboard issue, but how the system is handling the text, since as far as I know selecting and suggestions are not handled by the keyboard, but by the system.

One other thing, about the reboot to recovery issue. Could it be related to root?

When I used the last Sept build, and 10-04, WITHOUT SuperSU I could not reboot into recovery. But after installing it, rebooting to recovery has worked every time.
[Nook HD, HD+ Android Development] neutronjeff:
On flashing 1004 Ovation without new kernel, OpenGapps micro, did apps restore and reboot. I'm getting Unfortunately, Google partner setup ... Error.
[Nook HD, HD+ Android Development] amaces:
I would, but some days there are several builds uploaded, and Box will at least tell you how long ago they were changed.

Even with the public link, when you preview each file anonymously, Box will give you at least a fuzzy modification date (e.g., modified today).

If you're logged into a Box account, I think you can get detailed revision information, with actual modification timestamps.

These are quasi-automatic uploads, first testing successful compilation, then allowing me to verify on ovation.

The images in experimental are in addition to whatever builds in the regular device folders, and will at least boot.

Unless I tag things differently, the experimental builds are more or less previews of what I hope to incorporate in the next batch of full builds. Once that happens, or they prove dead ends, these rapid builds go away. Either way, the only to see what's going on is by looking through GitHub logs, and since I constantly rebase/remove cruft, your best bet is through diffs between commit heads.

Those kernels are objectively better, at least based on my use patterns over the past couple of days. Some things were restructured, others that were on back burner integrated; I may get to describe the changes for the next set of full builds.

Now, even when they run well, current builds will never feel exactly like in the past, mainly because CM is not stationary, and we basically have to keep up with upstream (see their changes to cutils), in addition to improving our own device trees. As I said, a device with enough memory will run wonderfully with their changes.

Sure, core text processing could be at fault, but you said that a simple change in the keyboard settings solved it… Can you confirm that this is indeed the AOSP keyboard, and if so, can you test Google's?

Based on the few empirical reports about this, root does seem to be involved somehow. I expected the init system and sepolicy to be fully in charge of setting up reboot to recovery, but since I always have root enabled, it's possible that CM's advanced reboot menu leverages su somehow.

No problems with the 10/04 build & nano OpenGApps here; maybe the app restore (Titanium?) failed somehow. I rarely do backups, and if I do, it's full /data (only) in TWRP. Last time I had a GApps issues (Play Services crashing, so different), a Dalvik & /cache wipe solved it. Depending on what happens afterward, you may need a clean install.
[Nook HD, HD+ Android Development] twiztid_:
My upgrade process goes like this:

Wipe -> Advanced -> check System/Cache/Dalvik

Install the ROM first

Install updated Kernel if available

Install SuperSU if needed

Install GApps

Reboot

If you're going to be restoring your apps (Data partition) there's no point in wiping your Data, since you're just restoring it. If you insist on wiping/restoring data, or have a reason for it that I'm not aware of, you should install GApps -after- you've restored, so the GApps package files will work as they are intended.
[Nook HD, HD+ Android Development] neutronjeff:
Thanks, I did do a full wipe as usual. I have not added SuperSU yet. The restore I mean is the normal application download/restore after doing the basic device & Google account setup, not in recovery. Sorry for causing confusion.
[Nook HD, HD+ Android Development] amaces:
OK, that's a bit odd then… You're saying that the account setup went OK, but then you ran into those errors when you started using the device? Same after reboot? It's been a long time since I've done a clean install, so it's possible the setup wizard in the current OpenGApps, or its interaction with CM is buggy.
[Nook HD, HD+ Android Development] twiztid_:
I used OpenGApps 8-01 on clean installs of 10-04, and last Sept build (forget date) without issues.

Same issue with the Google keyboard too, same 'solution'.
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=4473900]amaces[/MENTION], I always try to test latest Experimental kernel or rom for hummingbird. Lately (on 10/8/kernel now with 10/4 rom) everything has been running well. Do you want us to let you know each time, or only if something is wrong? P.S. if you need a pre-alpha tester for marshmallow on hummingbird, I'd be glad to help :)
[Nook HD, HD+ Android Development] amaces:
Thanks, you're my main hummingbird tester ;) Definitely let me know when things break; otherwise, I tend to assume they're are more or less like on ovation.

Another odd issue since I use the Google keyboard full-time, and have no such problem, even switching between different languages, dictionaries, etc. Maybe it's one of those times when Google overzealously backed up some settings that no clean install will undo. After taking a snapshot of your /data in TWRP, you could do a little experiment: full wipe, then set as new device (instead of restoring from a device backup), maybe even link to another Google account, if that's an option. You can restore your /data without too much hassle, should that fail.
[Nook HD, HD+ Android Development] neutronjeff:
Correct.
[Nook HD, HD+ Android Development] twisteroid:
Hmm. Flashed CM12.1 on my ovation a while ago, but only noticed today that I can't turn the tablet off any more. As soon as it shuts down it would turn on again by itself. Upgraded to the latest version (20151004), same issue. Is this a known problem?
[Nook HD, HD+ Android Development] veekay:
Anyone else have massive battery drain when the screen is off? I have wifi set to off when sleeping, but it still remains connected and sucks the battery. On CM11 I could go over a month of screen off time and now I can barely last a day.
[Nook HD, HD+ Android Development] king200:
I've noticed the same thing on HD+ but never thought of WiFi. I attributed it to the fact that the battery is old and nearing the end.
[Nook HD, HD+ Android Development] MossyTC:
I'm not getting that drain using the 0906 (6th Sept) build.

There is a useful thread on saving battery usage here - Extreme Battery Life. Particulary useful is the suggestion to use Better Battery Stats to see what services + apps are using your battery.

Also check "Settings | Battery" on your Nook to get an overview of whats using the battery, if you haven't done so already.
[Nook HD, HD+ Android Development] TBueno:
No drain on ovation here. You probably have some power guzzling app installed.

Also, I've had adverse effects on battery life when setting Wi-Fi to sleep while screen is off, try "WiFi always on" instead, it might surprise you. WiFi power management has been very efficient since kit kat.

If it doesn't help, Greenify could be a solution.
[Nook HD, HD+ Android Development] king200:
On other CM 12.1 devices, WiFi appears in Settings-Battery. On this device, WiFi does not appear at all.
[Nook HD, HD+ Android Development] MossyTC:
That suggests that Wifi is not the problem, for you.
[Nook HD, HD+ Android Development] twiztid_:
I believe the battery drain is a wakelock issue. If you view your History details, you will see a mostly solid bar for Awake, when it should closely match Screen on. Using Wakelock Detector, I have not been able to reduce its awake time, or find the cause, even after stopping all the usual suspects, like cLock, Google Play Services, and other Google services, in fact it even happens on a completely fresh install without GApps.
[Nook HD, HD+ Android Development] MossyTC:
I've never used Wakelock Detector so I don't know how it compares to Better Battery Stats, however BBS lists the apps and services that cause wakelocks, so even if Wakelock Detector is supposed to do the same, it would be worth checking out BBS.
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=4473900]amaces[/MENTION], I have noticed that with the 10/8 hummingbird kernel , my device under normal use seems to be running about 4 degrees cooler according to trickster mod: about 28 C vs. 32 C.
[Nook HD, HD+ Android Development] veekay:
Wifi off manually = battery doesn't drain when off. Wifi off when screen off = battery drains massively. I rarely use my tablet (which is how I can go for 4-6 weeks on a charge), but it does seem the settings don't work the same as they did in CM11. I have no switched to an app to manually turn wifi on and off.

I checked in BBS and it shows a wifi connection still going on and connecting even when the screen was off and the kernel itself is the only real process using power.
[Nook HD, HD+ Android Development] amaces:
The mid-week kernels are definitely more efficient in a couple of areas, and lowmemorykiller learned new tricks as well. For the first time in a while, the device remains fairly responsive after a day or two of regular use, with Chrome, Newsstand included. Actually, for the first time ever, when under lots of stress, the device soft rebooted instead of regular hard reset, which is good since the kernel never crashed, just launched a new zygote, and continued to managed memory well. Obviously, I'm still unhappy with the occasional 2-3 second lags, while compaction, other memory shuffling frees up enough to continue.

Aww, you must be new here ;) Lots of discussion about this and reboot to recovery failure on *some* devices. Empirically, it seems that root improves things, and since these are release/user builds, you'll have to install a root manager yourself.

Not massive drain, but during the past week or so, I had this hunch something is off with battery life during sleep. Hopefully, it's not kernel related, but yeah, nothing changed with the Wi-Fi system (e.g., drivers, supplicant, etc) in many months. I just want to see a relatively flat battery graph during deep sleep (usually, 80-90% here).

Same advice, keeping Wi-Fi always on is more battery-friendly at this point, plus a much better user experience; otherwise, after every reconnect, the avalanche of net-related operations and syncs slows everything down.

Both of these apps have similar functionality, at least for basic wakelock analysis (and likely draw from the same raw system data sources). Otherwise, the BBS dev is very active right now, and his app has been the go-to for debugging battery life; thanks for mentioning it.
[Nook HD, HD+ Android Development] Scorchgid:
can't get gapps to work (multiple crashes)

Hi so I'm trying to install this ROM (Ovation) and I appear to have some difficulties. I am able to install the ROM itself and SU (I haven't gotten around to XPosed yet)

When I try to install the Gapps after I have installed it in recovery I boot. I'm greeted with the following crashing (on a loop so another one of these will pop up has soon as I dismiss the last one).

unfortunately ... has stopped

setup wizard

google partner setup

google app

google one time inti

com.google.process.gapps

I've used open_gapps-arm-5.1-nano-20151010.zip

pa_gapps-modular-nano-5.1-20150315-signed.zip (Can't remember where I got it from).

Could I possibly have some help with this
[Nook HD, HD+ Android Development] LivinOne:
Are ther eany builds we can download? I've been using CM11 and my Nook just keeps getting worse. I mostly use it for surfing so there is hardly any apps on it... With cm-11-20150907-NIGHTLY-ovation.zip now Wifi will only get 11Mbit even when I'm 12" from the router!

I need to try 12.1 or this thing goes on slezebay
[Nook HD, HD+ Android Development] brenyoka:
When I do a full wipe, this is the order in which I flash the components in recovery, in one go, i.e. no reboots in between:

1. latest ovation build

2. supersu (v2.46)

3. latest gapps from opengapps

It seems to me you may have used a wrong gapps package? You used opengapps nano (so have I), yet the name of the file does not follow their typical name-setting format. It should be "open_gapps-arm-5.1-nano-[8 didgit number referring to the date].zip". Perhaps the best is to grab the file form their main site, not from github? This way of flashing has always worked well for me.
[Nook HD, HD+ Android Development] amaces:
Blind Testing

I'd like to rank the 10/12 builds against the ones in experimental (10/11). Both sets are built from pretty much the same snapshot; flashing 10/11 on top of 10/12 (or vice versa) will not require waiting for ART re-optimization.

Although I think one set is visibly smoother, it also seems to have twitchier memory management, and possibly stability issues. No details about what's different in each as I want as blind testing as possible. Otherwise, kernel is the same (the uber-optimized one from last week).

If you venture into this testing business, give each build at least a couple of days of regular use, then post back your assessment (subjective, quantitative, etc). To reiterate, no waiting or cleaning is necessary between these builds.
[Nook HD, HD+ Android Development] asksmity:
Flashing 10/12 from 10/4 now. Will i need clean flash or will dirty be ok? I clean flashed 10.04.
[Nook HD, HD+ Android Development] amaces:
No cleaning necessary if already on CM12.1 (actually, even CM12.0 is safe, so really, /data wiping is only required with CM10/11).
[Nook HD, HD+ Android Development] dbrickg:
I finally got around to my Nook HD+ again. Flashed the 10/12 12.1 zip file, the supersu 2.29 beta, and the 10/12 Opengapps package. Everything seems to be working really well so far. Thanks for everybody's work, suggestions, and troubleshooting.
[Nook HD, HD+ Android Development] pastordl:
Neither 10/11 nor 10/12 will get past the blue android. Dirty flashing over last romantic released. Let run over thirty minutes never made it to setting up art. Tried re-downloading three times on both. Double checked and am downloading ovation for my HD+. Had to revert to prior release. Both rooms are a no go for me.
[Nook HD, HD+ Android Development] zenlifexxa:
I'm using the 10/12 (cm-12.1-20151012-UNOFFICIAL-hummingbird) build on my HD.

Everything works fine but I'm having "accelerated" video playback when watching netflix or dramafever.

Hopefully, this issue can be fixed in next build. Thanks so much for OP's hardworking and contribution!
[Nook HD, HD+ Android Development] asakurato:
10/12 is really worse for me than 10/04. Audio is stuttering in games (the only one I have, Plants vs Zombies 2). Also both video and audio is stuttering in MX player using HW and HW+ decoder (used to work fine). Youtube is same, no stuttering, but 60fps doesn't work. I also had accelerated video once, but it was normal after it.

---------- Post added at 09:49 AM ---------- Previous post was at 09:13 AM ----------

Why I can never revert to earlier build without wiping data? I always get force closes, bootloops and whatnot. And I can't do data wipe now, because I haven't saved anything.
[Nook HD, HD+ Android Development] king200:
I have 2 HD+. One is 16GB and the other 32GB that I've cloned. The chip is the same. I am not running 10/12 in 16GB and 10/04 with experimental 10/07 kernel.

Any quick test to run with these?

The main app that I use is Newsstand and it had much lag in 10/04-07. I haven't had time to work with in 10/12.
[Nook HD, HD+ Android Development] belfastraven:
The 10/11 hummingbird ran well for me, although I could see from Process statistics in developer apps that it isn't great for memory management. The 10/12 seems laggier once in an app, and video is stuttering. I have just gone back to 10/11. I have not (at least in the last couple of months) had any problems with my HD rebooting, btw. If it "froze" in the past I would soft reboot it. Perhaps those hard reboots are more of an HD+ issue.

P.S. I think some people may be confused about your saying that no cleaning is necessary between builds and are trying to install one of them on top of an older build without "cleaning"....
[Nook HD, HD+ Android Development] amaces:
Using Xposed? If so, you need at least v75.

Wow, the Netflix stuff is almost funny… Every couple of weeks something breaks there, yet I'm not touching anything directly related, nor do I see obvious changes in CM review. Of course, maintainers can bypass Gerrit to push directly into repositories, so god knows what the problem is this time.

Can you also try the 10/11 build in experimental?

No particular test, just keep an eye on regressions and/or improvements. Again, the comparison should be between 10/12 and 10/11 in experimental; ignore anything prior.

No changes to codecs and whatnot. Did you happen to use one of the kernels from last week (10/07?) with the 10/04 ROM, and if so, did you have the same stuttering?

Don't know… maybe the minor framework changes upstream prevent it? Either way, you should have at least a good /data backup if you decide to venture onto the very latest build… If you were still on 10/12, I would've suggested that you try 10/11 in experimental, but you should probably stick with whatever works for you.

Your observations about memory use and lagginess make sense, but I still don't know why video would stutter on any of them…

To reiterate, /data (full) wipe/clean install shouldn't be necessary with any prior CM12 build (unless you have specific reproducible issues). Dalvik and /cache wiping/regeneration happens whether we like it or not, if there were framework/other core changes between builds (which is almost a weekly given with upstream CM).

I was simply incentivizing people to test by mentioning that switching between 10/11 <-> 10/12 will not trigger the time-consuming Dalvik/cache optimization.