Anyone got these two working together. I get the n800 working with a SE P910i and a Razr, but not a WM5 device. Tried two, the MIO 710 and the 02-XPAs. Problem seems to be that I cant get the the N800 to see the devices as phones, just PDA's.

Any ideas guys.

Cheers

Tim

As I recall, for devices that id's as PDAs you have to pair manually first, but you'll find the details in the forum. Search for e.g. 'TyTN', that's one thread I remember.

I just managed to get my N800 to pair with my Tmobile MDA (HTC Wizard).

I was running a custom ROM before and could see DUN as a service but it would never connect through the phone. Then I installed the Tmobile WM5 ROM from the middle of last year (most current to them) and no luck, same issue connecting.

After that, I put the WM6 ROM on and found that they dropped DUN for BT PAN which the N800 doesn't (directly) support. So finally I went back to the TMO WM5 ROM but with a twist.

When you run a ROM upgrade on your phone, it first flashes the phone, then reboots, and finally it runs a script that customizes your phone (skins, plugins, ringtones, network settings, etc). You can break the customization process if you soft-reset before it starts installing files. This also saves a ton of space on the device since junk you probably won't use isn't installed.

Obviously if I'm carrying on about this procedure, you can imagine that it worked. After setting up my GPRS settings and making sure my phone got online, I turned on BT, paired the phone and N800, and set up a standard Packet Data connection and it worked right away!

This isn't really the forum to discuss Windows Mobile tweaking but if you are missing some important customization .CAB files, you can find them by using Total Commander and manually inputting the path "\EXTERNAL_ROM\" and that should get you to where you can install the .CABs by clicking them individually. I usually copy them out of there to an easier to navigate to directory.

That was very long winded, sorry. It boils down to the DUN profile in WM5 AKU2.2 working on my MDA as long as the T-Mobile tweaks and junk aren't run. So that should imply that ANY WM5 PPC phone ought to work as well if the customizing ROMs aren't loaded after a reflash.

I mentioned this in another thread, but it's important, so I'll post it here too.

The DUN profile was removed in WM5 AKU3, and replaced with PAN. Just as you described in WM6.

So newer WM5 devices, such as the T-Mobile Dash, will NOT work with the N800 without a whole lot of finagling in Xterm.

WOW, looks like a lot of messing for not much gain.

I have a SE P910i sitting idle and that works straight off the mark, so I might just use that if im on a road trip with the N800. Lucky for me we have WIFI at work.

Thanks for the help guys.

Tim

Have any of you tried the methods described in the following wiki entries? I've no idea if they work, they may be out of date and they may or may not work with the N800:

http://maemo.org/maemowiki/HOWTO-BluetoothNetworking
http://maemo.org/maemowiki/Bluetooth...nectionManager

Unless I'm mistaken, the BT PAN client for WM5 AKU3/WM6 needs to be started and stopped manually so it's not a very elegant solution.

It is unfortunate that MS decided to abandon BT DUN in favor of BT PAN. I can connect via BT DUN with my phone in my pocket instead of having to take it out, turn on the PAN service, and then remember to shut it off afterwards. Plus there are a number of devices (PDAs, PNAs, etc) that need the DUN profile to work.

I think what I'm getting at is Microsoft's Bluetooth stack on Windows Mobile is a worthless pile of garbage and has only gotten worse as time has progressed.