Hi,

I have been searching the forums all night, and cannot find an answer.

I followed the instruction to set up my Bluetooth CF with my T630 as described in

http://www.zaurususergroup.com/modules.php...ename=Bluetooth

and

shirtpocket site

Everything is ok until I start DUN in Networks, it seems that Zaurus is trying to initiate the T630, but the BT CF just does not light up at all + there is no indication at all from the phone that things are happening.

I then tried

dund -c 00:0E:XX:XX:7F:XX
It seems to work, lights on BT CF and T630 blinks ...

sdptool browse
it works.

hciconfig
It works ...

Are there any commandline that test the DUN interface ?
How can I test /dev/rfcomm0 is working ?

Need help desperately ...

Thanks.

AL

Hi,

Sounds like you have made all the changes needed ...

Don't have a T630, but do have a T610 and that works fine with DUN and Zaurus, so can't see any reason why T630 should be any different.

Have you checked the basics. Switch off/restart both Phone and Zaurus (reboot) jut in case something has got stuck.

I know sometimes, the bluetooth connection would misbehave if you had trouble with it already.

Also, might be worth deleting the Zaurus Pairing on the phone if you already have one and temporarily unhiding the phone.

Sorry I can't give more specific help...

Zuber

Did you set up a CID for your BT connection on the T630? When I had a T610, this was the one thing I missed and it caused all sorts of problems connecting.

You say the BT CF is lighting up. Could it be that you have a bad BT card?

Guys,

I need your help. I'm trying to do DUNthrough my treo 650 with a socket revision h. When i do pppdialer it says :

failed to open /dev/rfcomm0: no such device.

I am sure the bluetooth is working because when i run hciconfig i get information and a mac address for the card. Also, I was able to pair it with the treo from the treos end. Any ideas would be welcome. Thanks!!!

p.s. although it is strange that when i do:

sdptool browse i only get the mac address i dont get more information like im supposed to, like the channel for example.

Have you edited /etc/bluetooth/rfcomm.conf as per the Bluetooth Howto and restarted bluetooth? It sounds like you are missing this.

Hi,



I had trouble with 'sdptool browse' showing nothing, so I tried 'sdptool search' instead, and that worked.

E.g. sdptool search DUN 12:34:56:78:90

I have found that phones often have broken implementations of the SDP profile, so sometimes it works sometimes it doesn't and there are also several other ways of scanning a device as alexl shows.

Just to be confusing, different bluetooth commandline tools have different sub-commands (e.g. browse, scan, search). To further compound the error, sdptools DOESNT actually tell you the sub-command was invalid, so you don't even realise what's gone wrong.

As said above, try using "hcitool scan" (I think) to see if the Z can find the phone. Then try "hcitool cc xx:xx..." and make a bluetooth connection to the phone. If that works, you know the underlying bluetooth channel works.

Check that /dev/rfcomm* exists: "ls -la /dev/rfcomm*" and make the devices if missing.

Paul