[Wayland-bugs] [Bug 99695] Can't manage acceleration profile on HP 255 G5 "SynPS/2 Synaptics TouchPad"

Tue Feb 7 09:38:09 UTC 2017

https://bugs.freedesktop.org/show_bug.cgi?id=99695

--- Comment #6 from giuseppemargarita at gmail.com ---
(In reply to Peter Hutterer from comment #5) 
> which ones of those did you actually configure though? just because libinput
> doesn't have an option doesn't mean it doesn't exist, e.g. the noise
> cancellation in libinput is basically the same as synaptics. as for the
> actual speed, it's a bit hard to figure out what synaptics does...

I've actually configured libinput because I opened this bug report and want to
help you to find the solution. The options are listed in the first comment.
I wrote the configuration in a .conf file in xorg directory because I can't
configure libinput from Plasma desktop. Unfortunately Plasma 5 has not a full
support to libinput, so I can't configure it properly from system settings.
In system setting I can't change some options and others are grayed. There's
also a bug which I can't set the right acceleration speed. 
I talked about that here: https://bbs.archlinux.org/viewtopic.php?id=222388
And found a workaround setting the right acceleration speed from an executable
script run by Plasma at its startup.

Anyway, libinput is too problematic for me and I will use synaptics because
it's more comfortable.  

When using synaptics, the options used are the following (all configured by
system setting in Plasma 5; no text xorg .conf file and no scripts are used):  
Device 'SynPS/2 Synaptics TouchPad':
        Device Enabled (142):   1
        Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        Device Accel Profile (270):     1
        Device Accel Constant Deceleration (271):       2.500000
        Device Accel Adaptive Deceleration (272):       1.000000
        Device Accel Velocity Scaling (273):    12.500000
        Synaptics Edges (274):  1632, 5350, 1356, 4584
        Synaptics Finger (275): 25, 30, 0
        Synaptics Tap Time (276):       180
        Synaptics Tap Move (277):       254
        Synaptics Tap Durations (278):  180, 180, 100
        Synaptics ClickPad (279):       0
        Synaptics Middle Button Timeout (280):  75
        Synaptics Two-Finger Pressure (281):    282
        Synaptics Two-Finger Width (282):       7
        Synaptics Scrolling Distance (283):     116, 116
        Synaptics Edge Scrolling (284): 0, 0, 0
        Synaptics Two-Finger Scrolling (285):   1, 1
        Synaptics Move Speed (286):     1.000000, 1.750000, 0.034947, 0.000000
        Synaptics Off (287):    2
        Synaptics Locked Drags (288):   0
        Synaptics Locked Drags Timeout (289):   5000
        Synaptics Tap Action (290):     0, 0, 0, 0, 1, 2, 3
        Synaptics Click Action (291):   1, 1, 1
        Synaptics Circular Scrolling (292):     0
        Synaptics Circular Scrolling Distance (293):    0.100007
        Synaptics Circular Scrolling Trigger (294):     0
        Synaptics Circular Pad (295):   0
        Synaptics Palm Detection (296): 0
        Synaptics Palm Dimensions (297):        10, 200
        Synaptics Coasting Speed (298): 20.000000, 50.000000
        Synaptics Pressure Motion (299):        30, 160
        Synaptics Pressure Motion Factor (300): 1.000000, 1.000000
        Synaptics Grab Event Device (301):      0
        Synaptics Gestures (302):       1
        Synaptics Capabilities (303):   1, 0, 1, 1, 1, 1, 1
        Synaptics Pad Resolution (304): 89, 40
        Synaptics Area (305):   0, 0, 0, 0                                      
        Synaptics Noise Cancellation (306):     28, 28                          
        Device Product ID (266):        2, 7                                    
        Device Node (265):      "/dev/input/event13"

It would be great if you can reproduce the behavior of these options in
libinput. But I can't configure noise cancellation and don't know if
deceleration is available in libinput.

> the current profile is the 'adaptive' profile, same as the mouse profile.
> You can quite easily hack the source to use the flat profile instead but tbh
> I doubt that's the behaviour you want either.

Okay, but why can't I set the flat profile from the configuration?

> the question is *why* this happens, since the acceleration itself should be
> the same on any device, regardless of the resolution. So far I only found a
> possible issue with the sampling rate but yours is within the same range as
> my touchpad here, so shouldn't be affected by that. Any help in identifying
> why your touchpad appears to accelerate when it shouldn't would be
> appreciated.

I don't know how, I gave you all I could report. Can't you find anything from
evemu record?

-- 
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/20170207/2cce7dd3/attachment-0001.html>