yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
Yesterday I flashed the experimental kernel over the 9/06 build, and after a few games of Hearthstone I can say its HUGELY improved. Not perfect (yet? :D), but without a doubt improved. There's still some freezes during the matches, and at the end of the match/game, but they are significantly shorter. For comparison to previous versions (around 8/19 I think), the game play is much smoother overall, but the spots I get short freezes in now previously I would get lots and longer stuttering.

This is with the zRAM enabled, I have not tried with it disabled yet, because I haven't felt the need to turn it off since everything is running well. I know you said you don't use the tablet for games, so I hope all these improvements and tweaks/fixes also have some uses beyond games and add to overall performance.

I'm still getting dropped between games, and when the screen idles off, but its not a biggie.
[Nook HD, HD+ Android Development] TBueno:
Been running the latest experimental kernel over sep-06 build since yesterday and seeing the best performance on the HD+ so far. App launching, in-app responsiveness and web browsing are pretty snappy. Awesome work!

RAM's "basal metabolic rate" after boot is around 350MB with full/default Gapps and a lot of apps, so I guess it's quite optimized.

Heads-up: right after flashing the new kernel, my unit would get warmer and warmer while in use (unplugged), to the point it would reboot spontaneously. After three reboots it settled though, and it's been perfectly cool both while in use and charging. :good:
[Nook HD, HD+ Android Development] belfastraven:
hummingbird with 9/9 kernal

[Everything smooth--no freezes yet while reading, web surfing, mail, after 10 hrs or so.
[Nook HD, HD+ Android Development] amaces:
The kernels from earlier today should be even better for long term use; these are probably the end of my backporting and experimentation this week, but we need more testing before the full builds.

No idea why network would behave differently since I haven't really changed much there. Do you know the exact build when it started to happen?

That's definitely not good; never had the pleasure of self-reboot because of overeating. The chipset can overheat, but the thermal throttling should kick in and prevent such an extreme case. If it happens again, definitely try to get a log; the very recent changes don't have much to do with overheating, but everything is possible.

Haven't read the whole thing, but I'll mention the simple instructions for external recovery in the OP here, if you device is only soft-bricked. You should even be able to flash current recovery/kernel ZIPs in verygreeen's SD card CWM, rather than mess with the raw images within.
[Nook HD, HD+ Android Development] twiztid_:
I think it was the 8/26 build. I'll look around and see what I have for ROMs and backups and see if I can find when it starts.

New kernel starts off amazing, but about half way through a 10 minute match it slows down considerably, and by the end lots of lock ups. As for my disconnect issue, I think its related to the slowdowns, where the server isn't getting a response from my game client within a certain period of time, so it assumes I'm not there and disconnects my connection.
[Nook HD, HD+ Android Development] mattyyey:
I dont have time to look with adb now, but the sdcard image from your thread booted first time, normally doesnt do that. Quick look, it said it couldnt mount internal sd and /data so... yea, I'll fix it l8r, thanks alot
[Nook HD, HD+ Android Development] TBueno:
Flashed the latest experimental kernel (ovation_lmk+moto-rbtrees) on top of 0906 yesterday. No overheating issues this time, and everything is just as fast. Graphic-wise, the tablet behaves like a radically different (better) device in comparison to when it was running builds from a month ago.

Turned out the sites I usually access from the HD+ (this forum and a local newspaper) are really taxing on system resources. Tried YouTube from Chrome, watched a few videos, and another news site - it felt really snappy and responsive, and hitting home did not trigger a launcher reload. Also tried feedly, browsed through some articles, including one with embedded media (soundcloud), and that did not kill the launcher either. Awesome!

So for my use case improvements are remarkable, and the ROM is visibly maturing. WTG AMaces!
[Nook HD, HD+ Android Development] amaces:
Interesting, when you do dumpsys meminfo, what do the last six lines say? The last kernel is the first that works well with lower swappiness on the 09/06 ROM for me… I will scale back one if the three ideas I implemented in the lowmemorykiller logic, and will send for testing.

Yup, Chrome and Newsstand are my benchmarks as well. Many games are actually lighter than these two, since most of game rendering bypasses the general UI subsystems.
[Nook HD, HD+ Android Development] twiztid_:
Apparently, dumpsys meminfo isn't through ADB... But on the upside, I have ADB working now. :D

Total RAM: 795844 kB (status normal)
Free RAM: 135364 kB (210484 cached pss + -116816 cached kernel + 41696 free)
Used RAM: 541964 kB (393064 used pss + 148900 kernel)
Lost RAM: 118516 kB
ZRAM: 672 kB physical used for 6776 kB in swap (196604 kB total swap)
KSM: 35392 kB saved from shared 4300 kB
156024 kB unshared; 281208 kB volatile
Tuning: 128 (large 402), oom 122880 kB, restore limit 40960 kB (high-end-gfx)

Apparently a large Lost RAM is bad... so I'm not sure what to do now. After a reboot, it's down to 89827 kB, so I'm not sure if that's "normal" or what....
[Nook HD, HD+ Android Development] amaces:
Wait, I had disabled KSM in the past two kernels… Do you have additional persistent/init modifications?
[Nook HD, HD+ Android Development] twiztid_:
Is that /data/local/userinit.sh? If so, my file is renamed so it shouldn't be loaded.

Beyond that, I don't know what that is really. I recall that there's a persistent option somewhere in the settings, but I don't think I've ever used it and certainly not on any Android 5.x.
[Nook HD, HD+ Android Development] krustyzy:
Thanks a lot. That did the trick.

Now I only wonder why performing a factory reset provokes such behaviour. Nevertheless, now is the time to enjoy Lollipop ;)
[Nook HD, HD+ Android Development] shdware:
deleted
[Nook HD, HD+ Android Development] amaces:
Those patches are still separate; my plan was to remove all extra variables, and generally hope that they're not needed anymore. I haven't tested them yet on .101, but they should still apply cleanly, or with minimal changes. Alas, the old issues remain.

Based on the first few paragraphs here, dirty flashing should work even over CM12.0.

Looks like that driver was first included in K3.1, and it's been revamped in the newer kernels. There are some backports for 3.0, but I haven't found one with enough good information. The link you sent is for a newer kernel, which has the Wiimote driver already included. Will keep this in mind, although so many other issues…

Yeah, lots of weird issues, although now that I spent almost a week with this, it makes sense that all the leftover KFire code would cause problems. Overall, all this effort for a fully working .101 may not be worth it, given that buffer underflows still happen. It's been quite a learning experience, but I think I'll focus on just a better .72 (SLUB works after all), and the perennially non-booting 3.4…

Good find, that means a discrepancy between the audio HAL glue and the kernel. This may eventually help fix sound on .101, but now I'm more keen on the Dialer issue, since it probably stems from HAL as well.
[Nook HD, HD+ Android Development] Zippy Dufus:
Good news on Hangouts Dialer, a new update fixed the force-close and it is now working on my Nook Tablet. It is back to the unintelligible sound on the NookHD++. This means that the problem is very likely in the kernel and not the shared B&N code. Thanks to the OP in this thread for diagnosing the problem.

I got scared by the reports of the TWRP boot loop issue and removed your build after about 6 hours. But I see that this may be some unrelated problem with TWRP itself. So if you have any significant changes, I will build another ROM with your original patches re-enabled. I did see a screen flicker in my build without them.

Also, for what it's worth, here are a couple Antutu benchmarks for your kernel: 17,937, 17771. My only statistic for my first Lollipop build is 17,871. Most of my benchmarks for CM11 range between 18,500 and 19,000. Of course, comparing is dubious because Antutu is always making updated to their program.

As always, your work is greatly appreciated!
[Nook HD, HD+ Android Development] amaces:
Yup, just noticed the different behavior after the Hangouts update. I'm gonna call it an improvement ;) At least, now it displays an error message about missing camera, but goes ahead with the call. Still, whichever audio sink it chooses in the HAL is still broken, whether because of wrong gain or configuration values, or some other issue with the switch to DMIC. Apparently, there's an alternative audio path (SND_OMAP_SOC_ABE_DL2), so I'll try that at some point. After that, disabling SND_OMAP4_ABE_USE_ALT_FW will remove the digital MIC, but apparently the standard firmware has other improvements.
[Nook HD, HD+ Android Development] belfastraven:
On nook HD hummingbird with 4/23 build , charging and sound are working fine for me with the exception that in "settings" "sound", the "notification" label appears but the slider isn't there.

I haven't yet determined whether I would get sound notifications anyway. My perception is that the tablet is running more quickly and smoothly. These rom's just keep getting better and better . Thanks, amaces.
[Nook HD, HD+ Android Development] amaces:
That flood of issues (sound, charging, etc) was happening with an experimental kernel, which is now on the back burner. The ROMs in the device folders use the normal trusty kernel (3.0.72), albeit with a few configuration upgrades.
[Nook HD, HD+ Android Development] twiztid_:
With the latest two builds, has anyone noticed WiFi issue after the screen goes off?

Example, I'm watching a video (MX Player) off my local network (ES File Explorer), if I pause and let the screen turn off sometimes I am unable to resume the video, it just sits at a black screen and I have to close them manually. If I go back into ES File Manager, my local network is unavailable for about a minute.

I don't believe this is an issue with either app, since neither were updated since updating CM, and it affects other apps like my wake on lan app. I have not noticed it affect my browser, but it may be I just haven't noticed it. It may only be affecting local connections, or only be caused when it sleeps with an open stream connection.

Well... the problem seems to have gone away. I didn't notice the problem yesterday, and my tablet has gone to sleep while a video was paused a few times today without issue. No settings have been changed, and as far as I know nothing has been updated.
[Nook HD, HD+ Android Development] pmt223:
Thanks so much for the work on this. Keeps getting better and better. I'm using the hummingbird model, so I really appreciate the work you do. If you need any help testing anything or whatever, please let me know.
[Nook HD, HD+ Android Development] techdudepro:
Which Recovery do you recommend using with your 12.1 ROM?

Right now I use CWM, but I see that you have a TWRP available... which one do you recommend for use with 12.1 on hummingbird?
[Nook HD, HD+ Android Development] twiztid_:
I used CWM for a long time on my HD+, but had to make the switch to TWRP for John Lee's Yellow Kernel/ROM. Been using it since and I hate that I can't use TWRP on my phone. It feels better once you give it a chance, and I haven't had any issue. Also, the version provided by Amaces has F2FS support if you ever need it or want to mess around, but apparently it's less of an issue with Android 5.x.
[Nook HD, HD+ Android Development] techdudepro:
Oh and one more thing-- is there a bug reporter for this 12.1 build? because I know two and would like to share them... They are mentioned here:

1: I cannot see the battery percentage now, if the number is in the battery icon. I appears to be white on white now.

2:When the keyboard is up, and I am ready to type, the menu keys (home, menu, back buttons) start flashing randomly, at random times. They start blinking as soon as I type something on the keyboard (onscreen one)

And keep up the good work [MENTION=4473900]amaces[/MENTION]!
[Nook HD, HD+ Android Development] toplist:
I also noticed screen flashing. However, it only happens on landscape mode for me. If I switch to portrait mode, the flashing stops.
[Nook HD, HD+ Android Development] krustyzy:
That used to happen for me, too. Disabling hw overlays seemed to help, though. Same with CM11 before.
[Nook HD, HD+ Android Development] techdudepro:
Wow, thanks. Worked like a charm. Now I can use a blue light filter again, without my while screen flashing! But I hope it gets fixed for other noobs...
[Nook HD, HD+ Android Development] techdudepro:
[MENTION=4473900]amaces[/MENTION]-- I have 1 feature request for a future build. Could you add the Ambiant Display feature that is is Lollipop? Like the double-tap-wake would be an awesome feature...
[Nook HD, HD+ Android Development] amaces:
Another Attempt at Screen Casting, Doze Mode, plus Updates…

While trolling for different ideas for fixing our remaining issues, I stumbled about this unmerged commit, which makes a lot of sense to me, and may be the reason for the Chromecast-ing failure. Could someone test screen casting with the experimental ovation build I uploaded earlier today?

Sure, I activated and attempted a basic configuration of the new Doze mode for our devices (see the ovation build in the experimental folder) but I don't think it works very well. These features require good kernel support, plus we don't have an ambient light or a proximity sensor, and I'm not entirely convinced about the sensitivity of the accelerometer. Either way, battery drain will be much worse since the digitizer has to be kept awake for extended periods during sleep, then waking the whole LCD is pretty expensive compared to OLEDs. Bottomline, emulating these Moto or Nexus 6 features will be pretty expensive and somewhat gimmicky on a 9" inch screen, and without proper kernel hooks, existing app solutions (e.g., AcDisplay, Peek, etc) are probably better.

For the folks who haven't followed the recurring discussions about the nasty flickering bug on the original CM12.0 thread, I've added post #3 ;) Basically, disabling HW overlays is not a proper solution, not encouraged, and it will definitely not help us get included in the official nightlies. It's a major deal breaker on ovation, and everyone is looking for a solution. Honestly, the OP information is kept fairly sparse since people shouldn't use alpha ROMs a daily drivers, yet we all do…

Thanks, [MENTION=5467906]MossyTC[/MENTION]. I think it'd be great if we can have an automatic way of generating changelogs only for the relevant repos, akin to CMx logs (e.g., acclaim's). As you probably noticed, I took out the additional timestamp since it felt awkward, and no one does it, but I will keep thinking about your idea. Of course, this will be solved automatically once our devices get official nightlies ;)
[Nook HD, HD+ Android Development] tj2003:
Installed today's build.

1. Battery display works

2. Sound on device works

3. Ext sd works

4. Cast is same as before. Chromecast sound no picture. If you cast from Google Play Movies both sound and picture.

FireTv stick picture but no sound.

Thank you for all your work and keeping CM for Nook HD plus alive and updating.
[Nook HD, HD+ Android Development] ieatabiscuit:
The uge to tinker with things always brings me back to this thread. I wish I could do more than test it and hope for official nightly support, but I'm still flash and grin phase of my Modding. Too noobish to get into the guts. Still, this is the best ovation/hummingbird thread there is, and I wanted to take the time to say it.
[Nook HD, HD+ Android Development] king200:
I'm ready to go with the latest experimental. I'm a bit confused about, "the new Doze mode".

Is doze enabled/disabled in settings? I don't use a lockscreen and wonder if there is any reason that I would want Doze?
[Nook HD, HD+ Android Development] amaces:
That's pretty odd since the init.rc scripts in the kernel image were used to start KSM. Maybe you need to move the old userinit to a different folder, or make sure anything related to KSM is commented out.
[Nook HD, HD+ Android Development] twiztid_:
I deleted my userinit.sh file, rebooted and the KSM is still showing, it should be blank right? My /init.rc file has no "ksm" in it.

What would you suggest I do to fix this? I'm not opposed to doing a full wipe and starting completely fresh (after a backup), if you think that will solve it.

Thank you for this personal assistance :D I really do appreciate all you do more than words can say.
[Nook HD, HD+ Android Development] amaces:
Check /init.omap4.rc; the ksm/run line should be commented out in all these kernels. Also, there's an alternative kernel (lmk+no-compaction) in experimental, also KSM-free.
[Nook HD, HD+ Android Development] twiztid_:
I used kernel-ovation_lmk+moto-rbtrees.zip, I'll give the other one a shot in a few and let you know.

Edit: Whoops... I may have been using an older kernel. I just noticed my TWRP was looking in my Download folder, not my SD card folder. The things you don't notice at 3am when you're tired but your brain just won't shut off...

Edit2: New kernel, no KSM. Still have a lot of "Lost RAM" and my Free RAM is negative, but I'm running a game in the background.

Edit3: Deer Lord it's glorious! Everything ran so smooth in the game I tested out. Animations actually played fully, and almost completely smooth. Thank you SO much! Time for round 2...
[Nook HD, HD+ Android Development] amaces:
Don't worry about Lost RAM, other weird statistics as long as memory is not critical and it doesn't slow down.

Was this the no-compaction kernel, or the one from yesterday?
[Nook HD, HD+ Android Development] twiztid_:
Yeah it is. But the no-compaction wasn't there when I downloaded yesterday. It lists it as uploaded today.
[Nook HD, HD+ Android Development] amaces:
That's good; you can test the one from yesterday for a bit, then compare with the latest.
[Nook HD, HD+ Android Development] belfastraven:
Latest Experimental hummingbird kernel (built 10/10) has been running well for me all day, using kidle app, chrome_dev, newstand, nytimes, checking settings, etc. No freezes, good battery life.

thanks
[Nook HD, HD+ Android Development] snoozer854:
Are you still having the turning off & staying off issue?

I have been having the same problem as you since CM 11.

I am currently running the 9-6-15 12.1 & it still is pain getting it to turn off.

Holding the Power Button down when it starts back up works, but I wish it would just shut off & stay off.

With CM 11 I used QuickBoot app to turn it off & it stayed off, but it doesn't seem to help with CM 12.1

Was mainly just curious if you found a fix for this issue.

Thank you

Mark
[Nook HD, HD+ Android Development] Ashley2001:
Is there a guide to install a kernel when I install the latest zip when I restart I am stuck on the bootloader screen
[Nook HD, HD+ Android Development] twiztid_:
Make sure you're using the right builds, and not mix-and-matching.

HD is Hummingbird, HD+ is Ovation.
[Nook HD, HD+ Android Development] euqilobaid:
Yes, i still have the issue on the tablet. One of the few ROMs which didn't result with power-off issue on my tablet was Tweaked Xperia.
[Nook HD, HD+ Android Development] bazza1603:
I am having issues as well . Needs switching off a few times for it to actually stay off....
[Nook HD, HD+ Android Development] brenyoka:
Let me just say I am amazed by the smooth collaborative effort I see on this site.

I have an HD+ with an old CM10 stable on it which was installed by my friend over a year ago. I am now planning to install this version from scratch. Is there a noob-friendly source somewhere on doing a fresh install? Thanks in advance!
[Nook HD, HD+ Android Development] mmnspeed:
Install procedure is simple.Install flashify from play store.Use it to flash twrp recovery.Since it is an old version,download the latest one from op and install it from the already installed twrp recovery(one from flashify).Download the latest version of the ROM from op.Clear data and cache in twrp.Install the downloaded ROM from twrp(you might want to backup the old version first in twrp as cwm backups aren't compatible).You now have a working lollipop ROM without Google apps.Optionally you can flash the kernel given in the op.Also gapps for lollipop downloaded from the internet(I googled for it,don't know if there is a link in this thread).You can do all these things after having installed the ROM.Just go into recovery and install,as simple as that.Any other clarifications or things I missed hopefully will be posted by other users.

Sent from my GT-I9082.
[Nook HD, HD+ Android Development] snoozer854:
Other the restart issue 12.1 is working great on my Nook HD.

A battery issue that I have been having for quite awhile is now gone too. No more having battery level go from 100% down to 20% within minutes then going back to where level should be as it is plugged into charger.

Here is a link to the issue I was having before. Back then I really didn't think it was rom related, but boy was I wrong.

http://xdaforums.com/nook-hd/help/battery-level-issues-t2917660
[Nook HD, HD+ Android Development] Zippy Dufus:
[MENTION=4473900]amaces[/MENTION], have the upstream folks reverted the ROM compression as well as other monkeying around?

My 09/12 and 09/13 ROM sizes grew back to almost 228 MB up from 191 MB for my 09/04 build. Also, OpenGapps micro can no longer be installed because space limitations in /system. So I dropped down to OpenGapps pico which installed OK and will have to install back Gmail which is the only app that I apparently use and was not included in pico. Further, my 09/12 build messed up the filesystem so I couldn't reinstall 09/04 without repairing/reformatting it.

09/13 seems to be working fine so this post is just an alert.

== EDIT ==

I just had two awesome Antutu tests on 09/13: 19112, 19435. I rarely get over 18500 on my device and can't remember ever seeing over 19000 with CM12!

Great work!! :good:
[Nook HD, HD+ Android Development] amaces:
I was testing building with DEXPREOPT to speed up first boot, as I had mentioned a few pages back. That unfortunately increases the size of the system image by about 100 MB, and the LZMA-compressed ROM by 35 MB. Anyway, it doesn't seem worthwhile given that most of the pre-optimization step is spent on user apps in /data. Also, I think that using Xposed nullifies DEX pre-optimization since it replaces ART… So given all the downsides (longer compile too), I turned it off for now.

A nano-class package worked too, still leaving 30-40 MB free in /system, but yeah, you can return to the previous package now. I also switched to OpenGApps, and was pleasantly surprised that my Smart Lock issue is fixed.
[Nook HD, HD+ Android Development] TeutonJon78:
You can add me to the +1 column for the not staying powered off issue.
[Nook HD, HD+ Android Development] ieatabiscuit:
I have to ask, really out of curiosity more than anything. Why would you turn it off in the first place? I always just keep mine on, and charge it as needed. I do it that way because when you plug it in, it just causes it to boot up anyway, so I gave up trying to turn it off back when it was still stock. Doing this has never caused me a single issue, am I missing something, or is it preference, or is there even a point either way? I am so curious because so many people are worried about turning it off, where as long as I can get to recovery I'm fine. I feel like I'm the only one that doesn't turn it off.