[Q] Hd+ extremely suggish

peeam

Member
Dec 14, 2010
33
5
0
My HD+ of late has become more and more sluggish and sometimes becomes unresponsive for a few seconds. It hangs when opening an app, a book or while browsing the web. I am using the updated stock 2.1. Checking the RAM, I was surprised to see free RAM as low as 80MB. Killing apps running in the background does not help much. The internal memory is only 40% full. I am at a loss to understand what is going on. Has anybody else noticed this ? Should I wipe it clean and start again ? My device is not rooted. Any advice regarding backing up would be helpful.

Thanks

PeeAM
 

cozumelstu

New member
May 27, 2013
1
0
0
maybe uninstall some questionable apps

My HD+ of late has become more and more sluggish and sometimes becomes unresponsive for a few seconds. It hangs when opening an app, a book or while browsing the web. I am using the updated stock 2.1. Checking the RAM, I was surprised to see free RAM as low as 80MB. Killing apps running in the background does not help much. The internal memory is only 40% full. I am at a loss to understand what is going on. Has anybody else noticed this ? Should I wipe it clean and start again ? My device is not rooted. Any advice regarding backing up would be helpful.

Thanks

PeeAM
I was having similar issue so I started looking at apps that weren't exactly Nook approved. I removed an HD wallpaper app and my Nook was healed.
 

peeam

Member
Dec 14, 2010
33
5
0
I just saw lag on my swift key keyboard for the first time. I'm using apex too.
I am using Nova launcher from day 1 and the performance has deteriorated over time, so I cannot blame it. It could be an app hogging the memory. I have to kill a lot of processes to make it functional. I routinely get the message about the program not responding irrespective of which app I have opened. Even the browser (chrome, ICS) just crashes.
 

jamus28

Senior Member
Mar 17, 2011
656
284
0
So after booting up my new HD+ for the first time today, and letting it update to 2.1, it was extremely slow... Slower than my 600mhz HTC aria. I tried rebooting again and installing apex. i have google sync disabled.

Then I force stopped "Home" and cleared its data. The tablet runs better, even when using B&N Home launcher.

its still not as fast as the dual core should be. I wish there was a way to reduce or disable animations in developer options.
I may try CM10.1
 

xdatoast

Member
Mar 28, 2011
21
0
0
So after booting up my new HD+ for the first time today, and letting it update to 2.1, it was extremely slow... Slower than my 600mhz HTC aria. I tried rebooting again and installing apex. i have google sync disabled.

Then I force stopped "Home" and cleared its data. The tablet runs better, even when using B&N Home launcher.

its still not as fast as the dual core should be. I wish there was a way to reduce or disable animations in developer options.
I may try CM10.1
I'll add my name to those seeing lag since the update to 2.1. I'll try this and see if I get improvment. Anyone have any idea why this might be happening?
 

jamus28

Senior Member
Mar 17, 2011
656
284
0
My tablet is running at a more satisfactory speed since I froze/disabled a bunch of bn apps, ditched apex, and use lightning launcher/zeam with full!screen. I also used spareparts+ to set animation transitions to fast.
Just don't make the mistake I made first of uninstalling twitter or chrome. All your hard work will reset.


I may make a symlinked build prop and play with this.
https://code.google.com/p/android/issues/detail?id=40961

It worked on my htc one s with similar specs.
 
Last edited:

jamus28

Senior Member
Mar 17, 2011
656
284
0
So I adjusted the heapgrowthlimit and heapsize.
The stock settings were at 96M and 160M respectively. I don't know what they were pre-2.1

I changed a symlinked buildprop to 64 and 384.

So it feels a bit snappier. Could be placebo, but it's definitely not slower. If anyone else tries adjusting these let me know what you think.
 

View92612

Senior Member
May 10, 2013
117
14
0
Plano, TX
So I adjusted the heapgrowthlimit and heapsize.
The stock settings were at 96M and 160M respectively. I don't know what they were pre-2.1
I changed a symlinked buildprop to 64 and 384.
I checked and found verygreen's CM10.1 rom (emmc) has 64 and 256. It is very snappy.
It's not apple to apple comparison as CM10.1 is based on Android 4.2.2.
I'm surprised stock has only 160M though.
 

rushless

Senior Member
Jan 16, 2008
3,684
446
0
The killer for me is the library sync process. I disabled the app, but it still does its thing. When a game or app slows down, it is when the sync starts. It is random, but should only be when the device is turned on, or when content is changed. The way they set it up makes no sense.

Restarting the device still shows the app disabled, but still syncs.

There also appears to be a lag that happens and is only fixed by a restart, but that is not as common as the sync issue.
 
Last edited:

View92612

Senior Member
May 10, 2013
117
14
0
Plano, TX
The killer for me is the library sync process. I disabled the app, but it still does its thing. When a game or app slows down, it is when the sync starts.
That is one of the reasons that led me to replace the stock rom with CM10.1 on emmc. It is much better than the stock rom...
I really do not need that library having both Google Play and Amazon App store. I also have the Nook App which works just fine with CM10.1.
 

rushless

Senior Member
Jan 16, 2008
3,684
446
0
Even after clearing cashe and removing large data games, my HD+ was still acting sluggish. Based on the apps running in the background, no rogue apps seems to be causing it. No games beyond small ones were playing smooth and would randomly studder. Flash content also was making the device run very hot.

I boxed the HD+ up for return. Not sure what the issue is, but probably is 2.1, since the chipset should be fine. I might exchange for another and start from scratch with 10.1... Not sure at the moment. Were it not for the lag and odd heat issues, I would keep the device. Perhaps 10.1 is the answer, but
my return window ends soon.

I feel bad, since when I first got the device, it worked fine and doubted people that said the lag is there and common. They were right and I was wrong, so would be nice if 10.1 fixes the issues.

Added: Though my Excite 7.7 is a lot faster overall, I miss the HD+ display already.
 
Last edited:

View92612

Senior Member
May 10, 2013
117
14
0
Plano, TX
No games beyond small ones were playing smooth and would randomly studder. Flash content also was making the device run very hot.

Added: Though my Excite 7.7 is a lot faster overall, I miss the HD+ display already.
I was able to play Dungeon Hunter 4 on CM10.1 and it seems to be okay. Web browsing is also very smooth. Flash does make it quite hot but same as my HTC Amaze Android phone so I'm used to it.

However, The HD+ is definitely not perfect, once in a long while (maybe like once in 2-3 days) the touch UI may become unresponsive.
That can be fixed by turning off and turning back on the display. Also I had screen flickering in settings screen(black background) under CM10.1 RC2. I have since flashed the latest RC4 and the flickering is gone. I have not tested it long enough to see if it still has the same UI problem.

Sorry for your bad experience. I am keeping the HD+ for myself but would not buy it for gifts because I know it has some issues that are not easy to fix without modification. And not everyone wants or has time to mod a tablet.

Update:

Just ran another Vellamo HTML5 benchmark and scored 1899 with CM10.1 RC4...very impressive.
On stock it was 1378 and I had 1379 on Nexus 7. Of course, benchmark may not be 100% indicative of daily operations.
Web browsing seems to be at least on par with Nexus 7, though. With the bigger screen it is definitely a more pleasant experience.
 
Last edited:

peeam

Member
Dec 14, 2010
33
5
0
It seems that there is a big difference in benchmarks and actual performance, at least for some individual devices. I tried everything including CM10, orginal stock and the latest stock. Each time it would be fine initially and then gradually slow down to become unresponsive. I 'killed' processes, background apps frequently to make it usable but that ought not to be the way for regular use. I play no games except occasional spider solitaire. The main use was web browsing and reading books. I also have a samsung 7plus tab which did not suffer from any of these issues and became my go to device. So for now, its THANKS to the developers and goodbye Nook via ebay.

PeeAm
 

rushless

Senior Member
Jan 16, 2008
3,684
446
0
The 4470 for browser marks is faster than the Tegra 3. At least that is what Anandtech shows.

I took mine back to Best Buy, but do miss the display. Played MAME reloaded great. Seems any game that retrieves data on the fly has issues with stuttering with 2.1 at least. The reason I think this, is small games do not have the issue, nor does MAME which loads the games into memory to play. No on the fly data access.

Still tempted to get another and try 10.1 from the start. Even after a reset, 2.1 had the issues with games and other apps where my Excite 7.7 is smooth. In the Nooks defence, the TF300 is not real smooth either. A little better than the Nook HD+, but slower with MAME. Nook ruled with MAME.
 

View92612

Senior Member
May 10, 2013
117
14
0
Plano, TX
It seems that there is a big difference in benchmarks and actual performance, at least for some individual devices. I tried everything including CM10, orginal stock and the latest stock. PeeAm
Just curious...did you try CM10 or 10.1. Also did you run it on SD card or emmc?
I didn't like CM10 at all and tried CM10.1 on SD card at first. The SD card performance simply sucks. It is only good for experiments not for any serious usage in my opinion. (Had poor benchmark results worse than stock, too.)
I tried CM10.1 RC2 and RC4 on emmc mainly for reading and web browsing. Both worked great.

Although I was able to play Dungeon Hunter 4, (from the start to boss fight) I believe I get a bit better frame rates on Nexus 7.
It's playable on Nook HD+ at reasonable frame rates but not super fast.(looks much better due to bigger screen)
I did not have any io issues likely because Dungeon Hunter 4 load all contents into memory up front in each area.
When I transition to a different area I did notice a temporary lag---must be from the loading of new data.

There is one trade-off with CM10.1 which is that the free gems supported by ads do not work.
I installed promotional apps but the gems never show up on the Nook HD+. That's not the case with Nexus 7.
 

peeam

Member
Dec 14, 2010
33
5
0
I actually started using the Nook HD+ with CM10 on SD. The primary reason for buying it was the active developer community. I chose CM 10 over 10.1 as it was considered more stable than 10.1. Initial experience was great. However, I found that the the stock was better for battery life and for the sleep function with shutting the case. Then I updated the stock with the latest version and gradually the device became slower irrespective of using CM 10 or stock. I did not move to installing CM 10.1 on emmc as by then I had decided to sell the device. Again, not being a 'gamer' the great screen resolution and other specs was less important than battery life and responsiveness on browsing for the way I used the device. Like most things in life, I am sure there is a right 'one' for each one of us.
 

rushless

Senior Member
Jan 16, 2008
3,684
446
0
Battery life for what it was mainly intended (reading stuff and light apps) is great, but playing Flash and 3D games seems to be the main killer. Playing local video was good too. Since I am a gamer to some degree, the stutter from any game that loads data bugged me. No other Android device I have does this. The TF300 has issues with multitasking, but games do not stutter.

I think the issue is 2.1, but perhaps they cut corners with ram and flash speed? This would explain the stutter and the slooow load time for games like Asphalt 7. Even 108mb size pak files for Quake 2 loaded slowly. Almost ten times slower than my other devices. A few seconds or less on the other devices.
 
Last edited: