All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	David Heidelberg <david@ixit.cz>
Subject: Re: bluez: Export SDP "Remote audio volume control" item for HSP profile
Date: Sat, 21 Mar 2020 19:40:15 +0100	[thread overview]
Message-ID: <20200321184015.mtmb7zfk3jqcf6ya@pali> (raw)
In-Reply-To: <CABBYNZ+nuBOH8gu1EJ4iF_r8v53g3rvVMcCm_Kt=5SXijhQY7A@mail.gmail.com>

On Friday 20 March 2020 10:48:02 Luiz Augusto von Dentz wrote:
> Hi Pali,
> 
> On Fri, Mar 20, 2020 at 6:02 AM Pali Rohár <pali.rohar@gmail.com> wrote:
> >
> > On Sunday 09 February 2020 14:02:43 Pali Rohár wrote:
> > > 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@gmail.com> 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?
> >
> > Hello, I have not got any answer to my question.
> >
> > So may I ask again how to retrieve SDP attribute 0x0302 "Remote audio
> > volume control" for a remote bluetooth headset with HSP profile?
> >
> > It is really important as this attribute says if remote bluetooth
> > headset supports volume control or not. In case it does not support, we
> > need to switch to software volume control on host side.
> >
> > There is open pulseaudio bug that on some headsets it is not possible to
> > control volume level and therefore pulseaudio needs to switch to
> > software volume control.
> >
> > But without checking this SDP attribute 0x0302 this is not possible.
> 
> Not sure when I will have time to work on this one, btw can't you
> actually detect this via some AT command, or the headset simple don't
> respond to the AT command for volume control?

Hello Luiz! I'm planing to add some "workaround" by detecting what
happen when VGS or VGM commands are sent. But this is just a workaround
and I would like to know how would proper solution would like.

Does it mean that currently it is really not possible to retrieve SDP
attributes of remote device? And we need to wait until bluez daemon
exports it via DBus API (fd_properties dictionary under Features key)?

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

  reply	other threads:[~2020-03-21 18:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 17:29 bluez: Export SDP "Remote audio volume control" item for HSP profile Pali Rohár
2019-12-12 19:42 ` Luiz Augusto von Dentz
2019-12-12 23:03   ` Pali Rohár
2020-02-09 13:02     ` Pali Rohár
2020-03-20 13:01       ` Pali Rohár
2020-03-20 17:48         ` Luiz Augusto von Dentz
2020-03-21 18:40           ` Pali Rohár [this message]
2020-03-21 19:54             ` Pali Rohár
2020-04-13 16:25               ` [PATCH 0/3] " Pali Rohár
2020-04-13 16:25                 ` [PATCH 1/3] src/profile: Distinguish between zero-set HFP AG features and unset HFP AG features Pali Rohár
2020-04-13 16:44                   ` Luiz Augusto von Dentz
2020-04-13 16:52                     ` Pali Rohár
2020-04-13 16:58                       ` Luiz Augusto von Dentz
2020-04-13 17:17                         ` Pali Rohár
2020-04-13 17:47                           ` Luiz Augusto von Dentz
2020-04-13 17:58                             ` Pali Rohár
2020-04-13 19:41                               ` Luiz Augusto von Dentz
2020-04-13 19:51                                 ` Pali Rohár
2020-04-13 20:24                                   ` Luiz Augusto von Dentz
2020-04-13 20:42                                     ` Pali Rohár
2020-04-13 21:07                                       ` Luiz Augusto von Dentz
2020-04-13 22:26                                         ` Pali Rohár
2020-04-13 16:25                 ` [PATCH 2/3] src/profile: Export Remote Audio Volume Control SDP value for HSP HS role via first bit in features value Pali Rohár
2020-04-13 16:25                 ` [PATCH 3/3] src/profile: Add default SDP record for Headset role of HSP 1.2 profile with Erratum 3507 Pali Rohár
2020-04-13 16:51                   ` Luiz Augusto von Dentz
2020-04-14  0:09                 ` [PATCH 0/3] bluez: Export SDP "Remote audio volume control" item for HSP profile Luiz Augusto von Dentz
2020-04-14  8:09                   ` Pali Rohár
2020-04-14 19:53                   ` Pali Rohár
2020-04-14 20:28                     ` Luiz Augusto von Dentz
2020-04-14 20:46                       ` [PATCH] doc: Update documentation for HSP and HFP profiles Pali Rohár
2020-04-14 21:03                         ` Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200321184015.mtmb7zfk3jqcf6ya@pali \
    --to=pali.rohar@gmail.com \
    --cc=david@ixit.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.