linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rohit Sharma <rohitsharmaddun@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: AVRCP 1.3 support
Date: Wed, 7 Mar 2012 23:01:30 -0800	[thread overview]
Message-ID: <CAPHSBCnoTp_YAJayhRB4xt7ZdZOuTD9MdqkWrDN_MYAvCOVFEw@mail.gmail.com> (raw)

Hi All,

For AVRCP 1.3 support in current bluez, this is supported using
org.bluez.Media Interface in which a player registers with bluez using
RegisterPlayer DBus methods.
Have a query how the bluez will be identifying the player and respond
the correct metadata or attributes.

Based on the following blog, Is this supported in pulseAudio currently
which version of player or pulseAudio i should be using for handling
this.
http://jprvita.wordpress.com/

The proposed approach to implement this project is to have PulseAudio
intermediating data exchange between media players and bluetoothd. For
each audio stream going to a bluetooth audio sink it would listen to
TrackChange and StatusChange signals coming from the application
generating the stream going to that device and send this information
to the remote peer through AVRCP calling a method exposed on
bluetoothd’s org.bluez.Control interface. This integration could
latter be extended for basic player controls, having PulseAudio to
listen to bluetoothd signals and call methods on media players MPRIS
interfaces to trigger the matching action. Also, a similar approach
could be modeled for adding content browsing capability, as defined by
AVRCP 1.4 specification.

Thanks & Regards
Rohit Sharma

             reply	other threads:[~2012-03-08  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  7:01 Rohit Sharma [this message]
2012-03-08 10:39 ` AVRCP 1.3 support 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=CAPHSBCnoTp_YAJayhRB4xt7ZdZOuTD9MdqkWrDN_MYAvCOVFEw@mail.gmail.com \
    --to=rohitsharmaddun@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).