I'm trying to configure a Bluetooth audio sink with pulseaudio for my Raspberry Pi. I've been following various guides and making some progress on my own too, since every guide I've found seems to be outdated.
I have bluez running and working. I manage to pair it to my Mac Book Pro using the new bluetoothctl tool introduced with bluez 5.5, which centralizes the operation of the Bluetooth devices using a separate console interface. With it, I was able to pair my device, set it as trusted and even connect to it. However, I currently don't know how to configure the Audio Sink capability for my Raspberry's Bluetooth device so that it shows as one of the available "services" to my computer. In previous versions, the way to go was by modifying /etc/bluetooth/audio.conf and adding something like:
$this->bbcode_second_pass_code('', '[General]
Enable=Source,Sink,Media')
However, I don't think this file is being read right now, since the /etc/bluetooth folder doesn't even exist (tried creating it though).
Using the bluetoothctl tool, I can show the info of the Raspberry's device:
$this->bbcode_second_pass_code('', '[bluetooth]# show
Controller 00:02:72:C5:C8:15
Name: RaspberryPi
Alias: RaspberryPi
Class: 0x000000
Powered: yes
Discoverable: yes
Pairable: yes
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0505
Discovering: no')
Where it can be seen that there's nothing related to audio in the UUID rows. There is however for my Mac Book's device:
$this->bbcode_second_pass_code('', '[bluetooth]# info 20:C9:D0:82:75:62
Device 20:C9:D0:82:75:62
Name: brAzzis-MBP
Alias: brAzzis-MBP
Class: 0x3a010c
Icon: computer
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: GN (00001117-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)')
Which makes me think that the step I'm missing is adding that capability (Audio Sink?) somehow.
With bluetoothd running, I'm currently trying to run pulseaudio using: pulseaudio --start. This causes the following messages in /var/log/messages.log:
$this->bbcode_second_pass_code('', 'Jun 15 17:28:14 raspberrypi dbus-daemon[132]: dbus[132]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.37" (uid=1000 pid=888 comm="pulseaudio --start ") interface="org.bluez.Manager" member="GetProperties" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=945 comm="/usr/lib/bluetooth/bluetoothd ")
Jun 15 17:28:57 raspberrypi pulseaudio[958]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jun 15 17:28:57 raspberrypi pulseaudio[958]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11')
From the first line, it seems like pulseaudio is trying to communicate with bluetoothd through dbus, but the message is being filtered for a permissions-related issue. I'm running bluetoothd as root and pulseaudio as my user, brazzi. I added my user to the "lp" group, which as stated in /etc/dbus-1/system.d/bluetooth.conf, should enable me to talk with the daemon:
$this->bbcode_second_pass_code('', '<policy group="lp">
<allow send_destination="org.bluez"/>
</policy>')
I don't understand the second lines though... (I don't have a desktop environment, only XBMC running directly).
Any ideas what pieces of the puzzle might I be missing?
Any help will be really appreciated
Thanks!