From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] RE[2]: inquiry scan problems
Date: Mon, 29 Nov 2004 22:50:45 +0100 [thread overview]
Message-ID: <1101765045.7562.48.camel@pegasus> (raw)
In-Reply-To: <41AB96DF.4080405@zhwin.ch>
Hi Marco,
> yes. i tried the inquiries with "hcitool scan".
> again, i do 5 and more inquiries in a row with one second sleep between
> inquiries single "hcitool scan"'s...
>
> here what i noted:
> - it needs in average 4 inquiries to get a new device after it's in
> rainge (4 single "hcitool scan" until it's visible).
> - it needs in average 2 inquiries to see that a device is no longer in
> rainge (or has bluetooth disabled). the first new inquiry usually gives
> "n/a" as the friendlyName, the second one doesn't list it again.
> does maybe bluez or my bluetooth dongle cache old inquiries or is there
> still radiation in the air :-) ?
for me this sounds more like a job periodic inquiry.
Regards
Marcel
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-29 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 21:38 [Bluez-users] RE[2]: inquiry scan problems Marco Trudel
2004-11-29 21:50 ` Marcel Holtmann [this message]
2004-11-29 21:59 ` Marco Trudel
2004-11-30 5:28 ` 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=1101765045.7562.48.camel@pegasus \
--to=marcel@holtmann.org \
--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.