Running CM7.0.3 of 8GB uSD card. When using the stock browser, it seems like I frequently have to tap several times to get the NC to recognize I am trying to tap/touch the link. Does anyone else have this issue? I used a nook screen recalibrate app ( https://market.android.com/details?id=com.assid.android.nookrecalibrate ), but haven't noticed any difference.
I just noticed, that Nook must be rooted for the recalibrate app. Stupid question I'm sure... is my Nook "rooted" if I am booting/running from the addin uSD card? I didn't do anything to the builtin memory device (it still has stock 1.2 I think).
I have never noticed any phantom/ghost touches.
So, anyone else having these missing touch problems?
Thanks!
cm7 = rooted
run the nook touch screen calibrate app not plugged into the power
also, getting a screen protector helps with phantom touches
I pretty much never use the Nook while it is plugged. Are there any other utilities to help determine if the screen touch sensor is calibrated? I remember way back to the Palm days, there was a recalibrate function to help keep touches lined up with the display.
Remove the uSD, boot into your stock ROM and see determine the responsiveness of your NC screen.
If it's bad, back to B&N.
If it's good, blame your uSD.
First off. Clean your screen. Turn the screen on and off and then run the nook screen recalibrate app
Sent from my NookColor using Tapatalk
koopakid08 said:
First off. Clean your screen. Turn the screen on and off and then run the nook screen recalibrate app
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I notice that a simple screen on/off and a regular screen cleaning helps
Related
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
Ok folks, I registered here because I felt this forum was the best place to get help. Here is my problem. I use a Nook Color 1.1 running the latest autonooter, and I've started having major touchscreen problems. What happens is this: The screen has started registering touches when I am nowhere near the screen, and when I do touch the screen, it only sometimes registers at the right location. This has made it impossible to use at all, and I'd like to know if there's any way of fixing it without having to do anything on the Nook Color. Thanks for your input,
TechPlease
Reboot? Wipe the screen? Reimage?
Sounds like damage to me.
TechPlease said:
Ok folks, I registered here because I felt this forum was the best place to get help. Here is my problem. I use a Nook Color 1.1 running the latest autonooter, and I've started having major touchscreen problems. What happens is this: The screen has started registering touches when I am nowhere near the screen, and when I do touch the screen, it only sometimes registers at the right location. This has made it impossible to use at all, and I'd like to know if there's any way of fixing it without having to do anything on the Nook Color. Thanks for your input,
TechPlease
Click to expand...
Click to collapse
Clean the screen thoroughly then reboot. Does this fix the issue, even if only temporarily? If so, buy a matte screen protector. The NC screen has a tacky coating that seems to collect oil/moisture more than other screens I've used.
If that doesn't work, download a screen calibration app. There's one floating around the forums.
TechPlease said:
Ok folks, I registered here because I felt this forum was the best place to get help. Here is my problem. I use a Nook Color 1.1 running the latest autonooter, and I've started having major touchscreen problems. What happens is this: The screen has started registering touches when I am nowhere near the screen, and when I do touch the screen, it only sometimes registers at the right location. This has made it impossible to use at all, and I'd like to know if there's any way of fixing it without having to do anything on the Nook Color. Thanks for your input,
TechPlease
Click to expand...
Click to collapse
I had the exact same experience when I first tried to install CM7 to run from an SD card. I couldn't sign in to my Google account because just hovering my finger over a key produced a string of letters on the screen (ie: yyyyyyyyyyy)
It was really freaky. I had to sneak up on a key and jab it real fast so that it would type only one letter.
I also had a problem with key registration. I would go to type an "r" and a "t" would be typed. So I had to touch the key at the extreme left edge (or sometimes on an an adjacent key!) to get the letter I wanted to show up.
Fortunately, after I got CM7 up an running properly, the screen problem went away. BTW, I do use a anti-glare screen protector, which, I think, lessens the screen sensitivity a little.
If I were you, I would try restoring my Nook back to stock, and see if the screen is still too sensitive. If it is, it's time for a new Nook. If it's not, try rooting again.
Good Luck.
Try Nook Screen Recalibration on the market. I had the same problem (pressing Q gave me W). It certainly improves it.
use a screen protector or put a thin plastic sheet on your screen and then recalibrate it.
using the method given here.
http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
If you are using a screen protector u can keep using it, however i removed mine after a week or two and didn't really get any weird touches what so ever after that (earlier my touchscreen was unusable).
Thanks for all your suggestions
Thanks for all your suggestions. I think it got worse after I used a recalibration app from the marketplace. For those suggesting I try an app, I can't get the NC to settle down enough to let me tap on things. Yes, I do use a screen protector, so that's not an issue. I will try recalibrating from my computer, and if that doesn't work, is there a good tutorial on how to put it back to stock, and is there a way to re-stockp) it so that if I DO need a new one, I can just return mine? Mine is (if I hadn't rooted it) still under warranty.
TechPlease
Seems like it's fixed.
I think I got it fixed. It calmed down enough for me to run the Nook Screen Calibration app from the Android Marketplace again, and that seems to have cleared the problem up. Mods, please (if you can) mark as SOLVED.
If I connect my nook color to AC adapter, touchscreen will response randomly , so I unplugged usb cable and touchscreen works again
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.
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