[ROM][NOOK HD+] Unofficial CM10.2.1 Stable w/ TabletUI + ArchiDroid Optimizations

CM10.2.1 Stable* for Nook HD+ (Ovation)

Credit to
-Verygreen and CM team for Ovation's CM10.2
-JustArchi for build optimizations
-Caldair for TabletUI patch

In this edition:
--- TabletUI capable. Caldair's patch stopped working after nightly Dec 5, 2013. I reverted minor commits to mainly translations and circle battery to allow the patch to succeed:

--- ArchiDroid Optimizations using GCC 4.7
http://xdaforums.com/showthread.php?t=2754997
The build using GCC 4.8 toolchain would not boot, but all other optimizations remain.

--- 30 media volume steps
--- 0.25x animation speed options under developer settings
--- Tiny reduction to cm10.2 speaker gain to reduce distortion at highest volumes.
--- STABILITY. Not my doing. In my experience, cm10.2 rarely reboots or crashes.
--- Flash videos works well enough

*Technically a June 14 nightly post-stable. However, there have been very few commits since the 10.2.1 stable was released months before.
**Touch fuzz 3x5 and Trim support are already integrated into the CM10.2 kernel. No need to flash an old separate kernel.
Installation notes:
-Compatible with New and old CWM recovery (no need to downgrade)
1)Format /system AND factory reset (data, cache), then flash ROM zip
2)Flash GAPPs for android 4.3. These work: http://xdaforums.com/showthread.php?t=2240652 (Use 4.3)
-DO NOT restore system data from CM11
3)First complete a full boot and setup of the rom before installing tabletUI patch


Download ROM: http://d-h.st/jpd

Download TabletUI Patch: http://d-h.st/5Ar
*DO NOT install the tabletUI patch without first completing a full boot and setup of the rom.*
TIPS
For a permanent menu button, I like to set my nook hardware key to open/close menu.
Xposed modules can do this or you can edit the gpio user key file very easily.
Go to the folder user - > key layouts - > gpio-keys.kl
Edit the file with system rw.
Change the word "HOME" to "MENU". Reboot.

Default trebuchet launcher slow? Try Nova or Apex from store. They work a lot better in my experience.
UPDATE 6/21:
Fixed ExFat support.
Added ROW I/O, Intelliactive CPU governor.
Get flash player below!

Enjoy!
Chrome Pop-up blocker perfect for visiting Dev-Host

leapinlar said:

You are going to be sorry you did that if someone with an HD gets a hold of this and tries to flash it. It will brick his device.

A better solution is to use the update-binary from a kitkat zip and the assert works.

Sent from my BN NookHD+ using XDA Premium HD app

Click to expand...

Click to collapse

I see what you're saying, but it's a bit of an exaggeration to say someone will brick. They'll need to boot into recovery and flash a new Rom.
I deleted the line because not everyone has the new kk recovery, and I want it to be compatible with both.

jpisini said:

Overall pretty good so far. Very smooth. Still testing.

Sent from my BN NookHD+ using XDA Free mobile app

Screen can be a bit twitchy, anyone know if there is a fuzz kernel for 10.2?

Sent from my BN NookHD+ using XDA Free mobile app

Click to expand...

Click to collapse

Dr. Marbles touch (3x5 I remember?) fuzz commit is already integrated. If it's laggy for you, maybe try to run a manual trim with lagfix and reboot. Also, the stock launcher is a bit slow, I'd get Nova or similar.

leapinlar said:

If you did what I said it will be compatible with both new and old recoveries. That way you will not be responsible for causing grief for noob HD users.

The issue is not that the assert line exists, it is because the KK recovery using the older update-binary interpreter from older zips causes the assert statement to fail. If you put a new update-binary from a kk ROM in your ROM then the kk recovery will interpret the assert command correctly and it passes. The beauty is that older recoveries also interpret the assert command correctly using the new kk update-binary.

Sent from my BN NookHD+ using XDA Premium HD app

Click to expand...

Click to collapse

I didn't know the new assert line was backwards compatible. I'll upload a new one. Would using the newer update-binary be enough or do I need to alter the update-script as well?

Ok done. Thanks for clearing that up.
For those who didn't understand what leapinlar was talking about, don't worry. The ROM is exactly the same. No need to reflash.

Also, since there's some confusion around, I should mention that 3x5 touchfuzz and trim support have been in all cm10.2 nightlies/stables since november 23 and jan 8, respectfully. There's no need to download an old separate kernel from the one of the threads.
https://github.com/CyanogenMod/android_kernel_bn_omap/commits/cm-10.2

Edit: Fixed below

andr0idfreak said:

It works fine on official 10.2 Nightlies and the stable 10.2.1. Just a heads up.

Click to expand...

Click to collapse

You know what, you're right. It's the kernel optimizations. I see a commit patch for it too. When I get the chance I'll recompile those files.

andr0idfreak said:

Took a break from cm11 due to the aggressive memory management affecting multitasking, and installed this. Pretty solid, smooth and speedy. Great work!

Just found out that my 32gb Samsung MicroSD card formatted with exfat file system doesn't seem to be mounting. It shows up fine in TWRP though.

Click to expand...

Click to collapse

Try this
http://d-h.st/jpd

Haven't had chance to test.
Also added Row I/O scheduler and intelliactive governor options