[PROBLEM] Bluetooth Audio output (Transmitter)

[IriDium]

What I was doing is looking at other distro that have the BT audio working and seeing what the difference was between them.

Raspbian was the closest to our setup and the only obvious thing was pi-bluetooth. Didn't work either way.

[schiway]

(21st May, 2016 12:30 AM)IriDium Wrote:  What I was doing is looking at other distro that have the BT audio working and seeing what the difference was between them.

Raspbian was the closest to our setup and the only obvious thing was pi-bluetooth. Didn't work either way.

I succeed in RetroPie's kodi, But I could only get it work at the first time, after reboot, back to zero;
RetroPie is based-on Raspbian, isn't that the closest distro?

[f1vefour]

I'm going to follow this and see what happens.

[IriDium]

Well I THINK I have got this working reliably. Three times in succession .

However, the quality is appalling. Stuttering and glitches, so not something you'd really use.

(This might be a configuration issue or worse kernel issue.) If so, a new thread is required.

These are the steps I took.

Terminal

sudo apt-get install pulseaudio-module-bluetooth

(Thanks to @abdulmueid for the next steps)

Terminal

sudo gpasswd -a xbian pulse
sudo gpasswd -a xbian lp
sudo gpasswd -a pulse lp
sudo gpasswd -a xbian audio
sudo gpasswd -a pulse audio
sudo reboot

I also set the class but it didn't seem to make any difference.

Terminal

hcitool scan
hcitool inq
sudo hciconfig hci0 class 0xXXXXXX

(Where 0xXXXXXX is the class from the previous step

<Turn on BT scan mode>

Terminal

sudo bluetoothctl -a
power on
scan on
pair xxxx
trust xxxx
exit

Terminal

killall pulseaudio

<Restarts pulseaudio>

Terminal

sudo bluetoothctl -a
connect xxxx

After a little wait, something should be heard through the speaker.

After a reboot, it sometimes doesn't connect automatically so rerun the connect xxxxxxx

[Nachteule]

@IriDium

I'm still struggling with my BT Speaker on RPi3

in bluetoothctl I get

Terminal

[bluetooth]# list
Controller B8:27:EB:05:36:CB kmxbilr2 [default]
[bluetooth]# show
Controller B8:27:EB:05:36:CB
Name: kmxbilr2
Alias: kmxbilr2
Class: 0x0c0000
Powered: yes
Discoverable: no
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)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0517
Discovering: yes
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller B8:27:EB:05:36:CB Discoverable: yes
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# connect 00:75:58:67:2E:F3
Attempting to connect to 00:75:58:67:2E:F3
[CHG] Device 00:75:58:67:2E:F3 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:75:58:67:2E:F3 Connected: no
[CHG] Device 00:75:58:67:2E:F3 Connected: yes
[CHG] Device 00:75:58:67:2E:F3 Connected: no
[CHG] Controller B8:27:EB:05:36:CB Discoverable: no
[bluetooth]# info 00:75:58:67:2E:F3
Device 00:75:58:67:2E:F3
Name: SBLS 6 A1
Alias: SBLS 6 A1
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: yes
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

And in syslog I'm getting those strange messages:

Terminal

Jun 1 17:45:47 kmxbilr2 bluetoothd[1698]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource
Jun 1 17:45:47 kmxbilr2 bluetoothd[1698]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink
Jun 1 17:45:55 kmxbilr2 pulseaudio[8483]: [pulseaudio] main.c: Dieses Programm sollte ohne die Option --system nicht als Administrator ausgeführt werden.
Jun 1 17:45:55 kmxbilr2 pulseaudio[8486]: [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 1 17:45:55 kmxbilr2 pulseaudio[8486]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jun 1 17:45:55 kmxbilr2 pulseaudio[8486]: [pulseaudio] bluez4-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
Jun 1 17:45:55 kmxbilr2 bluetoothd[1698]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSource
Jun 1 17:45:55 kmxbilr2 bluetoothd[1698]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSink
Jun 1 17:46:08 kmxbilr2 bluetoothd[1698]: connect error: Invalid exchange (52)
Jun 1 17:46:14 kmxbilr2 bluetoothd[1698]: connect error: Invalid exchange (52)
Jun 1 17:47:09 kmxbilr2 bluetoothd[1698]: connect error: Invalid exchange (52)
Jun 1 17:47:15 kmxbilr2 bluetoothd[1698]: connect error: Invalid exchange (52)
Jun 1 17:50:23 kmxbilr2 bluetoothd[1698]: connect error: Invalid exchange (52)
Jun 1 17:50:31 kmxbilr2 bluetoothd[1698]: connect error: Invalid exchange (52)

Did you ever seen this behavior?

Btw, at my openSUSE 13.1 running notebook the BT speaker is running perfectly (using same command sequence)

[IriDium]

Never seen most of those errors. The bluez.error.Failed seems to be related to permissions or not rebooting after installing.

I remember seeing something about X11 in one of the config file, but can't remember where.

All mine was done on a fresh RPI2/3 install on a RPi3 and Amazon BT speaker.

Have you selected Pulseaudio in Kodi and seen that it is running.

Sometimes killall pulseaudio and reconnecting sometimes works.

[Nachteule]

Are you using RPi3's onboard BT?

After disabling that crappy onboard BT and using my 12 (!!!) year old BlueFritz! BT usb stick I got it working

Sound is ok and do not have any glitches, only using sound over BT and WLAN at the same time is not possible, playing video is extremely stuttering

[IriDium]

@Nachteule

Yes onboard!! I have a USB BT dongle, I'll give that a try and see I get the same problems.

I haven't tried BT and Wifi together.

If that works, I'll create a new thread for onboard BT chip problems.

[IriDium]

I've just done some testing on Libreelec (Couldn't get any sound output on XBian ) and the quality of the music is terrible on the RPI3 onboard BT controller, whereas using a BT dongle as the controller, the sound quality was acceptable.

So bottom line, the RPi3 BT controller should not be used for audio (Unless you have perforated eardrums or deaf).

[Nachteule]

(4th Jun, 2016 07:36 PM)IriDium Wrote:  I've just done some testing on Libreelec (Couldn't get any sound output on XBian ) and the quality of the music is

Can you tell me what your problem with XBian was/is?

Quote:terrible on the RPI3 onboard BT controller, whereas using a BT dongle as the controller, the sound quality was acceptable.

So bottom line, the RPi3 BT controller should not be used for audio (Unless you have perforated eardrums or deaf).

Yeah, Broadcom WLAN and BT chips are really crap. I have a Hummingboard for testing (has Broadcom WLAN and probably Broadcom BT chip onboard) and never was able to play 720p LiveTV stream over that Broadcom WLAN chip

[IriDium]

(4th Jun, 2016 09:52 PM)Nachteule Wrote:  Can you tell me what your problem with XBian was/is?

No idea. I've installed everything, added the permissions and rebooted. I can pair, trust and connect successfully, but no output to the speaker.

I'll reflash and start again. (nope same problem - no sound output).

[Nachteule]

(4th Jun, 2016 10:16 PM)IriDium Wrote:  

(4th Jun, 2016 09:52 PM)Nachteule Wrote:  Can you tell me what your problem with XBian was/is?

No idea. I've installed everything, added the permissions and rebooted. I can pair, trust and connect successfully, but no output to the speaker.

I'll reflash and start again. (nope same problem - no sound output).

Do you have dtparam=audio=on enabled in /boot/config.txt?

I had to disable this because PA uses onboard sound as default sink

[IriDium]

I'll give dtparam=audio=on a try but I also tried it on a cubox-i using the onboard BT with the same result - no sound to the speaker.

BTW: Bluetooth is not enabled by default on the IMX6 image.

[Nachteule]

(5th Jun, 2016 03:24 AM)IriDium Wrote:  I'll give dtparam=audio=on a try but I also tried it on a cubox-i using the onboard BT with the same result - no sound to the speaker.

Oh sorry, my fault. I had to disable it and not uncomment

Quote:BTW: Bluetooth is not enabled by default on the IMX6 image.

Really? Mine is enabled. Hmmm

[IriDium]

Is dtparam=audio=on set as default? If not, then I was running a vanilla RPi3 newly flashed image.

IMX6
/etc/default/bluetooth
BLUETOOTH_ENABLED=0

Not something I have set