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
Every couple of days I have a problem with the screen becoming VERY unresponsive. It seems to affect the whole screen and requires touching characters on the keyboard, web buttons, app icons, etc. multiple times before the touch is registered. The problem persists until I reboot the device.
I haven't rooted yet or otherwise modded it at all, but maybe I have a poorly optimized app running? Haven't tried to capture a logcat yet either (and frankly wouldn't know what I was looking at).
Has anyone else experienced something like this?
Thanks!
_john
Looks like mine is suffering something similar to the problems discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1779652
I also have this issue. Was able to reproduce with multi touch tester apps. When I cross axis the touch points freak out. I think it's a grounding issue. If I touch the headphone jack or have headphones in the issue goes away. Called in a RMA request yesterday. Hope this issue isn't present in the next device.
Sent from my Nexus 7 using xda premium
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Edit: disregard this post. got the forums mixed up with another device.
bryancotton84 said:
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Click to expand...
Click to collapse
sounds like a software glitch, is anything eating up the processor?
I'm on LRX210 out of the box. I haven't had any battery stat app running but nothing unusual is going on in the regular battery app
I have this issue as well. Drives me nuts when I'm playing clash of clans. Found a sprint forum post that says it could relate to screen protectors? I have an invisible shield on right now.
Mauk80 said:
I have this issue as well. Drives me nuts when I'm playing clash of clans. Found a sprint forum post that says it could relate to screen protectors? I have an invisible shield on right now.
Click to expand...
Click to collapse
I have a screen protector but I've never had issues with it before. The touchscreen is COMPLETELY unresponsive 100% of the time
cowkong said:
I have a screen protector but I've never had issues with it before. The touchscreen is COMPLETELY unresponsive 100% of the time
Click to expand...
Click to collapse
Have you updated to 5.1? Since 5.1, there were significant changes that appear to have been made to proximity sensor that seem to be affected by any sort of screen protector that may cover it. If your protector covers the sensor, then I suggest removing it.
I haven't. I currently have the notification on my lockscreen (since I can still use the power button and view that basic info). It simply just stopped working while I was using it. Going into the Sprint store early this afternoon
My N6 arrived yesterday and was immediately unusable. The keyboard filled in a ton of garbage when I was asked to first enter my name ... Power cycled to try again and have had nothing but reliability issues with typing at times the screen will lock while trying to type (no response) or assume I've clicked when I haven't which makes accurate data entry impossible.
wiped, reset and upgraded software from 5.0 to 5.01 to 5.1 - had to remove my ATT sim which initially blocked this process and reset. Issues are still present seems like the screen is defective.
Support has issued an RMA to return the device after suggesting they would replace. Not a great start.
im having the same issue with my nexus, i went back to stock, not even rooted anymore, still doing it, its driving me nuts..
RMA. It's quite obvious you have a hardware problem.
graydiggy said:
RMA. It's quite obvious you have a hardware problem.
Click to expand...
Click to collapse
I'm actually not so sure that it is. I've seen this issue intermittently across 3 different devices, but only on 5.1.1 firmwares.
semperfi123 said:
I'm actually not so sure that it is. I've seen this issue intermittently across 3 different devices, but only on 5.1.1 firmwares.
Click to expand...
Click to collapse
Although we're in an pls thread, I tend to agree. If it was a hardware issue, I don't think we'd see the OS acting out the touches later.. It means the hardware actually accepted the input but the OS didn't do any thing., Likely an OS hang or something.
bryancotton84 said:
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Click to expand...
Click to collapse
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues?
[email protected] said:
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues?
Click to expand...
Click to collapse
This is a N6 thread [emoji4]
I've started to have touch screen issues the past few days.
Any idea what may cause it?
Sometimes, when I touch the screen, say in settings, I touch one item, but a different item is selected somewhere randomly on the screen.
Happens in TWRP as well. If I select options to wipe, it will select others, and then it doesn't swipe over to execute the action.
No ideas? What would make touches appear where I don't touch, even on TWRP?
I tried the keyboard calibration on HTC's keyboard.
Any ideas? Screen protector?
It comes and goes.
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
mcwups1 said:
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
Click to expand...
Click to collapse
I opened another thread about a similar issue I'm having after Lollipop. My gesture launch randomly stops working and I have to reboot. No other issues for me though. I have an anti-glare screen protector on mine, but had no issues before the update. I've thought about a factory reset to see if that would cure what ails.
I'm on tmo but have the same exact issues. This is what i've found so far...
I turned on the developer options and turned on show pointer. This will show you where the touches are landing.
If you scroll down slowly, you can see most of the touches are in line (up and down) and not random on the screen.
I've removed all programs that have screen overlays (screen filter, twilight etc)
I've removed the cases thinking they might be causing the issue, but removing them only slightly improved the issue I thought...
Sometimes its hard to reproduce the effect, its not consistent. So this leads me to believe that it could be a process that's running in the background that calls attention at the moment you're touching the screen, and then refocuses the screen to your point of contact. And in between it thinks you're moving your finger when you really aren't.
In any event, I can't find the exact cause of this. But, it definitely started after the update to lollipop. I had none of these issues before. I even got the phone exchanged because I believed the digitizer went bad or something. But this issue exists on my original phone, its replacement, and now on my wife's current phone and that phones replacement (across 4 phones).
I'm currently working on my wife's replacement (4 or 5 non-oem programs installed) and continue to have the problem. But it is not consistent as I can't readily reproduce it.
What i've done to try and learn more is when I see the screen pointer light up in random places, I keep pressure on the screen so I can observe where the screen is registering contact. It almost looks as if it's trying to pull down the shade. Whether it be because of the dual points of contact and it thinks we're swiping down, or because of another program that is stealing focus for whatever reason.
If anyone else has insights into this, please let us know as this is more than frustrating! I keep calling people in hanouts with a lot of people and they aren't happy about it lol.
Also for reference, we're using ADW ex launcher instead of Stock HTC Sense. But even when I remove ADW (uninstall) and run sense, it continues to happen. So it's not that.
This is a touchscreen issue I've discovered on my phone. I was running stock 5.1 on a Nexus 6 bought back in March. I don't want to RMA due to the units they send you being refurbs. The video here isn't mine but it is another user who had a similar issue. The user was directly trying to make the swipes happen. The time that it usually occurs is during regular text messaging with swype turned on. Just don't tell me to turn off the feature though, because you'd expect to not be speed limited during texting on a near $700 phone.
Can anyone tell me if there is a way to stop this phone from performing ghost swipes? I don't understand how it happens/why it happens. I had a oneplus with this problem and it's giving me a fit that I have it here.
does it happen only when plugged in?
simms22 said:
does it happen only when plugged in?
Click to expand...
Click to collapse
It happens at any given time regardless of keyboard. I've used a couple touch screen testers like YAMTT and I could reproduce the results there as well. It's almost as if the touchscreen does not have a high enough touch recognition resolution so it makes shortcuts.
I even had an RMA unit with the same issue. My unit was made on 3/7/2015 and the RMA unit was made back in december.