9:40 a.m.
On Mon, 2011-01-17 at 09:24 +0100, Patrick Ohly wrote:
I'm not sure what's up with the E71. Typically Nokia phones
can be
reached without having to dive into the command line, like the author of
http://syncevolution.org/wiki/nokia-e71-ubuntu-1004-lts did.
Me neither. The frustrating thing is a bunch of people have asked him to
clarify in the comments section and to finish the tutorial, but he
doesn't seem to be responsive for some reason.
Reading
what he did it remains unclear to me why he is changing the OBEX
channel, in particular to the one used by "OBEX File Transfer" - that
looks just plain wrong.
If you use just the "sync-ui" to create a configuration for
the E71,
using the generic "Nokia" template, does it work? If so, please fix the
Wiki.
Something difficult to do is installing the sync-ui package because it
conflicts with the syncevolution-evolution package. Not sure which one
of them I need to make this sync stuff work with Evolution.
Anyway, let's diagnose this. What is the output of "hcitool
scan"?
$ hcitool scan
Scanning ...
00:21:FE:CB:6D:4D Foo
What
does "sdptool search --bdaddr <bdaddr from scan> SYNCML" say?
$ sdptool search --bdaddr "00:21:FE:CB:6D:4D" SYNCML
Searching for SYNCML on 00:21:FE:CB:6D:4D ...
Service Name: SyncMLClient
Service RecHandle: 0x10018
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
For the N97 I get:
$ hcitool scan
Scanning ...
A0:4E:04:1E:AD:30 Nokia N97 mini
$ sdptool search --bdaddr A0:4E:04:1E:AD:30 SYNCML
Searching for SYNCML on A0:4E:04:1E:AD:30 ...
Service Name: SyncMLClient
Service RecHandle: 0x1000b
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 7
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
Note that SyncEvolution automatically finds the right channel. There
should never be a need to specify it explicitly.
I'm not sure why he suggested to change it, but my OBEX File Transfer
service appears to be on channel 11 also:
Service Name: OBEX File Transfer
Service RecHandle: 0x10019
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 11
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com