Bug ID 1094255
Summary Bluetooth headset wrong profile (HSP instead of A2DP)
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Sound
Assignee tiwai@suse.com
Reporter ivan.topolsky@isb-sib.ch
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Since updating my laptop today
(pulseaudio 11.99.1-1.1
bluez 5.49-3.1)


I'm hit with a bug similar to this old (Pulseaudio 10) one :
https://bugs.freedesktop.org/show_bug.cgi?id=92102#c28

When connected automatically, the headset is only available in HSP/HFP:

# pacmd list-cards
>    index: 4
>        name: <bluez_card.00_0D_44_D0_85_20>
>        driver: <module-bluez5-device.c>
>        owner module: 32
>        properties:
>                device.description = "UE9000"
>                device.string = "00:0D:44:D0:85:20"
>                device.api = "bluez"
>                device.class = "sound"
>                device.bus = "bluetooth"
>                device.form_factor = "headphone"
>                bluez.path = "/org/bluez/hci0/dev_00_0D_44_D0_85_20"
>                bluez.class = "0x240418"
>                bluez.alias = "UE9000"
>                device.icon_name = "audio-headphones-bluetooth"
>        profiles:
>                headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: unknown)
>                off: Off (priority 0, available: yes)
>        active profile: <headset_head_unit>
>        sinks:
>                bluez_sink.00_0D_44_D0_85_20.headset_head_unit/#4: UE9000
>        sources:
>                bluez_sink.00_0D_44_D0_85_20.headset_head_unit.monitor/#8: Monitor of UE9000
>                bluez_source.00_0D_44_D0_85_20.headset_head_unit/#9: UE9000
>        ports:
>                headphone-output: Headphone (priority 0, latency offset 0 usec, available: unknown)
>                        properties:

>                headphone-input: Bluetooth Input (priority 0, latency offset 0 usec, available: unknown)
>                        properties:

# pacmd set-card-profile 4 a2dp_sink
> No such profile: a2dp_sink


But if I manually disconnect and reconnect from the command line (as mentioned
in the old bug), A2DP becomes available again :

# bluetoothctl
# devices
> Device 00:0D:44:D0:85:20 UE9000
# disconnect 00:0D:44:D0:85:20
> Attempting to disconnect from 00:0D:44:D0:85:20
> Successful disconnected
# connect 00:0D:44:D0:85:20
> Attempting to connect to 00:0D:44:D0:85:20
> [CHG] Device 00:0D:44:D0:85:20 Connected: yes
> Connection successful
> [CHG] Device 00:0D:44:D0:85:20 ServicesResolved: yes
# exit
# pactl list cards

> Card #6
>        Name: bluez_card.00_0D_44_D0_85_20
>        Driver: module-bluez5-device.c
>        Owner Module: 35
>        Properties:
>                device.description = "UE9000"
>                device.string = "00:0D:44:D0:85:20"
>                device.api = "bluez"
>                device.class = "sound"
>                device.bus = "bluetooth"
>                device.form_factor = "headphone"
>                bluez.path = "/org/bluez/hci0/dev_00_0D_44_D0_85_20"
>                bluez.class = "0x240418"
>                bluez.alias = "UE9000"
>                device.icon_name = "audio-headphones-bluetooth"
>        Profiles:
>                headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
>                a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: yes)
>                off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
>        Active Profile: headset_head_unit
>        Ports:
>                headphone-output: Headphone (priority: 0, latency offset: 0 usec, available)
>                        Part of profile(s): headset_head_unit, a2dp_sink
>                headphone-input: Bluetooth Input (priority: 0, latency offset: 0 usec, available)
>                        Part of profile(s): headset_head_unit
#pacmd set-card-profile 6 a2dp_sink


It might be related to this bug :
https://bugzilla.opensuse.org/show_bug.cgi?id=987114

(In that case no any sound profile shows up in PulseAudio, not even A2DP. I had
the problem 1 week ago, but did not investigate any further).


The hardware is a Logitech Ultimate Ears 9000 noisecancelling bluetooth
headset.
It has been working flawlessly in the past.


You are receiving this mail because: