[Wayland-bugs] [Bug 99079] Improve Surface Pro Type Cover 2 support

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 99079
           Summary: Improve Surface Pro Type Cover 2 support
           Product: Wayland
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libinput
          Assignee: wayland-bugs at lists.freedesktop.org
          Reporter: defree at gmail.com

Using Surface Pro 2 is a bit painful due to some problems with input devices.

I would like to help / provide patches to improve this. Being new to libinput,
wayland, and more generally freedesktop workflow, I am not sure how to approach
the problem and I will appreciate some help to get started.

Below I report the output of libinput-debug-events when I trigger the
problematic behaviors.

# Touchpad

model: Microsoft Type Cover 2 Japanese version (but I suspect it happens with
western version(s) too)
usb-id: 045e:07aa Microsoft Corp. 
libinput-name: MICROSOFT SAM

## Problems

Spurious KEY_F23 event when clicking (that is a single click produces mouse
button + keypress events). (+ pad disabled notification)

Clunky scroll:
- not always detected
- take time to start then scroll by one big chunk

No tap and drag feature, this is critical for usability.

# Touchscreen

usb-id: 03eb:8209 Atmel Corp. 
libinput-name: Atmel Atmel maXTouch Digitizer 

## Problem

I am not familiar with touchscreen, so maybe the behavior I am about to
describe is normal and the bug elsewhere.

A sequence for a click is TOUCH_DOWN, TOUCH_FRAME, TOUCH_UP.
During motion, every TOUCH_MOTION is interleaved with a TOUCH_FRAME.

This seems to confuse software a lot (Gnome 3, Firefox, Chrome, both under xorg
and wayland/xwayland).

I cannot tell if the bug is in these software or in the input library, but
basically actions are missed. For instance, a touch doesn't turn into an actual
click or does so unreliably.

I tested the same software on another laptop with touchscreen and the same
actions were not so unreliable.  However I didn't think about tracing events at
that time, so I cannot tell if the problem is at this level or not.

# Software versions

The computer is running Manjaro with a kernel 4.6 patched to enable USB quirks
on the Type Cover 2 JP.
Other software are manjaro stable versions, that is at the time of writing:
libinput-1.5.3
wayland-1.12
gnome-3.22
xorg-1.18
xf86-input-libinput-0.22

-- 
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/20161214/158f824b/attachment.html>