Solved Enable Bluetooth CSL - V4.0 USB on recalbox x86_64

[daarky]

Hi!

I installed Recalbox 6.0 RC1 on an USB stick (SanDisk Ultra Fit 64 GB USB 3.1) for usage on my laptop (Acer Aspire V5-573g). Currently I'm using the internal Intel 7260.HMWWB.R Dual Band Wireless-AC 7260-PCIe WLAN / 802.11AC, Bluetooth 4.0 Mini-PCI-Card to connect my 8bitdo SFC30 controllers via bluetooth. Since the connection is very laggy and the distance before loosing the connection is very small (I noticed the same behaviour using the controllers in Windows) I decided to buy a CSL - V4.0 USB nano adapter Bluetooth with DEL Class 4.0. While the USB dongle works fine when booting into Windows (the USB dongle starts blinking and I can connect the controllers), I have problems using the USB bluetooth dongle when booting into recalbox. The bluetooth dongle doesn't blink and each time I try to connect the controller recalbox uses the Intel bluetooth.

Is there a way to disable the internal bt and enable the USB bluetooth? I have read some thread regarding a similar problem for the RPI3 (blacklisting the internal bt using dtoverlay=pi3-disable-bt) but I doubt that this will work on my PC.

Any help would be appreciated.

[daarky]

Edit:
I managed to disable the onboard Bluetooth dongle and enable the USB bt via the terminal:
hcitool --all (displays both internal as hci0 and usb bt as hci1)
hcitool hci0 down
hcitool hci1 up
Afterwards I am able to pair my 8bitdo SFC30 manually as described in the recal box wiki.

Problem left: The settings are not saved. After a restart the onboard bt is used again. Maybe it is overwritten by some other settings, maybe bluetoothctl?
Is there a way to save the settings or to switch from hci0 to hci1 via bluetoothctl?

[daarky]

Edit2:
I solved my problem.
For anyone else who has similar problems with switching from an onboard bluetooth to a second usb bluetooth dongle:
editing 'recalbox/etc/udev/rules.d/81-bt-power.rules' did the trick. I changed Kernel=="hci0" to "hci1" and after a reboot the usb dongle powers up.
I am not sure but it's maybe necessary to additionally switch /update the default agent via bluetoothctl. Afterwards controllers can be paired manually as described here.