Bluetooth phone pairs but does not connect

Troubleshooting
1

Creating a bug report/issue

I would like to connect m android phone to the dietpi and play audio to the pi. But the dietpi wont connect to the phone. It does pair.
I have searched the existing open and closed issues but not find a solution

Required Information

  • DietPi version | 9.1.1
  • Distro version | Bookworm
  • Kernel version | Linux DietPi 6.1.21-v8+ #1642
  • Architecture | arm64
  • SBC model | RPi 3 Model B+ (aarch64)
  • Power supply used | (EG: 5V 1A RAVpower)
  • SD card used | SanDisk ultra

Additional Information (if applicable)

  • Software title | Bluetooth
  • Software title installed freshly

Steps to reproduce.

Bluetooth activated in dietpi-config, using bluetoothctl managed to pair my android phone but not able to connect using command connect . Get the following error message:

Attempting to connect to XX:XX:XX:73:DE:22
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

I also tried to connect my MacBook, running ubuntu and get the same. It initially connects then immediately disconnects and gives the same message

2

Searching the web brings the following [SOLVED] Bluetooth connect failed: br-connection-profile-unavailable. / Newbie Corner / Arch Linux Forums maybe it helps

3

Thanks, I also found this article. I did not find any thing that helped.

Do we use ALSA on dietpi or Pulse to control bluetooth?

4

there is no need to DietPi tool set. You could try to solution from the Arch Linux forum

5

There are several possible solutions that people on the forum report as working.

I’ve tried:

  • ControllerMode = bredr
    in
    /etc/bluetooth/main.conf
# Restricts all controllers to the specified transport. Default value
# is "dual", i.e. both BR/EDR and LE enabled (when supported by the >
# Possible values: "dual", "bredr", "le"
ControllerMode = bredr
  • restarted services

No change. The Macbook running ubuntu connects and then disconnects
The Android phone pairs, but does not connect

Some on the forum from the link report installing bluetoothpulse, solves the issue - hence my question “Do we use ALSA on dietpi or Pulse to control bluetooth?”

When I run sudo journalctl -u bluetooth I get

Mar 10 13:51:56 DietPi (uetoothd)[581]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Mar 10 13:51:56 DietPi systemd[1]: Starting bluetooth.service - Bluetooth service...
Mar 10 13:51:56 DietPi bluetoothd[581]: Bluetooth daemon 5.66
Mar 10 13:51:56 DietPi systemd[1]: Started bluetooth.service - Bluetooth service.
Mar 10 13:51:56 DietPi bluetoothd[581]: Starting SDP server
Mar 10 13:51:56 DietPi bluetoothd[581]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Mar 10 13:51:56 DietPi bluetoothd[581]: src/plugin.c:plugin_init() Failed to init vcp plugin
Mar 10 13:51:56 DietPi bluetoothd[581]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Mar 10 13:51:56 DietPi bluetoothd[581]: src/plugin.c:plugin_init() Failed to init mcp plugin
Mar 10 13:51:56 DietPi bluetoothd[581]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Mar 10 13:51:56 DietPi bluetoothd[581]: src/plugin.c:plugin_init() Failed to init bap plugin
Mar 10 13:51:56 DietPi bluetoothd[581]: Bluetooth management interface 1.22 initialized
Mar 10 13:51:57 DietPi bluetoothd[581]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 10 13:51:57 DietPi bluetoothd[581]: sap-server: Operation not permitted (1)
Mar 10 13:51:58 DietPi bluetoothd[581]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 10 13:51:58 DietPi bluetoothd[581]: sap-server: Operation not permitted (1)
Mar 10 13:51:58 DietPi bluetoothd[581]: Failed to set privacy: Rejected (0x0b)
Mar 10 13:51:58 DietPi bluetoothd[581]: Failed to set privacy: Rejected (0x0b)
Mar 10 13:52:01 DietPi bluetoothd[581]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Mar 10 14:14:55 DietPi systemd[1]: Stopping bluetooth.service - Bluetooth service...
Mar 10 14:14:55 DietPi bluetoothd[581]: Terminating
Mar 10 14:14:55 DietPi bluetoothd[581]: Stopping SDP server
Mar 10 14:14:55 DietPi bluetoothd[581]: Exit
Mar 10 14:14:56 DietPi systemd[1]: bluetooth.service: Deactivated successfully.
Mar 10 14:14:56 DietPi systemd[1]: Stopped bluetooth.service - Bluetooth service.
Mar 10 14:15:06 DietPi systemd[1]: Starting bluetooth.service - Bluetooth service...
Mar 10 14:15:06 DietPi (uetoothd)[2780]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Mar 10 14:15:06 DietPi bluetoothd[2780]: Bluetooth daemon 5.66
Mar 10 14:15:06 DietPi systemd[1]: Started bluetooth.service - Bluetooth service.
Mar 10 14:15:06 DietPi bluetoothd[2780]: Starting SDP server
Mar 10 14:15:06 DietPi bluetoothd[2780]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Mar 10 14:15:06 DietPi bluetoothd[2780]: src/plugin.c:plugin_init() Failed to init vcp plugin
Mar 10 14:15:06 DietPi bluetoothd[2780]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Mar 10 14:15:06 DietPi bluetoothd[2780]: src/plugin.c:plugin_init() Failed to init mcp plugin
Mar 10 14:15:06 DietPi bluetoothd[2780]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Mar 10 14:15:06 DietPi bluetoothd[2780]: src/plugin.c:plugin_init() Failed to init bap plugin
Mar 10 14:15:06 DietPi bluetoothd[2780]: Bluetooth management interface 1.22 initialized
Mar 10 14:15:06 DietPi bluetoothd[2780]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 10 14:15:06 DietPi bluetoothd[2780]: sap-server: Operation not permitted (1)
Mar 10 14:15:06 DietPi bluetoothd[2780]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 10 14:15:06 DietPi bluetoothd[2780]: sap-server: Operation not permitted (1)
Mar 10 14:21:22 DietPi bluetoothd[2780]: Terminating
Mar 10 14:21:22 DietPi systemd[1]: Stopping bluetooth.service - Bluetooth service...
Mar 10 14:21:22 DietPi bluetoothd[2780]: Stopping SDP server
Mar 10 14:21:22 DietPi systemd[1]: bluetooth.service: Deactivated successfully.
Mar 10 14:21:22 DietPi bluetoothd[2780]: Exit
Mar 10 14:21:22 DietPi systemd[1]: Stopped bluetooth.service - Bluetooth service.
Mar 10 14:21:22 DietPi systemd[1]: Starting bluetooth.service - Bluetooth service...
Mar 10 14:21:22 DietPi (uetoothd)[3165]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Mar 10 14:21:22 DietPi bluetoothd[3165]: Bluetooth daemon 5.66
Mar 10 14:21:22 DietPi systemd[1]: Started bluetooth.service - Bluetooth service.
Mar 10 14:21:22 DietPi bluetoothd[3165]: Starting SDP server
Mar 10 14:21:22 DietPi bluetoothd[3165]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Mar 10 14:21:22 DietPi bluetoothd[3165]: src/plugin.c:plugin_init() Failed to init vcp plugin
Mar 10 14:21:22 DietPi bluetoothd[3165]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Mar 10 14:21:22 DietPi bluetoothd[3165]: src/plugin.c:plugin_init() Failed to init mcp plugin
Mar 10 14:21:22 DietPi bluetoothd[3165]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Mar 10 14:21:22 DietPi bluetoothd[3165]: src/plugin.c:plugin_init() Failed to init bap plugin
Mar 10 14:21:22 DietPi bluetoothd[3165]: Bluetooth management interface 1.22 initialized
Mar 10 14:21:22 DietPi bluetoothd[3165]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 10 14:21:22 DietPi bluetoothd[3165]: sap-server: Operation not permitted (1)
Mar 10 14:21:22 DietPi bluetoothd[3165]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 10 14:21:22 DietPi bluetoothd[3165]: sap-server: Operation not permitted (1)
Mar 10 14:25:23 DietPi bluetoothd[3165]: src/service.c:btd_service_connect() a2dp-source profile connect failed for 30:09:C0:73:DE:22: Protocol not available

anyone got any ideas?

6

So, I also installed pulseaudio… still no difference

sudo apt install bluetooth pulseaudio-module-bluetooth

:face_with_symbols_over_mouth:

7

There are some errors about dbus, which is not installed by default on DietPi.

apt install dbus
8

dbus now installed, but still no joy.

Device 30:09:C0:73:DE:22 Paired: yes
Pairing successful
[CHG] Device 30:09:C0:73:DE:22 ServicesResolved: no
[CHG] Device 30:09:C0:73:DE:22 Connected: no


systemctl status bluetooth.service

returns

root@DietPi:~# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/bluetooth.service.d
             └─dietpi-process_tool.conf, dietpi-services_edit.conf
     Active: active (running) since Mon 2024-03-11 07:40:29 GMT; 12min ago
       Docs: man:bluetoothd(8)
   Main PID: 472 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 779)
        CPU: 392ms
     CGroup: /system.slice/bluetooth.service
             └─472 /usr/libexec/bluetooth/bluetoothd

Mar 11 07:40:29 DietPi bluetoothd[472]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Mar 11 07:40:29 DietPi bluetoothd[472]: src/plugin.c:plugin_init() Failed to init mcp plugin
Mar 11 07:40:29 DietPi bluetoothd[472]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Mar 11 07:40:29 DietPi bluetoothd[472]: src/plugin.c:plugin_init() Failed to init bap plugin
Mar 11 07:40:29 DietPi bluetoothd[472]: Bluetooth management interface 1.22 initialized
Mar 11 07:40:29 DietPi bluetoothd[472]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 11 07:40:29 DietPi bluetoothd[472]: sap-server: Operation not permitted (1)
Mar 11 07:40:29 DietPi bluetoothd[472]: Failed to set privacy: Rejected (0x0b)
Mar 11 07:41:42 DietPi bluetoothd[472]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Mar 11 07:48:03 DietPi bluetoothd[472]: src/service.c:btd_service_connect() a2dp-source profile connect failed for 30:09:C0:73:DE:22: Protocol not available

I managed to connect and old iPad ! but not my phone… very odd

9

Then it’s probably a compatibility problem, what phone do you try to connect?

10

an android, Motorola g60s

11

I tried it on my other dietpi with a pi4 and same issue

12

Hm it’s already paired, did you try also trust and connect?
I also think, when it’s working with another device there is maybe a incompatibility with the motorola phone.

13

it might be a general problem and not dedicated to DietPi. Because it seems not working on a Ubuntu system as well?

14

Yea, my guess is Motorola did not implement it right, or violated some specs or something?!

15

correct, it does not connect with ubuntu. Have only success with and old iPad.

16

could be. Yes, I did trust and connect. does do trust, but not connect

17

This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.