Touchscreen issues

icyitscold

Member
Mar 12, 2011
14
0
0
Visit site
I noticed today that my Nexus 7 suffered from the touchscreen issue referenced at the link below after watching a youtube video.

Video: Nexus 7 touchscreen defect

Is this affecting everyone or is it limited to a few devices? I really don't want to have to return this and wait for a new one but if I must... :(
 

effreyj

Well-known member
Sep 9, 2011
710
3
0
Visit site
I've noticed when I play games sometimes I have similar issues. I'm wondering if it's a software bug though...
 

keithz

Well-known member
Jun 6, 2011
168
21
0
Visit site
I noticed it when typing the other day. Keyboard just wasn't picking up inputs.

Very frustrating.

Hoping it's an easily fixable software bug.
 

Small_law

Well-known member
Apr 20, 2010
620
34
0
Visit site
Not seeing it, but swiping through home screens feels a bit jitterly, like it's had too much caffeine, especially when I first pick it up. That's due to the Way they've increased touch response. Topolsky at the Verge noted it in his review. Not a big issue.
 

DahakaSand

New member
Jul 21, 2012
1
0
0
Visit site
It's happened to me too but the quickest way to fix it is to just press the power button and turn it back on without shutting it down. You'll notice that the touch sensitivity comes back perfectly. I think it is a software issue so hopefully google will fix it up.
 

ShaggyKids

Well-known member
Dec 1, 2010
2,714
37
48
Visit site
I think I detected this issue on mine a couple of times. I was using the GO Keyboard so switched back to Swift Key and going to see if that makes a difference. Got to thinking since it's a keyboard issue maybe it's the keyboard app I was using.
 

berrydroidapple

Well-known member
Jul 11, 2012
121
6
0
Visit site
O.K. I thought it was just me. Last night I noticed the screen became less responsive and while typing I got all kinds of strange words. Scared the heck out of me.

This morning I did use a microfiber towel I have to clean the screen, and can report no issues.:)
 

ShaggyKids

Well-known member
Dec 1, 2010
2,714
37
48
Visit site
The problem seems to happen after longer periods of use, and at least for me.

Sent from my AWESOME Nexus 7 via Tapatalk 2 :)
 

Technomancer07

New member
Sep 6, 2012
1
0
0
Visit site
I am still having this issue as of Sept 2012. I notice that the touchscreen will stop responding as easily after the device is active for a couple of days. A reboot solves the problem. I don't use the Nexus 7 constantly during the day. Any idea how to let Google know this is happening directly?
 

Wayren

Active member
Apr 17, 2011
36
0
0
Visit site
Huh. I seem to have the opposite problem. After my Nexus 7 has been on for 20+ minutes the top half of the screen in portrait mode starts behaving like someone is rapidly tapping the screen all over. It makes it unusable. I have to power cycle the device to return it to working order. Issue continues after a factory reset. Gonna call support tonight about it.
 

mmaestro

Well-known member
Oct 13, 2010
84
4
0
Visit site
There is a long, long troubleshooting thread at XDA here.
And also a thread on Google's codebase for Android here.

The tl;dr version: there seem to be two distinct issues. One is slow storage, which may vary across devices and is compounded by background sync and filling the storage. 2 programs which have a big impact on this are Currents and Play Magazines. If you're having issues, try disabling both of these and see if it helps, also try to keep at least 3GB of storage free on your device. That seems to be the issue which is fixed by a full reboot. My gut feeling is that it's poor implementation of garbage collection on the storage, which should be fixable with a software patch, but that's just gut, I could be way off base.
The second issue is lack of responsiveness which is fixed by turning the screen on and off. I've seen suggestions that this is a hardware defect, a bad ground in the screen and may be something that needs to be warrantied. That seems more speculative, though.

FWIW, my Nexus has both issues, but to a manageable degree so I haven't replaced it, yet.