From: Marco Trudel <trudemar@zhwin.ch>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] RE[2]: inquiry scan problems
Date: Mon, 29 Nov 2004 22:38:39 +0100 [thread overview]
Message-ID: <41AB96DF.4080405@zhwin.ch> (raw)
> > [my description of the inquiry problems with java (jsr82)]
> can your reproduce it without using any JSR-82 stuff?
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 :-) ?
- during scans, if nothin changes (no new/disappeared devices), the
friendlyName changes to n/a for a single inquiry (very rare, but it happens)
- if multiple new devices come in rainge, old devices migt have a n/a
friendlyName (the right one comes back in the next scan)
thanks for your time...
kind regards
Marco
-------------------------------------------------------
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 reply other threads:[~2004-11-29 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 21:38 Marco Trudel [this message]
2004-11-29 21:50 ` [Bluez-users] RE[2]: inquiry scan problems Marcel Holtmann
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=41AB96DF.4080405@zhwin.ch \
--to=trudemar@zhwin.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox