From: Diego Liziero <liziero.diego@unimore.it>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hcitool scan problems....
Date: Thu, 25 Nov 2004 09:29:32 +0100 [thread overview]
Message-ID: <1101371373.11603.24.camel@igno> (raw)
In-Reply-To: <1C090C0C-3E51-11D9-950D-00039390D626@pepper.com>
On Wed, 2004-11-24 at 14:43 -0500, Michael Frey wrote:
> I am currently seeing strange behavior while doing "scans".
>
> It takes me several scans to see the devices I have in range. Also,
> sometimes when I issue "hcitool scan" it does not even scan. It just
> stops immediately after printing "Scanning ...".
>
> Can anyone explain this?
Maybe,
the default option is to search other bluetooth devices
for 8 windows (about 10 seconds).
Try to wait 10 seconds or decrease the scanning length
with option --length=how_many_win_to_use_for_searching
When you see the devices printed immediately,
it could be because they are discovered during the first
window, or because they are already in the cache,
due to a previous scan.
Regards,
--
Diego Liziero <diego.liziero@unimore.it>
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-11-25 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 19:43 [Bluez-devel] hcitool scan problems Michael Frey
2004-11-24 21:48 ` Marcel Holtmann
2004-11-29 15:42 ` Michael Frey
2004-11-25 8:29 ` Diego Liziero [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=1101371373.11603.24.camel@igno \
--to=liziero.diego@unimore.it \
--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 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.