Database Develop

Touch screen issues...

So I am wondering if any of the wonderful people here at XDA are experiencing screen issues with the nook color. I have had my unit about a week, and have had numerous episodes of the screen registering touches randomly. This issue is apparently not isolated as there are youtube videos and a B&N support forum thread discussing the matter.
So is anyone out there having any touchscreen craziness? If so are you doing anything about it? Not sure if I should return my unit and get another or wait for some possible firmware update...
As always any wisdom is appreciated!

http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
Says at the top recalibrating will fixes "phantom touches" or inaccurate touches, or not respond to reasonable touches.

Mine was doing the same. I bought a screen protector and so far it hasn't happened.

My screen wasn't having "phantom touches," but at times I would press near the top and bottom edges, it seems to not be very responsive there. For example, pressing the search button in the marketplace that's at the very top right. Or pressing one of the buttons at the bottom menu.
I wiped my device back to factory and then did the latest Auto-Nooter, and started using Go Launcher. Things are much better now it seems. I think it may still happen occasionally though.

camwinnn said:
...recalibrating will fixes "phantom touches" or inaccurate touches, or not respond to reasonable touches.
Click to expand...
Click to collapse
Not just the phantom but inaccurate touches which sounds like yours, atm thats all ive seen about fixing screen stuff.
But other threads have been started where others have the same problem on the outer parts of the screen so it could be a Firmware/Hardware problem.
GTOMEX09 said:
works for me, in that the process completes, but the touchscreen is the same. The sensitivity issue at the edges is universal and very frustrating.
Click to expand...
Click to collapse
rboatright said:
Try running calibration while holding a finger on the screen near the edge.
Click to expand...
Click to collapse

[Q] My screen taps/touches/clicks itself

as the title says i was reading when the menu started showing and hiding again and again i tought was some book issues but when i got to the homescreen it began to run apps i had on it, i have no idea of the cause of this problem

I've had this same problem. I believe it's just the software and not a deficient screen. If you look over on the nookdevs website, there's a page about recalibrating the screen. I've tried it a couple of times and it's definitely improved it. Every now and then something wacky happens, but I guess that's to be expected when you let B&N develop for Android.

I had this happen myself once, and it was pretty annoying... If I didn't have adb available I don't think I could have fixed it until I did. I wasn't able to tap the screen myself, it was taping all over the place.
I did manage after a few minutes to get multitouch paint installed and it was drawing weird dots, lines, angles, etc...
I now have the recalibrate command in gscript but not sure I could run it while it's acting up. Luckily it's only happened once, and it happened while plugged in but never seen it happen again.

Happens a lot on my NC, and I think every time its because my kids touch it with dirty fingers (sweets, chocolate etc), smearing small amounts of dirt on the screen.
The screen goes nuts within few seconds, thinks its being clicked etc...
Wiping/cleaning the screen helps to resore normal behavior, btw - while the screen is moist it does not work for me at all...
Ordered screen protectors, lets see if it makes a differencel

My screen randomly goes nuts as well. It seems like a sudden, rather than a gradual thing. The screen sometimes gets pretty dirty, but cleaning it didn't seem to make much difference. Odd thing is, what DID make a difference was taking it out of the aftermarket case. I have no idea why this would work, but it does. One thing this case does is that it pushes the power and volume buttons in, as it uses four elastic straps at the corners. Maybe holding these buttons a certain way recalibrates the screen, and if you're touching it at the time, it freaks out?

I've noticed my screen only bugs out when I have it plugged into the charger.
As long as its unplugged, its fine. As soon as i pop in the cord, the screen goes haywire.
Only the wall charger though, not when its plugged into the USB on the computer.

My screen was doing that until I got a screen protector.
Sent from my LogicPD Zoom2 using XDA App

Also, if you lock and unlock the NC it should stop acting funny.

I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?

RChadwick said:
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
Click to expand...
Click to collapse
Mine does the same thing every now and again. And like you, locking the screen and waking it back up fixes it every time. It's definitely software related.

Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.

My case has a latch, but the magnet is not against the nook when I'm using it..

HotShotAzn said:
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
Click to expand...
Click to collapse
Heh, I've considered that.. Also considered the mystery sensor to the left of the Nook button too.. Nook is afraid of the dark.
Seriously though, with the CPU guvna' set to ondemand and wifi turned OFF before I power it off I haven't seen it reboot yet. It rebooted once yesterday and I know it had wifi left on as I had just been using it and didn't turn it off before it went to sleep.
So totally making up numbers here....
Default CPU governor + wifi on = 30% chance it's gonna reboot when it goes to sleep..
ondemand governor + wifi on = 20% chance it's gonna reboot
ondemand govenor + wifi off = <10% chance it's gonna reboot (not gonna even say 0 here.. heh)

RChadwick said:
My case has a latch, but the magnet is not against the nook when I'm using it..
Click to expand...
Click to collapse
I tested this theory. When the Nook is in the case, I get crazy screen taps when i try to type something. Out of the case, its perfectly fine.
When I just rest the Nook on the open case (not inside the straps/holders), it will also get crazy screen taps.
One thing to note is I also did not have any problems before updating to 1.0.1. Not saying the update is the cause of the problem but its one of the variables.

Left side touch screen misbehaving after wet

Hi,
Last week I used to be outside with much rainy condition.
Though it never got totally under water, many times it's screen got wet with substantial rain drops.
Slowly, phone started misbehaving with following symptoms,
1. Around 10% of left side of touch screen doesn't show response. I enabled show touches from developer option and when I try to touch left side, say "a" letter in keyboard, it doesn't show touches and pointer jumps immediately to left edge.
2. Many times, I am not able to unlock phone as no touch are detected.
3. After unlock, many times though I am not touching phone, it shows couple of pointers (I enabled show touches in developer option to trace this) on left edge. It keeps moving resulting in erratic behavior, say screen zooms in and out, some icons clicked automatic, deleted automatic etc.
4. Sometimes I noticed that capacitive buttons are also not responding.
For all above, I have to off (not complete switch off)and on the phone. After few attempts, it becomes responding except point 1 above.
I have reflashed ROM (Vivikat) just to ensure it's not software issue.
Now it seems hardware issue with following two possibilities...
1. It's matter of some moisture in phone only. I have to try hard to dry out all moisture and phone will become responding.
2. Digitizer has some issue and may call for replacement (I don't want to do that...:crying.
Can you guys share your views/experience and advise?

RmatriX1218 said:
Hi,
Last week I used to be outside with much rainy condition.
Though it never got totally under water, many times it's screen got wet with substantial rain drops.
Slowly, phone started misbehaving with following symptoms,
1. Around 10% of left side of touch screen doesn't show response. I enabled show touches from developer option and when I try to touch left side, say "a" letter in keyboard, it doesn't show touches and pointer jumps immediately to left edge.
2. Many times, I am not able to unlock phone as no touch are detected.
3. After unlock, many times though I am not touching phone, it shows couple of pointers (I enabled show touches in developer option to trace this) on left edge. It keeps moving resulting in erratic behavior, say screen zooms in and out, some icons clicked automatic, deleted automatic etc.
4. Sometimes I noticed that capacitive buttons are also not responding.
For all above, I have to off (not complete switch off)and on the phone. After few attempts, it becomes responding except point 1 above.
I have reflashed ROM (Vivikat) just to ensure it's not software issue.
Now it seems hardware issue with following two possibilities...
1. It's matter of some moisture in phone only. I have to try hard to dry out all moisture and phone will become responding.
2. Digitizer has some issue and may call for replacement (I don't want to do that...:crying.
Can you guys share your views/experience and advise?
Click to expand...
Click to collapse
I just had touch screen issues but not with water or rain. It was the CPU. Almost whenever I overclocked it, I had touch screen issues. Both misbehaving and not behaving at all. Change the CPU frequency and restart the phone and see what happens. :good:

Eternalman said:
I just had touch screen issues but not with water or rain. It was the CPU. Almost whenever I overclocked it, I had touch screen issues. Both misbehaving and not behaving at all. Change the CPU frequency and restart the phone and see what happens. :good:
Click to expand...
Click to collapse
Thanks for your reply.
I have never overclocked my device.
However, I tried to underclocked it if by any chance, it can solve the issue.
But issue still there.
A small portion of left column on touch screen seems not responding or giving erratic behavior.
Does, water can damage digitizer to that extent that can not be recovered even after drying
Or, I should keep hope and wait more before I go for digitizer replacement

RmatriX1218 said:
Thanks for your reply.
I have never overclocked my device.
However, I tried to underclocked it if by any chance, it can solve the issue.
But issue still there.
A small portion of left column on touch screen seems not responding or giving erratic behavior.
Does, water can damage digitizer to that extent that can not be recovered even after drying
Or, I should keep hope and wait more before I go for digitizer replacement
Click to expand...
Click to collapse
If the digitizer is damaged, it is probably done. But if you can open the open, check the digitizer and see if there are any things stuck on it. My recommendation: ask an engineer to open it and clean it with the special spray they use to clean electronic parts. Maybe the water has had only a side effect and it will be fixed by cleaning the digitizer.

Eternalman said:
If the digitizer is damaged, it is probably done. But if you can open the open, check the digitizer and see if there are any things stuck on it. My recommendation: ask an engineer to open it and clean it with the special spray they use to clean electronic parts. Maybe the water has had only a side effect and it will be fixed by cleaning the digitizer.
Click to expand...
Click to collapse
Thanks.
I loved to hear your words, as I have still hope for resolving issue without replacement of digitizer :fingers-crossed:
I'll find some engineer to get it serviced....and post update.

RmatriX1218 said:
Thanks.
I loved to hear your words, as I have still hope for resolving issue without replacement of digitizer :fingers-crossed:
I'll find some engineer to get it serviced....and post update.
Click to expand...
Click to collapse
You're Welcome buddy! :highfive:

Double tap to wake. Or more like quadruple tap to wake, eh?

I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?

If you move your phone first, then it will work by double tapping.
I think that quadruple tap works because one of those first two taps moves the phone.

Not from my experimentation. It doesn't seem to matter if i've moved it first or tapped it directly when it's sitting on the table. Then only factor that seems to matter is time since screen off.
Thanks for the input though.

It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.

pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
Click to expand...
Click to collapse
I'm on A.5.77, which is the latest, right?
I have this issue about 5% of the time, 95% of the time even if I have the phone lying still on the table double tap works. Must be something (also) else than the firmware!

pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake
Click to expand...
Click to collapse
double tap works first time every time even if the phone has been sitting still and idle for 10 hours.
I know theres a few people who have this problem but its something other than just the new firmware.

I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.

pipspeak said:
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
Click to expand...
Click to collapse
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...

had a tempered glass protector on from day one, phone has always been stock, no other launcher. T2W worked brilliantly until the latest firmware update. frustrating when the phone is the car mount, i have to hit the power button to get the screen on instead of just tap-tap.

quarrymanpaul said:
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
Click to expand...
Click to collapse
Full day's use now and replacing Nova launcher with Apex has definitely improved things.
Might help others in the same situation who are scratching their heads wondering why everyone else seems to have perfect tap2wake.

Tried Apex for a day as well. No different than Nova for me.

hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap

AM Radio said:
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Not working here.
I have a Nillkin tempered glass on mine though.

quack3d said:
I have a Nillkin tempered glass on mine though.
Click to expand...
Click to collapse
me too. weird. fingers crossed the next update takes care of this, properly.

AM Radio said:
...TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Works for me too. [emoji4]

Did Lollipop fix this problem?

quack3d said:
Did Lollipop fix this problem?
Click to expand...
Click to collapse
Not really. In fact it got worse.

quarrymanpaul said:
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
Click to expand...
Click to collapse
Well, I can tell you why this is happening. this happened to me, because I just had too many xposed modules.. once I got rid of them, everything went back to normal

Been a long time since I've posted here but found this thread as had the same issue when the phone is flat on a table.
Anyway, think I've found a solid solution or work around, depends how you look at it. If you use just an extended finger, all other fingers closed or away from the phone, it's very inconsistent but mostly unresponsive.
Solution: grip the top and bottom of the phone lightly with your thumb and middle or 4th finger at the same time as tapping the screen with your index finger. Works every time for me.
So Sony's reduced the sensitivity to the point where it needs additional capacitance so it knows you are holding the phone and it won't unlock in your pocket. Makes sense.

pretty frastrating here too.. but really can't find out the main reason of the problem here as immediately when I got the phone I rooted it, flashed .77, replaced stock launcher with nova, installed expsed and 2-3 modules :crying:
will try the three-taps and olding-phone+index-finger-tapping workarounds, thanks for the hints

Please help - screen randomly becomes nonresponsive - but only partly - please read

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