From: Emiliano Heyns <emiliano.heyns@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] hcitool scan times
Date: Fri, 18 Feb 2005 23:30:20 +0100 [thread overview]
Message-ID: <ac72cfc8050218143042696ba4@mail.gmail.com> (raw)
In-Reply-To: <421638BC.2020808@gmx.ch>
On Fri, 18 Feb 2005 19:49:32 +0100, Marco Trudel <mtrudel@gmx.ch> wrote:
> hello emiliano
>
> read the bluetooth specification.
> you've to allow remote devices ~10.5 seconds to answer... so 13 seconds
> makes sense...
> that it is so fast from time to time is, because a cached result is
> returned. look at the source of hcitool for more information...
OK, thanks. This could actually work to my benefit if I disable the
hcitool cache -- the device could take the time the user takes from
walking into range to being at the device for detecting, if you walk
out of range before that you were only passing the device. Good. Now I
only have to look at average office walking speeds to see how great I
want this radius to be :)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-18 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 9:24 [Bluez-users] hcitool scan times Emiliano Heyns
2005-02-18 18:49 ` Marco Trudel
2005-02-18 22:30 ` Emiliano Heyns [this message]
2005-02-18 22:45 ` Marco Trudel
2005-02-19 13:17 ` Emiliano Heyns
2005-02-21 23:07 ` Marcel Holtmann
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=ac72cfc8050218143042696ba4@mail.gmail.com \
--to=emiliano.heyns@gmail.com \
--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.