Selecting channel for SyncMLClient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multisync (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
Description: Ubuntu 9.04
Release: 9.04 - Jaunty 64bit
I purchased a new Nokia 5800 - nice phone - and set up Bluetooth - worked fine for a while (1 Day) and then half the time I had to force a connect FROM the phone to the PC.
Worked in this mode on and off for 4 days then it stopped, no sdptool browse response. So restarted the phone, could not transfer the calendar but sdptool browse <id> worked.
I then checked the output from sdptool browse <id> and noticed that the SyncMLClient channel had changed from 6 to 5 !!!
So I changed my settings to 5 in the Multisync tool, all good calender transfer worked.
Next evening transfer failed. So I checked the channel again - and it had reset back to 6!
Here are some comments from another bug - suggestion is that Multisync should be able to query the phone (via SDPtool?) and determine the correct channel.
kylea wrote:
> I then checked the output from sdptool browse <id> and noticed that the
> SyncMLClient channel had changed from 6 to 5 !!!
That's fine. It's not much different to computers changing IP address.
Apps should read the metadata (from sdptool!) and work out the right channel to use.
> So I changed my settings to 5 in the Multisync tool, all good calender
> transfer worked
Sounds like the bug is Multisync requiring you to enter the channel number.
It should work it out automatically. Maybe you could file a bug report for Multisync?
Here it is on Channel 5
Service Name: SyncMLClient 0000-1000- 8000-0002ee0000 02
Service RecHandle: 0x10006
Service Class ID List:
UUID 128: 00000002-
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
"OBEX" (0x0008) 0000-1000- 8000-0002ee0000 02)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-
Version: 0x0100