Skip to content

bluez5: fix issues with simultaneous HF & AG

P V requested to merge pvir/pipewire:bluez-fixes into master

In Pipewire<->Pipewire BT connections, it seems HFP gets connected both as HF and AG on both sides, with separate RFCOMM. It seems we don't know which side was the initiator and what the user intended, so we can't cut one of the connections, but instead have to deal with it.

Not sure if allowing this is spec violation (didn't find a statement in HFP spec so far), but not clear what could be done about it.

Two issues fixed here:

  • For changing codecs, the RFCOMM corresponding to remote HF profile should be used.
  • We should try avoid both sides selecting audio-gateway profile. Break the tie by preferring to be A2DP sender, if remote is both A2DP sink and HF.

This is probably the issue in wireplumber#510

Edited by P V

Merge request reports