yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Jon Lee:
I don't know about the last version, but I made sure to test it on this version. It seems to be working, (as does the Wi-Fi Analyzer app). Wi-Fi Display also seems to scan properly now (but that's as far as I can test it). If Wi-Fi display doesn't work, I will need proper logs to carry it any further (but it should???).

http://www.mediafire.com/download/5c47r1xz10di3ia/cm-417.zip

This is the (mostly?) working version.

I had to package it slightly different to make it fly through mediafire.

This will need to be unzipped to give the rom and md5 to be flashed.

YMMV.

I also learned how to share/beam files yesterday using Bluetooth. Slow as Christmas, but it works.
[Nook HD, HD+ Android Development] PMikeP:
++++++++++

Update: I was able to dnld it from my desktop. Don't know if it's a table issue or a Chrome tablet issue, but this download required a captcha. (Whereas with the others, I didn't have to do that. Did mediafire changed it's GUI?)

+++++++++++

I can't dnld it from mediafire. Instead of the typical dnld screen I get a screen asking me to "Authorize Download." Which takes me to a new screen asking same.
[Nook HD, HD+ Android Development] Jon Lee:
I double checked the link. It does seem like mediafire has changed things (they now want flash enabled to do a link/text copy!?). Seems to work with firefox tho.

BTW, I consider whatever put on the net to be public domain, meaning that anyone is welcome to share/host these things. I'm mentally exhausted, and it's the weekend, and this one seems about right, so I'll probably leave it at this for awhile. (IE. give it a break). Plus, although this build is about right, the one that came after is totally broken (for no good reason)...

So I have work to do if I want to do any further builds.

Just to try again.....

http://www.mediafire.com/download/5c47r1xz10di3ia/cm-417.zip
[Nook HD, HD+ Android Development] Jon Lee:
PS. The only OCD issue I've found with it is having to turn bluetooth off to connect wi-fi, before turning bluetooth back on. I think it might be a radio priority issue... dunno, some other day...
[Nook HD, HD+ Android Development] PMikeP:
A quick thanks. It's working fine here.

Update:

- I did a dirty flash.

- Wi-Fi now scans and finds new signals automatically. (Whereas before I had to turn WiFi off and on to find new signals.)

- Wi-Fi now holds Region Code.

- Wi-Fi Analyzer works.

- Wireless Display works and searches. (Unfortunately for me, it doesn't show the Roku.)

- Roku's Player app now works without having to allow "kernel" to have firewall access.

- I tried a few "beam" apps to talk to the Roku. No joy. (From what I gather, they don't use the Direct connection.)

- If I have my WiFi connected to a different router that is not the same router that the Roku uses (I have the Roku stick which is wireless - there might be some competition because the direct connection is the same channel as the Roku Wi-Fi), I occasionally get a message that "WiFi will be disconnected during direct Wi-Fi." Which I would expect.

- I can still connect with the Roku when I have Roku's beta mirroring app enabled. I get the Mirror app's Logo on connection, but I still only get a third of the way into a gas gauge about a video. I suspect this is a Roku problem. (The Nook is not listed on their tested devices. )

- I turned WiFi off, turned BlueTooth on, and was able to enable WiFi with BlueTooth on. But in the past I've seen the problem that Jon reported, where I've had to turn off BlueTooth when connected in order for WiFi to initialize.)

As to the rest of the ROM's performance, haven't had any problems. Very stable.
[Nook HD, HD+ Android Development] DSoundso:
I've got some heavy bug and would like to know if some of you experience it too. If I shutdown my nook overnight (with nearly full charge) it feels warm in the morning and the battery is down to 10% or fully empty.

It was very annoying. I had a paper prepared for university with annotations and all and couldn't access it due to zero battery.
[Nook HD, HD+ Android Development] Jon Lee:
The only advice I can give is to make sure you're not running on the performance governor (not how these things were designed), in fact I would have removed the performance governor altogether had not some other governors relied on it.

If not, some app is placing a wakelock on your device. Might be tricky to find, entire threads are devoted to this issue....

I'll have you know, with this last build, I did have random browser reboots for a few days that went away just as suddenly as they came...

http://code.google.com/p/android/issues/detail?id=40784

This has me completely stumped... why it would appear and then disappear out of the blue.. Right now it works perfectly, so I dunno...
[Nook HD, HD+ Android Development] PMikeP:
When you say "shutdown," do you mean that you turned it off? (As opposed to putting it to sleep.) I rarely power mine down anymore, but when I do, I make sure the backlight on the screen turns off. In the past, with a buggy ROM, the backlight didn't turn off on a tablet of mine, leaving my tablet in an unknown state.

In those cases, the only way I've been able to turn off the tablet is via TWRP's Power Off button.

In your case, it sounds like either the tablet didn't shut down completely, leaving the CPU running at 100%, or perhaps you battery failed in a minor short circuit and self-discharged. You'll know if it's the latter if you battery doesn't hold a charge anymorre.
[Nook HD, HD+ Android Development] PMikeP:
Minor screen corruption

Hey Jon:

I caught one instance of screen corruption on the keyboard. It didn't wreck anything and went away with another tap. But thought it might be telling you something if ever you have to squish a bug. I didn't see a way to insert the screen shot in this post, so it's attached.
[Nook HD, HD+ Android Development] Jon Lee:
I tried 3 or 4 different keyboards and all experienced minor graphical glitches to some extent.

To make matters worse, the ODR/Output Data Rate setting of kxtf9 is a tradeoff between touchscreen stability and graphical glitches. At 800f, touchscreen is very, very stable.. but graphical glitching becomes very obvious. I have it set at 400f which helps touchscreen and where graphical glitching starts to become noticeable.
[Nook HD, HD+ Android Development] Jon Lee:
First (fully) working build I've had in over a week.

ROM: http://www.mediafire.com/download/212wwd6iifw52d7/cm-10.2-20150427-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/9bd1siucb6d1f8d/cm-10.2-20150427-UNOFFICIAL-ovation.zip.md5sum

1). Made some changes to external/chromium http_cache.

http://pastebin.com/CKLk7Yw9

2). Backported linux-3.4 drivers/hid wiimote drivers to kernel. Completely untested, but they're there.

Kernel Source:

http://www.mediafire.com/download/xe048152mwkb2u3/kernel-20150427.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
Chrome was randomly shutting down here, but I assumed it was a memory problem, caused by having 20 tabs open. I'll let you know how this new ROM does.

P.S. AnTuTu now up to 19980. So close to 20K.
[Nook HD, HD+ Android Development] xflier:
Tried 427 build, kept getting also keyboard stopped errors. Thx thou
[Nook HD, HD+ Android Development] PMikeP:
Apparently you have to do a total wipe for the new keyboard to work. No problems here since I did that. The ROM is worth it. This is what it must be like to own an iPad. (No shutdowns.)
[Nook HD, HD+ Android Development] xflier:
yes, I wiped data, system, cache, Dalvik cache, and internal storage. still have the issue, I am trying to install the google keyboard from store to see if this issue will be gone or not.

thanks for your help!
[Nook HD, HD+ Android Development] Jon Lee:
Gapps issue.

http://xdaforums.com/showthread.php?t=2699413&page=21

See post #202 (btw one of his packages has a keyboard)

Also play with it first. Check out the ROM before installing gapps.
[Nook HD, HD+ Android Development] xflier:
Thx, I installed the one w/o keyboard, much better not completely thou. I tried the one with the keyboard, seems the issue is gone, thanks!
[Nook HD, HD+ Android Development] Jon Lee:
ROM: http://www.mediafire.com/download/ukda4ebmwrhz6pb/cm-10.2-20150507-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/ullph4k89kkiqke/cm-10.2-20150507-UNOFFICIAL-ovation.zip.md5sum

This has a bugfix pulled from lollipop in system/extras/libpagemap which affected system memory management, when zram was enabled through system settings, that caused for an occasional "random" FC. (traced from linearalloc in libutils).

http://pastebin.com/eeQVa11A

Also, partial application of Amaces DSS patch which allowed me to go up to 800F on kxtf9 ODR in the kernel.

The two sort of cancel the effects of the other.

Kernel Source: http://www.mediafire.com/download/7en8j55op7u17gk/kernel-20150507.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
I haven't had a crash yet, but will try this build. The only minor problem I've had is that sometimes the keyboard will freeze in Chrome. Turning the screen off & on fixes it.

And I couldn't update Chrome yesterday w/o uninstalling old first. But I would bet that's a Chrome issue.

Update: new ROM seems even faster in use, but benchmarks a tad slower.
[Nook HD, HD+ Android Development] Jon Lee:
I noticed that as well. I think we traded some benchmark performance to graphics throughput which allows for faster transitions. I may (will) end up dropping ktxf9 odr back to 400. This would probably help the benchmark and help reduce graphic artifacts. That said, I'm hoping this is, what I would consider to be, the first "long term stable" release. So far it's looking very good on my end (I had a few more days testing the libpagemap changes than everyone else... and no tombstones yet!.. knock on wood).

If you think about it, a 100/16 MHz OC is nothing... I spent the majority of my attention on memory management, which is where I thought it would do us the most good (I really wanted CMA bad- like piranha has). I was concerned, I guess, that the ZRAM stability issue was in the kernel, so I was relieved to find that it's just a version problem and that 10.2 isn't really fully setup to handle swap (normally).
[Nook HD, HD+ Android Development] PMikeP:
I thought that this version ran a tad faster on AnTuTu's 3D test. (7 fps vs. 5 fps.) But I didn't keep good notes.
[Nook HD, HD+ Android Development] PMikeP:
You got me thinking, so I checked. I had 9 tombstones today. Transparent, since the tablet keeps working. But thought I'd mention them.

Is there anything specific I can tell you abt them that would help you stomp on 'em?

Here"s a couple lines:

pid: 21367, tid: 21367, name: sh >>> sh <<<

signal 13 (SIGPIPE), code -6 (SI_TKILL), fault addr --------
[Nook HD, HD+ Android Development] Jon Lee:
A lot of them are application specific, for which I take no responsibility for...

You would need to delete them and start over to represent the latest build, as they are saved from the previous builds.

The swap bug was a true system bug, meaning any application could experience a forced close (Seemed I was averaging one FC every three days or so... just about when zram would start populating).

Anyway, I'm fairly confident the major bugs have been taken care of. The 800f ktxf9 odr causes some issue, but I'll fix that here soon. (Need some other excuse to put out another release... would like a working kexec setup to facilitate with kernel testing, so that will probably be it...)
[Nook HD, HD+ Android Development] PMikeP:
Yes, I had deleted the previous tombstones. I have no idea what SIGPIPE referred to, but after some googling, I uninstalled a wifi direct app I had installed to try to talk to the Roku. I wasn't using the app, but the tombstones have stopped.
[Nook HD, HD+ Android Development] jdjohn:
Stuck on the animated boot screen after flashing. Using latest TWRP.
[Nook HD, HD+ Android Development] PMikeP:
What ROM did you come from? Does the latest TWRP support f2fs? (I don't know bc I've been using the version of TWRP that Jon recommended for this hybrid ROM.) If you installed GAPPS, you need to let this ROM boot first w/o GAPPS. Else, it will stick at boot animation.
[Nook HD, HD+ Android Development] jdjohn:
Was coming from Xperia Carbon JB. I don't know whether TWRP 2.7.1 handles f2fs or not. I didn't install Gapps per the instructions, so that shouldn't be the problem...did full factory wipe, etc.

EDIT: I see the custom TWRP now in post #95. I'll give that a shot later.
[Nook HD, HD+ Android Development] PMikeP:
Check out #189 too. (There are some later posts too about installing this ROM.) Jon suggests double formatting the various partitions to ensure that they're wiped. I had to wipe /system for this ROM to work. And /system stays ext4.
[Nook HD, HD+ Android Development] jdjohn:
Thanks for the references and tips...finally got it installed. I had the same wi-fi issue as others reported (wouldn't turn on; region code not sticking), but a dirty flash of the ROM fixed it. I also encountered the location services not working for apps. But responsiveness is good, no screen flicker like CM12, no Chrome crashes, so looking good so far! Thanks for the work!
[Nook HD, HD+ Android Development] PMikeP:
Locations might work after you install GAPPS.
[Nook HD, HD+ Android Development] jdjohn:
Actually I already had Gapps installed...of course AFTER letting the ROM settle in per instructions ;) The locations issue must have something to do with wi-fi since these tablets have no GPS or cell radio. The only way to determine location is from wi-fi...probably based on IP address???
[Nook HD, HD+ Android Development] PMikeP:
I use a Tom-Tom GPS w/ BT out and a free app to receive the data. Works better than the built in GPS in my Gal Tab 2.
[Nook HD, HD+ Android Development] PMikeP:
BT not working?

Nevermind. Nut behind the wheel. I had disabled Bluetooth headphone service, thinking that I didn't need it for my GPS dongle.

I just tried BT with the last ROM. It won't turn on.

I've tried different combinations of WiFi & BT. No joy.

Anyone else or just me?
[Nook HD, HD+ Android Development] infra_red_dude:
Location doesn't work for me as well for some reason. Gapps don't seem to matter for this issue. Tried without and with (including various versions).
[Nook HD, HD+ Android Development] PMikeP:
Stupid question, but do you have "Allow Mock Locations" enabled in Developer Options? A requirement for my Tom-Tom to interface.
[Nook HD, HD+ Android Development] Jon Lee:
As promised, here is the ktxf9 400f ODR version.

ROM: http://www.mediafire.com/download/k07q3yzgt7wgum6/cm-10.2-20150516-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/59r43or1ozohk44/cm-10.2-20150516-UNOFFICIAL-ovation.zip.md5sum

If running the previous version, I do believe this one is worth upgrading to, as this one has a very polished "feel" to it.

This is/was the last working version before I broke the kernel (but good), making some DSS changes. So it should be awhile before I make any further updates.

Thanks again to everyone who has made this possible! I'm quite pleased with the way this has turned out.
[Nook HD, HD+ Android Development] PMikeP:
Me too. I've been able to run forever w/ 20 tabs open in Chrome, sometimes watching YT's, w/o problems. B&N should hire you to bring an updated version of the HD+ to market!
[Nook HD, HD+ Android Development] FirePsych:
Did you dirty flash?
[Nook HD, HD+ Android Development] infra_red_dude:
Yep, it's enabled. Still no "location love".

Thanks, Jon. Will try this out. This has been the most amazing ROM on my HD+. Thanks for all the hard work.
[Nook HD, HD+ Android Development] PMikeP:
Yes. Ever since the first clean flash of this series of Jon's Yellow kernel (circa March), I've been able to dirty flash his updates.

I have to flash the modified GAPPS each time after first boot of an update. For some reason, GAPPS goes away after flashing.
[Nook HD, HD+ Android Development] FirePsych:
Thanks.

I'm up and running and had to flash GAPPs too.
[Nook HD, HD+ Android Development] xflier:
I want to say location didn't work for me neither before. It always said location didn't turn on, but it was on. Then I tried to install a different gapps, it worked. Google Maps doesn't work, but apps like flixster and Here maps work fine. Now I am using YourZgappsXS 4.3 version.
[Nook HD, HD+ Android Development] PMikeP:
Force GPU rendering - Y/N?

So, Jon:

From your nuts & bolts ROM perspective, should we be using Force GPU Rendering with this ROM?
[Nook HD, HD+ Android Development] Jon Lee:
No, I don't believe it is necessary for this version of 10.2 as 2D benchmarks are acceptable without it (something about later versions ignore egl.cfg, and it's there now for legacy purposes).
[Nook HD, HD+ Android Development] infra_red_dude:
Jon,

The CM version is stamped with 2015-05-05 in Settings but kernel is stamped with "May 16 2015". Is it just a case of not updating the CM version number or is there more to it?

Thanks!
[Nook HD, HD+ Android Development] Jon Lee:
This last version was really just a minor kernel update, so I didn't feel the need to recompile the whole of the system in its entirety. I still don't have the kernel back to where I had it before. I could kick myself for not making a backup before messing with it more.
[Nook HD, HD+ Android Development] dk1keith:
This is probably a very noob question but....is this the rom and kernel. And do you flash it in recovery like any other rom?

Thanks
[Nook HD, HD+ Android Development] PMikeP:
Yes, ROM & kernel in one. No, you don't flash like any other. It's special. I'm on my tablet tight now, so can't find it easily for you, but start reading posts backward from here to find the special insallation instructions.

---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------

I know the feeling.
[Nook HD, HD+ Android Development] pinguy1982:
[MENTION=5664601]Jon Lee[/MENTION] this is a big ask but any chance you may update the ovation-kernel-cm10.1.3_v23?

I have packaged a few of your 10.2 kernels and they do work with 10.1.3 ROMs. The only issue is with the security tab in settings. The security tab in settings FC's if I use one of your 10.3 kernels in a 10.1.3 ROM..

This is purely a selfish request. My ROM is almost perfect with the 10.2_ovation-kernel-Mar-22-2015. The only issue is with the FC's of the security tab on the settings.

If you do decide to do this It would also be awesome if you included zRAM again. Unsure of your reasons to remove it from the 10.3 kernel, but for me it has been a huge help.

If you want to have a look over my zRAM script I have attached it to this post.
[Nook HD, HD+ Android Development] Jon Lee:
No guarantees, but I'll see what I can do. It may be a week or two...
[Nook HD, HD+ Android Development] Jon Lee:
I have pulled in various omap video/dss fixes/changes from p-android-omap-3.4.

http://pastebin.com/cxCeD5sQ

Let's see... added BGRA32 colorspace. Updated pixel clock (pclk) calculations. Separated PM ops into separate structures. Added FOURCC framebuffer support. Eliminated some mutex locks.

Also, the kexec stuff can be safely ignored as it needs further work....

I have two flavors to go with on this kernel.

10.1

ROM: http://www.mediafire.com/download/rxsikm0nwwltq9s/cm-10.1-20150527-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/m5bjqgk1jh1xc74/cm-10.1-20150527-UNOFFICIAL-ovation.zip.md5sum

10.2

ROM: http://www.mediafire.com/download/6uq83k173apctc7/cm-10.2-20150526-UNOFFICIAL-ovation.zip

MD5: http://www.mediafire.com/download/ookcfsql6jcs0k6/cm-10.2-20150526-UNOFFICIAL-ovation.zip.md5sum

Some notes about 10.1...

The only bug I'm aware of so far is that an initial reboot is required before wi-fi can be brought up.

(That should take care of it, let me know if it doesn't...)

Bluetooth works much better in 10.1, than it does in 10.2

Can be installed with any desired combination of ext4/f2fs filesystems. (unlike 10.2, which requires ext4 system and f2fs data & cache).

And, BTW, I had forgotten how good 10.1 can be. I haven't switched back yet.

Kernel Source: http://www.mediafire.com/download/zyuf2g1v7v760tb/kernel-20150527.tar.gz
[Nook HD, HD+ Android Development] PMikeP:
I presume that it would take a total wipe to drop down tp 10.1?
[Nook HD, HD+ Android Development] Jon Lee:
If you keep data f2fs (unchanged), you should be able to just do a factory reset without having your internal storage wiped (with twrp anyway). If you convert data to another FS, then it wipes internal storage.

That's what I did, flash over old, then factory reset
[Nook HD, HD+ Android Development] PMikeP:
Thx. It's not factory reset first then flash? (Or dorder doesn't make a difference?)

And why do you like 10.1 better? I'm willing to try it, but would have to find a new GAPPS.
[Nook HD, HD+ Android Development] Jon Lee:
Functionally, there's very little difference. 10.1 boots much quicker (albeit with a lopsided boot animation).

Bluetooth on 10.2 has always been a bother for me. Functional, but not nice.

Browser on 10.1 seems more stable (I'm aware of at least one other system bug on 10.2 that I haven't tackled yet... it's rare enough that most would never notice it.). No graphical glitches on 10.1 keyboard.. Historically, 10.1 has always been considered to be more stable than 10.2.

BTW, zram can be enabled from system performance settings in both versions.

Also, I don't mess with gapps, so I'm no help there.
[Nook HD, HD+ Android Development] PMikeP:
Tnx. I'll stay w/ your 10.2 for now. BT works fine w/ my Tom-Tom. I get a keyboard lockup in Chrome sometimes, but all I have to do is either toggle screen on/off or minimize keyboard. Sometimes Chrome forgets that I'm logged into Twitter, but I figure that's 'cause I have too many tabs open.

Sometimes, when I come out of stdby, the apps will be minimized to the multitasker. But your last few iterations of this ROM have not crashed, which is great for use as a navaid in the cockpit. I bumped zRAM back up to 18% after you fixed it & all seems fine.
[Nook HD, HD+ Android Development] pinguy1982:
Thanks [MENTION=5664601]Jon Lee[/MENTION] for doing a 10.1 release. As you have said I do find 10.1 to be more stable, and the Gapps work much better. Always have had issues with 10.2 and the Gapps.

Just one issue. You said you have enabled zRAM. I can't seem to get it working. It does work in ovation-kernel-cm10.1.3_v23 but not in your latest release.

You can use an app called OS Monitor to check. According to the app swap isn't enabled.

See the attachment of it working in v23.
[Nook HD, HD+ Android Development] PMikeP:
I still don't see what I'm missing. 10.2 hasn't crashed or failed on me for a couple months. How can 10.1 be more stable than that?
[Nook HD, HD+ Android Development] Jon Lee:
I had to polish 10.2 some. I just threw 10.1 together (ie someone already polished it).

These two are very, very similar (obviously).

Zram... Just add an insmod line to your zram script to insert the zram module.

The rest of us just do it through the settings menu.

If you use a script based zram init, Mike touched on it earlier, it is better to make two smaller containers, than one large one, and give them different weights. I read the technical arguments on this, and it is the proper way to do it. (I didn't. CM didn't. Anyway it has to do with SMP and cpu/mutex locks.). It takes a special way of loading the zram module to get multiple containers.

It can be checked by issuing a 'cat /proc/meminfo' and listed under swap total and swap free.