Touch Display 2 (ilitek_v3): periodic phantom touch at a fixed point every 12.864 s

Open
#7,638 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux

Research direction

Start with the ilitek_v3 touchscreen driver and its handling of the well-formed 0x5B axis packets described in the report. Reproduce the issue with sudo libinput debug-events on the listed Touch Display 2 setup; done means the periodic phantom TOUCH_DOWN/TOUCH_UP events stop without introducing packet errors.

Written by the indexing model from the issue text.

Description

Describe the bug

Pi 5, Touch Display 2 10", Raspberry Pi OS trixie, kernel 6.18.50+rpt-rpi-2712, portrait (no transform), nothing touching the panel.

libinput debug-events shows a zero-duration TOUCH_DOWN/TOUCH_UP at exactly 95.00/2.40 (1140/46 mm) every 12.864 s, indefinitely:

event6 TOUCH_DOWN +64.288s 0 (0) 95.00/ 2.40 (1140.00/46.00mm)
event6 TOUCH_UP +64.288s 0 (0)
event6 TOUCH_DOWN +77.152s 0 (0) 95.00/ 2.40 (1140.00/46.00mm)
event6 TOUCH_UP +77.152s 0 (0)
event6 TOUCH_DOWN +90.016s 0 (0) 95.00/ 2.40 (1140.00/46.00mm)
event6 TOUCH_UP +90.016s 0 (0)

dmesg: ilitek_v3 11-0041: protocol version 00060522, FW AP Version 140.0.7.0, Core 2.2.0.3, Configured size 1200 x 1920 swapxy. No checksum or length errors logged, so the packet is a well-formed 0x5B axis packet from the controller.

Effect: any idle/screen-blanking setup (swayidle + wlopm) never engages, and kiosk pages get a click at that point every 13 s. Looks like the same class as #4749 / 99ba5ff on the 7" panel. Happy to test a patch.

Steps to reproduce the behaviour
  1. Pi 5 + Touch Display 2 10" on DSI, Raspberry Pi OS trixie (64-bit), fully updated (kernel 6.18.50+rpt-rpi-2712). Display powered from the Pi's 5V header, official 27 W supply.
  2. Boot to the labwc desktop. Do not touch the panel.
  3. Run: sudo libinput debug-events
  4. Wait a minute.

Expected: no touch events.
Actual: a zero-duration TOUCH_DOWN/TOUCH_UP at exactly 95.00/2.40 (1140/46 mm) every 12.864 s, indefinitely. No errors in dmesg.

Device (s)

Raspberry Pi 5

System

https://pastebin.com/rH0wb5n3

Logs

No response

Additional context

No response

Dominant language
C
Stars
13.3k
Forks
5.5k
Avg merge
4d 10h
Merged PRs (30d)
31

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.