Relative mouse movements bugs

[UhnShin]

When I turn on the relative mouse movement the on screen mous just straight up stop moving. Other emulator doesn't do this.

My device is Google Pixel 9

[github-actions]

🤖 Bannerlator AI

Here is what you can do right now:

1. Use "Cursor to Touchpoint" — long-press the game tile, go into its settings, and enable "Move Cursor to Touchpoint" (or "Cursor to Touch"). This forces the cursor to reposition under your finger on every touch-down, which mitigates the frozen cursor.

2. Use the touchpad mode instead of touchscreen mode — open the in-game drawer (swipe from the left edge) and toggle off the "Touchscreen" switch. In touchpad mode the cursor follows finger deltas rather than absolute positions, which may feel less stuck.

3. Connect a Bluetooth mouse — relative mouse mode was designed for physical mouse input (pointer capture). With a real mouse connected, the cursor movement is handled by the OS driver and the frozen-on-screen-cursor issue does not apply.

This is a code-level issue: in several places (touch down, finger move, and touchscreen move), the isRelativeMouseMovement branch sends events to the game but never calls the X server pointer-move method that redraws the on-screen cursor. A code change in TouchpadView.java would be needed so that the on-screen cursor is also updated alongside the game input. Whether it gets built is the maintainer's call; nothing has changed as a result of this reply.

Checked: app/src/main/java/com/winlator/star/widget/TouchpadView.java:474,490,658, app/src/main/java/com/winlator/star/XServerDisplayActivity.java:2635

---

ℹ️ Please read — about this project

Bannerlator is a personal build — made by me (The412Banner), for my own device, my own needs, and my own use.

It's a personal continuation of the Winlator Star Bionic project (star-emu/star) after it was discontinued and archived. None of the original developers are involved except me; it stands on their work plus cherry-picked commits from across the community — all credited in the repo.

This is NOT an official or general-purpose Winlator release. It is built and tuned for my hardware and my workflow, and published as-is purely in case it happens to be useful to someone else.

• No guarantee it works on any other device, GPU, or Android version.
• No support, and no commitment to fix anything that works for me but not for you. If a feature works on my device, it isn't broken — for me, which is what this build is for.
• Bug reports / feature requests for setups I don't run may simply be closed. That's not personal; this just isn't a community-support project.
• You're free to use, modify, fork, or share it (GPL-3.0). If it doesn't work on your setup, that's expected — it wasn't built for it.

Cited from the Bannerlator codebase. For a follow-up, open a new question.