Bluetooth RetroPie Setup Script Issues
-
@mitu Yes I have. If it helps, I am able to successfully connect with bluetooth on other images such as the latest version of Raspberry Pi OS released on March 4th
-
RetroPie is based on Raspberry Pi OS (the Lite version), so if you've updated RetroPie-Setup and the OS/packages, it should have the same software as on a Raspberry Pi OS image.
If you've update RetroPie-Setup, can you post the exact version of RetroPie you have installed ? -
@mitu I see. Yes, I'm running version 4.7.11
-
Can you connect via SSH (as the normal
pi
user), runbluetoothctl
from that login session and then try again the pairing from RetroPie-Setup ?EDIT: if you don't have SSH enabled, you can exit EmulationStation, login in a second screen (
Alt+F2
would get you a 2nd login screen,Alt+F1
switches back to the main screen) and startbluetoothctl
from there. You can run RetroPie-Setup on the 1st login screen withcd RetroPie-Setup sudo ./retropie_setup.sh
-
@mitu Okay, I just did it, and it froze at the same spot on the GUI. bluetoothctl spat out the devices in range while doing the search, that ended with the following lines:
[CHG] Device 8:BIT:DO:MAC:ADDRESS:HERE Connected: yes [CHG] Device 8:BIT:DO:MAC:ADDRESS:HERE Connected: no
So it looks like it connected for a split second maybe? The controller kept acting like it was still syncing until it timed out.
A minute later it spat out this stuff:
[DEL] Device RANDOM:DEVICE RANDOM-DEVICE [DEL] Device RANDOM:DEVICE RANDOM-DEVICE
EDIT: the device now shows up in the list of paired devices, but refuses to connect.
-
@jtcuth48 You should remove the device from the list of paired devices before re-attempting to pair.
-
@mitu Unfortunately, same result, freezing when choosing "DisplayYesNo". I even tried the other options but no dice
-
Hi,
i have exactly the same problem with a 8bitdo zero 2.
Can't make it to connect in any way. -
@link3384 Yeah, I've tested a friend's board (same model as mine) and it has the same issue. I think it's a problem on Raspberry Pi OS' end. I've had some luck with running "sudo service bluetooth restart" and then connecting, but it's hit or miss. Sorry I can't offer more assistance, this is a real bummer
-
I think it is a problem of retropie 4.7.1.
I can't find retropie 4.6 anywhere to test if it works there.
When i put recalbox to the sd card the 8bitdo connects in one minute and it works fine. -
Same exact problem here - Thanks
-
I'm having same issue with raspberry version 1.4.
@jtcuth48 could you check your board version using following command?
cat /proc/cpuinfo/ -
Here is another piece of information. I have two Raspberry 4 boards. One was upgraded to boot from USB {SSD) the one other one has not been upgraded.
Bluetooth devices connect right away to the one that has not been upgraded. On the one with the USB boot upgrade will not connect at all, it will not complete the security phase of the Bluetooth connection process.
Also I have tried both boards using Batocera and the connection is flawless. But I prefer to use Retropie for my emulation.
Thanks 😊
-
EDIT: A cheap USB bluetooth dongle combined with disabling onboard bluetooth fixed the issue, the controller connected like butter. Looks like the issue is likely with the bluez package in Pi OS.
Guys, I've had success with both Recalbox and Batocera straight out of the box, but Raspberry Pi OS itself has the same issues as Retropie so I think it's on their end possibly, and I don't think it's an issue with the 8bitdo issue either, I think the version of bluez preinstalled is janky. Until this is fixed, I think I may stick to recalbox because it seems to just work.. I would prefer Retropie but if it doesn't work then I don't know.
@pscotto1234, the output of that command is:
processor : 0 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 1 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 2 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 3 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 Hardware : BCM2711 Revision : b03114 Serial : 100000002a9f6133 Model : Raspberry Pi 4 Model B Rev 1.4
-
@jtcuth48 said in Bluetooth RetroPie Setup Script Issues:
EDIT: A cheap USB bluetooth dongle combined with disabling onboard bluetooth fixed the issue, the controller connected like butter. Looks like the issue is likely with the bluez package in Pi OS.
Guys, I've had success with both Recalbox and Batocera straight out of the box, but Raspberry Pi OS itself has the same issues as Retropie so I think it's on their end possibly, and I don't think it's an issue with the 8bitdo issue either, I think the version of bluez preinstalled is janky. Until this is fixed, I think I may stick to recalbox because it seems to just work.. I would prefer Retropie but if it doesn't work then I don't know.
@pscotto1234, the output of that command is:
processor : 0 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 1 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 2 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 3 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 270.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 Hardware : BCM2711 Revision : b03114 Serial : 100000002a9f6133 Model : Raspberry Pi 4 Model B Rev 1.4
You have a 1.4 model. I said in another 3d as well that the problem is mainly related with new raspberry.
I think that the problem can only be resolved by upgrading bluetooth driver.
@jtcuth48 could you tell me what BT dongle are you using? -
-
Hi, I was about to post this exact topic.
I tried with an SN30 Pro and a Switch Pro and am experiencing the same problem - the setup utility freezes when selecting a security mode.
Pi Model or other hardware: Raspberry Pi 4B
Power Supply used: Canakit Pi 4
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.7.1
Built From: Pre-made image from website
USB Devices connected: USB storage stick, keyboard
Controller used: 8BitDo SN30 Pro, Switch Pro controllerOccasionally after the failed pairing I'm unable to remove the device:
Restarting the Pi seems to fix this.EDIT:: Found a workaround from this thread on the official forums:
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=304000&hilit=Bluetooth&start=25
At the command line, type these commands:
sudo systemctl daemon-reload sudo systemctl restart bluetooth
Then restart emulationstation and go to Bluetooth config. This allows me to pair and use the SN Pro. Rebooting breaks it again, but you don't need to re-pair - type the above into command line again, then go to Connect all paired devices in the Bluetooth config and make sure your controller is on.
EDIT 2:: "Pair all Connected" isn't working very well for me anymore. For best results, after every reboot, restart the daemon/bluetooth service, remove the paired device, then pair again. This also will fail occasionally; it seems like if I get the org.bluez.error screen on a boot, nothing will get it to work. Try rebooting again.
-
@loopsheloop said in Bluetooth RetroPie Setup Script Issues:
Occasionally after the failed pairing I'm unable to remove the device:
What Pi4 model do you have ? Can you run
cat /proc/cpuinfo
and post the output ? -
@mitu said in Bluetooth RetroPie Setup Script Issues:
What Pi4 model do you have ? Can you run
cat /proc/cpuinfo
and post the output ?It's the Pi 4 B. Results look pretty similar to the one previously posted:
2 lines that the console remembers isn't the worst workaround I've ever dealt with :) Thanks for looking at this!
-
@loopsheloop said in Bluetooth RetroPie Setup Script Issues:
It's the Pi 4 B.
Just wanted to confirm this is a 1.4 model (last line) - thank you. Looks like it's not an issue with older models (as @pscotto1234 also noticed), I'm wondering what's different in 1.4 vs older models during the Bluetooth start-up that requiring a restart of the
bluetooth
service necessary.I have one of the older models (1.1) and can't seem to replicate this either with my current install or with a fresh one.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.