Repository navigation
android: A60, a pointer that reports positions moves the cursor to them - #35
Closed
utkarshdalal wants to merge 1 commit into
Closed
utkarshdalal wants to merge 1 commit into
utkarshdalal wants to merge 1 commit into
Conversation
This was referenced Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The host app sends input through a virtual pointer. Only the relative request (
motion) was handled, so the app turned every touch position into a step from a cursor position it tracked for itself. gamescope keeps the cursor inside the focused window's surface, so the two positions drifted apart whenever a step was clamped here, a window took the focus, a game warped the pointer, or the window was smaller than the nested display. Every later touch then landed off by that amount.This adds patch
0053-A60-absolute-pointer-motion.patch:wlserver_new_inputalso listens for a pointer'smotion_absolute.wlserver_mouseabsolutemaps the position (0..1 on the output) to the focused window as the touch path does: output size, window offset, window scale, then a clamp to the surface.Needs the injector to send real extents with
motion_absolute(GameNative/gamenative-drm, PR to follow) and the app to send positions.Device run, Poco F6 (Snapdragon 8s Gen 3), Balatro, 1280x720 container on a 2712x1220 panel (271 px bars left and right), touchscreen mode on, with #35, GameNative/gamenative-drm#63 and utkarshdalal/GameNative#2395 together: taps on menu buttons landed on target after taps in the left bar, the right bar and a swipe that ended in a bar; taps just outside a button edge did not activate it; a card drag in a run worked; no crash or injector error in logcat. Taps were injected with adb (150 ms press). A captured mouse or a controller stick was not tested.