From: Guillaume Bedot <littletux@zarb.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SDP server failing to connect
Date: Sat, 02 Feb 2008 11:55:14 +0100 [thread overview]
Message-ID: <1201949715.11895.15.camel@littletux> (raw)
In-Reply-To: <523334.87939.qm@web8401.mail.in.yahoo.com>
Hello,
On sam, 2008-02-02 at 12:46 +0530, pramod gurav wrote:
> my /bin/bluepin(permission 755) has
> #!/bin/sh
> echo "PIN:G1UvjyBAx2WZ2ebc"
As a headset (usually?) can't let you enter a pin code, there is a
default like "0000" or "1234".
Did you try these ?
The pin code is usually written in the documentation if you haven't got
it second-hand.
Regards,
Guillaume B.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-02-02 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 7:16 [Bluez-users] SDP server failing to connect pramod gurav
2008-02-02 10:55 ` Guillaume Bedot [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=1201949715.11895.15.camel@littletux \
--to=littletux@zarb.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox