Bug 94986

Summary: ETPS/2 Elantech Touchpad imprecise pointer movement using libinput
Product: Wayland Reporter: jiteshsingh <jiteshsingh17>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: bugseforuns, peter.hutterer
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 98535    
Attachments: evemu-describe output

Description jiteshsingh 2016-04-18 07:01:40 UTC
I have Asus K55VM-SX086D laptop. The touchpad is ETPS/2 Elantech Touchpad. Pointer movement was very fine when synaptics driver was in use. After switching to libinput, I no more feel the same accuracy and control as it used to be. I am not able to precisely point objects, I either overshoot or undershoot them. I have already tried adjusting accel speed via xinput, hysteresis patch, this patch: https://bugzilla.redhat.com/show_bug.cgi?id=1316655, but no success. Following are the details:

$ xinput --list-props 13
Device 'ETPS/2 Elantech Touchpad':
    Device Enabled (138):    1
    Coordinate Transformation Matrix (140):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    libinput Tapping Enabled (274):    1
    libinput Tapping Enabled Default (275):    0
    libinput Tapping Drag Enabled (276):    1
    libinput Tapping Drag Enabled Default (277):    1
    libinput Tapping Drag Lock Enabled (278):    0
    libinput Tapping Drag Lock Enabled Default (279):    0
    libinput Accel Speed (280):    0.000000
    libinput Accel Speed Default (281):    0.000000
    libinput Natural Scrolling Enabled (282):    1
    libinput Natural Scrolling Enabled Default (283):    0
    libinput Send Events Modes Available (258):    1, 1
    libinput Send Events Mode Enabled (259):    0, 0
    libinput Send Events Mode Enabled Default (260):    0, 0
    libinput Left Handed Enabled (284):    0
    libinput Left Handed Enabled Default (285):    0
    libinput Scroll Methods Available (286):    1, 1, 0
    libinput Scroll Method Enabled (287):    1, 0, 0
    libinput Scroll Method Enabled Default (288):    1, 0, 0
    libinput Click Methods Available (289):    1, 1
    libinput Click Method Enabled (290):    1, 0
    libinput Click Method Enabled Default (291):    1, 0
    libinput Disable While Typing Enabled (292):    1
    libinput Disable While Typing Enabled Default (293):    1
    Device Node (261):    "/dev/input/event5"
    Device Product ID (262):    2, 14
    libinput Drag Lock Buttons (294):    <no items>
    libinput Horizonal Scroll Enabled (263):    1
Comment 1 Peter Hutterer 2016-04-22 04:40:38 UTC
Attach the output from evemu-describe for your touchpad please, thanks.
Comment 2 jiteshsingh 2016-04-22 07:08:49 UTC
It seems the problem has been fixed already. Either I have got used to the new behaviour or any recent update might have fixed it. Thankyou.
Comment 3 Peter Hutterer 2016-04-26 05:23:02 UTC
alright, thanks. I'll close this bug now, please re-open if it happens again.
Comment 4 jiteshsingh 2017-03-30 17:16:40 UTC
Created attachment 130587 [details]
evemu-describe output
Comment 5 jiteshsingh 2017-03-30 17:20:42 UTC
Hi Peter,

I have been waiting for it to get fixed in libinput updates. But unfortunately, the problem still exists with no improvement. I have attached evemu-describe output.

Thanks.
Comment 6 Daniel van Vugt 2018-01-10 08:14:11 UTC
Sounds like a duplicate of bug 98839. The fix for that bug resolves imprecise pointer movement on every touchpad I had tested. It is due for release in libinput 1.10.0
Comment 7 Daniel van Vugt 2018-01-10 08:15:42 UTC
Maybe see how the fix for bug 101139 goes too.
Comment 8 Peter Hutterer 2018-04-20 05:54:28 UTC
Closing, libinput 1.8 or so had new touchpad accel code, this bug is now a year old. The current bug to complain about touchpad acceleration is Bug 101139, or as Daniel mentioned, Bug 98839 may have fixed this too.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.