Refused to switch profile to headset_head_unit: Not connected

Bug #1576559 reported by Alok Parlikar on 2016-04-29
510
This bug affects 117 people
Affects Status Importance Assigned to Milestone
PulseAudio
Unknown
Unknown
pulseaudio (Ubuntu)
High
Unassigned

Bug Description

I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone.

The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message:

W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected

I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

pulseaudio:
  Installed: 1:8.0-0ubuntu3

bluez:
  Installed: 5.37-0ubuntu5

Launchpad Janitor (janitor) wrote :

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

Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Bernie Bernstein (bernie9998) wrote :
Download full text (3.2 KiB)

I'm getting the same issue with my logitech H800 headset.

Here's a more verbose pulseaudio log of the device connecting and attempting to switch profiles:

I: [pulseaudio] module-card-restore.c: Restored profile 'a2dp_sink' for card bluez_card.88_C6_26_31_DF_F0.
I: [pulseaudio] module-card-restore.c: Restoring port latency offsets for card bluez_card.88_C6_26_31_DF_F0.
I: [pulseaudio] card.c: Created 3 "bluez_card.88_C6_26_31_DF_F0"
I: [pulseaudio] module-bluez5-device.c: Transport /org/bluez/hci0/dev_88_C6_26_31_DF_F0/fd2 acquired: fd 28
I: [pulseaudio] module-bluez5-device.c: SBC parameters: allocation=0, subbands=1, blocks=3, bitpool=53
I: [pulseaudio] sink.c: Created sink 1 "bluez_sink.88_C6_26_31_DF_F0" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right
I: [pulseaudio] sink.c: bluetooth.protocol = "a2dp_sink"
I: [pulseaudio] sink.c: device.description = "H800 Logitech Headset"
I: [pulseaudio] sink.c: device.string = "88:C6:26:31:DF:F0"
I: [pulseaudio] sink.c: device.api = "bluez"
I: [pulseaudio] sink.c: device.class = "sound"
I: [pulseaudio] sink.c: device.bus = "bluetooth"
I: [pulseaudio] sink.c: device.form_factor = "headset"
I: [pulseaudio] sink.c: bluez.path = "/org/bluez/hci0/dev_88_C6_26_31_DF_F0"
I: [pulseaudio] sink.c: bluez.class = "0x240404"
I: [pulseaudio] sink.c: bluez.alias = "H800 Logitech Headset"
I: [pulseaudio] sink.c: device.icon_name = "audio-headset-bluetooth"
I: [pulseaudio] sink.c: device.intended_roles = "phone"
I: [pulseaudio] source.c: Created source 2 "bluez_sink.88_C6_26_31_DF_F0.monitor" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right
I: [pulseaudio] source.c: device.description = "Monitor of H800 Logitech Headset"
I: [pulseaudio] source.c: device.class = "monitor"
I: [pulseaudio] source.c: device.string = "88:C6:26:31:DF:F0"
I: [pulseaudio] source.c: device.api = "bluez"
I: [pulseaudio] source.c: device.bus = "bluetooth"
I: [pulseaudio] source.c: device.form_factor = "headset"
I: [pulseaudio] source.c: bluez.path = "/org/bluez/hci0/dev_88_C6_26_31_DF_F0"
I: [pulseaudio] source.c: bluez.class = "0x240404"
I: [pulseaudio] source.c: bluez.alias = "H800 Logitech Headset"
I: [pulseaudio] source.c: device.icon_name = "audio-headset-bluetooth"
I: [pulseaudio] source.c: device.intended_roles = "phone"
I: [bluetooth] core-util.c: Successfully enabled SCHED_RR scheduling for thread, with priority 5.
I: [bluetooth] module-bluez5-device.c: Transport /org/bluez/hci0/dev_88_C6_26_31_DF_F0/fd2 resuming
I: [pulseaudio] module.c: Loaded "module-bluez5-device" (index: #22; argument: "path=/org/bluez/hci0/dev_88_C6_26_31_DF_F0").
I: [pulseaudio] module-card-restore.c: Card bluez_card.88_C6_26_31_DF_F0 profile a2dp_sink became available, activating.
I: [pulseaudio] module-suspend-on-idle.c: Sink bluez_sink.88_C6_26_31_DF_F0 idle for too long, suspending ...
I: [bluetooth] bluez5-util.c: Transport /org/bluez/hci0/dev_88_C6_26_31_DF_F0/fd2 released
I: [pulseaudio] module-card-restore.c: Card bluez_card.88_C6_26_31_DF_F0 profile a2dp_sink became available, activating.
W: [pulseaudio] module-b...

Read more...

tags: added: xenial

More than a year and this bug is not yet fixed?

Is it a huge problem to solve?

Can I help with some log files or something like that?

J. Scott Farrow (jscott-farrow) wrote :

I gave up and spent $80 on new headphones that seem to work. GhostTek SoDrop2s, if anyone wants to know. Working for me on 17.04 Zesty.

varacanero (varacanero) wrote :

I also spend hours on this issue trying to get a Logitech H800 headset working and finally gave up.
It would be at least nice to know what's the problem (pulseaudio ? bluez ? Headset ?) and if it's on the roadmap to fix it.

varacanero (varacanero) wrote :

Also, how to find out which Headsets work and which not, before spending the money and finding out they don't.

varacanero (varacanero) wrote :

Btw, I experience this issue with Ubuntu 17.10. I tried upgrading pulseaudio to the bionic version but the problem persists.

JR (juergen-richtsfeld) wrote :

I have the same issue on Kubuntu 18.04 (upgraded) with my EP650 headset. This worked a few releases ago. Sound with A2DP works well.

nasatome (nasatome) wrote :

Same Issue in Ubuntu 18.10
My Bluedio F2 It works well as an A2DP sync, but can't use it as a headset with microphone.

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1734960/comments/9

nasatome (nasatome) wrote :

I add this extra information in case it works:

I have some "Bluedio F2" brand headphones that do not activate the microphone, however, my Philips SHB4000 hearing aids detect them without any problem (the input).
Where in Windows and Android the Bluedio & Philips Microphone works for me without problems.

Ubuntu 18.10
nasatome at nasatome-pc in ~
$ uname -r
4.18.0-10-generic

nasatome at nasatome-pc in ~
$ bluetoothctl
Agent registered
[Bluedio F]# devices
Device 18:07:21:27:08:11 Bluedio F
Device 00:1E:7C:37:EF:22 Philips SHB4000
[Bluedio F]# info 18:07:21:27:08:11
Device 18:07:21:27:08:11 (public)
 Name: Bluedio F
 Alias: Bluedio F
 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: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
[Bluedio F]# info 00:1E:7C:37:EF:22
Device 00:1E:7C:37:EF:22 (public)
 Name: Philips SHB4000
 Alias: Philips SHB4000
 Class: 0x00240404
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: no
 LegacyPairing: no
 UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
 UUID: Audio Sink (0000110b-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:v0039p13A4d0115
 ManufacturerData Key: 0x5349
 ManufacturerData Value:
  53 43 SC
[Bluedio F]#

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625

Kendon Bell (kendonb) wrote :

I am also seeing this problem:

```
[Jabra MOVE v2.5.0]# info 74:5C:4B:2A:E3:BE
Device 74:5C:4B:2A:E3:BE (public)
 Name: Jabra MOVE v2.5.0
 Alias: Jabra MOVE v2.5.0
 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)
[Jabra MOVE v2.5.0]#
```

Luis Perez (lpb89) wrote :

Hi:

I'm also impacted by this bug.

[HD 4.50BTNC]# info
Device 00:16:94:32:40:CD (public)
 Name: HD 4.50BTNC
 Alias: HD 4.50BTNC
 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)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: bluetooth:v0A12p0001d0000

When i select HSP/HFP as profile to use headset microphone, device restarts and switches back again to A2DP profile.

There's any news about this bug?
Has anyone tried to apply any workarround?

Tom Mercelis (tom-mercelis) wrote :

Hi,

I seem to have same problem with bluetooth headset Plantronics Backbeat pro2: A2DP works fine, media keys work. But when switching to HSF/HFP, no playback and no audio from mic.
Headset seems to switch the mode (something in the Noice cancellation audibly changes) when switching between A2DP and HSP/HFP profile; on occasions the headset "reboots" when changing mode as mentioned in the previous comment.

In https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/comments/3 it was suggested this could be due to missing Headset profile, but on this device both Headset and Handsfree profile are available.

Device E4:22:A5:XX:XX:XX (public)
 Name: PLT BB PRO 2
 Alias: PLT BB PRO 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: 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: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: bluetooth:v0055p0113d0110

Daniel van Vugt (vanvugt) wrote :

Can someone experiencing this bug please report it to the PulseAudio developers?

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new

and then tell us the new bug ID.

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

Daniel van Vugt (vanvugt) wrote :

Can someone experiencing this bug please report it to the PulseAudio developers?

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new

and then tell us the new bug ID.

Net User (onetuser) wrote :

Have the same issue in Ubuntu 18.04.2 LTS.
In pavucontrol or in blueman-applet:
If select A2DP sound works;
If select HSP/HFP sound/mic do not work.

bluetoothctl output:
        Name: Jabra Elite 65t
        Alias: Jabra Elite 65t
        Class: 0x00240404
        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: 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)
        Modalias: bluetooth:v0067p247Ed020E

Aleksandar (voja-vocni) wrote :

The same problem here, "Headset" is not missing.
I'm using Ubuntu 18.04.

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.

Daniel van Vugt (vanvugt) wrote :

Please also answer comment #16/#14.

tags: added: bionic
Jerry Kao (jerry.kao) wrote :

I have similar issue with 19.04. Input/ouput with profile HSP/HFP is very noisy.

Aaron Kogan (aaron-kogan) wrote :

I was read official pulseaudio gitlab bugs. Seems like bluetooth module problem. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/#index7h2
They recommend use separate usb bluetooth.

Sebastien Bacher (seb128) wrote :
Changed in pulseaudio (Ubuntu):
importance: Undecided → High

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)

Checked it on Arch Linux with Bluez 5.52, and got it working

A. H (ubunteer) wrote :

Mistakenly posted under a duplicate, issue is still here on Ubuntu 18 with a Sennheiser headset. Issue is bound to pop up more now with everyone remoting under lockdowns.

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

tags: added: focal

Exact same problem with an Anker Soundcore Q10

Carmen (camyavra) wrote :

I have the same issue with Anker Soundcore Life p2, the microphone doesnt work, as i can't connect them in HSP/HFP mode. I get the following error:
 [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected
I use Ubuntu 18.04 and run out of ideas on what to do to get over that....

Same here, cannot switch profile to HSP/HFP for Soundcore Life P2 on an ThinkPad T430s:

Device E8:07:BF:9B:23:D2 (public)
Name: Soundcore Life P2
Alias: Soundcore Life P2
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)

Some fix would be very much appreciated, I am available to help if I can.

otheos (ubuntu-otheos) wrote :

This is not a bug, but lack of support for headsets that only have the HFP (Handsfree) profile and no HSP (Headset) profile. Many current headsets only support HFP, and these won't work since pulseway doesn't support HFP only.

I find this ridiculous since there are a number of projects on git that have patched versions of pusleaudio to support HFP only headsets, so I wonder why this is not merging to the mainline of pulseaudio.

With everyone on their headsets doing teleconferencing during the lockdown, this limitation of pulseway has been exemplified.

Please have a look at it.

Daniel van Vugt (vanvugt) wrote :

Can someone experiencing this bug please report it to the PulseAudio developers?

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new

and then tell us the new bug ID.

It has been reported some time ago already, e.g. as Bug 84 or 742

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/84
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/742

There are even related PRs, but nobody at pulseaudio seems to really care about them, e.g.

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/94
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/288 (WIP though and following a new, rather unaligned approach)

Ryan Moore (h0h0h0b0) wrote :

I"ve had this problem on a clean install of 20.04 on a new laptop, with two headsets that support both profiles.

```
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)
```
Name: OnePlus Bullets Wireless 2
Alias: OnePlus Bullets Wireless 2
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
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: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v000ApFFFFdFFFF
```

Toni (scorpio92) wrote :

Year 2020 and we still looking for a solution. Bug confirmed with Canyon and JBL headphones 2 days ago by me.

kilroy (kilroy42) wrote :

Fresh install of Ubuntu 20.04 with a TT BH060 (TaoTronics):

Device E8:AB:FA:*:*:* (public)
        Name: TAOTRONICS SoundSurge 60
        Alias: TAOTRONICS SoundSurge 60
        Class: 0x00240418
        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)
        UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v000ApFFFFdFFFF

Also, kernel messages (hundreds):
[149342.549626] Bluetooth: hci0: SCO packet for unknown connection handle 0
[149342.549628] Bluetooth: hci0: SCO packet for unknown connection handle 12289

Switching to HSP/HFP just deactivates it completely. Only A2DP works as expected.

A M (amlabs) wrote :

(I'm not using Ubuntu for my desktop but I'have had the same problem. I'm running Pulseaudio 13 built with enable_bluez5_native_headset and Bluez 5.54)
Solved it by adding headset=native forthe module module-bluetooth-discover in default.pa :
 load-module module-bluetooth-discover headset=native
in ~/.pulse/default.pa (or /etc/pulse/default.pa)
then restarting pulseaudio with pulseaudio -k
Since Pulseaudio 11.0 has ofono support, "headset=auto" option enabled by default,

pactl list shows that both profiles with available: yes

Generally when using VoIP application automatically switch bluetooth profile to HSP works , but when not or when switch back to A2DP need to be done annually (for me, Blueman does the job with a few clicks).

Sound with HSP profile isn't very good and HFP doesn't seems to work as I haven't setup phonesimp (ref https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/ )

Rodrigo Pádua (rodrigoclp) wrote :

Same problem for me!
Ubuntu 20.04, Blitzwolf FYE6

Marcio (marcio-munhoz) wrote :

Same problem.
Ubuntu 20.04 LTS, JBL TUNE 120TWS (A2DP 1.3 AVRCP 1.5 HFP 1.6)

Michael Heller (chusti) wrote :

same issue here with a freeVoice headset.
as soon as I switch to hsp/hfp mode audio stops working.
funny enough the beeps while changing sound volume are hearable

Michael Heller (chusti) wrote :

I fixed the problem for my laptop.
it looks like its a configuration issue in /etc/pulse/default.pa file.
I simply made a diff with a previous ubuntu version aka 19.10 and adjust the config (I copied the config file ) and restart pulseaudio with "systemctl --user restart pulseaudio".
and my hsp/hfp profile now works and I can use the microphone as well.

Sebastien Bacher (seb128) wrote :

@Michael, could you tell us what option you changed back to fix the issue exactly?

@Sebastien I installed ubuntu 19.10 in a VM, compared the file Michael refers to with the one in my system (20.04) and only the following lines are removed in 20.04:

### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams

According to pulseaudio's release notes this is because this functionality is moved to the core and no longer needed.

Sebastien Bacher (seb128) wrote :

Thanks, but despite the 'no longer needed' part is still making a difference for you?

Sanmati Jain (jainsanmati) wrote :

Same problem.
Ubuntu 20.04 LTS,"realme Buds Air".

Harsh Varia (hvaria) wrote :

Same problem confirmed it's an issue. Using Galaxy Buds+ and Beats X. Please help fix this. We are all working from home and need this feature.

Egons.Zile (egons-zile) wrote :

Same here Ununtu 20.04 with Anker Soundcore life Q10, what is worse it that ofono/phonesim can't be used properly, no stable version for Ubuntu 20.04 and no proper instructions to set it up...
Please help!!!

Brett D (brettface) wrote :

Same issue here with Aukey EP-N5 bluetooth earbuds on 20.04.1. This is a top-selling set of earbuds on Amazon so I thought they'd work.

The microphone doesn't appear at all in the list of input devices under system Sound Settings.

Attempting to change the profile within Blueman to HSP/HFP results in "Failed to change profile to headset_head_unit".

Maddening.

Rodrigo Pádua (rodrigoclp) wrote :

Hey Guys!

Any news about this bug?
Any alternative solution before the definitive fix?

All of my friends are complaining about the same issue. It seems that is affecting everybody.

Daniel van Vugt (vanvugt) wrote :

I suggest you ask the PulseAudio experts at:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/84

Timothy Clarke (tim-ub-lap) wrote :

For those approaching the issue from afresh it looks like HSP/HFP shares functionality with bluetooth modems rather than solely audio. As such there's a disagreement between pulseaudio who are only interested in the audio parts, ofono who deals with the modem parts and the bluetooth stack (bluez) who connect the to the hardware.

The issue came about as support was dropped (assuming someone else would pick it up) as pulse audio and bluez went to later versions. It hasn't been resolved because no one wants to ether deal with the other part, or have another abstraction layer to switch between modem and audio functionality

Same issue here with Sony WH-CH710N on a fresh install of Ubuntu 20.04.1 LTS kernel 5.4.0-42-generic

zwn (zwn) wrote :

Same problem with Edifier TWS200:

Device 5C:C6:E9:C4:29:2F (public)
 Name: EDIFIER TWS200 R
 Alias: EDIFIER TWS200 R
 Class: 0x00240404
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: no
 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)

Only Handsfree available, no Headset.

shizow (glukkon) wrote :

It seems this bug affects almost everyone who wants to use earbuds with Linux? How come this issue is still nox fixed after such a long time?

Marcio (marcio-munhoz) wrote :

The impression that I get is that will never be fixed

Daniel van Vugt (vanvugt) wrote :

PulseAudio developers probably don't monitor this bug. If you would like to comment to them then please use:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/84

Vlad V. (vlasebian) wrote :

Hi!

I had the same problem with JBL TUNE500BT Headphones on Ubuntu 20.04. I did a kernel update to 5.8.9-050809-generic version using ubuntu-mainline-kernel.sh script [1]. I also uninstalled ofono and ofono-phonesim which I installed earlier when trying to fix this problem and reverted any changes I did to the default.pa file. It seems to be working now, but audio quality is awful when using HSP/HFP, which is related to another bug [2]. I don't know if it's a good solution, but maybe it will help someone.

[1]: https://raw.githubusercontent.com/pimlie/ubuntu-mainline-kernel.sh/master/ubuntu-mainline-kernel.sh
[2]: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151

Marcio (marcio-munhoz) wrote :

I tried update kernel, but no success.
Probably because my headphone doesn't have the hsp profile, only the hfp 1.6.

Loyce LEICHNIG (macarun) wrote :

Hi !

I don't have the exact same problem given in the title.

I am on an Ubuntu 18.04 laptop for work and use BOSE QC 35 II headphones and more recently Sony WF-1000XM3s earbuds.

I can switch from one profile to another, A2DP Sink to HSP/HFP. However, with the A2DP profile I have stereo sound (good) but no microphone. With the HSP/HFP profile, I have mono sound (not good) with crackling but with the microphone working.

As soon as I choose my headphones/earphones in the inputs, it automatically switches the sound profile (output) of my device to HSP/HFP. If I select the A2DP profile again, it changes the microphone input to the laptop one or a usb dock (when I use one with microphone input), which is not practical if I want to take a few steps away from the laptop.

I read here and there that the A2DP was only mono-directional which explains the lack of support for the microphone.

I hope that in 2021 (it's dead for 2020), someone will find a new way to make Bluetooth devices work with a microphone on linux in stereo with good sound quality.
In my opinion, the HSP/HFP profile is no longer made for the years 2020+.

Daniel van Vugt (vanvugt) wrote :

That's probably more relevant to bug 1838151 than this one.

LI CHEN AARON (liaaron1) wrote :

Same version of ubuntu and same bluetooth earbuds work fine on different desktop but not on my laptop. Does this have something to do with model of the bluetooth as well?

Information collected from my laptop (not working)

[Jabra Elite 65t]# info 70:BF:92:22:3B:71
Device 70:BF:92:22:3B:71 (public)
 Name: Jabra Elite 65t
 Alias: Jabra Elite 65t
 Class: 0x00240404
 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: 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)
 Modalias: bluetooth:v0067p247Ed0222
 ManufacturerData Key: 0x0067
 ManufacturerData Value:
  03 07 01 4c 03 0b 7e 24 ...L..~$

shizow (glukkon) wrote :

are there any earbuds where the microphone works at least somehow with linux?

tags: added: a2dp
Daniel van Vugt (vanvugt) wrote :

Try also:

  load-module module-bluetooth-policy auto_switch=2

in /etc/pulse/default.pa as suggested in bug 508522.

Download full text (4.6 KiB)

Same issue here. As many others here, I need to use the mic at work's meetings and I needed to spent extra money on a wired headset because of this bug made my airpods useless for the task.

elementary OS 5.1.7 Hera, Built on Ubuntu 18.04.4 LTS.
Linux 4.15.0-135-generic.

$pactl list cards
Card #0
 Name: alsa_card.pci-0000_00_1b.0
 Driver: module-alsa-card.c
 Owner Module: 7
 Properties:
  alsa.card = "0"
  alsa.card_name = "HDA Intel"
  alsa.long_card_name = "HDA Intel at 0xf0000000 irq 26"
  alsa.driver_name = "snd_hda_intel"
  device.bus_path = "pci-0000:00:1b.0"
  sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
  device.bus = "pci"
  device.vendor.id = "8086"
  device.vendor.name = "Intel Corporation"
  device.product.id = "27d8"
  device.product.name = "NM10/ICH7 Family High Definition Audio Controller"
  device.form_factor = "internal"
  device.string = "0"
  device.description = "Built-in Audio"
  module-udev-detect.discovered = "1"
  device.icon_name = "audio-card-pci"
 Profiles:
  input:analog-stereo: Analog Stereo Input (sinks: 0, sources: 1, priority: 60, available: no)
  output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 0, priority: 6000, available: yes)
  output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (sinks: 1, sources: 1, priority: 6060, available: yes)
  output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, sources: 0, priority: 5500, available: yes)
  output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (sinks: 1, sources: 1, priority: 5560, available: yes)
  off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
 Active Profile: output:analog-stereo+input:analog-stereo
 Ports:
  analog-input-mic: Microphone (priority: 8700, latency offset: 0 usec, not available)
   Properties:
    device.icon_name = "audio-input-microphone"
   Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:iec958-stereo+input:analog-stereo
  analog-output-speaker: Speakers (priority: 10000, latency offset: 0 usec)
   Properties:
    device.icon_name = "audio-speakers"
   Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo
  analog-output-headphones: Headphones (priority: 9000, latency offset: 0 usec, not available)
   Properties:
    device.icon_name = "audio-headphones"
   Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo
  iec958-stereo-output: Digital Output (S/PDIF) (priority: 0, latency offset: 0 usec)
   Part of profile(s): output:iec958-stereo, output:iec958-stereo+input:analog-stereo

Card #7
 Name: bluez_card.AC_80_1C_01_34_B0
 Driver: module-bluez5-device.c
 Owner Module: 33
 Properties:
  device.description = "Baseus Encok W04 Pro"
  device.string = "AC:80:1C:01:34:B0"
  device.api = "bluez"
  device.class = "sound"
  device.bus = "bluetooth"
  device.form_factor = "headset"
  bluez.path = "/org/bluez/hci0/dev_AC_80_1C_01_34_B0"
  bluez.class = "0x240404"
  bluez.alias = "Baseus Encok W04 Pro"
  device.icon_name = "audio-headset-bluetooth"
  device.intended_roles = "phone"
 Profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sou...

Read more...

Rajitha Karunarathne (raaajit) wrote :

So this bug is here from around 2016 , still haven't yet solved

Rajitha Karunarathne (raaajit) wrote :

Ubnutu you need to consider on giving a Solid solution for Bluetooth headsets since that is a common use case for most.

Daniel van Vugt (vanvugt) wrote :

Please try the suggestion in comment #60.

Daniel van Vugt (vanvugt) wrote :

Upstream suggests this fix in progress is related:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/491

Changed in pulseaudio (Ubuntu):
status: Confirmed → In Progress
Arnaud F (ead2019) wrote :

Hi, 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:

TY :-)

Ryan Ruen (music-makes-it) wrote :

@Daniel van Vugt - Thank you for suggesting the change in post #60. It didn't work for me though.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.