From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Question about hci_create_connection and clock offset
Date: Thu, 24 Apr 2008 15:18:17 +0200 [thread overview]
Message-ID: <1209043097.12684.6.camel@violet.holtmann.net> (raw)
In-Reply-To: <1209038634.6611.209.camel@pancake>
Hi Florian,
> > > However, what I'm trying to do - repeating inquiries in one thread,
> > > checking RSSI in another one (even for devices that haven't been
> > > seen by
> > > the last inquiries) - doesn't seem possible in the D-Bus API, as there
> > > is no function to create a low-level ACL connection to a device
> > > address..?
> > what do you expect from the RSSI value that you get from an active ACL
> > link. It is different from the RSSI value you get via inquiry anyway.
> Well, that wouldn't matter, as I'm going to put all that into a wrapper
> class anyway.
>
> Maybe a word about what I'm trying to do - as you may have guessed
> already, it's about proximity sensing. I've put a minimal Dbus interface
> into my wrapper class and it's actually working quite nicely. However,
> some of the devices which I'm working with - e.g., Motorola mobile
> phones - have a hardcoded discoverable timeout of 3 minutes.
>
> This makes things a bit more difficult for me, as these phones suddenly
> vanish from the list which the Dbus interface is providing, even if they
> are still in range. With the hci_* interface, I can simply try to open
> an ACL connection and get the RSSI value to see if they are just
> invisible. How do I do this with Dbus?
and that RSSI value is totally different from the one you get via an
inquiry and thus you can't put them together. If you could, I would have
done this inside the kernel.
And no matter what you try, creating an ACL baseband connection is most
expensive operation in Bluetooth. So it takes time and that it takes
even more time if you have to wait for the page timeout if the device is
not in range.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-24 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 11:37 [Bluez-devel] Question about hci_create_connection and clock offset Florian Echtler
2008-04-23 13:07 ` Florian Echtler
2008-04-23 16:23 ` Marcel Holtmann
2008-04-24 12:03 ` Florian Echtler
2008-04-24 13:18 ` Marcel Holtmann [this message]
2008-04-24 20:38 ` Florian Echtler
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=1209043097.12684.6.camel@violet.holtmann.net \
--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