For some reason my nook running CM7 stable off of sdcard becomes unresponsive for what seems no reason. It still functions just fine I see the background moving and still receive email but all buttons and touch screen stop working.
Has anyone else experienced this or know of a fix or anything I can do?
Sent from my Nexus S 4G using Tapatalk
Its called SoD. (Sleep of death) Common problem. Do a search and you will find many fixes. I use tasker to turn wifi on/off when screen is on/off.
---------------------------------
Sent from my LG Optimus V using Tapatalk
I thought SOD was when the device wont wake up. Mine seems to "freeze" while i'm using it but everything continues to function just no button or touchscreen response.
Are you overclocked/undervolted? What are your settings?
Sent from my NookColor using Tapatalk
Its just straight up CM7 have not changed anything.
Sent from my Nexus S 4G using Tapatalk
Related
A new problem appeared on my NexusOne FRF91 - when using N1 as a WiFi hotspot for a while my display gets sometime frozen - I can switch phone on via a button, I can see a display but display doesn't react on any touch. I haven't noticed anything like this on FRF83 or FRF50. Anybody else with similar experience? Any idea about workaround, pls?
Thanks, Pavel
Sent from my Nexus One using XDA App
Well I've been running gingervolt on my phone and it has been running fine until now. Today my softkeys won't light up anymore unless I go to settings and click on the screen brightness that's when they come on but once it times out and goes black they won't come back on when I unlock it. Also when I received a call and slide the screen up for some reason I can't hear anything and the phone hangs up. Does anyone know what can I do to fix this issue? Thanks. Version 2.3.4 running gingervolt 1.3
Sent from my VS910 4G using XDA App
robledjl said:
Well I've been running gingervolt on my phone and it has been running fine until now. Today my softkeys won't light up anymore unless I go to settings and click on the screen brightness that's when they come on but once it times out and goes black they won't come back on when I unlock it. Also when I received a call and slide the screen up for some reason I can't hear anything and the phone hangs up. Does anyone know what can I do to fix this issue? Thanks. Version 2.3.4 running gingervolt 1.3
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
This happened to me the first night gv 1.3 was released. It went away the next day though. Re-flash?
Ok. I will reflash and hopefully that would fix it
Sent from my AT100 using Tapatalk
This happens on my phone once in a while. I just open up adjbrightness and problem solved.
Sent from my VS910 4G using XDA App
This will sound weird but what I do when this happens (usually a restart of device) is bring the phone's screen to my laptop screen momentarily, or just hit it with a beam of light from my 700 lumen flashlight It's quick and easy
adrenaline_rush said:
This will sound weird but what I do when this happens (usually a restart of device) is bring the phone's screen to my laptop screen momentarily, or just hit it with a beam of light from my 700 lumen flashlight It's quick and easy
Click to expand...
Click to collapse
haha, very MacGyver...Going into Settings > Display and toggling auto brightness on/off would probably accomplish the same thing.
jamrwoo said:
haha, very macgyver...going into settings > display and toggling auto brightness on/off would probably accomplish the same thing. :d
Click to expand...
Click to collapse
no it won't jamrwoo !!!!!!
Alright guys I reflashed it And it fixed the soft key issues but im still having problems answering the phone. When I slide it up to answer i can't hear anything... Timer keeps going but I have to hang up and call them back... Sometimes it just hangs up when I try answering. Does anyone have any other suggestions? Thanks a lot for reading my post.
Sent from my AT100 using Tapatalk
robledjl said:
Alright guys I reflashed it And it fixed the soft key issues but im still having problems answering the phone. When I slide it up to answer i can't hear anything... Timer keeps going but I have to hang up and call them back... Sometimes it just hangs up when I try answering. Does anyone have any other suggestions? Thanks a lot for reading my post.
Sent from my AT100 using Tapatalk
Click to expand...
Click to collapse
With everything that you've tried, it's starting to sound like it might be a hardware issue. If that's the case, you might have to send it in to get it fixed.
So should i restore to stock and see if that fixes the problem? I guess either way I need to restore to stock if I need to send it off to get fixed right?
Sent from my AT100 using Tapatalk
robledjl said:
So should i restore to stock and see if that fixes the problem? I guess either way I need to restore to stock if I need to send it off to get fixed right?
Sent from my AT100 using Tapatalk
Click to expand...
Click to collapse
Couldn't hurt. I would do it if nothing else has worked.
Sent from my VS910 4G using Tapatalk
The screen changes - a cream tinit that goes on and off every few seconds. Most noticeable on white screens eg Google Reader. Does anyone else have this, and how do I fix it!!! It's so winding me up and lets down an otherwise amazing screen and device.
Try turning off automatic brightness (settings, screen) and test if issue is still there.
Sent from my GT-N7000 using Tapatalk 2
99% certain its the automatic brightness being set on...just untick the box in the display section of settings, that should also disable the tinting effect when your on Google and internet sites
Sent from my GT-N7000 using XDA
Go to Settings>Display>and on the bottom you will see "Auto adjust screen power" turn that off and you wont get the cream tint
The power settings seem to be the culprit. So far, it seems much better. I'll report back if it reverts back to disco lights.
I'd recommend to update your phone if you havent done so yet. Check if same issues arise if they do, and you eally want the setting maybe send the unit back?
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
I'd recommend to update your phone if you havent done so yet. Check if same issues arise if they do, and you eally want the setting maybe send the unit back?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'm using midnote 3.4, but it did the same on gingerbread too.
anybody know what app to use to light up the lower buttons when receiving a notification
Sent from my LG-P880
There's an app called no led but as we've discovered, it prevents the fone from entering deep sleep and hammers the battery
Sent from my LT26i using Tapatalk 2
any others
Sent from my LG-P880
It has been investigated here, but with limited success.
I use the linked one since it came out here without any problems. Works fine for me. It's a bit tricky to set up, but once done, it's great.
During calls screen goes black and cannot activate dialpad or hang up. CM 7.2 Any insight appreciated. Otherwise phone is perfect. Doesn't matter how I set proximity setting. Stays lit if I use speaker on.
Sent from my Nexus One using Tapatalk 2
bangwhiz said:
During calls screen goes black and cannot activate dialpad or hang up. CM 7.2 Any insight appreciated. Otherwise phone is perfect. Doesn't matter how I set proximity setting. Stays lit if I use speaker on.
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I recall I had this problem too when using CM 7.2. Try to use different kernel and making sure your max setting for the CPU is not too high. 998Mhtz is enough.
I clicked the thanks button but wanted to add that I removed my Setcpu app which was set for on demand between highest and lowest settings. It works fine on my Nook Color which is wifi only running 7.2 Stable with no calling capability. When I uninstalled Setcpu app from Nexus problem disappeared.
Sent from my Nexus One using Tapatalk 2
I had something like this, but the cause was a fullbody case which blocked the prox. sensor.
Hope this help ppl finding this topic and dont have a configuration issue.
I will remove my case and check it out.
Sent from my NookColor using Tapatalk 2
i had got the same problem but i had offical stock 2.3.6 for my nexus one. Yesterday, i flashed my nexus one with CM10, and now ,i don't have such an annoying problem "until now". I will re-type in 2 or 3 days if i got a problem again.
I went back to 7.1 from 7.2 and have no more problems. I have setcpu running Max speed on demand and no issues with it either. I could not stop the problem using 7.2
Sent from my NookColor using Tapatalk 2