Mailinglist Archive: opensuse-factory (826 mails)

< Previous Next >
Re: [opensuse-factory] Workarounds for Buggy Bluetooth Audio
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Sat, 7 Oct 2017 22:57:38 +0200 (CEST)
  • Message-id: <nycvar.YFH.7.76.1710072206190.12786@zvanf-gvevgu.inyvabe>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Content-ID: <nycvar.YFH.7.76.1710072222520.12786@zvanf-gvevgu.inyvabe>


Somehow, your answer scaped my notice at the time :-(

El 2017-08-16 a las 19:34 +0200, Jan Engelhardt escribió:
On Tuesday 2017-08-15 15:21, Carlos E. R. wrote:
On 2017-08-15 06:45, Jan Engelhardt wrote:

Not sure what exactly the KDE tools do, but if you use
(just) bluetoothctl and pulseaudio - I can tell how if needed -
is the success rate better?

How? :-)

Wiki page perhaps?

There is no BT stack in XFCE to my knowledge, so I would like to try
another means.

# bluetoothctl
BT# power on
-- at this point, devices paired in the past are usable --

BT# agent on
BT# default-agent
BT# discoverable on
BT# pairable on
BT# scan on
BT# pair XX:XX:XX:XX:XX:XX


after that, the sound device should show up in `pavucontrol`
and be usable from media players when they are set to use libpulse.


Unfortunately, it does not work for me. I assume it has to be done as root (because you wrote '# bluetoothctl', not "> ..."


minas-tirith:~ # bluetooth
bluetooth-sendto bluetoothctl minas-tirith:~ # bluetoothctl [NEW] Controller 00:19:0E:05:6B:46 minas-tirith-0 [default]
[NEW] Device 00:24:7D:66:42:C9 Mobilis in mobile 5220 [NEW] Device 28:CC:01:9B:62:C7 MobilisInMobile
[NEW] Device 41:00:00:00:87:F1 Avenzo AV604
[bluetooth]# power on
[CHG] Controller 00:19:0E:05:6B:46 Class: 0x0c010c
Changing power on succeeded
[CHG] Controller 00:19:0E:05:6B:46 Powered: yes
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent Default agent request successful
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 00:19:0E:05:6B:46 Discoverable: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[DEL] Device 41:00:00:00:87:F1 Avenzo AV604
[DEL] Device 28:CC:01:9B:62:C7 MobilisInMobile
[DEL] Device 00:24:7D:66:42:C9 Mobilis in mobile 5220 [CHG] Controller 00:19:0E:05:6B:46 Class: 0x000000
[CHG] Controller 00:19:0E:05:6B:46 Powered: no
[CHG] Controller 00:19:0E:05:6B:46 Discovering: no
[CHG] Controller 00:19:0E:05:6B:46 Discoverable: no
[DEL] Controller 00:19:0E:05:6B:46 minas-tirith-0 [default]
[bluetooth]# scan on
No default controller available
[bluetooth]#


I try as user, I can not even start:

cer@minas-tirith:~> bluetoothctl [bluetooth]# power on
No default controller available
[bluetooth]# power off
No default controller available
[bluetooth]#


I restart "bluetooth.service" as root, then try to repeat the sequence as user,
same problem:

[bluetooth]# power on bluetoothd...
No default controller available
[bluetooth]#



Notice that bluetooth worked on this same hardware some releases ago, till XFCE removed the BT stack. I used it to transfer files to a phone.


minas-tirith:~ # zypper se pulseaudio-bluetooth
...
Loading repository data...
Reading installed packages...
No matching items found.
minas-tirith:~ #


minas-tirith:~ # rpm -qa | grep -i pulseaudio
pulseaudio-bash-completion-9.0-2.3.1.x86_64
pulseaudio-9.0-2.3.1.x86_64
pulseaudio-module-lirc-9.0-2.3.1.x86_64
pulseaudio-utils-32bit-9.0-2.3.1.x86_64
pulseaudio-lang-9.0-2.3.1.noarch
pulseaudio-utils-9.0-2.3.1.x86_64
xfce4-panel-plugin-pulseaudio-0.2.3-3.2.x86_64
pulseaudio-module-gconf-9.0-2.3.1.x86_64
pulseaudio-module-bluetooth-9.0-2.3.1.x86_64
pulseaudio-module-jack-9.0-2.3.1.x86_64
pulseaudio-module-zeroconf-9.0-2.3.1.x86_64
pulseaudio-module-x11-9.0-2.3.1.x86_64
minas-tirith:~ #



I remove and re-insert the USB-BT dongle and try again. This time I can not
pair:


cer@minas-tirith:~> bluetoothctl [NEW] Controller 00:19:0E:05:6B:46 minas-tirith-0 [default]
[NEW] Device 00:24:7D:66:42:C9 Mobilis in mobile 5220 [NEW] Device 28:CC:01:9B:62:C7 MobilisInMobile
[NEW] Device 41:00:00:00:87:F1 Avenzo AV604 <========
[bluetooth]# power on
[CHG] Controller 00:19:0E:05:6B:46 Class: 0x0c010c
Changing power on succeeded
[CHG] Controller 00:19:0E:05:6B:46 Powered: yes
[bluetooth]# default-agent No agent is registered
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 00:19:0E:05:6B:46 Discoverable: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:19:0E:05:6B:46 Discovering: yes
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[CHG] Device 41:00:00:00:87:F1 RSSI: -60
[bluetooth]# scan off
[CHG] Device 41:00:00:00:87:F1 RSSI is nil
Discovery stopped
[CHG] Controller 00:19:0E:05:6B:46 Discovering: no
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:19:0E:05:6B:46 Discovering: yes
[CHG] Device 41:00:00:00:87:F1 RSSI: -67
[CHG] Device 41:00:00:00:87:F1 RSSI: -76
[CHG] Device 41:00:00:00:87:F1 RSSI: -67
[CHG] Device 41:00:00:00:87:F1 RSSI: -75
[CHG] Device 41:00:00:00:87:F1 RSSI: -67
[CHG] Device 41:00:00:00:87:F1 RSSI: -75
[CHG] Device 41:00:00:00:87:F1 RSSI: -67
[CHG] Device 41:00:00:00:87:F1 RSSI: -76
[CHG] Device 41:00:00:00:87:F1 RSSI: -67
[CHG] Device 41:00:00:00:87:F1 RSSI: -80
[CHG] Device 41:00:00:00:87:F1 RSSI: -68
[CHG] Device 41:00:00:00:87:F1 RSSI: -81
[CHG] Device 41:00:00:00:87:F1 RSSI: -72
[CHG] Device 41:00:00:00:87:F1 RSSI: -63
[CHG] Device 41:00:00:00:87:F1 RSSI: -75
[CHG] Device 41:00:00:00:87:F1 RSSI: -61
[CHG] Device 41:00:00:00:87:F1 RSSI: -74
[CHG] Device 41:00:00:00:87:F1 RSSI: -65
[bluetooth]# pair 41:00:00:00:87:F1
Attempting to pair with 41:00:00:00:87:F1
Failed to pair: org.bluez.Error.AlreadyExists
[CHG] Device 41:00:00:00:87:F1 RSSI: -73
[CHG] Device 41:00:00:00:87:F1 RSSI: -81
[CHG] Device 41:00:00:00:87:F1 RSSI: -71
[CHG] Device 41:00:00:00:87:F1 RSSI: -63
[CHG] Device 41:00:00:00:87:F1 RSSI: -54
[CHG] Device 41:00:00:00:87:F1 RSSI: -63
[CHG] Device 41:00:00:00:87:F1 RSSI: -82
[CHG] Device 41:00:00:00:87:F1 RSSI: -66
[bluetooth]# info 41:00:00:00:87:F1
Device 41:00:00:00:87:F1
Name: Avenzo AV604
Alias: Avenzo AV604
Class: 0x240404
Icon: audio-card
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: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Headset HS (00001131-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v000Fp0000d0000
RSSI: -66
[CHG] Device 41:00:00:00:87:F1 RSSI: -76
[CHG] Device 41:00:00:00:87:F1 RSSI: -68
[CHG] Controller 00:19:0E:05:6B:46 Discoverable: no
[CHG] Device 41:00:00:00:87:F1 RSSI: -76
[CHG] Device 41:00:00:00:87:F1 RSSI: -66
[CHG] Device 41:00:00:00:87:F1 RSSI: -75
[CHG] Device 41:00:00:00:87:F1 RSSI: -65
[CHG] Device 41:00:00:00:87:F1 RSSI: -76
[CHG] Device 41:00:00:00:87:F1 RSSI: -63
[CHG] Device 41:00:00:00:87:F1 RSSI: -55
[CHG] Device 41:00:00:00:87:F1 RSSI: -63
[CHG] Device 41:00:00:00:87:F1 RSSI: -78
[CHG] Device 41:00:00:00:87:F1 RSSI: -67
[CHG] Device 41:00:00:00:87:F1 RSSI: -80
[CHG] Device 41:00:00:00:87:F1 RSSI: -68
[CHG] Device 41:00:00:00:87:F1 RSSI: -78
[CHG] Device 41:00:00:00:87:F1 RSSI: -66
[CHG] Device 41:00:00:00:87:F1 RSSI: -74
[CHG] Device 41:00:00:00:87:F1 RSSI: -62
[bluetooth]# scan off
[CHG] Device 41:00:00:00:87:F1 RSSI is nil
Discovery stopped
[CHG] Controller 00:19:0E:05:6B:46 Discovering: no
[bluetooth]#


I interpret is as the BT stack already paired in the past with the headphone. But why doesn't pair? The headphones is asking me (by voice, non stop) to enter the code '0000' in the computer, so it is seeing it.


[bluetooth]# show
Controller 00:19:0E:05:6B:46
Name: minas-tirith.valinor
Alias: minas-tirith-0
Class: 0x0c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-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:v1D6Bp0246d0529
Discovering: no
[CHG] Device 41:00:00:00:87:F1 Connected: yes
[CHG] Device 41:00:00:00:87:F1 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 41:00:00:00:87:F1 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 41:00:00:00:87:F1 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 41:00:00:00:87:F1 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 41:00:00:00:87:F1 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 41:00:00:00:87:F1 UUIDs: 00001131-0000-1000-8000-00805f9b34fb
[CHG] Device 41:00:00:00:87:F1 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[Avenzo AV604]#



Why has the prompt changed to "[Avenzo AV604]"? Is it connected?


[Avenzo AV604]# info 41:00:00:00:87:F1
Device 41:00:00:00:87:F1
Name: Avenzo AV604
Alias: Avenzo AV604
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Headset HS (00001131-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v000Fp0000d0000
[Avenzo AV604]#


Well, yes, it is connected! When, how? What did I do?


Well, pavucontrol show it under "Configuration", the profile is deactivated. It
offers two:

Headset Head Unit (HSP/HPP)

and I hear something about "Call active, Phone 1"

Or I can change to "High Fidelity Playback (A2DP Sink)"


I play a video, but I don't hear it on the phone, it is going to the laptop speakers. Ah, I have to go to the "Playback" tab and change the output device Mplayer is using.

:-)


Well, it does work, thanks. :-)
A bit complicated, though...


- -- Cheers
Carlos E. R.

(from 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAlnZP8oACgkQja8UbcUWM1xi5QD+L3HAH9ukXhiuudPY38HTLCIe
LMtQIKZRxJXuh9sWSxgA/jUTSUQZmrdTrJs6AvH2wcSjc4Yj2XdhzNRUJ2Qu20kx
=G4Gd
-----END PGP SIGNATURE-----
< Previous Next >
Follow Ups