On Friday 13 December 2019 00:03:14 Pali Rohár wrote: > On Thursday 12 December 2019 21:42:27 Luiz Augusto von Dentz wrote: > > Hi Pali, > > > > On Thu, Dec 12, 2019 at 7:31 PM Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > > > > > > Hello! > > > > > > According to HSP 1.2 specification, section 4.7 Remote Audio Volume > > > Control, Support for remote audio volume control is optional, so an > > > implementation may support none, either, or both of the controls for > > > microphone volume and speaker volume. > > > > > > According to HSP 1.2 specification, section 5.3 SDP Interoperability > > > Requirements, bluetooth device with HSP profile announce via SDP "Remote > > > audio volume control" field information if device itself supports volume > > > control. > > > > > > But currently I did not found any way how to access "Remote audio volume > > > control" SDP field in (pulseaudio) application as bluez does not export > > > it. > > > > > > Can you please export this field? E.g. for HFP profile all optional > > > features from SDP are passed to NewConnection() DBus method via > > > fd_properties dictionary under Features key. Could you export that > > > "Remote audio volume control" bit for HSP profile in Features key? > > > > > > And in same way, this needs to be handled also in RegisterProfile() DBus > > > method. > > > > Do you have a use case in mind? > > Yes, checking in pulseaudio if remote side announce that supports remote > volume control or not. And based on this switch to software volume > level. Hello Luiz! Is it is possible to export this field? -- Pali Rohár pali.rohar@xxxxxxxxx