Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Trouble pairing with new phone... (FIXED!)
Date: Mon, 14 Feb 2005 20:27:00 +0100	[thread overview]
Message-ID: <1108409220.7780.15.camel@notepaq> (raw)
In-Reply-To: <4210E7C1.6010706@cc.gatech.edu>

Hi Jay,

> I figured out how to pair with my T610 phone.
> 
> Point 1: The computer must initiate the connection. (If you attempt to scan for 
> new devices on your phone and add it there, apparently bluez will not accept 
> incoming pairing requests. Something to do with roleswitch and bluez wanting to 
> be the master? Perhaps...)
> 
> Point 2: My version of blueZ ignores the /etc/bluetooth/pin file (even when in 
> "auto" mode) and I HAD to replace the pin_helper with a link to a script which 
> simply printed "PIN:1234" (replace number with your pin).
> 
> So, once I replace "pin_helper /usr/bin/bluepin" with "pin_helper /sbin/pintest" 
> (where the pintest file contained "echo "PIN:1234") and initiated an rfcomm 
> connection to the phone with my pppd chat script, I was able to type the pin 
> into my phone and pair.
> 
> [(going the other way, from the phone to the computer, didn't work...possibly a 
> problem with the phone, possibly a problem with bluez (as it works under 
> windows...)]
> 
> My hcid.conf options are as follows:
> Options:
> autoinit yes;
> security auto;
> pairing multi;
> pin_helper /sbin/pintest
> 
> Device:
> name "BlueZ (%d)";
> class 0x100;
> iscan enable;
> pscan enable;
> lp rswitch,hold,sniff,park;
> lm accept,master;
> # Authentication and Encryption
>          auth enable;
>          encrypt enable;

if you still wanna use security mode 3 then go with it. If you set
yourself to master then go with it. These are not defaults settings and
there is a reason why.

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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-14 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 18:02 [Bluez-users] Re: Trouble pairing with new phone... (FIXED!) Jay Summet
2005-02-14 19:27 ` Marcel Holtmann [this message]
2005-02-17 14:02   ` Ka Kin Cheung
2005-02-19 11:43     ` Fredy P.

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=1108409220.7780.15.camel@notepaq \
    --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