I've been effected by this problem for a while now, it's an issue on stock and cyanogen's rom. So far as I can tell a phantom input is detected at a very specific location on the touch screen provided the primary input is within a specific range along the vertical axis.
I've taken screenshots with the Pointer Location Tool in Dev Tools and wrote a short description of what's going on in each screenshot. This seems to go show up and go away sporadically, seemingly for no reason.
Screenshots here:
http://dl.dropbox.com/u/1620808/touchscreen_bug.zip
If I rotate the screen once and back, the single input part of the bug goes away, if I use two fingers though as shown in one of the screenshots, the bug is still there. Then after letting the screen sleep for a minute or two, it's completely gone.
Anyone else with this problem?
This is a known problem, there are two many threads already stating this
The phone is not yet fully supporting multitouch 100% it only has pinch and zoom, CM has said he found something in the framework that is disabled and should fix this when enabled (but not completly fix all multi touch issues)
I'm not entirely sure how much of this problem is a multitouch issue. I've noticed in particular that when I touch a specific area of the screen, it registers in that place and in a second place that always has a fixed point along the y axis.
This often makes scrolling a pain as I am only able to flick up in the area above the affected location.
This problem can also make typing a pain when I type on the second from bottom row and instead end up hitting the bottom row.
Related
I am not sure whether it is my mind playing trick with me or not, but I feel like my phone is less sensitive after I did the hard reset (power+volume down). Sometimes I need to press 2-3 times because the first light tap was not detected.
So is there anyway to increase the sensitivity?
I have the same problem, but no idea that is the hardware or only software problem.....
Fresh owner of this Optimus 2X in France, in our community, frandroid.com, we encounter the same problem , I think this is a software issue.
Did someone already contact LG??
Maybe they should include this into the bug list thread.
May I know were you guys having this problem since it is out of the box? or after reset?
I have the same problem started from day 1 till now
I have the same issue and already thought I'd be the only one having this problem.
I would not say it's a problem with sensitivity, but it feels like the touchscreen goes into some kind of sleepmode where then you need to press a second time, to wake it up.
Continuous touching is no problem. (like when typing rapidly on the keyboard)
This video is not from me, but it shows the problem.
Have a look at 13:28 and 13:37. The reviewer tries to hit the "Ackermann" entry, but the touchscreen does not recognize the touch. At 13:37 the guy has to press another time to get the entry selected.
http://www.youtube.com/watch?v=VRid-Yhu7Gg&feature=player_embedded
Yes! The touchscreen is definitely less sensitive than my old HTC Hero, and gets quite frustrating sometimes when a scroll misses the first part of the movement or a click is missed.
Sent from my LG-P990 using XDA App
just in case, are you guys using 20110218 baseband too?
The same problem here. If I unlock the screen and then tap on any on screen apps, I need to touch again for it to open. Only the first time though, after that it function ok. I think this is a bug and needs to be fixed... I have my pc for double-click.
Yep, count me in. Same problem here. Sometimes screen taps aren't registered. Will do some research later on, but I think it's a software problem. (maybe you have to tap 2x as fast )
Hi,
same problem here!
Potentially a driver issue. A Nexus S user had a similar issue in this thread: http://forum.cyanogenmod.com/topic/18431-tuning-driver-to-deal-with-unresponsive-touchscreen/
He managed to tweak the driver and it works fine now. Need to know C++ (I think?) to understand though.
9mmBullet said:
Potentially a driver issue. A Nexus S user had a similar issue in this thread: http://forum.cyanogenmod.com/topic/18431-tuning-driver-to-deal-with-unresponsive-touchscreen/
He managed to tweak the driver and it works fine now. Need to know C++ (I think?) to understand though.
Click to expand...
Click to collapse
I see, then probably they will fix it on the next update/gingerbread?
Same issue here.
Correct me if I'm wrong, but the problem seems to be that the screen has zero tolerance when it comes to tapping and swiping together. If you tap and slide your finger a bit directly after the tap, the tap is ignored. In other words your tap has to be a steady tap when you click on a button or an app. Right on the spot and with no swiping or sliding afterwards. I can't reproduce this on any of my other devices.
Ergo, it seems that the natural tapping I'm used to isn't working on the x2. It seems like I have to adjust my tap. I think that this could in principle be solved with a setting somewhere, because clearly the x2 is capable of registering this in for example a web page.
The great thing of this is that you can safely tap and swipe in the app drawer to scroll up and down or left and right. The downside is that a tap with a little swipe isn't registered at all. I would say that LG has choosen here for a wrong setting.
My personal experience about screen sensivity.. can you confirm if it's the same for your device?
I noticed a strange touch response.. and after some tests, I can say that the touch screen and icons are influenced by the surface where the phone was put!
with the phone in my hands, it's all ok (only sometimes - rare - I need to tap more than once).
If I put the phone over a glass surface (like a glass table) without touching it with both hands, the touch and the icons not respond!! NEVER!
If I put the phone on my scanner the touch screen works ok, but the icons not (or only few and rare taps was detected).!
If I put the phone over my big Onkyo amplifier.. It works like in my hands.. or better!! even without touching with hands.. only with a finger!
Put it back on my glass table.. and all stop working again. If I put a aluminium foil under the phone (between phone and table).. the touch and the icons works again !!
If I put it on the bed.. it don't work.
LG support say that they have tested the phone about this issue after my report.. but no strange response was detected by them. I don't know if they really tested it..
Try it and let me know what you think about!
tested on glass surface, I can press and swipe through pages with a finger without problem.
it is true that my device is not so responsive, but aint reaching that level yet
i read about a similar behaviour on other devices because some devices need a proper grounding for the capacitive screen to work correctly. You can find this problem via google.
Some devices have problem in a car-mounting, for example.
But i think thats not the problem the thread-opener talked about?
Guys I'm looking to get this phone and after reading Engadgets review of the X2 where they mention that the screen is not as sensitive to the touch as other phones I got a bit worried and started googling which lead me here!
Is this true? The screen isn't very sensitive and you have to apply more pressure than other capacitive phones?
I know that the OP is talking about a different issue but I reckon LG will get that sorted out via software update, or at least hope so!
Please do post your experience about the screen sensitivity of the X2 as this is putting me off. I currently have the Motorola Milestone 2 which is very sensitive to the touch even with a screen protector on it.
Cheers
My Note seems unable (or unwilling) to detect touchscreen contact within a relatively small margin of each edge.
Using the 'Pointer location' option in Developer Options, I can see that no matter where along the edge I put my finger, it seems to clamp it to 20px away from the edge. Taking the left edge, for an example, I can see the line tracking my finger up until I hit the margin, and then it will go no further left. It is still detecting the press, though, moving my finger up and down will result in a perfectly straight line being drawn parallel to the edge of the screen.
I'm using PA3 (RC3). Either the problem doesn't exist or I just didn't notice on stock. I only became aware of it when attempting to mess around with the new 'Pie' thing in PA, and realising that it's somewhat difficult for PA to detect the gesture when the edge of the screen isn't registering the touch!
I'd appreciate it if anyone could quickly check whether their Note has the same issue, or if anyone is aware of a way of expanding the area on which touches will be registered.
Aryzvalos said:
My Note seems unable (or unwilling) to detect touchscreen contact within a relatively small margin of each edge.
Using the 'Pointer location' option in Developer Options, I can see that no matter where along the edge I put my finger, it seems to clamp it to 20px away from the edge. Taking the left edge, for an example, I can see the line tracking my finger up until I hit the margin, and then it will go no further left. It is still detecting the press, though, moving my finger up and down will result in a perfectly straight line being drawn parallel to the edge of the screen.
I'm using PA3 (RC3). Either the problem doesn't exist or I just didn't notice on stock. I only became aware of it when attempting to mess around with the new 'Pie' thing in PA, and realising that it's somewhat difficult for PA to detect the gesture when the edge of the screen isn't registering the touch!
I'd appreciate it if anyone could quickly check whether their Note has the same issue, or if anyone is aware of a way of expanding the area on which touches will be registered.
Click to expand...
Click to collapse
try the touch screen benchmark app found on the play store to know if you have any problem with the touch screen
terminator_5505 said:
try the touch screen benchmark app found on the play store to know if you have any problem with the touch screen
Click to expand...
Click to collapse
I wasn't sure to which app you were referring, but I found one that was able to fairly clearly show the issue. I took a screenshot and attached it to this post.
Each of those lines was drawn from or to the edge of the screen. You can see they all stop significantly before the boundary. The app is ScreenTouchTest, if someone would mind repeating the experiment and seeing what results they get!
Same thing happens with me. However, when using the S-Pen, the boundary gets to the right, ie the screen area increases. Here are two screen shots, one with finger and the other with S-Pen.
P.S: sorry for the big pictures...
Dial *#0*# and do a screen test..
Sent from my GT-N7000 using Tapatalk 2
Is anyone experiencing touches being registered slightly off target from where you are actually touching the screen? When I enable Settings > Developer Options > "Show touches" and "Pointer location", I see that touches register significantly lower and to the right of where the tip of my finger touches the screen. In the screenshot, you can see that the crosshair and circle are not aligning; the white circle appears to be what is actually registered when using the phone.
This seems like a software/kernel issue. I'm surprised no one else has mentioned this yet..it's very annoying!
neemoxtrm said:
Is anyone experiencing touches being registered slightly off target from where you are actually touching the screen? When I enable Settings > Developer Options > "Show touches" and "Pointer location", I see that touches register significantly lower and to the right of where the tip of my finger touches the screen. In the screenshot, you can see that the crosshair and circle are not aligning; the white circle appears to be what is actually registered when using the phone.
This seems like a software/kernel issue. I'm surprised no one else has mentioned this yet..it's very annoying!
Click to expand...
Click to collapse
whoa!! never realise until you mention it.. yea im having that problem too!! im using international version and original made in Taiwan itself.. any custom kernel solve this already??:silly:
I wonder if this is related to the problems people are experiencing using the home key and back key. If touches aren't registering in the right place, surely this could exacerbate an already existing fault with sensitivity of these 'keys'
Currently interchangeably using HTC One, BBZ10 and Note 2
Have you tried using the calibration tool under Settings -> Language & Keyboard -> HTC Sense Input -> Advanced -> Calibration tool? Not sure if this would make a difference in your case.
Apparently touching the screen very lightly while using the calibration tool helps capacitive button sensitivity for some people, as well.
mang0 said:
Have you tried using the calibration tool under Settings -> Language & Keyboard -> HTC Sense Input -> Advanced -> Calibration tool? Not sure if this would make a difference in your case.
Apparently touching the screen very lightly while using the calibration tool helps capacitive button sensitivity for some people, as well.
Click to expand...
Click to collapse
That's not changing anything for me. Are you able to confirm whether or not touches are being registered off-target?
i have the same issue
anyone has an ideo to solve this problem?
I almost think that's how it's supposed to be. It's not putting up an X for you to try and touch, it just showing you where you are touching. Now if it was putting up a target for you to try for and it was off that would be different.
stevessvt said:
I almost think that's how it's supposed to be. It's not putting up an X for you to try and touch, it just showing you where you are touching. Now if it was putting up a target for you to try for and it was off that would be different.
Click to expand...
Click to collapse
It makes sense if they assume that most people are using it one handed with the right hand. You usually would hit the point you are trying to hit a bit low and to the right. But in other cases, you might not.
It's strange. Where the lines intersect is exactly where I touch, so it knows where I am touching. But the circle is always lower right.
Anyone that has received the 1.29 update try this out? Is it fixed? Ive tested this out on other devices and the circle is always where the lines intersect, not like the One.
Happening on mine, too, I just tested it.
It would be one thing if the system weren't reading the coordinates correctly, but it appears that it is.. it's just registering the action off target. That strikes me more as a software/calibration issue. This explains why I've had a hard time hitting very small links on webpages in Firefox.. I'm touching dead on the link, but it's not registering it there.
Hurricane9 said:
It makes sense if they assume that most people are using it one handed with the right hand. You usually would hit the point you are trying to hit a bit low and to the right. But in other cases, you might not.
Click to expand...
Click to collapse
I don't get this. We've all been using smart phones long enough to know where we're touching the screen and how to do it properly. They shouldn't be trying to compensate for anything, and I hope there's a function somewhere that allows us to recalibrate or turn whatever this is off, so that it simply registers the actions at the exact point of contact.
Do you have the 1.29 update, or an older version?
1.26.502.10. Stock AT&T. Unlocked & rooted, but not ROMd.
mine register where I touch them( 1.29.401.12), yet I feel I am missing more links in the browser than before (but that might be a browser problem, before I used opera mobile)
Hey guys,
I turned on the two developer options and then used a drawing app to confirm where the touches were being registered. It turns out my touches were registering at the intersection of the two lines (which is where I'm actually touching) instead of the circle. Looks like there's really nothing wrong here, other than the way they are displaying that little circle thingy.
Sent from my HTC One using xda app-developers app
I have tested the phone lot , but I haven't noticed this issue. I am even surprised of the touchscreen. I have never seen such a perfectly visible display. I pressed gently and it reacts as normal.
To people with this problem. Did your last phone is Samsung Galaxy? Or have you ever been a longer Samsung user?
I ask cause I have this problem ONLY on Galaxy phones. When I use HTC , even Wildfire It have superior reactions of the touchscreen.
Yeah, even though it seems off, my touches are registering right at the intersection.
I first noticed this on a running game where you have to hold down either the left or right side of the screen to move in that direction. It would usually register the first press, but not that I had held my finger down so I wasnt moving properly. I thought this was due to the game it's self rather than my phone.
I've just downloaded Naugh where you have to rotate the screen by touching either side of the phone, and again the same issue. It's really unresponsive - It will recognise the tap but not that i've held it, it will stop working. Occasionaly this will also happen when scrolling a page.
I did a quick google search and found that the Z1 had this issue, but havent found a fix.
Has anyone else experienced this? Or if not, any suggestions on figuring out whats wrong?
Edit: I recorded a video of exactly what I mean: https://www.youtube.com/watch?v=UW2gCWpThWc
I don't know if my problem with my screen is related to yours, but i'm experiencing some problems as well.
On the picture i attached in this post is a picture taken of my screen with a black background.
In the middle of the screen there is a slight discolouring, and in this particular spot the touch screen is very unresponsive, i'm especially noticing this when playing candy crush, making it almost impossible to swap the two candies in this particular spot
Both of these sound a bit like my problem was at first, but mine quickly got worse (in hours) and then I found the hairline crack in the screen.
Bottom corner and not in a part of the screen that displays anything - just the 'glass' front at the bottom - but a third of the screen near the middle doesn't respond to touch.
It gradually got worse over a couple of hours until it stopped responding altogether.
I'm having a weird issue with a phone that I'm otherwise completely happy.
The screen feels too sensitive to the touch, which in turn makes pretty difficult to type quickly or results in many accidental presses.
Running the latest Lineage OS 20.0.
To reproduce:
Open keyboard, and hover your thumb over a key. SLOWLY move it closer to the screen where it's touching lightly. You should get ridiculous key spam, like a full row in 1 second.
Possible issue:
It appears that the 'finger' area required for a touch to be registered is too small
What I've tried:
Disabling haptics, different keyboard, changing "Cursor speed", a Magisk module that was supposed to add touchscreen sensitivity control.
Any pointers are very welcome, thank you!
empy16 said:
I'm having a weird issue with a phone that I'm otherwise completely happy.
The screen feels too sensitive to the touch, which in turn makes pretty difficult to type quickly or results in many accidental presses.
Running the latest Lineage OS 20.0.
To reproduce:
Open keyboard, and hover your thumb over a key. SLOWLY move it closer to the screen where it's touching lightly. You should get ridiculous key spam, like a full row in 1 second.
Possible issue:
It appears that the 'finger' area required for a touch to be registered is too small
What I've tried:
Disabling haptics, different keyboard, changing "Cursor speed", a Magisk module that was supposed to add touchscreen sensitivity control.
Any pointers are very welcome, thank you!
Click to expand...
Click to collapse
I can recreate this as well. I don't really see how it could be a problem. I don't get accidental touches, in fact I find that the screen isn't sensitive enough and sometimes it doesn't register touches. The phone had a touch problem in Android 11 where it wouldn't register touches and I guess the devs tried everything they could to fix a display that was just too garbage to be saved anyway, so now we're stuck with how it is. I guess you could try a GSI with open source drivers that you could edit yourself since the drivers we have are closed source and the custom ROM devs (which should know better than anyone else) told me they couldn't fix it since they didn't have access to the drivers.