Bluetooth fail to work with Debian Stretch

Hi all,
I had posted earlier that I have problems getting the Bluetooth to work on my Rock Pi4B running Debian stretch.

It cannot detect other bluetooth devices and neither can other bluetooth devices detect it during scanning.

I would appreciate your help and advice to get it to work.

Regards.
Liew

1 Like

Hi ycliew1,

There are some bugs in the current bluetooth service, you need to manually execute the following command after logging in the system.

sudo systemctl restart brcm_patch.service

Sorry for the inconvenience. We are checking the problem.

Hi ycliew1,

We found a temporary solution, please install rockpi4-brcm-patch package from stretch-testing of Radxa APT and reboot.

1 Like

Thanks but when i tried it, i get the message E: Unable to locate package rockpi4-brcm-patch.

Sorry but I new to linux and would appreciate if you could provide the instructions for installing this package.

Regards.
Liew

Worked here after installing rockpi4-brcm-patch and rebooting.

Hi Liew,

Try the following:

sudo apt-get update
sudo apt-get install rockpi4-brcm-patch
sudo reboot   #  reboots system

brcm-patch is installed, reboot system, restart service, but not working yet…

brcm-patch running:
     sudo systemctl status brcm-patch
     brcm-patch.service - Bluetooth Patch
       Loaded: loaded (/lib/systemd/system/brcm-patch.service; enabled; vendor preset: enabled)
       Active: **active (running) since Fri 2019-12-13 00:33:29 UTC; 6s ago**
      Process: 3409 ExecStop=/usr/bin/killall brcm_patchram_plus (code=exited, status=0/SUCCESS)
      Process: 3413 ExecStartPre=/usr/sbin/rfkill block bluetooth (code=exited, status=0/SUCCESS)
     Main PID: 3418 (brcm_patchram_p)
       CGroup: /system.slice/brcm-patch.service
               └─3418 /usr/bin/brcm_patchram_plus -d --enable_hci --no2bytes --use_baudrate_for_downloade --tosleep 200000 --baudrate 1500000 --patchram /lib/firmware/br

    Dec 13 00:33:29 rockpi4b systemd[1]: Starting Bluetooth Patch...
    Dec 13 00:33:29 rockpi4b systemd[1]: Started Bluetooth Patch.

This is interesting in syslog:

Dec 13 00:34:11 localhost dbus[663]: [system] Successfully activated service 'org.blueman.Mechanism'
Dec 13 00:34:11 localhost blueman-mechani[3453]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Dec 13 00:34:11 localhost blueman-mechanism: loading Rfcomm
Dec 13 00:34:11 localhost blueman-mechanism: loading Ppp
Dec 13 00:34:11 localhost blueman-mechanism: loading Network
Dec 13 00:34:11 localhost blueman-mechanism: loading RfKill
Dec 13 00:34:11 localhost kernel: [ 2578.679660] [BT_RFKILL]: rfkill_rk_set_power: set bt wake_host pin output high!
Dec 13 00:34:11 localhost kernel: [ 2578.721518] [BT_RFKILL]: ENABLE UART_RTS
Dec 13 00:34:11 localhost kernel: [ 2578.822503] [BT_RFKILL]: DISABLE UART_RTS
Dec 13 00:34:11 localhost kernel: [ 2578.822587] [BT_RFKILL]: bt turn on power
Dec 13 00:34:11 localhost systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 13 00:34:11 localhost systemd[1]: Started Load/Save RF Kill Switch Status.
**Dec 13 00:34:15 localhost kernel: [ 2582.524035] Bluetooth: hci0 sending frame failed (-49)**
Dec 13 00:34:15 localhost systemd[1]: Reached target Bluetooth.
Dec 13 00:34:15 localhost systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Dec 13 00:34:15 localhost systemd[1]: Stopped target Bluetooth.
Dec 13 00:34:15 localhost systemd[1]: brcm-patch.service: Control process exited, code=exited status=1
Dec 13 00:34:15 localhost systemd[1]: brcm-patch.service: Unit entered failed state.
Dec 13 00:34:15 localhost systemd[1]: brcm-patch.service: Failed with result 'exit-code'.
Dec 13 00:34:17 localhost systemd[1]: brcm-patch.service: Service hold-off time over, scheduling restart.
Dec 13 00:34:17 localhost systemd[1]: Stopped Bluetooth Patch.

Hey @domven

Reading your logs, I am not able to see where the issue is.

What the brcm-patch service does is automate the steps below, can try them individually and see where it fails: