Socket CF Bluetooth Rev 2.5G

[ccrandal]

Wanna trade cards?
Would using Affix help?  Sounds like it might have a better UI as well.

[albertr]

You can always get an Ambicom BT2000E card (that uses a different driver) from Amazon.com for around $53 or so. Or maybe even less if you shop around. The recent version of bt2000e_cs driver should be able to survive suspend/resume without need of additional steps, or at least I hope so. However, the old driver in tumnus\' ipk does require apm scripts to reset the card after resume.

If you really wanna trade, I have an old Socket card (revision \"F\" that is 1.1 - compliant and doesn\'t stick out too). It works fine, but requires a reset after resume with BlueZ. I believe it survives suspend just fine with Affix (or at least it has with old Affix 1.2.6).

As far as GUI goes, Affix has a Connector Qtopia application that helps to browse and establish rfcomm connection to remote device (kick off pppd, etc), but unfortunately afaik development sorta stopped and no new versions were produced for a while. You probably don\'t want to stick with software that is no longer actively supported and updated...
-albertr

[maslovsky]

You don\'t need to install the applets - they are already included in the 1.20 ROM. Just go to the Network Setup application and create a connection to your cell phone (using dialup applet) or PC with bluetooth (using PAN applet). You don\'t have to edit any conf files - frcomm.conf is populated when you create a dialup connection uusing the applet.

[ccrandal]

Ya, after messing around I did realize that those applets were already there.  I thought the applets I installed had the ability to scan for bluetooth devices and list all those that were discovered.

Actually, just running the applet did not create the appropriate entry in the rfcomm.conf file.  Only after installing sudo, susp-resume, and susp-resume-bluez did it work... of course, as I stated earlier, the susp-resume messed up my ability to power down.

Hopefully, since I\'m pretending to be sick today, I\'ll have time to reflash the ROM and start fresh again.  If I can get the Socket CF rev2.5 to work, I\'ll post my procedure in case anyone else could benefit.  Otherwise, I\'ll have to hunt for another card.

Thanks,
Curt

[maslovsky]

Actually, just running the applet did not create the appropriate entry in the rfcomm.conf file.

This is strange. Did you actualy created a new connection to the phone?
Did it fnid your phone when you clicked Search button?

[ccrandal]

Well, when I was finally able to get info from sdptool, it did display my phone\'s MAC.  So, somehow it did find it.  However, I did not see any option to search when creating a bluetooth-dialup connection in the applet.  I did see something in the bluetooth-pan applet, but the search button never found anything and would tell me to search manually.

I did open the terminal and did a `dund --search 30`... that was the only set of switches and args that caused my phone to respond (the bluetooth icon briefly showed a connection.  I need to do more research on how to properly use the dund command as there\'s no man page available (no man util installed right now I believe).

Thanks,
Curt

[ccrandal]

OK, before I bricked my Z, I did locate the BT DUN Search widget in the Bluetooth Dialup Applet, but when hitting the search button it quickly returned saying it could not locate any devices with a DUN profile.

Seems like I need susp-resume and susp-resume-bluez installed to get this to work, however, under this ROM it seems to mess up my ability to turn the Z on and off (and has now bricked the device... I\'m letting it sit for a few hours w/o a battery or AC to see if that clears up that problem).

I\'ll play some more if I can get the Z running again, but it\'s looking like I either need a different ROM or a different BT card.

Thanks,
Curt

[ccrandal]

I got the Z back up and running after letting it sit w/o power for an hour or so.  While I was waiting, I noticed I did not try one thing... adding the `killall hciattach` and `cardctl eject` to the /etc/apm.d/bluetooth file.  Now, my bluetooth card is being recognized, and I was able to search for my phone.

So, I\'m all set except for one small detail.... my SE T610 phone wants a passkey.  The bluetooth applet did request that I create a passkey, so I assume there\'s a default passkey.  I tried 0000, 000000, 0000000, 9999, 999999, 99999999, 1111, etc., but none work.  Did a quick search in the forum and didn\'t find anything... anyone here know the correct passkey to use?

Thanks
Curt

[ccrandal]

I think I spent too much time on this last night and needed to come at this again fresh.  I found where the passkey is... kept reading over it in the bluetooth how-to and it just didn\'t register.

Curt

[maslovsky]

ccrandal, sorry to put you in all this mess...  I realy appriciate your efforts. I will ask tumnus what he did in his packages for the revision G cards to work and will include those fixes into the next ROM version.

BTW, the default pin code is 1234 you did not try that one...

[ccrandal]

No need to apologize.  I had a SL-5000D, so I knew when diving back in with another Zaurus this was going to be a bit of a project.  The Cacko ROM is pretty dang good!  Thanks for your efforts and let me know how I can be of assistance to help.

Yep, I got the right pin... I just read that how-to too many times and kept skipping over that little nugget of info.

To recap, in case anyone else is having the same issues I just went through, to get the Socket CF rev2.5G card to work under the Cacko Qt 1.20 ROM perform these procedures:

1.) Install the bluez_csr_serial_01.ipk package (link on the bluetooth how-to page)
2.) Install sudo (do not install susp-resume or susp-resume-bluez)
3.) Go to Qkonsole and su to root
4.) vi /etc/pcmcia/bluetooth.conf and comment out the 3 lines related to the Socket CF rev2.5G card
5.) vi /etc/apm.d/bluetooth and add the lines \"killall hciattach\" and \"cardctl eject\" to the suspend case block
6.) Using the applet or cmd line, eject the card and then execute `cardctl resume` at the cmd line
7.) Create a Bluetooth Dialup connection in the network applet
8.) In the applet, do a search for your phone (haven\'t gotten PAN to work yet, though... I\'ll keep trying)
9.) Go back to Qkonsole and execute `sdptool browse` and `hciconfig`... both should be giving valid output
10.) Be patient (unlike me), carefully read this thread and the bluetooth how-to... if you can\'t get it to work, go to sleep and try again in the morning.

Thanks all for the help!
Curt

[ccrandal]

BTW, thanks everyone for being patient with me.  I\'m an angry IT professional and quickly lose patience when things don\'t work right the first time or two... kinda like road rage behind a monitor.
Now that I\'ve got my BT connection working, I\'m really loving the Cacko Qt ROM a lot.  Kudos to maslovsky and tumnus and everyone else involved for their hardwork.

Curt

[maslovsky]

thanks Curt, I now seem to know what needs to be fixed in the ROM to make it work with Socket G cards out of the box.
I\'m planning on new ROM builds next week - would you like to beta test them to make sure Socket G  cards are indded handled properly?

Regarding PAN - first double check that it\'s configured properly on the PC end. If it\'s set up then \" sdptool search NAP\" should find your PC as well as the applet.

[ccrandal]

I would be more than happy to beta test the new ROM, just let me know when it\'s ready.

I think my Powerbook should be setup properly.  I actually tried to pair from the Powerbook side, but it failed... can\'t remember the error message.  But, the Powerbook did find the device \"zaurus\".  I need to check out the Mac forums here to see if there\'s something a little special I need to do.

One thing I would like to work on are the WiFi and Bluetooth applets in the network application.  I really like how Palm detects and sets up bluetooth devices and WiFi access points.  So, after I get a couple of other projects out of the way, I\'d like to give that a try.

Thanks
Curt

[GMan]

Hi,

Well I just tried to get my Socket BT card to connect (I think it\'s RevG - I bought it from someone who told me it was - is there a way I can tell)?

ccrandal, I followed your instructions (and after a reboot) everything seems to work (at least I can do hcicontrol ans sdptool now).  I am in the process of getting a BT phone so I was trying to get PAN to work.  My WinXP machine can detect my Z (shows up a \"Laptop\") when I hit the connect in the applet and it prompts me for a PIN which I typed in.  After a short while my XP machine returns with \"Error in pairing with device Laptop\". Reason: Timeout occurred during pairing.  I even tried using pand directly from the instructions at http://www.jens-koenen.de/index.html but same error.  The sdptool search NAP does find my PC as a NAP.

I am running Cacko 1.2 with the sudo and bluez-serial drivers listed previously in this post.  When I commented out the settings in the bluetooth.conf file and insert my CF card, I get a generic Serial or modem type whereas before I got Socket Bluetooth.  I am using a Kensington USB BT adapter (on sale at Best Buy this week) on my PC.  At the moment I don\'t have any other BT devices to check either my PC or Z against.

Any suggestions?

Thanks.
-Gary