Open Hew-ux opened 2 years ago
Does this issue only occur with the RPi3? Have you tried x86_64? Have you tried Raspberry Pi OS?
What pairing mode have you tried? It seems there are various compatibility modes.
I've tried pairing with Raspi OS on a Raspberry Pi 4 and it works as intended. The controller itself is fine.
As described, I tried two compatibility modes (it describes them as "Auto" and "PC"). "Auto" is the first I tried, which is able to connect only if you can type out its MAC address quickly enough before Batocera pairs with another device (which means, until this issue is fixed first then it will be impossible to ever pair this controller successfully using the menu) and "PC" results in the ghost connection, where the controller thinks it's connected but Batocera does not process any of its inputs.
My x86_64 OC does not have Bluetooth, so I cannot test that. However, one is on the way in the post.
So RPi4 with Batocera is also cactus?
I don't have Batocera on my RPi 4 for testing. I was testing that it could connect to my Pi 4 which is currently serving as my NAS.
Can you try Raspi OS on your Raspberry Pi 3 please.
I have tried on RaspiOS on my Pi 3 and it pairs fine.
Issue: Bluetooth "pairing failed" when attempting to pair with the Mocute-056 Bluetooth controller. The controller itself acts as if though pairing was successful and thinks it is sending controller inputs to the Batocera, however Batocera does not respond to them. This is on the Raspberry Pi 3 image but could be an issue on all platforms.
Reproduction:
Logs: bluetooth-agent.log.txt
Additional info: Attempting to pair manually via SSH fails too: Seems like the older bug of it automatically attempting to connect to other devices without instruction is still present.
Edit: Tried manually pairing again. If quick enough, you can input the command to pair right before Batocera automatically tries to pair with the undesired device:
Attempting to pair the device in its "PC" mode results in the similar "connected but no data is sent" state as before:
After doing this, if I make the device itself attempt to pair again, and then try to repair it in Batocera, it acts like it cannot pair anymore: