Bluetooth headset HSP/HFP mode not working in Bionic

Bug #1768625 reported by Nikhil on 2018-05-02
274
This bug affects 55 people
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Undecided
Unassigned

Bug Description

There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So!

Steps to reproduce:
1. enable bluetooth on computer and switch on the headset.
2. pair and connect the headset
3. go to settings to switch headset to HSP/HFP mode to enable mic
4. save and close window.

Expected behaviour:
1. mic should be enabled and headset should be usable to attend calls on laptop.

Behaviour in error:
1. Headset profile switches back to A2DP and mic is not enabled.

I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE.

Software versions:
Kernel: 4.15.0-20-generic
Bluez version: 5.48-0ubuntu3
pulseaudio: 1:11.1-1ubuntu7
pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

Additional information:
Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset:

Output from Headset section:
        profiles:
                a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown)
                headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no)
                off: Off (priority 0, available: yes)
        active profile: <a2dp_sink>

tags: added: a2dp bionic mic
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Owais Lone (loneowais) wrote :

I'm facing the same issue with Ubuntu 18.04 and Kubuntu 18.04. I also tried a live CD which had the same problem.

I tried Apple Airpods and a Sennheiser headset and had the same issue with both. For me personally, this is the biggest issue I have with Ubuntu 18.04 right now as it doesn't let me use a wireless headset for meetings so it affects my work.

Gustavo Niemeyer (niemeyer) wrote :

The issue is most probably that your headset implements the HFP profile, but not the HSP profile, and pulseaudio does not yet support the HFP profile despite what that line says (HSP/HFP). To confirm, run bluetoothctl, and type something like:

> devices
(...)
> info 11:22:33:44:55:66

Where the address is the one for your headset. It will likely display something like this:

        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)

If so, the "Headset" (HSP) profile is missing.

Changed in pulseaudio (Ubuntu):
status: Confirmed → Incomplete
Christopher Berner (cberner) wrote :

Actually, for the Bose QC35 II, "Headset" is not missing. See below:

Device 2C:41:A1:80:A1:C4 (public)
 Name: Christopher's Bose QC35 II
 Alias: Christopher's Bose QC35 II
 Class: 0x00240418
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
 UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
 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: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
 UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
 UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
 Modalias: bluetooth:v009Ep4020d0251

Max Ehrlich (queuecumber) wrote :

Also having this issue, the "headset" profile is not missing

 Name: OrigAudio_HP
 Alias: OrigAudio_HP
 Class: 0x00260404
 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)
 RSSI: -60

Mike Monteiro (m-monteiro) wrote :

Also experiencing this issue and the "headset" profile is not missing for me, either:

Device 28:11:A5:78:66:9A
 Name: Bose QC35 II
 Alias: Bose QC35 II
 Class: 0x240418
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
 UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
 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: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
 UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
 UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
 UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
 Modalias: bluetooth:v009Ep4020d0413

Amir Omidi (amir+ubuntu) wrote :

Experiencing this
Device 9C:64:8B:7D:C7:3D (public)
 Name: Amir’s AirPods
 Alias: Amir’s AirPods
 Class: 0x00240418
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Service Discovery Serve.. (00001000-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: Vendor specific (74ec2172-0bad-4d01-8f77-997b2be0722a)
 UUID: Vendor specific (9bd708d7-64c7-4e9f-9ded-f6b6c4551967)
 Modalias: bluetooth:v004Cp200Fd0A00
 RSSI: -54

dreasty (dreasty-d) wrote :

The same problem

ontroller DC:85:DE:56:6C:C4 (public)
 Name: dreasty
 Alias: dreasty
 Class: 0x003c010c
 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: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
 UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
 UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
 UUID: Vendor specific (185f3df4-3268-4e3f-9fca-d4d5059915bd)
 UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
 UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
 UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
 UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
 UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
 UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
 UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v1D6Bp0246d0530
 Discovering: yes

Card #3
 Name: bluez_card.0C_FE_5D_60_26_11
 Driver: module-bluez5-device.c
 Owner Module: 29
 Properties:
  device.description = "TicPods 2611"
  device.string = "0C:FE:5D:60:26:11"
  device.api = "bluez"
  device.class = "sound"
  device.bus = "bluetooth"
  device.form_factor = "headset"
  bluez.path = "/org/bluez/hci0/dev_0C_FE_5D_60_26_11"
  bluez.class = "0x2c0404"
  bluez.alias = "TicPods 2611"
  device.icon_name = "audio-headset-bluetooth"
  device.intended_roles = "phone"
 Profiles:
  a2dp_source: High Fidelity Capture (A2DP Source) (sinks: 0, sources: 1, priority: 20, available: no)
  a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: yes)
  headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: no)
  off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
 Active Profile: a2dp_sink
 Ports:
  headset-output: Headset (priority: 0, latency offset: 0 usec)
   Part of profile(s): a2dp_sink, headset_head_unit
  headset-input: Headset (priority: 0, latency offset: 0 usec, not available)
   Part of profile(s): a2dp_source, headset_head_unit

Aleksandar (voja-vocni) wrote :

The same problem here, "Headset" is not missing.
Device 5C:FB:7C:86:8A:D9 (public)
 Name: JBL TUNE110BT
 Alias: JBL TUNE110BT
 Class: 0x00240404
 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: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

Using blueman, I can somehow force the headset profile. Unfortunately, I can only hear hissing noise in this case for both input and output. I think there is definitely something wrong in how pavucontrol handles this.
Also, my headphones were tested with an android phone and were working.

Simon Art (simonart) wrote :

I get the following for the Logitech H800 wireless headset (without "headset"):

Device 00:0D:44:D2:71:61 (public)
 Name: H800 Logitech Headset
 Alias: H800 Logitech Headset
 Class: 0x00240404
 Icon: audio-card
 Paired: yes
 Trusted: yes
 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: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

Same here on Linux CH-W-7269416 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Device 04:5D:4B:99:46:9C (public)
        Name: WH-1000XM2
        Alias: WH-1000XM2
        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: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d)
        UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba)
        UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
        Modalias: usb:v054Cp0C67d0105

Richard Smith (smithbone) wrote :

Same with a Bose Noise Canceling 700. Have the profile but nothing shows up on the list of capture devices.

Device 60:AB:D2:02:00:B4 (public)
        Name: Bose NC 700 HP
        Alias: Bose NC 700 HP
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
        UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
        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: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
        UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
        UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
        Modalias: bluetooth:v009Ep4024d1211
        ManufacturerData Key: 0x0f03
        ManufacturerData Value:
  c2 12 8c c8 86 2f 04 73 ...../.s
        ServiceData Key: 0000fe2c-0000-1000-8000-00805f9b34fb
        ServiceData Value:
  84 c3 1b ...

rick beldin (rick-beldin) wrote :

Same problem on 18.04 with Sony headset:

s
[WI-1000X]# info 38:18:4C:04:C7:2A
Device 38:18:4C:04:C7:2A (public)
        Name: WI-1000X
        Alias: WI-1000X
        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: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d)
        UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
        UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
        UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba)
        UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
        UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
        Modalias: usb:v054Cp0C63d0411

Device 00:22:37:14:4E:E8 (public)
 Name: Philips SHB9100
 Alias: Philips SHB9100
 Class: 0x00240404
 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)

A. H (ubunteer) wrote :

Device 00:16:94:32:A8:A7 (public)
 Name: HD 4.40BT
 Alias: HD 4.40BT
 Class: 0x00240404
 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: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: bluetooth:v0A12p0001d0000

Same issue, random noise with some small pulses here and there when in Headset mode, works fine in A2DP. Not a great look when trying to convince your company to pull the trigger on Linux :( now with the must-have of teleconferencing.

Patola (patola) wrote :
Download full text (9.8 KiB)

Same problem with my OneAudio headset. I try to enable HSP/FSP profile and it says unavailable. It worked OK in 18.04 then I upgraded to 20.04 and it stopped working.

4 card(s) available.
    index: 0
        name: <alsa_card.pci-0000_07_00.1>
        driver: <module-alsa-card.c>
        owner module: 7
        properties:
                alsa.card = "0"
                alsa.card_name = "HDA NVidia"
                alsa.long_card_name = "HDA NVidia at 0xf6080000 irq 65"
                alsa.driver_name = "snd_hda_intel"
                device.bus_path = "pci-0000:07:00.1"
                sysfs.path = "/devices/pci0000:00/0000:00:03.1/0000:07:00.1/sound/card0"
                device.bus = "pci"
                device.vendor.id = "10de"
                device.vendor.name = "NVIDIA Corporation"
                device.product.id = "10f8"
                device.product.name = "TU104 HD Audio Controller"
                device.string = "0"
                device.description = "TU104 HD Audio Controller"
                module-udev-detect.discovered = "1"
                device.icon_name = "audio-card-pci"
        profiles:
                output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown)
                output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no)
                output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no)
                output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no)
                output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no)
                output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no)
                output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no)
                output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no)
                output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no)
                output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no)
                off: Off (priority 0, available: unknown)
        active profile: <output:hdmi-stereo>
        sinks:
                alsa_output.pci-0000_07_00.1.hdmi-stereo/#5: TU104 HD Audio Controller Digital Stereo (HDMI)
        sources:
                alsa_output.pci-0000_07_00.1.hdmi-stereo.monitor/#7: Monitor of TU104 HD Audio Controller Digital Stereo (HDMI)
        ports:
                hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes)
                        properties:
                                device.icon_name = "video-display"
                                device.product.name = "34GL750
     "
                hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no)
                        properties:
                                device.icon_name = "video-display"
                hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, avail...

Brian Frantz (blfrantz) wrote :

Also having this problem in Ubuntu 20.04 with the Anker Soundcore Life 2 headset:
Device 88:D0:39:39:83:07 (public)
 Name: Soundcore Life 2
 Alias: Soundcore Life 2
 Class: 0x00240404
 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)

Audio profile set to Headset (HSP/HFP). Headset connection LED blinks (error). Works in A2DP mode (without microphone). These headphones work fine as a headset in Windows 10. Seriously frustrating, trying to switch to Ubuntu for work and something this basic really should be fixed by now.

Rodrigo Pádua (rodrigoclp) wrote :

Same problem, I try to enable HSP/FSP profile and it says unavailable. It worked fine in the 18.04. I upgraded to 20.04 and it stopped working.

name: <bluez_card.00_00_AB_CD_7B_D5>
 driver: <module-bluez5-device.c>
 owner module: 26
 properties:
  device.description = "BW-FYE6"
  device.string = "00:00:AB:CD:7B:D5"
  device.api = "bluez"
  device.class = "sound"
  device.bus = "bluetooth"
  device.form_factor = "headset"
  bluez.path = "/org/bluez/hci0/dev_00_00_AB_CD_7B_D5"
  bluez.class = "0x240404"
  bluez.alias = "BW-FYE6"
  device.icon_name = "audio-headset-bluetooth"
  device.intended_roles = "phone"
 profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no)
  off: Off (priority 0, available: yes)
 active profile: <a2dp_sink>
 sinks:
  bluez_sink.00_00_AB_CD_7B_D5.a2dp_sink/#1: BW-FYE6
 sources:
  bluez_sink.00_00_AB_CD_7B_D5.a2dp_sink.monitor/#2: Monitor of BW-FYE6
 ports:
  headset-output: Headset (priority 0, latency offset 0 usec, available: unknown)
   properties:

  headset-input: Headset (priority 0, latency offset 0 usec, available: no)
   properties:

Same problem here. A2DP works fine, but HSP/HFP is marked as unavailable.

$ uname -r
4.19.66-gentoo

$ pulseaudio --version
pulseaudio 13.0

Device 5C:FB:7C:E2:7A:5B (public)
 Name: JBL TUNE500BT
 Alias: JBL TUNE500BT
 Class: 0x00240404
 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: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

Ion Ruiz (hashelandia) wrote :

Same error with 16.04 and JBL headset, I tried 20.04 in livecd and same problem.

Name: JBL LIVE400BT
Alias: JBL LIVE400BT
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: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
 UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7)

Same issue here. Ubuntu 18.04, kernel 5.3.0-53-generic, pulseaudio 11.1, sound card: Intel Sunrise Point-LP HD Audio (HDA Intel PCH) and chipset: Conexant Generic.

Name: H1 Pro
Alias: H1 Pro
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
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)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

Burak Kakillioglu (bkakilli) wrote :

Same issue here (without headset line). Cannot switch to HSP/HFP mode. I have a dual boot Windows 10, the headset (audio output and microphone) works fine there.

Ubuntu 18.04.4, kernel 4.15.0-106-generic, pulseaudio 11.1
Card: HDA Intel PCH HD (Dell 200 Series PCH HD) Chip: Realtek ALC3861

Device 98:52:3D:73:D3:5B (public)
 Name: Soundcore Liberty Air 2
 Alias: Soundcore Liberty Air 2
 Class: 0x00240404
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
 UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
 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: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
 UUID: Vendor specific (0000eb03-d102-11e1-9b23-00025b00a5a5)
 RSSI: -59

Apurva Shukla (naezeroth) wrote :

Same issue here - I can't switch to HSP/HFP mode on Ubuntu 20.04

uname -r
5.4.0-39-generic

pulseaudio --version
pulseaudio 13.99.1

Device 38:18:4C:94:DE:B2 (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: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d)
 UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
 UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
 UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba)
 UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b)
 UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
 Modalias: usb:v054Cp0CD3d0422
 ManufacturerData Key: 0x012d
 ManufacturerData Value:
  04 00 01 31 00 01 b3 ee e4 3f 00 60 d0 00 00 00 ...1.....?.`....
  00 00 00 ...

#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal

#uname -r
5.4.0-37-generic

#pulseaudio --version
pulseaudio 13.99.1

[B4:86:55:E1:8B:07]
  Name: FlyPods Lite
  Alias: FlyPods Lite [rw]
  Address: B4:86:55:E1:8B:07
  Icon: audio-card
  Class: 0x2c0404
  Paired: 1
  Trusted: 1 [rw]
  Blocked: 0 [rw]
  Connected: 1
  UUIDs: [AudioSource, AudioSink, AVRemoteControl, Handsfree, PnPInformation]

 bt-device -s B4:86:55:E1:8B:07
Discovering services...

[RECORD:0x10000]
SrvClassIDList: "AudioSink"
ProtocolDescList:
    "L2CAP", 0x19
    "AVDTP", 0x103
BTProfileDescList:
    "AdvAudio", 0x103
SrvName: "Advanced Audio"
ProviderName: "MtView"

[RECORD:0x10002]
SrvClassIDList: "Handsfree", "Audio"
ProtocolDescList:
    "L2CAP"
    "RFCOMM", Channel: 1
BTProfileDescList:
    "Handsfree", 0x107
SrvName: "Hands-Free unit "

[RECORD:0x10001]
SrvClassIDList: "AVRemote", "VideoConf"
ProtocolDescList:
    "L2CAP", 0x17
    "AVCTP", 0x102
BTProfileDescList:
    "AVRemote", 0x105
SrvName: "MVIEW "
ProviderName: "MVIEW "

[RECORD:0x10003]
SrvClassIDList: "AudioSource"
ProtocolDescList:
    "L2CAP", 0x19
    "AVDTP", 0x103
BTProfileDescList:
    "AdvAudio", 0x103
SrvName: "Advanced Audio"
ProviderName: "MtView"

Filip (filipcynarski) wrote :

Any update on that issue? It can be a workaround using ofono but it is crappy ofono is not included in focal as well. And setting ofono up takes a few minutes and it is a hell two switch profiles, restart headset and do a lot of stuff which can be automated. It would be great to have it as an OS part. I use AirPods and only sound works out of the box but for the mic I have to struggle with ofono and I'm not glad to use this workaround.

Daniel van Vugt (vanvugt) wrote :

This bug is closed as a duplicate of bug 1576559 so please put all discussion in that other bug instead... Unless it's about the correctness of the duplicate status.

Sanmati Jain (jainsanmati) wrote :

Same problem here. A2DP works fine, but HSP/HFP is marked as unavailable.

<pre>Card #2
 Name: bluez_card.00_01_00_00_02_C0
 Driver: module-bluez5-device.c
 Owner Module: 24
 Properties:
  device.description = &quot;realme Buds Air&quot;
  device.string = &quot;00:01:00:00:02:C0&quot;
  device.api = &quot;bluez&quot;
  device.class = &quot;sound&quot;
  device.bus = &quot;bluetooth&quot;
  device.form_factor = &quot;headset&quot;
  bluez.path = &quot;/org/bluez/hci0/dev_00_01_00_00_02_C0&quot;
  bluez.class = &quot;0x240404&quot;
  bluez.alias = &quot;realme Buds Air&quot;
  device.icon_name = &quot;audio-headset-bluetooth&quot;
  device.intended_roles = &quot;phone&quot;
 Profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: yes)
  headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: no)
  off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
 Active Profile: a2dp_sink
 Ports:
  headset-output: Headset (priority: 0, latency offset: -10000 usec)
   Part of profile(s): a2dp_sink, headset_head_unit
  headset-input: Headset (priority: 0, latency offset: 0 usec, not available)
   Part of profile(s): headset_head_unit
</pre>

Arnaud F (ead2019) wrote :

Same issue, only AD2P:

Device 00:12:40:13:BA:D0 (public)
 Name: SOUNDPEATS Truengine 3 SE
 Alias: SOUNDPEATS Truengine 3 SE
 Class: 0x00240404
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
 UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
 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: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
 UUID: Vendor specific (0000eb03-d102-11e1-9b23-00025b00a5a5)
 ManufacturerData Key: 0x000a
 ManufacturerData Value:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers