bluepin overwritten

I've found out that running the Bluetooth Manager application overwrites the changes in /etc/bluetooth/hcid.conf, i.e. the change of the /opt/QtPalmtop/bin/bluepin app to the customized script. So a work around would be just to replace the old bluepin application with the new script.

Global Positioning System (GPS)

I bought a Royaltek RBT-1000 GPS. This is a little (60gr) bluetooth GPS reciever. Connecting it to the Zaurus was really easy (mainly following this ipaq bluetooth gps howto),

1. Turn the GPS and Zaurus on.
2. Insert bluetooth CF. I found out that if the Zaurus was suspended with the bluetooth card inserted I had to restart the CF card with,

   #cardctl eject; cardctl insert

3. Edit /etc/bluetooth/rfcomm.conf,
   
4. Bind the dev (If the bind option is disabled).,

   # rfcomm bind /dev/rfcomm0

5. To see the raw feed,

   # cat /dev/rfcomm0

6. Start gpsd, this daemon gives a simpler interface to the gps feed, qpegps and (I think) roadmap use it to recieve data from the gps.

   #gpsd -f /dev/rfcomm0

   adding the -n switch turns on the bluetooth immidiatly and leaves it on (even if there is no active connection) otherwise gpsd closes the bluetooth after the connection was closed. This is good if I want to recive data using a command line script like (thanx ckuethe),

   #echo "0" | nc localhost 2947

   This will spit out the position and velocity information.
7. Connecting to gpsd using telnet,

   # telnet localhost 2947

   there several commands that are documented in the gpsd manpage.
8. roadmap gps terminal seems to work out of the box,

   # roadgps

   but gives very limited information (only satellite constellation and signal strength).
   

That was the easy part. roadmap started ok only if I start it from the map folder (where usdir.rdm exists) managed to connect to the gps, but it doesn't show the map (which I got from freemap.co.il). qpegps started ok, but couldn't connect to gpsd which makes it useless.

bluetooth...

I'm trying to connect my Motorola RAZR V3 using a bluetooth connection. This is what I found to be semi-successful:
On cellphone side:

1. Enable bluetooth connection.
2. Enable detection.

On the zaurus side:

1. Set the pin number:

# echo "0000" > /etc/bluetooth/pin

2. create the script /usr/bin/bluepincat.sh
   

   #!/bin/sh
   echo -n "PIN:"
   cat /etc/bluetooth/pin
   

   
   
   Alternatively In Bluetooth Manager (under the Settings tab), uncheck "enable authentification" and "enable encryption", and set the Default Passkey to "0000", this seems to work aswell.


3. In /etc/bluetooth/hcid.conf, change security from user to auto.
   also change the PIN helper to pin_helper /usr/bin/bluepincat.sh;
   
   
4. Restart the bluetooth service:
   

   # /etc/init.d/bluetooth stop; /etc/init.d/bluetooth start

Now I can do:

# hcitool inq

and I see the information about the cellphone.

# sdptool browse MAC_ADDRESS

and I see a list of services - with gibberish titles... but list of them nonetheless...

This concludes it, I cannot send files to the cellphone. When I try sending files from the cellphone to the Zaurus I receive a "Service Not Supported" error.