public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] how to use bluez-audio with "point-and-click" audio selection	applications
Date: Sat, 23 Feb 2008 23:13:56 -0500	[thread overview]
Message-ID: <1203826436.8021.20.camel@pc.ilinx> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]

I've seen it mentioned time and time again that using bluez-audio, the
bluetooth headset will not be enumerated as a sound device as other
devices are, like sound cards.  The answer seems to be always, "just
type in bluetooth where it wants a device selection".  Well, I guess
that's fine for an application that provides that.

But how does one deal with this problem with devices that enumerate
sound devices and provide a point-and-click-menu type interface for
them.  One example of such is Ekiga.

Despite my previous posting about my troubles with getting a BT headset
working on Ubuntu Hardy (my desktop workstation), I did manage to get it
working on Ubuntu Gutsy on my laptop.  i.e. I can successfully do:

$ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE

and hear myself.  I'd like to use this headset with Ekiga though.  Any
ideas?

BTW: what's with the long pause opening the headset for playback?

20228 23:14:06 socket(PF_FILE, SOCK_STREAM, 0) = 3
20228 23:14:06 connect(3, {sa_family=AF_FILE, path=@/org/bluez/audio}, 110) = 0
20228 23:14:06 pipe([4, 5])             = 0
20228 23:14:06 fcntl64(4, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
20228 23:14:06 fcntl64(5, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
20228 23:14:06 send(3, "00:1A:45:1B:19:89\0\0\0\0\f\1\0\0\0\0\0\0\0\0\0"..., 34, 0) = 34
20228 23:14:06 recv(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\10\0010\0\2"..., 30, 0) = 30
20228 23:14:10 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"m", 1}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {6}}, msg_flags=0}, 0) = 1
20228 23:14:10 recv(6, 0x8062324, 48, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily unavailable)

Notice the 4 seconds between sending and receiving a message on
the /org/bluez/audio socket.

b.


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

                 reply	other threads:[~2008-02-24  4:13 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=1203826436.8021.20.camel@pc.ilinx \
    --to=brian@interlinx.bc.ca \
    --cc=bluez-users@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