Touchpad cannot be used effectively
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Description
I can use the Touchpad with Sony DualShock 4 or DualSense to navigate in GNU/Linux, both for MATE (the desktop environment) and for RetroArch.
In Android TV the touchpad cursor is visible and functional, but it does not work as expected in RetroArch (RetroArch_ra32.apk).
Actual Behavior
The touchpad cannot navigate
The navigation is so wildly inconsistent that it becomes completely unusable. The cursor jumps erratically in random directions before suddenly freezing.
The touchpad cursor is not visible
While the menu entries can be selected and changed, there is no visible mouse cursor to indicate the current selection. This creates a frustrating experience due to the touchpad's sensitivity and the inability to see the cursor.
Additional Notes
This issue significantly hampers the user experience when navigating the RetroArch interface using a touchpad-enabled controller on Android TV devices. A fix would greatly enhance usability.
Expected behavior
No response
Steps to reproduce the bug
- Download the RetroArch APK from retroarch.com.
- Install it on any Android TV device
- Connect a compatible controller with a touchpad (e.g., Sony DualShock 4 or DualSense).
- Launch RetroArch.
- Press any button to establish the connection with the controller.
- Lightly touch the touchpad.
Version/Commit
1.22.2
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
RetroArch_ra32.apk
Affected Cores
No response
Environment information
- Operating System: Android TV 14
- Device: Google TV Streamer
Relevant log output
Contributor 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.
Research direction
Start by reproducing the issue with RetroArch_ra32.apk on an Android TV device using a DualShock 4 or DualSense touchpad, following the listed steps. Investigate the frontend's touchpad navigation and cursor behavior; done means consistent navigation and a visible cursor in the RetroArch interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100