When I wake up my Nexus S sometimes there is a dead patch on the lower left of the screen, I notice it because I can't use the keyboard on the left-hand side. If I lock it and wake it again it works just fine.
It's running 2.3.4, any ideas what could be the problem?
Related
I seem to have a problem with the letter p on the default honeycomb keyboard - it doesnt seem to let me use the letter p correctly. If I hit the key i the dead centre, it is completely unresponsive. But around the edges of the letter it works fine.
I dont think its and issue with the touchscreen as it works fine in other apps (no dead spots) just i the keyboard in lamdscape mode.
Am I completely crazy or can anyone else replicate?
Actually, after playing with it a little more there seems to be a small area of the screen completely unresponsive to touch.
Could this be a software issue or is it likely to be a fault with the touch matrix on the screen?
Have you tried restarting the tf?
Try turn off and then turn on the screen. Also check this thread out: http://forum.xda-developers.com/showthread.php?t=1068569
Thanks for the quick replies. Just restarted it and it seems fine for now. Didn't realise there was a known issue wrt touch screen responsiveness
Running CyanogenMod 6.1.2 - 0.10, fastboot with boot2.img, Go Launcher Ex.
Anybody has a problem with the top half of the screen being unresponsive? For example, I can't scroll between screen flicking on top half of the screen. But the bottom half would work.
The HW is fine, because if I tries to drag an icon from the bottom half, I can move it freely to the top half of the screen no problem.
In google map, I can rotate my device to landscape, and the problem rotates with it. I can't access any of the buttons on the top half of the program, but bottom half works fine.
I have only been able to reproduce using boot2 or boot5. I haven't seen this without swap. Restarting launcher does not fix it. I have seen cases where it fixes itself after a while (say 5 minutes).
Anybody seen the same problem? Thanks.
The same thing happens to me occasionally on Cyanogenmod 6.3 RC3. Putting it to sleep and waking up a few times usually solves it for me. A reboot will do it on the rare occasions sleep won't work.
i have an inspire with cm7.1 stable..
after running fine since i updated it, just the other day out of the blue the lock screen now rotates depending on the phones orientation..
on top of that its also very buggy, if i try to unlock the phone while its re-orienting itself, the phone will reboot..
anybody know how i can stop this?
I believe that my touch screen is not working, because when I turn my Motorola Milestone 3 on it goes to the lock screen (With the circle and a key icon that pulsates) and I cannot get it to move to the left or the right. Basically my phone has become a clock. It also no longer shows me if anyone is calling, but rings on their end. Does anyone have any suggestions? Also if I open the keypad, more often than not it freezes (I know that it has frozen because the icon in the middle is no longer pulsating, and the clock gets stuck.)
I noticed yesterday that the upper left corner of the screen isn't registering touches.
Anything I can do to correct? Maybe my tempered glass screen protector is bugging something out?
Since my bootloader is unlocked, I'm guessing I'm up the creek without a paddle for a warranty fix or replacement?
Thoughts?
Disregard, a restart of the phone remedied... Go figure ?
I'm having the same issue
also having the same issue. restart does fix the problem, but then the issue returns after a few hours. it also does NOT seem to be a hardware issue, as even when I rotate the phone from portrait to landscape, the 'new' topleft corner (previously the top-right corner in portrait mode) will also become unresponsive. seems like a firmware bug or something? anybody have any longterm solution rather than restarting the phone every few hours?
I've noticed that if I rotate to landscape , that previously unresponsive spot on the screen works fine.
I've also noticed that if I tap on the status bar just above it, it works fine.
Very odd! Other than that small quirk, I love the phone!
Same thing
Same issue here.. Corrects after a restart... Other than that it's the best phone I've had.
Issue seems to have been resolved in Marshmallow, or at least so far been running all day without the problem !