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.
I just recently got an HD + and put CM 10.1 on it. Every once in a while I get this weird glitch when waking it up from sleep. I get the home screen with the unlock button in the center per normal, but when I try to swipe to the right for the desktop icon, the screen flashes once then goes back to sleep. No matter how many times I try to wake it up this way it just goes back to sleep. I fixed it the first few times by rebooting but this morning when it did it, I tried swiping to the left to the browser icon and it worked. It brought up the browser and I just quit out of it to get to the desktop.
Anyone else have this happen?
darien87 said:
I just recently got an HD + and put CM 10.1 on it. Every once in a while I get this weird glitch when waking it up from sleep. I get the home screen with the unlock button in the center per normal, but when I try to swipe to the right for the desktop icon, the screen flashes once then goes back to sleep. No matter how many times I try to wake it up this way it just goes back to sleep. I fixed it the first few times by rebooting but this morning when it did it, I tried swiping to the left to the browser icon and it worked. It brought up the browser and I just quit out of it to get to the desktop.
Anyone else have this happen?
Click to expand...
Click to collapse
Lots of folks see this. It is usually caused by your case with a magnet in it to turn the screen off. Just open it twice.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks Leap. Didn't even think of the case being the culprit. Thanks for the info. I didn't even know the case had the feature until I got it.
I was thinking the Nook had a photocell that was reacting to opening and closing the case but it's a magnet that does it?
darien87 said:
Thanks Leap. Didn't even think of the case being the culprit. Thanks for the info. I didn't even know the case had the feature until I got it.
I was thinking the Nook had a photocell that was reacting to opening and closing the case but it's a magnet that does it?
Click to expand...
Click to collapse
Yep
Sent from my Galaxy Tab 2 using XDA Premium
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.
Hey guys, this is a weird error that just started for no reason that I can think of. I had the latest nightly build on my Nook HD when all of a sudden various parts of the screen would just be auto tapping. I tried restarting multiple times, I even went for a factory reset but ended up simply flashing TWRP on it and flashing the latest AOSP Rom.
The problem is, when I load over to TWRP, I'm still getting these touch errors. Does that mean that it's something hardware wise that was broken? Does anyone have any advice on what to do next?
All and any help is appreciated, thank you.
Try cleaning the screen thoroughly. It gets very sensitive when dirty.
Sent from my SM-T707V using XDA Premium HD app
Sometimes putting the nook to sleep and waking it up again with the power button is enough to fix "stuck touches", something gets reset when the screen is switched off.
Also, some 3rd party chargers can cause continuous random "ghost" taps all over the screen while the charger is plugged in, but the problem goes away as soon as the charger is unplugged.
One thing that can help you figure out what's going on is going into developer options and enabling the "show touches" option. That way you can at least see when a "ghost" or "stuck" touch happens. Be careful when entering passwords in this mode though, since it makes it easier for someone else to follow what you're tapping too.
Sent from my BN Nook HD using Tapatalk
Now there is another long topic on freezing, but its basically about 10seconds freeze , then things normal and stuff. Mine is different so I made a new topic.
Have sprint note. On Marshmellow now but happened on Lollipop as well.
The problem is:
After several hours of use, or may even a day, the phone just freezes....partly. Let me explain. Basically if you touch anywhere on the screen, it won't register the touch. If you hit the hard recents button, it'll show recents, but you can't click any program (it doesn't register your touch). When it first happened I thought I needed a new screen, but quickly found out I probably don't: If I hit the nav bar, it will pull down full screen, and if I have it full of notifications, I can click any of the notifications, whether its near the top, middle, or bottom, and it registers the touch and sends me to the app. But then again, at that app, the screen doesn't register. Even if I touch in the same place on the screen where I clicked the notification that sent me to the app. But the nav bar still works. It recognizes the touch, and will pull down full screen, and I can click anywhere on the screen and my touch will register. Also if I hold the power button and the reboot options come up (which on mine has option from top down to bottom, I can click any option on the screen, and it will register my touch. But if I hit the home button, the whole screen is non responsive. So I have a partial freeze. The whole screen doesn't work, but then the whole screen will work when I pull the nav bar down, so im totally confused. I already tried usually differnt launchers, but same thing, after while, screen will be non responsive
If I reboot then everything works fine and normal, so I doubt its a screen issue. Because if its broke its broke. Also tried a hard reset,problem still came back. I guess it may be an app clashing problem but I have over 100 apps it could be any one of them
Has anybody experienced something similar?
I had a buddy give me an LG Lucid3 that had a similar issue... It actually got worse over time and the touchscreen totally stopped working. (He thought) I took it apart and actually the connection was good. Put it back together and just kept rebooting it multiple times in a row. Finally, the touch started to work a little an for some reason I thought to go and download an antivirus program. The phone had 11. Got rid of them and phone has been working fine for a couple weeks now. Idk if that's your problem but I figured I'd share this experience because I've never seen anything like it.
Sent from my KYOCERA-C6745 using Tapatalk