Whats the fastest Nook HD+ rom to date?

spanielgita

Member
Nov 13, 2004
24
0
0
I have CM11 installed on my nook hd+ at the moment and its decent.
I feel I would like to install the quickest and most efficient rom and kernel.

Does anyone know what rom is quickest/ most responsive.
 

spanielgita

Member
Nov 13, 2004
24
0
0
I have CM11 installed on my nook hd+ at the moment and its decent.
I feel I would like to install the quickest and most efficient rom and kernel.

Does anyone know what rom is quickest/ most responsive.
Ok I'm going to answer my own question.

I have tried the cm 11 rom and it gave me funny flashing screens, not particularly fast.
Cm 10.1 seems to be better stability and speed wise. I am upgrading to cm 10.2 now.
 

asakurato

Senior Member
Sep 30, 2012
599
111
73
Tbilisi
The screen flashing is caused by wallpaper, as users has guessed. Are you using Nova launcher by the chance? As for the question, I use succulent's CM11 for some months already, best rom here. I also run Trim one a week.

Sent from my Nook HD+ using xda app-developers app
 

Trekker56

Senior Member
Dec 21, 2010
303
61
0
The screen flashing is caused by wallpaper, as users has guessed. Are you using Nova launcher by the chance? As for the question, I use succulent's CM11 for some months already, best rom here. I also run Trim one a week.

Sent from my Nook HD+ using xda app-developers app
I am currently running CM11 snapshot version. Previously I was running 10.2 stable. To be honest, I don't notice any significant difference in performance.

My tablet is new and I have not yet had the need to run trim. Can someone guide me how do I run it if I want to? I couldn't seem to find this info in the trim thread.

___________________
Sent from my BN NookHD+ using Tapatalk Pro.
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
0
I am currently running CM11 snapshot version. Previously I was running 10.2 stable. To be honest, I don't notice any significant difference in performance.

My tablet is new and I have not yet had the need to run trim. Can someone guide me how do I run it if I want to? I couldn't seem to find this info in the trim thread.

Sent from my BN NookHD+ using Tapatalk Pro.
I think it is automatic with CM11. You don't have to do anything yourself.

Sent from my BN NookHD+ using XDA Premium HD app
 
Last edited:

jpisini

Senior Member
Nov 26, 2011
1,330
254
0
Weymouth
I am currently running CM11 snapshot version. Previously I was running 10.2 stable. To be honest, I don't notice any significant difference in performance.

My tablet is new and I have not yet had the need to run trim. Can someone guide me how do I run it if I want to? I couldn't seem to find this info in the trim thread.

___________________
Sent from my BN NookHD+ using Tapatalk Pro.
Trim is only automatic if your tablet is plugged in and idle. If you have apps that run in the background it will prevent trim from working. It can be run from the terminal if needed you will need to double check but I think it is Sudo fstrim -v /

Sent from my PC36100 using xda app-developers app
 

sirbender42

Member
Sep 20, 2011
37
1
0
Succulent's CM11 is the best ROM out there, imo.
(And yes, screen flashing is because of a bug in the wallpaper settings. It can be avoided by setting your wallpaper using the "Full Tool" instead of the "Portrait Tool".)
http://goo.im/devs/succulent/ovation/cyanogenmod/internal/cm_ovation_11.0_07MAR2014_HD.zip
I am curious to find out more about Succulent's CM11. His changes etc.

Is there a link to a forum post where this ROM is posted? This is better then just a download link in case he posts newer ROMs.

Cheers,
sb
 

JanSpatschek

Senior Member
Dec 1, 2012
315
54
0
Waidhofen
www.rlbrt.de
I am curious to find out more about Succulent's CM11. His changes etc.

Is there a link to a forum post where this ROM is posted? This is better then just a download link in case he posts newer ROMs.

Cheers,
sb
Yes, here you go: http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/

I would recommend the 3/7 build with the 8x8 fuzz kernel.
His latest build has the CM Theme engine bug (which sometimes FC's systemui etc.)
 

sirbender42

Member
Sep 20, 2011
37
1
0

sirbender42

Member
Sep 20, 2011
37
1
0
Yes, here you go: http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/

I would recommend the 3/7 build with the 8x8 fuzz kernel.
His latest build has the CM Theme engine bug (which sometimes FC's systemui etc.)
Bummer. I tried to read the install description for http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/ including the 8x8 fuzz kernel several times. I already flashed CM11 M6 using a tutorial so I thought I will figure it out. But the description just confuses me.

Could somebody please write a short step-by-step tutorial including links to files needed?
 

HiddenG

Senior Member
Nov 5, 2011
160
46
0
Manchester
To be honest, I'm still using CM 10.1.3 (Android 4.2.2) on the Nook HD+. I'm not too bothered about being on the latest Android version, as long as my current build is stable; which I find CM 10.1.3 is; a stable version of CM 10.2 has been released, and although the TRIM bug is non-existent now, I'm still not risking anything. CM 10.1.3 has not caused any problems whatsoever on my Nook HD+.

The Nook HD (the 7" model) is not affected by the TRIM bug, so I've updated that to CM 10.2; and that does offer a more responsive OS, most likely due to TRIM. I don't think I'll be updating these two tablets any time soon, especially as CyanogenMod are no longer releasing stable builds.
 

swaaye

Senior Member
Mar 16, 2011
450
74
0
10.2.1 has wifi scanning quirks and I find that the web browser crashes often. So I'm on 10.1.3 as well. Maybe CM11 will be solid one day.

It blows my mind how much work it takes to make Google's Android drops work right.

By the way you can TRIM with 10.1.3 as long as you don't have a bugged EMMC chip. There is a app in the store called eMMC Brickbug Check that will tell you if you do. CM10.2.1 and newer have a kernel patch to workaround this bug but 10.1.3 does not.
 
Last edited: