Bug 506879 - Switching Headset from HSP to A2DP Fails
Switching Headset from HSP to A2DP Fails
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-19 00:24 EDT by Brian Pitts
Modified: 2009-09-16 09:52 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-16 09:52:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Pitts 2009-06-19 00:24:05 EDT
Description of problem:
Bluetooth headset will not switch to A2DP mode.

Version-Release number of selected component (if applicable):
Version    : 4.37
Release    : 2.fc11

How reproducible:
Occurred every time until I switched the telephone duplex profile from HSP to HFP.

Steps to Reproduce:
1. Using bluetooth-applet, pair Plantronics Voyager 855 headset with a computer running Fedora 11.
2. In pavucontrol, change the configuration from Telephony Duplex to High Fidelity Playback.
Actual results:
No change occurs. "module-bluetooth-device.c: A2DP is not connected, refused to switch profile" is written to /var/log/messages.

Expected results:
I expected my headset to provide stereo audio instead of mono.

Additional info:
I found a workaround at https://tango.0pointer.de/pipermail/pulseaudio-discuss/2009-April/003698.html. Creating /etc/bluetooth/audio.conf with the contents


then restarting bluetooth and connecting the headset provided the expected behaviour.
Comment 1 Bastien Nocera 2009-06-19 10:21:15 EDT
HFP=true is the default in newer versions of bluez, we'll need to upgrade at some point...
Comment 2 Bastien Nocera 2009-09-16 09:52:27 EDT
was fixed in 4.38, and we ship 4.42 in F11, so closing.

Please reopen if this didn't fix the bug for you.

Note You need to log in before you can comment on or make changes to this bug.