From: Conrad W. <con...@we...> - 2006-05-03 10:01:17
|
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 (=C3=A4, =C3=B6, = =C3=BC, ...) 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? 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. 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. If traces for a specific issue are needed, please let me know. By the way, excellent work! Conrad. --=20 Conrad Wolf <con...@we...> |
From: Gerik H. <gh...@gm...> - 2006-05-04 09:31:37
|
Hi Conrad, nice to hear, that it works at last. I have already checked out and compile= d=20 the svn versions but didn't have the time so far to test it! Am Mittwoch, 3. Mai 2006 11:56 schrieb Conrad Wolf: > Hi list! >=20 > 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. >=20 > 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. >=20 > If I add a contact or an appointment with German umlauts (=C3=A4, =C3=B6,= =C3=BC, ...) > 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? This problem is caused by the use of utf8 encoding on your PC and iso8859 o= n=20 the phone. If you copy the vcf's manually to the phone you can convert them= =20 using iconv. There seem to be converters already integrated into the code as the working= =20 transfer from phone to pc shows. So it's propably a minor bug? Regards Gerik |
From: Armin B. <arm...@de...> - 2006-05-09 00:42:39
Attachments:
signature.asc
|
Conrad Wolf wrote: > Hi list! >=20 > 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. >=20 > 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. >=20 > If I add a contact or an appointment with German umlauts (=C3=A4, =C3=B6= , =C3=BC, ...) > in evolution, after synchronization the umlauts appear kind of scramble= d > 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 an= d > 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 :) >=20 > Second problem appears when I create an appointment with an alarm set i= n > 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 wit= h > 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)? >=20 > 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? Armin >=20 > If traces for a specific issue are needed, please let me know. By the > way, excellent work! >=20 > Conrad. >=20 >=20 |
From: Conrad W. <con...@we...> - 2006-05-10 23:05:43
|
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. |
From: Armin B. <arm...@de...> - 2006-05-19 11:03:14
Attachments:
signature.asc
|
Hi, >=20 > The X-EPOCAGENDAENTRYTYPE:ANNIVERSARY seems to be Symbian specific agai= n. If=20 > this is all the case and if it is common to all Symbian devices, it mig= ht=20 > make sense to create a special syncml-symbian-client or to include a sw= itch=20 > into the syncml-obex-client to take care of these peculiarities. What d= o you=20 > reckon? OpenSync supports so called "extensions" in its format converters. A extensions implements device-specific "enhancements" to the vcards to support such devices. So we now need a extension to the vcard format called "symbian" which takes care of shaping the vcard into something these devices accept. we are currently reworking the internal format conversion to make it more powerful. At the moment it would not be possible to create this "symbian" extension yet. >=20 > One other problem occured when I imported my real contact list (all uml= auts=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 transfer= red=20 > contacts, but suddenly after about 30 of 150 contacts the sync stoped. = > 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: >=20 > I/O error : Attempt to load network entity=20 > http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd >=20 > After a while tons of error messages of this type appear: >=20 > Error writing entry pas-id-445FBF6C00000060 to member 2: Timeout while = waiting=20 > for a reply to message "COMMIT_CHANGE" > Mapping Write Error: Timeout while waiting for a reply to=20 > message "COMMIT_CHANGE" >=20 > The syncml-obex-client trace ends with the following lines: >=20 > [1147126085.317415] <<<<<<< client_message_handler > [1147126085.755768] >>>>>>> _manager_event(0x80831e0, 6, 0x80c9768, (n= il),=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, 0x8= 667ef8,=20 > 0x8082500) > [1147126091.77014] There was an error in the session 219: Received a s= tatus=20 > after commands > [1147126091.77071] <--- ERROR --- _manager_event: Received a status aft= er=20 > commands > [1147126091.77110] >>>>>>> _smlManagerEventFree(0x820e7e0) > [1147126091.77149] >>>>>>> smlSessionUnref(0x80c9768) > [1147126091.77187] <<<<<<< smlSessionUnref > [1147126091.77227] <<<<<<< _smlManagerEventFree >=20 > No idea what happened here, but it's not nice. It never happened when I= did=20 > the testing with only a few entries. >=20 > I've taken traces of all the above syncs, but I decided not to attach t= hem to=20 > this mail. I'll send em off-list. the syncml protocols clearly states that no status has to be sent after a command has been sent. but some devices simply ignore the standard and 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 > Hope this helps a bit. >=20 > Conrad. >=20 >=20 >> Armin >> >=20 >=20 > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job = easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642 > _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users >=20 |
From: Conrad W. <con...@we...> - 2006-05-24 22:25:17
|
> > One other problem occured when I imported my real contact list (all umlauts > > substituted) to evolution to sync it to my phone. The sync started okey and > > the phone display was showing a progress bar and the number of transferred > > contacts, but suddenly after about 30 of 150 contacts the sync stoped. > > Sometimes this occured at entry 27 sometimes at 30 and so on. I had the > > impression that this coincides with the following line appearing on the CL: > > > > I/O error : Attempt to load network entity > > 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 waiting > > for a reply to message "COMMIT_CHANGE" > > Mapping Write Error: Timeout while waiting for a reply to > > 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), > > 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, 0x8667ef8, > > 0x8082500) > > [1147126091.77014] There was an error in the session 219: Received a status > > after commands > > [1147126091.77071] <--- ERROR --- _manager_event: Received a status after > > 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 > > the testing with only a few entries. > > > > I've taken traces of all the above syncs, but I decided not to attach them to > > this mail. I'll send em off-list. > > the syncml protocols clearly states that no status has to be sent after > a command has been sent. but some devices simply ignore the standard and > do this anyways. > > there is a option in the config AllowLateStatus which you can set to 1 > to allow such behaviour. > > Best Regards, > Armin Hi Armin, I put <AllowLateStatus>1</AllowLateStatus> 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 I/O error : Attempt to load network entity http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd appears on the command line. I read somewhere on the list that one could ignore this error message. Is that definite or is there a chance that it is correlated to the freezing of the sync? Cheers, Conrad. -- Conrad Wolf <con...@we...> |
From: Armin B. <arm...@de...> - 2006-06-02 19:39:06
Attachments:
signature.asc
|
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 |
From: Conrad W. <con...@we...> - 2006-06-03 09:59:03
|
On Friday, 2. June 2006 21:39, Armin Bauer wrote: > Conrad Wolf wrote: > >>> One other problem occured when I imported my real contact list (all > >>> umlauts substituted) to evolution to sync it to my phone. The sync > >>> started okey and the phone display was showing a progress bar and the > >>> number of transferred contacts, but suddenly after about 30 of 150 > >>> contacts the sync stoped. Sometimes this occured at entry 27 sometimes > >>> at 30 and so on. I had the impression that this coincides with the > >>> following line appearing on the CL: > >>> > >>> I/O error : Attempt to load network entity > >>> 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 > >>> waiting for a reply to message "COMMIT_CHANGE" > >>> Mapping Write Error: Timeout while waiting for a reply to > >>> 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), 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, > >>> 0x8667ef8, 0x8082500) > >>> [1147126091.77014] There was an error in the session 219: Received a > >>> status after commands > >>> [1147126091.77071] <--- ERROR --- _manager_event: Received a status > >>> after 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 the testing with only a few entries. > >>> > >>> I've taken traces of all the above syncs, but I decided not to attach > >>> them to this mail. I'll send em off-list. > >> > >> the syncml protocols clearly states that no status has to be sent after > >> a command has been sent. but some devices simply ignore the standard and > >> do this anyways. > >> > >> there is a option in the config AllowLateStatus which you can set to 1 > >> to allow such behaviour. > >> > >> Best Regards, > >> Armin > > > > Hi Armin, > > > > I put > > > > <AllowLateStatus>1</AllowLateStatus> > > > > 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 > > > > I/O error : Attempt to load network entity > > http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd > > > > appears on the command line. I read somewhere on the list that one could > > ignore this error message. Is that definite or is there a chance that it > > 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 I checked out the new version from svn a few days ago and the problem went away :-). Thanks a lot!!! I still have the problem though that sometimes some random entry gives me a 'Error 500' message during the sync, while the same entry works at other times. I'll do some more testing on that issue and then report again. Aside from that everything seems to work fine now. Good work! Conrad. |
From: Armin B. <arm...@de...> - 2006-06-05 00:08:18
Attachments:
signature.asc
|
Conrad Wolf wrote: > On Friday, 2. June 2006 21:39, Armin Bauer wrote: >> Conrad Wolf wrote: >>>>> One other problem occured when I imported my real contact list (all= >>>>> umlauts substituted) to evolution to sync it to my phone. The sync >>>>> started okey and the phone display was showing a progress bar and t= he >>>>> number of transferred contacts, but suddenly after about 30 of 150 >>>>> contacts the sync stoped. Sometimes this occured at entry 27 someti= mes >>>>> at 30 and so on. I had the impression that this coincides with the >>>>> following line appearing on the CL: >>>>> >>>>> I/O error : Attempt to load network entity >>>>> 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 wh= ile >>>>> waiting for a reply to message "COMMIT_CHANGE" >>>>> Mapping Write Error: Timeout while waiting for a reply to >>>>> 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), 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,= >>>>> 0x8667ef8, 0x8082500) >>>>> [1147126091.77014] There was an error in the session 219: Received= a >>>>> status after commands >>>>> [1147126091.77071] <--- ERROR --- _manager_event: Received a status= >>>>> after 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 wh= en I >>>>> did the testing with only a few entries. >>>>> >>>>> I've taken traces of all the above syncs, but I decided not to atta= ch >>>>> them to this mail. I'll send em off-list. >>>> the syncml protocols clearly states that no status has to be sent af= ter >>>> a command has been sent. but some devices simply ignore the standard= and >>>> do this anyways. >>>> >>>> there is a option in the config AllowLateStatus which you can set to= 1 >>>> to allow such behaviour. >>>> >>>> Best Regards, >>>> Armin >>> Hi Armin, >>> >>> I put >>> >>> <AllowLateStatus>1</AllowLateStatus> >>> >>> into my syncml-obex-client.conf, but that didn't help. I also split m= y >>> 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 progre= ss >>> bar and the counting of transferred entries on the phone always occur= s >>> when >>> >>> I/O error : Attempt to load network entity >>> http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd >>> >>> appears on the command line. I read somewhere on the list that one co= uld >>> ignore this error message. Is that definite or is there a chance that= it >>> is correlated to the freezing of the sync? >> this is definitely not related to the freeze (actually i finally manag= ed >> 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= =2E >> >> Armin >=20 >=20 > I checked out the new version from svn a few days ago and the problem w= ent=20 > away :-). Thanks a lot!!! >=20 > I still have the problem though that sometimes some random entry gives = me=20 > a 'Error 500' message during the sync, while the same entry works at ot= her=20 > times. I'll do some more testing on that issue and then report again. This is a known "bug". A lot of phones dont understand the events that are generated by applications like evolution. the solution to this will be, that opensync will convert such events internally to something that is understood by the phones. Writing this converter is a lot of work, thats why this isnt fixed yet. Armin >=20 > Aside from that everything seems to work fine now. Good work! >=20 > Conrad. >=20 |