Bug 506879

Summary: Switching Headset from HSP to A2DP Fails
Product: [Fedora] Fedora Reporter: Brian Pitts <brian>
Component: bluezAssignee: Bastien Nocera <bnocera>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 11CC: bnocera, dwmw2, marcel, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-16 13:52:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian Pitts 2009-06-19 04:24:05 UTC
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

[Headset]
HFP=true

then restarting bluetooth and connecting the headset provided the expected behaviour.

Comment 1 Bastien Nocera 2009-06-19 14:21:15 UTC
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 13:52:27 UTC
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=c369f322aa87e30a025a6e3b6facb1fa77c0c79b
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.