(ANDROID) RetroArch Read Wrong Controller
Open
Nobody has claimed this yet.
input
platform: android
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
when the device is connected to the m100 plus controller, retroarch reads as Magicsee R1 instead of M100 plus.
Expected behavior
should retroarch read controller as M100 plus
Actual behavior
retroarch instead reads as magicsee R1 Handled controller
Steps to reproduce the bug
- Connect the M100 Plus controller to the device
- Open RetroArch
- Press any key on the controller to make RetroArch run autoconfig
- When running autoconfig, RetroArch will read as Magicsee R1 and not M100 Plus
- when trying to manually config, the gamepad and the right analog don't work. Right analogue only and Buttons like R1, R2, A, B and more
Version/Commit
- RetroArch: This only happens in Version 1.9.1 and above
Environment information
- OS: Xiaomi Redmi 4A / MIUI 10 / Android Nougat
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 controller autoconfiguration on the Xiaomi Redmi 4A with Android Nougat, using RetroArch 1.9.1 or later, then compare the M100 Plus and Magicsee R1 identification and manual mappings. Done means RetroArch identifies the controller as M100 Plus and the right analogue and reported buttons work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100