Bug 102883 - Low precision in slow and little touchpad movements
Summary: Low precision in slow and little touchpad movements
Status: RESOLVED DUPLICATE of bug 98839
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-19 18:01 UTC by Aleix Vidal Gaya
Modified: 2017-10-12 03:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
evemu-record reproducing the bug (98.29 KB, text/plain)
2017-09-19 18:01 UTC, Aleix Vidal Gaya
Details

Description Aleix Vidal Gaya 2017-09-19 18:01:39 UTC
Created attachment 134345 [details]
evemu-record reproducing the bug

I have an Acer Aspire V5-573PG with Synaptics touchpad, running Debian testing distribution.

The libinput version installed is 1.8.2-1.

When moving the pointer with the touchpad, when trying to make precise and slow movements, the cursor makes jumps instead of moving precisely between continuous pixels. This behaviour is not the one expected, as with the Synaptics driver the precision in this type of movement is perfect, as it is in Windows too.

Evemu-record file reproducing the bug attached.

The udevadm info returns:

P: /devices/platform/i8042/serio1/input/input2/event1
N: input/event1
E: DEVNAME=/dev/input/event1
E: DEVPATH=/devices/platform/i8042/serio1/input/input2/event1
E: ID_BUS=i8042
E: ID_INPUT=1
E: ID_INPUT_HEIGHT_MM=75
E: ID_INPUT_TOUCHPAD=1
E: ID_INPUT_TOUCHPAD_INTEGRATION=internal
E: ID_INPUT_WIDTH_MM=104
E: LIBINPUT_ATTR_PRESSURE_RANGE=10:8
E: LIBINPUT_DEVICE_GROUP=11/2/7/1b1:isa0060/serio1
E: LIBINPUT_MODEL_SYNAPTICS_SERIAL_TOUCHPAD=1
E: MAJOR=13
E: MINOR=65
E: SUBSYSTEM=input
E: USEC_INITIALIZED=12970407

The contents of /sys/class/dmi/id/modalias is:

dmi:bvnInsydeCorp.:bvrV2.30:bd01/12/2015:svnAcer:pnAspireV5-573PG:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:

The evemu-describre command returns:

# EVEMU 1.3
# Kernel: 4.12.0-1-amd64
# DMI: dmi:bvnInsydeCorp.:bvrV2.30:bd01/12/2015:svnAcer:pnAspireV5-573PG:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
# Input device name: "SynPS/2 Synaptics TouchPad"
# Input device ID: bus 0x11 vendor 0x02 product 0x07 version 0x1b1
# Size in mm: 104x75
# Supported events:
#   Event type 0 (EV_SYN)
#     Event code 0 (SYN_REPORT)
#     Event code 1 (SYN_CONFIG)
#     Event code 2 (SYN_MT_REPORT)
#     Event code 3 (SYN_DROPPED)
#     Event code 4 ((null))
#     Event code 5 ((null))
#     Event code 6 ((null))
#     Event code 7 ((null))
#     Event code 8 ((null))
#     Event code 9 ((null))
#     Event code 10 ((null))
#     Event code 11 ((null))
#     Event code 12 ((null))
#     Event code 13 ((null))
#     Event code 14 ((null))
#     Event code 15 (SYN_MAX)
#   Event type 1 (EV_KEY)
#     Event code 272 (BTN_LEFT)
#     Event code 325 (BTN_TOOL_FINGER)
#     Event code 328 (BTN_TOOL_QUINTTAP)
#     Event code 330 (BTN_TOUCH)
#     Event code 333 (BTN_TOOL_DOUBLETAP)
#     Event code 334 (BTN_TOOL_TRIPLETAP)
#     Event code 335 (BTN_TOOL_QUADTAP)
#   Event type 3 (EV_ABS)
#     Event code 0 (ABS_X)
#       Value     4681
#       Min       1278
#       Max       5662
#       Fuzz         0
#       Flat         0
#       Resolution  42
#     Event code 1 (ABS_Y)
#       Value     2031
#       Min       1198
#       Max       4656
#       Fuzz         0
#       Flat         0
#       Resolution  46
#     Event code 24 (ABS_PRESSURE)
#       Value        0
#       Min          0
#       Max        255
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 28 (ABS_TOOL_WIDTH)
#       Value        0
#       Min          0
#       Max         15
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 47 (ABS_MT_SLOT)
#       Value        1
#       Min          0
#       Max          1
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 53 (ABS_MT_POSITION_X)
#       Value        0
#       Min       1278
#       Max       5662
#       Fuzz         8
#       Flat         0
#       Resolution  42
#     Event code 54 (ABS_MT_POSITION_Y)
#       Value        0
#       Min       1198
#       Max       4656
#       Fuzz         8
#       Flat         0
#       Resolution  46
#     Event code 57 (ABS_MT_TRACKING_ID)
#       Value        0
#       Min          0
#       Max      65535
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 58 (ABS_MT_PRESSURE)
#       Value        0
#       Min          0
#       Max        255
#       Fuzz         0
#       Flat         0
#       Resolution   0
# Properties:
#   Property  type 0 (INPUT_PROP_POINTER)
#   Property  type 2 (INPUT_PROP_BUTTONPAD)
N: SynPS/2 Synaptics TouchPad
I: 0011 0002 0007 01b1
P: 05 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 01 00 00 00 00 00
B: 01 20 e5 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 00 00 00 00 00 00 00 00
B: 03 03 00 00 11 00 80 60 06
B: 04 00 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
A: 00 1278 5662 0 0 42
A: 01 1198 4656 0 0 46
A: 18 0 255 0 0 0
A: 1c 0 15 0 0 0
A: 2f 0 1 0 0 0
A: 35 1278 5662 8 0 42
A: 36 1198 4656 8 0 46
A: 39 0 65535 0 0 0
A: 3a 0 255 0 0 0
Comment 1 Nate Graham 2017-10-12 03:51:47 UTC
This is almost certainly hysteresis: https://bugs.freedesktop.org/show_bug.cgi?id=98839

*** This bug has been marked as a duplicate of bug 98839 ***


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.