<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Tap timeout seems too low" href="https://bugs.freedesktop.org/show_bug.cgi?id=99447#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Tap timeout seems too low" href="https://bugs.freedesktop.org/show_bug.cgi?id=99447">bug 99447</a> from <a class="email" href="mailto:grawity@gmail.com" title="Mantas Mikulėnas <grawity@gmail.com>"> Mantas Mikulėnas</a> <pre>Can confirm. I remember the blog post said "Some users may see a drop in tap detection rate. This is hopefully a subconscious enough effect that those users learn to tap faster or with less movement"... But, well, it's very noticeable. (At first there were occassions where it'd only pick up every 3rd or 4th tap, so instinctually I kept trying to tap *harder*, but that of course doesn't help when the driver wants shorter taps... Now I'm pretending that the touchpad is lava.) That said: I did some evemu|awk to report the BTN_TOUCH duration and noticed that a very large part of my taps show up as being ~83 ms, ~93 ms, ~104 ms, ~114 ms, or [rarely] ~124 ms long. (For example, I got 114.174, 114.439, 114.010, 114.458, and 114.538 *in a row*). Could it be that the touchpad or the kernel only reports every ~10 ms, because I don't think my tapping was *that* precise? So while I haven't tested it yet, I'd probably be fine with 120 ms as the threshold. (This is Dell Inspiron 5547, with Synaptics over I2C. Haven't tested the update on my old Asus yet.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>