After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 748654 - Bluetooth headset profile not changable
Bluetooth headset profile not changable
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Sound
git master
Other Linux
: Normal normal
: ---
Assigned To: Control center sound maintainer(s)
Control-Center Maintainers
triaged
Depends on:
Blocks:
 
 
Reported: 2015-04-29 15:42 UTC by Niklas Keller
Modified: 2021-06-09 16:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Niklas Keller 2015-04-29 15:42:35 UTC
If you connect to a bluetooth headset, changing the profile doesn't have any effect. It keeps using HSP/HFP even if the select box is changed to A2DP.
Comment 1 Britt Yazel 2015-05-18 05:53:26 UTC
Hi I believe bug 749208 may be the same issue as this one. Either way, I will copy what I posted there:

Hi, I also have what I believe is this issue, however with me it was the pairing of my bluetooth headphones, not a speaker. However, I believe both are caused by the same thing. It seems that the pulse audio module: module-bluetooth-discover works only if started after the X11 session is up. Perhaps the changes to gdm running on Wayland natively, or some other issue, has caused this command to never successfully run?

Further, I have come accross a workaround for the time being:

Edit the file:
/etc/pulse/default.pa
and comment out (with an # at the beginning of the line) the following line:
#load-module module-bluetooth-discover
now edit the file:
/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
    fi
add the following line:
    /usr/bin/pactl load-module module-bluetooth-discover
This way the Pulse audio’s Bluetooth modules will not be downloaded at boot time but after x11 is started.

I have a thread on the Archlinux forums here:
https://bbs.archlinux.org/viewtopic.php?id=197482

and I reported this issue to pulseaudio, so they can know about it here:
https://bugs.freedesktop.org/show_bug.cgi?id=90490
Comment 2 Britt Yazel 2015-10-09 05:57:02 UTC
This issue is still persistent on 3.18
Comment 3 Pander 2017-05-07 20:46:26 UTC
I have a similar problem when trying to play audio from Ubuntu 17.04 to Sony MDR-1000X https://www.sony.com/electronics/headband-headphones/mdr-1000x

Setting up the Bluetooth connection in GNOME Control Center works. It reports Connection: On, Paired: Yes, Type: Headset, Address: ... When I go to Sound Settings, I see it listed below my internal sound card as Headset - MDR-1000X but when I select it, nothing happens and audio keeps playing over the internal sound card.

Only with the application blueman-manager from the blueman package I can change for this bluetooth device the Audio Profile from Headset Head Unit (HSP/HFP) to High Fidelity Playback (A2DP Sink) and I can select it in the Sound Settings and audio is being played from this headset.

So, for many users this is way too difficult to figure out. So next to Sound Settings providing a way to change Audio Profile, the Audio Profile should IMHO by deault be set to A2DP and not SHP/HFP.
Comment 4 Pander 2017-05-07 20:54:28 UTC
Ah, once I have done this, I can change the Profile for this headset in GNOME Control Center - Sound Settings, not now anymore after reconnecting. When/If a fix is out there, I am willing to help testing.
Comment 6 Ricardo 2018-06-06 11:50:40 UTC
I had the same problem on Debian 10 (Buster/Testing).

What worked for me was the workaround 1 described in this link 

https://wiki.debian.org/BluetoothUser/a2dp

Is there any hope for a permanent fix?
Comment 7 Pander 2020-11-17 14:48:55 UTC
What is the current status (with regard to that bugzilla is replaced with github)?
Comment 8 André Klapper 2021-06-09 16:25:32 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.