Bluetooth DUN to Windows Mobile
 

I am pleased with my new Smartphone (the i-mate sp5m) but am having problems with the bluetooth dial-up networking. It worked fine on my RAZR.

I tested everything (you all know how thorough I am in testing) and it seems it may be due to the old icd version mentioned on the wiki:

http://maemo.org/maemowiki/BluetoothDUN

Pairing works, but the phone doesn't offer OBEX. When attempting to connect fo either "packet data" or "data call" I get "Connection to phone failed. Try again?"

I started the sdpd properly of course.

icd is version 0.93.1

Is there an updated icd somewhere?

*bump*
Does anyone know anything about this icd thing?

Use this ICD - http://qapf.shackspace.com/icd, it's a yet-unreleased version that should solve your issue :)

All windows mobile devices running the bluetooth stack microsoft provides have the same issue. The problem is the phone directly after pairing with something runs a service discovery on it. The N770 does not respond to service discovery requests by default because it runs no bluetooth services.

This fix to this half of the problem is that the user must gain root and issue the command using xterm, as root, "sdpd" to turn on the service discovery protocal daemon so the phone can see that the n770 runs no services and it will correctly pair. SDPD will only run until you reboot the phone, but you don't need it beyond getting the two devices paired.

The second half of the problem is the icd binary shipping in the n770 today contains a PPP chatscript too complex for the simple minded Windows Smartphone. This fix gets more complex.

To fix this problem you have to download a binary from Http://qapf.shackspace.com/icd which a nokia dev provided to me to fix this issue, and you have to overwrite the icd binary on the device with this one. To do this you have to first copy the binary to your device, either via memory card or other methods, then you need to run ps -Aux | grep icd to find the path the current icd binary exists at. After you know where you need to copy your new icd binary to, you need to issue a stop command to osso-ic via its init.d script so the service will stop gracefully. Once that is done you copy the new binary over the old one, and then start the osso-ic service via its init.d script.

I have done these steps myself and it works for the devices. At that point you can make connections via the normal gui tools and dial out to your wireless data provider.

Thanks Qapf.
Everyone else: Qapf and I discussed this over IM briefly.
I take all this information and write a complete HOWTO and include a shell script that walks the user through the installation.

The workaround using Qapf's instructions are posted:
http://thoughtfix.blogspot.com/2006/...h-windows.html

I also took the liberty of fixing the information in the Maemo wiki, fixing Qapf's link, and adding my link in the maemo wiki.

http://maemo.org/maemowiki/BluetoothDUN

Hope that helps!

Great. Did this - still no pairing and now the wi-fi won't work

Fixed it by switching back to old icd. Aparrently the new one doesn't support wi-fi.

Whoa jstiel! What firmware were you running? I've never heard of that happening. My attempt worked on the -51 firmware.

No luck with new icd and Cingular 2125!
 

I paired the devices for the first time after following the directions on the ToughtFix site, but still cannot get them to connect to the internet. It almost works...on the Cingular 2125 the signal meter quickly flashes to signify they are connected but then it drops the pairing immediately. Anyone have any ideas?