How to install bluetooth on Asus Eee PC

After countless nights and days of figuring out what’s going wrong with my Asus Eee PC, bluetooth dongle, and 3G phone, I have finally set it up successfully. Thanks to all the forums I’ve gone through. I know they all do not have complete and step by step configuration details but they are my only and primary source.

I’m gonna list all the issues I had to let you see if you also have gone through them.

  1. Bluetooth functions well but cannot connect to phone (wrong passkey)
  2. Asus Eee PC detects the phone but the phone cannot see the Asus Eee PC (pairing issue)
    Can't connect RFCOMM socket: Connection refused
  3. Pairing was successful but wvdial says Modem not responding.
  4. a lot more, can’t name them all, builds from one another.

Now here’s the simpiest steps on “how to install / configure bluetooth modem phone with Asus Eee PC”.


  • bluetooth dongle
  • bluetooth utility (i used bluez-utilz) here’s the steps i followed
  • rfcomm, hcid, (i think these come with bluez-utils)
  • wvdial
  • root access
  • i don’t think I forgot something here…

Ok, let’s start installing your bluetooth device and phone modem on your Asus Eee Pc.

  1. Given that you have all the requirements above, connect your bluetooth dongle to your asus eee
  2. Make sure it’s running. On your console, type: hciconfig
    My Results:
    hci0: Type: USB
    BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
    RX bytes:1056115 acl:2996 sco:0 events:2802 errors:0
    TX bytes:225742 acl:2361 sco:0 commands:236 errors:0

    In case your result says DOWN, start your bluetooth device by doing any of the following:
    hciconfig up (where dev is hci0 in my case)
    /etc/init.d/bluetooth restart
  3. Turn on your phone’s bluetooth and scan using sdptool
    sdptool browse
    This command will display all the services available from your phone. Look for the service related to “Dial up Networking”
    My results:
    Service Name: Dial-Up Networking
    Service RecHandle: 0x10002
    Service Class ID List:
    "Dialup Networking" (0x1103)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 2
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Dialup Networking" (0x1103)
    Version: 0x0100

    Take note of the channel for it’s very important.

  4. Add an rfcomm device
    kwrite /etc/bluetooth/rfcomm.conf
    Paste the following:
    rfcomm0 {
    bind yes;
    device ;
    channel 2;
    comment "Dial-up networking";
  5. Create a wvdial entry for your phone.
    My entry:
    [Dialer NBT]
    Init1 = ATZ
    Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Init3 = AT+CGDCONT=1,"IP","
    Modem Type = USB Modem
    ISDN = 0
    Phone = *99#
    New PPPD = yes
    Modem = /dev/rfcomm0 #rfcomm entry
    Username = yourusername
    Password = yourpassword
    Baud = 460800
    Idle Seconds = 3000
    Auto DNS = 1
    Stupid Mode = 1
    Compuserve = 0
    Baud = 460800
    Dial Command = ATD
    Ask Password = 0
    FlowControl = NOFLOW
  6. Configure hcid.conf to automatically accept connection from your phone.
    My hcid.conf
    # 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 "0000";
    # 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, master;
    discovto 0;
    # 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;

  7. To make sure all config settings are applied, I advise to restart your bluetooth once more.
  8. Start your your internet connection.
    wvdial In my case, NBT
  9. Enjoy.

For any issues you might encounter, just leave a comment on this post and I will try my best to help you resolve it. Thanks for the visit.

You may also like...

14 Responses

  1. Martin says:

    I tried following your instructions but my Eee would not allow me to save the rfcomm.conf from section 4.

  2. Martin, I assume you’re having “access denied” warning…

    You have to create rfcomm as root. Try this…

    sudo kwrite /etc/bluetooth/rfcomm.conf

    If it’s not it, please let me know the problem you’re having. Thanks.

  3. Martin Higgins - MM0DUN says:

    Hi thanks – yes it was an access rights issue. Resolved it now.

    Did get it to work once but now it shows on phone as bluetooth connected and then disconnects after 10 seconds…dunno what happened….any tips? Usina Nokia N95 S60 3rd.

    Same phone works great on my Acer PC via bluetooth for DUN.


  4. Martin Higgins - MM0DUN says:

    Also meant to say that I have used the GUI version to start stop and have modified the files behind the button to do what the files above do.

    Bluetooth channel is correct.

  5. Martin Higgins - MM0DUN says:

    Also cannot find any “bluez-utils” to give me a bluetooth applet. This all new to me as I am Windows and Novell IT here and big learning curve. lol Any help appreciated. Thanks.

  6. Martin Higgins - MM0DUN says:

    I did miss out step 5 cause not certail what you meant here, as create a WVDIAL.conf file or use a until to create or what.

  7. Martin Higgins says:


    Deleted the bluetooth pairing with the Eee on my phone and then ran through the GPRS Icon on the Eee in the SETTINGS Tab and then paired following the Eee on-screen instructions and lol it worked. Sometimes phone does not respond but if the phone is powered off and on again the bluetooth GPRS works. Just watch out for the DUN channel on the phone changing as this would appear to be the norm on the Nokia N95. Keep a copy of the instructions for editing the file on the Eee to adapt for this.

    Thanks to all and this site for all the Eee tips…

  8. You did it right! Congratulations.

  9. Joni says:

    I can’t seem to pair my EEE pc with my phone. the laptop can find my phone. but each time, it asks for my eee pc bluetooth password. i don’t know what it is because for starter, i didn’t set up one. can you help?

  10. Dave says:

    There has GOT to be an easier way. Should be, plug in dongle, drivers load automatically, then, your headset pairs with the netbook through the dongle. There should be nothing more to it. Not that the above is reality, but, that’s how simple it should be.

  11. Great points…I would note that as someone who really doesn’t comment to blogs much (in fact, this may be my first post), I don’t think the term “lurker” is very becoming to a non-posting reader. It’s not your fault in the least , but perhaps the blogosphere could come up with a better, non-creepy name for the 90% of us that enjoy just reading the posts.

  12. appreciate it for providing valuable information on the topic. I am a fan to your website. Keep up monetary management job.

  13. I was suggested this web site by my cousin. I am not sure whether this post is written by him as no one else know such detailed about my problem. You’re wonderful! I will definitely digg it and personally recommend to my friends. I have bookmarked it in my web and social networks. TY!

  1. January 21, 2008

    […] to installe bluetooth GPRS on Asus Eee PC. I have tried it already but failed. After I successfully configured it manually, it worked as […]

Leave a Reply

%d bloggers like this: