I have Sony WH-1000XM2 Bluetooth 4.1 headphones (with profiles A2DP, AVRCP, HFP, and HSP) which work with Ubuntu .

However, they constantly connect to the PC in the headset mode with subpar mono audio. For proper high def stereo, I must:

  1. Turn on headphones, wait for them to pair (auto connects to headset mode)
  2. Disconnect the headphones using Blueman-manager
  3. Reconnect to the headphones specifying the High Fidelity Playback Audio Profile.

When I try to change profiles while connected I get the Failed to change profile to a2dp_sink. Funnily enough it can change from a2dp to hsp/hsf just fine...

Is there a way to configure this Bluetooth device to auto connect to high fidelity playback?

Multiple searches for a solution on the web have found nothing useful.

  • 1
    This answer helped me to have the headset be recognized and detected automatically as new default sound device once it connected via bluetooth. Maybe it might improve your situation too, even if it doesn't look too related on first sight?
    – Byte Commander
    May 7, 2019 at 12:50
  • You may find askubuntu.com/questions/806215/… helpful.
    – K7AAY
    May 7, 2019 at 23:00
  • I switched my 22.04 installation from pulseaudio to pipewire with this installation instruction and me headset now correctly switched between HFP and A2DP depending on if an application uses the microphone.
    – Freddy
    Feb 23, 2023 at 9:59

6 Answers 6


I had the exact same problem. My Sony WH-1000XM2 used to work only when initially paired with Ubuntu 18.04. After a reboot or headphones off/on they used to connect automatically but the sound was awful. I had to remove the Bluetooth device and pair it again. I tried all of the solutions on the Internet which claim that configurations in:




should do the trick. Well, they don't. The headphones keep working with the 'HSP/HFP' profile and the 'A2DP Sink' can not be set until the phones are repaired.

The more convenient way is to use the command line instead of physically pressing buttons and reconnecting through the UI. So this answer helped me achieve this. However, this looks like a lot of commands to me, so I scripted them in this gist. It should work out of the box.

Whenever the phones get automatically reconnected (after the initial pairing) and they start using 'HSP/HFP' just execute this script and the profile will be set to 'A2DP Sink'. You may have to tweak the sleep intervals according to your headphones.

I hope this is getting fixed in upcoming releases of PulseAudio and Ubuntu.

  • 3
    This is spot on, thanks for your gist! It worked for my Sony WH-CH700N headphones first time.
    – Al Bennett
    Nov 19, 2019 at 18:53
  • 2
    I confirm gist works with JBL.
    – stiv
    Feb 5, 2020 at 22:16
  • This is not working with Sony WH1000XM4. They are still going to HSP after running the gist. Apr 19, 2021 at 6:45

I had a similar problem with Ubuntu 20.04

I was able to select the A2DP profile for my headphones (Bose QC 700). I was able to select A2DP, but every time the headphones disconnected, it would default to the HSP/HFP profile.

Following the solution mentioned here and here, A2DP is now selected automatically at every connection:

  • Add to /etc/pulse/default.pa to automatically switch pulseaudio sink to Bluez:
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
load-module module-switch-on-connect  # Add this
  • Edit /etc/bluetooth/main.conf to auto select A2DP profile (instead of HSP/HFP):
Disable=Headset # Add this
  • Apply changes (you may as well need to turn your bluetooth headphones off, then back on):
pulseaudio -k                       # Kills pulseaudio
pulseaudio --start                  # Starts pulseaudio
sudo systemctl restart bluetooth
  • This works! - Excellent answer! Linking to solutions AND adding the solution to the answer... :)
    – lobner
    Jan 21, 2022 at 9:35
  • That works like a charm. Jul 22, 2022 at 13:11
  • This works for me only until I restart the OS, afterwards the head-phone profile is default again. If I manually restart pulseaudio and bluetooth then the bug goes away. Would be nice to not have to do this manual step
    – wi2ard
    Aug 2, 2022 at 10:44

I had a very similar problem. As egelev states, many of the solutions do not really solve anything...

However, for future reference, I found a solution involving changing /etc/pulse/default.pa which worked perfectly for me, the full solution can be found here. In short, doing the following automatically changes the profile to A2DP and disables the headphone function upon connecting to bluetooth headphones with mics:

# In /etc/pulse/default.pa do the following:
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
load-module module-switch-on-connect # Add this line

# Create or change /etc/bluetooth/audio.conf with the following lines:

# Restart pulseaudio
pulseaudio -k

I wound up writing a custom script to do this. You're going to have to adjust the Bluetooth address in order to make it work correctly for your own headset:



if [ -e ${LOCKFILE} ] && kill -0 `cat ${LOCKFILE}`; then
    echo "already running"

# make sure the lockfile is removed when we exit and then claim it
trap "rm -f ${LOCKFILE}; exit" INT TERM EXIT
echo $$ > ${LOCKFILE}

/usr/bin/gdbus monitor --system --dest org.bluez |
    while read -r X; 
        if echo $X | grep  "${DEV_ID}.*'Connected': <true>"
            echo -n "BT headset detected, configuring "
            pacmd  set-card-profile bluez_card.${DEV_ID} a2dp_sink

I run this script from autostart, and it's been working for me.


I had a similar problem and I forgot that I installed pipewire which in combination with the pulseaudio-module-bluetooth package conflicts with the a2dp (advanced audio distribution profile). Hence, check if pipewire is running

ps -e | grep pipewire

If it is running either uninstall pipewire and keep the pulseaudio-module-bluetooth module or you can give pipewire a chance, since it has advanced options and performance.

  • Keeping pipewire

    First uninstall the following module at the command line with

    sudo apt remove pulseaudio-module-bluetooth

    and install all pipewire packages with

     sudo apt-get install pipewire-*

    additional add the following code at the end of your /etc/pulse/default.pa configuration file:

    ### Added to make headset work for pipewire
    ### https://wiki.debian.org/BluetoothUser/a2dp
    load-module module-bluez5-device 
    load-module module-bluez5-discover

    On my plasma desktop all codecs are now available:

    enter image description here

  • Keeping default pulseaudio-module

    In case you use the default pulseaudio setup from ubuntu simple uninstall or disable pipwire e.g.:

    sudo apt-get remove pipewire*

More information about the a2dp problem can be found on BluetoothUser/a2dp - Debian Wiki.

BTW: My bluetooth hardware is implemented in the Intel Corporation Wi-Fi 6 AX201 chip which made it necessary to download (as on March 2022) the latest firmware driver from the linux kernel homepage. The firmware I am using is:

> ls  -1 /lib/firmware/iwlwifi-QuZ-a0-hr-b0-*

  • +1 Omg, I can switch right in the audio applet instead of opening the settings all the time (picture says a thousand words). That's going to lower my response time by half a minute when people try to call me on Teams. I haven't tried pipewire, but pulseaudio works fine. Sep 26, 2022 at 16:15
  • Pipewire is the default audio set on Fedora and many other distributions. Maybe ubuntu will also switch as others have done.
    – abu_bua
    Sep 27, 2022 at 0:07

Add something like that to /etc/pulse/default.pa

.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover

.ifexists module-switch-on-connect.so
load-module module-switch-on-connect

.ifexists module-bluez5-device.so
load-module module-bluez5-device

.ifexists module-bluez5-discover.so
load-module module-bluez5-discover

Restart bluetooth and pulseaudio services.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .