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;


I've attached two log files from hcidump -x. from_phone is when I attempted to 
pair the phone with the computer. to_phone is when I allowed the pppd/rfcomm 
connection to initiate the pairing between the phone and the computer. (After 
the link key is established, it then goes into my rfcomm/PPP setup...)

In summary, the SE T610 doesn't want to pair with bluez when it initializes the 
connection (is the master?) and for some reason bluez doesn't seem to correct 
this (doesn't role switch by default?). However, you can work around the problem 
by forcing bluez to initialize the connection.

(Also, it appears that my bluez hcid is not waiting for the pin_helper to return 
with a pin (e.g. the /usr/bin/bluepin and /usr/bin/bluez-pin helper programs did 
not work for me, while replacing them with a script that just echoed my pin 
(quickly) did work...)


Jay