From: Frederic Dalleau <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New A2DP support : HOWTO ?
Date: Mon, 13 Aug 2007 18:46:31 +0200 [thread overview]
Message-ID: <1187023591.6262.28.camel@ubuntu.mpl.access-company.com> (raw)
In-Reply-To: <46C088D7.9000108@silicom.fr>
Hi,
> Certainly a very stupid question : but how do we get started using
> the
> brand new A2DP support ? - for me it seems that it still favors sco over
> a2dp :-(
I modified the test-audio python script to get something like this:
Look at your syslog to see what happen.
I then got my headset connected and could hear something ;)
#!/usr/bin/python
import dbus
bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'),
'org.bluez.Manager')
conn = manager.ActivateService('audio')
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'),
'org.bluez.audio.Manager')
# Create device
path = audio.CreateDevice("00:03:89:AA:BD:64")
# Get org.bluez.audio.Sink interface
sink = dbus.Interface(bus.get_object(conn, path),
'org.bluez.audio.Sink')
try:
sink.Connect()
except:
pass
#sink.Disconnect()
Hope this helps
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-13 16:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 16:37 [Bluez-devel] New A2DP support : HOWTO ? Fabien Chevalier
2007-08-13 16:46 ` Frederic Dalleau [this message]
2007-08-13 17:06 ` Marcel Holtmann
2007-08-13 17:25 ` Frederic Dalleau
2007-08-13 17:50 ` Marcel Holtmann
2007-08-14 12:50 ` Fabien Chevalier
2007-08-14 16:30 ` Marcel Holtmann
2007-08-17 10:42 ` Fabien Chevalier
2007-08-17 11:00 ` Marcel Holtmann
2007-08-17 11:28 ` Fabien Chevalier
2007-08-17 11:42 ` Johan Hedberg
2007-08-17 12:44 ` Frederic Dalleau
2007-08-17 13:18 ` Johan Hedberg
2007-08-17 13:43 ` Johan Hedberg
2007-08-17 13:53 ` Frederic Dalleau
2007-08-17 14:02 ` Marcel Holtmann
2007-08-17 14:15 ` Brad Midgley
2007-08-17 14:29 ` Frederic Dalleau
2007-08-18 14:10 ` Fabien Chevalier
2007-08-18 14:02 ` Fabien Chevalier
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=1187023591.6262.28.camel@ubuntu.mpl.access-company.com \
--to=frederic.dalleau@access-company.com \
--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