From: deker <deker@slackdot.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] bluez audio questions
Date: Thu, 16 Oct 2008 15:58:36 -0400 [thread overview]
Message-ID: <48F79CEC.2020803@slackdot.org> (raw)
So, per Brad's advice I've been following the audio HOWTO at
http://wiki.bluez.org/wiki/HOWTO/AudioDevices
I seem to either not be getting something, or bluez has changed it's
dbus interface for audio dramatically. Looking at the HOWTO, it would
appear that I have to active the audio service before I can send audio
to a device. Great, no problem. Ok, one
problem...org.bluez.Manager.ActivateService doesn't seem to exist.
Looking at the dbus API spec in the 4.13 source tarball doesn't list it,
and looking at dbus with D-Feet I see what matches the API listed in the
docs. Is there some new method for service activation I'm missing?
Any help is appreciated. I really don't feel like this should be rocket
surgery, I guess I just haven't found the bluez-audio Rosetta Stone yet...
Thanks again,
-d
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-10-16 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 19:58 deker [this message]
2008-10-16 21:54 ` [Bluez-devel] bluez audio questions 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=48F79CEC.2020803@slackdot.org \
--to=deker@slackdot.org \
--cc=bluez-devel@lists.sourceforge.net \
/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