Database Develop

[Q] Touchscreen sensitivity issues in CM9/CM10 (but not webOS)... any advice?

Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.

To clarify, I think this might be two separate issues...
I'm not as concerned with the CM9 issue, as it is only a mild annoyance and everything else is outstanding. CM10 is virtually unusable, however, so I'm hoping someone can help me out there.

thatdumbguy said:
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
Click to expand...
Click to collapse
I've not had this issue, but this might help. Go here : http://goo.im/devs/jcsullins/cmtouchpad/testing
Download the touch pressure utility (should be the last one) and flash it. Hope it helps.
Good luck.

As an update, after shelving the touchpad for a few months, I have revisited it, and, after doing a clean install of jcsullins' CM10.1 w/BT Fix (20130808), the same issues as above still persist. I've done the following, although I didn't really expect most of them to work:
Switching to stylus mode (no difference)
Changing the accessibility settings for touch & hold delay
Even went so far as to install another launcher (nova) to ensure it wasn't trebuchet (not that I think it was)
Same for the keyboard
This has never been an issue I've seen in webOS... additionally, I don't remember ever having any issues in CM7 either. I did play with webOS for some time today to make sure it wasn't some kind of hardware failure between now and the last time I used it frequently, but I failed to reproduce the problem there.
Is there any light someone can shed on the subject? Thanks!

Thanks for that Chicle_11... I don't know why I failed to mention it, but I did also try the patches with CM9, but it is to my understanding that they were rolled into cm9 nightlies at some point?
I wonder if I could be having a minor hardware issue that just isn't severe enough to display in webOS, because I can't seem to find anything else about this, especially the keyboard problem with CM10. Its bizaar for sure.

Started experiencing the same issues after upgrading from cm9
I recently upgraded from cm9 to cm10.2 and immediately noticed this issue. There were no such issues with cm9. When swyping on the keyboard (any - Google, Swype, etc.), the system registers that I lifted my finger, and so garbage gets typed - you can also see the effect in the trace. When typing instead, letters sometimes double-up for a single press. When playing games like PvZ2, dragging a plant results in a release of the plant before I've lifted my finger, and sometimes the plant gets planted across the screen from where my finger is pressing.

[Q] Nook HD+ CM10.1 Issues

I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks

excalibar001 said:
I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks
Click to expand...
Click to collapse
I'm pretty sure there is no light sensor on a tablet that has no camera.

Overall CM 10.1 is a whole lot better than stock 2.1. Some games do not work that did with stock (Buggy Blitz, Moonshiners and NBA 2013), but all the Zen Pinball Star Wars games work (they did not with 2.1).
With CM 10.1, you can not get any more less intrusive with Android, especially compared to stock on the Nook HD+. The good news is there is no more stutter with apps and a lot of apps load faster. The bad news is some apps still load slow and there is intermittent lag when pressing to start apps or navigate. Tapatalk is an example. There can sometimes be a 5 to 10 second delay from the time the app is activated to the time there is an action. Same with navigating and with other apps as far as lag such as browsers and games. The weird thing is when games play, there is no lag or signs of touch response problems. Games play well and so do virtual pads for game emulators. The issue is not touch sensitivity, since the press registers, but sometimes takes a while before an action happens.
For whatever reason, the Nook HD+ has an intermittent lag problem that also existed with stock 2.1, though the app stutter has thankfully gone away. The lag really stands out when comparing to my S3 and Excite 7.7. Those both are stock, but respond instantly when activating and navigating apps and only have slight issues if updating apps in the background.
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Bad memory management, perhaps? Added: Nope, if so, games in action would be laggy as well.

channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
You are right, there is no light sensor so autobrightness does not work.
Sent from my Nook HD+ running CM10.1 on emmc.

rushless said:
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Click to expand...
Click to collapse
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.

verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
Tapatalk seems to be a poster child app for the issue. It does seem like a wait state issue. Added: That said, it does not do it all the time, so probably not app specific. I just use Taptalk a lot. The lag seems to happen with most apps, but not all the time. 30% of the time seems about right. The good news is the stutter issue that was them main problem IMO with stock 2.1 is gone. No sign yet, in spite of the intermittent app start and navigation lag.
What app can I install to log the issue?
Thanks

rushless said:
What app can I install to log the issue?
Click to expand...
Click to collapse
I don't think there is a good one for logging.
I just need to be able to reproduce myself so I can poke at it from multiple angles.

It does seem to be an app start/stop and navigation lag. No lag when using touch or virtual controls in games.
Not having the stutter in the GTA games is nice. It was GTA Stutter City with stock 2.1. as in many other games. Smooth now, while playing a game.

channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
While I agree that HD+ may not have a light sensors, however, a light sensor has nothing to do with camera and primarily used to control the screen brightness. A camera can detect brightness through its image sensors which is separate from a light sensor.

Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.

verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
I would like to thank you first verygreen for your efforts. You have made the HD+ such a useful tablet.
I have noticed that sometimes my screen would turn off momentarily for no reason. This happen more frequently when I am using and charging he tablet at the same time. I believe that it is due to the magnetic cover flap sensors which goes awry for some reason. Is there a way to turn this sensor off for those of us who are not using a cover with magnetic flap?

rushless said:
Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.
Click to expand...
Click to collapse
No, as many have said here, including me, there is NO hardware sensor, so auto brightness cannot work.
Sent from my Nook HD+ running CM10.1 on emmc.

As mentioned, I do not use it, but would not be the first time for a phantom setting. Look at stock 2.1 and the slow app loading, stuttering state that it is. Not exactly a model for strict user experience QA.

Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta

Not had a random reboot yet.

Must be some misbehaving apps since I have never had random reboots. However, my screen flicker once in a while if I charge and use it at the same time.

mrpunk2u said:
Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
GPS is off - not sure what's causing it - Also, i keep getting Google Sign in errors and asks for my password at least 2x daily

Intermittent lag aside, I use the Nook now more than the iPad 4. Same nice display clarity and not locked down.
Wild how an OS mod can change perspective on a device so much.

My biggest problem has been with touch, it's not that responsive sometimes and sometimes I have my finger hovering over a button and it clicks it (is that phantom clicking?).. Overall it's MUCH better than stock and mad props to all the developers. My girlfriends tablet has been getting random reboots as well, i'll check to see if GPS is on.

[Q] Nook HD+ Random reboots normal ?

Hi,
On a Nook HD+ 32GB CM10.1 (6/15) on emmc. I am getting random reboots, perhaps once or twice a day. Is this normal ?
Thanks

I ran that build for about 1 week and had 2 or 3 random reboots total. I am currently running killersloth's Carbon ROM for about 24 hours, and so far no reboots. Not a lot of data to go off yet. The devs are doing awesome and I can only think (hope) it will continue since there are so many Nooks flooding the market right now

I've had quite many android devices (all on customROMs), so I've seen many unexpected reboots.
But no reboot is considered normal.
I flashed the same ROM on six different HD+ (all 16GB, from 5 different stores. Three are mine and other three are for my friends).
I've never seen (or heard complains about) an unexpected reboot.
For my own HD+, I tried CARBON B1/B2 and now back to latest CM10.1 and still haven't seen a reboot.
Maybe some app you're running ?

Usually caused by being overburdened, out of memory. Unfortunately most people report this as "random"
I haven't experienced an unexpected reboot on the HD with verygreens cm10.1 or with my carbon build. However I never keep going if the device becomes sluggish, I let it finish whatever task I told it to do that's using up all the available memory.
Sent from my Galaxy Nexus using xda premium

I've actually switched from CM10.1 EMMC (last build I tried was early August) to CarbonRom (B11).
I don't know if my Nook HD+ was over burdened, but I've seen it charging on my desk and it decides to reboot. I started "tracking" the reboots and noticed that they happened fairly often (once a day or more some times). I'd open Chrome and Nook reader just so they would show up in my recent apps menu. Then I'd leave it and check it later, sometimes the recent apps would be empty which means at some point the tablet rebooted.
Regardless, Carbonrom works well for me since I'm not usually doing anything critical with my tablet just email, web browsing, and reading.
Occasionally I'll bust out FreeCell or Trapped as far as games go. The best part is that I'm not getting the reboots.
Not sure what was happening with CM10.1, but I'll probably give it a shot again when 10.2 isn't experimental because I do like the Trebuchet launcher (which I can put on carbon, but Trebuchet crashes when I try to change the number of screens and a few other settings).

My Nook also randomly reboots. Just lying on the table without me touching it, or when I read comics or surf the web. It does seem *completely* random. I am beginning to think it is a hardware issue B&N cannot fix.

I was using EMMC Carbon B11 for a time in my HD+ because it offered the Tablet UI among other features. I also experienced occasional unexpected reboots while using that ROM but their low rate was nothing that made the ROM unusable. A few weeks ago I switched from B11 to a 4.3 EMMC ROM from iamafanof that also offers the Tablet UI and seems in my experience so far to have noticeably fewer unexpected reboots or restarts. For anyone who is experiencing "excessive" reboot rates using another ROM, iamafanof's 4.3 ROM might be worth a try. He also has a 4.3 ROM for the Nook Tablet. His ROMs can be found at his WordPress.com page.

Hi All,
I was experiencing random reboot issue on my Nook HD+ for a long time.
Only thing that helped is rooting my device and installation of CPU with max frequency 1300 MHz. I haven't noticed degradation of performance but reboots went away.
I assume root cause was CPU overheating
Hope this will be useful for someone

Hi,
I have a NOOK HD+ (with CM 10.2 stable), my device reboot very very often, i don't think it is normal and would like if a expert check my last_kmsg.dat and tell me what is going wrong on my device.
I also set my CPU @1300MHz to avoid overheating but it doesn't helped
thanks in advance
btw. I don't use a SDCard

wahidx said:
Hi,
I have a NOOK HD+ (with CM 10.2 stable), my device reboot very very often, i don't think it is normal and would like if a expert check my last_kmsg.dat and tell me what is going wrong on my device.
I also set my CPU @1300MHz to avoid overheating but it doesn't helped
thanks in advance
btw. I don't use a SDCard
Click to expand...
Click to collapse
Yes. I was seeing this one a lot on CM10.1.3. Definite kernel bug.
I made some kernel changes to /drivers/mmc and haven't seen it since.
If you want to try it, check out my 'overclock omap4470' thread (use one of the last two kernels; I made the touchscreen I2C fixes and mmc fixes at the same time).
FWIW this morning I had a random reboot with ABE Power Management (first reboot in awhile though). So I'm trying to chase that one down.
Edit:
Also here's an example of omap thermal opp throttling.
http://pastebin.com/gA2vFt1e
(this was before I reduced the voltages)

Jon Lee said:
Yes. I was seeing this one a lot on CM10.1.3. Definite kernel bug.
I made some kernel changes to /drivers/mmc and haven't seen it since.
If you want to try it, check out my 'overclock omap4470' thread (use one of the last two kernels; I made the touchscreen I2C fixes and mmc fixes at the same time).
FWIW this morning I had a random reboot with ABE Power Management (first reboot in awhile though). So I'm trying to chase that one down.
Click to expand...
Click to collapse
Thx Jon for replay, i will try that and report how that gone
btw. can i use your kernel with CM10.2 or should i downgrade to CM 10.1.3 first?

[Q] Problems with Touchpad CM

Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/

iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.

chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning

Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..

iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.

chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.

I use milaq's nightlies, and for my needs, it's more than adequate.

[Q] CM11 M10 Ovation test?

The M10 build of CM11 just came out, I read the blog post and saw the new version in my OTA updates (I flashed CWM to internal so I can do that and have for a few versions). I know it will probably go smoothly, but the horror stories about boot loops, soft bricks, and Android system process crashes that I've read about in the comments make me really nervous. Nobody's yet posted about the HD+/Ovation, but the first 5 CM11 M updates were all bad, even with a complete wipe, so I don't want to take the risk.
I am aware, though, that there are many users here who literally keep their devices for development and ROM testing purposes and don't have (much) personal date to worry about losing. Not so for me. So, I was wondering, could anyone do a CWM backup to SD, perform the OTA upgrade from the settings panel, and write a review/say what happens? Note that I have the most recent gapps installed, so those should be tested because they may cause issues.
Preferably someone with gapps who was going to do an upgrade anyway, so I don't inconvenience anyone by having them upgrade where they otherwise wouldn't.

You hint, but do not really say, that you already have CM11 installed. If so what version?
Many have already tried M10 and said there are issues with media scanner if you dirty install. See the CM11 thread.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
You hint, but do not really say, that you already have CM11 installed. If so what version?
Many have already tried M10 and said there are issues with media scanner if you dirty install. See the CM11 thread.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
M9, and it works perfectly, which is why I'm wary about updating. Also, the media scanner error can apparently be fixed by wiping the app's data/cache in settings and rebooting.

Seanthedroid said:
M9, and it works perfectly, which is why I'm wary about updating. Also, the media scanner error can apparently be fixed by wiping the app's data/cache in settings and rebooting.
Click to expand...
Click to collapse
I installed M10 over M9, and it went very smooth. The usually two reboots, followed by optimising apps, and everything is up and running again. If anything comes up, I will certainly mention it.

Seanthedroid said:
The M10 build of CM11 just came out, I read the blog post and saw the new version in my OTA updates (I flashed CWM to internal so I can do that and have for a few versions). I know it will probably go smoothly, but the horror stories about boot loops, soft bricks, and Android system process crashes that I've read about in the comments make me really nervous. Nobody's yet posted about the HD+/Ovation, but the first 5 CM11 M updates were all bad, even with a complete wipe, so I don't want to take the risk.
I am aware, though, that there are many users here who literally keep their devices for development and ROM testing purposes and don't have (much) personal date to worry about losing. Not so for me. So, I was wondering, could anyone do a CWM backup to SD, perform the OTA upgrade from the settings panel, and write a review/say what happens? Note that I have the most recent gapps installed, so those should be tested because they may cause issues.
Preferably someone with gapps who was going to do an upgrade anyway, so I don't inconvenience anyone by having them upgrade where they otherwise wouldn't.
Click to expand...
Click to collapse
I went from 10.2.1 to cm 11 nightlies just a few weeks ago and was pleased except for a few glitches like screen flashes between apps. When m10 came out I decided to go for what I understood as a generally more stable rom. Unfortunately I did not wipe first as I had upgraded from previous nghtlies without a problem. I had some issues as mentioned in another thread and realized you must wipe before install and I reinstalled. So far so good and I thank titanium for making restoration so easy. I still see screen flashes and a few random crashes but it seems good.

MrPuddington said:
I installed M10 over M9, and it went very smooth. The usually two reboots, followed by optimising apps, and everything is up and running again. If anything comes up, I will certainly mention it.
Click to expand...
Click to collapse
I've just upgraded to m10, it's smooth and stable
But my device is slow, maybe cpu of nook hd+ is weak
Sent from my C6916 using Tapatalk

USRobotics said:
I've just upgraded to m10, it's smooth and stable
But my device is slow, maybe cpu of nook hd+ is weak
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
My HD+ also seems quite slow, especially as I load more apps on the 32GB internal card. My 7" HD has no issues with m10 nightlies, and is quite peppy.

danshane said:
My HD+ also seems quite slow, especially as I load more apps on the 32GB internal card. My 7" HD has no issues with m10 nightlies, and is quite peppy.
Click to expand...
Click to collapse
I had noticed an interesting sort of choppiness or hitching after first flashing M10 but it either has gone away or I'm now adjusted to it. It wasn't much to begin with but it was there. Otherwise, that was all.
My nook is ~138 apps during the cache configuration (art) upon first boot as the best number I can give for app load. Surely the more apps and the more background services running on the device the harder it will be for it to keep everything going as fast as possible. If your not on art, that might help (recovery backup first for safety + be aware of art's hunger for more internal storage).
Otherwise, its also possible to "out grow" the device and need something more powerful at the same screen size. If your needs change, the device may need to be changed. (Or similar). Too many apps and you could find yourself there.

sandsofmyst said:
If your not on art, that might help (recovery backup first for safety + be aware of art's hunger for more internal storage).
Otherwise, its also possible to "out grow" the device and need something more powerful at the same screen size. If your needs change, the device may need to be changed. (Or similar). Too many apps and you could find yourself there.
Click to expand...
Click to collapse
I tried ART with no improvement, so i am just going to experiment with a different build. My wife has an identical, fully loaded HD+ that zips right along on CM 10 with Jelly Bean, and my HD has no lag with KitKat, so I am not worried that the hardware will not handle the job. My son has an old Nook Tablet (pre-HD) that is really peppy on CM11 KitKat. I think all the Nook models are great for modding, and I am sure I will get this one performing as I like once I hit on the right combination.
** UPDATE ** I installed the latest Pac-Man ROM and I am now getting the performance I hoped for.

Installed M10. Did full wipe.
Was running a nightly from 03/2014 that was rock solid and fast (using ART).
All I can say to any one thinking of going to M10 is prepare to be disappointed. Its really laggy, even with other launchers, it looks terrible, the refresh rate/redraws/whatever are really obvious. Uncomfortably obvious. The screen sensitivity is really bad. Not responsive at all. I am looking forward to checking out the battery life over the next few days, because I have a sneaking suspicion it will deliver the trifecta of slower speeds, less responsive screen and worse battery life.
Trebuchet seems to be getting worse and worse. I wish Cyanogenmod would do a deal with one of the proper launchers and stop subjecting us to the substandard experience that is Trebuchet.
Oh yeah, and to top it all, the HD+ will no longer turn off. Selecting power off in the power menu just reboots the device. I now have to reboot into recovery and power off from there.
I am really disappointed. After all that effort backing up, wiping and reinstalling everything and actually took several (so many!) steps backwards.

gandalf_grey91 said:
Installed M10. Did full wipe.
Was running a nightly from 03/2014 that was rock solid and fast (using ART).
All I can say to any one thinking of going to M10 is prepare to be disappointed. Its really laggy, even with other launchers, it looks terrible, the refresh rate/redraws/whatever are really obvious. Uncomfortably obvious. The screen sensitivity is really bad. Not responsive at all. I am looking forward to checking out the battery life over the next few days, because I have a sneaking suspicion it will deliver the trifecta of slower speeds, less responsive screen and worse battery life.
Trebuchet seems to be getting worse and worse. I wish Cyanogenmod would do a deal with one of the proper launchers and stop subjecting us to the substandard experience that is Trebuchet.
Oh yeah, and to top it all, the HD+ will no longer turn off. Selecting power off in the power menu just reboots the device. I now have to reboot into recovery and power off from there.
...
Click to expand...
Click to collapse
I upgraded to M10 from M9 and so far had none of the issues you described. The only and somewhat minor problem is ~25% of Playstore app updates would abort on first try.
FWIW I use the Nova launcher and love it.

digixmax said:
I upgraded to M10 from M9 and so far had none of the issues you described. The only and somewhat minor problem is ~25% of Playstore app updates would abort on first try.
FWIW I use the Nova launcher and love it.
Click to expand...
Click to collapse
I can only report the facts, I was expecting a different experience from M10. Generally, I also choose to use Nova but on M10 it is suddenly jerky, jagged and uncomfortably laggy.
I believe the Play store issue is a google issue, which seems to come and go as they update Play store app. For me, it started in March of this year, was fixed later on and then came back a couple of months later, only to disappear a few weeks later..

Update: the Power Off = Reboot issue cleared up after 3 reboots/power offs. Its now working properly.