Mailinglist Archive: opensuse-factory (421 mails)

< Previous Next >
Re: [opensuse-factory] Workarounds for Buggy Bluetooth Audio
  • From: Chan Ju Ping <email@xxxxxxxxx>
  • Date: Thu, 28 Sep 2017 16:36:11 +0800
  • Message-id: <2713569.70P7jV9R3S@inari>
On Friday, 25 August 2017 02:03:49 +08 Jan Engelhardt wrote:
Right, I had another go with another sound device, and that reminded me of
all the things still needed to be done.

1. ensuring pulseaudio-bluetooth is installed (may need restart?)
2. (maybe bluetooth.service also needs a restart?)

3. bluetoothctl needs to be run as normal user, not root

4. after pair XX,
[bluetooth]> info D0:E7:82:64:21:90
Device D0:E7:82:64:21:90
Name: Cone
Alias: Cone
Class: 0x040000
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Audio Sink
(0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target
(0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu..
(0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control
(0000110e-0000-1000-8000-00805f9b34fb) 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) Modalias: bluetooth:v00F2p0001d0001

Obviously, the device in question needs an audio sink (A2DP) to work in the
first place...,

BT> connect XX:XX...

Hopefully things work. If not, `journalctl -u bluetooth.service` might help
if only to reveal permission errors.

On error, sad things like

bluetoothd[13692]: Sap driver initialization failed.
bluetoothd[13692]: sap-server: Operation not permitted (1)
bluetoothd[13692]: a2dp-sink profile connect failed for
D0:E7:82:64:21:90: Protocol not available
(=> pulseaudio-bluetooth not installed)

could show. Or, when successful:
: Endpoint registered: sender=:1.397 path=/MediaEndpoint/A2DPSource
: Endpoint registered: sender=:1.397 path=/MediaEndpoint/A2DPSink
: /org/bluez/hci0/dev_D0_E7_82_64_21_90/fd0: fd(22) ready
: /org/bluez/hci0/dev_D0_E7_82_64_21_90/fd1: fd(22) ready

Sorry for the late reply. Since this email, bluetooth audio has been working
far more consistently. It would seem that I just need to wait for a bit after
pairing and the audio will Just Work (TM), presumably because stuff is being
loaded in the background out of sight.

Also, I got new Bluetooth headphones that seem to work far better than either
of my previous devices.

Yay for progress!
< Previous Next >
This Thread
  • No further messages