When I hit the power button to shut the screen off, it flashes brightly before it goes off.
Wondering if this is a Nook Color thing in general, or just a CM7 thing. Is this related to the fact that the screen animation doesn't work on CM7 when using the current kernel? I heard that Dalingrin had the screen animation working in the early test kernel and wondered if this got rid of the screen flash as well.
FWIW, mine flashes also. I haven't researched the cause, though.
CM7.0.2 from SD, when I tap the power button, it fades over about half a second. No flash, although occasionally there's a flicker in the middle of the fade. Power on happens much quicker, but there is a bit of fade-in.
I did enable on and off animations, even though I didn't think they were supposed to work yet.
this is a CM7 thing. its a power off and on animation. if you dont like it you can turn it off in settings. personally i like it. it reminds me of the old CRT screens.
boxcar8028 said:
this is a CM7 thing. its a power off and on animation. if you dont like it you can turn it off in settings. personally i like it. it reminds me of the old CRT screens.
Click to expand...
Click to collapse
More specifically it's a 2.3 thing - but I think the problem is that it doesn't work the same as on other standard resolution screens so it just ends up 'flashing' rather than doing a fancy animation. Your solution is correct though.
Interesting. The on/off animations are off by default in the Encore build. I enabled them in the settings and still had the flash (as one would expect). However, once I disabled them again everything was fine. I wonder if this is another persistence bug, similar to airplane mode?
My screen flashes whether the screen animations are on or off, though to be fair it doesn't flash every time, definitely more often than not though.
Mine is more of a quick blink rather than an obvious flash. And it isn't consistent.
My screen flashes as well. It just started doing this yesterday and I've been running cm7 off my sd card for about a week with no other problems. Worse, sometimes the screen turns green and stays that way until I hit the N button. Any idea what this means and possibly how to fix it? Any input would be greatly appreciated. Thanks.
FairJuno said:
My screen flashes as well. It just started doing this yesterday and I've been running cm7 off my sd card for about a week with no other problems. Worse, sometimes the screen turns green and stays that way until I hit the N button. Any idea what this means and possibly how to fix it? Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Which version of CM7 are you running? I haven't seen the flash or the green screen since I switched from 7.0.2 to nightly 86. Maybe it's coincidence, but it looks like the flash issue has been fixed.
(The power button does sometimes turn off the screen briefly then turn it right back on again -- hitting the power button a second time always turns it off.)
akaCat said:
Which version of CM7 are you running? I haven't seen the flash or the green screen since I switched from 7.0.2 to nightly 86. Maybe it's coincidence, but it looks like the flash issue has been fixed.
(The power button does sometimes turn off the screen briefly then turn it right back on again -- hitting the power button a second time always turns it off.)
Click to expand...
Click to collapse
It's the CM7.0.3 stable version. Maybe I should do an update. I wasn't sure if that was the problem since it had just started doing this. Are you saying you've seen the green screen? Just curious because I can't find anything about it anywhere. Thank you for your response. I'm going to try out the nightly and see if that fixes the problem.
Mine does more of a quick flicker,i think its the screen off/on animation issue on the nook because the animation works fine on my droid incredible cm7
GreenXSniper said:
Mine does more of a quick flicker,i think its the screen off/on animation issue on the nook because the animation works fine on my droid incredible cm7
Click to expand...
Click to collapse
Actually, that's what mine does too. Sometimes there's a flash, but most of the time it's a quick flicker. If it's just the animation then I probably don't need to worry about it. It's just the green screen that worried me...though that only occurred when I kept messing with it. I haven't messed with it the past couple of days so I haven't seen the green screen. Maybe I was causing some kind of error.
FairJuno said:
It's the CM7.0.3 stable version. Maybe I should do an update. I wasn't sure if that was the problem since it had just started doing this. Are you saying you've seen the green screen? Just curious because I can't find anything about it anywhere. Thank you for your response. I'm going to try out the nightly and see if that fixes the problem.
Click to expand...
Click to collapse
Yup, I've seen the green screen. I don't remember what build I was on at the time because I looked at a bunch over a couple of days. It could have been 7.0.3.
Or maybe I messed up something on my nook, and flashing another build corrected it? Either way, I haven't seen it in a few weeks.
akaCat said:
Yup, I've seen the green screen. I don't remember what build I was on at the time because I looked at a bunch over a couple of days. It could have been 7.0.3.
Or maybe I messed up something on my nook, and flashing another build corrected it? Either way, I haven't seen it in a few weeks.
Click to expand...
Click to collapse
That's good that you haven't seen it in a while. And not that I want anyone else to suffer, but I'm glad I wasn't the only one. LOL. Hopefully that means I'll have an easy fix. I haven't seen it in a few days myself, so I'm just going to wait and see what happens. Most likely I'll update to a nightly. Thanks for the responses. Now I'm not worried about it anymore.
Related
so here are my specs:
Cyanogen's 3.4 and his 1.2 recovery rom.
H's SPL and the newest radio.
Hero 1.2 theme.
So the problem I've been running into lately (which is the past few days) is that my screen just shuts off all of the sudden.
Like as I'm scrolling and reading news from the USA Today app, the screen shuts off and goes blank as if it was locking the screen.
I press menu of course to wake up my screen/phone and my phone seem normal.
This also happens when I get a notification for an email then click it and instead of it opening my gmail, the screen goes blank like mentioned above.
And when i press menu to wake it up, the screen that my phone is on is the gmail app.
Another instance is when I'm twitdroid and want to click a twitpic link to see a pic, it goes blank again. When I wake it up, it's at the twitpic page in the browser.
It's so odd to me because I'm physically using the touchscreen and then my screen goes to sleep. Before it happened my once in awhile, now it's more consistent... and getting rather annoying.
I've also been getting more lag during transitions.
Anyone else run into this? Know of any fix or why this happens?
Is it the theme? Transitions?
thank in advance
It might help to post a log from around the time the undesired backlight/screen shutting off is occurring.
jashsu said:
It might help to post a log from around the time the undesired backlight/screen shutting off is occurring.
Click to expand...
Click to collapse
oh good idea haha
i'll try to post one up if i'm ever near a comp when this happens.
Have you tried to reflash your current ROM? Wipe? Try a different ROM?
These are basic troubleshooting steps you should attempt before creating a new thread.
breaultm said:
Have you tried to reflash your current ROM? Wipe? Try a different ROM?
These are basic troubleshooting steps you should attempt before creating a new thread.
Click to expand...
Click to collapse
umm how do you know if i did or did not wipe and re-flashed my current rom and/or tried to do basic troubleshooting before making this thread?
anywho... my OP was a legitimate question and for good reason
thanks for trying to help though
i've been having these problems too. for the screen backlight problem, i just rebooted and it seems to work fine now. but the lagging is quite annoying at times, especially the gmail app.
mile7985 said:
i've been having these problems too. for the screen backlight problem, i just rebooted and it seems to work fine now. but the lagging is quite annoying at times, especially the gmail app.
Click to expand...
Click to collapse
ohhh so it's a backlight problem. ahhhhhh ic ic
mrcrs said:
ohhh so it's a backlight problem. ahhhhhh ic ic
Click to expand...
Click to collapse
well that's what i'm assuming because when it happens to me, i see it dim first, then shut off.
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
I think many of you are misinterpreting the "Random Reboots" you're experiencing. Unless the screen goes completely blank, then it is not a true reboot, if all it does is flash back to boot animation it is just the graphical shell crashing.
Good point, I did notice that it booted up significantly faster than a full reboot when it happened to me before and that it only dropped to the boot animation.
That makes a lot of sense actually
Sent from my MB860 using XDA App
Thanks for the suggestion - that does make some sense. Is there a way to verify this, though? In my case, my DInc will be in a stand on my desk - screen off, so I can't actually see what happens - when I'll hear it vibrate, and I'll notice the white HTC screen followed by the boot animation. It's only done this since I rooted, and it has done it with at least three of the ROMs I've used.
CaptBananaPants said:
Thanks for the suggestion - that does make some sense. Is there a way to verify this, though? In my case, my DInc will be in a stand on my desk - screen off, so I can't actually see what happens - when I'll hear it vibrate, and I'll notice the white HTC screen followed by the boot animation. It's only done this since I rooted, and it has done it with at least three of the ROMs I've used.
Click to expand...
Click to collapse
Yeah, same deal. I have learned to do "real" reboots, especially after rooting. What I mean is actually turning it off, counting to like 20 (maybe pull the battery), and then turn it back on.
Recently I had an issue with the capacitive buttons not lighting up at all so I tried a "quick" reboot (the kind that requires root) and it did nothing, then I tried a "real" reboot and they work fine now.
Agreed. I can confirm the Atrix is not doing a full reboot. I had a call on speaker phone then all of a sudden my screen showed the boot animation and I could hear the other person talking for an additional 15-20 sec while the phone finished "booting". Our conversation was not ended until the home screen came back up, at this point my bars/service dropped to no service. Also, I have not rooted or modified the Atrix, its stock.. w/LauncherPro+.
WiredPirate said:
Agreed. I can confirm the Atrix is not doing a full reboot. I had a call on speaker phone then all of a sudden my screen showed the boot animation and I could hear the other person talking for an additional 15-20 sec while the phone finished "booting". Our conversation was not ended until the home screen came back up, at this point my bars/service dropped to no service. Also, I have not rooted or modified the Atrix, its stock.. w/LauncherPro+.
Click to expand...
Click to collapse
I had those "reboots" twice now. Once while using Maps and once while sitting on my desk not being used. I was also using LauncherPro+. I wonder if that might have been part of it. I stopped using LP+ and haven't had a "reboot" yet (knock on wood)
I have been running CM7 on my Nook Color successfully for about 6 months now, but there is an ongoing issue that drives me nuts. Any help is appreciated. The problem is that, occasionally (about 4-5 times a week), the Nook will go to screen timeout and then not be able to come back out with any combination of buttons. The "n" button, power button, volume buttons, etc. all have absolutely no effect whether you press and release or hold down. The only way to get things back is to hold down the power button for 8-10 seconds and release...then hold the power button down again until the screen flashes and the green Cyanogen logo comes up. This, to me, is forcing it to shut down and then rebooting, though I can't see what's going on onscreen until the reboot. Then it will boot normally and work like normal......until the next blackout.
This happens even if the battery meter is fully charged, mid-way, or getting low...makes no difference. It will also happen no matter what the screen was when it timed out (home screen, app screen, etc.). Any ideas?
emopdx34 said:
I have been running CM7 on my Nook Color successfully for about 6 months now, but there is an ongoing issue that drives me nuts. Any help is appreciated. The problem is that, occasionally (about 4-5 times a week), the Nook will go to screen timeout and then not be able to come back out with any combination of buttons. The "n" button, power button, volume buttons, etc. all have absolutely no effect whether you press and release or hold down. The only way to get things back is to hold down the power button for 8-10 seconds and release...then hold the power button down again until the screen flashes and the green Cyanogen logo comes up. This, to me, is forcing it to shut down and then rebooting, though I can't see what's going on onscreen until the reboot. Then it will boot normally and work like normal......until the next blackout.
This happens even if the battery meter is fully charged, mid-way, or getting low...makes no difference. It will also happen no matter what the screen was when it timed out (home screen, app screen, etc.). Any ideas?
Click to expand...
Click to collapse
This is Sleep of Death (SOD). Well known issue. It happens when you have wifi set to stay on all the time. When the screen turns off and the nook goes into deep sleep, sometimes wifi and deep sleep get tangled up and you can't turn the screen back on. Only solution is to change your wifi setting or get a patched wifi module and flash that to your system. If you want a link to that patched file just ask and I will post it.
Edit: here it is:
http://d01.megashares.com/dl/8VPCE7N/wifi_SOD_patch.zip
Sent from my NookColor running ICS and Tapatalk
Thanks for the solution
I guess I wasn't using the magic keywords to find the problem online. Thank you so much for the solution and link.
@leapinlar: Do we know if that fix will work with mrg666's new kernel?
It still reports 2.6.32.9 in about tablet but I was under the impression that was because he was too tired to change it that night.
In my case I'm just happy to set wifi to turn off when the screen turns off, (I hate, hate, double hate, loath entirely when a device I've put to sleep trys to get my attention).
MISRy said:
@leapinlar: Do we know if that fix will work with mrg666's new kernel?
It still reports 2.6.32.9 in about tablet but I was under the impression that was because he was too tired to change it that night.
In my case I'm just happy to set wifi to turn off when the screen turns off, (I hate, hate, double hate, loath entirely when a device I've put to sleep trys to get my attention).
Click to expand...
Click to collapse
The patch only works on 2.6.32.9 kernels. I don't know anything about his new kernel. Just backup your existing twlan_drv.ko in /system/lib/module by renaming it .bak before flashing, and if it does not work restore your backup.
leapinlar said:
The patch only works on 2.6.32.9 kernels. I don't know anything about his new kernel. Just backup your existing twlan_drv.ko in /system/lib/module by renaming it .bak before flashing, and if it does not work restore your backup.
Click to expand...
Click to collapse
Yeah, I did that last night and didn't get an SOD but that really doesn't tell us much. I'll try to remember to take this over to his thread.
MISRy said:
Yeah, I did that last night and didn't get an SOD but that really doesn't tell us much. I'll try to remember to take this over to his thread.
Click to expand...
Click to collapse
Well, if you flashed it and wifi still works, it is compatible. On the CM9 kernel, it worked on .9 kernel until they updated to .59 and then if you used the patch, wifi quit working.
I just bought a A7+ and it will not always return from a black screen. I can resume it a couple times after it has gone into a hibernation mode, then it will just randomly not work. The green light will stay solid and I can't see anything on the screen and the buttons will not work.
I tried flashing with the lastest firmware, which installed perfectly. However this still doesn't fix the problem.
It's incredabily annoying, to be reading a web page, set the tablet down, try to turn it on and in the process lock it up.
Any ideas? Am I doing something ridiculous here?
chrisphotonic said:
I just bought a A7+ and it will not always return from a black screen. I can resume it a couple times after it has gone into a hibernation mode, then it will just randomly not work. The green light will stay solid and I can't see anything on the screen and the buttons will not work.
I tried flashing with the lastest firmware, which installed perfectly. However this still doesn't fix the problem.
It's incredabily annoying, to be reading a web page, set the tablet down, try to turn it on and in the process lock it up.
Any ideas? Am I doing something ridiculous here?
Click to expand...
Click to collapse
You are not the only one that has this problem. I have two that do the same thing. Did you ever find a solution?
nowell29 said:
You are not the only one that has this problem. I have two that do the same thing. Did you ever find a solution?
Click to expand...
Click to collapse
If you go to the manufactures site and download the newest update it will fix this problem. You won't be able to use custom roms, but it will make it work