search

DIGImend / digimend-kernel-drivers

DIGImend graphics tablet drivers for the Linux kernel
GNU General Public License v2.0
1.17k stars 173 forks source link

Huion Kamvas 16 Pro, Fedora32 -> touch strip unresponsive #422

Open robert-clayton opened 4 years ago

robert-clayton commented 4 years ago

Hardware: Huion Kamvas 16 Pro Distro: Fedora 32 (KDE Plasmashell) Kernel: 5.6.19-300.fc32.x86_64 Issue: Touch Strip not showing any activity

I've followed the README by:

Various related outputs:

[robert@localhost ~]$ xsetwacom --list devices
HID 256c:006d Pen stylus                id: 10  type: STYLUS    
HID 256c:006d Pad pad                   id: 11  type: PAD       
HID 256c:006d Touch Strip pad           id: 12  type: PAD
[robert@localhost ~]$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Pen stylus                  id=10   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Pad pad                     id=11   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Touch Strip pad             id=12   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Dial                        id=13   [slave  pointer  (2)]
⎜   ↳ Razer Razer Naga Chroma                   id=14   [slave  pointer  (2)]
⎜   ↳ Razer Razer Naga Chroma Consumer Control  id=16   [slave  pointer  (2)]
⎜   ↳ Logitech G815 RGB MECHANICAL GAMING KEYBOARD Mouse        id=21   [slave  pointer  (2)]
[robert@localhost ~]$ xinput test "HID 256c:006d Touch Strip pad"
^C
[robert@localhost digimend-kernel-drivers]$ cat /sys/module/hid_uclogic/version
10
[robert@localhost digimend-kernel-drivers]$ sudo modinfo hid-uclogic
filename:       /lib/modules/5.6.19-300.fc32.x86_64/extra/hid-uclogic.ko.xz
version:        10
license:        GPL
author:         Nikolai Kondrashov
author:         Martin Rusko
srcversion:     957BF5A50EF2C284749D987
alias:          hid:b0003g*v000028BDp00000042
alias:          hid:b0003g*v000028BDp00000094
alias:          hid:b0003g*v000028BDp00000075
alias:          hid:b0003g*v000028BDp00000055
alias:          hid:b0003g*v000028BDp00000071
alias:          hid:b0003g*v000028BDp00000074
alias:          hid:b0003g*v00002179p00000053
alias:          hid:b0003g*v00005543p00003031
alias:          hid:b0003g*v00005543p00000047
alias:          hid:b0003g*v00005543p00000045
alias:          hid:b0003g*v00005543p00000081
alias:          hid:b0003g*v00005543p0000004D
alias:          hid:b0003g*v00005543p0000006E
alias:          hid:b0003g*v0000256Cp0000006D
alias:          hid:b0003g*v0000256Cp0000006E
alias:          hid:b0003g*v00005543p00000781
alias:          hid:b0003g*v00005543p00000522
alias:          hid:b0003g*v00005543p00000064
alias:          hid:b0003g*v00005543p00000005
alias:          hid:b0003g*v00005543p00000004
alias:          hid:b0003g*v00005543p00000003
alias:          hid:b0003g*v00005543p00000042
depends:        
retpoline:      Y
name:           hid_uclogic
vermagic:       5.6.19-300.fc32.x86_64 SMP mod_unload

Any help would be appreciated.

(EDITED to remove issues stemming from my acs patch override and provide better formatting.)

robert-clayton commented 4 years ago

This might deserve a separate issue, but it's just sudo dnf -y kernel-devel for Fedora-based systems now.

Shinmera commented 4 years ago

Same problem here, on Arch Linux 5.8.1. All the buttons show up fine, but the touch strip does not. No inputs on xinput test, and even manually forcing all buttons and wheel/strip parameters to keys on all pads shows nothing.

⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech TrackPoint                id=18   [slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                  id=19   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Pad pad                     id=12   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Dial pad                    id=13   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Pen stylus                  id=14   [slave  pointer  (2)]
⎜   ↳ HID 256c:006d Touch Strip pad             id=15   [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C           id=16   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=17   [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=20   [slave  keyboard (3)]
Popolon commented 4 years ago

Please could you report a full diagnostics as in http://digimend.github.io/support/howto/trbl/diagnostics/ I have a Kamvas pro 20, have about the same issues, I added #463 for my version this is probably the same protocol in both, as they are from the same product line. In my case, I don't have the same USB id (256c:006e), and Touch Strip pad even don't display in xinput list, I have only pad and pen pen (0)

Shinmera : I use ArchLinux too, you can find all the tool needed in arch. package usbutils and AUR package uclogic-tools hidrd-git

Popolon commented 4 years ago

@Shinmera I managed to have most of things working (strips + most buttons + tilt) by installing on Arch Linux, the AUR package digimend-kernel-drivers-dkms-git https://aur.archlinux.org/packages/digimend-kernel-drivers-dkms-git/

The PKGBUILD receipe is clear and what is made inside could be reused on other distributions.

Shinmera commented 4 years ago

I've updated everything to the latest arch (5.8.13-arch1-1) and reinstalled the package, but it didn't improve the situation. Touch strip still does not report any xinput events on any of the devices.

I've attached all the diagnostic files. descriptors.txt frame_buttons.txt frame_strip.txt hid_report_descriptors.txt pen_buttons.txt pen_coords.txt pen_pressure.txt pen_tilt.txt probe.txt

spbnick commented 4 years ago

Does any one of you get anything out of evtest for the "Touch Strip" device?

Shinmera commented 4 years ago

Yes, I get events for the strip device (first moving down, then up):

Input device name: "HID 256c:006d Touch Strip"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 256 (BTN_0)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max        1
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max        1
    Event code 8 (ABS_WHEEL)
      Value      0
      Min        0
      Max        7
      Resolution       3
    Event code 40 (ABS_MISC)
      Value      0
      Min        0
      Max      255
Properties:
Testing ... (interrupt to exit)
Event: time 1601888878.645171, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1601888878.645171, -------------- SYN_REPORT ------------
Event: time 1601888878.983132, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 1
Event: time 1601888878.983132, -------------- SYN_REPORT ------------
Event: time 1601888879.177166, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 2
Event: time 1601888879.177166, -------------- SYN_REPORT ------------
Event: time 1601888879.427168, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 3
Event: time 1601888879.427168, -------------- SYN_REPORT ------------
Event: time 1601888879.621173, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 4
Event: time 1601888879.621173, -------------- SYN_REPORT ------------
Event: time 1601888879.835169, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 5
Event: time 1601888879.835169, -------------- SYN_REPORT ------------
Event: time 1601888880.159170, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 6
Event: time 1601888880.159170, -------------- SYN_REPORT ------------
Event: time 1601888880.535172, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1601888880.535172, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1601888880.535172, -------------- SYN_REPORT ------------
Event: time 1601888882.539133, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1601888882.539133, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 6
Event: time 1601888882.539133, -------------- SYN_REPORT ------------
Event: time 1601888882.755131, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 5
Event: time 1601888882.755131, -------------- SYN_REPORT ------------
Event: time 1601888882.981133, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 4
Event: time 1601888882.981133, -------------- SYN_REPORT ------------
Event: time 1601888883.165171, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 3
Event: time 1601888883.165171, -------------- SYN_REPORT ------------
Event: time 1601888883.347168, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 2
Event: time 1601888883.347168, -------------- SYN_REPORT ------------
Event: time 1601888883.529194, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 1
Event: time 1601888883.529194, -------------- SYN_REPORT ------------
Event: time 1601888883.691172, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1601888883.691172, -------------- SYN_REPORT ------------
Event: time 1601888883.971171, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1601888883.971171, -------------- SYN_REPORT ------------
spbnick commented 4 years ago

The evtest output looks OK. Please try the latest release (v10) and see if it works. Post your xorg.0.log here or the equivalent journal output, if it doesn't.

spbnick commented 4 years ago

Also please see the release notes regarding the limited support fro touch strips/rings.

Popolon commented 4 years ago

I tried v10 on ArchLinux, and Huion Kamvas Pro 20 (see #463), and I have no more cursor. Ptxconf, see the device, but the mouse cursor isn't moved anymore by stylus. I come back to previous release (10.rc0.r1 (g691dae8)) and it works again.

spbnick commented 4 years ago

@Popolon, that is troubling news. Could you post an evtest output for your stylus with v10?

Popolon commented 4 years ago

I have the same problem with the current one (10.rc0.r1) one time yesterday. This time, I power on tablet before or at the same time than computer, and i tried to use pen, before XFCE launch endend. That was perhaps the case too the day of my try. I will retry with v10, waiting for full boot before powering on the tablet.

Popolon commented 4 years ago

OK, it worked this time. I need to investigate why for, when i touch the screen with stylus before the end, of the startup sequence (and at wich stage ?) the stlus is no more detected at all. What I remember, is that PTXConf, seen it with "stylus" name, not pen (as now), I used the 50-wacom.conf to map it to wacom tablet. I will make more try in different cases.

Popolon commented 4 years ago

So I just tried more cases :

I don't remember what I done when I had the bug yesterday, but at least the new version of the driver works finely. This is as most a common bug, or a bug somwhere in Xinput or tablet itself... By default the bug is not seen with evtest/PTXconf, i need to move the pen near the screen to make it discovered and the device appear.

Popolon commented 4 years ago

again the bug today, I just started the tablet after about a day of usage of the system. the stylus is not seen even if I move him near from the screen. Strangely device 21 is missing 

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Power Button
/dev/input/event1:  Power Button
/dev/input/event2:  PC Speaker
/dev/input/event3:  Eee PC WMI hotkeys
/dev/input/event4:  Video Bus
/dev/input/event5:  HDA Intel PCH Front Mic
/dev/input/event6:  HDA Intel PCH Rear Mic
/dev/input/event7:  HDA Intel PCH Line
/dev/input/event8:  HDA Intel PCH Line Out Front
/dev/input/event9:  HDA Intel PCH Line Out Surround
/dev/input/event10: HDA Intel PCH Line Out CLFE
/dev/input/event11: HDA Intel PCH Line Out Side
/dev/input/event12: HDA Intel PCH Front Headphone
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event14: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event15: Logitech USB Optical Mouse
/dev/input/event16: NOVATEK USB Keyboard
/dev/input/event17: NOVATEK USB Keyboard System Control
/dev/input/event18: NOVATEK USB Keyboard Consumer Control
/dev/input/event19: NOVATEK USB Keyboard
/dev/input/event20: Razer Razer Electra V2 USB Consumer Control
/dev/input/event22: Tablet Monitor
/dev/input/event23: Tablet Monitor Pad
/dev/input/event24: Tablet Monitor Touch Strip
/dev/input/event25: Tablet Monitor Dial
Select the device event number [0-25]:

I turn off the tablet and turn on again, I can move the cursor with stylus, but don't see the stylus on evtest, and there is one less device (the tablet monitor devices was reassigned:

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Power Button
/dev/input/event1:  Power Button
/dev/input/event2:  PC Speaker
/dev/input/event3:  Eee PC WMI hotkeys
/dev/input/event4:  Video Bus
/dev/input/event5:  HDA Intel PCH Front Mic
/dev/input/event6:  HDA Intel PCH Rear Mic
/dev/input/event7:  HDA Intel PCH Line
/dev/input/event8:  HDA Intel PCH Line Out Front
/dev/input/event9:  HDA Intel PCH Line Out Surround
/dev/input/event10: HDA Intel PCH Line Out CLFE
/dev/input/event11: HDA Intel PCH Line Out Side
/dev/input/event12: HDA Intel PCH Front Headphone
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event14: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event15: Logitech USB Optical Mouse
/dev/input/event16: NOVATEK USB Keyboard
/dev/input/event17: NOVATEK USB Keyboard System Control
/dev/input/event18: NOVATEK USB Keyboard Consumer Control
/dev/input/event19: NOVATEK USB Keyboard
/dev/input/event20: Razer Razer Electra V2 USB Consumer Control
/dev/input/event21: Tablet Monitor
/dev/input/event22: Tablet Monitor Pad
/dev/input/event23: Tablet Monitor Touch Strip
/dev/input/event24: Tablet Monitor Dial
Select the device event number [0-24]:
Popolon commented 4 years ago

But at the same time I am able to configure it with PTXconf.

See evtest and PTXconf!

Popolon commented 4 years ago

With driver 10.rc0.r1.g691dae8 Gnome see the tablet, and allow to configure it. with driver 10.r0.gec5c16d doesn't see the tablet, and then doesn't allow to configure it.

evtest with 10.rc0.r1.g691dae8:

/dev/input/event22: Tablet Monitor Pen
/dev/input/event23: Tablet Monitor Pad
/dev/input/event24: Tablet Monitor Touch Strip
/dev/input/event25: Tablet Monitor Dial
Select the device event number [0-25]: 22      
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x256c product 0x6e version 0x111
Input device name: "Tablet Monitor Pen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 320 (BTN_TOOL_PEN)
    Event code 330 (BTN_TOUCH)
    Event code 331 (BTN_STYLUS)
    Event code 332 (BTN_STYLUS2)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max    86970
      Resolution     200
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max    47752
      Resolution     200
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max     8191
    Event code 26 (ABS_TILT_X)
      Value      0
      Min      -60
      Max       60
      Resolution      57
    Event code 27 (ABS_TILT_Y)
      Value      0
      Min      -60
      Max       60
      Resolution      57
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)

evtest with 10.r0.gec5c16d (october version)

/dev/input/event22: Tablet Monitor
/dev/input/event23: Tablet Monitor Pad
/dev/input/event24: Tablet Monitor Touch Strip
/dev/input/event25: Tablet Monitor Dial
Select the device event number [0-25]: 22
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x256c product 0x6e version 0x111
Input device name: "Tablet Monitor"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 320 (BTN_TOOL_PEN)
    Event code 330 (BTN_TOUCH)
    Event code 331 (BTN_STYLUS)
    Event code 332 (BTN_STYLUS2)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value  24967
      Min        0
      Max    86970
      Resolution     200
    Event code 1 (ABS_Y)
      Value  36468
      Min        0
      Max    47752
      Resolution     200
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max     8191
    Event code 26 (ABS_TILT_X)
      Value    -23
      Min      -60
      Max       60
      Resolution      57
    Event code 27 (ABS_TILT_Y)
      Value     36
      Min      -60
      Max       60
      Resolution      57
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
  Property type 0 (INPUT_PROP_POINTER)
Testing ... (interrupt to exit)

I tried : start gnome in newer : it don't see it

Popolon commented 4 years ago

xsetwacom display 'stylus' in one case 'Pen stylus' in other case:

10.rc0.r1.g691dae8

$ xsetwacom --list devices
Tablet Monitor Pad pad              id: 15  type: PAD       
Tablet Monitor Dial pad             id: 16  type: PAD       
Tablet Monitor Touch Strip pad      id: 17  type: PAD       
Tablet Monitor Pen stylus           id: 18  type: STYLUS

10.r0.gec5c16d 

$ xsetwacom --list devices
Tablet Monitor Touch Strip pad      id: 15  type: PAD       
Tablet Monitor Pad pad              id: 16  type: PAD       
Tablet Monitor stylus               id: 17  type: STYLUS    
Tablet Monitor Dial pad             id: 18  type: PAD
dentex commented 3 years ago

I have a Kamvas Pro 13 and the only thing that doesn't work is that touch strip.

I get a nice output with evtest, but besides that, I had no luck trying to mess with xsetwacom (see https://github.com/dwilches/huion-kamvas-pro-13/issues/1)

~$ sudo evtest 
No device specified, trying to scan all of /dev/input/event*
Available devices:
[...]
/dev/input/event11: Tablet Monitor Pad
/dev/input/event12: Tablet Monitor Touch Strip
/dev/input/event13: Tablet Monitor Dial
[...]
Select the device event number [0-24]: 12
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x256c product 0x6d version 0x111
Input device name: "Tablet Monitor Touch Strip"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 256 (BTN_0)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max        1
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max        1
    Event code 8 (ABS_WHEEL)
      Value      0
      Min        0
      Max        7
      Resolution       3
    Event code 40 (ABS_MISC)
      Value      0
      Min        0
      Max      255
Properties:
Testing ... (interrupt to exit)
Event: time 1606839487.853348, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839487.853348, -------------- SYN_REPORT ------------
Event: time 1606839488.001379, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 1
Event: time 1606839488.001379, -------------- SYN_REPORT ------------
Event: time 1606839488.149384, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 2
Event: time 1606839488.149384, -------------- SYN_REPORT ------------
Event: time 1606839488.309370, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 3
Event: time 1606839488.309370, -------------- SYN_REPORT ------------
Event: time 1606839488.507360, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 4
Event: time 1606839488.507360, -------------- SYN_REPORT ------------
Event: time 1606839488.743336, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 5
Event: time 1606839488.743336, -------------- SYN_REPORT ------------
Event: time 1606839488.991347, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 6
Event: time 1606839488.991347, -------------- SYN_REPORT ------------
Event: time 1606839489.473367, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839489.473367, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839489.473367, -------------- SYN_REPORT ------------
Event: time 1606839492.361392, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839492.361392, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 4
Event: time 1606839492.361392, -------------- SYN_REPORT ------------
Event: time 1606839492.493445, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839492.493445, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839492.493445, -------------- SYN_REPORT ------------
Event: time 1606839493.229431, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839493.229431, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 1
Event: time 1606839493.229431, -------------- SYN_REPORT ------------
Event: time 1606839493.371428, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839493.371428, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839493.371428, -------------- SYN_REPORT ------------
Event: time 1606839493.917444, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839493.917444, -------------- SYN_REPORT ------------
Event: time 1606839494.059437, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839494.059437, -------------- SYN_REPORT ------------
Event: time 1606839495.279448, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839495.279448, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 3
Event: time 1606839495.279448, -------------- SYN_REPORT ------------
Event: time 1606839495.435459, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839495.435459, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839495.435459, -------------- SYN_REPORT ------------
Event: time 1606839496.013454, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839496.013454, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 4
Event: time 1606839496.013454, -------------- SYN_REPORT ------------
Event: time 1606839496.127464, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839496.127464, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839496.127464, -------------- SYN_REPORT ------------
Event: time 1606839497.413283, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839497.413283, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 1
Event: time 1606839497.413283, -------------- SYN_REPORT ------------
Event: time 1606839497.573522, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839497.573522, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839497.573522, -------------- SYN_REPORT ------------
Event: time 1606839503.871573, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839503.871573, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 6
Event: time 1606839503.871573, -------------- SYN_REPORT ------------
Event: time 1606839504.091578, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 5
Event: time 1606839504.091578, -------------- SYN_REPORT ------------
Event: time 1606839504.259588, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 4
Event: time 1606839504.259588, -------------- SYN_REPORT ------------
Event: time 1606839504.429368, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 3
Event: time 1606839504.429368, -------------- SYN_REPORT ------------
Event: time 1606839504.635597, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 2
Event: time 1606839504.635597, -------------- SYN_REPORT ------------
Event: time 1606839504.833596, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 1
Event: time 1606839504.833596, -------------- SYN_REPORT ------------
Event: time 1606839505.013615, type 3 (EV_ABS), code 8 (ABS_WHEEL), value 0
Event: time 1606839505.013615, -------------- SYN_REPORT ------------
Event: time 1606839505.211609, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839505.211609, -------------- SYN_REPORT ------------
Event: time 1606839507.225635, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839507.225635, -------------- SYN_REPORT ------------
Event: time 1606839507.385632, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1606839507.385632, -------------- SYN_REPORT ------------
Event: time 1606839507.895637, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1606839507.895637, -------------- SYN_REPORT ------------