Hi, I'm only a couple days into owning the Nook HD+, really happy with it but sort of working on trying to get my performance a bit better. It's just a little sluggish. I'm currently on the latest official CM Nightlies (cm-11-20140617-NIGHTLY-ovation.zip)
It's about 80% usable but just slow enough that I'm considering flashing a new ROM. So far, I've turned on ART, set processor to ONDEMAND and I/O Scheduler to NOOP, as well as turning off animations and anything I can to get better response. Honestly, it's almost fine.. I'm just a little obsessive with tweaking. And it is pretty obviously slower than my Galaxy S4.
First question is, are most people using a slow CM11 or did I screw up? I had a few hiccups on my CM11 install at first, is it possible I did something then or now to cause the slow performance? Even the CM boot animation is slowww. I could factory reset, wipe dalvik cache etc and reflash my same CM11 Nightly to see if a fresh start is better.
Secondly:
Some people recommend 'Succulent' builds
Some people recommend 10.1.3 Stable
There are also Unofficial 10.2.1 Builds and even Carbon ROM
I would start flashing away myself, but I already spent some time setting up my apps & accounts & blah blah on my current ROM and I'd like to only do it all over again if I really know it's gonna help. Do we think CM11 is gonna get better quickly with each new Nightly and Milestone?
Can any seasoned Nook Warrior help guide me down the path of enlightenment? My performance is not great but it's usable. I'd love to have KitKat on this device but if it really just won't fly I'm OK with 4.3 or 4.2 if it means I can have the tablet of my dreams. Help me XDA, you're my only hope.
=====================
edit: Since I got no responses here (what the deal, XDA?), I am starting to just go through the ROMs I linked myself to see how they perform. Just did a full wipe & restore to flash the 'Succulent' 28APR2014 Build. There is an immediate difference in that the CM boot animation is correct now, and not laggy and ****ed. This gave me a lot of hope, however after setting it up & messing around a bit, it's not quite as drastic a change as the animation. A bit faster, a bit better, not perfect. Gonna give it a day or two of use then probably try 10.2.
I'd be surprised if you saw significant performance differences between ROMs. They are all based on pretty much the same code after all. Although the Antutu benchmark results for my HD were about 10% better with CM 10.x.x than with the B&N software, I could detect no real world difference.
Sent from my Nexus 7 using XDA Free mobile app
lmacmil said:
I'd be surprised if you saw significant performance differences between ROMs. They are all based on pretty much the same code after all. Although the Antutu benchmark results for my HD were about 10% better with CM 10.x.x than with the B&N software, I could detect no real world difference.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
hey thank you for the reply! so far I'm pretty much settled with the 'Succulent' ROM. I'm surprised there wouldn't be a big jump in performance going back to 10.2.x or 10.1.x- wouldn't those be much less demanding on the hardware? that's what I had assumed anyway.
either way, I will probably stick with this ROM for now.
pchc_lx said:
hey thank you for the reply! so far I'm pretty much settled with the 'Succulent' ROM. I'm surprised there wouldn't be a big jump in performance going back to 10.2.x or 10.1.x- wouldn't those be much less demanding on the hardware? that's what I had assumed anyway.
either way, I will probably stick with this ROM for now.
Click to expand...
Click to collapse
Actually Google did a ton of work to make KitKat run in less ram so it should be bit smoother than earlier versions.
jpisini said:
Actually Google did a ton of work to make KitKat run in less ram so it should be bit smoother than earlier versions.
Click to expand...
Click to collapse
Wow, great to know! I will definitely try to stay on CM11 now. the Succulent build is pretty great. I'd say I'm happy.
I am pretty happy with his build as well it makes good use of the hardware. The Nook will never be as smooth as an iPad but for the price it is a great tablet.
Sent from my SPH-L900 using XDA Free mobile app
jpisini said:
I am pretty happy with his build as well it makes good use of the hardware. The Nook will never be as smooth as an iPad but for the price it is a great tablet.
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, pretty much this. Although mine actually is equal to or a bit better than the GF's 1st gen ipad. Shame is she can't go back to an earlier iOS or install a custom ROM. so a physically perfect device is bordeline unusable because of apple policy. such a shame.
80% usable?
I don't know how one quantifies usability, but I had no complaints using CM 10.2.1. It's even faster using CM 11 6/15 and on. I'd say mine is 100% usable.
(You are on emmc, right?)
I use two apps for usability "benchmarking." The first is Garmin Pilot. There's a menu that pops up for map overlays that takes time to display. The closer to real time, the more usable the ROM. There's about a half second delay.
The other "app" I've started using to gauge usability is APPS in Settings. It used to be on CM 10.2.1 that it took a second or two to populate the Running applications. Now, in CM 11, the Running apps populate almost immediately after swiping. Can't get much faster than that.
FWIW, AnTuTu benchmarks at about 13660. (Hotplug, deadline, 512Kb cache using SD-Booster. Dalvik.)
I wonder if you need to run trim manually? I noticed my browser slowing down last month and used Lagfree. Browser sped back up.
Or perhaps do a /system wipe and reinstall? I've had leftovers in /system before.
PMikeP said:
FWIW, AnTuTu benchmarks at about 13660. (Hotplug, deadline, 512Kb cache using SD-Booster. Dalvik.)
I wonder if you need to run trim manually? I noticed my browser slowing down last month and used Lagfree. Browser sped back up.
Click to expand...
Click to collapse
I have 3 Antutu data points for my HD. Stock: 12697, 10.1.3: 13234, 10.2.1: 13713. I know Antutu isn't 100% repeatable so it may be that the 10.1 and the 10.2 numbers aren't really different but they are both definitely faster than stock firmware. I saw similar improvements on my wife's HD+.
I thought trim was built-in from 4.3 on?
lmacmil said:
I have 3 Antutu data points for my HD. Stock: 12697, 10.1.3: 13234, 10.2.1: 13713. I know Antutu isn't 100% repeatable so it may be that the 10.1 and the 10.2 numbers aren't really different but they are both definitely faster than stock firmware. I saw similar improvements on my wife's HD+.
I thought trim was built-in from 4.3 on?
Click to expand...
Click to collapse
Seems like we're in the same ballpark benchmarkwise.
Yes, I've read that trim was built into the ROM. But I don't know when it triggers (daily, weekly, monthly) while charging. All I know is that, last week, while still on 10.2.1, my browser got really slow. So I used lagfix and the browser sped back up.
PMikeP said:
Yes, I've read that trim was built into the ROM. But I don't know when it triggers (daily, weekly, monthly) while charging. All I know is that, last week, while still on 10.2.1, my browser got really slow. So I used lagfix and the browser sped back up.
Click to expand...
Click to collapse
I used lagfix when I was on 10.1.3 but never really noticed any difference.
Sent from my Nexus 7 using XDA Free mobile app
I have been running the official cm11 m4 build on art for about 3 months now and am very satisfied with the performance. In all this time, I have only had a couple of random reboots.
I have not tried succulent's build, so can't compare, but am happy with my hd+.
___________________
Sent from my BN NookHD+ using Tapatalk Pro.
Related
Hi,
I'm having my Nexus One for about two weeks now and I already started a thread about the choppy scrolling between homescreens but now I want to know if there are other people that find their Nexus One slow and if they were able to make it faster in any way.
When I bought this phone I thought android would 'fly' on it cause I already had a HTC Magic and that went reasonably fast. But everything I'm using on my Nexus One feels choppy and not fluent as I expected/want it to be. For example when you start the browser or any other program you get this zoom animation which is nice but it doesn't go fluent, it goes choppy like you would play a videogame with 5 FPS.
And as I already mentioned the same counts for the launcher, it's just not fluent and doesn't feel fast at all.
I've tested different rom's, froyo, etc. but nothing seems to make it right so now I'm wondering if there are people that have the same issue's? Is it normal that the Nexus One isn't super fast to use or is there something wrong with my phone and should I return it?
i think something is wrong. especially with froyo the phone is ultra-fast.
Try Linpack and some other benchmarks and post the results.
Or try osmonitor for example and see what the cpu speed does, perhaps it is stuck @ 245 mhz for some reason lol
Ok, my score in Linpack is 6844 (MFLOPS). Don't know if that's good or bad. In BencmarkPi my Nexus One calculates Pi in 2842 miliseconds. And in Neocore I get 26.4 FPS which seems pretty normal to me.
I don't think my problems are hardware related, it more feels like it's the software.
Ow and I ran OSmonitor now and there's something strange. It says Memory Total: 217.440K Free: 67.500K
Is this a known bug or should it say 512MB?
renegadEEE said:
Ok, my score in Linpack is 6844 (MFLOPS). Don't know if that's good or bad. In BencmarkPi my Nexus One calculates Pi in 2842 miliseconds. And in Neocore I get 26.4 FPS which seems pretty normal to me.
I don't think my problems are hardware related, it more feels like it's the software.
Ow and I ran OSmonitor now and there's something strange. It says Memory Total: 217.440K Free: 67.500K
Is this a known bug or should it say 512MB?
Click to expand...
Click to collapse
your using eclair without a highmem kernel, thats why it only shows that much RAM. What roms have you tried? Try cyanogens or even stock froyo and see how the speed improves. I think you may be feeling its slow because of the extra animations that werent present during 1.6 which is what the MT3G is on
flybyme said:
your using eclair without a highmem kernel, thats why it only shows that much RAM. What roms have you tried? Try cyanogens or even stock froyo and see how the speed improves. I think you may be feeling its slow because of the extra animations that werent present during 1.6 which is what the MT3G is on
Click to expand...
Click to collapse
But the kernel thing doesn't affect the speed? I believe stock Froyo is one of the best I've tried so far. I tried cyanogen too, 5.0.7 I believe, but the launcher was extremely slow on that one.
Or am I flashing my roms the wrong way so things don't run smooth? I just download the .zip files, put them on my sd card, boot into recovery, whipe and flash. Normally it should work that way I believe.
And on my HTC Magic I was using a rom with Sense UI that worked very smooth. Maybe I should try the Desire ports but I like the stock Nexus One UI better.
Also I can't understand why there are developers OC'en the Nexus One? If it's really that fast already why would you risk that you're phone dies quicker for that extra performance?
And I don't hate animations, I even like them, but not if they are choppy.
renegadEEE said:
But the kernel thing doesn't affect the speed? I believe stock Froyo is one of the best I've tried so far. I tried cyanogen too, 5.0.7 I believe, but the launcher was extremely slow on that one.
Or am I flashing my roms the wrong way so things don't run smooth? I just download the .zip files, put them on my sd card, boot into recovery, whipe and flash. Normally it should work that way I believe.
And on my HTC Magic I was using a rom with Sense UI that worked very smooth. Maybe I should try the Desire ports but I like the stock Nexus One UI better.
Also I can't understand why there are developers OC'en the Nexus One? If it's really that fast already why would you risk that you're phone dies quicker for that extra performance?
And I don't hate animations, I even like them, but not if they are choppy.
Click to expand...
Click to collapse
the kernel is actually the primary factor when it comes to speed. how the kernel manages actions on the phone is the deciding factor on what makes it run fast. you can have a very fast phone hardwarewise, but if the kernel is designed poorly, the phone will run slow as well. Using a kernel that does not have highmem enabled means your probably running an older kernel that does not have updates for speed. the latest froyo kernel has highmem and JIT enabled for faster application use as well as over smoother feel.
i love the animations as well
im coming from the G1 and i havent had any of the of the problems you seem to be having. you are flashing the roms correctly (unless there are additional things such as google apps you need, idk whats the procedure on that for the nexus) Im running fully stock with froyo FRF72.
I would imagine that Desire would be SLOWER than stock android not faster. However the animations may be better optimized. I only used sense on the G1 and it was slow as heck on there (i would have used it all the time otherwise) The main reason that things look so choppy is because rendering is not handled by the GPU, rather the CPU. This puts more strain on the CPU than should be necessary.
I don't get why they OC the CPU either. Seriously, 1gHz is fast for a PHONE. I can understand why when the phone starts getting dated why you would....but its not gonna be dated till at least Q4 2010 when the 1.2-2gHz snapdragons are coming out.
Qualcomm will have a 1.5gHz ready for new phones this year. DUAL-CORE
http://gizmodo.com/5443976/qualcomm...dragon-smartphones-are-about-to-go-hyperspeed
As for the problem. Sounds weird. Try LauncherPro for a test. That is smooth launcher that flows like butter. If that is choppy then there is something seriously fu-bar going on with yer phone
I've flashed the stock froyo FRF50 now and till now it looks a lot better. OS manager now shows a total of 400MB memory. Is this the normal amount it should show? Or should I be looking for another kernel for froyo? And what is the difference between froyo FRF50 and FRF72?
-------------------------------------
Sent via the XDA Tapatalk App
so is your nexus smooth and fluid now? because mine is very smooth swiping the homescreens. using launcher pro. no choppiness at all.
Stock launchers to me are kinda choppy too. And that was my only complain with the nexus. Like the previous posters advised, try launcher pro and adwlauncher, tweak the settings to your liking and you'll see the difference. As far as kernel for froyo try pershoots kernel, it seems to be very smooth and speedy.
renegadEEE said:
I've flashed the stock froyo FRF50 now and till now it looks a lot better. OS manager now shows a total of 400MB memory. Is this the normal amount it should show? Or should I be looking for another kernel for froyo? And what is the difference between froyo FRF50 and FRF72?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Ok, thanks for al the replies and great advice! With the fresh Froyo rom and a better kernel everything goes way better now!
-------------------------------------
Sent via the XDA Tapatalk App
renegadEEE said:
Ok, thanks for al the replies and great advice! With the fresh Froyo rom and a better kernel everything goes way better now!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
400 is normal. FRF72 seems to help battery life greatly for me. browser seems more stable and google apps have been updated (alarm and calendar)
renegadEEE said:
Ok, thanks for al the replies and great advice! With the fresh Froyo rom and a better kernel everything goes way better now!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Minor suggestion - install ADW.Launcher (you'll have to tweak the settings a bit to make it nice) or Launcher Pro (works great as is) with your Froyo ROM. You'll thank me for it. The stock launcher scrolling is choppy - always has been, never was really fixed in Froyo (at least as of FRF50 - I haven't even bothered trying it with FRF72).
I am interested in this ROM recently posted in the Development section: "[ROM][JB-4.3.1][HALO][P7300/P7310][PORTED] CyanogenMod 10.2 / SGT7"
The last time I experimented with a JB 4.3 ROM on this tablet (back in October), I had issues with Netflix. Excessive buffering and choppiness.
Has anyone used this ROM and tested Netflix extensively? How was it working?
Martin089 said:
I think it is a good and fast ROM, but it does not work 3G and telephony
Click to expand...
Click to collapse
Thanks.... I ended up trying it and am quite pleased. I don't have a 3G-enabled tablet so that is a non-issue for me.
drwtsn32x said:
Thanks.... I ended up trying it and am quite pleased. I don't have a 3G-enabled tablet so that is a non-issue for me.
Click to expand...
Click to collapse
After using it for a while longer, I am seeing buffering/choppiness with Netflix. Anyone else? Otherwise this ROM is pretty nice.
drwtsn32x said:
After using it for a while longer, I am seeing buffering/choppiness with Netflix. Anyone else? Otherwise this ROM is pretty nice.
Click to expand...
Click to collapse
I gave up on this ROM.... it just felt too slow. Not sure if it's because not enough RAM was left over for apps and the like, but everything just felt way too slow.
I am now trying the Stock-based Ultra ROM and the performance is MUCH better. Of course I have to put up with the Samsung stuff.
drwtsn32x said:
I gave up on this ROM.... it just felt too slow. Not sure if it's because not enough RAM was left over for apps and the like, but everything just felt way too slow.
I am now trying the Stock-based Ultra ROM and the performance is MUCH better. Of course I have to put up with the Samsung stuff.
Click to expand...
Click to collapse
I used this rom for a couple of months and never experienced lag except in hd videos and games. I disabled animations, disabled hw overlays, forced gpu rendering and set background process limit to four processes at most. Used nova launcher amd set all amimations to lightning fast and this rom worked like a charm.....never had to overclock. I also disabled a number of apps that I never use.
Ok so I've tried almost every rom there is for the Nook HD+ even some weird Pacman rom. But reciently I decided to try out the stock rom seeing I bought mine already rooted. Its crazy but it seems faster! I was locked in a crazy boot cycle the other day with a newer rom and just decided to install stock as I had it there on my external sd card. I updated it to version 2.2.0 even tho last time I tried it, it failed (Its ment to) and everything just seems smoother. Although its has now been unrooted
I guess the only trouble I will run into is that it doesn't have trim support? I can probably see it slowing down in about 3 weeks.. How is everyone elses experience with the stock rom been?
Maybe it is just your nook that run stock better. Mine two nook and lots of others are running CM like a charm.
At least for mine nook , CM 10.2 just blow stock rom out of water and back in and out again. Smoother , faster, more customisable, better battery life...
Many say also say CM 11 kick ass as well.
I think stock runs faster, too. At first, with a fresh install. After installing my 150 or so apps it gets as slow as anything else if not slower, plus there is no TRIM support. I prefer CM11; it's pretty impressive in both speed and performance, and it's hard for me to give up the many customizations available and built-in root access.
Darrian said:
I think stock runs faster, too. At first, with a fresh install. After installing my 150 or so apps it gets as slow as anything else if not slower, plus there is no TRIM support. I prefer CM11; it's pretty impressive in both speed and performance, and it's hard for me to give up the many customizations available and built-in root access.
Click to expand...
Click to collapse
hmmmm i was just pondering , how much faster cm11 will be compared with stock rom , just bought a HD+ , browsing is a bit sluggish and choppy when zooming in and out , using a fairly low level browser called Boat browser , i use the same browser on my Samsung Note 3 and its spot on nice and fast........i was hoping CM11 when i install it tomorrow would make quite a lot of difference .....seems as if it might not be based on the messages above !!!
justwondering said:
hmmmm i was just pondering , how much faster cm11 will be compared with stock rom , just bought a HD+ , browsing is a bit sluggish and choppy when zooming in and out , using a fairly low level browser called Boat browser , i use the same browser on my Samsung Note 3 and its spot on nice and fast........i was hoping CM11 when i install it tomorrow would make quite a lot of difference .....seems as if it might not be based on the messages above !!!
Click to expand...
Click to collapse
No. stock rom is definitely not faster. Not by a long shot. That's crazy talk.
jamus28 said:
No. stock rom is definitely not faster. Not by a long shot. That's crazy talk.
Click to expand...
Click to collapse
That's good to know, I shall install in the next few hours.
Which is your favourite version of kitkat for the nook hd+?
Antutu results are about 10% better with 10.1 or 10.2 vs stock on my HD. Didn't spend enough time with the stock ROM to tell if there was a noticeable performance difference.
Sent from my BN Nook HD using XDA Free mobile app
Just installed the latest CM11 nightly , boy what a difference it has made to the overall slickness / speed of the Android experince on the Nook HD+ , i only paid UK £54.99 delivered , turned up today , did my homework over the past few days and hey presto CM11 has turn a bit of a sluggish tab into a bargain great experince tablet !!! i generall use my Galaxay Note 3 for my evening surfing , but i guess i will be using the HD + most evenings instead !
jamus28 said:
No. stock rom is definitely not faster. Not by a long shot. That's crazy talk.
Click to expand...
Click to collapse
Maybe OP 's nook is different then most of ours . Stock rom has its magic on his nook.
But for those who is really looking for a more responsive rom, I strongly recommend giving cm a try.
My nook is on cm 10.2. It usually last 1 week for me on a charge and I do quite some reading and watching movies.
justwondering said:
Just installed the latest CM11 nightly , boy what a difference it has made to the overall slickness / speed of the Android experince on the Nook HD+ , i only paid UK £54.99 delivered , turned up today , did my homework over the past few days and hey presto CM11 has turn a bit of a sluggish tab into a bargain great experince tablet !!! i generall use my Galaxay Note 3 for my evening surfing , but i guess i will be using the HD + most evenings instead !
Click to expand...
Click to collapse
Dalvik or ART?
Sent from my BN NookHD+ using Tapatalk
I had the stock ROM with some the mods such as rooted and install unknown apps. I was happy with it but once I tried cm10.1 yellow kernel or the cm10.2 with the archdroid optimizations, I will never go back. I would recommend cm10.2 with the archdroid optimizations unless over clocking is important to you. If OC is important check out the yellow kernel ROM.
Sent from my BN NookHD+ using XDA Free mobile app
justwondering said:
hmmmm i was just pondering , how much faster cm11 will be compared with stock rom , just bought a HD+ , browsing is a bit sluggish and choppy when zooming in and out , using a fairly low level browser called Boat browser , i use the same browser on my Samsung Note 3 and its spot on nice and fast........i was hoping CM11 when i install it tomorrow would make quite a lot of difference .....seems as if it might not be based on the messages above !!!
Click to expand...
Click to collapse
I used to use Boat, too, but now I use Javelin. I recommend you check it out. Also make sure you run trim after you get everything installed and set up; it could make a difference.
I think on the HD+ there's something wrong with the video driver. Because I agree as well that with CM11 (any version M or nightly) the OS seems more responsive but video transitions and anything involving the screen updates is a dog. Try playing games like PvZ or some others with specific types of video needs and it's just a wreck. I made a video to highlight my Nook HD+ vs Kindle Fire (first generation slow as dirt) with the KF boot screen making the HD+ cry. You can see when I page back left after paging right the HD+ stutters trying to load the mostly empty page too.
https://www.youtube.com/watch?v=PEJK-VUZunk
brentil said:
I think on the HD+ there's something wrong with the video driver. Because I agree as well that with CM11 (any version M or nightly) the OS seems more responsive but video transitions and anything involving the screen updates is a dog. Try playing games like PvZ or some others with specific types of video needs and it's just a wreck. I made a video to highlight my Nook HD+ vs Kindle Fire (first generation slow as dirt) with the KF boot screen making the HD+ cry. You can see when I page back left after paging right the HD+ stutters trying to load the mostly empty page too.
https://www.youtube.com/watch?v=PEJK-VUZunk
Click to expand...
Click to collapse
Nook HD+ has a 1920x1280 LCD. That's a lot of pixels to render and it is a bit too much for the TI OMAP 4470 to bear it seems. Most high performance computers don't even render that many pixels.
swaaye said:
Nook HD+ has a 1920x1280 LCD. That's a lot of pixels to render and it is a bit too much for the TI OMAP 4470 to bear it seems. Most high performance computers don't even render that many pixels
Click to expand...
Click to collapse
The Kindle Fire HD 8.9" uses the same CPU/GPU and it doesn't have issues doing the same tasks. As the OP stated too the stock rom handles the load better too. I really believe we have a driver or memory management issue.
brentil said:
The Kindle Fire HD 8.9" uses the same CPU/GPU and it doesn't have issues doing the same tasks. As the OP stated too the stock rom handles the load better too. I really believe we have a driver or memory management issue.
Click to expand...
Click to collapse
Could be. Jon Lee of the Yellow Kernel thread has done some changes to the PowerVR and Vivante GPU drivers but it hasn't really changed much as far as I can tell.
He also suggested using the "Force GPU rendering" setting in developer options but that has some caveats. It forces apps that aren't configured to use GPU rendering to do so, but forcing things doesn't always work out as you'd like. Some apps use the GPU(s) already.
We have smart people working on the kernels here and if whatever causes the graphics lag was obvious/addressable it would probably be gone. I am positive that resolution is part of the problem. I've used lower end OMAP4 devices like Nook Tablet with 1024x600 and they were much smoother.
brentil said:
Try playing games like PvZ or some others with specific types of video needs and it's just a wreck.
Click to expand...
Click to collapse
Games aren't a really good way of deciding what's happening.
They can have different quality settings that there's generally no menu for, so its automatic picking for quality. Historically at least, Real Racing 3 would pick it wrongly and thus the game would have bad framerate on the nook hd+ needing use of a 3rd party app to force the game to lower graphics quality.
sandsofmyst said:
Games aren't a really good way of deciding what's happening.
Click to expand...
Click to collapse
I typically agree with this statement but if you view the video I posted in my other thread about this topic it's clearly apparent that an old as dirt, 1 GHz, 512mb, very first generation Android tablet running the exact same OS release smacked the crap out of the HD+. The Nook HD+ as is, is an embarrassing device running the non-default OS. The point of this is to ensure someone is aware of this and to see if anything can be done about it.
I haven't tried an emmc install of cm, only dual boot Jelly Bean and KitKat sd cards. But they break some of my regularly used apps, hence no emmc install.
But what I haave found is replacing the stock launcher with Holo launcher really speeds up stock. And Swapps task switcher lets you access recent apps. I'm not sure how it compares to an internal install of cm though, but I'm happy enough with performance.
In reading the commits for my Note II I noticed some new commits for the HD+ that haven't been closed yet. It looks like they're enabling a 128 MB swap partition for this device.
http://review.cyanogenmod.org/#/c/68840/
I had bought a Nook HD+ to be the replacement for my aging 1st generation Kindle Fire (Otter) tablet. However after having had it for 6 months now I've been rather disappointed with it. On paper it should have been better than my OG KF in every way but in reality that has not been true.
Nook HD+
Released 2012
1.50GHz TI OMAP 4470 (ARM Cortex A9 + PowerVR SGX 544)
1 GB of memory
32 GB storage (controller without issue too)
CM11 Nightly 2014.08.02 installed to internal storage
Davlik, stock kernel, not overclocked
Kindle Fire
Released 2011
1GHz TI OMAP 4430 (ARM Cortex A9 + PowerVR SGX540)
512 MB of memory
8 GB storage
CM11 Nightly 2014.08.02 installed to internal storage
Davlik, stock kernel, not overclocked
Whenever it comes to anything relating to the screen though this old as dirt KF tablet still performs better than this much newer and on paper better device. The Nook HD+ is obviously better as most apps perform much better like browsing FB app, looking at web pages with lots of content, running any number of non-visual intensive apps.
Places the Nook HD+ bogs down.
Paging around in the home screen stutters when loading icons even if the page has already been loaded.
Closing an app and returning to the home screen is extremely sluggish and then requires reloading of each page.
The boot animation is completely embarrassing, it jitters and skips like it's been beaten to death.
Scrolling through large pages of data in Chrome jitters rather badly.
Some games with intensive video requirements are just nasty at times. Running really slow or slowing down over time.
This video shows the KF next to the Nook HD+ to show how horrible the start animation is. After loading I page left then right and you can see the home page stutter on loading the icons when I come back left.
https://www.youtube.com/watch?v=PEJK-VUZunk
This video shows loading PvZ 2 where just the loading screens alone are running slower and jitter more. Then when loaded menus take longer to load and are very jittery compared to the KF.
https://www.youtube.com/watch?v=XCG8GKIWyso
Note - I even removed the overclock from the KF for these tests.
I realize the resolution is greater on the HD+ than the KF but the Amazon KF HD 8.9" uses the same hardware as the HD+ and it doesn't have the same issues. I also recall when running the stock firmware the system was much more responsive than it is under CM11 (any version).
This really seems like a lack of a good video driver or something wrong with the memory management.
I'm looking for serious discussion on this and not "well mine works fine so it must be yours..." or suggestions of running some random ROM or running TRIM or tweaking some random setting. This is something more than basic settings as I've already tried several over the last 6 months along with fresh installs of CM.
Your hd+ looks normal. I wouldn't think about it too much as its more than likely not getting better than that.
I just bought a new phone and the hardware made android so much more snappier then it was on the last one no matter how much people had tweaked the roms.
Just how it is. Its a cheap tablet with a nice size screen and hardware not quite capable.
sandsofmyst said:
Your hd+ looks normal. I wouldn't think about it too much as its more than likely not getting better than that.
I just bought a new phone and the hardware made android so much more snappier then it was on the last one no matter how much people had tweaked the roms.
Just how it is. Its a cheap tablet with a nice size screen and hardware not quite capable.
Click to expand...
Click to collapse
I've installed CM11 for two of my friends on their HD+'s, and their is snappier than mine. All are fresh installs. There is a very noticeable difference between mine (purchased in June, 2013), and theirs (purchased in May & June 2014). I didn't write everything down, but there was very little difference in the information for each device as reported by Quadrant.
Odenknight said:
I've installed CM11 for two of my friends on their HD+'s, and their is snappier than mine. All are fresh installs. There is a very noticeable difference between mine (purchased in June, 2013), and theirs (purchased in May & June 2014). I didn't write everything down, but there was very little difference in the information for each device as reported by Quadrant.
Click to expand...
Click to collapse
You maybe experiencing lag since you have been running longer (since 2013, not just with CM11). Also you may have a different emmc chip than they do. There are hardware differences between some devices
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You maybe experiencing lag since you have been running longer (since 2013, not just with CM11). Also you may have a different emmc chip than they do. There are hardware differences between some devices
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the info. I'll ask them to send me the device info and I'll compare them both. Based off of what you said earlier, it may be due to too many writes to the chip? If so, I can live with that. I did abuse the heck out of it.
Thanks to you, VG, and everyone else in the community who put all of this together.
Odenknight said:
Thanks for the info. I'll ask them to send me the device info and I'll compare them both. Based off of what you said earlier, it may be due to too many writes to the chip? If so, I can live with that. I did abuse the heck out of it.
Thanks to you, VG, and everyone else in the community who put all of this together.
Click to expand...
Click to collapse
That is exactly what I meant. But if you run CM11 enough, it may speed up due to it running TRIM in the background.
Sent from my BN NookHD+ using XDA Premium HD app
Idk. Had two of these, one for three months and this one since around when you got yours. It performs as I remember and as I expect.
But since your comparing directly to another aren't ALL electronics that way? This display is more blue than that one, this hard drive has more errors that that one. This cpu can be oc'd more than that one.
There's always things causing speed differences. Background services, amount of free space - its best to have >50% free space, amount of installed apps, what leapinlar pointed out, etc.
In one month they could have no noticeable difference. Tis all I'm saying.
[You might was to switch over to using art instead of dalvic as well if not already. It may/may not help in making it feel faster as its suppoed to be the PBT™ (Performance Boosting Thing). Mine is on art. You may also want to go into the recovery and do a full backup before that.]
sandsofmyst said:
[You might was to switch over to using art instead of dalvic as well if not already. It may/may not help in making it feel faster as its suppoed to be the PBT™ (Performance Boosting Thing). Mine is on art. You may also want to go into the recovery and do a full backup before that.]
Click to expand...
Click to collapse
Pardon my ignorance, but how do you do this?
neoage said:
Pardon my ignorance, but how do you do this?
Click to expand...
Click to collapse
This post is for a phone, but it is the same for all devices (I just randomly picked a post):
http://forums.androidcentral.com/android-4-4-kitkat/404625-enabling-art-android-4-4-3-devices.html
Quote "To enable ART, Go to settings => About Phone =>Then go to Build Number and tap on Build Number until it ask if you want to enable Developer Options (or something in that effect) Once you say yes, Go back once and above About Phone you should see Developer options.
Under Developer options, go to "Select Runtime" (which should be on Dalvik) and select ART. Once you do this it will need to reboot your phone and then it will go through an update process on your Apps. Depending on how many Apps you have this can take a bit. I suggest doing when you won't need your phone for a few minutes and also make sure to plug your phone into power to help it go faster.
Once it is done, I suggest testing one or two apps to make sure they work. Then I would reboot your phone one more time. (This seems to fix a noticed app lag after the update). Once it comes back up, use your phone as normal and enjoy the free speed boost and a little added battery life. I have not noticed any issue with the 168 apps on my Nexus 5 nor any stability issue with the device, but again you millage may vary on your device and apps."
Some additional notes:
I stress doing a full recovery backup first. If you don't have enough internal space available, then that may cause it to be unusable when android starts up due to it failing while configuring art.
Phones (and other low internal storage devices) are a bit problematic due to amount of space available. My htc sensation couldn't enable art from not enough internal space. But the nook hd+ (for instance) has plenty (assuming its not all used).
Art is supposed to be enabled automatically in the next android release.
"With the L Developer Preview, ART is now the default runtime."
https://developer.android.com/preview/api-overview.html
Art requires more space due the fact that apps are pre-compiled during install:
"ART, on the other hand, uses an Ahead-of-Time compiler (AOT) to process application instructions before they're needed so things run more smoothly for the user."
http://lifehacker.com/android-art-vs-dalvik-runtimes-effect-on-battery-life-1507264545
You'll possibly lose about half a GB or more. It just depends on how many apps including the apps included with the rom.
The reason why the hd+ has poorer performance is probably due to it dragging a 1920x1080 (2073600 pixels) screen while the Fire has a 1024x600 screen (614400 pixels). Processing a full 1080p screen vs a 600 makes a big difference. The 544 isn't much of an upgrade over the 540 to make up for it. While it doubles the frame rate in graphics by about 2x over the 540, its having to push more than 3x the pixels.
Apple had the same issue with the ipad 3 when they went to the retina screen. It was a bit of a dog on pushing the retina screen, hence the quick rollout of the ipad 4 with a much faster cpu and gpu.
Lastly, amazon has a lot of pretty good paid developers optimizing the heck out of the Fire. I doubt its running a stock google display/graphics driver.
One of the things with high density displays. They're pretty and nice for text but you need plenty of horsepower to run them.
I signed up for alerts but doesn't seem like I was getting them.
I was comparing it to the OG Kindle Fire because it was the first real Android tablet and it's old as dirt now. Also as mentioned in the other performance vs stock thread when running the default Nook HD+ OS the interface is a lot more responsive and games perform better too. It seems like there's something missing between those kernel's/drivers and the CM version.
Of note these commits might help us with some of our issues. It looks like they're enabling a 128 MB swap partition for this device.
http://review.cyanogenmod.org/#/c/68840/
Total noob here, so please go gently on me. I've searched the Nook HD/HD+ General Forum and could not find any threads on this- forgive me if I missed them.
I'm on my second HD+. The first one would overheat and shut down. I've seen online that this is a common problem. The new (recertified) one also heats up in the lower left quadrant when using a browser, but it hasn't shut down (yet).
I've tried CM11 on SD just for fun, but it freezes several times an hour on me, which makes it hard for me to give Kitkat a fair trial. Honestly, I don't have any issues with the Nook stock ROM. I've put Holo Launcher on it, and it does everything I want to just fine (photo frame, reading, simple games, videos, etc.).
I would be willing to root and/or EMMC CM ROM if it would help with the overheating issue without sacrificing stability or battery life.
Any ideas?
Thanks!
Heat issues
I had heat issues with stock and all CM11 roms. However....Pac Rom seems to have solved the issues.
Go here for how to : http://forum.xda-developers.com/showthread.php?t=2705381
I've tried many of these ROMs and am using this with ZERO problems. Don't forget to turn off location services and be chincy with apps you let run in the background. No CNN widgets.
Download: https://s.basketbuild.com/filedl/de...tion/nightly/pac_ovation-nightly-20140805.zip
I am using the latest TWRP .... http://forum.xda-developers.com/nook-hd/development/recovery-unofficial-twrp-2-7-1-0-t2828280
Not sure if this will flash with CM recovery...Think so..just not sure.
Either way...Pac Rom has been the best so far for my Nook HD+
tigerucla said:
Total noob here, so please go gently on me. I've searched the Nook HD/HD+ General Forum and could not find any threads on this- forgive me if I missed them.
I'm on my second HD+. The first one would overheat and shut down. I've seen online that this is a common problem. The new (recertified) one also heats up in the lower left quadrant when using a browser, but it hasn't shut down (yet).
I've tried CM11 on SD just for fun, but it freezes several times an hour on me, which makes it hard for me to give Kitkat a fair trial. Honestly, I don't have any issues with the Nook stock ROM. I've put Holo Launcher on it, and it does everything I want to just fine (photo frame, reading, simple games, videos, etc.).
I would be willing to root and/or EMMC CM ROM if it would help with the overheating issue without sacrificing stability or battery life.
Any ideas?
Thanks!
Click to expand...
Click to collapse
They all get a little warm in the lower left the CPU is there and they don't have fans. It should not get so hot as to be uncomfortable though.
Sent from my SPH-L900 using XDA Free mobile app
tigerucla said:
...
I've tried CM11 on SD just for fun, but it freezes several times an hour on me, which makes it hard for me to give Kitkat a fair trial. Honestly, I don't have any issues with the Nook stock ROM. I've put Holo Launcher on it, and it does everything I want to just fine (photo frame, reading, simple games, videos, etc.).
I would be willing to root and/or EMMC CM ROM if it would help with the overheating issue without sacrificing stability or battery life.
Any ideas?
Click to expand...
Click to collapse
In my experience CM10.x and CM11 run noticeably cooler than stock ROM.
What brand & class of SD did you use? Generally class 4 is better than class 6 or 10 for running ROM off SD -- see http://forum.xda-developers.com/showthread.php?t=1005633 for discussion of comparative performance of different SD makes/models for the purpose of hosting ROM.
Thank you all for your help. I guess if it doesn't shut down, I can live with it warming up a bit.
Have any of you had any instability issues with the ROMs you're currently using? Any effect on battery life?
The SD card I'm using is a SanDisk 16GB class 4 micro SDHC. I played with it some more today, and it's no better- still freezes quite often.
tigerucla said:
Thank you all for your help. I guess if it doesn't shut down, I can live with it warming up a bit.
Have any of you had any instability issues with the ROMs you're currently using? Any effect on battery life?
The SD card I'm using is a SanDisk 16GB class 4 micro SDHC. I played with it some more today, and it's no better- still freezes quite often.
Click to expand...
Click to collapse
I never liked running ROMs on any SD cards because the internal memory is usually much faster on these sort of devices. I'm not 100% sure (maybe someone who is can chime in), but I believe that you're not going to have TRIM support with a SD card so the system is going to slow down over time.
Thanks ryanl2299. I'm only running on SD as a trial. I realize that running it on EMMC would be faster and more stable. But I have seen in forums that some people still have problems running ROMs on EMMC.
If the overheating issue becomes more of a problem (i.e. random restarts/shutdowns), I just want to know if there are any apps or ROMs which would improve the overheating issue. If there are any ROMs which would help, I most certainly do an EMMC install (as long as I'm not trading one problem for another due to the ROM being unstable).
Thanks again for everyone's input!
Custom HD+ Roms
tigerucla said:
Thanks ryanl2299. I'm only running on SD as a trial. I realize that running it on EMMC would be faster and more stable. But I have seen in forums that some people still have problems running ROMs on EMMC.
If the overheating issue becomes more of a problem (i.e. random restarts/shutdowns), I just want to know if there are any apps or ROMs which would improve the overheating issue. If there are any ROMs which would help, I most certainly do an EMMC install (as long as I'm not trading one problem for another due to the ROM being unstable).
Thanks again for everyone's input![/
Technically, the stock ROM is not much different than Pac-Roms or CM10 or CM11 or Vanir, Omni or Android box Wasser. Sure there are elements that differ from device. We all need to be able to freely change to custom ROMs for our device and go back and forth. It's like overclocking your pc. The stock B&N Rom can be backed up and restored. Always do a back up on good SD card. Perhaps even upload your backed up ROM to a cloud source.
I will probably die with my HD+ in my hand.
Vanilla Droid is always best.
Click to expand...
Click to collapse
How you use it will effect heat more than any rom will (think games vs reading).
Though, I'm wondering if down clocking the cpu would help or hurt.
Or how about art instead of dalvic. Chrome instead of firefox. low brightness vs. full brightness, in 90 degree weather vs indoors. Etc. Course all that could be included under how you use it as well and all of it can affect heat output.
I have never worried about overheating when used within reason - they should not overheat except for a factory defect or outside of reasonable conditions of which the latter should be covered under technical boundaries and common sense. If your in direct sun and it feels too hot then move the device into the shade. etc.
ART didn't work
Switched to ART on my Nook HD+ using pac_ovation 4.4.4 08252014. The tablet works amazingly well with Dalvik. ART seems fine....can't tell much difference in speed. Wish this tab had a quad core. Truly good stuff with Omniswitch and Slim Recents along with the app bar. Love it.
sandsofmyst said:
How you use it will effect heat more than any rom will (think games vs reading).
Though, I'm wondering if down clocking the cpu would help or hurt.
Or how about art instead of dalvic. Chrome instead of firefox. low brightness vs. full brightness, in 90 degree weather vs indoors. Etc. Course all that could be included under how you use it as well and all of it can affect heat output.
I have never worried about overheating when used within reason - they should not overheat except for a factory defect or outside of reasonable conditions of which the latter should be covered under technical boundaries and common sense. If your in direct sun and it feels too hot then move the device into the shade. etc.
Click to expand...
Click to collapse
jaytee100 said:
I had heat issues with stock and all CM11 roms. However....Pac Rom seems to have solved the issues.
Go here for how to : http://forum.xda-developers.com/showthread.php?t=2705381
I've tried many of these ROMs and am using this with ZERO problems. Don't forget to turn off location services and be chincy with apps you let run in the background. No CNN widgets.
Download: https://s.basketbuild.com/filedl/de...tion/nightly/pac_ovation-nightly-20140805.zip
Click to expand...
Click to collapse
Sorry to hijack the thread. Do you feel PAC gives you better smoother performance. What score do you get with antutu 5?
Do you still get screen flashing if you don't disable hardware overlay?
I'm running cm11 and it's OK but always looking around [emoji1]
Thanks.