Pull #15597 No Longer Working in RetroArch Android 1.20.0
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
When using an S Pen stylus on my Galaxy ZFold, the app responds to the tip of the stylus being near the screen by constantly "auto-clicking" whatever buttons it's near. Makes many Nintendo DS games effectively unplayable.
Previous commit that is supposed to fix this: https://github.com/libretro/RetroArch/pull/15597
Expected behavior
Using a stylus on RA Android previously would have the preview circle under the tip of the stylus, but the app would not react to it unless the tip made contact with the screen surface.
Steps to reproduce the bug
- Open RetroArch Android 1.20.0 on a compatible device.
- Use an S Pen or similar compatible stylus to navigate the application instead of touch controls.
- Observe menus being clicked and dragged instead of buttons being selected by touching them with the stylus.
3a. Open a game and notice that moving the stylus near any of the onscreen controls "auto-clicks" them when the stylus is near
Version/Commit
1.20.0
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android 15
Affected Cores
No response
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 reviewing pull request #15597 and the Android input-handling changes it introduced, then reproduce the issue on Android 15 with an S Pen or compatible stylus. Done means hover or proximity alone no longer activates menus or on-screen controls, while contact still selects and drags as expected.
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