[Bug] Stale remote cursor images remain visible after cursor shape changes on Android

Open
#1,611 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android
Domain
mobile

Research direction

No source file or test is named. Start by reproducing the issue in the Android client while changing between arrow, hand, text, and resize cursors, then trace the cursor-shape update and rendering path. Done means repeated shape changes no longer leave accumulated cursor images, with behavior verified at 30 and 60 FPS.

Written by the indexing model from the issue text.

Description

bug
Describe the bug

When streaming a Windows desktop to Android with Moonlight, changing the Windows cursor shape leaves the previous cursor image permanently visible at its previous position.

For example, when the cursor changes from the normal arrow to the hand cursor, the previous arrow remains visible. When it changes again to the text cursor or another cursor shape, another stale cursor image is added.

The most notable behavior is that the stale cursor images are rendered on top of the current active cursor. The current cursor continues to move and function normally, but old cursor images remain permanently visible underneath/behind the current cursor interaction and are visually stacked above the current cursor image.

The stale cursor images do not disappear by themselves and remain until the Moonlight streaming session is restarted.

This appears to be triggered specifically by cursor shape changes, rather than normal cursor movement.

Steps to reproduce

1.Start a Moonlight Android streaming session to a Windows PC running Sunshine.
2.Stream the Windows desktop.
3.Move the mouse over different UI elements so that the Windows cursor changes shape, for example:
•normal arrow
•hand cursor over links/buttons
•text cursor over text fields
•resize cursor near window borders
4.Move back and forth between areas with different cursor shapes.
5.Observe that every cursor shape change leaves the previous cursor image at its old location.
6.Repeat several times. Multiple stale cursor images accumulate and remain visible.

The stale cursor images are rendered above the current normal cursor.

Affected games

N/A — the problem reproduces on the Windows desktop and does not appear to be game-specific.

Other Moonlight clients

Not tested.

Moonlight adjusted settings

Yes

Moonlight adjusted settings (please complete the following information)

Tested at 30 FPS and 60 FPS; both reproduce the issue.
Tested with "Remote desktop mouse mode" enabled and disabled; both reproduce the issue.
Host is streamed through Sunshine using the DXGI capture method.

Moonlight default settings

Yes

Gamepad-related connection issue

No

Gamepad-related input issue

No

Gamepad-related streaming issue

No

Android version

Android 16 and Android 10

Device model

HONOR 500 Pro/HUAWEI MatePad 11 (2021), DBY-W09

Server PC OS version

Windows 11 Home, Version 25H2, Chinese (Simplified)

Server PC GeForce Experience version

NVIDIA App 11.0.9.251

Server PC Nvidia GPU driver version

NVIDIA GeForce Game Ready Driver 592.27

Server PC antivirus and firewall software

Huorong Internet Security (火绒安全软件), Microsoft Defender Antivirus, and Windows Defender Firewall

Screenshots

A screen recording is attached showing the issue.

The recording demonstrates the cursor changing between the normal arrow, hand, text, and resize cursors. Each cursor shape change leaves the previous cursor image permanently visible at its old position. The stale cursor images are rendered above the current active cursor.

The issue is reproducible on the Android Moonlight client.

https://github.com/user-attachments/assets/88545495-181e-4216-bdb6-e4c98c498f0d

Relevant log output
No relevant log output available at this time.
Additional context

The issue reproduces consistently on multiple Android devices using the same Windows host:

HUAWEI MatePad 11 (2021), DBY-W09
HONOR 500 Pro

The Windows host itself does not show any cursor artifacts.

The problem is specifically triggered when the remote Windows cursor changes shape. For example:

Arrow → Hand
Hand → Text
Text → Resize cursor
Resize cursor → Arrow

Whenever the cursor shape changes, the previous cursor image remains permanently at its previous position.

The stale cursor image is rendered on top of the current active cursor, rather than simply appearing as a normal video-frame ghost/trail.

The current cursor continues to move and function normally.

Each additional cursor shape change creates another stale cursor image, so the artifacts accumulate over time.

The stale cursor images do not disappear automatically and are cleared when the Moonlight streaming session is restarted.

The issue reproduces at both 30 FPS and 60 FPS.

The issue reproduces with both Remote Desktop Mouse Mode enabled and disabled.

The issue also reproduces with Moonlight V+, so it does not appear to be specific to a single Moonlight Android build.

Host configuration:

Windows 11 Home, Version 25H2
NVIDIA GeForce RTX 5080 Laptop GPU
NVIDIA GeForce Game Ready Driver 592.27
NVIDIA App 11.0.9.251
Sunshine 2026.914.233613
DXGI capture

Changing Sunshine to Windows Graphics Capture (WGC) resulted in a 503 error in this environment, so WGC could not be tested as a comparison.

A screen recording is attached showing the cursor changing between different Windows cursor shapes and the stale cursor images accumulating.

Dominant language
C
Stars
7.5k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

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 moonlight-stream/moonlight-android

All issues in moonlight-stream/moonlight-android

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.