Hi, I bought their display: https://www.waveshare.com/wiki/12.3-DSI-TOUCH-A and compiled their modules. They work fine with the stock Raspberry Pi OS kernel.
However, the touch latency is up to around 300 ms. The first touch after a pause appears on the screen after about 50 ms, but when dragging, the event queue length increases to about five events and stays at that length. As a result, the mouse pointer lags behind the finger by roughly 300 ms, during which about five events are received in 50 ms increments, visible as five distinct pointer positions on the screen. In contrast, a regular mouse feels almost instantaneous on the same display.
Is this behavior similar with the official Raspberry Pi touchscreen? Can the Waveshare custom module source be modified so that the queue is discarded altogether and only the latest event is transmitted? Or is this a Pi-level configuration that can be changed elsewhere?
However, the touch latency is up to around 300 ms. The first touch after a pause appears on the screen after about 50 ms, but when dragging, the event queue length increases to about five events and stays at that length. As a result, the mouse pointer lags behind the finger by roughly 300 ms, during which about five events are received in 50 ms increments, visible as five distinct pointer positions on the screen. In contrast, a regular mouse feels almost instantaneous on the same display.
Is this behavior similar with the official Raspberry Pi touchscreen? Can the Waveshare custom module source be modified so that the queue is discarded altogether and only the latest event is transmitted? Or is this a Pi-level configuration that can be changed elsewhere?
Statistics: Posted by scriptmonkey — Mon Oct 27, 2025 5:12 pm — Replies 3 — Views 83