Comment 31 for bug 405294

Just wanted to add my two cents worth ...

I spent most of the day trying to figure out why this was happening.

This is definitely not a PA problem. It also occurs using ALSA with the bluetooth plugin.

This is a problem at the bluetooth stack level.

As stated above, it appears that it has something to do with the fact both A2DP and hsc are enabled simultaneously. I also was able to work around it using blueman and connecting/disconnecting the different profiles. However, before that I changed some settings on the bluez daemon configuration. Otherwise the blueman trick doesn't work. I have the following settings in audio.conf:

#[General]
Enable=Source,Control,Sink
Disable=Headset,Gateway
AutoConnect=false

#[Headset]
HFP=true
MaxConnected=1

And the following link setup (from hciconfig -a) :From this should be able to work out what goes in hcid.conf
hci0: Type: USB
 BD Address: 00:90:CC:ED:35:10 ACL MTU: 310:10 SCO MTU: 64:8
 UP RUNNING PSCAN
 RX bytes:119527 acl:77 sco:0 events:16505 errors:0
 TX bytes:4916687 acl:15925 sco:0 commands:553 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Class: 0x5a010c
 Service Classes: Networking, Capturing, Object Transfer, Telephony
 Device Class: Computer, Laptop
 HCI Ver: 1.2 (0x2) HCI Rev: 0xc5c LMP Ver: 1.2 (0x2) LMP Subver: 0xc5c
 Manufacturer: Cambridge Silicon Radio (10)
hcid.conf:

lp rswitch,hold,sniff,park;
lm accept,master;

I'm running bluez 4.58 and pulseaudio 0.9.19 on a gentoo distro.
I know this should probably be raised as a bluez issue, but this is the only place I could find the exact same issue, so I thought I would post here. Sorry!

Finally, could you let me know what headset you were using? I have a pretty old HT820 motorola...