Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones

[Vincent Lefevre]

On 2021-09-10 09:12:48 +0300, Igor Kovalenko wrote:
> If your headphones support both HSP (Headset) and HFP (Handsfree)
> profiles, pulseaudio will now prefer HFP by default.
> This usually works fine unless bluez does not want to connect
> headphones with HFP profile for some reason.

I could eventually solve the problem, which was apparently caused by
some other Bluetooth audio device. Some details below...

> Please attach 'bluetoothctl info' for your headset,

zira:~> bluetoothctl devices
Device 7C:96:D2:4E:98:41 EDIFIER Luna Eclipse HD
Device 38:18:4C:4B:AC:93 WH-1000XM3

zira:~> bluetoothctl info 7C:96:D2:4E:98:41
Device 7C:96:D2:4E:98:41 (public)
        Name: EDIFIER Luna Eclipse HD
        Alias: EDIFIER Luna Eclipse HD
        Class: 0x00240428
        Icon: audio-card
        Paired: yes
        Trusted: no
        Blocked: no
        Connected: yes
        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)

zira:~> bluetoothctl info 38:18:4C:4B:AC:93
Device 38:18:4C:4B:AC:93 (public)
        Name: WH-1000XM3
        Alias: WH-1000XM3
        Class: 0x00240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
        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: 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: Amazon.com Services, Inc. (0000fe03-0000-1000-8000-00805f9b34fb)
[Vendor specific UUIDs]
        Modalias: usb:v054Cp0CD3d0452

What I did first is to upgrade again to pulseaudio 15.0+dfsg1-2, then
reboot. With my settings, I automatically connect to 7C:96:D2:4E:98:41
after logging in. As before, I could then connect to the headset with

  bluetoothctl connect 38:18:4C:4B:AC:93

which succeeded, but the headset wasn't recognized by PulseAudio 15.
I had to disconnect from both devices with 2 "bluetoothctl disconnect"
commands, then connect to the headset *alone* so that it could get
recognized by PulseAudio 15.

Now everything is OK, even after reboot with my usual settings.
I suppose that there was old or incomplete information for the
headphones. I wonder whether PulseAudio could have done something
to avoid this issue, or whether this is worth an announce (if this
is a known issue that may affect other users).

Note: With PulseAudio 15, I can now have both devices with the
A2DP Sink profile (this was not possible with PulseAudio 14, as
I could still check before upgrading again to PulseAudio 15).

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)