Re: [Opensync-users] Partial success on Nokia 6630

[Armin B. <arm...@de...>]

Conrad Wolf wrote:
>>> One other problem occured when I imported my real contact list (all u=
mlauts=20
>>> substituted) to evolution to sync it to my phone. The sync started ok=
ey and=20
>>> the phone display was showing a progress bar and the number of transf=
erred=20
>>> contacts, but suddenly after about 30 of 150 contacts the sync stoped=
=2E=20
>>> Sometimes this occured at entry 27 sometimes at 30 and so on. I had t=
he=20
>>> impression that this coincides with the following line appearing on t=
he CL:
>>>
>>> I/O error : Attempt to load network entity=20
>>> http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
>>>
>>> After a while tons of error messages of this type appear:
>>>
>>> Error writing entry pas-id-445FBF6C00000060 to member 2: Timeout whil=
e waiting=20
>>> for a reply to message "COMMIT_CHANGE"
>>> Mapping Write Error: Timeout while waiting for a reply to=20
>>> message "COMMIT_CHANGE"
>>>
>>> The syncml-obex-client trace ends with the following lines:
>>>
>>> [1147126085.317415]	<<<<<<<  client_message_handler
>>> [1147126085.755768]	>>>>>>>  _manager_event(0x80831e0, 6, 0x80c9768, =
(nil),=20
>>> 0x8082500)
>>> [1147126085.755848]	<<<<<<<  _manager_event
>>> [1147126085.755888]	>>>>>>>  _smlManagerEventFree(0x858dc98)
>>> [1147126085.755927]		>>>>>>>  smlSessionUnref(0x80c9768)
>>> [1147126085.755965]		<<<<<<<  smlSessionUnref
>>> [1147126085.756003]	<<<<<<<  _smlManagerEventFree
>>> [1147126091.76960]	>>>>>>>  _manager_event(0x80831e0, 7, 0x80c9768, 0=
x8667ef8,=20
>>> 0x8082500)
>>> [1147126091.77014]		There was an error in the session 219: Received a=
 status=20
>>> after commands
>>> [1147126091.77071]	<--- ERROR --- _manager_event: Received a status a=
fter=20
>>> commands
>>> [1147126091.77110]	>>>>>>>  _smlManagerEventFree(0x820e7e0)
>>> [1147126091.77149]		>>>>>>>  smlSessionUnref(0x80c9768)
>>> [1147126091.77187]		<<<<<<<  smlSessionUnref
>>> [1147126091.77227]	<<<<<<<  _smlManagerEventFree
>>>
>>> No idea what happened here, but it's not nice. It never happened when=
 I did=20
>>> the testing with only a few entries.
>>>
>>> I've taken traces of all the above syncs, but I decided not to attach=
 them to=20
>>> this mail. I'll send em off-list.
>> the syncml protocols clearly states that no status has to be sent afte=
r
>> a command has been sent. but some devices simply ignore the standard a=
nd
>> do this anyways.
>>
>> there is a option in the config AllowLateStatus which you can set to 1=

>> to allow such behaviour.
>>
>> Best Regards,
>> Armin
>=20
> Hi Armin,
>=20
> I put
>=20
> <AllowLateStatus>1</AllowLateStatus>
>=20
> into my syncml-obex-client.conf, but that didn't help. I also split my
> contact list into 2 parts and tried to sync these parts separately to
> check whether I have a corrupt entry, but the sync freezes with both
> parts at something between entry 25 to 30. The freezing of the progress=

> bar and the counting of transferred entries on the phone always occurs
> when
>=20
> I/O error : Attempt to load network entity
> http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
>=20
> appears on the command line. I read somewhere on the list that one coul=
d
> ignore this error message. Is that definite or is there a chance that i=
t
> is correlated to the freezing of the sync?

this is definitely not related to the freeze (actually i finally managed
to squelch the error message).

allowLateStatus is not needed anymore (it is now enabled by default).

i uploaded some fixes to the svn lately. so maybe it works for you now.

Armin

>=20
> Cheers,
> Conrad.
>=20
>=20