On 3/23/21 10:39 PM, Klemens Nanni wrote: > On Tue, Mar 23, 2021 at 09:29:09PM +0100, Ulf Brosziewski wrote: >> In order to distinguish tap gestures from short movements, the touchpad >> input driver in wsmouse checks whether the distance between the initial >> and the last position of a touch exceeds the 'maxdist' limit. Some >> touchpads provide unreliable coordinates when more than one contact is >> being made simultaneously, and in this case the filter may be too strong >> - and superfluous, because only one-finger contacts should trigger pointer >> movement; it should be safe to skip the test for multi-finger contacts >> (with Non-MT-touchpads, it isn't possible anyway). > This fixes it for me on the ThinkPad X230 but it seems to have no > effect on the Pinebook Pro where double and triple taps are barely^Wnot > recognised at all.
This means we have two distinct issues here. On the Thinkpad, it's coordinates, on the Pinebook, it's the timing - as your logs have shown, there are either overlong delays between some reports, or the clock is irregular. Some events are missing. I'm afraid that there is no quick solution for the Pinebook problem. A quick web search suggests that it is not rare with this hardware; however, I haven't looked at any details yet. > > Do you want me to provide the same logs with this diff? > Anything specific order/test/action/whatever I can carry out? > I think a new log isn't necessary at present. I'll try to find out more, and if I can come up with new insights or ideas, you'll hear from me.
