[Wayland-bugs] [Bug 99695] Can't manage acceleration profile on HP 255 G5 "SynPS/2 Synaptics TouchPad"
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Feb 20 10:01:57 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=99695
--- Comment #21 from Giuseppe Margarita <giuseppemargarita at gmail.com> ---
(In reply to Peter Hutterer from comment #20)
> for a <6mm movement you get a 70 pixel movement. That seems about alright
> compared to what I have here (with the default 0.0 setting).
> fwiw, the 'flat' acceleration profile would give you 226 pixels - clearly
> not useful.
Wait, I have -0.4 acceleration speed as stated in the previous comments (I
can't set it from Plasma system settings, but I set it from an autostart
script).
Default 0.0 is too fast for me.
> a factor of 0.4 should be a roughly 1:1 movement between the finger and the
> pointer on the screen, is this correct? If that's not the case, do
> different-length movements reflect this?
This is often correct, but sometimes I get 0.3.
If I do a >6mm movement with always the same speed, I get always 0.4.
But when the speed is not the same, maybe if I slow it on the end of the
movement, sometimes I get 0.3.
button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to
BUTTON_STATE_NONE
event13: touch movement 8.0mm, pixels 103.3, raw px 314.3, avg factor 0.3
button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to
BUTTON_STATE_NONE
event13: touch movement 12.1mm, pixels 165.0, raw px 474.4, avg factor 0.3
event13 POINTER_MOTION +8.62s 0.35/ 0.00
event13 POINTER_MOTION +8.63s 0.54/ 0.00
event13 POINTER_MOTION +8.64s 0.64/ 0.00
event13 POINTER_MOTION +8.65s 1.11/ 0.00
event13 POINTER_MOTION +8.66s 1.29/ 0.00
event13 POINTER_MOTION +8.67s 1.44/ 0.00
event13 POINTER_MOTION +8.68s 1.58/ 0.00
event13 POINTER_MOTION +8.69s 1.70/ 0.00
event13 POINTER_MOTION +8.70s 1.81/ 0.00
event13 POINTER_MOTION +8.71s 2.58/ 0.00
event13 POINTER_MOTION +8.72s 2.77/ 0.00
event13 POINTER_MOTION +8.73s 2.17/ 0.00
event13 POINTER_MOTION +8.74s 2.91/ 0.00
event13 POINTER_MOTION +8.75s 2.91/ 0.00
event13 POINTER_MOTION +8.76s 2.91/ 0.00
event13 POINTER_MOTION +8.77s 2.91/ 0.00
event13 POINTER_MOTION +8.78s 2.55/ 0.00
event13 POINTER_MOTION +8.79s 3.64/ 0.00
event13 POINTER_MOTION +8.80s 2.91/ 0.00
event13 POINTER_MOTION +8.81s 3.64/ 0.00
event13 POINTER_MOTION +8.82s 4.37/ 0.00
event13 POINTER_MOTION +8.83s 3.64/ 0.00
event13 POINTER_MOTION +8.84s 3.64/ 0.00
event13 POINTER_MOTION +8.85s 4.01/ 0.00
event13 POINTER_MOTION +8.86s 2.91/ 0.00
event13 POINTER_MOTION +8.87s 2.91/ 0.00
event13 POINTER_MOTION +8.88s 2.19/ 0.00
event13 POINTER_MOTION +8.89s 2.19/ 0.00
event13 POINTER_MOTION +8.90s 2.19/ 0.00
event13 POINTER_MOTION +8.91s 1.46/ 0.00
event13 POINTER_MOTION +8.92s 1.46/ 0.00
event13 POINTER_MOTION +8.93s 0.73/ 0.00
event13 POINTER_MOTION +8.94s 0.73/ 0.00
event13 POINTER_MOTION +8.95s 0.73/ 0.00
event13 POINTER_MOTION +8.96s 0.73/ 0.00
event13 POINTER_MOTION +8.97s 0.73/ 0.34
event13 POINTER_MOTION +8.98s 0.36/ 0.83
button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to
BUTTON_STATE_NONE
event13: touch movement 14.2mm, pixels 194.7, raw px 557.2, avg factor 0.3
event13 POINTER_MOTION +36.72s 0.48/ 0.00
event13 POINTER_MOTION +36.73s 3.58/ 0.00
event13 POINTER_MOTION +36.74s 3.48/ 0.00
event13 POINTER_MOTION +36.75s 4.87/ 0.00
event13 POINTER_MOTION +36.76s 3.64/ 0.00
event13 POINTER_MOTION +36.77s 3.64/ 0.00
event13 POINTER_MOTION +36.78s 3.64/ 0.00
event13 POINTER_MOTION +36.79s 3.64/ 0.00
event13 POINTER_MOTION +36.80s 3.64/ 0.17
event13 POINTER_MOTION +36.81s 4.37/ 0.00
event13 POINTER_MOTION +36.82s 4.37/ 0.00
event13 POINTER_MOTION +36.83s 5.10/ 0.00
event13 POINTER_MOTION +36.84s 4.37/ 0.00
event13 POINTER_MOTION +36.85s 3.64/ 0.00
event13 POINTER_MOTION +36.86s 3.64/ 0.00
event13 POINTER_MOTION +36.87s 3.64/ 0.00
event13 POINTER_MOTION +36.88s 2.91/ 0.00
event13 POINTER_MOTION +36.89s 2.91/ 0.00
event13 POINTER_MOTION +36.90s 2.91/ 0.00
event13 POINTER_MOTION +36.91s 2.91/ 0.00
event13 POINTER_MOTION +36.92s 2.91/ 0.00
event13 POINTER_MOTION +36.93s 2.91/ 0.00
event13 POINTER_MOTION +36.94s 2.91/ 0.00
event13 POINTER_MOTION +36.95s 2.91/ 0.00
event13 POINTER_MOTION +36.96s 2.91/ 0.00
event13 POINTER_MOTION +36.97s 2.91/ 0.00
event13 POINTER_MOTION +36.98s 2.91/ 0.00
event13 POINTER_MOTION +36.99s 2.91/ 0.00
event13 POINTER_MOTION +37.00s 2.91/ 0.00
event13 POINTER_MOTION +37.01s 2.91/ 0.00
event13 POINTER_MOTION +37.02s 2.55/ 1.02
event13 POINTER_MOTION +37.03s 2.91/ 0.68
event13 POINTER_MOTION +37.04s 2.19/ 0.00
event13 POINTER_MOTION +37.05s 2.19/ 0.00
event13 POINTER_MOTION +37.06s 2.19/ 0.00
event13 POINTER_MOTION +37.07s 2.19/ 0.00
event13 POINTER_MOTION +37.08s 2.19/ 0.51
event13 POINTER_MOTION +37.09s 1.46/ 0.68
event13 POINTER_MOTION +37.10s 2.19/ 0.17
event13 POINTER_MOTION +37.11s 1.46/ 0.00
event13 POINTER_MOTION +37.12s 1.46/ 0.68
event13 POINTER_MOTION +37.13s 1.46/ 0.00
event13 POINTER_MOTION +37.14s 2.55/ 0.85
event13 POINTER_MOTION +37.15s 0.73/ 0.17
event13 POINTER_MOTION +37.16s 1.46/ 0.68
event13 POINTER_MOTION +37.17s 0.73/ 0.00
event13 POINTER_MOTION +37.18s 0.72/ 0.67
event13 POINTER_MOTION +37.19s 0.65/ 0.00
event13 POINTER_MOTION +37.20s 0.65/ 0.60
event13 POINTER_MOTION +37.21s 0.65/ 0.00
event13 POINTER_MOTION +37.22s 0.33/ 0.93
event13 POINTER_MOTION +37.23s 0.67/ 0.00
event13 POINTER_MOTION +37.23s 0.67/ 0.63
event13 POINTER_MOTION +37.24s 0.65/ 0.00
event13 POINTER_MOTION +37.26s 0.65/ 0.61
event13 POINTER_MOTION +37.27s 0.65/ 0.00
event13 POINTER_MOTION +37.27s 0.65/ 0.61
event13 POINTER_MOTION +37.28s 0.65/ 0.00
event13 POINTER_MOTION +37.30s 0.59/ 0.00
event13 POINTER_MOTION +37.30s 0.59/ 0.00
event13 POINTER_MOTION +37.33s 0.54/ 0.00
event13 POINTER_MOTION +37.33s 0.50/ 0.00
event13 POINTER_MOTION +37.87s 0.38/ 0.00
button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to
BUTTON_STATE_NONE
event13: touch movement 29.3mm, pixels 398.9, raw px 1154.8, avg factor 0.3
Is this correct? Should I get always 0.4 in these cases?
Anyway I'm getting used to libinput behavior, but don't know why I feel that
very shorts movements are still strange, not always precise.
I felt synaptics was more precise. Also proprietary synaptics on Windows, even
if I generally don't like its behavior.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20170220/f1bc6522/attachment.html>
More information about the wayland-bugs
mailing list