You are not logged in.
Hi All,
With the upgrade to PulseAudio 6.0 last week, my Bose OE SoundLink bluetooth headset no longer connects to the A2DP profile.
The new PulseAudio 6.0 upgrade brought a headset_head_unit: Headset Head Unit (HSP/HFP) profile that actually works! Unfortunately, I get a Refused to switch profile to a2dp_sink: Not connected when I attempt to switch to the a2dp_sink profile.
To switch pulseaudio profile:
$ pacmd set-card-profile 1 a2dp_sink
Failed to set card profile to 'a2dp_sink'.
Started pulseaudio in foreground and the interesting logs are here:
$ pulseaudio -k && pulseaudio -vvvvv
... (lots of logs)...
... (above set-card-profile command executed) ...
I: [pulseaudio] client.c: Created 6 "UNIX socket client"
W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected
D: [pulseaudio] cli.c: CLI got EOF from user.
I: [pulseaudio] client.c: Freed 6 "UNIX socket client"
$ pacmd ls
... (lots of logs) ...
index: 1
name: <bluez_card.00_0C_8A_EA_B3_96>
driver: <module-bluez5-device.c>
owner module: 27
properties:
device.description = "Bose OE SoundLink"
device.string = "00:0C:8A:EA:B3:96"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headphone"
bluez.path = "/org/bluez/hci0/dev_00_0C_8A_EA_B3_96"
bluez.class = "0x240418"
bluez.alias = "Bose OE SoundLink"
device.icon_name = "audio-headphones-bluetooth"
profiles:
headset_head_unit: Headset Head Unit (HSP/HFP) (priority 20, available: unknown)
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 10, available: no)
off: Off (priority 0, available: yes)
active profile: <headset_head_unit>
sinks:
bluez_sink.00_0C_8A_EA_B3_96/#1: Bose OE SoundLink
sources:
bluez_sink.00_0C_8A_EA_B3_96.monitor/#2: Monitor of Bose OE SoundLink
bluez_source.00_0C_8A_EA_B3_96/#3: Bose OE SoundLink
ports:
headphone-output: Headphone (priority 0, latency offset 0 usec, available: unknown)
properties:headphone-input: Bluetooth Input (priority 0, latency offset 0 usec, available: unknown)
properties:
Uploaded full logs of pacmd ls and pulseaudio -vvvv: https://gist.github.com/saamalik/7fd15b9826cbede2665c
Anyone have any ideas why A2DP stopped working after PulseAudio 6.0 upgrade?
Offline
Interesting. Your headset seems to be reporting that a2dp_sink is not available. Have you tried re-pairing the headset just in case?
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
@Soukyuu - didn't work. I also deleted the ~/.config/pulse directory and rebooted system, but the a2dp_sink still shows unavailable.
Offline
I have the same issue with my Sony XRS-X3, it's an external bluetooth speaker that supports a mic.
index: 2
name: <bluez_card.0C_A6_94_7A_96_A7>
driver: <module-bluez5-device.c>
owner module: 28
properties:
device.description = "SONY:SRS-X3"
device.string = "0C:A6:94:7A:96:A7"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "speaker"
bluez.path = "/org/bluez/hci0/dev_0C_A6_94_7A_96_A7"
bluez.class = "0x240414"
bluez.alias = "SONY:SRS-X3"
device.icon_name = "audio-speakers-bluetooth"
profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 10, available: no)
headset_head_unit: Headset Head Unit (HSP/HFP) (priority 20, available: unknown)
off: Off (priority 0, available: yes)
active profile: <headset_head_unit>
sinks:
bluez_sink.0C_A6_94_7A_96_A7/#2: SONY:SRS-X3
sources:
bluez_sink.0C_A6_94_7A_96_A7.monitor/#3: Monitor of SONY:SRS-X3
bluez_source.0C_A6_94_7A_96_A7/#4: SONY:SRS-X3
ports:
speaker-output: Speaker (priority 0, latency offset 0 usec, available: unknown)
properties:
speaker-input: Bluetooth Input (priority 0, latency offset 0 usec, available: unknown)
properties:
Offline
@grunn did you start experiencing isues after the PulseAudio 6.0 upgrade?
Offline
Yes, though I had issues before the upgrade as well. Before the upgrade I had to forget/re-pair the XRS-X3 every time I wanted to use it but a2dp worked. After the upgrade I can't get a2dp working, only the HSP/HFP profile works.
Offline
I was giving time to pulseaudio5/bluez5 to get in shape. But new commits on bluez5 are ONLY for android, and looks like Pulseaudio 6 is just worst, don't know wtf is going on here cause bluez4/pulseaudio4 works perfect, right now I'm using Mint KDE and my Bluetooth Headset works better than in Windows 8.1.
Try to submit bug to pulseaudio devs
Pulseaudio 6 is in Ubuntu Vivid 15.04 but they use with bluez 4.101. I will try it later to see if works.
Last edited by felipe (2015-02-24 18:15:48)
Offline
Cool. I'll also submit a request to the PulseAudio forum.
Offline
For anyone who missed it.
There is a workaround. Works with my Philips SHB5500
Offline
@Robiasiewicz that fixed it for me! You're a genius. Thanks!! I have a Bose OE SoundLink
Offline
@Robias Did you file a report with ArchLinux/PulseAudio?
Offline
@SimFox3
I'm just a guy who googled it. The credit goes to blog's author.
No, I didn't.
Offline
Thanks for the workaround, this also fixed it for my Sony XRS-X3
Offline
Hello,
If is possible someone could explain what I need to do for my bluetooth work out of box. I'd appreciate a lot.
Thanks a lot
Offline
@HenriqueNunnes See the following link: https://wiki.archlinux.org/index.php/Bluetooth_headset
If it doesn't work, see the following post: https://g751jy.wordpress.com/about/parr … h-headset/
Offline
I have the same issue - I cant switch old headphones paired a year ago from a2dp, and a new heaset - to a2dp.
https://g751jy.wordpress.com/about/parr … h-headset/ - this link was deleted
Offline
Cached version of the page: http://webcache.googleusercontent.com/s … clnk&gl=us
Here are the steps:
Bug and possible solution: actually I found a bug in that make the headset unusable, it seems that the pulse audio module: module-bluetooth-discover works only if started after the X11 session is up. So I have a workaround.
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
fiadd 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.
Last edited by SimFox3 (2015-05-06 17:54:06)
Offline
This sounds very similar to a this thread ... https://bbs.archlinux.org/viewtopic.php … 3#p1526283
rainpl found this solution http://www.debuntu.org/how-to-disable-p … nd-in-gdm/ which prevents GDM capturing a2dp sink on session start.
Not sure which display manager you are using or if this is applicable in this instance, but I hope it helps .... worked for me.
Offline
This sounds very similar to a this thread ... https://bbs.archlinux.org/viewtopic.php … 3#p1526283
rainpl found this solution http://www.debuntu.org/how-to-disable-p … nd-in-gdm/ which prevents GDM capturing a2dp sink on session start.
Not sure which display manager you are using or if this is applicable in this instance, but I hope it helps .... worked for me.
Thanks a bunch for this tip! My Bluetooth headset was not being registered by PulseAudio for some reason lately, it turns out that this is the reason why (since I am using GDM and Gnome). The solution in that link causes pulseaudio to recognize my bt headset every time!
Offline
Thanks for this.
I had the same issue, and the solution by "toppy" worked fine.
Offline
I hate to bring up an old thread, but the OP's problem is exactly what is happening with me. I tried the fixes that SimFox3 and toppy posted, but I still get the same error. I have the LG HBS750 (LG Tone Pro).
index: 3
name: <bluez_card.00_18_6B_74_36_8D>
driver: <module-bluez5-device.c>
owner module: 27
properties:
device.description = "LG HBS750"
device.string = "00:18:6B:74:36:8D"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_00_18_6B_74_36_8D"
bluez.class = "0x240404"
bluez.alias = "LG HBS750"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
profiles:
headset_head_unit: Headset Head Unit (HSP/HFP) (priority 20, available: unknown)
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 10, available: no)
off: Off (priority 0, available: yes)
active profile: <headset_head_unit>
sinks:
bluez_sink.00_18_6B_74_36_8D/#4: LG HBS750
sources:
bluez_sink.00_18_6B_74_36_8D.monitor/#6: Monitor of LG HBS750
bluez_source.00_18_6B_74_36_8D/#7: LG HBS750
ports:
headset-output: Headset (priority 0, latency offset 0 usec, available: unknown)
properties:
headset-input: Headset (priority 0, latency offset 0 usec, available: unknown)
properties:
Offline
@jmayniac I too had this problem. Run the below and it will remove execute rights on pulseaudio binary for the gdm user, which makes it actually work. I'm not sure what changed, but the autospawn setting is totally ignored now. I've updated the troubleshooting section of the bluetooth headset wiki page to reflect this too:
setfacl -m u:gdm:r /usr/bin/pulseaudio
Then just kill pulseaudio for gdm and it won't be able to respawn:
sudo pkill pulseaudio
Last edited by justin-8 (2015-10-01 20:14:15)
Offline
@justin-8
Thank you for this ...I have just installed Gnome/GDM 3.18 and will give it a try :-)
Offline
A remark from my side:
If you're using systemd (which by now you probably are) rainpl's solution will not work anymore as pulseaudio is started anyway by the systemd user session (this is the case on my system).
Changing acl will break after the next update of pulseaudio so this fix seems dull to me.
You should be able to disable the bluetooth module for the gdm user:
machinectl shell gdm@
sed '/.*ifexists.*bluetooth.*/,/.*endif.*/d' /etc/pulse/default.pa > ~/.config/pulse/default.pa
Last edited by tillmann (2015-11-03 22:14:35)
Offline
I'm really getting tired of jumping through hoops of whatever nonsense the pulseaudio & bluez devs come up with during each release that breaks headsets again. Seriously again? What do I have to do this time?
I don't have gdm installed at all.
If the problem is pulseaudio's modules loading before X11, restarting pulseaudio should suffice as a workaround; it doesn't.
There's something missing that would enable a2dp profiles.... a library? a configuration option? a third-party configuration tool that both dev teams assume to exist but actually does not (like the last time headset support was destroyed)?
Edit: Found it.
For the time being, the A2DP profile will only made be available when a bluetooth device has been connected by explicitly giving the "connect" command in bluetoothctl.
Last edited by quequotion (2015-11-13 19:27:22)
makepkg-optimize · indicator-powersave · pantheon-{3d,lite} · {pantheon,higan}-qq
Offline