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

[esmenikmatixx]

knock on seems to be working better for me now. im curious about the windowsmgr.max_events_per_sec=200
i was going to just put 90 because it made sense in what was posted earlier, but i figured better safe than sorry since im ls991 with no .tot to save me

 

[mcnick0495]

Just curious, but anyone here using the H810 (AT&T) model, and applied these changes?

 

[mdoctor]

Made a noticeable difference for me. This was a frequent issue for me, but after a couple of days with these build.prop settings, it has definitely improved, although the problem has not been completely nixed, these settings are a definite improvement. The knock-on taps work the first time almost 90% of the time (before it was about 50%). Also missed taps have greatly decreased, and swipes read as taps have greatly reduced as well. Many thanks to OP for making my G4 actually tolerable to use.

Sent from my LG-H810 using XDA Free mobile app

 

[RedOCtobyr]

**** man, I'm failing at 6 as well. My device is not rooted as I was considering sending it back for warranty. Please let us know after some testing. I mostly want to know if the swipes registering as taps still occur as frequently if at all.

I'm not quite sure what we're testing here But I can get to 10 touches. Verizon, running 611A, no touchscreen tweaks done.

 

[chrisokaly]

**** man, I'm failing at 6 as well. My device is not rooted as I was considering sending it back for warranty. Please let us know after some testing. I mostly want to know if the swipes registering as taps still occur as frequently if at all.

hey... try to lay the phone on your lap/leg and 1 by 1 add your index finger thru pinky on each side of the phone.... that is right index thru pinky on the right side of the phone, then left index thru pinky on the left side. one finger, one hand at a time. let me know if you get past 6. try your BEST not to move your fingers or the phone, and dont get too close to any of the edges

 

[mcnick0495]

hey... try to lay the phone on your lap/leg and 1 by 1 add your index finger thru pinky on each side of the phone.... that is right index thru pinky on the right side of the phone, then left index thru pinky on the left side. one finger, one hand at a time. let me know if you get past 6. try your BEST not to move your fingers or the phone, and dont get too close to any of the edges

It's a grounding issue I believe. Not sure what kind of fix is needed, but I believe it could be done through software.

And BTW, mine bugs when I try it on a table or other surface, but when in my lap or touching my body somehow it works flawlessly.

 

[uly609]

Just curious, but anyone here using the H810 (AT&T) model, and applied these changes?

I have an H810 and made the changes. You can find what I did a few pages back

 

[AegisValour]

hey... try to lay the phone on your lap/leg and 1 by 1 add your index finger thru pinky on each side of the phone.... that is right index thru pinky on the right side of the phone, then left index thru pinky on the left side. one finger, one hand at a time. let me know if you get past 6. try your BEST not to move your fingers or the phone, and dont get too close to any of the edges

I can say it's a little harder to reach 6 but that might be conditions of your test.

If I try it with a flat surface sometimes it fails at 6 sometimes it'll hold. The sides do seem a little off but the phone does rock. What were you looking for in particular?

 

[rickmatic]

It's a grounding issue I believe. Not sure what kind of fix is needed, but I believe it could be done through software.

And BTW, mine bugs when I try it on a table or other surface, but when in my lap or touching my body somehow it works flawlessly.

I thought of this with your post....

 

[spartan268]

Tried this out. It made minor improvements, but it's still there.

My test is to have the phone plugged in and try typing. This always craps out my keyboard and starts registering some words as swypes and it's a complete disaster.
After using this, I had less swypes going on, but it still occured. BUT it was less frequent. So it's a start.

Or this could all be placebo.

 

[Mr.Miyagi555]

What keyboard are you using? You could use something like swift key and make sure the swipe me is off. Totally irrelevant to the tapping issue, but would help you in your case with the swiping keyboard issue.

 

[spartan268]

What keyboard are you using? You could use something like swift key and make sure the swipe me is off. Totally irrelevant to the tapping issue, but would help you in your case with the swiping keyboard issue.

I am using swift key. Normally I like to use the Swype every now and then so the other hand is free to do my business. But honestly I'll take up your suggestion because the swype on swiftkey is absolute garbage. My HTC stock was amazing at it, but swiftkey just can't seem to get the pathing right. And the pathway I leave is spot on too.

 

[bitbitbit]

I noticed a difference when I made the changes in build.prop. Wanting to make things even better, I started removing some of the lines and see what effects they have. I also did some research on the new lines. Seems like a lot of them aren't documented anywhere.

At the end of it, I am only left with a few lines and don't notice any difference from before when I have all the suggested changes. Here is what I have now
touch.deviceType=touchScreen
touch.pressure.calibration=default
ro.min.fling_velocity=8000
ro.min_pointer_dur=8

I am not even sure if the first two lines make a difference but from reading about them on android.com, it doesn't look like they will hurt anything so I kept them. fling_velocity makes a major difference in scrolling speed. I am not entirely sure if the last line makes a difference either but I am thinking it may reduce accidental taps (when you are actually trying to swipe) so I kept it too. At one point I thought touch.pressure.scale was making a difference but from the debugging data, it doesn't look like that number was actually doing anything.

Just sharing my experience in case someone else want to tinker with the tweaks further. :good:

 

[mrcrusha829]

I wanted to state that some of the issues that people are seeing are due to the light sensor on top of the phone when it comes to double tap to wake.

This is most likely the way LG intended to make sure that the phone doesn't wake up in our pockets. You can test out my theory by putting your finger across the top to cover the sensor and with your other hand try to double tap to wake the phone.

Sent from my LG-H811 using Tapatalk

 

[frankymix]

I wanted to state that some of the issues that people are seeing are due to the light sensor on top of the phone when it comes to double tap to wake.

This is most likely the way LG intended to make sure that the phone doesn't wake up in our pockets. You can test out my theory by putting your finger across the top to cover the sensor and with your other hand try to double tap to wake the phone.

Sent from my LG-H811 using Tapatalk

Yes i tried this and it's true. The light sensor does not let double tap to wake work if covered.

Sent from my LG-H811 using Tapatalk

 

[mcnick0495]

Yes i tried this and it's true. The light sensor does not let double tap to wake work if covered.

Sent from my LG-H811 using Tapatalk

Proximity sensor, FYI.

 

[frankymix]

Not really noticing much of a difference.. Will keep you guys posted.

Sent from my LG-H811 using Tapatalk

 

[Red_Baran]

I used the Nexus 4 and the "snappier" modifications and so far I see a nice improvement. But I have only run it for a few min, I will update again later. Thank you!

 

[Milimbar]

Proximity sensor, FYI.

No, ambient light sensor, same one that auto adjusts brightness based on ambient light.
No light = no touchscreen.

 

[mcnick0495]

No, ambient light sensor, same one that auto adjusts brightness based on ambient light.
No light = no touchscreen.

There's an ambient light sensor, used to detect your ambient light and adjust brightness automatically (given you have auto brightness turned on).

Right next to it is a proximity sensor. The same thing that turns your screen off when you put your phone to your head when on a phone call.

Double tap to wake works in a pitch dark room. So it doesn't use the light sensor, but rather the proximity sensor.