<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c15">Comment # 15</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 <a class="email" href="mailto:Hi-Angel@yandex.ru" title="Hi-Angel <Hi-Angel@yandex.ru>"> Hi-Angel</a> <pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=105043#c14">comment #14</a>) > (In reply to Hi-Angel from <a href="show_bug.cgi?id=105043#c13">comment #13</a>) > > Np, I did the record with the option; will try the kernel boot option, but a > > bit later — I'm travelling, don't have ATM a live-usb/cd to boot from if I > > screw up something. > > add it manually on boot instead of writing into the grub.cfg and the worst > thing that can happen is that you don't have a touchpad :) > > > event7 - tap state: TAP_STATE_IDLE → TAP_EVENT_TOUCH → TAP_STATE_TOUCH > > event7 - tap state: TAP_STATE_TOUCH → TAP_EVENT_TOUCH → TAP_STATE_TOUCH_2 > > event7 - tap state: TAP_STATE_TOUCH_2 → TAP_EVENT_MOTION → > > TAP_STATE_TOUCH_2_HOLD > > event7 - tap state: TAP_STATE_TOUCH_2_HOLD → TAP_EVENT_MOTION → > > TAP_STATE_TOUCH_2_HOLD > > translation: idle to 'one finger down' to 'two fingers down' to 'motion > threshold exceeded'. if you have the git repo, there is a > touchpad-tap-state-machine.svg that illustrates all this. try not to scream > when you see it first ;) Thanks, I like the graph, though I think being svg is not good. I think such graph would be nicer in html, or something alike that would allow a text search/highlight. > > event7 - tap state: TAP_STATE_TOUCH_2 → TAP_EVENT_MOTION → > > TAP_STATE_TOUCH_2_HOLD > > same here - you're getting motion events when the second finger is down, > exceeding the internal thresholds and we go from tap to just 'two fingers > down'. note that the state machine is independent of everything else, so > tapping is in the 'two fingers down' state when e.g. you're two-finger > scrolling. > > The 'button state' debug events are for the software button state, unrelated > again. Thanks, I think I see. For the record, I might be getting motion events of fingers down because I'm also affected by #104828 aka "wobbly touchpad". 2 days ago I did also override hysteresis locally to have it always enabled — and I think this codepath ought to remove the motion before deciding if the user is scrolling or not.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>