Cannot map hotkey to virtual gamepad (RetroPad overlay) Android
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 — I saw #11021 but I can’t tell if the underlying issue is the same as mine.
Description
I am trying to map taking a screenshot to an on-screen button on Android. I am playing a Nintendo DS game, so I won’t need L2, R2, L3, or R3. R3 was mapped to “joystick touchscreen” in the core settings, but since I’m playing on smartphone, I decided I didn’t need it and unmapped it.
However, when I plugged in at external controller and mapped the “Screenshot” shortcut to R3, the on-screen R3 button did not do the same thing as the external controller’s R3.
And when I try to remap the shortcuts by setting the on-screen controller overlay to not disappear in the menu, the controller mapping dialog does not respond to any of the on-screen controller buttons, not just R3.
Video: https://streamable.com/t2shyw
Expected behavior
I should either be able to:
- map “Screenshot” to R3, then have the on-screen R3 button take a screenshot, or:
- map specifically the on-screen R3 button to taking a screenshot
Steps to reproduce the bug
Seen in the video:
- While the on-screen controller overlay is set to not hide in the menu...
- Go to hotkey mapping
- Try to map R3 to “Screenshot” using the Overlay
Version/Commit
1.20.0, Git 7a5fcd4
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android 15 (Motorola Moto g64)
Affected Cores
melonDS, possibly all others?
Environment information
No response
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 on Android 15 with the RetroPad overlay kept visible, then follow the hotkey mapping dialog while attempting to map R3 to Screenshot. Compare the external controller behavior with the on-screen R3 button; done means the overlay button can trigger Screenshot or can be mapped specifically to it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100