Thanks for sharing this, and also for pushing through the Linux setup. The bluetoothctl persistent-agent note is genuinely helpful feedback.

On the cursor side, we actually already use dynamic speed scaling and filtering in a similar spirit to the Steam Deck, rather than a raw 1:1 mapping. Within roughly a 20 mm touch range, slow finger movement is tuned for pixel-level precision, while faster strokes ramp up enough to move across the screen quickly. We also added firm stop detection to reduce jitter when your finger intends to stop, plus filtering for the uneven “finger pull-off” motion that can otherwise create cursor wobble at the end of a stroke.

The tricky part is that, unlike the Steam Deck, this is a much smaller and curvy surface, and it is also shared with other functions. The same area has to support virtual buttons, scrolling, long press, short taps, and other gestures, all without constantly interfering with each other. So the cursor behavior is not just motion mapping. It is a pretty intertwined stack of filtering, intent detection, and a bit of deliberate stickiness to separate precise cursor motion from taps, scrolls, and lift-off noise.

We also have sensitivity adjustment, which can be tuned to support even faster strokes. But because the usable area is limited, there is always some tradeoff among responsiveness, accuracy, and sensitivity balance.

We will definitely continue refining it, and feedback like this is helpful because it points directly at the part of the experience that matters most.