Related
Hi All,
I've got my HD+ running CM10.1 using the emmc method (works great by the way, really smooth and responsive) but the device seems to be rebooting overnight when left plugged in and charging.
I used to get quite a few reboots with CM10.1 using the hydrib method as well (emmc seems far more stable for me).
Is there anyway of debugging what might be causing the reboots?
I just left chrome running last night so I could see if it had rebooted by the time I got up.
Thanks
Paul
BigMacca said:
Hi All,
I've got my HD+ running CM10.1 using the emmc method (works great by the way, really smooth and responsive) but the device seems to be rebooting overnight when left plugged in and charging.
I used to get quite a few reboots with CM10.1 using the hydrib method as well (emmc seems far more stable for me).
Is there anyway of debugging what might be causing the reboots?
I just left chrome running last night so I could see if it had rebooted by the time I got up.
Thanks
Paul
Click to expand...
Click to collapse
It is probably an installed app. I have no reboots. I would suspect chrome, which I don't have installed.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
It is probably an installed app. I have no reboots. I would suspect chrome, which I don't have installed.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the reply .
Is simply having the app installed enough to cause issues or does it actually have to be running?
BigMacca said:
Thanks for the reply .
Is simply having the app installed enough to cause issues or does it actually have to be running?
Click to expand...
Click to collapse
Some apps run services in the background even if not active at the moment. It may be one of those.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Some apps run services in the background even if not active at the moment. It may be one of those.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Cheers mate,
I've found where you can check to see what services are running, I'll start shutting things down and do a little trail and error over the next few nights to see if I can track down which app is the culprit
leapinlar said:
Some apps run services in the background even if not active at the moment. It may be one of those.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I still seem to be having reboots now and again (never whilst actually using the device though...)
It's no the end of the world as the only way I can tell the nook has rebooted is that there are no apps loaded when I go to use it, but I've not been able to track down what app / apps are causing it yet.
Is there any kind of debug logging I can get at / enable?
Cheers
Macca
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.
I've seen some info about Nook HD+ touchscreens having lag and unresponsiveness problems, but that was with an old version of the stock firmware and occasional bad microSD cards.
Has anyone had this problem with the current CM10.1 ROM?
I upgraded to CM10.1 over the weekend and I'm having all kinds of touchscreen problems since changing over. I frequently have to tap two or three times (the last time being very slow and deliberate - and a little more forceful because it is pissing me off) and sometimes have to hold a tap in place so that it will register.
If all else fails, I'm going to go back to stock, but I'd rather not. I'll probably try re-downloading and re-installing CM10.1.
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm doing this right now. I just got the N+ with the 06/15 emmc build. It certainly does not feel as smooth as the Nexus 7 around the Launcher and apps: it feels like the whole system is running at 20FPS(exception is Boat Browser, Youtube, and other minority apps). I'm still looking at this time hoping that the higher resolution isn't the limiting factor on the OMAP4 hardware.
leapinlar said:
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks Leapinlar! :good:
The post that is most meaningful in for this issue in that thread is #834:
http://forum.xda-developers.com/showpost.php?p=42645288&postcount=834
Where it points you to an app that seems to fix the problem - even if that fix is only temporary. Here's the app:
https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en
Tom2112 said:
Where it points you to an app that seems to fix the problem - even if that fix is only temporary. Here's the app:
https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en
Click to expand...
Click to collapse
This fix worked great for me as well. Is this a "permanent" fix in the sense that I only have to do it once? or will there be a need to do it again (e.g., after reboot?
Thanks
That's useful to know about the recalibrate app, I may use in the future.
This is a bit obvious but I've found a good clean of the screen helps.
srgibbs99 said:
This fix worked great for me as well. Is this a "permanent" fix in the sense that I only have to do it once? or will there be a need to do it again (e.g., after reboot?
Thanks
Click to expand...
Click to collapse
I think it is something that will need to be repeated. The gurus over in the other thread imply that it is something that degrades over time.
Also, as mdwsmith suggests, it is helpful to keep the screen clean. The Nook HD+ seems very susceptible to greasy fingerprints messing with the touch sensitivity - more so than any other tablet/phone I've used.
Tom2112 said:
I think it is something that will need to be repeated. The gurus over in the other thread imply that it is something that degrades over time.
Also, as mdwsmith suggests, it is helpful to keep the screen clean. The Nook HD+ seems very susceptible to greasy fingerprints messing with the touch sensitivity - more so than any other tablet/phone I've used.
Click to expand...
Click to collapse
Thanks Tom, i have noticed that having fingers/screen very clean helps.
Open up the developer options in settings and enable "Show touches" and "pointed location." Use the device with these options on to see a trace of how the touchscreen registers your touches. You start to get an idea of how sensitive the touchscreen is. You can also clearly see why some touches don't register sometimes. I touched the screen to click a button but it thinks I want to scroll because the trace shows I made the slightest of a line when I pushed down on the screen.
Sent from my Barnes & Noble Nook HD+ using Tapatalk HD
I installed a matte/non-reflective screen protector on my Nook HD+ because I had read elsewhere that it would help the touch sensitivity issues.
It didn't. So I will probably remove it.
verygreen has a thread up with a zip you can flash that did wonders for my touch screen. check it out
bckrupps said:
verygreen has a thread up with a zip you can flash that did wonders for my touch screen. check it out
Click to expand...
Click to collapse
Thanks! I will check it out.
Here's a link for those that find this thread first:
http://forum.xda-developers.com/showthread.php?t=2347003
I found on my Nook HD+ that when the touchscreen starts acting wonky like this it wants to be cleaned. *Especially* ( and sometimes only ) where the glass meets the bezel. I wrap the cleaning cloth around my finger and angle my nail in at about 45 degrees, and gently but firmly 'scrub' around the bezel edge. I can actually feel a buildup there physically from the varying friction of my movement. After that is starts acting like it did ootb.
Tom2112 said:
I've seen some info about Nook HD+ touchscreens having lag and unresponsiveness problems, but that was with an old version of the stock firmware and occasional bad microSD cards.
Has anyone had this problem with the current CM10.1 ROM?
I upgraded to CM10.1 over the weekend and I'm having all kinds of touchscreen problems since changing over. I frequently have to tap two or three times (the last time being very slow and deliberate - and a little more forceful because it is pissing me off) and sometimes have to hold a tap in place so that it will register.
If all else fails, I'm going to go back to stock, but I'd rather not. I'll probably try re-downloading and re-installing CM10.1.
Click to expand...
Click to collapse
I'm on CM10.1 too and faced the same tapping lag - third time is very slow. I lost almost 40 hours of testing, testing and more testing of this nasty lag and there is no result for now, maybe it's some option in the phone that eliminates the lag but I can't find it for 40 hours... But I'm sure for one thing - if the slow tap is ALWAYS the third time, then the reason is some setting. There is nothing in your hardware/performance, be sure about that. Just searching for solution......
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?
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.