From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] org.bluez.Audio and connections
Date: Tue, 12 Dec 2006 20:18:16 -0700 [thread overview]
Message-ID: <457F70F8.6040309@xmission.com> (raw)
Marcel
Can we go back and look at audio connection init & inspect? I proposed
ListConnectedStreams and ways to examine each stream for profile and
status... we may start up an audio app after the connection was already
going so the app would have missed seeing the connect signals.
Do these look ok?
array{string} ListAudioDevices()
Returns list of bdaddrs for devices that
report audio in their device class.
array{string} Connect(string bdaddr)
Connects the headset/headphones using A2DP or
HSP/HFP or both. Returns the array of streams
representing the successful connections.
void Disconnect(string bdaddr)
Disconnect all streams to the audio device.
array{string} ListConnectedStreams()
string StreamAddress(string stream)
Returns the bdaddr the indicated stream
connects to.
boolean IsHeadset(string stream)
Return true if the stream represents a
headset.
boolean IsSink(string stream)
Return true if the stream represents
headphones.
boolean IsPlaying(string stream)
Return true if the stream is in a playing
state.
boolean IsPaused(string stream)
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2006-12-13 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=457F70F8.6040309@xmission.com \
--to=bmidgley@xmission.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