[8125, K-JAM, P4300, MDA Vario General] chinnybob:
It does not work on any channel:

root@desktop:~# sdptool records 00:12:37:83:08:19
Service Name: Audio Video Remote Control Profile
Service RecHandle: 0x10000
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100

Service Name: Voice Gateway
Service RecHandle: 0x10001
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100

Service Name: Voice Gateway
Service RecHandle: 0x10002
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101

Service Name: OBEX Object Push
Service RecHandle: 0x10003
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100

Service Name: Dial-up Networking
Service RecHandle: 0x10004
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100

Service Name: Serial Port
Service RecHandle: 0x10007
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Serial Port" (0x1101)
Version: 0x0100

root@desktop:~# rfcomm bind 0 00:12:37:83:08:19 0
root@desktop:~# picocom /dev/rfcomm0
picocom v1.4

[...]

FATAL: cannot open /dev/rfcomm0: Invalid argument
root@desktop:~# rfcomm release 0
root@desktop:~# rfcomm bind 0 00:12:37:83:08:19 1
root@desktop:~# picocom /dev/rfcomm0
picocom v1.4

[...]

FATAL: cannot open /dev/rfcomm0: Connection reset by peer

root@desktop:~#
root@desktop:~# rfcomm release 0
root@desktop:~# rfcomm bind 0 00:12:37:83:08:19 2
root@desktop:~# picocom /dev/rfcomm0
picocom v1.4

[...]

Terminal ready

Thanks for using picocom
root@desktop:~# rfcomm release 0
root@desktop:~# rfcomm bind 0 00:12:37:83:08:19 3
root@desktop:~# picocom /dev/rfcomm0
picocom v1.4

[...]

FATAL: cannot open /dev/rfcomm0: Connection reset by peer
root@desktop:~# rfcomm release 0
root@desktop:~# rfcomm bind 0 00:12:37:83:08:19 4
root@desktop:~# picocom /dev/rfcomm0
picocom v1.4

[...]

FATAL: cannot open /dev/rfcomm0: Connection reset by peer
root@desktop:~# rfcomm release 0
root@desktop:~# rfcomm bind 0 00:12:37:83:08:19 5
root@desktop:~# picocom /dev/rfcomm0
picocom v1.4

[...]

FATAL: cannot open /dev/rfcomm0: Connection reset by peer
root@desktop:~#

The only channel which results in "terminal ready" is channel two, which, as you can see from sdptool output, is the obex push client (which works.) Obviously it does not respond to AT commands. All other channels return "connection reset by peer."

The latest synce, which supposedly supports WM5, also does not work for me over bluetooth, see this post:

http://sourceforge.net/mailarchive/message.php?msg_id=15415947

(basically, it fails before it can establish an rfcomm connection.)

Needless to say, it all works fine when using windows (tested on VMware using the exact same hardware.)