opensync-users

[Opensync-users] SE K608i: syncml-obex-client error

[Jason G. <ja...@lo...>]

Fedora core 5
openobex 1.2
expat-2.0.0
libopensync-0.18
libopensync-plugin-file-0.18
libsoup (vcs head)
libsyncml (vcs head)
multisync-0.90.18
syncml-plugin (vcs head)
wbxml2-0.9.0 (patched)

Hello,

Just a status report on the SE K608i.  It fails on the sync, however I
am hopeful that it's something simple, and am willing to continue
testing.  Note that although the sync fails as described below, I am
able to transfer files OK using obexftp over usb.

I've been able to do a clean build/install with the configuration above,
however, when I try and sync, I get the following:

[root@pinback apps]# msynctool --sync sf
Synchronizing group "sf"
The previous synchronization was unclean. Slow-syncing
Member 1 of type file-sync just connected
Member 2 of type syncml-obex-client had an error while connecting:
Request not successfull: 80
Member 1 of type file-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error synchronizing: Unable to connect one of the members

My log shows:

Apr  2 15:22:36 pinback kernel: usb 1-1: usbfs: interface 1 claimed by
cdc_acm while 'msynctool' sets config #1

Based on this message I guessed that it may be due to some sort of
conflict with cdc_acm, so I did a "modprobe -r cdc_acm", but I still get
the same result from msynctool, but without an accompanying error in the
log.

In case it helps, my phone reads "Session failed.  Invalid server
response".

I am not sure how to proceed now - advice appreciated.

Re: [Opensync-users] SE K608i: syncml-obex-client error

[Jason G. <ja...@lo...>]

In case it helps, I turned on tracing in libsyncml, and the relevant
output is shown below.

[1143959889.465957] >>>>>>>  smlThreadStartCallback(0x935ff68)
[1143959889.466170]  +++++++++ This is the worker thread of thread
0x935ff68 for context 0x935f920 +++++++++
[1143959889.564931]  >>>>>>>  smlTransportWorkerHandler(0x93894c8,
0x935f810)
[1143959889.565051]   >>>>>>>  smlTransportObexClientConnect(0x93601c0)
[1143959889.565115]    connecting to usb interface 0
[1143959889.590042]    found 1 interfaces
[1143959889.630085]    usb connect done
[1143959889.731357]    >>>>>>>  _smlObexEvent(0x9360f00, 0x939b010, 0,
3, 0, 32)
[1143959889.731484]     Request Done
[1143959889.731551]     Next header 203, 1, 0x1
[1143959889.731625]     Found connection number: 1
[1143959889.731691]     Next header 74, 154739656, 0x93923c8
[1143959889.731756]     Found who: SYNCML-SYNC
[1143959889.731825]     >>>>>>>  smlTransportReceiveEvent(0x935f810,
(nil), 0, (nil), (nil))
[1143959889.732016]      >>>>>>>  _smlManagerDataHandler(0x935f810,
(nil), 0, (nil), (nil), 0x935f760)
[1143959889.732087]      <<<<<<<  _smlManagerDataHandler
[1143959889.732149]     <<<<<<<  smlTransportReceiveEvent
[1143959889.732209]    <<<<<<<  _smlObexEvent
[1143959889.732278]   <<<<<<<  smlTransportObexClientConnect
[1143959889.732341]  <<<<<<<  smlTransportWorkerHandler
[1143959889.783335]  >>>>>>>  smlTransportWorkerHandler(0x9389848,
0x935f810)
[1143959889.783442]   >>>>>>>  smlTransportObexClientSend(0x93601c0,
(nil), 0x93899f0, 0, 8, 0x93894c8)
[1143959889.783513]    Adding connection id 1
[1143959889.783581]    Target application/vnd.syncml+xml
[1143959890.83439]    >>>>>>>  _smlObexEvent(0x9360f00, 0x939a7a0, 0, 3,
2, 80)
[1143959890.83565]     Request Done
[1143959890.83639]     >>>>>>>  smlTransportReceiveEvent(0x935f810,
(nil), 2, (nil), 0x93894c8)
[1143959890.83706]      >>>>>>>  _smlManagerDataHandler(0x935f810,
(nil), 2, (nil), 0x93894c8, 0x935f760)
[1143959890.83783]      <--- ERROR --- _smlManagerDataHandler: Request
not successfull: 80
[1143959890.83845]     <<<<<<<  smlTransportReceiveEvent
[1143959890.83907]    <--- ERROR --- _smlObexEvent: Request not
successfull: 80
[1143959890.83975]    Done sending the put request
[1143959890.84040]    Adding connection id 1
[1143959890.104234]    >>>>>>>  _smlObexEvent(0x9360f00, 0x939a760, 0,
3, 3, 79)
[1143959890.104363]     Request Done
[1143959890.104435]     >>>>>>>  smlTransportReceiveEvent(0x935f810,
(nil), 2, (nil), 0x939b538)
[1143959890.104500]      >>>>>>>  _smlManagerDataHandler(0x935f810,
(nil), 2, (nil), 0x939b538, 0x935f760)
[1143959890.104576]      <--- ERROR --- _smlManagerDataHandler: Request
not successfull: 79
[1143959890.104638]     <<<<<<<  smlTransportReceiveEvent
[1143959890.104700]    <--- ERROR --- _smlObexEvent: Request not
successfull: 79
[1143959890.104766]   <<<<<<<  smlTransportObexClientSend
[1143959890.104830]   >>>>>>>  smlTransportDataDeref(0x93899f0)
[1143959890.104891]   <<<<<<<  smlTransportDataDeref: refCount > 0
[1143959890.104953]  <<<<<<<  smlTransportWorkerHandler

Re: [Opensync-users] SE K608i: syncml-obex-client error

[Dave H. <sk...@ph...>]

Hi Jason

On Sun, 2006-04-02 at 16:00 +1000, Jason Grant wrote:
<snip />
> Hello,
> 
> Just a status report on the SE K608i.  It fails on the sync, however I
> am hopeful that it's something simple, and am willing to continue
> testing.  Note that although the sync fails as described below, I am
> able to transfer files OK using obexftp over usb.
> 

The K608i is an orange/3 branded K600i, I have the V600i which is the
vodafone branded version, which strangely is recognised by lsusb in
parts as a K608i.

I haven't tried syncing the phone using opensync or any other software,
I have got it working as a modem and can use obex ftp to grab pics and
music from the phone and to upload the same along with contacts and
events.

Having a look at the output of lsusb I don't think the phone supports
syncml via usb.  It does support it OTA but that isn't cheap or
desirable.

If I am wrong I apologise for the confusion caused by my ignorance.

Cheers

Dave

Re: [Opensync-users] SE K608i: syncml-obex-client error

[Jason G. <ja...@lo...>]

On Sun, 2006-04-02 at 16:33 +1000, Dave Hall wrote:

> 
> Having a look at the output of lsusb I don't think the phone supports
> syncml via usb.  It does support it OTA but that isn't cheap or
> desirable.


That's a shame.  According to the manual, the phone supplies a bluetooth
profile called "SyncML OBEX binding", so I guess I'll need to wait until
opensync supports bluetooth transport.

I'll happily test/troubleshoot this functionality when it is released.

Thanks for the info.

Jason.