Red Hat Bugzilla – Bug 981742
Bluetooth A2DP audio stopped working in Fedora 19
Last modified: 2013-07-06 17:21:20 EDT
Description of problem:
I use the Sennheiser MM550 bluetooth headphones. They support both the telephony and A2DP profiles.
In Fedora 18 A2DP worked perfectly fine. As of the upgrade, it fails to work. The headset uses "Telephony Duplex (HSP/HFP)" when it associates. Changing to A2DP via pavucontrol results in no sound.
Happens with 100% consistency
Steps to Reproduce:
1. Associate headphones
2. Play sound. Notice the quality is bad.
3. Check Configuration tab of pavucontrol
4. Try to change profile to A2DP
Sound stops playing. On the first attempt to change to A2DP, the selection automatically changes to "Off". On subsequent attempts, A2DP remains selected, but still doesn't work. Reconnecting the headphones or any other actions result in HSP/HFP getting used again.
Headphones should work in A2DP mode.
Logs while associating:
Jul 5 18:40:08 madhatter kernel: [ 9162.860711] Bluetooth: Wrong link type (-71)
Jul 5 18:40:16 madhatter kernel: [ 9170.738314] input: 00:16:94:0B:70:BA as /devices/virtual/input/input16
Jul 5 18:40:17 madhatter bluetoothd: bluetoothd: /org/bluez/22295/hci0/dev_00_16_94_0B_70_BA/fd2: fd(30) ready
Jul 5 18:40:17 madhatter bluetoothd: /org/bluez/22295/hci0/dev_00_16_94_0B_70_BA/fd2: fd(30) ready
On trying to change to A2DP:
Jul 5 18:41:00 madhatter bluetoothd: bluetoothd: Audio connection got disconnected
Jul 5 18:41:00 madhatter bluetoothd: Audio connection got disconnected
Jul 5 18:41:00 madhatter pulseaudio: [pulseaudio] module-bluetooth-device.c: Profile has no transport
Oops. Looks like something in the configuration changed in the release, and there was a .rpmnew file that made everything work again.