From: "Csillag Kristóf" <csillag.kristof@gmail.com>
To: bluez-users@lists.sourceforge.net
Cc: marcel@holtmann.org
Subject: Using AVRCP with current BlueZ
Date: Thu, 22 Nov 2007 17:26:25 +0100 [thread overview]
Message-ID: <9a119b3c0711220826u405b3845pb1101fcfb2c42e3c@mail.gmail.com> (raw)
Hi there!
The wiki page at http://wiki.bluez.org/wiki/HOWTO/AudioDevices says that
I no longer not need bluetooth-alsa, plugz, btsco or the like for audio
to work - they are now obsolete.
My question is, how can I use AVRCP now? bluetooth-alsa used to contain
some support for it, but now I guess it's gone. Browsing the source
code of bluez-utils, I see some dbus interface, but I can not find
any example demonstrating how to use this.
Could you please point me to the right documentation (if it exists)?
Thank you for your help:
Kristof Csillag
next reply other threads:[~2007-11-22 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 16:26 Csillag Kristóf [this message]
2007-11-22 17:13 ` [Bluez-users] Using AVRCP with current BlueZ Johan Hedberg
2007-11-23 2:36 ` \x11
2007-11-23 12:00 ` Csillag Kristóf
2007-11-23 12:32 ` Johan Hedberg
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=9a119b3c0711220826u405b3845pb1101fcfb2c42e3c@mail.gmail.com \
--to=csillag.kristof@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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