<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Touchpad very sensitive" href="https://bugs.freedesktop.org/show_bug.cgi?id=98835#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Touchpad very sensitive" href="https://bugs.freedesktop.org/show_bug.cgi?id=98835">bug 98835</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>Note that the below is half archiving of my thoughts as well as a real comment :) (In reply to arjon.bujupi from <a href="show_bug.cgi?id=98835#c8">comment #8</a>) > Created <a href="attachment.cgi?id=128359" name="attach_128359" title="second.evemu">attachment 128359</a> <a href="attachment.cgi?id=128359&action=edit" title="second.evemu">[details]</a> > second.evemu reminder: this was the fast left-right motion slight no-motion at the beginning but then a curving motion to the right, so the finger movement is nicely visible. Almost all of that motion falls into the maximum acceleration, i.e. the area where we don't scale further but merely apply the maximum acceleration factor - that's true almost from the beginning of the motion onwards. I guess if it goes that easily to the right edge of the screen, we need to adjust motion speed that the current max acceleration is triggered much later. In this recording you're reaching the max acceleration factor early despite going 4 times as fast later. (In reply to arjon.bujupi from <a href="show_bug.cgi?id=98835#c9">comment #9</a>) > Created <a href="attachment.cgi?id=128360" name="attach_128360" title="third.evemu">attachment 128360</a> <a href="attachment.cgi?id=128360&action=edit" title="third.evemu">[details]</a> > third.evemu reminder: this was the 2cm click motion. I can see by the motion vectors that you overshot a little. most of your movement falls into the 'acceleration' range, i.e. before we cap the maximum factor. The immediate first and last movements (i.e. the ones after the overshoot) were decelerated. Would you say that that cursor movement was still too fast when correcting for the overshoot (and moving slower)? Is there a speed setting that makes your touchpad usable for this action? Most recent suggestion was -0.55 which apparently makes it like macos' touchpad movement. try with xinput "ETPS/2 Elantech Touchpad" "libinput Accel Speed" -0.55, and try some other values too please (anything between -1.0 and 0.0 slows down)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>