Bluetooth testers wanted!

[azvarel]

@bkg2k they have similar addresses, but they are not the same

[chris72]

I use a Nintendo Switch Pro Controller with a Raspi 3b+. With the internal bluetooth the controller didn't reconnect after rebooting. With an external Logilink Bluetooth Stick the controller will reconnect after reboot.

[xHardcore]

@Bkg2k the system continues to report N you have any solution?

[xHardcore]

This post is deleted!

[Bkg2k]

@xhardcore Make sure you have an empty line under options bluetooth disable\_ertm=Y in the file /etc/modprobe.d/bluetooth.conf.
Go to the end of line and press return if not sure. Then save and reboot

[xHardcore]

@bkg2k now it worked, thank you

[murmelbahn]

@bkg2k said in Bluetooth testers wanted!:

@xhardcore Make sure you have an empty line under options bluetooth disable\_ertm=Y in the file /etc/modprobe.d/bluetooth.conf.
Go to the end of line and press return if not sure. Then save and reboot

Sorry but this didnt work for me:( I've logged in via SSH as root, maybe this is a problem?

[Bkg2k]

@murmelbahn Can you try options bluetooth disable_ertm=Y (w/o the backslash) ?

[Alexander]

For me is equal

PI3B with internal bluetooth
PI3B with internal bluetooth disabled, and external dongle "Plugable Technologies USB-BT4LE" attached
1 8bitdo SF30 Pro (latest firmware 1.30)

No changes or improvements for me:

Controller always takes about 5-10 seconds to connect the first time or after waking up.
Sometimes doesn't reconnect after waking up
Never reconnects after reboot

Hope this helps a bit

[Scudmuffer]

I have noticed that when pairing my bluetooth controller (GameSir G3s YES I KNOW IT HAS ISSUES IN THE COMPATIBILITY LIST) that it works flawlessly in emulation station. Once the emulators launch, however, there is no functionality at all. While testing some of these options I realized the only time I see the retroarch message "100% connected [insert controller here]" is when I send an SSH reboot or poweroff command.
I stopped emulation station as well to see if it was holding onto the bluetooth handshake, but never saw that message.
Looks like something is not pushing the bluetooth controls over to the launcher.

[Voytex86]

My config:

• Raspberry Pi 3 B+ with latest version of Recalbox OS (onboard Bluetooth and WiFi disabled)
• Retroflag NESPi CASE+ with "safe shutdown" scripts installed
• FEASYCOM FSC-BP119 100m USB Bluetooth Dongle (CSR8510A10 chipset)
• 8BitDo SN30 pro controller (dinput)
• Verbatim 32GB USB 2.0 drive as an external storage
• Retroflag USB controller
• USB keyboard

The system reports "Y", but my 8BitDo SN30 pro does not connect automatically after rebooting. So I have to turn it off and turn it on again while the system is already loaded in "main menu" - this is the only way to reconnect
When the controller is connected it works well during emulation.

How about editing the /etc/bluetooth/main.conf file?

[newbell]

The solution worked for me with a XBOX ONE S controller. I am able to move through recalbox menus.
My issue is that when I open any game from any system, the controller doesnt work. It only works when I am at recalbox menus.
Thanks.

[LeManchot]

Hello,
I have some trouble with my Moga Pro Power... Can't connect it to Recalbox 7.
However, I have no problem with my 2 8bitdo.
Should I try that on Recalbox 7 ?

[Benzitor]

Ps4 all good
Switch pro, not yet running
8bitdo ok

[MorgS9]

When I tried to save the bluetooth.conf file, nano reported
"Error writing /etc/modprobe.d/bluetooth.conf: Read-only file system"

I tried using chmod to give the file write perms, and it gave me the same Read-only file system error.

Am I doing something wrong? I am using the latest version of PuTTY, and using Recalbox 7.1.1 Reloaded installed with NOOBS on a Raspberry Pi 4 B+.

[Pitch64]

@MorgS9 Via ssh before you open the file:

mount -o remount,rw /

[acris]

by default , ERTM = 1, no need to test
it 's too old.