Database Develop

[Q] Screen inaccuracy issues

I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?

Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.

It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.

I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App

msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.

It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).

Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!

Most probably replaced the phone's MB.

Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...

I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.

ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App

pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?

xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.

The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.

Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.

The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.

Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.

Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App

Nookie Froyo Users!!! Touch Screen corners.

It seems that corner touch screen sensitivity issues are prevalent among all nook color users. What I'm wondering is, does nookie Froyo have this issue as well?

Yes, or at least for me.

No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.

I'm on a rooted stock, but my edge sensitivity issues went away when I loaded one of the overclock kernels. I don't know how the two could be linked, but it is the only explanation I have for the difference. I'm not sure if that's been explored on Nookie, but I thought I would share since that would point to a software issue rather than hardware.

isolated_epidemic said:
I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
That I'm not so sure of. Using "Touch Test" I see all touches, but they seem to get shifted slightly when I press near the edges. Maybe this could get solved in the driver (maybe with some help of calibration tool). I hope to have time to play with this sometime soon.

isolated_epidemic said:
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
How can you be so sure?
If i use google market, sometimes the search button is hard to press,
but using appbrain market it works 100% of the time without problems.

No its not H/W I think, run some tests and corners work fine.
Its certainly something else, I also have better response after loading OC.

I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
I've seen the same behaviour as well, some apps the corners take 18,013,108 tries to get to work, other apps I'm all "Whoa, first try and it worked?!".
I put the 950 OC on my autonoot but then I started playing with Froyo on a C10 SD card (very quick) so I don't know if the OC's actually helped with the corners or not. And of course this is the one day I leave it at home since I got it.

Ultimoose said:
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
Click to expand...
Click to collapse
Use Menu>Search instead of trying to touch the top magnifying glass.

Happens to me with Froyo. I seriously doubt its hardware related. Seemed to work fine on the stock B&N.

It is common for digitizers to be less accurate along the edges but the Nook Color seems worse than normal. I've noticed the problem regardless of kernel or rom used.

I'm pretty sure it has something to do with the LCD Density. All buttons/elements are a lot easier to press when I switched to 240-250. It does look ugly though, it'd be a lot prettier when we get a custom rom running.

Sigvard is right. Fixed for me by chaging my LCD Density. I set it to 200, which is a little too large for me, so I may lower it. But since doing that I have had no problems at all.
Guide here: http://forum.xda-developers.com/showthread.php?t=889951&highlight=LCD+Density

Ha! I have the exact problem even with stock rom. I though it was the problem of the particular corner of the unit I got! It is much easier to press the button in landscape view.

I dont believe its the screen. Download AppBrain and tap the search button. it works 100% of the time

It is the screen. Use a drawing program and notice how it is easy to draw a straight line in the middle and not as easy on the sides and corners. Note, you need to drag your finger slowly or else you will see more interpolation.
Raising the LCD density just hides the problem by making the hit zone bigger. Fortunately, I can live with the it.

[Q] Touch Screen Responsiveness

Device: Nook Color rooted to 1.1
I had my Nook Color in the car today (40 degrees or so), pulled it out to show her what it looked like rooted. While standing in the driveway showing her different things, I found the touch screen was overly sensitive. As I was scrolling through different things (the app list, twitter, facebook), the slightest touch would select/open an item. It normally doesn't do this. It was incredibly frustrating and almost unusable. I pulled it out later and it seems to be behaving like it normally does.
Does temperature affect the NC screen? Where they any touch screen changes in 1.1? Is there a setting to calibrate the touch screen? I can't seem to find one. Any other suggestions?
I tried doing a search on the forum, but the search crashed.
Thanks.

horsemom said:
Is there a setting to calibrate the touch screen? I can't seem to find one.
Click to expand...
Click to collapse
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
I don't know if it's placebo or not, but I feel like this app improved my screen response.
http://forum.xda-developers.com/showthread.php?t=934500
As for the other question, I would expect the screen to be less responsive in cold weather, but I don't have anything to base that on.

Guessing what you experienced was due to condensation on the screen. Doesn't take much and can be 'invisible' to you but the screen is sensitive to 'stuff' on the screen and will become overly sensitive if there is anything on it, like moisture, skin oils, etc .. a screen protector may help but unless it continues that is probably the cause.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
What you experience is probably temperature related, but another thing to try is to increase the LCD screen density to around 190, 200, or a little more. For me, I get improved sensitivity, especially near the corners.

My daughter accidentally got a little water on the screen and it was a little erratic. I put it in a ziplock with a handful of rice for about 6 hours and it was like new.

I have owned 3 nook colors, the first one I owned freaked out when I used a damp cloth to wipe the screen. It exhibited some strange behavior and emitted some loud static from the speaker. It would not power down or anything... finally it just went back to normal, so I took it back to B&N and then went and bought one at walmart. I took it back because I thought I wanted the Viewsonic G Tablet. But after trying it I finally bought a Nook Color at Best Buy, bought a screen protector too so that I don't have a repeat of my first NC. The screens on these things are, I believe, rather sensitive and the cold or the moisture may have played a part in your unit's behavior.
migrax

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
Same here. My screen also seems very inaccurate.
Have you found a fix?
Sent from a NookColor using the xda app

I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).

tenderidol said:
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
Click to expand...
Click to collapse
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook

It's funny, actually... The cold makes your skin less detectable because of vasoconstriction in your fingers as a physiological response to the cold temperature, but a hint of moisture by means of condensation has the opposite effect.
For me, condensation is rarely a problem, but the decreased capillary blood flow effect is quite noticeable.
Sent from my Nexus S using XDA Premium App

One thing that's been mentioned before (and the B&N salesman told me while buying a screenprotector) is that if the screen has a lot of fingerprints, it'll make the nook act weird.
Try wiping the screen of fingerprints.

don_ernesto said:
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
Click to expand...
Click to collapse
Thanks for the reply. Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!

tenderidol said:
Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
Click to expand...
Click to collapse
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply

don_ernesto said:
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
Click to expand...
Click to collapse
Thanks again for the reply.
Yes, I'd love to take care of it ASAP, since I'm sick of trying to hit a small button on the screen and going somewhere else instead.
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!

tenderidol said:
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
Click to expand...
Click to collapse
go ahead! you won't loose any app or any data (not even your progress in Angry Birds)
Of course, before applying this changes i always make a backup. good to have a way back in case something goes wrong

Good test tool
I ran GoJimi's tool, and since then my screen has been flipping out. Typing anything is a good test...I enter one key like "z", and get 2 - "zm". Utterly maddening.
A good tool to see what's going on is "Mutitouch Test" from JerryW in the market.
When I press with one finger, I see a "phantom" 2nd point jumping around. Very quick way to see 1) how good tracking is and 2) if there's any random inintended multitouch action happening.

Nexus 7 touchscreen dead spots

So i've noticed a very strange issue with my Nexus 7. If I wake the tablet up while touching the screen I get some very strange touchscreen behavior. It's almost as if there are dead areas on the touchscreen that don't respond to touch. If I put it back to sleep and wake it up without touching the screen the issue is gone. I've made a youtube video demonstrating the issue but I can't post the link yet since I haven't had 10 posts yet. If someone PMs me I will message them the link so that they can post it to this thread.
Has anybody else experienced this issue?

I'm having the same issue. I noticed it while typing.
Sent from my Nexus 7 using xda premium

Any specific areas that are less responsive? I wonder if there's a touchscreen calibration app for the Nexus. I know there are for other devices.

El Daddy said:
I'm having the same issue. I noticed it while typing.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
+1 Definitely noticing this. It appears to occur randomly and inconsistently in different regions. The same region will not go dead again, necessarily. It seems as though the screen simply does not register those touches.

clankfu said:
Any specific areas that are less responsive? I wonder if there's a touchscreen calibration app for the Nexus. I know there are for other devices.
Click to expand...
Click to collapse
It seems to be towards the center most of the time and the dead zone appears to vary in size. It's possible the dead spot may center around whatever part of the screen was touched when waking the device. I'll have to do some more testing to see if that is the case.

solvingchaos said:
It seems to be towards the center most of the time and the dead zone appears to vary in size. It's possible the dead spot may center around whatever part of the screen was touched when waking the device. I'll have to do some more testing to see if that is the case.
Click to expand...
Click to collapse
Just got mine and it was sitting outside in the heat and the touchscreen was not responding well when I first turned it. After it cooled off and installed the update every thing is working fine.

Here is a video from the OP. He asked me to post it for him.

Is it possible that the capacitance of the screen is calibrated upon wake or something? Not even sure if possible, but it's a thought.
Edit: a drawing app may allow you to demonstrate a little easier.

I don't know if my issue is related but scrolling is totally inconsistent on my n7. Usually when I swipe it'll work correctly but one out of five times a swipe will be registered as a tap. This gets really annoying when you're trying to scroll but end up clicking something instead. Wonder if my n7 is defective.
Sent from my Nexus 7 using Tapatalk 2

El Daddy said:
Here is a video from the OP. He asked me to post it for him.
Click to expand...
Click to collapse
I don't have my N7 yet so I can't test it out for you but that's definitely weird. Can someone with an N7 try to duplicate the issue?

grukko said:
I don't know if my issue is related but scrolling is totally inconsistent on my n7. Usually when I swipe it'll work correctly but one out of five times a swipe will be registered as a tap. This gets really annoying when you're trying to scroll but end up clicking something instead. Wonder if my n7 is defective.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I've also seen this happen on occasion when I trigger the issue. Swipes will sometimes register as clicks...

A good way to confirm the dead spot is to download a drawing program and see if there are breaks when you try to draw a straight line. Even though I can replicate the dead spot when scrolling, everything seems fine in the drawing program.
Sent from my Nexus 7 using Tapatalk 2

This is an Android problem as far as I am concerned. All of my android devices have typed funky while charging.

grukko said:
A good way to confirm the dead spot is to download a drawing program and see if there are breaks when you try to draw a straight line. Even though I can replicate the dead spot when scrolling, everything seems fine in the drawing program.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I tried this out in two drawing apps and got different results. In "Draw Free" when drawing vertical lines my line would stop at the beginning of the "dead" spot and pick up again on the other side of the "dead" spot. I could not replicate the issue when drawing vertical lines in the "Picasso" drawing app.

Not seeing this issue on my Nexus 7. Not very helpful in tracking the problem, but I figured it was worth mentioning that this doesn't seem to be global. I'll post again if I manage to replicate the issue.

I enabled show touches in developer options when it started happening, and I saw ghost touches nearing the middle left side of the screen when nearing areas with dead spots.
Seems like a grounding issue internally causing the touch driver to short in some places.

nicatronTg said:
I enabled show touches in developer options when it started happening, and I saw ghost touches nearing the middle left side of the screen when nearing areas with dead spots.
Seems like a grounding issue internally causing the touch driver to short in some places.
Click to expand...
Click to collapse
If it is due to a internal grounding issue I don't think it will be as simple as a software fix
I am on the fence on whether I should try and get mine swapped out with a new one at GameStop...At a minimum I am going to try and call google support at some point today and get their take on the situation.

I would definitely swap it out.

Hello to all. I don't have an Nexus 7 but i do have Nexus S and i noticed from some time when i take out the phone from my pocket if i touch the screen and then turn it on the display was not responsive on touch but did not make some tests to see if the touch before turning on the screen was the exact problem. Now i saw this thread and tried the "pointer location" in Developer options and got this:
Turning off the screen.
Put my finger on a chosen spot.
Turn on the screen.
Unlock.
Try to draw a line passing through the exact same place where my finger was when i turned on the screen.
The line get to the point and then make a half circle around the spot or it break the line and then continue after the point where my finger was.
After turning off and on the display again the non responding spot disapear.
Sorry for my bad english

I too am having this problem.
I bought one at Sam's because i was sick of waiting on the play store....now I'm trying to decide if i should take delivery in the hopes that the touchscreen bug is only on some...
Sent from my Galaxy Nexus using Tapatalk 2

Getting a better look at this multitouch issue, with some good ol' community feedback

Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan

I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.

If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.

peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs

Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan

Yes, i have this problem. And only while device is laying on the table.

Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.

Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan

Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2

if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.

herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult

Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.

ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?

ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.

I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.

I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app

Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O

DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.

dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.

Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind