- the Z recognizes it when the card is inserted (socket rev 2.5).

- bluetooth - ppp profile cannot get bluetooth settings from it (network app)

- commandline sdptool browse returns "inquiry failed". A bluetooth phone was available at the time.

I'm confused about what I am seeing because the rev K is supposed to be cacko 1.23 friendly. The belkin card responded much better. Am I doing something wrong?

I'm really beginning to think cardmgr is not so stable. I ended up rebooting the Z and now the network config has no problem seeing the socket bluetooth. Before I did this I hciconfig gave no info and dmesg said very little.

There were some other stuff that I did, but they are irrelevant now that it's set up. I'm now waiting for the phone to be activated and then it should be mobile surfing bliss (except in the subways).

sometimes you need to reinsert the card....I have a rev K with no issues, stock Cacko Rom

thanks bam, but I tried re-inserting multiple times. The Belkin card was like that too. The frustrating part is that the belkin worked the whole time the socket didn't.

Why do you use the Socket one and not the belkin one?
I have a Nokia DTL-4 and have the problem that always I try to connect with the Nokia 6310 phone, after entering the PIN on the phone the Zaurus "rfcomm" command line application reports "Resource temporarily not available".

Could this be a problem with the card, i.e. solvable with another card? Or is there something wrong in my system?

daniel

the belkin card is much bigger in every dimension. It wouldn't fit in the piel frama case with all my other stuff. Not only is the socket able to fit in the piel frama, but I can also just leave it in the cf slot as it does not protrude.

I'm still waiting for sprint to activate my phone to test the dun with the socket card. The belkin card worked with my cingular moto phone no problem.