[pulseaudio-discuss] [PATCH v9 0/8] Bluetooth A2DP codecs

[Pali Rohár]

On Thursday 25 April 2019 13:28:16 Pali Rohár wrote:
> On Thursday 25 April 2019 14:19:15 Luiz Augusto von Dentz wrote:
> > These seems to work great, I can even switch on the fly the profiles
> > and after a short delay it switches without a problem, there is one
> > issue related to reconnecting though:
> > 
> > https://gist.github.com/Vudentz/40f10e85fb860083958edae67093f016
> > 
> > With BlueZ remembering the last used endpoint (aptX) it seems the
> > policy ignores that and reverts to highest priority (SBC UHQ),

Relevant lines:

D: [lt-pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_94_20_53_2E_08_CE/sep5/fd26 available for profile a2dp_sink_aptx
...
D: [lt-pulseaudio] card.c: a2dp_sink_aptx availability unknown
...
D: [lt-pulseaudio] card.c: off availability yes
I: [lt-pulseaudio] card.c: bluez_card.94_20_53_2E_08_CE: active_profile: a2dp_sink_sbc_uhq2
D: [lt-pulseaudio] module-bluetooth-policy.c: Looking for A2DP profile activated by bluez for card bluez_card.94_20_53_2E_08_CE
I: [lt-pulseaudio] card.c: Created 5 "bluez_card.94_20_53_2E_08_CE"

We got information that sep5 is activated with fd26 and it corespondent
to profile a2dp_sink_aptx. And on next lines we see that profile has
unknown availability -- which means that it is possible to switch to
that codec/profile, but it is not activated yet. On next lines we see
that module-bluetooth-policy is trying to find "a2dp_*" which has
availability "on", but there is no one. So initial profile stay
a2dp_sink_sbc_uhq2 which was chosen as default by card.c.

So problem is why a2dp_sink_aptx profile has unknown availability even
it is activated? It should have "on" availability. And then policy
choose it as initial.

-- 
Pali Rohár
pali.rohar at gmail.com