Stephan has once again come on strong with this, the latest update to his bluetooth dial-up article.

Bluetooth Dial-up for the PMA - Giraffe Style!

OpenPMA brings with it many advantages, one of which is built-in bluetooth support. This makes the entire setup and operation far easier than in previous releases of PMA firmware (Archos and openPMA alike). If you are not yet using openPMA 0.2, you will need to follow the previous guide. Due to the improvements it is recommended that you upgrade, however. See the related articles (below) for more information on both these topics.

Once again, you will need to be running openPMA 0.2 (Giraffe) to use the following instructions.

SOFTWARE NEEDED

1. Install: Tree!Explorer QT  (if you haven't done so already)
   via link: "Getting Around the File Limitations with Tree!Explorer QT"

HARDWARE NEEDED

• Have your Bluetooth enabled mobile phone in hand
• Switch it on, then
• ENABLE bluetooth on the phone (= set to ON)
• Get your Bluetooth USB dongle (you have to buy it first if you haven't done so, see link below)
  If you need a 10 or 100 meter device it's up to you, but be assured that you don't like to run 100m just to reach your phone. So a 10m device is more secure and convenient at the moment - unless you want to hack your neighbor's phone or BT (bluetooth) network - which I don't recommend.
  
  
• Connect your USB bluetooth dongle to the PMA via the USB host cable. You can use a USB HUB with a keyboard and the USB BT dongle connected at the same time if you like.
  
  
  Author's Note:
  BTW, I use a Nokia 6310i phone and a Belkin FBT013 USB dongle here ... (Belkin link here - it's a  Bluetooth standard v2.0 +EDR device:
  http://catalog.belkin.com/IWCatProductPage.process?Merchant_Id=&Section_Id=200583&pcount=&Product_Id=273109

CONFIGURE DEVICES

1. Create new network connection of type "Dial-Up (Bluetooth)"
   
   
2. Tab (Account):
   Name (use a good name here), Username, Password. Phone depends on your network carrier (= mobile phone connection) e.g. (for an expensive German Vodaphone mobile access point)
   • Name: 6310i D2 BT
   • User: d2
   • Password: d2
   • Number: +49172229000
     
     
3. Tab (Modem):
• BT Device: dev/rfcomm0
• Init String: ATZ
  (you might change the init string here in a second step, for example to use HSCSD mode on the Nokia phone use:
  at+cbst=81,0,1;+chsn=6,3,0,8 here)
  
• Speed: 57600  (you can try 115200, but it did not work in my case)
• Hardware flow control: OFF (no checkmark)
• Flow Control: 30 sec
  
  
  

PREPARATION

1. Delete all files under /opt/Qtopia/etc/bluetooth, just to make sure you're not working with old, obsolete settings.
   
   
2. It is recommended to perform another install of openPMA 0.2. This is just to ensure that the bluetooth files needed are correct and intact. No files or settings will be lost during this process.
   
   Shut down the PMA, connect to USB, boot, copy aimage.img & openpma.img once again to "/System" folder. Disconnect safely from USB, the let PMA boot and allow the 2nd partition to be updated (again).
   
   
3. Using Tree!Explorer QT, copy pin and bluepin files from "/opt/Qtopia/etc/bluetooth" to "/media". Rename them to pin.txt and bluepin.txt.
   
   
4. Edit the ("1234") pin number found inside BOTH files to the same numeric number YOU need for YOUR device (you can use the PMA's editor for this). Some BT phones don't need a fixed PIN, so you use can whatever you like. Some BT modems require a fixed PIN, so you will have to change it here. Rename both files back to pin and bluepin. Copy them back to the "/opt/Qtopia/etc/bluetooth" folder overwriting the old files.
   
   
5. Create a bluetooth connection via the Settings > Network applet with the appropriate values as mentioned in "Configure devices" section, above.
   
   I would recommend also (as previously) no hardware flow control, flow control to 30 sec. Leave the "Phone adress" entry at the Phone tab blank for the moment, only enter your pin as described. Connect your USB BT stick to the USB host cable and plug it into the PMA. At the Daemon tab, press "Restart Bluetooth" button. It might take a few seconds for this to complete.
   
   
6. Use the terminal, and enter "sdptool browse".
   
   response is (example):
   Browsing 00:10:20:0A:0B:0C
   Service Name: Fax
   ...
   Service Name: OBEX Object Push
   ...
   Service-Name: Dial-up Networking
   Service RecHandle: 0x1002
   ...
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
   Channel: 1
   Language Base Attr List:
   Profile Descriptor List:
   "Dialup Noetworking" (0x1103)
   Version: 0x0100
   Service Name: Nokia PC Suite
   ...
   [plus more or less Service names]
   
   
   The second line shows "Browsing xx:yy:zz:aa:bb". Make sure that "Service-Name: Dial-up Networking" has channel 1 shown. xx:yy:zz:aa:bb is the address of your BT device (phone) which to be entered in the network applet under Phone address. Do so.
   
   
7. Enter "rfcomm" at the terminal. Response shall show:
   
   rfcomm0: xx:yy:zz:aa:bb channel 1 clean
   
   So you know everything's running.
   
   
8. In the Daemon tab for your BT connection, you might have to check "BT at startup". Try if it works with this option unchecked, as it might save some power not running BT all the time. Click OK now for your BT connection.
   
   
9. Connect to your BT phone via the dial-up manager in the taskbar. You will be asked to enter the PIN on the phone the first time you connect. Later on (and depending on your device), it may be possible that the phone will store the pin and won't ask again.

Notes:
Always disconnect the connection via the dial-up symbol in the taskbar first! If you disconnect the connection thru the phone first, the dial-up (BT) symbol (connect) might hang and you have to end it manually from the phone's side - or (worst case) you have to reboot the PMA to stop it.

If you change between two different BT modems, you will have to press the "Restart Bluetooth" button in Daemon tab first.

Don't ask if different PIN entries for different BT modems will work. I haven't tried it, so it's up to you to experiment!

Report it and other findings here ...