[Android] Mouse support not working in menus despite being enabled (Bluetooth / USB hub)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
Research direction
The payload names no source files, tests or entry points, so start by finding where the menu mouse-support setting is read and where Android touch and pointer events reach the menu. The relevant log output section is empty, so reproduce on an Android device with a Bluetooth or USB mouse and capture logcat first. Done means mouse clicks and scrolling move menu selection on Android, confirmed on the reported device or an equivalent one.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Description:
After enabling mouse support under the menu controls in RetroArch on Android, mouse inputs (clicks, cursor movement, and scrolling) do not register or affect menu navigation at all.
Note that the mouse works normally throughout the rest of the Android TV system and other apps—the issue is isolated to RetroArch.
Actual Behavior
Nothing works. No cursor gestures, clicks, or scroll actions change selected menu items or interact with the menu interface in any way.
Expected behavior
The mouse cursor should be visible (or register gestures), allow clicking/selecting menu items, and the scroll wheel should scroll through menu lists.
Steps to reproduce the bug
- Connect a mouse to an Android device (tested via Bluetooth / USB hub).
- Open RetroArch.
- Navigate to Settings -> User Interface -> Menu Controls.
- Toggle Mouse Support on.
- Attempt to use the mouse to navigate menus (move cursor, click items, or use the scroll wheel).
Version/Commit
1.22.2
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android TV 14, Google TV Streamer
Affected Cores
Environment information
- OS: Android TV 14
- RetroArch Version: 1.22.2 nightly 2026-11-13
- Device: Google TV Streamer
- Input Device: Logitech M575 via Bluetooth
Relevant log output
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 2.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·