****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine
Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
anyone ?
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.
Related
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
I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."
I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!
Is there an FAQ about this digitizer issue?
JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me
Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733
JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
jeremy89632 said:
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
Click to expand...
Click to collapse
i sent him a mail. here are the responses:
it seems unlikely:
- I don't have the device
- it uses different touch controller than 10.1
- kernel doesn't support configurable parameters for 8.9
Click to expand...
Click to collapse
I'm speaking about driver provided for controller used in 8.9, it has
no possibility to change configuration. And the firmware of the
controller is a binary blob with no documentation.
Click to expand...
Click to collapse
looks like we are unlucky
being very upset with this problem i started poking around the build.prop
it might be placebo but i feel that when this is added:
Code:
windowsmgr.max_events_per_sec=300
it gets a little more responsive. still not what i want it to be but better than before.
Try Touchscreen booster
It seems to have helped mine.
thanks. seems a little more responsive.
here is the apk if anybody else was wondering:
http://forum.xda-developers.com/showthread.php?t=1261237
My 8.9 LTE is super sensative, probbly the most I have seen on any android tab.
I can just barely graze my screen with rhe back of my fingernail and it even picks that up.
Compared to my roomates ASUS Transformer Prime, wo cant even use his fingernail unless he really jams it down.
iinteresting but im on the tegra version which aparently has completely different hardware
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
MatteAce said:
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
Click to expand...
Click to collapse
Try TouchScreen Booster?
the_hatrix said:
Try TouchScreen Booster?
Click to expand...
Click to collapse
that's been the first thing I did, but the improvements it brings are very light.
Does the tablet really have different hardware between the wifi and the LTE version? (at least regarding the screen digitizer)
Loccy said:
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Click to expand...
Click to collapse
Hmm, is it really a sensitivity issue? If I swipe first then wiggle like you mention, the screen will wiggle slightly. It sounds like there is a threshold to switch from holding the finger down motionless, to scrolling from left to right.
Perhaps a threshold setting (if available) is sufficient to overcome this?
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Kasracer said:
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Click to expand...
Click to collapse
I have Samsung 3.2 OTA update and it really changes nothing.
Btw no answer yet from Samsung, and yes, the problem is just about some sort of accidental touch filter
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
Does anyone have issues with the touchscreen skipping every once in a while? Occasionally, there is an area on the lower half of the screen that seems to be insensitive, but if you start touching around it, it goes back to normal.
I've discussed this with some fellow Z1 owners and it appears to be a relatively common issue. There is some discussion that it may be due to overheating or a software issue.
Anyone else have this problem?
Had this once while my device overheated hard(~47-48°).
Not sure if I have to be concerned about that, because otherwise it works fine.
koopa101 said:
Does anyone have issues with the touchscreen skipping every once in a while? Occasionally, there is an area on the lower half of the screen that seems to be insensitive, but if you start touching around it, it goes back to normal.
I've discussed this with some fellow Z1 owners and it appears to be a relatively common issue. There is some discussion that it may be due to overheating or a software issue.
Anyone else have this problem?
Click to expand...
Click to collapse
Same here
Sent from my C6903 using XDA Premium 4 mobile app
At first I thought it was an issue with crappy screen protectors. The Z1 already has a anti-crack film on the screen so I thought that adding a poorly made screen protector would create too much distance from my touch to the sensor. However, I've tried replacing the screen protector and also asked other people with varying brands of screen protectors and it seems that the issue still persists.
The issue seems to occur most often on the password screen for me (which is particularly annoying).
I've had it too, lower half of screen does not register slides on login screen for a brief moment.. No overheat!
Sent from my C6903 using Tapatalk
No overheat here 2 but with the same issue.
Also the last days i think that all the screen sometimes is more insensitive than usual.I have to touch 2-3 times to do what i want.
I think that is a hardware issue.
Have it sometimes as well sadly! Can't figure out when exactly it's happening though..
I find it very annoying when I'm scrolling and at the bottom part of the screen, the scrolling becomes a click, which brings me to a place I did not intend to go to. Hope it's software, but can't imagine that.
Happens to me as well, regardless of device temperature. Based on the seemingly random nature of the issue, it should be a simple fix via software update. A similar bug persisted on the 2013 Nexus 7 devices when you laid them flat on a surface.
koopa101 said:
Does anyone have issues with the touchscreen skipping every once in a while? Occasionally, there is an area on the lower half of the screen that seems to be insensitive, but if you start touching around it, it goes back to normal.
I've discussed this with some fellow Z1 owners and it appears to be a relatively common issue. There is some discussion that it may be due to overheating or a software issue.
Anyone else have this problem?
Click to expand...
Click to collapse
Same problem here!!!
I think is a hardware issue. When you touch the alu frame the phone works fine. If the phone is on the table or in a cover the issue are immediately there.
Sorry for my bad english. Hope you understand
I noticed some small things and thought it was me but I guess this makes sense.
Could be worse, my previous Note 3 had multitouch issues and had problems register several fingers :silly:
Considering how common the issue appears to be, I find it hard to believe that this is a hardware issue.
I also don't believe it's related to overheating since it seems to happen even when I haven't used the phone at all for a long time.
It feels like a software issue to me since the issue sends to go away if you touch another section of your screen
koopa101 said:
Considering how common the issue appears to be, I find it hard to believe that this is a hardware issue.
I also don't believe it's related to overheating since it seems to happen even when I haven't used the phone at all for a long time.
It feels like a software issue to me since the issue sends to go away if you touch another section of your screen
Click to expand...
Click to collapse
When you touch the alu frame the issue is not there. Only when you use phone without touching the frame.
Must be some kind of hardware issue...
Sent from my iPad using Tapatalk HD
I am having the exact same issue. The weird thing is, is that it doesn't always fail to register my finger. I've gone a few days without it, then suddenly it's back again. Also in the Xperia Diagnostics app I could then see the phone failing to register a proper line, then 20 seconds later it's gone. Weird thing indeed.
Sent from my C6903 using XDA Premium 4 mobile app
nonamedk said:
When you touch the alu frame the issue is not there. Only when you use phone without touching the frame.
Must be some kind of hardware issue...
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Is this the case? I don't think I've ever used my phone without touching the frame somehow.
koopa101 said:
Does anyone have issues with the touchscreen skipping every once in a while? Occasionally, there is an area on the lower half of the screen that seems to be insensitive, but if you start touching around it, it goes back to normal.
I've discussed this with some fellow Z1 owners and it appears to be a relatively common issue. There is some discussion that it may be due to overheating or a software issue.
Anyone else have this problem?
Click to expand...
Click to collapse
Yes, I have it as well.. First of all though, to reply to a lot of people on this thread, it happens regardless of "flat surface, touching the frame, overheating", or anything else. It seems to be completely random with me. Sometimes everything is perfect, then it goes nuts for no apparent reason whatsoever. I'm almost sure it's a software issue, and hope sony will address this issue soon!
it also happens sometimes to me.
the only thing that helps is to touch the ground of the ac power socket. it seems like the screen needs much more potential difference between the pointer and the screen itself and after a while of using it the pointer (you and your fingers) are more loaded.
thats my theory to it.
Jimmyness said:
Yes, I have it as well.. First of all though, to reply to a lot of people on this thread, it happens regardless of "flat surface, touching the frame, overheating", or anything else. It seems to be completely random with me. Sometimes everything is perfect, then it goes nuts for no apparent reason whatsoever. I'm almost sure it's a software issue, and hope sony will address this issue soon!
Click to expand...
Click to collapse
Unfortunately, unlike the rooting camera bug, it doesn't sound like Sony has even acknowledge it at all.
Exactly this.
http://www.youtube.com/watch?v=h0sqwwUoEPc
I often have to attempt inputting my password multiple times before I can finally get it right. I have since switched to PIN unlock. Really wish there was some sort of response from Sony.
I'd you're using pie then stop using it and retry the affected area. I had this issues because of the activation area causing certain keys on the keyboard to become non responsive.
Sent from my Z1.
Has anyone tryed the touchfwtool?
URL itechdestiny.com/xperia-touch-screen-solution-touchfwtools-apk-download/
My phone is on the way back from repair. They only have calibrated the screen.