Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 128
    • Issues 128
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Librem5
  • linux
  • Issues
  • #136
Closed
Open
Created Jan 05, 2020 by Sebastian Krzyszkowiak@sebastian.krzyszkowiakMaintainer

Touch points getting stuck

Sometimes the kernel doesn't notice that the finger has been released from the touchscreen, resulting in a stuck touch point.

libinput debug-events:

# finger placed on screen
 event1   TOUCH_DOWN        +7.32s      0 (0) 38.33/46.74 (276.00/673.00mm)
 event1   TOUCH_FRAME       +7.32s
# finger released
#
# finger placed again
 event1   TOUCH_MOTION     +16.99s      0 (0) 81.11/62.99 (584.00/907.00mm)
 event1   TOUCH_FRAME      +16.99s
# finger released
 event1   TOUCH_UP         +17.05s
 event1   TOUCH_FRAME      +17.05s

evtest:

# finger placed on screen
Event: time 1578191602.590064, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 412
Event: time 1578191602.590064, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 463
Event: time 1578191602.590064, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 670
Event: time 1578191602.590064, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1578191602.590064, type 3 (EV_ABS), code 0 (ABS_X), value 463
Event: time 1578191602.590064, type 3 (EV_ABS), code 1 (ABS_Y), value 670
Event: time 1578191602.590064, -------------- SYN_REPORT ------------
# finger released
#
# finger placed again
Event: time 1578191614.366974, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 139
Event: time 1578191614.366974, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 861
Event: time 1578191614.366974, type 3 (EV_ABS), code 0 (ABS_X), value 139
Event: time 1578191614.366974, type 3 (EV_ABS), code 1 (ABS_Y), value 861
Event: time 1578191614.366974, -------------- SYN_REPORT ------------
# finger released
Event: time 1578191614.392739, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1578191614.392739, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1578191614.392739, -------------- SYN_REPORT ------------

This is Birch - I never noticed such behavior on the devkit.

Edited Jan 06, 2020 by Sebastian Krzyszkowiak
Assignee
Assign to
Time tracking