Menu
▾
▴
Re: [Opensync-users] Partial success on Nokia 6630
|
From: Armin B. <arm...@de...> - 2006-05-19 11:03:14
|
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 |
