From: Peter Wurmsdobler <peter@wurmsdobler.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Headset, ALSA and other issues
Date: Fri, 08 Feb 2008 09:34:14 +0000 [thread overview]
Message-ID: <47AC2216.6030600@wurmsdobler.org> (raw)
In-Reply-To: <E7A0FBBA-A2CF-4B87-B4CA-B05CD6BF5600@gmail.com>
Hello Johan,
> The preferred way would be to use the BlueZ D-Bus interface, but I'm
> not aware of any nice UI to do it (e.g. the bluetooth-wizard from
> bluez-gnome is still incomplete).
I had this wizard running on the desktop, but I am not very happy with
it as it is not clear how it happens, what happens and also it is not
predictible enough.
> You can however find some examples
> of running dbus-send from the command line and example python scripts
> here:
> http://wiki.bluez.org/wiki/HOWTO/Bonding
Thanks, I will have a look at it.
If a "client" would send requests on the dbus, who would be the
receiver? WOuld it have to be hcid?
As mentioned earlier, the entire bt system appears to me very woolly;
difficult to get a grip onit.
peter
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-02-08 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 19:05 [Bluez-users] Headset, ALSA and other issues Peter Wurmsdobler
2008-02-07 19:49 ` Brad Midgley
2008-02-07 22:43 ` Peter Wurmsdobler
2008-02-07 22:52 ` Brad Midgley
2008-02-07 22:59 ` Rod Boyce
2008-02-08 1:06 ` Brian Sammon
2008-02-08 9:05 ` Peter Wurmsdobler
2008-02-08 9:26 ` Johan Hedberg
2008-02-08 9:34 ` Peter Wurmsdobler [this message]
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=47AC2216.6030600@wurmsdobler.org \
--to=peter@wurmsdobler.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.