Related
Hi!
I recently bought an O3D and I'm getting some multi-touch problems.
As you can see, when you tap 3 times with another finger already tapping, multi-touch goes totally wrong. This happens after unlock/lock screen sometimes, and if you tap 3 times again the problem disappears.
Video from other user.
Kernel problem? Is there any solution? This makes playing multi-touch games (Nova for example) really anoying or zooming in browser with two fingers.
So sad to see the behavior of your touch screen, cause when I do the same test on my O3D it recognize 8 fingers without any problems. Are you rooted? Did you try for example my ROM to see if it makes any difference?
Sent from my amazing LG O3D using ThiaiZO3D V2.4
ThiaiZ said:
So sad to see the behavior of your touch screen, cause when I do the same test on my O3D it recognize 8 fingers without any problems. Are you rooted? Did you try for example my ROM to see if it makes any difference?
Sent from my amazing LG O3D using ThiaiZO3D V2.4
Click to expand...
Click to collapse
Mine recognizes up to 10, but when this happens only recognizes one at time. If you tap three times the problem is gone until you tap 3 times again.
I've tried with custom roms (one of them is yours), rooted, etc.
i confirm the problem...but the games looks not to be affected by it...they works perfectly.Only with touch test i have the problem...very strange and i have your rom thiaiZ...any other experice of it?
I have the same problem...
I'm on CM7 nightly 32 (for the P925 because of the Baseband problems)
but it is a bit strange.. sometimes it works and sometimes it doesnt, i don't know why
I have similar problem.
When I play a game the touch screen with 1 finger is okay but when I play with 2 fingers it stops to recognize the both fingers.
So I have to walk and then stop and then aim and then fire which sucks.
I have the same problem. Is this problem related with hardware?
hi everyone,
i tested this too and i noticed a certain pattern. If i turn off my phone and then turn it on and then run the multitouch tester i will get the issue you described. However if i turn it off and then turn it on and then move my finger from the left of the screen to the right of the screen 3 times(on the homescreen) and then I run the multitouch tester the issue is gone and the touch screen works perfect afterwards. Its a very weird bug. can someone confirm this on their phone also. If a programmer can develop an app that imitates 3 swipes when the phone unlocks then this annoyance is fixed.
Multitouch problem-any permament solution?
Have anyone found a permament solution?The thing is annoying.Has anyone got hardware fixing solution to this problem?Maybe the flat cable (placed at power button)?I've noticed it after 5 months of use.I haven't tried it myself with any other optimus 3d device.Could anyone confirm not having a problem?Btw, I use 2.35 official, without root or any kind of mod.Please, help.
rgunara said:
hi everyone,
(...)However if i turn it off and then turn it on and then move my finger from the left of the screen to the right of the screen 3 times(on the homescreen) and then I run the multitouch tester the issue is gone and the touch screen works perfect afterwards. (...)
Click to expand...
Click to collapse
Yeah, I've noticed this problem too and your three swipe solution seems to work fine. I also realised that I don't need to be on the home screen for this to work. I swiped on the tester screen itself and multitouch resumes working.
Testing with Antutu Tester I can get 10 simultaneous touches. The hard thing is to make 10 fingers fit into the screen
Sent from my LG-P920H using xda app-developers app
Hey, was playing Gameloft's Modern Combat 3 on my G2x running Eaglesblood sandwich, build 3, and i noticed something strange that greatly hindered gameplay.
The issue i was facing is that the floating analog joystick logs my input while moving the player only for like 2-3 seconds and then just reverts to its originaly postion forcing me to touch the screen again to make it register my input. This basically causes the player to move in spurts!
I don't know whether this is a game specific issue, isolated issue or an issue related to the ROM. Hope it's isolated. I'm not trying to allocate blame here, but i think the new Trinity kernel with the UMS feature that came with EB build 3 might have a different touchscreen sensitivity compared to other kernels.... dunno if im right, but just a guess.
Anyone else having similar issues?
Get "Phone Tester" from the market and go to Multi-Touch test. Hold down your fingers and move around then leave them on the screen for a bit (just imitate playing). That'll tell you if it's an application specific issue or not.
https://play.google.com/store/apps/details?id=com.mtorres.phonetester&feature=search_result
Jufjufjuf said:
Get "Phone Tester" from the market and go to Multi-Touch test. Hold down your fingers and move around then leave them on the screen for a bit (just imitate playing). That'll tell you if it's an application specific issue or not.
https://play.google.com/store/apps/details?id=com.mtorres.phonetester&feature=search_result
Click to expand...
Click to collapse
The G2x should have no problems with multi-touch. It supports up to 10-touch points simultaneously.
Theonew said:
The G2x should have no problems with multi-touch. It supports up to 10-touch points simultaneously.
Click to expand...
Click to collapse
The point of the test is to figure out whether his problem is application specific or not. Not to show whether multi-touch works but that the points stay on the screen.
Will take a look at phone tester.. Thanks
But did anyone experience similar issues?
Hi,
Does anyone else get this? When I try to use the S-pen to locate the cursor in the Google Drive app (editing a Google doc), the screen goes crazy giving haptic feedback when the S-pen approaches (not even touches) the screen. This will cause the cursor to jump about too. It makes my Google Drive App unuseable with the S-pen.
Dan
Walker Street said:
Hi,
Does anyone else get this? When I try to use the S-pen to locate the cursor in the Google Drive app (editing a Google doc), the screen goes crazy giving haptic feedback when the S-pen approaches (not even touches) the screen. This will cause the cursor to jump about too. It makes my Google Drive App unuseable with the S-pen.
Dan
Click to expand...
Click to collapse
No problem here.
Works fine for me as well.
Old thread, oh well.
Just came to say this also happens to me and is insanely annoying; so much that GDrive is literally impossible to use with the S-Pen. I thought it was because the sensitivity was too high, as is the problem usually when the pen gets twitchy, but I adjusted it to no avail.
This is with the Vzw Note 2, by the way.
Same S-pen issue with Docs
Walker Street said:
Hi,
Does anyone else get this? When I try to use the S-pen to locate the cursor in the Google Drive app (editing a Google doc), the screen goes crazy giving haptic feedback when the S-pen approaches (not even touches) the screen. This will cause the cursor to jump about too. It makes my Google Drive App unuseable with the S-pen.
Dan
Click to expand...
Click to collapse
This just started occurring with my Note 3 after the Lollipop update. Insane haptic feedback while hovering the s-pen cursor over the Screen while Docs is opened.
I love the GMD apps, including S-Pen Control & Gesture Control. I only use the S-Pen when I am writing or marking up drawings, occasionally when editing pictures, but by far, most of the time I navigate by hand.
I have used Gesture Control on numerous tablets & devices including the Nexus 10, Note 2, Note 10.1 & now the Note 8. It has worked flawlessly for the most part on every device I have used aside from the Note 8.
I have contacted the developer about the issue, which is that the "Back" function fails because the InputDispatcher drops the call. "Back" works fine using GMD S-Pen Control, but not on Gesture Control.
What I am wondering, since I don't see the complaint anywhere else, is if anyone else is using the app & having the same issue.
I have pulled a logcat for the app, so I know it is not a SuperUser issue, but nobody else seems to be reporting the issue, so either it is working for other, or I am the only one using GMD Gesture Control on the Galaxy Note 8.
Anyone else using this app & either having this issue?
GSLEON3 said:
I love the GMD apps, including S-Pen Control & Gesture Control. I only use the S-Pen when I am writing or marking up drawings, occasionally when editing pictures, but by far, most of the time I navigate by hand.
I have used Gesture Control on numerous tablets & devices including the Nexus 10, Note 2, Note 10.1 & now the Note 8. It has worked flawlessly for the most part on every device I have used aside from the Note 8.
I have contacted the developer about the issue, which is that the "Back" function fails because the InputDispatcher drops the call. "Back" works fine using GMD S-Pen Control, but not on Gesture Control.
What I am wondering, since I don't see the complaint anywhere else, is if anyone else is using the app & having the same issue.
I have pulled a logcat for the app, so I know it is not a SuperUser issue, but nobody else seems to be reporting the issue, so either it is working for other, or I am the only one using GMD Gesture Control on the Galaxy Note 8.
Anyone else using this app & either having this issue?
Click to expand...
Click to collapse
I have been having the same issues. I thought it was me or another app. I have the same two GMD apps. S-Pen no issues. Gesture Control "Back" is hit or miss most to the time miss.
same problem
GSLEON3 said:
I love the GMD apps, including S-Pen Control & Gesture Control. I only use the S-Pen when I am writing or marking up drawings, occasionally when editing pictures, but by far, most of the time I navigate by hand.
I have used Gesture Control on numerous tablets & devices including the Nexus 10, Note 2, Note 10.1 & now the Note 8. It has worked flawlessly for the most part on every device I have used aside from the Note 8.
I have contacted the developer about the issue, which is that the "Back" function fails because the InputDispatcher drops the call. "Back" works fine using GMD S-Pen Control, but not on Gesture Control.
What I am wondering, since I don't see the complaint anywhere else, is if anyone else is using the app & having the same issue.
I have pulled a logcat for the app, so I know it is not a SuperUser issue, but nobody else seems to be reporting the issue, so either it is working for other, or I am the only one using GMD Gesture Control on the Galaxy Note 8.
Anyone else using this app & either having this issue?
Click to expand...
Click to collapse
Works intermittently, seems to be very dependant on what app is open ie: greader pro, can three finger back from read article to summary list 90% of times but get zero response while on summary page, should return me to desktop but just flashes 'back' indicator but no flash from capacitive buttons and no action occurs.
Terry
I have the same issue. I created a custom gesture of one touch point DL and that almost leads registers. The default three touch swipe down doesn't work so I disabled it the created a customer gesture to do the same thing. It works intermittently. I contacted the developer to let him/her know. I followed the directions as well om the FAQ on his website regarding SuperSU.
Sent from my GT-N5110 using XDA Premium HD app
I've been having this issue as well.
It's not only the gmd app, but I changed my dpi in build.prop to enable tablet mode when I disabled the capacitive buttons and the back button on the nav bar acts the same way.
Must be a bug in the firmware I guess.
wrangla said:
I've been having this issue as well.
It's not only the gmd app, but I changed my dpi in build.prop to enable tablet mode when I disabled the capacitive buttons and the back button on the nav bar acts the same way.
Must be a bug in the firmware I guess.
Click to expand...
Click to collapse
I am seeing the same issue as well. Any response from the developer yet? Should I also reported the issue to the development?
I had the same problem. For me, activating "Evaluate gestures only on release" in "settings" and restarting ("Restart Service") solved the issue.
Gesendet von meinem GT-N8010 mit Tapatalk 2
griesbau said:
I had the same problem. For me, activating "Evaluate gestures only on release" in "settings" and restarting ("Restart Service") solved the issue.
Gesendet von meinem GT-N8010 mit Tapatalk 2
Click to expand...
Click to collapse
I just tried the same but no luck. Did restart the service and everything but still experiencing the same intermittent "back gesture not working" issue. It doesn't seem to be dependent on the app being used. I sometimes keep trying and repeating the gesture and sometimes it eventually works. Tried all that superuser and supersu but to no avail.
Hope developer knows how to fix it.
Thanks for the pointer anyway.
griesbau said:
I had the same problem. For me, activating "Evaluate gestures only on release" in "settings" and restarting ("Restart Service") solved the issue.
Thanks for the tips, seems work for me as well .
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
+1
Any news on this? Setting the evaluate option seems to improve it a bit, but still more than 50% of my back gestures are not evaluated
Gesendet von meinem GT-N5100 mit Tapatalk 2
Hello friends, to begin with, I would like to clarify that I play with two individual triggers, but the error also occurs when I use all four fingers.
My problem is that after 30 or 40 seconds of play I can no longer aim (use the scope)(right side) without first having to lift my right thumb off the screen.
I hope you can help me with this problem since it is very annoying to have to stop touching the screen with my right thumb to be able to aim (use the scope)
Has anyone had that problem when playing PUBG with the S22 Ultra?
Same here been trying to figure out a way to fix it, its really annoying
Bot_droid said:
Same here been trying to figure out a way to fix it, its really annoying
Click to expand...
Click to collapse
Yes and it seems that it only happens to Samsung. The same thing happened to me with an S20+ and now with the S22Ultra. It seems that no one has a solution.