[pulseaudio-discuss] Extra A2DP codecs support in bluetooth module

Georgi Boiko georgi at pandasauce.org
Sun Jul 22 09:14:21 UTC 2018

Hi Pali,

Does it have to be codec switching? If there was to be an implementation 
that settles on the best quality codec available that is supported by 
both sides of communication, it would already be over and beyond what 
currently exists. The order is obvious as of today:






BlueZ already follows this logic, it is just that PA does not register 
any capabilities other than SBC.

Allowing forced codec selection through the GUI is nice to have, but 
given the complexity of implementing it, may not be worth the hassle for 
the initial milestone.

On 22/07/18 09:51, Pali Rohár wrote:
> Hi!
> On Sunday 22 July 2018 00:10:47 Georgi Boiko wrote:
>> Hi,
>> Does anybody know what happened after this discussion? Is this long overdue
>> upgrade on the roadmap?
>> https://lists.freedesktop.org/archives/pulseaudio-discuss/2017-July/028398.html
> See this thread:
> https://lists.freedesktop.org/archives/pulseaudio-discuss/2018-July/030198.html
> Basically there is a patch for aptX support, but that one just replace
> SBC by aptX. So need to decide which codec to support at compile time.
> This is current limitation of bluez - linux bluetooth daemon - which
> does not support codec switching.
> See also this thread:
> https://lists.freedesktop.org/archives/pulseaudio-discuss/2018-July/030253.html
> So until bluez is extended to support switching and configuring A2DP
> codec, there would not be support for any other codec then SBC.

More information about the pulseaudio-discuss mailing list