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

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi Armin,

On Sunday, 7. May 2006 18:39, Armin Bauer wrote:
> Conrad Wolf wrote:
> > Hi list!
> >
> > Yeppie! After applying the wbxml2-patch I finally managed to sync my
> > Nokia 6630 to evolution via USB. I'm using libopensync-0.18,
> > libopensync-plugin-evolution2-0.18 and a fairly recent svn version of
> > the syncml-obex-client.
> >
> > I can create contacts and appointments in evolution as well as on the
> > phone and they'll be properly synchronized. It also works to change an
> > entry on the phone or in evolution and synchronize. However, I've still
> > some issues with umlauts, alarms and recurrences.
> >
> > If I add a contact or an appointment with German umlauts (=EF=BF=BD=C2=
=A4, =EF=BF=BD=C4=A5, =EF=BF=BD=C4=B5,
> > ...) in evolution, after synchronization the umlauts appear kind of
> > scrambled on the phone. If I add umlauts on the phone, they are
> > transfered correctly to evolution. I figure that it has something to do
> > with evolution's export functions, because the same problem occurs when=
 I
> > export my contacts from evolution as vcards. Is this a known problem and
> > is there anything I can do about it?
>
> Yes, this is a known problem. Opensync does not support conversion of
> encodings at the moment (but this is a big TODO on our list). so if the
> phone does not use the same encoding as evo2 (and it probably doesnt)
> then the umlaute will be scrambled. There is not much you can do about
> this (besides fixing this problem in opensync :)

I'd love to do that, but at the moment  I'm unfortunately lacking the time =
as=20
well as the skills to do so. Anyway, if I find some spare time, I might try=
 to=20
take a look at the source code. This won't bring any results in the near=20
future though, 'cause I've not really a lot of experience in programming. I=
=20
only had some C/C++ classes at university, that's about it. For now I'll=20
substitute the umlauts by the corresponding ae, oe, ...

> > Second problem appears when I create an appointment with an alarm set in
> > evolution. The sync will fail on that entry and synchronization will
> > only finish successfully again after removing the alarm or the whole
> > entry from evolution. On the other hand, if I create an appointment with
> > alarm on the phone, the sync is successful and the appointment appears
> > in evolution. However the alarm set on the phone ist not present in
> > evolution. Any ideas? This would be quite important for me to work.
>
> Can you show me an event from evo2 and one from the phone which do not
> work correctly (you can extract them from the trace files if necessary)?

I've createt an event in evolution first and did a sync between evo and the=
=20
phone which terminated with the following error:

conrad@hlphys20:~$ msynctool --sync evo-nokia6630-test
Synchronizing group "evo-nokia6630-test"
Member 1 of type evo2-sync just connected
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
received event dsession
received contact dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Received a entry 20060508T184918Z-7234-1000-1-1@hlphys20 with data of size =
4=20
from member 1. Changetype ADDED
Member 1 of type evo2-sync just sent all changes
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our Alert
Received an reply to our Alert
Going to receive 0 changes
Going to receive 0 changes
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 1 of type evo2-sync committed all changes.
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our sync
Received an reply to our sync
Error writing entry 20060508T184918Z-7234-1000-1-1@hlphys20 to member 2:=20
Unable to commit change. Error 500
Mapping Write Error: Unable to commit change. Error 500
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 1 of type evo2-sync just disconnected
Member 2 of type syncml-obex-client had an error while disconnecting: Link=
=20
Error
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

After this sync I did another sync between evo and the file-sync plugin to =
get=20
the evo entry:

BEGIN:VCALENDAR
VERSION:1.0
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20060508T184918Z
DTSTART:20060508T080000Z
DTEND:20060508T100000Z
TRANSP:TRANSPARENT
SEQUENCE:2
SUMMARY:Whatever
CLASS:PUBLIC
CREATED:20060508T184943
LAST-MODIFIED:20060508T184943
BEGIN:VALARM
DESCRIPTION:Whatever
ACTION:DISPLAY
TRIGGER;VALUE=3DDURATION;RELATED=3DSTART:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR

When creating a similar entry on the phone, the sync between evo and the ph=
one=20
give me the following CL output:

conrad@hlphys20:~$ msynctool --sync evo-nokia6630-test
Synchronizing group "evo-nokia6630-test"
The previous synchronization was unclean. Slow-syncing
Member 1 of type evo2-sync just connected
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
received event dsession
received contact dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Member 1 of type evo2-sync just sent all changes
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our Alert
Received an reply to our Alert
Going to receive 0 changes
Going to receive 1 changes
Received a entry 18 with data of size 345 from member 2. Changetype ADDED
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Sent a entry 20060508T190305Z-7234-1000-1-3@hlphys20 of size 242 to member =
1.=20
Changetype ADDED
Member 1 of type evo2-sync committed all changes.
Member 1 of type evo2-sync just disconnected
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our sync
Received an reply to our sync
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync was successful

The sync seems to have worked fine, but when I fetch the etries from evo an=
d=20
the phone via file-syncs, the evo entry is not showing any alarm:

Phone:

BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
UID:18
SUMMARY:Whatever
DTSTART:20060509T080000
DTEND:20060509T100000
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PRIVATE
DCREATED:20060508T000000
AALARM;TYPE=3DX-EPOCSOUND:20060509T074500;;0;CalenAlarmSound
LAST-MODIFIED:20060508T170300
PRIORITY:0
STATUS:NEEDS ACTION
END:VEVENT
END:VCALENDAR

Evo:

BEGIN:VCALENDAR
VERSION:1.0
METHOD:PUBLISH
BEGIN:VEVENT
SUMMARY:Whatever
DTSTART:20060509T080000
DTEND:20060509T100000
CLASS:PRIVATE
CREATED:20060508T190305
LAST-MODIFIED:20060508T190305
PRIORITY:0
DTSTAMP:20060508T190305Z
END:VEVENT
END:VCALENDAR

This seems to be due to the AALARM field used by the phone. I did a little=
=20
Google search about it and it looks like this would be a Symbian specific=20
command.

> > Third issue is a similar thing with recurrences. If I create an
> > appointment with recurrence, only the "master"-appointment is synced.
> > Its recurrences do not appear in the calendar they are synced to, but
> > only in the original one. Wouldn't be too serious if this will not work,
> > because in evolution recurrences are a pain anyway.
>
> in which direction does this problem appear? does your phone support
> recurrences?

Yes, it does. At least if they're not to complex (exceptions, etc.). I did =
the=20
same game as for the alarm for a recurring entry. Creating an entry in=20
evolution would again cause the sync to fail, this time with a different=20
error though:

conrad@hlphys20:~$ msynctool --sync evo-nokia6630-test
Synchronizing group "evo-nokia6630-test"
Member 1 of type evo2-sync just connected
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
received event dsession
received contact dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Received a entry 20060508T190943Z-7234-1000-1-6@hlphys20 with data of size =
4=20
from member 1. Changetype ADDED
Received a entry 20060508T190305Z-7234-1000-1-3@hlphys20 with data of size =
0=20
from member 1. Changetype DELETED
Member 1 of type evo2-sync just sent all changes
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our Alert
Received an reply to our Alert
Going to receive 0 changes
Going to receive 0 changes
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 1 of type evo2-sync committed all changes.
Error writing entry 18 to member 2: content type was not configured
Mapping Write Error: content type was not configured
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our sync
Received an reply to our sync
Sent a entry 19 of size 338 to member 2. Changetype ADDED
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 1 of type evo2-sync just disconnected
Member 2 of type syncml-obex-client had an error while disconnecting: Link=
=20
Error
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

The corresponding entries are:

Evo:

BEGIN:VCALENDAR
VERSION:1.0
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20060508T190943Z
DTSTART:20060509T080000Z
DTEND:20060509T100000Z
TRANSP:TRANSPARENT
SEQUENCE:2
SUMMARY:Whatever
CLASS:PUBLIC
RRULE:FREQ=3DWEEKLY;UNTIL=3D20060530;INTERVAL=3D1;BYDAY=3DTU
CREATED:20060508T191057
LAST-MODIFIED:20060508T191057
END:VEVENT
END:VCALENDAR

Phone:

BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
UID:19
SUMMARY:Whatever
DTSTART:20060509T080000
DTEND:20060509T100000
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PUBLIC
DCREATED:20060508T000000
LAST-MODIFIED:20060508T170900
PRIORITY:0
STATUS:NEEDS ACTION
END:VEVENT
END:VCALENDAR

As you can see, the entry was synced to the phone, but the recurrence is=20
missing. Creating the event on the phone and syncing results again in a=20
successful sync:

conrad@hlphys20:~$ msynctool --sync evo-nokia6630-test
Synchronizing group "evo-nokia6630-test"
The previous synchronization was unclean. Slow-syncing
Member 1 of type evo2-sync just connected
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
received event dsession
received contact dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Member 1 of type evo2-sync just sent all changes
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our Alert
Received an reply to our Alert
Going to receive 1 changes
Going to receive 0 changes
Received a entry 20 with data of size 314 from member 2. Changetype ADDED
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Sent a entry 20060508T214137Z-7234-1000-1-9@hlphys20 of size 271 to member =
1.=20
Changetype ADDED
Member 1 of type evo2-sync committed all changes.
Member 1 of type evo2-sync just disconnected
I/O error : Attempt to load network entity=20
http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
Received an reply to our sync
Received an reply to our sync
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync was successful

Evo:

BEGIN:VCALENDAR
VERSION:1.0
METHOD:PUBLISH
BEGIN:VEVENT
SUMMARY:Whatever
DTSTART:20060509T080000
DTEND:20060509T100000
CLASS:PRIVATE
CREATED:20060508T214137
LAST-MODIFIED:20060508T214137
PRIORITY:0
DTSTAMP:20060508T214137Z
END:VEVENT
END:VCALENDAR

Phone:

BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
UID:20
SUMMARY:Whatever
DTSTART:20060509T080000
DTEND:20060509T100000
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PRIVATE
DCREATED:20060508T000000
RRULE:W1 TU 20060530T080000
LAST-MODIFIED:20060508T193800
PRIORITY:0
STATUS:NEEDS ACTION
END:VEVENT
END:VCALENDAR

However, as you can see from the entries, the recurrence rule is not=20
transferred to evolution. Comparing this phone entry to the evolution entry=
=20
from above it seems that the phone also uses different parameters for RRULE.

When playing around with recurrences I also created an anniversary entry on=
=20
the mobile, which is a special type of entry for yearly recurring events.=20
This entry looks like the following and is not recognized by evolution.

BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
UID:21
SUMMARY:Test
DTSTART:20060510T000000
DTEND:20060510T000000
X-EPOCAGENDAENTRYTYPE:ANNIVERSARY
CLASS:PRIVATE
DCREATED:20060510T000000
RRULE:YM1 5 #0
LAST-MODIFIED:20060510T195900
PRIORITY:0
STATUS:NEEDS ACTION
END:VEVENT
END:VCALENDAR

The X-EPOCAGENDAENTRYTYPE:ANNIVERSARY seems to be Symbian specific again. I=
f=20
this is all the case and if it is common to all Symbian devices, it might=20
make sense to create a special syncml-symbian-client or to include a switch=
=20
into the syncml-obex-client to take care of these peculiarities. What do yo=
u=20
reckon?

One other problem occured when I imported my real contact list (all umlauts=
=20
substituted) to evolution to sync it to my phone. The sync started okey and=
=20
the phone display was showing a progress bar and the number of transferred=
=20
contacts, but suddenly after about 30 of 150 contacts the sync stoped.=20
Sometimes this occured at entry 27 sometimes at 30 and so on. I had the=20
impression that this coincides with the following line appearing on the 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 while wait=
ing=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, 0x8667e=
f8,=20
0x8082500)
[1147126091.77014]		There was an error in the session 219: Received a statu=
s=20
after commands
[1147126091.77071]	<--- ERROR --- _manager_event: Received a status after=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.

Hope this helps a bit.

Conrad.

> Armin
>
> > If traces for a specific issue are needed, please let me know. By the
> > way, excellent work!
> >
> > Conrad.