What brand and model is your Android box
I use a USB BT dongle with a Realtek RTL8761B chip, cost $5, plugged it in and it automatically worked in CE.
Hi Portisch,
I am a little lost:
I have a X96 max plus box. and installed the latest nightly
dmesg | paste:
https://paste.coreelec.org/SurvivorClipping
BT is showing a strange behaviour:
I can connect to my audio device.
However I always get a âno replyâ error.
Funnily it works once! and I have no idea why?
I did now âhurry upâ connecting to my audio device after a reboot and it works.
I can choose âtrust and connectâ and it works.
However this is kind of not reproducible.
https://paste.coreelec.org/RelatingStudying
Here an updated dmesg log while it works.
perhaps the difference help to track this down.
BT just sucks.
1 Like
Is it an expected solution for the HK523SF chip?
Vontar X4 4g/32gb Amlogic s905x4 rev.c with latest 22.0-Piers_nightly_20250417 (Amlogic-no.aarch64)
No working BT/Wifi but with NG/NE both are working properly.
udevadm info /sys/bus/sdio/devices/* | paste
https://paste.coreelec.org/PatronBurnt
udevadm info /sys/bus/pci/devices/* | paste
lspci | paste
Both above commands shows âNo such deviceâ
dmesg | paste
Got an SK1, clearly NO is a work in progress compared to NG but the worst part is the bluetooth just not working.
I tried a usb bluetooth dongle and deactivated the internal UART one with hciconfig but it wonât even connect my UR01 remote without freezing which is even worst than the internal UART one.
The problem is clearly in BlueZ library like stated before so I have to use a keyboard for now.
Anyone else managed to use a remote using bluetooth?
My Ugoos X4Q extra with the UR01 connected through Bluetooth works great. Internal BT. In all BT remotes Iâve tested this one is the one that works better. No repair after reboot no nothing. Just always working
We did spot this bluez issue long time ago.
It happens with the new realtek chips and there is no solution since months
@Portisch , ok the internal is realtek on sk1 then⌠it does still freezes when I try with an asus USB-BT500 bluetooth dongle after deactivating the internal one though. Same dongle works fine on LibreELEC on a Beelink mini pc.
LE use mainline Linux, we use vendor.
Without a dmesg nothing can be done.
Oh I see, I just read on amlogicâs vendor maintained linux kernel specific for their SoCs. Now I understand why LibreELEC on my mini pc has so poor hdr support versus CoreELEC on my amlogic boxes.
Thank you to the CoreELEC team for your work!
Can you give me the steps to disable internal Bluetooth you have done please? Iâve got working dongle with sk1.
It looks like that USB-BT500 is using a Realtek RTL8761B chip.
I have a different USB BT dongle that also uses the same RTL8761B, working in CE NO. If you are having problems getting a remote to pair through CoreELEC settings, try it through SSH instead.
CoreELEC:~ # bluetoothctl
Show all BT controllers
[bluetooth]# list
Set the USB BT controller
[bluetooth]# select <bt-controller-mac>
Put your remote in pairing mode
[bluetooth]# scan on
[bluetooth]# pair <remote-mac>
[bluetooth]# trust <remote-mac>
[bluetooth]# connect <remote-mac>
You can add this line to your autostart.sh to select the USB BT dongle on startup
bluetoothctl select <bt-controller-mac>
Alternatively you can blacklist the driver for the internal BT controller. My experience is that this is a worse option because without the BT driver, the internal BT controller may not be able to go into a low power mode.
I found the correct hci number by doing this:
CoreELEC:/flash # hciconfig list
hci0: Type: Primary Bus: UART
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:6 SCO MTU: 255:12
UP RUNNING
RX bytes:1687 acl:0 sco:0 events:61 errors:0
TX bytes:3517 acl:0 sco:0 commands:60 errors:0
In this example, only the internal Bluetooth is present on the device as I unplugged my dongle now. The UART one is the internal bluetooth and the USB dongle will say USB instead of UART.
When I plugged both, hci0 became my dongle and hci1 became the UART. So, I did the following command to disable Bluetooth hc1 (UART):
hciconfig hci1 down
You can put it in autostart.sh:
sleep 5 # wait for the Bluetooth service to run at boot
hciconfig hci1 down # disable the internal Bluetooth controller
But I am unsure this is the correct way to disable the internal bluetooth. I know this didnât work for me as it was freezing when I tried to pair the UR01 remote.
I think the last post of YadaYada might be a better approach, I will try that and report back.
The method from YadaYada worked! My UR01 remote now connects and stays connected. Didnât reboot yet to test autostart thing but thanks for the help!
1 Like
Yeah I tried that and this never worked for me as well 
Tought you may have some other way of disabling it.
One option is to disable kernel module using by BT. But you need to find out which one is used with command lsmod.
echo "blacklist your_module_name" >> /storage/.config/modprobe.d/blacklist.conf
1 Like