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?

Did you make sure Bluetooth stayed "turned on" throughout? Some Smartphones turn off Bluetooth unless "discoverable" or a program or "handsfree mode" turns it on.

I'm sure the bluetooth was on. It seems asthough they connect for a second then immediately disconnect. The Cingular 2125 uses the WM5 OS. Maybe the ICD isn't compatible with this OS.

My i-mate SP5m uses Windows Mobile 5 too. The procedure I wrote worked exactly as written.

Is it possible that your carrier disabled Bluetooth DUN abilities in your phone? Can you use Bluetooth for file transfer and synchronization? Some carriers (Notoriously Verizon) limit Bluetooth to "Headset/Handsfree" mode only.

Both my laptop and Dell Axim x50v can connect via bluetooth and use DUN. I am completely out of ideas. Any other suggestions?

tried the fix and works great! i am using it with an mpx220 and am greatful for everones input. been waiting for this since day one...

Finally got it to work!!!
 

Thanks to everyone for their help. Now I can use the 770 anywhere I have a signal on my phone. Thanks again!!

airbillion: What fixed it so I can add it to the HOWTO notes?

3.2005.51-13

What worked for me!
 

I set up my own connection to Cingular throught the mobile operator wizard. The wizard had the Cingular internet connection dialing *99***#1 which caused my phone to reject the attempt. Instead, I dialed *99# in the profile I created and it worked right away!

I went and bought an MDA so that i could take advantage of EDGE but cannot connect correctly with the new icd installed. don't know if it worked with the old icd, does anyone know. i can pair without a problem, but when i try to connect it fails and will not let me go online. also, unde the phone details, it says supports DUN but under cellular type, it says none. Looks like it thinks it's only a PPC.

phatman81: Are you able to use bluetooth DUN with a laptop or other machine? I'd test your service provider's ability to get you online first to make sure it's not a phone/service issue.

I followed the same procedure (from Thoughtfix Site) but when i try to pair my i-mate jam(wm2003) phone with nokia 770 , the jam accepts the pairing but nokia prompts me with the following message:"selected phone does not have services that can be used. Select another phone".

Any ideas of why do i get this message?

Thank you.

Sorry for the delay in response, started new job and an finally getting time to get back to doing things outside of work, but last time i tried, my MDA still would not connect, giving me the same error as menelaos. I'm at work now, but do not have my tablet with me, so i can't try now, but will attemp if anyone has had success with an MDA or other PPC (mobile 5.0) device.

P.S. To answer your question, no i do not have a data issue with my provider... i actually work for them now, so i know right away if there is an outage.

Not fixed in 5.2006.13-7
 

The 5.2006.13-7 software update apparently does not have the MPX220 aka Windows Smartphone fix that was discussed on maemo.org.

Started to use my 770 again (brought it to work w/ me) and now i can get online with my MDA. Don't know what i did different. All the settings were left alone. The only problem i've had were random disconnects. i entered the proxy settings and since then it has been smooth sailing. Now if only the media player could support an ORB.com stream, i would have a nice size portable TV with me at all times! Anyone got any ideas? or any other media player suggestions?

Re: Bluetooth DUN to Windows Mobile
 

I'm under the impression that there might be an easier fix than updating the ICD on the 770... See my new thread here:

http://www.internettablettalk.com/fo...windows+mobile

I'd like to know if anyone has tried editing the WM5 registry to fix this dumb DUN problem.