Comment 2 for bug 1519007

I looked through the linked syslog and the device you connect here has atleast support for HSP and A2DP. It gets connected on HSP and A2DP.

What telepathy-ofono now does when a call comes in is the following:

It switches the profile of the available bluetooth audio card to "headset_head_unit" (which means HSP). With that the device is now prepared for HSP and A2DP is not active anymore so we can't play any audio on it anymore. HSP is only meant for voice. This wouldn't happen if the device supports A2DP only. In that case the profile of the bluetooth audio card wouldn't be switched to "headset_head_unit" but would still be "a2dp_sink" and being able to play the ringtone.

IMHO there is one thing we should fix in telepathy-ofono: We should switch to te "headset_head_unit" profile for the bluetooth audio card only when the call becomes active and stay with A2DP as long as possible (if this doesn't give a too long delay between activating the call and switch to headset_head_unit).

Marking bluez as invalid for this bug and adding telepathy-ofono for the guys to comment.

@Victor: Please retest this with a speaker which supports A2DP-only and not HSP or HFP. You can find out what each device supports by looking at its details with bluetoothctl.