Database Develop

[Q] Erratic Touchscreen Issues

No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.

have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk

Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.

angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?

dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!

angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.

bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.

I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.

I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.

I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.

queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!

Cm7 and random freezing

I'm running cm7.1 stable, running off emmc, and every now and then my beautiful NC just locks up, I have it OC to 1.2ghz, I did a search and only end up with results from older nightly threads. Is this a common issue or just me?
PS... I have reflashed and cleared, data,cache, etc..
Thanks
Sent from my NookColor using XDA

Have you always had the issue or did it start recently? I would look at uninstalling any new apps you downloaded prior to the issue starting. There is a good chance you might find a bad app to be your problem.

It wasnt happening before, I tried cm9 with opengl, after I reverted back to cm7(fresh install not nandroid) it started happening, the apps I am running were the same apps I was running before trying cm9(and the freezing problem wasn't happening)
Sent from my HTC Sensation 4G using XDA

Since you are going for a clean install anyway and there is no issue with the CM7 install script did you try the factory reset option or was it just the caches that you cleared? Have you confirmed that you have a good download of the CM7 zip?
Also you might want to try flashing your latest nandroid and make sure that is still running the same as when you created it. If so and you still want to install fresh try it coming off of that one instead of from CM9.
JP

I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.

511pf said:
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
Click to expand...
Click to collapse
I do have beautiful widgets installed, let me remove it and see if it helps
Sent from my HTC Sensation 4G using XDA

So did removing BW resolve the random freeze? My wife's NC is doing the exact same thing and she has BW too. But I just installed CM7 on hers last night so not sure if BW is the culprit or not yet.

I've been running CM 7.2.0 RC1 from SD card about a month now, and I've experienced a number of freezes. On April 5, I had two freezes within a few hours, and I started keeping track of the freezes, hoping a pattern would emerge.
From April 5 through April 17, there were a total of eight freezes. I don't know what the uptime was when the first freeze occurred on April 5, but all subsequent freezes occurred with less than two days uptime. During those 13 days, uptime got above two days on two occasions; both times a "Sleep of Death" occurred before uptime reached three days.
Was there a pattern? Yes! Every single freeze occurred while I was using Opera Mobile browser, and browsing these forums at forum.xda-developers.com.
On April 18 I started using Dolphin to browse the xda forums, and there has not been a single freeze so far. (I still use Opera Mobile for other browsing.) Uptime had reached five days when I voluntarily rebooted this morning.
I realize this may not be relevant to the rest of the discussion in this thread, which seems to deal with CM 7.1. Then again, maybe it is. This seemed the logical place to report the observation.
Update: Opera Mobile has updated to version 12.00.ADR-1204201824 on April 25. I'll revert to using Opera Mobile on the xda forums, to see if it still freezes.

My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.

threebeers said:
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
Click to expand...
Click to collapse
You really don't gain much and lose a lot by running apps installed to sd. Since everything is automatically on 'sd' with an sd install, those that say they are installed to phone are really still on sd (in /data, which is also on sd). The only reason to install apps to sdcard is if you have so many installed that you have no more room in /data. And with sd installs, usually the /data is made of a generous size. Installing apps to sd slows your system since it has more system overhead to work through.
I know it sounds confusing, but with sd installs, installing to phone means installed to /data which is a partition of your sd. If it says installed to sd, it means it is installed to sdcard, which is another partition of your sd. So no matter where you tell it, it is all on sd and /data is faster because of less system overhead.

For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!

pink401k said:
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
Click to expand...
Click to collapse
Came to post the same thing. My nook color will run max OC 1200 but often it will freeze for no reason. After many attempts of uninstalling the many different apps I thought were causing it I started moving the OC lower in small increments and running for a long as possible without a freeze. Finally got down to 975 and haven't had a freeze in days.
Kinda disappointed though since someone got it at 1600 and most run at 1200 and all I can get is less than 1000. I'm probably moving to a Asus Transformer Infinity soon anyways though.

It has been known since the early days of Dalingrin's overclocking kernels that many of the NC's have issues with anything above 1100 MHz and undervolting can create a great deal of instability.
My recommendations are to try 1100 MHz max... and lower voltage .05 mV at each step. I personally never have issues with these settings...
You can then try lowering voltage .05 mV at a time until you start having issues... then increase it back to the last one you had no issues with.
I just leave mine at 1100 and .05 mV lower than the reported "Stock Voltage"

[Q] Hd+ extremely suggish

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 ran into this, but seemed to be due to going under 3gb of storage. The HD+ does not seem to like going under that.

maybe uninstall some questionable apps
peeam said:
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
Click to expand...
Click to collapse
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.

cozumelstu said:
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.
Click to expand...
Click to collapse
Same, but for me it was my launcher (Apex). Try other ones out there.

I just saw lag on my swift key keyboard for the first time. I'm using apex too.

gunnyman said:
I just saw lag on my swift key keyboard for the first time. I'm using apex too.
Click to expand...
Click to collapse
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.

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

jamus28 said:
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
Click to expand...
Click to collapse
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?

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.

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.

jamus28 said:
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.
Click to expand...
Click to collapse
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.

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.

rushless said:
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.
Click to expand...
Click to collapse
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.

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.

rushless said:
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.
Click to expand...
Click to collapse
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.

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

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.

peeam said:
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
Click to expand...
Click to collapse
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.

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.

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.

Touch screen temporarily unresponsive

I had a similar problem(but worse) sometimes when using the stock rom.
I've replaced the stock rom and been using CM10.1 on emmc.
Sometimes when playing games the touch screen may become unresponsive but the 3 standard buttons still would work.
(as well as the hardware buttons.)
When this happens I'm not able to click on any of the icons on the home screen. (none of the control buttons work in game, either.)
I wonder if this is a hardware problem, CM10 problem, or a problem with the coding of the game (dungeon hunter 4.)
The problem actually does not last. Nook HD+ recovers by itself after about 1 minute.
Else, I could also click on the power button to turn off display and turn it back on.
Once it's back on everything is working including the in-game controls.
Does anyone have a similar problem?
I doubt this could be a bug in the game (Dungeon Hunter 4). The game is very buggy but when I play it on Nexus 7, I never experienced any control button issues. (Though it does crash "a lot" and sometimes more often than on the Nook HD+)

I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help

ndttung8487 said:
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
Click to expand...
Click to collapse
Thanks. I appreciate your help. I had this problem again today and I noticed the available ram was indeed quite low at the time.
Although it seemed unresponsive, it seemed more like being extremely slow.
Somehow if I turn off the display and turn it backs on it gets a bit better.
I suspect dungeon hunter 4 has a memory leaking problem. (memory not released completely if reload an area many times.)
I tend to have this problem if I load a lot of data in the game several times.
Strangely this does not occur on Nexus 7 based on the latest patch.
I searched in xda and it seemed last year Nexus 7 also had the same problem especially when playing certain games.

So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Here is his topic: http://forum.xda-developers.com/showthread.php?t=2263553

ndttung8487 said:
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Click to expand...
Click to collapse
Thanks. I deleted the game as it is very buggy, crashes often and with many in game bugs. I'm finally done with it.
If I encounter the same issue with other apps I'll definitely upload the log.

I had it on all roms
Hi,
No, you are not alone. The issue occurred on all roms I used so far.
Indeed it mostly shows up in games, though I think I noticed it in other apps too occasionally.
I usually use the power button, but I'll try clearing the memory in the future...
M.

[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.