cjdshaw wrote:

In any case, you may have an easier time if you use this script
http://www.3eportal.com/index.php?optio … p;Itemid=1

The script does nothing except facilitate gprs config setup and I already used it. The script requires the phone to initaite pairing and even the scripts author admited to me that he does not know how to initiate pairing from the epc. Seems to be a real mystery!

Are you saying that the epc can't initiate pairing?
I initiate  from the pc not the phone when I use my xp laptop.

When I try to search for devices from the phone (turns out it can), it doesn't find the epc.

Last edited by bikeman (2008-04-10 11:21:33 am)

Not sure what to actually do here, I get no such file or directory at
/var/lib/bluetooth/00:15:83:09:36:97/config

How do I delete the whole
/var/lib/bluetooth/<BLUETOOTH ADDRESS>
folder?

Last edited by bikeman (2008-04-10 12:32:10 pm)

devices:
hci0  00:15:83:09:36:97

I don't have a bluetooth directory

cd /var/lib/bluetooth/
bash: cd: /var/lib/bluetooth/: no such file or directory

Last edited by bikeman (2008-04-10 12:38:50 pm)

re cap:
my phone can initiate paring but my eee pc is apparently undiscoverable. Advice to delete /var/lib/bluetooth/<BLUETOOTH ADDRESS> hasn't gone anywhere because I dont have this directory!

I am not sure what the gprs config utility from 3eportal.com is supposed to do but my rfcomm.conf file is still blank.

I am really hacked off with this now - so much for 'easy to..' more like 'exasperating to..'

bikeman wrote:

re cap:
my phone can initiate paring but my eee pc is apparently undiscoverable. Advice to delete /var/lib/bluetooth/<BLUETOOTH ADDRESS> hasn't gone anywhere because I dont have this directory!

I am not sure what the gprs config utility from 3eportal.com is supposed to do but my rfcomm.conf file is still blank.

I am really hacked off with this now - so much for 'easy to..' more like 'exasperating to..'

OK, ignoring your rather negative attitude, it sounds like when you installed Bluetooth, you've messed up the default config files. Your /etc/bluetooth/hcid.conf should contain

#
# HCI daemon configuration file.
#

# HCId options
options {
    # Automatically initialize new devices
    autoinit yes;

    # Security Manager mode
    #   none - Security manager disabled
    #   auto - Use local PIN for incoming connections
    #   user - Always ask user for a PIN
    #
    security auto;

    # Pairing mode
    #   none  - Pairing disabled
    #   multi - Allow pairing with already paired devices
    #   once  - Pair once and deny successive attempts
    pairing multi;

    # Default PIN code for incoming connections
    passkey "<EEE PASSKEY>";
}

# Default settings for HCI devices
device {
    # Local device name
    #   %d - device id
    #   %h - host name
    name "%h-%d";

    # Local device class
    class 0x3e0100;

    # Default packet type
    #pkt_type DH1,DM1,HV1;

    # Inquiry and Page scan
    iscan enable; pscan enable;

    # Default link mode
    #   none   - no specific policy 
    #   accept - always accept incoming connections
    #   master - become master on incoming connections,
    #            deny role switch on outgoing connections
    lm accept;

    # Default link policy
    #   none    - no specific policy
    #   rswitch - allow role switch
    #   hold    - allow hold mode
    #   sniff   - allow sniff mode
    #   park    - allow park mode
    lp rswitch,hold,sniff,park;
}

with <EEE PASSKEY> replaced by a numerical code and your /etc/bluetooth/rfcomm.conf should contain

#
# RFCOMM configuration file.
#

rfcomm0 {
#    # Automatically bind the device at startup
    bind yes;
#
#    # Bluetooth address of the device
    device <YOUR PHONES BLUETOOTH ID>;
#
#    # RFCOMM channel for the connection
    channel    <PHONE'S DUN CHANNEL>;
#
#    # Description of the connection
    comment "GPRS Connection";
}

Try creating these and making the /var/lib/bluetooth directory with

sudo mkdir /var/lib/bluetooth

and rebooting. You'll also need /etc/default/bluetooth and /etc/init.d/bluetooth but I'm hoping these are intact from the bluez-utils install.

cjdshaw, in bikeman's defence he has a 2G eeepc and didn't have the bluetooth items that come on a 4G. I've been having him change his repos and by looking at what I have on my 4G, told him to install blue-utilez and libbluetools2. Since I really know nothing about bluetooth, I've probably screwed something up for him. (Picture the blind leading the blind).
If there are other things he needs on his 2G to get this working, he has the p701 repos. I'm not sure if I had him add another one "tuxfamily" or not. If he needs other packages, please tell him what and which repo to make active to obtain the proper tools.

I have now got this working after 2 days of frustration. So that others may benefit I have recorded the steps and edited my original post above.
The thread title 'initiate bluetooth pairing...' obviously doesn't cover the thread subject anymore and should perhaps be changed.
I hope this helps others avoid the problems I experienced. If useful could this be made sticky or put in wiki?

since I have a 4G Eee PC.. do I start at step 3. Pair epc to phone?

I have installed 3egprs and have bluetooth running via dongle from the Eee PC. My mobile phone (Dopod 838 Pro w/ Windows Mobile 6) is connected to the internet and I have turned on internet sharing via bluetooth.

Acording to my phone settings, the AP is 'internet' - so this is what I put in the 3egprs.  When I click the icon in the internet tap - it says that GPRS is running (as I side point, if I click it again, it still says its running.. ie it doesn't turn off). But the browser cannot load any webpages and I can't tell if there's a real connection to the phone - do I need to do something in network? I've got very stuck!

I've got the same problem, I think. My phone can't seem to find the EEEPC any more. Mine's a 4G and my phone's a Sony EricssonW380i. The dongle was working fine when I first tested it before I installed the deb file. They also talked to eachother as far as I could tell when I was setting up the passkeys, but they seem to have fallen out with eachother now! My phone can normally initiate communication with other mobiles but doesn't give me an option to connect with the EEEPC. Bizarre.
I've tried to follow what people have suggested to get it to work, but it really has to be in baby language for me, being a hopeless newbie! (I'm amazed that I managed to download the deb file, so I'm doing well...)

Hope this might help another newbie like me.
I can transfer pictures and music between my eeepc 4G, Xandros. and my Nokia 2630 phone.
Works with an ASUS WL-BTD201M Dongle adapter and also with a "Tiny" style one.
I started by trying "Using Bluetooth peripherals with the Eee" from the EeeUser Wiki and every thing seemed connected.
Then did "Adding Additional Software Repositries" also from the wiki.
Then dowloaded kbluetooth (sudo apt-get install kbluetooth) which I think comes from the xepc repositry.
Then Ctrl alt T to open a console and launch kbluetooth (sudo kbluetooth)
After trial and error realised that the adapter needs to be configured to be discoverable and I had to delete all previous pairings from the phone that had used the same dongle.
Then open a picture from the gallery on the phone and send via bluetooth. Abracadabara - a dialog opens on the eeepc to accept the file.