From: "Rolf E. Thorup" <rolft@daimi.au.dk>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Power level & Scan Timing
Date: Thu, 09 Sep 2004 09:45:30 +0200 [thread overview]
Message-ID: <41400A1A.3010808@daimi.au.dk> (raw)
In-Reply-To: <413F701F.5020905@3wt.com.br>
Rafael Vidal Aroca wrote:
>
> Hello,
>
> i'm playing with my dbt-120 d-link usb dongle, and i'm not managing
> to do some things i wanted...
[...]
> 2) I'm using hcitool scan to constantly detect if my ipaq is near my
> desktop. It seems to be really slow (from 10 to 15 seconds to
> scan)...can this time be reduced? Does bluez do some kind of cache? (i
> ask that because i can turn my ipaq of, and hcitool scan will not only
> detect my ipaq anymore in about 12 seconds...)
Try `hcitool scan --help` and you will see there is an option
--length=N. The default is 8 which according to the source of hcitool is
approx. 10 seconds. So try with something lower than 8.
From the help output you will also see a --flush option. Guess what
that does ;-)
Regards
Rolf
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-09-09 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 20:48 [Bluez-users] Power level & Scan Timing Rafael Vidal Aroca
2004-09-09 7:33 ` Marcel Holtmann
2004-09-09 17:26 ` Rafael Vidal Aroca
2004-09-10 8:35 ` Marcel Holtmann
2004-09-09 7:45 ` Rolf E. Thorup [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=41400A1A.3010808@daimi.au.dk \
--to=rolft@daimi.au.dk \
--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.