On Saturday 08 June 2019 12:59:24 Pali Rohár wrote: > Ok. So is there any way how to check if bluez supports profile switching > or not? And if not, could be introduced some flag/property on DBus so > applications would not this information? Because older versions of bluez does not support profile switching and does not support properly remembering last used SEP, I need to know this information in pulseaudio. To prevent any breakage e.g. that high bandwidth codec would be chosen by old version of bluez in unsuitable environment. Because of these problems I do not think that pulseaudio should register these high quality codec with fixed high bandwidth. And currently there is no way (or at last I do not know) how to check if bluez support these features. And I need to know it at time when pulseaudio is registering to DBus so it would correctly decide if SBC UHQ codec should be registered via DBus to bluez or not. Currently I know one way how to detect it -- look if there are available SEP paths at dbus. But this works only after A2DP connection is active. So I cannot use this "heuristic". Therefore I'm asking for some DBus property or flag or whatever which would tell me, prior to registering A2DP codecs via DBus to bluez, if bluez supports profile switching or not. Without this information, pulseaudio could enter into state when it is unable to transmit any audio via bluetooth because old bluez chosen unsuitable codec. And because old bluez version does not support profile switching, nobody (pulseaudio or user) is able to fix this problem. -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: PGP signature
