All Bluetooth Controller show up as the same Xperia Play on new Android Tablet
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
Hi there,
i bought a new Android Tablet, an ALLDOCUBE iPlay 70 mini Ultra and i am trying to connect two controller to it or better said, i want to use them in RetroArch (installed from F-Droid)
In Android, they get detected as the following:
Controller 1 --> Switch Pro Controller (Correct)
Controller 2 --> 8bitdo M30 (Correct)
Inside RetroArch, both controller get detected as the same Xperia Play controller. That means both are controller one. When i go into the controller settings, nothing is plugged into Port 2. According to RetroArch, there is only one controller plugged into Port 1 called Xperia Play.
When i control with any of the two controller, both control this Xperia Play Controller. So its impossible to me to play with 2 controllers.
I reset all settings inside RetroArch and restarted with new blanko settings and even re-installed the app and restarted and re-paired the controller, nothing changes.
Expected behavior
They should be detected as Switch Pro Controller and 8bitdo M30
They should not control the same controller but be detected as two independent.
Steps to reproduce the bug
- Install RetroArch
- Press something on the Switch Pro Controller
- It says "Xperia Play was connected to Port 1"
- Press something on the 8bitdo M30 Controller
- There is no Popup that says a new controller was detected
- Both controllers control the same controller in Port 1
Version/Commit
1.21.0
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android 15
Affected Cores
All
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
No source file or test is named. Start by reproducing on Android 15 with a Switch Pro Controller and an 8bitdo M30, then inspect the controller detection and port-assignment path and capture relevant logs. Done means both devices retain their distinct names and are assigned to independent ports instead of sharing Xperia Play on Port 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100