I just rooted the Nook Color with Auto Nooter 3.0. It was all working perfectly for the first few hours, then screen just turn unresponsive from time to time. had to try so many times to get the unlock screen to unlock. and while typing, it just hits random keys that I wasn't even close to be touching. It's like the screen is sensing the touch in the wrong spots.
Anyone ever experience this? anything I can do to fix this?
Thanks!
Clean the screen and see if that doesn't fix it.
We seem to have a lot of screen issues in the last few days.
Try recalibrating your screen if cleaning doesn't work.
Unplug it from the charger if it is plugged in.
Sent from my PC36100 using Tapatalk
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
lancorp said:
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
Click to expand...
Click to collapse
I have heard about this problem from several people, but usually it is on an HD+ with the cover that wakes up the tablet. However, I just experienced this a few minutes ago and my Nook has never had a case on it, let alone one that wakes it.
It happened when waking it with the n button but after turning off the screen with the power button and back on with the power button, it worked. (not turning off the Nook, just screen off and back on)
So it appears that it is not only the magnetic wake up that causes the issue.
Sent from my nook HD+ running cm10.1 on emmc from Tapatalk HD
Mine does that too. I thought it was a hardware defect, but I tried another one and it does exactly the same thing.
So far it's only happened with a case-induced wake for me. It happens regardless of whether I sleep it using the case or the power switch.
The lockscreen loop stops if I sleep/wake it using the cover consistently, but it doesn't go away if I sleep/wake it using the power switch, oddly.
same problem with no known solution
lancorp said:
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
Click to expand...
Click to collapse
I have the same problem and no solution. I wonder if a newer release of CM would help.
Also, in regards to temporary coping, when this problem appears is there a method (besides reset) to deal with the problem. I noticed that sometimes I can eventually get past the lockscreen without restarting, but I'm not sure what causes that. The best solution I have for my wife at this point is I delayed locking-after-sleep to 30 minutes.
Two-user set-up (my wife and me). I am fairly new to the scene--first time I ever loaded CM on any device. I recently bought the HD+ from Best Buy for $150. I tried to follow the verbatim instructions from e.mote titled "[NOOK HD/HD+] Installing CyanogenMod 10.1 for Dummies." I haven't used custom ROMs much since my heady days with my Palm Pre.
I'm in the same boat. Hd+ running CM 10.1.3. I wonder if this still happens on the 10.2 builds...
While on 10.1 this happened to me every time after charging (well, maybe not every time, but that's when it happened...), but if I just turned off screen and then back on I was fine until next charging.
I put on 10.2 earlier today (from Iamafanof site, so not from here). Will be interesting to see if the problem is till there, but I won't know tat for a while yet.
Nook HD problems waking up
asawi said:
While on 10.1 this happened to me every time after charging (well, maybe not every time, but that's when it happened...), but if I just turned off screen and then back on I was fine until next charging.
I put on 10.2 earlier today (from Iamafanof site, so not from here). Will be interesting to see if the problem is till there, but I won't know tat for a while yet.
Click to expand...
Click to collapse
Im seeing this on both 10.1 and 10.2 on my nook HD no cover.
I'm seeing this even without a lock screen. The screen turns on for a second, after that turns off. After many tries it works or after a restart. With lock screen it is the same as above.
Happend on CM 10.1 and CM 10.2 with a cover
So there's no solution to this problem and you just have to reboot it?
You just close and open the cover again
Sent from my rooted GS3 running CM11
oboefiend said:
You just close and open the cover again
Sent from my rooted GS3 running CM11
Click to expand...
Click to collapse
I'll try that again but I don't think it worked.
I have been having the same issue as well with mine. Just curious if really has been a solution to this?
No it is a hardware issue. There are two options close and reopen cover or cut magnets out and turn on manually. I don't think anyone has tried more powerful magnets if you want to test that it would be helpful.
Sent from my SPH-L900 using XDA Free mobile app
I kinow its an old thread, but I Fixed it by closing and opening the magnetic cover, rather than using the power/off/on screen button and it worked.
Only fix is to do one of three things. Remove the magnet from the cover, remove the cover is self, disable the lock screen. It's because the cover and lock screen confuse each other and it has the cover wake it, then the lock screen sleep it, then it sticks. It's very well known, and nothing to panic over, just really freaking annoying.
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Probably software issue.
If your using a magnetic case (problem)
You could try disabling the lockscreen if its enabled.
Daydream could in my theory affect that time frame.
The backlight should last years longer. The gpu should as well. I can't think of any other hardware issue.
If you have an sdcard try cm11 [or the bn rom] and see what happens. OR full backup of current rom in cwm and flash cm11 to internal. Clean and restore 10.1.3 and be back to right where you left off.
lmacmil said:
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Click to expand...
Click to collapse
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case but it happens without it. Before this happen, my slide to unlock screen would act up by not unlocking when I slide to unlock; it would just go back to the initial lock screen. Slide to unlock would not work so I turn off the lockscreen, now experiencing blackout screens when I try to wake it up by pressing either buttons. This problem happens infrequently but it is annoying.
kinvid said:
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case...
Click to expand...
Click to collapse
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
lmacmil said:
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Works like this on my HD+, too. Sometimes requires opening case cover twice, but the screen always comes on.
anyone have their nook hd + start acting like it haunted? while reading a book pages turn back and forth by itself. watching a youtube video and it starts doing its own thing. entering and exiting apps???
the screen also started doin some weird pixellating thing.
hydro6773 said:
the screen also started doin some weird pixellating thing.
Click to expand...
Click to collapse
I have had the screen do odd things from time to time but I have never seen "some weird pixellating thing".
did you do anything to fix it?
hydro6773 said:
did you do anything to fix it?
Click to expand...
Click to collapse
Did you try cleaning your fingerprints off?
Sent from my SCH-i705 using XDA Premium HD app
yes i cleaned the screen off and all my finger prints. I was doing some reading and some people say that they had the same problem and they said something about holding the power button for 20 seconds and then holing it for 2 seconds to turn it on. I tried that but it still eventually did the same thing. I also read some people said that once they put a screen protector on it seemed to help. What do you think?? Have you had this problem at all. I cant return it to B & N since its rooted and was purchased off craigslst. Is this a known issue?
When mine gets weird and I get phantom finger presses just shutting the screen off and turning it back on fixes it. Usually happens after long game sessions.
Sent from my SPH-L900 using XDA Free mobile app
This is the only problem I have with my nook HD+, but I am getting close to finding the problem.
I have managed to get dmesg to print out when the problem is occurring, and that isn't easy when it wants to start doing random presses !
Every time this problem occurs I see the same thing:
lowmemorykiller: killing 'ndroid.settings' adj 1000 to free 19712KB on behalf of 'kswapd0' because cache 85116KB is below limit 86016KB for oom_score_adj 12
free memory is 5568KB above reserved
When the crazy screen presses start happening lowmemorykiller begins closing all sorts of things one immediately after another, and then crashes out with a negative memory available like :
-58329KB available
I'm guessing there is a memory leak somewhere.
I've been getting phantom touches since upgrading to CM 11 (6/16 build and up), although I left the Touch & Hold delay to its stock "short" setting when I upgraded, so not a good experiment. (Two variables.)
For me, a web page will register a "click" while browsing with my thumb hovering about an inch over the screen.
I have "show touches" enabled, but I don't see a touch.
I have a screen protector. (Have had it for months.)
For now, I'm setting the Touch & Hold delay to Medium as a work around.
I have the same problem as others that sometimes after sleeping with the magnetic cover, even with the correct password I could not log in. I have delayed the screen automatic lock to 30 min and usually have to fix it with a restart if it happens.
I have another problem that if I have the nook covered with the magnetic cover for a time period longer than 2 hours. It seems to have been turned off. I have to try holding the power button to turn it back on and it will go through the nook splash screen and then the cyanogenmod start animations. Is this something expected with cyanogenmod? Has anyone else experienced this?
If it's a bug, I am wondering whether updating to CM 10.2.1 will fix it. I have read the first problem cannot be fixed and it might be hardware related. Is the second problem hardware related too? Thanks,
loveleo said:
I have the same problem as others that sometimes after sleeping with the magnetic cover, even with the correct password I could not log in. I have delayed the screen automatic lock to 30 min and usually have to fix it with a restart if it happens.
I have another problem that if I have the nook covered with the magnetic cover for a time period longer than 2 hours. It seems to have been turned off. I have to try holding the power button to turn it back on and it will go through the nook splash screen and then the cyanogenmod start animations. Is this something expected with cyanogenmod? Has anyone else experienced this?
If it's a bug, I am wondering whether updating to CM 10.2.1 will fix it. I have read the first problem cannot be fixed and it might be hardware related. Is the second problem hardware related too? Thanks,
Click to expand...
Click to collapse
You need to open and close the cover twice. It is a known bug on all CM versions.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You need to open and close the cover twice. It is a known bug on all CM versions.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Hum, I can't seem to reproduce my second problem for the last two days. The symptom was that when I tried to press the nook button or the power button to wake it up, nothing happens, it stayed at the black screen. I guess basically what I did was holding the power button to shut it off and then turn back on. I guess it might have needed a second time of opening the cover. I will keep watching and see whether this is the case.