Database Develop

Nook Color randomly hangs

Having a major issue here with my NC. Running CM 7.1 and I'm getting random hangups during normal use. The touchscreen becomes completely unresponsive, and I can't turn the display on or off. If I'm listening to music, however, the music continues to play. The only way to fix it is to reboot the NC. Has anyone heard of this and can offer me a fix?
Thanks in advance
oriz

Is it an SD card install? If so what is the brand of your card.
---------------------------------
Sent from my LG Optimus V using Tapatalk

Yes, I had the exact same problem with a new install on emmc, and uninstalling Beautiful Widgets on the advice of another thread I found here completely solved the problem. I had forgotten that BW did the same thing to my Incredible when I tried it a long time ago. If you don't have BW installed then take this as a warning not too

Very interesting...
I've had the exact same problem myself for awhile now, and couldn't figure out the cause. I even wiped the Nook and reflashed CM7.1, but the problem still popped up once and awhile.
I'm also using Beautiful Widgets. I think we have a pattern developing here. Can the OP confirm/deny he has BW installed?

Beautiful Widgets messed me up too...hung the hell out of my nook color. They even know of the issue and did nothing about it. Got it on Amazon as a paid app.

[Q] Phone Unresponsiveness

Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.

Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10¢ apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk

I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium

I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.

What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App

revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.

I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.

Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.

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] Tried Everything - Touchpad Screen Unresponsive (CM9)

Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6

flash the latest nightly.

screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks

the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.

Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system

Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...

Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.

Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )

i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA

Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed

This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?

I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2

Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app

I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?

I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2

I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.

Bump - still no fix identified for this by anyone with this issue please?

To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android

Reboot when TouchPad goes to sleep in Homescreen

This is a common problem since the very beginning. The only way to stop it from occuring is if I leave it on Browser and put it to sleep.
I just installed the latest CM9 and the problem still occurs.
Is there anyway to fix it?

Sepharite said:
This is a common problem since the very beginning. The only way to stop it from occuring is if I leave it on Browser and put it to sleep.
I just installed the latest CM9 and the problem still occurs.
Is there anyway to fix it?
Click to expand...
Click to collapse
After the first time you get it to sleep without rebooting, you can turn off the screen at any point without a problem, right?

Try raising up the minimum clock speed to 384 and see what happens.

Minimum cpu was already raised. I changed the schedule to deadline,let's see if this works.
Sent from my GT-I9100 using Tapatalk 2

Caches were cleaed upon installing the latest nightly? Used to have that problem with some of the very first nightlies, TP would reboot upon turning off the screen, clearing caches fixed that.

I have the same, or similar problem
allstar319 said:
Caches were cleaed upon installing the latest nightly? Used to have that problem with some of the very first nightlies, TP would reboot upon turning off the screen, clearing caches fixed that.
Click to expand...
Click to collapse
I have the same, or similar problem but unfortunately have not found a fix after trying every possible remedy from clearing the cache and upping the min frequency to a complete uninstall with acmeuninstaller . Clearing the cache may fix it for a small amount of time but it always seems to come back. I tried upgrading with both goo and with CWM thinking one may be missing something but both have the same results.
I managed to trace the problem to wifi turning off when sleeping for me. If i set wifi to stay on during sleep it does not happen, if I use a widget to go into airplane mode on sleep it does not happen but if i set wifi to turn off during sleep it happens. It may take a day or two to manifest but it always seems to come back.
I finally ended up using the 7/7 nightly because it doesn't do it and i dont feel like finding the exact nightly that the bug manifested in. I know it was after 7/7 and prior to 8/9. It is a pain as the 7/7 has some lag not found in the later nightly but if the choice is lag or greater battery drain, I choose lag.
Anyway..... Sorry to jack your thread. I feel for you, the reboot on sleep make the TP unusable. If you do manage to find a fix because i still search the forums hoping to see something i haven't tried yet.

Making the cpu scheduler to Deadline fixed the problem so far.
Sent from my GT-I9100 using Tapatalk 2

same problem
hello guys,
I have the same reboot-problem. I tried almost anything...
@Sepharite
Is it still fixed with cpu scheduler to Deadline?
If yes, how did you do that?
I just installed the app "No-frills CPU Control" und turned the cpu scheduler to Deadline, but it still reboots.
I have only no reboots, when I'm using the touchpad after booting for a while.
Anyone has an idea?

esemudeo said:
hello guys,
I have the same reboot-problem. I tried almost anything...
@Sepharite
Is it still fixed with cpu scheduler to Deadline?
If yes, how did you do that?
I just installed the app "No-frills CPU Control" und turned the cpu scheduler to Deadline, but it still reboots.
I have only no reboots, when I'm using the touchpad after booting for a while.
Anyone has an idea?
Click to expand...
Click to collapse
I've had the same problem for months. At this point, we may have to live with it. I find that if you let the device time out of its own, about 80% of the time it won't reboot again. It definitely serves as a reminder that we aren't in stable build territory yet (though, some people apparently don't experience this).
Sent from my SCH-I535 using Tapatalk 2

Infinite Jest said:
I've had the same problem for months. At this point, we may have to live with it. I find that if you let the device time out of its own, about 80% of the time it won't reboot again. It definitely serves as a reminder that we aren't in stable build territory yet (though, some people apparently don't experience this).
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer. I have to ask, you don`t have this problem anymore?

esemudeo said:
Thanks for the answer. I have to ask, you don`t have this problem anymore?
Click to expand...
Click to collapse
No, I still have this issue. I just live with it and try to minimize rebooting (which in have to do every couple of days anyway, thanks to match some point all of my apps crashing a couple of times when I try to open them unless I reboot.)

hey guys, good news.
User Sohip wrote in another thread, he also had reboots, but after he disabled the lock screen it stopped rebooting.
So I disabled the lock screen, and it seems to work. You should try it.
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
oh, now I get reboots again
---------- Post added at 11:00 AM ---------- Previous post was at 10:27 AM ----------
By the way, just in case, somenone tries ot fix this reboot-problem.
When the touchpad goes to sleep, it makes a „click“-sound, and then it reboots.
At least my touchpad makes a „click“-sound.

I haven't had a lock screen for months and the problem has persisted.