Nexus 7 - 2013 - Screen Unresponsive - Issue

[brosko]

Get this...I had purchased the Asus Memo Pad HD7 and used screen protector and had no problems. This must be a problem solely related to the Nexus 7.

Sent from my SM-N900V using Tapatalk

I think you're right.

 

[Haalcyon]

I think you're right.

Most definitely a Nexus 7 only issue. ...it may even be restricted to the early production WiFi models.


via the tablet

 

[brosko]

Most definitely a Nexus 7 only issue. ...it may even be restricted to the early production WiFi models.


via the tablet

Mine is a September 2013 production date.

 

[Haalcyon]

Mine is a September 2013 production date.

Okay, so the early production model theory is out.


via the tablet

 

[B. Diddy]

I've been wondering about this touchscreen issue lately. I've noticed very rare instances of decreased touchscreen sensitivity on my 2013 N7, and I think each time it happens, my finger happens to be very dry. I think very dry skin (i.e., with little natural skin oils) can reduce conductivity. For people who are having significant sensitivity issues--does it help if you take measures to prevent your fingertips from getting overly dry?

Posted via Android Central App

 

[carter17]

Something happened as the updates keep coming. When I first got it on release week it worked fine it could be flat on the table and worked normal touch screen that is. But now if its flat on its back it is unresponsive. And in general its just not as responsive as it used to be. But I still like my tablet nothing is perfect

Posted via Android Central App

 

[brosko]

But now if its flat on its back it is unresponsive. And in general its just not as responsive as it used to be.

Posted via Android Central App

I have the same exact thing happening to mine.

 

[infoghost]

I get this from time to time also. I used to reboot, but I've found just hitting the power button (putting it to sleep) for 10 seconds or so resolves it.

 

[Eaton Scrapple]

I put mine in developer mode and turned on the touch tracking. About one third of the time, and I've been watching closely, the touch will register as a trace on the screen and still the underlying app will DO NOTHING. Sometimes I have to tap an icon THREE TIMES to get it to activate the app. Other times such as being inside the Chrome browser, I also have to tap it twice. LET ME REPEAT...those first two touches are clearly recorded by the developer mode tracking! There's a trace and a blob right smack over the thing that didn't respond (such as Chrome new tab page, click on a "Most Recent" thumbnail). I can't find any rhyme or reason. IT IS NOT THE HARDWARE. It's Android, or the app, or something between the digitizer and the GO instruction!

I have also found that it seems to run in clusters. It'll work fine for quite a while and then sure enough every touch has to be done thrice to get anything done. WHEN that happens, I hook up a USB Mouse. For some reason, hooking up a mouse "revives" the sensitivity. Then it's OK for a long while again.

Very aggravating indeed. It's something in the code, not the hardware, though, I'm pretty sure. No amount of having them replace yours will fix BAD CODING.

 

[motorcycle_monkey]

I get this constantly. I have found if I touch the bezel part of the screen with one finger, and then touch the icon I am trying to touch with another, it works. Laying it flat often happens, putting it at an angle in my Poetic Slim case will often make it unresponsive. For a long time I have believed it was the case. One theory on some thread I read months ago was that it's a grounding issue, which the first Nexus had, which is why I touch off the active part of the screen with one finger and to the part I am trying to touch with another. It works, sometimes. The trick of shutting off the screen works, sometimes. Sometimes it seems to be only on certain apps. I have had both Nexus 7's, this one since the day it was released. I don't recall this many touch issues with the original I had. It's annoying, but the 90-95% of the time it works without issue is well worth keeping it around. Maybe there will be another new one this year and I will just replace this one, b/c I just cannot seem to skip a version, even though this one is awesome!

 

[Haalcyon]

I get this constantly. I have found if I touch the bezel part of the screen with one finger, and then touch the icon I am trying to touch with another, it works. Laying it flat often happens, putting it at an angle in my Poetic Slim case will often make it unresponsive. For a long time I have believed it was the case. One theory on some thread I read months ago was that it's a grounding issue, which the first Nexus had, which is why I touch off the active part of the screen with one finger and to the part I am trying to touch with another. It works, sometimes. The trick of shutting off the screen works, sometimes. Sometimes it seems to be only on certain apps. I have had both Nexus 7's, this one since the day it was released. I don't recall this many touch issues with the original I had. It's annoying, but the 90-95% of the time it works without issue is well worth keeping it around. Maybe there will be another new one this year and I will just replace this one, b/c I just cannot seem to skip a version, even though this one is awesome!

Either way, it's inexcusable. ...especially in 2013/14. If there were such an issue with iOS and the iPad the tech press would be having a field day. For me, I'd rather pay $10-$20 more and have Asus spend the time, effort, materials, whatever to ensure something like Google's flagship tablet was as close to perfect as any of its competitors instead of trying to save a buck and releasing something half-@$$. If I were Google Asus wouldn't be building any more devices with my name on it until they demonstrated more of an interest in quality control.

via one of the t@blets

 

[brosko]

Either way, it's inexcusable. ...especially in 2013/14. If there were such an issue with iOS and the iPad the tech press would be having a field day. For me, I'd rather pay $10-$20 more and have Asus spend the time, effort, materials, whatever to ensure something like Google's flagship tablet was as close to perfect as any of its competitors instead of trying to save a buck and releasing something half-@$$. If I were Google Asus wouldn't be building any more devices with my name on it until they demonstrated more of an interest in quality control.

via one of the t@blets

You are Absolutely 100% correct!!

 

[Relgoshan]

Hmmm. I wonder if this is actually related to my impressions of choppy scrolling on demo models? Inconsistently passing the touch data could contribute to that. My old Echo is so well tuned that sliding my finger from one screen to the other is still taken as a single smooth motion, and similarly I've never had scrolling lag on my new 7.0 LTE.

 

[brosko]

Hmmm. I wonder if this is actually related to my impressions of choppy scrolling on demo models? Inconsistently passing the touch data could contribute to that. My old Echo is so well tuned that sliding my finger from one screen to the other is still taken as a single smooth motion, and similarly I've never had scrolling lag on my new 7.0 LTE.

That could be the reason, never thought about that.

 

[motorcycle_monkey]

Either way, it's inexcusable. ...especially in 2013/14. If there were such an issue with iOS and the iPad the tech press would be having a field day. For me, I'd rather pay $10-$20 more and have Asus spend the time, effort, materials, whatever to ensure something like Google's flagship tablet was as close to perfect as any of its competitors instead of trying to save a buck and releasing something half-@$$. If I were Google Asus wouldn't be building any more devices with my name on it until they demonstrated more of an interest in quality control.

via one of the t@blets

I agree it's inexcusable, but I'm not giving up my tablet for the 2-3 weeks to send it to TX for ASUS to try to look at it and send it back in marginally better or the same shape it's currently in. I had the TF101 for a year and a half and never had a touch issue, and as I said, my original Nexus 7 didn't seem to have issues with touch.

Cheers!

 

[Haalcyon]

I agree it's inexcusable, but I'm not giving up my tablet for the 2-3 weeks to send it to TX for ASUS to try to look at it and send it back in marginally better or the same shape it's currently in. I had the TF101 for a year and a half and never had a touch issue, and as I said, my original Nexus 7 didn't seem to have issues with touch.

Cheers!

You're absolutely right, and there's a good chance you'd get the tablet back without the isue being resolved, so I wouldn't bother either. Very frustrating.


via the tablet

 

[sawaustin]

I guess your statement answers my question about what to do about mine! grrr! Stuck with it I guess.

You're absolutely right, and there's a good chance you'd get the tablet back without the isue being resolved, so I wouldn't bother either. Very frustrating.
via the tablet

No prob with my first 7. Now this with the 2013...and I paid for the 32!
Sounds like no solutions.

 

[mikemike162012]

They just shipped back my tablet after sending it in twice for repair service. Let's see what's new they did this time when I receive it. I also find the touchscreen issue is 30% on the top and bottom of the screen in portrait mode. After some digging, I kind of figure it is the exact same screen problem that plagued the 2012 nexus 7 that no amount of tweaking can help because the problem lies with the screen being fitted unevenly hence produced dead spots from both side of the screen. Get an drawing app to have an better look at the problem.

 

[blueskiesnh2o]

Would have to agree with you. I went through 3 2013 tablets, all with the "dead" screen area problem - when not plugged in and sitting on a non-conductive surface, part of the screen (the top third in portrait mode) would not respond to single touches. The online retailer was good enough to exchange the tablet twice, but the third time I was forced to send it to ASUS. Got it back after almost 3 weeks and NOTHING was done to it. Like the previous two tablets, the screen seems to work fine at first, then the issue creeps up after a few days' use. I don't know why.

I have given up on Google/ASUS admitting a problem and actually fixing it. I love the Nexus product but will avoid ASUS like the plague. I hope Google contracts to another builder next time around.

Now I have the screen freezing issue. This has gotten much worse since the 4.4.3 update. Don't know if it's related or not. Just now, I was playing some music with Google Play, and I have to swipe 6 or 7 times to pull down notifications or settings. I can swipe from page to page no problem but it takes multiple taps to open anything. I am going to uninstall a few apps I've installed recently and see if that helps, but it is extremely frustrating.

 

[trident76]

Recently, I decided to remove the screen protector, which I installed immediately after unboxing. Apparently, my Nexus 7's sporadic unresponsive screen was a result of the screen protector. Call me crazy or purely coincidental, but my device is working flawlessly now.

Exact same for me after months with screen protector, took it off and no more unresponsive or wacky touch screen, which is weird because I was sure it was grounding issue with the whole laying it down on a couch I.e. I mean it was terrible, I took it apart and nothing, put protector back on, problems immediately returned, anyone know if tempered glass will make a difference?