From: Thomas Kear <thomas.kear@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] how to make the device be discoverable
Date: Mon, 6 Aug 2007 19:57:48 +1200 [thread overview]
Message-ID: <200708061957.56356.thomas.kear@gmail.com> (raw)
In-Reply-To: <E1IHxKc-0003YU-HU@mail.sourceforge.net>
[-- Attachment #1.1: Type: text/plain, Size: 637 bytes --]
On Mon, 06 Aug 2007, leiyu@kcoe.cn wrote:
> Dear All,
>
> I use bluez in embedded linux, it can use "hcitool scan" command to search
> for other bluetooth device , how to make it be discoverable so that other
> device can discover it? Thanks!
>
> Best regards,
> Leiyu
dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0
org.bluez.Adapter.SetMode string:discoverable
More or less.
add
discovto 0;
to the 'device' section of hcid.conf to make it permanent, or a non-zero value
to set a time before the device becomes hidden again (i think in minutes, but
not sure)
Thomas
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-08-06 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 7:42 [Bluez-users] how to make the device be discoverable leiyu
2007-08-06 7:57 ` Thomas Kear [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=200708061957.56356.thomas.kear@gmail.com \
--to=thomas.kear@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.