<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - 3-fingers touch occasionally fails to get detected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105043#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - 3-fingers touch occasionally fails to get detected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105043">bug 105043</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>libinput converts the touches into relative motion, or taps, or scrolling, etc.
But libinput cannot *detect* the touches [1], that has to be done by the
firmware. The kernel sets BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP and
BTN_TOOL_TRIPLETAP together with the slot data (which is what we use where
available), so that's the easiest and quickest way to check if a finger is
detected at all.
Easiest way to verify if that is (part of) the issue is running evemu-record
|grep BTN_TOOL and checking that output while tapping. If you don't see
TRIPLETAP every time you three-finger tap, then that's the source of that.
Slower tapping can help, might be you're really too fast for the device to
detect contact.
Without that data, we can't do that much. So in this particular recording, the
only one we could fix in libinput is the one that's also detected as a palm,
but not the other two.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>