Possible Fix For Touchscreen Issues/Misses (Updated 08/29)

elcom

Senior Member
Jun 21, 2008
233
68
48
I am physically not capable of registering 9 touches and taking a screenshot, but I can assure you guys that it works while laying flat on a wood table (v10f).
 

dmatteo

New member
Dec 18, 2010
1
0
0
Nope not fixed 100% ,,its better but when it on a flat surface it's going crazy and can't pinch zoom ,,and multi touch not working,,, just working with one finger,,i have v10c,,so what do you think??
I've the same problem, I think also is a ground issue. If the device is in my hand it works well, but if I left it on a table or in the car holder is impossible to use it, YAMTT doesn't detect any touch.
When it is in the car holder to use it I've to touch the back cover with a finger to use it.
My release is V10C
 
Last edited:

joshuadjohnson22

Senior Member
Oct 27, 2011
3,388
1,256
0
Atlanta
I've the same problem, I think also is a ground issue. If the device is in my hand it works well, but if I left it on a table or in the car holder is impossible to use it, YAMTT doesn't detect any touch.
When it is in the car holder to use it I've to touch the back cover with a finger.
My release is V10C

After seeing so many people with 10C still having the issue I want to think that 10f can't possibly be the same as 10c. So far no one with 10f has had the issue and said it completely resolved the issue. There must have been something different. We need to get a rom of 10F going to confirm.

Sent from my LG-H810 using XDA Forums Pro.
 
  • Like
Reactions: xchasa

nyt

Senior Member
Jun 4, 2009
90
30
0
seems to be working a good deal better with debug.egl.swapinterval at -100, but I still get some swipes interpreted as taps
 
Last edited:

shag_on_e

Senior Member
Sep 3, 2011
973
268
0
I just tried Phone Tester a fairly new hardware testing app, and unplugged it would hit 6 fingers on screen and just stop saying 6 touches, then plugged in I was able to get all 10 several times. VS986 on 11a Verizon here.

Sent from my VS986 using Tapatalk
 
  • Like
Reactions: lawrence750

shadearg

Member
May 26, 2013
11
6
0
Please could all of you, including anyone else who has done the build.prop change that I haven't quoted, perform the same test as in this video here: http://1drv.ms/1MOwkQD
I tried the test with stock build.prop, default settings. The app (YAMTT) would stop recognizing all taps after 6 on battery, but registered 10 with no problem on charger.

VS986 11A
 
Last edited:
  • Like
Reactions: lawrence750

joshuadjohnson22

Senior Member
Oct 27, 2011
3,388
1,256
0
Atlanta
Someone will probably make a rooted system image we could flash with flashfire before that happens!

Sent from my VS986 using Tapatalk
A couple things would have to line up perfectly for this to happen... and it still would be questionable:
1. Partitions would have to be exact
2. It would have to be compatible with the kernel (hopefully the fix is not in the kernel cuz unless the hardware is identical we will have to use ours)

I'm not dev so this is just what I understand, if these things aren't right it may result it bootloop, force closes or security errors. Hopefully @diedemus can get a return to stock set up, if that works we may have a shot. He may even be willing to try it out since he seems to know what he is doing.
 

Mr.Miyagi555

Senior Member
Jun 10, 2012
575
74
0
These missed taps is probably the most digusting thing about this phone. I dont understand how QA could have missed this problem.

Another thing i seen in a thread and verified myself was the max processor speed my phone uses is 1.4 ghz on bbs. Can someone else confirm this too?

---------- Post added at 08:54 AM ---------- Previous post was at 08:52 AM ----------

After i random freak bootloop i dont want to put xposed or tweak the build prop yet. It doesnt seem likely that we are going to see some update from lg for this screen issue? I know its most likely hardware but couldnt they tweak the software to soften the blow?