Bluetooth problems galore with P800 / Thinkpad

[CoffeeKid]

Hi Folks. I got my P800 this morning, and after (still not) getting over the "wow" factor, I've had nothing but frustration trying to get bluetooth working with my ThinkPad X30 (WinXP Pro, bluetooth built in, using IBM's bluetooth software). I've installed the latest SE desktop software.

I do get the devices "seeing" each other. When I tried to pair the two from the thinkpad, the application hung, but when I rebooted and ran "My Bluetooth Places" again, the P800 was there, and was listed as paired.

I cannot get the serial port connection to work: when I try, a dialog box pops up after 10 seconds or so, saying "The Bluetooth Serial Port Connection Failed: The Remote device closed the connection".

I haven't got a clue how to get GPRS to work with my notebook through bluetooth, which is the primary reason why I bought this phone - to have wireless, gprs access to the internet, not only on the P800, but on my notebook (thru the bluetooth connection).

Please, someone help me diagnose and fix these problems. Before you say "read the manual", the manual I got is in Swedish :(

Thanks in advance from a very frustrated bluetooth P800 owner / nonuser.

Mark

I believe this is a problem with the Bluetooth stack that IBM are using (its an older version)

Do a search on bluetooth stack IBM and see what happens.

There are some great resources on Bluetooth out there, get goggling and find them

ta ta

[klarsen]

The problem is your thinkpad.. I have the same problems - search for Widcomm in the 7650 forum and you will get a lot of "help" on how to get the Widcomm stack to work better.

Widcomm stack has a know problem in the Thinkpad drivers - and other OEMs has corrected the problems - but IBM has not.

Post your request on the IBM Support Forum...

best

Kasper

[CoffeeKid]

Originally Posted by klarsen

The problem is your thinkpad.. I have the same problems - search for Widcomm in the 7650 forum and you will get a lot of "help" on how to get the Widcomm stack to work better.

Widcomm stack has a know problem in the Thinkpad drivers - and other OEMs has corrected the problems - but IBM has not.

Post your request on the IBM Support Forum...

best

Kasper

Thanks for the quick help, folks! I'm a complete and utter bluetooth newbie, so even terms like "stack" make my eyes go cross eyed, but I'll stay up all night if I have to, searching for problems with the widcomm stack on the 7650.

Mark

[klarsen]

stack = software for network communications (in short)

I have "patched" my widcomm to get it "semi-working" but you can read about that in the 7650 forum (The P800 and 7650 has the same problems - since the mRouter software is the software is the software showing the compatability problem)

But new versions of the software from Widcomm has solved the problems for other users.. But IBM is sooooo slow. ;-(

best

Kaz

[CoffeeKid]

Originally Posted by klarsen

But new versions of the software from Widcomm has solved the problems for other users.. But IBM is sooooo slow. ;-(
Kaz

Where should I write to IBM about this issue, and better yet, what should I be saying / asking for? I'm willing to write, and I know at least a half dozen other Thinkpad users in our company and within our clients I could get to write as well.

I'm actually surprised at IBM over this - normally they are zippy fast bringing out new drivers, new patches for their thinkpads.

Mark

[CoffeeKid]

Originally Posted by klarsen

stack = software for network communications (in short)

I have "patched" my widcomm to get it "semi-working" but you can read about that in the 7650 forum (The P800 and 7650 has the same problems - since the mRouter software is the software is the software showing the compatability problem)

But new versions of the software from Widcomm has solved the problems for other users.. But IBM is sooooo slow. ;-(

best

Kaz

Hi Kaz.

I spent many hours pouring over the 7650 forums looking for the solution (or the partial patch), but I cannot figure it out.

Would you be able to give me a bit more info about how you found a workaround?

Thanks

Mark