From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] friendly name in pin exchange
Date: Mon, 19 Mar 2007 16:10:01 +0100 [thread overview]
Message-ID: <1174317002.3690.15.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <BAY135-F39B9DECCEB581ABD12509B8710@phx.gbl>
Hi Vincent,
> I have a pin helper script that does pin exchange in my Bluez stack.
> The pin script detects incoming arguments and then hands out a pin
> accordingly.
>
> I am working with a device that the manufacturer says has a friendly name
> that is 20+ characters long. But incoming arguments, as I can see from the
> pin script, has only the bluetooth address of this remote device. I am
> looking at the Bluez D-Bus API but I do not see anything appropriate that I
> can call during pin exchange to fetch information like the friendly name.
> Is there another way to retrieve additional info about this device? This
> device is master and not discoverable so I have to wait for it to connect to
> my host.
the D-Bus API is the way to go. However you might wanna look at
bluez-gnome and its bluetooth-applet application, because that is
handling the passkey requests and also the name resolving.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-03-19 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 18:17 [Bluez-users] friendly name in pin exchange Vincent Yau
2007-03-19 15:10 ` Marcel Holtmann [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=1174317002.3690.15.camel@aeonflux.holtmann.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox