From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problems with my own inquiry
Date: Sat, 16 Jun 2007 09:29:47 +0200 [thread overview]
Message-ID: <1181978987.6846.50.camel@aeonflux.inter-touch.com> (raw)
In-Reply-To: <200706151809.04115.fernando@bluexare.org>
Hi Fernando,
> I have an application that works with the bluetooth, scanning and sending
> content with other devices..., and now, when I'm trying to make irt work in
> other distribution, it fails.
the solution is to use the new D-Bus based API. It takes care of
everything that you want.
> This is a normal work, whit INQUIRY_RESULT and COMMAND_STATUS, but in the new
> PC (a debian etch, buiilt by DebianLive) where I want to install the
> application the output is like this:
The new hcid switches into the best inquiry mode and that means Inquiry
with RSSI (which is different event) for a Bluetooth 1.2 dongle or
later. You have to watch for that event, too. Or use the D-Bus API that
does that for you and already takes care of Extended Inquiry of the
Bluetooth 2.1 specification.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-16 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 16:09 [Bluez-devel] Problems with my own inquiry Fernando Unzu
2007-06-16 7:29 ` Marcel Holtmann [this message]
2007-06-18 7:38 ` Fernando Unzu
2007-06-19 14:31 ` Marcel Holtmann
2007-06-20 0:43 ` Simon
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=1181978987.6846.50.camel@aeonflux.inter-touch.com \
--to=marcel@holtmann.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