← Back to team overview

kernel-packages team mailing list archive

[Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp


I had the same problem and for several months I have tried all possible
solutions I could find to no avail,... until today!

I found the solution in post #17 in the following
https://bbs.archlinux.org/viewtopic.php?pid=1526534#p1526534 (tnx

What I did:

# First copy the files I edited

    sudo cp /etc/bluetooth/audio.conf /etc/bluetooth/audio.conf_tmp
    sudo cp /etc/pulse/default.pa /etc/pulse/default.pa_tmp
    sudo cp /usr/bin/start-pulseaudio-x11 /usr/bin/start-pulseaudio-x11_tmp

#Edit /etc/bluetooth/audio.conf

    sudo nano /etc/bluetooth/audio.conf

This is in my audio.conf

    # Configuration file for the audio service
    # This section contains options which are not specific to any
    # particular interface
    # Switch to master role for incoming connections (defaults to true)

    # If we want to disable support for specific services
    # Defaults to supporting all implemented services

    # SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
    # Defaults to HCI

    # Automatically connect both A2DP and HFP/HSP profiles for incoming
    # connections. Some headsets that support both profiles will only connect the
    # other one automatically so the default setting of true is usually a good
    # idea.

    # Headset interface specific options (i.e. options which affect how the audio
    # service interacts with remote headset devices)

    # Set to true to support HFP, false means only HSP is supported
    # Defaults to true

    # Maximum number of connected HSP/HFP devices per adapter. Defaults to 1

    # Set to true to enable use of fast connectable mode (faster page scanning)
    # for HFP when incoming call starts. Default settings are restored after
    # call is answered or rejected. Page scan interval is much shorter and page
    # scan type changed to interlaced. Such allows faster connection initiated
    # by a headset.

    # Just an example of potential config options for the other interfaces

#Edit /etc/pulse/default.pa

    sudo nano /etc/pulse/default.pa

comment out (with an # at the beginning of the line) the following line

    #load-module module-bluetooth-discover

#now edit /usr/bin/start-pulseaudio-x11

    sudo nano /usr/bin/start-pulseaudio-x11

and after the lines

    if [ x”$SESSION_MANAGER” != x ] ; then
            /usr/bin/pactl load-module module-x11-xsmp “display=$DISPLAY session_manager=$SESSION_MANAGER” > /dev/null

add the following

    /usr/bin/pactl load-module module-bluetooth-discover

#Restarted and I was finally able tot switch to A2DP

Hope it works for you too.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
Status in pulseaudio package in Ubuntu:
Status in bluez source package in Vivid:
Status in pulseaudio source package in Vivid:

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve the problem for me:

To manage notifications about this bug go to: