|
From: Simon J. <si...@jo...> - 2008-02-05 19:06:49
|
Hi! I just got a Nokia E51 and wanted to sync it over Bluetooth. The phone uses channel 10 for SyncML [1], and requires a identifier "PC Suite". Syncing contacts and notes using syncml-obex-client works fine (as 'Contacts' and 'Notes' respectively). I've also set up 'msynctool', and it can sync contacts between syncml-obex-client and file-sync successfully. I'm using packages from Debian. However, syncing the calendar fails. I've tried libsyncml 0.4.5 (in Debian), and also libsyncml 0.4.6 (manual build), with same results. I just tried libsyncml from SVN, but that just fails with 'sml_support.c:443:E:smlSafeFree: Assertion "*address" failed'. The output from 0.4.5/0.4.6 is below. It also causes the phone to say 'Systemfel' (Swedish for 'System error'). Any ideas? Thanks, Simon [1] It has a 'SyncML DM Client' on channel 13, but it didn't seem to work. What is this? There was a 'Nokia SyncML Server' on channel 14 as well. jas@mocca:~$ /usr/local/bin/syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" --dumpinfo connection with device succeeded Received an Alert for the DS Server at Calendar: Type: 201, Last , Next 20080205T185652Z Slowsyncing Just received a new session with ID 1 Received the DevInf Session 1 reported final. flushing Received an reply to our Alert Session 1 reported final. flushing Session 1 has ended Send the output below to the libsyncml developers ======================================== Man: Nokia Mod: E51 FirmwareVersion: SoftwareVersion: 100.34.20 HardwareVersion: ReceiveLimit: 0 MaxObjSize: 0 Connection used: OBEX Client Identifier: PC Suite Databases: DB Locations: Calendar DB Type: text/x-vcalendar DB Slow: 1 Bluetooth: Yes Wbxml: Yes SyncML Version: 1.1 SupportsNumberofChanges: Yes SupportsLargeObjects: Yes jas@mocca:~$ |
|
From: Michael B. <mic...@cm...> - 2008-02-06 07:22:56
Attachments:
smime.p7s
|
Hi Simon, Simon Josefsson schrieb: > Hi! I just got a Nokia E51 and wanted to sync it over Bluetooth. The > phone uses channel 10 for SyncML [1], and requires a identifier "PC > Suite". Syncing contacts and notes using syncml-obex-client works fine > (as 'Contacts' and 'Notes' respectively). I've also set up 'msynctool', > and it can sync contacts between syncml-obex-client and file-sync > successfully. I'm using packages from Debian. libsyncml does not know anything about the synchronized content. So if contacts and notes synchronize correctly then libsyncml should work. Actually we have some problems with our vformat handling because iCal and vCal are not really compatible and additionally there are some special issues with Symbian (at minimum on UIQ 3 from Sony Ericsson). > However, syncing the calendar fails. I've tried libsyncml 0.4.5 (in > Debian), and also libsyncml 0.4.6 (manual build), with same results. I > just tried libsyncml from SVN, but that just fails with > 'sml_support.c:443:E:smlSafeFree: Assertion "*address" failed'. The assertion was newly introduced from me to detect wrong memory handling. Which subversion revision do you use? Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Simon J. <si...@jo...> - 2008-02-06 16:08:30
|
Michael Bell <mic...@cm...> writes: > Hi Simon, > > Simon Josefsson schrieb: > >> Hi! I just got a Nokia E51 and wanted to sync it over Bluetooth. The >> phone uses channel 10 for SyncML [1], and requires a identifier "PC >> Suite". Syncing contacts and notes using syncml-obex-client works fine >> (as 'Contacts' and 'Notes' respectively). I've also set up 'msynctool', >> and it can sync contacts between syncml-obex-client and file-sync >> successfully. I'm using packages from Debian. > > libsyncml does not know anything about the synchronized content. So if > contacts and notes synchronize correctly then libsyncml should > work. Actually we have some problems with our vformat handling because > iCal and vCal are not really compatible and additionally there are > some special issues with Symbian (at minimum on UIQ 3 from Sony > Ericsson). Hi Michael! Could the vformat problem explain why calendar syncing doesn't work, when contact syncing works? Since the phone prints an error message, it seems likely that a phone bug is involved. But maybe libsyncml could behave like Nokia's own software, to workaround this problem. My message was partially to gauge whether anyone else has seen this error, and if anyone compared traces with Nokia's software. >> However, syncing the calendar fails. I've tried libsyncml 0.4.5 (in >> Debian), and also libsyncml 0.4.6 (manual build), with same results. I >> just tried libsyncml from SVN, but that just fails with >> 'sml_support.c:443:E:smlSafeFree: Assertion "*address" failed'. > > The assertion was newly introduced from me to detect wrong memory > handling. Which subversion revision do you use? Revision 364. I removed my build tree and did a clean checkout and built it now, but it resulted in the same error. Thanks, /Simon jas@mocca:~/src$ rm -rf libsyncml jas@mocca:~/src$ svn co http://svn.opensync.org/libsyncml/trunk libsyncml A libsyncml/tools A libsyncml/tools/syncml-http-client.c A libsyncml/tools/syncml-http-server.1 A libsyncml/tools/syncml-http-server.c A libsyncml/tools/syncml-obex-client.1 A libsyncml/tools/CMakeLists.txt A libsyncml/tools/syncml-obex-client.c A libsyncml/tests A libsyncml/tests/check_wbxml_parser.c A libsyncml/tests/check_ds.c A libsyncml/tests/check_manager.c A libsyncml/tests/check_devinf.c A libsyncml/tests/check_sync.c A libsyncml/tests/check_elements.c A libsyncml/tests/check_xml_parser.c A libsyncml/tests/valgrind.supp A libsyncml/tests/check_http.c A libsyncml/tests/support.c A libsyncml/tests/check_san.c A libsyncml/tests/check_session.c A libsyncml/tests/check_base64.c A libsyncml/tests/support.h A libsyncml/tests/check_md5.c A libsyncml/tests/check_wbxml_assembler.c A libsyncml/tests/check_error.c A libsyncml/tests/check_xml_assembler.c A libsyncml/tests/check_obex.c A libsyncml/tests/CMakeLists.txt A libsyncml/AUTHORS A libsyncml/acinclude.m4 A libsyncml/CTestConfig.cmake A libsyncml/ChangeLog A libsyncml/COPYING A libsyncml/Doxyfile.in A libsyncml/docs A libsyncml/config.h.cmake A libsyncml/misc A libsyncml/misc/template.h A libsyncml/misc/debian A libsyncml/misc/debian/libsyncml-utils.install A libsyncml/misc/debian/control A libsyncml/misc/debian/libsyncml0.install A libsyncml/misc/debian/compat A libsyncml/misc/debian/changelog A libsyncml/misc/debian/copyright A libsyncml/misc/debian/docs A libsyncml/misc/debian/rules A libsyncml/misc/debian/libsyncml-dev.install A libsyncml/misc/doxygen.css A libsyncml/misc/Readme.RPM A libsyncml/misc/libsyncml.spec.in A libsyncml/misc/wbxml2-0.9.0.patch A libsyncml/misc/template.c A libsyncml/libsyncml A libsyncml/libsyncml/transports A libsyncml/libsyncml/transports/obex_client_internals.h A libsyncml/libsyncml/transports/obex_client.h A libsyncml/libsyncml/transports/http_client_internals.h A libsyncml/libsyncml/transports/http_client.h A libsyncml/libsyncml/transports/obex_server.c A libsyncml/libsyncml/transports/http_server.c A libsyncml/libsyncml/transports/obex_server_internals.h A libsyncml/libsyncml/transports/obex_server.h A libsyncml/libsyncml/transports/http_server_internals.h A libsyncml/libsyncml/transports/http_server.h A libsyncml/libsyncml/transports/obex_client.c A libsyncml/libsyncml/transports/http_client.c A libsyncml/libsyncml/sml_base64.c A libsyncml/libsyncml/sml_md5.c A libsyncml/libsyncml/sml_base64.h A libsyncml/libsyncml/sml_error.c A libsyncml/libsyncml/sml_md5.h A libsyncml/libsyncml/objects A libsyncml/libsyncml/objects/sml_auth_internals.h A libsyncml/libsyncml/objects/sml_devinf_obj.c A libsyncml/libsyncml/objects/sml_auth.h A libsyncml/libsyncml/objects/sml_devinf_obj_internals.h A libsyncml/libsyncml/objects/sml_devinf_obj.h A libsyncml/libsyncml/objects/sml_ds_server.c A libsyncml/libsyncml/objects/sml_ds_server_internals.h A libsyncml/libsyncml/objects/sml_auth.c A libsyncml/libsyncml/objects/sml_ds_server.h A libsyncml/libsyncml/sml_parse_internals.h A libsyncml/libsyncml/sml_error.h A libsyncml/libsyncml/sml_devinf_internals.h A libsyncml/libsyncml/sml_elements_internals.h A libsyncml/libsyncml/sml_command_internals.h A libsyncml/libsyncml/sml_session_internals.h A libsyncml/libsyncml/sml_queue_internals.h A libsyncml/libsyncml/sml_parse.c A libsyncml/libsyncml/sml_notification_internals.h A libsyncml/libsyncml/sml_devinf.c A libsyncml/libsyncml/sml_elements.c A libsyncml/libsyncml/sml_command.c A libsyncml/libsyncml/syncml_internals.h A libsyncml/libsyncml/sml_parse.h A libsyncml/libsyncml/sml_devinf.h A libsyncml/libsyncml/sml_transport_internals.h A libsyncml/libsyncml/CMakeLists.txt A libsyncml/libsyncml/sml_elements.h A libsyncml/libsyncml/sml_session.c A libsyncml/libsyncml/sml_command.h A libsyncml/libsyncml/sml_queue.c A libsyncml/libsyncml/sml_notification.c A libsyncml/libsyncml/sml_session.h A libsyncml/libsyncml/sml_notification.h A libsyncml/libsyncml/sml_transport.c A libsyncml/libsyncml/sml_manager_internals.h A libsyncml/libsyncml/syncml.h A libsyncml/libsyncml/parser A libsyncml/libsyncml/parser/sml_xml_assm.c A libsyncml/libsyncml/parser/sml_xml_assm_internals.h A libsyncml/libsyncml/parser/sml_xml_assm.h A libsyncml/libsyncml/parser/sml_wbxml.c A libsyncml/libsyncml/parser/sml_xml_parse.c A libsyncml/libsyncml/parser/sml_wbxml_internals.h A libsyncml/libsyncml/parser/sml_wbxml.h A libsyncml/libsyncml/parser/sml_xml_parse_internals.h A libsyncml/libsyncml/parser/sml_xml_parse.h A libsyncml/libsyncml/sml_transport.h A libsyncml/libsyncml/sml_manager.c A libsyncml/libsyncml/sml_support.c A libsyncml/libsyncml/sml_error_internals.h A libsyncml/libsyncml/sml_manager.h A libsyncml/libsyncml/sml_support.h A libsyncml/libsyncml/sml_defines.h A libsyncml/CMakeLists.txt A libsyncml/README A libsyncml/libsyncml-1.0.pc.cmake.in U libsyncml Fetching external item into 'libsyncml/cmake' A libsyncml/cmake/modules A libsyncml/cmake/modules/FindLibSoup2.cmake A libsyncml/cmake/modules/MacroEnsureOutOfSourceBuild.cmake A libsyncml/cmake/modules/FindORBit2.cmake A libsyncml/cmake/modules/FindSqlite.cmake A libsyncml/cmake/modules/FindGNUTLS.cmake A libsyncml/cmake/modules/FindCheck.cmake A libsyncml/cmake/modules/FindEDataCal1.0.cmake A libsyncml/cmake/modules/cmake_uninstall.cmake.in A libsyncml/cmake/modules/FindLibGnome2.cmake A libsyncml/cmake/modules/FindOpenObex.cmake A libsyncml/cmake/modules/FindEDataCal1.2.cmake A libsyncml/cmake/modules/FindGNOKII.cmake A libsyncml/cmake/modules/FindBlueZ.cmake A libsyncml/cmake/modules/FindBONOBOACTIVATION2.cmake A libsyncml/cmake/modules/FindECal1.0.cmake A libsyncml/cmake/modules/FindEvolutionDataServer1.0.cmake A libsyncml/cmake/modules/FindSqlite3.cmake A libsyncml/cmake/modules/FindECal1.2.cmake A libsyncml/cmake/modules/FindEvolutionDataServer1.2.cmake A libsyncml/cmake/modules/FindPythonLibs.cmake A libsyncml/cmake/modules/FindLibSyncMl.cmake A libsyncml/cmake/modules/FindKDEPIM3.cmake A libsyncml/cmake/modules/FindGLIB2.cmake A libsyncml/cmake/modules/FindEPackage.cmake A libsyncml/cmake/modules/FindBONOBO2.cmake A libsyncml/cmake/modules/FindLibWbxml2.cmake A libsyncml/cmake/modules/FindPilotLink.cmake A libsyncml/cmake/modules/FindGnomeVfs2.cmake A libsyncml/cmake/modules/FindPkgConfig.cmake A libsyncml/cmake/modules/FindEDataBook1.0.cmake A libsyncml/cmake/modules/FindLibXml2.cmake A libsyncml/cmake/modules/Compiler.cmake A libsyncml/cmake/modules/FindSWIG.cmake A libsyncml/cmake/modules/FindEDataBook1.2.cmake A libsyncml/cmake/modules/Testing.cmake A libsyncml/cmake/modules/FindGConf2.cmake A libsyncml/cmake/modules/FindEBook1.0.cmake A libsyncml/cmake/modules/FindEBook1.2.cmake A libsyncml/cmake/modules/ShowStatus.cmake A libsyncml/cmake/modules/FindEDataServer1.0.cmake A libsyncml/cmake/modules/FindEDataServer1.2.cmake A libsyncml/cmake/modules/COPYING-CMAKE-SCRIPTS A libsyncml/cmake/modules/FindOpenSync.cmake Checked out external at revision 3127. Checked out revision 364. jas@mocca:~/src$ cd libsyncml jas@mocca:~/src/libsyncml$ mkdir build jas@mocca:~/src/libsyncml$ cd build/ jas@mocca:~/src/libsyncml/build$ cmake -DCMAKE_INSTALL_PREFIX=/usr/local ../ -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Check size of void* -- Check size of void* - done -- Looking for include files HAVE_DLFCN_H -- Looking for include files HAVE_DLFCN_H - found -- Looking for include files HAVE_INTTYPES_H -- Looking for include files HAVE_INTTYPES_H - found -- Looking for include files HAVE_MEMORY_H -- Looking for include files HAVE_MEMORY_H - found -- Looking for include files HAVE_STDINT_H -- Looking for include files HAVE_STDINT_H - found -- Looking for include files HAVE_STDLIB_H -- Looking for include files HAVE_STDLIB_H - found -- Looking for include files HAVE_STRINGS_H -- Looking for include files HAVE_STRINGS_H - found -- Looking for include files HAVE_STRING_H -- Looking for include files HAVE_STRING_H - found -- Looking for include files HAVE_SYS_STAT_H -- Looking for include files HAVE_SYS_STAT_H - found -- Looking for include files HAVE_SYS_TYPES_H -- Looking for include files HAVE_SYS_TYPES_H - found -- Looking for include files HAVE_UNISTD_H -- Looking for include files HAVE_UNISTD_H - found -- Check size of uint16_t -- Check size of uint16_t - done -- Check size of uint32_t -- Check size of uint32_t - done -- Check size of uint8_t -- Check size of uint8_t - done -- checking for one of the modules 'glib-2.0' -- found glib-2.0, version 2.14.5 -- checking for one of the modules 'gmodule-2.0' -- found gmodule-2.0, version 2.14.5 -- checking for one of the modules 'gthread-2.0' -- found gthread-2.0, version 2.14.5 -- checking for one of the modules 'gobject-2.0' -- found gobject-2.0, version 2.14.5 -- Found GLib2: glib-2.0;gmodule-2.0;dl;glib-2.0;gthread-2.0;rt;glib-2.0 -- checking for one of the modules 'libxml-2.0' -- found libxml-2.0, version 2.6.31 -- checking for one of the modules 'openobex>=1.1' -- found openobex, version 1.3 -- checking for one of the modules 'libsoup-2.2>=2.2.91;libsoup2>=2.2.91' -- found libsoup-2.2, version 2.2.104 -- checking for one of the modules 'libwbxml2' -- found libwbxml2, version 0.9.0 -- checking for one of the modules 'bluez' -- found bluez, version 3.24 -- checking for one of the modules 'check' -- found check, version 0.9.5 -- ================================================== -- building tools ON -- tracing tools ON -- unit tests OFF -- http transports ON -- obex transports ON -- obex over bluetooth transports ON -- Configuring done -- Generating done -- Build files have been written to: /home/jas/src/libsyncml/build jas@mocca:~/src/libsyncml/build$ make Scanning dependencies of target syncml [ 3%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_base64.o [ 7%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_command.o [ 11%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_devinf.o [ 15%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_elements.o [ 19%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_error.o [ 23%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_manager.o [ 26%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_md5.o [ 30%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_notification.o [ 34%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_parse.o [ 38%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_queue.o [ 42%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_session.o [ 46%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_support.o [ 50%] Building C object libsyncml/CMakeFiles/syncml.dir/sml_transport.o [ 53%] Building C object libsyncml/CMakeFiles/syncml.dir/objects/sml_auth.o [ 57%] Building C object libsyncml/CMakeFiles/syncml.dir/objects/sml_devinf_obj.o [ 61%] Building C object libsyncml/CMakeFiles/syncml.dir/objects/sml_ds_server.o [ 65%] Building C object libsyncml/CMakeFiles/syncml.dir/parser/sml_wbxml.o [ 69%] Building C object libsyncml/CMakeFiles/syncml.dir/parser/sml_xml_assm.o [ 73%] Building C object libsyncml/CMakeFiles/syncml.dir/parser/sml_xml_parse.o [ 76%] Building C object libsyncml/CMakeFiles/syncml.dir/transports/http_client.o [ 80%] Building C object libsyncml/CMakeFiles/syncml.dir/transports/http_server.o [ 84%] Building C object libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o [ 88%] Building C object libsyncml/CMakeFiles/syncml.dir/transports/obex_server.o Linking C shared library libsyncml.so [ 88%] Built target syncml Scanning dependencies of target syncml-http-client [ 92%] Building C object tools/CMakeFiles/syncml-http-client.dir/syncml-http-client.o Linking C executable syncml-http-client [ 92%] Built target syncml-http-client Scanning dependencies of target syncml-http-server [ 96%] Building C object tools/CMakeFiles/syncml-http-server.dir/syncml-http-server.o Linking C executable syncml-http-server [ 96%] Built target syncml-http-server Scanning dependencies of target syncml-obex-client [100%] Building C object tools/CMakeFiles/syncml-obex-client.dir/syncml-obex-client.o Linking C executable syncml-obex-client [100%] Built target syncml-obex-client jas@mocca:~/src/libsyncml/build$ make install [ 88%] Built target syncml [ 92%] Built target syncml-http-client [ 96%] Built target syncml-http-server [100%] Built target syncml-obex-client Linking C shared library CMakeFiles/CMakeRelink.dir/libsyncml.so Linking C executable CMakeFiles/CMakeRelink.dir/syncml-http-client Linking C executable CMakeFiles/CMakeRelink.dir/syncml-http-server Linking C executable CMakeFiles/CMakeRelink.dir/syncml-obex-client Install the project... -- Install configuration: "" -- Installing /usr/local/lib/pkgconfig/libsyncml-1.0.pc -- Install configuration: "" -- Installing /usr/local/lib/libsyncml.so.0.0.0 -- Installing /usr/local/include/libsyncml-1.0/libsyncml/http_client.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/http_server.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/obex_client.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/obex_server.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_devinf_obj.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_ds_server.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_auth.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_base64.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_command.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_defines.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_devinf.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_elements.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_error.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_manager.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_md5.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_notification.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_parse.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_session.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/sml_transport.h -- Installing /usr/local/include/libsyncml-1.0/libsyncml/syncml.h -- Install configuration: "" -- Installing /usr/local/bin/syncml-http-client -- Installing /usr/local/bin/syncml-http-server -- Installing /usr/local/bin/syncml-obex-client -- Install configuration: "" jas@mocca:~/src/libsyncml/build$ sudo ldconfig jas@mocca:~/src/libsyncml/build$ /usr/local/bin/syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" --dumpinfo /home/jas/src/libsyncml/libsyncml/sml_support.c:443:E:smlSafeFree: Assertion "*address" failed Aborted jas@mocca:~/src/libsyncml/build$ |
|
From: Michael B. <mic...@cm...> - 2008-02-06 17:56:23
Attachments:
smime.p7s
|
Simon Josefsson schrieb: > Could the vformat problem explain why calendar syncing doesn't work, > when contact syncing works? Yes, I have myself heavy problems with OCS. Our vformat code creates several duplicates with the same UIDs internally. OCS detects this and returns errors while normal contact syncing works. > Since the phone prints an error message, it seems likely that a phone > bug is involved. But maybe libsyncml could behave like Nokia's own > software, to workaround this problem. My message was partially to gauge > whether anyone else has seen this error, and if anyone compared traces > with Nokia's software. This is not necessarily a phone bug. If OpenSync duplicates entries but the new entry includes the same UID then the phone will detect that there are two objects with the same internal UID. This is an error and so the phone reports an error code. Again this is the vCard UID and not the UID of SyncML for this object. >>> However, syncing the calendar fails. I've tried libsyncml 0.4.5 (in >>> Debian), and also libsyncml 0.4.6 (manual build), with same results. I >>> just tried libsyncml from SVN, but that just fails with >>> 'sml_support.c:443:E:smlSafeFree: Assertion "*address" failed'. >> The assertion was newly introduced from me to detect wrong memory >> handling. Which subversion revision do you use? I fixed some of these smlSafeFree bugs today (plus some race conditions). I introduced smlSafeFree to detect unclean memory handling in the libsyncml code and the assertions are the consequence :( newest SVN rev 365 and 3128 Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Simon J. <si...@jo...> - 2008-02-07 09:14:06
|
Michael Bell <mic...@cm...> writes: >> Could the vformat problem explain why calendar syncing doesn't work, >> when contact syncing works? > > Yes, I have myself heavy problems with OCS. Our vformat code creates > several duplicates with the same UIDs internally. OCS detects this and > returns errors while normal contact syncing works. Would this result in 'ERROR' in trace logs? I enabled tracing, but I don't see any errors in those logs. The problem seems to be on the phone, which fails and disconnects. >> Since the phone prints an error message, it seems likely that a phone >> bug is involved. But maybe libsyncml could behave like Nokia's own >> software, to workaround this problem. My message was partially to gauge >> whether anyone else has seen this error, and if anyone compared traces >> with Nokia's software. > > This is not necessarily a phone bug. If OpenSync duplicates entries > but the new entry includes the same UID then the phone will detect > that there are two objects with the same internal UID. This is an > error and so the phone reports an error code. > > Again this is the vCard UID and not the UID of SyncML for this object. I've searched for this problem a bit, and it seems to happen to a lot of people, even with Nokia's own software. And as far as I can tell, only when syncing the calendar. So I do suspect it is a phone bug after all. I'll see if I can find a Windows machine and test syncing on it. What worries me is that others have been able to work around this bug by erasing their entire calendar and starting from scratch, but I can't even get one simple calendar entry to sync properly. Those people typically end up with 'Sync Error' after a few sync's though, and have to erase the calendar again. >>>> However, syncing the calendar fails. I've tried libsyncml 0.4.5 (in >>>> Debian), and also libsyncml 0.4.6 (manual build), with same results. I >>>> just tried libsyncml from SVN, but that just fails with >>>> 'sml_support.c:443:E:smlSafeFree: Assertion "*address" failed'. >>> The assertion was newly introduced from me to detect wrong memory >>> handling. Which subversion revision do you use? > > I fixed some of these smlSafeFree bugs today (plus some race > conditions). I introduced smlSafeFree to detect unclean memory > handling in the libsyncml code and the assertions are the consequence > :( > > newest SVN rev 365 and 3128 It doesn't build: /home/jas/src/libsyncml/tools/syncml-http-server.c: In function ‘main’: /home/jas/src/libsyncml/tools/syncml-http-server.c:369: error: ‘SmlTransportHttpServerConfig’ has no member named ‘interface’ Thanks, /Simon |
|
From: Evgeni G. <sar...@di...> - 2008-02-06 16:10:24
|
Hi, On Tue, 05 Feb 2008 20:06:31 +0100 Simon Josefsson wrote: > Hi! I just got a Nokia E51 and wanted to sync it over Bluetooth. The > phone uses channel 10 for SyncML [1], and requires a identifier "PC > Suite". Syncing contacts and notes using syncml-obex-client works fine > (as 'Contacts' and 'Notes' respectively). I've also set up 'msynctool', > and it can sync contacts between syncml-obex-client and file-sync > successfully. I'm using packages from Debian. Could you please share your config? As my E51 do not want to sync, and opensync just says "String Table generation disabled: can't encode Literal" and I just don't understand why :( Regards Evgeni -- ^^^ | Evgeni -SargentD- Golov (sar...@di...) d(O_o)b | GPG/PGP-Key-ID: 0xAC15B50C >-|-< | 0C04 F872 0963 ADC9 AA83 882B 24A0 1418 AC15 B50C / \ | http://www.die-welt.net - sar...@ja... Kernel panic: Could not determine whether bit was one, zero or sqrt (1/PI)... (Jan Kohnert - debian-user-german) |
|
From: Simon J. <si...@jo...> - 2008-02-06 16:19:57
|
Evgeni Golov <sar...@di...> writes:
> Hi,
>
> On Tue, 05 Feb 2008 20:06:31 +0100 Simon Josefsson wrote:
>
>> Hi! I just got a Nokia E51 and wanted to sync it over Bluetooth. The
>> phone uses channel 10 for SyncML [1], and requires a identifier "PC
>> Suite". Syncing contacts and notes using syncml-obex-client works fine
>> (as 'Contacts' and 'Notes' respectively). I've also set up 'msynctool',
>> and it can sync contacts between syncml-obex-client and file-sync
>> successfully. I'm using packages from Debian.
>
> Could you please share your config? As my E51 do not want to sync, and
> opensync just says "String Table generation disabled: can't encode
> Literal" and I just don't understand why :(
Hi! This command works fine:
syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite"
Replace $MAC with your bluetooth MAC, and $CHANNEL with 10. This prints
my 153 contacts.
I don't believe it is reading any config files?
I'm using the latest phone software: '100.34.20 29-09-2007 rm-244 Nokia
E51 (03.1)'. Btw, be careful about updating software if your warranty
is void, I got this E51 because I bricked my old N80 when running Nokia
Software Update. The N80 phone is completely dead.
The msynctool config file I'm using is below. I didn't have to disable
stringtable generation, or touch any of the other parameters.
This is with libsyncml 0.4.5 (0.4.6 also seems to work), and opensync
0.35 from debian.
Good luck,
/Simon
<?xml version="1.0"?>
<config>
<!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is selected -->
<bluetooth_address>...</bluetooth_address>
<!-- (Only for bluetooth) The bluetooth channel to use. `sdptool browse $MAC` to search for the correct channel -->
<bluetooth_channel>10</bluetooth_channel>
<!-- (Only for USB) The usb interface number of the SYNCML-SYNC target. use syncml-obex-client -u (you will need access to the USB raw device) to find it. -->
<interface>0</interface>
<!-- The string that the plugin will use to identify itself. Some devices need a special string here. -->
<identifier>PC Suite</identifier>
<!-- The syncml version to use: 0 for 1.0, 1 for 1.1 and 2 for 1.2 -->
<version>1</version>
<!-- if the plugin should use wbxml -->
<wbxml>1</wbxml>
<!-- The username to use. Leave empty to not require a username -->
<username></username>
<!-- the password for the username -->
<password></password>
<!-- sets the connection type to use. 5 means obex over usb, 2 means obex over bluetooth -->
<type>2</type>
<!-- If wbxml is enabled, defines wether the wbxml should use string tables -->
<usestringtable>0</usestringtable>
<!-- Never send ADD command, but send REPLACE (not needed normally) -->
<onlyreplace>0</onlyreplace>
<!-- Workaround around for mobile phones which only use local timestamps and _no_ UTC timestamps! -->
<onlyLocaltime>0</onlyLocaltime>
<!-- Sets the maximum allowed size in bytes of incoming messages (some device need this option set). Example: 10000 -->
<recvLimit>0</recvLimit>
<maxObjSize>0</maxObjSize>
<!-- XXX: Currently you need to write this by your own.
Later it's planned to create such entries on the fly during
the discovery() call. Example database field:
-->
<database>
<name>Contacts</name>
<objtype>contact</objtype>
<objformat>vcard21</objformat>
</database>
</config>
|
|
From: Evgeni G. <sar...@di...> - 2008-02-07 12:54:14
|
Hi, On Wed, 06 Feb 2008 17:19:34 +0100 Simon Josefsson wrote: > syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" > > Replace $MAC with your bluetooth MAC, and $CHANNEL with 10. This prints > my 153 contacts. % syncml-obex-client -b MAC 10 --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" connection with device succeeded Received an Alert for the DS Server at Contacts: Type: 201, Last , Next 20080207T124939Z Slowsyncing Just received a new session with ID 1 Received the DevInf Session 1 reported final. flushing Received an transport error: Request not successfull: 67 That's what I get, also on Debian unstable, libsyncml 0.45 and the same software version on my e51, same for Calendar and Notes :( The phone just says "Systemfehler" (german for system error). I also tried using the USB cable, with no changes. |
|
From: Simon J. <si...@jo...> - 2008-02-07 13:29:27
|
Evgeni Golov <sar...@di...> writes:
> Hi,
>
> On Wed, 06 Feb 2008 17:19:34 +0100 Simon Josefsson wrote:
>
>> syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite"
>>
>> Replace $MAC with your bluetooth MAC, and $CHANNEL with 10. This prints
>> my 153 contacts.
>
> % syncml-obex-client -b MAC 10 --slow-sync text/x-vcard
> Contacts --wbxml --identifier "PC Suite"
> connection with device succeeded
> Received an Alert for the DS Server at Contacts: Type: 201, Last , Next
> 20080207T124939Z
> Slowsyncing
> Just received a new session with ID 1
> Received the DevInf
> Session 1 reported final. flushing
> Received an transport error: Request not successfull: 67
>
> That's what I get, also on Debian unstable, libsyncml 0.45 and the
> same software version on my e51, same for Calendar and Notes :(
> The phone just says "Systemfehler" (german for system error). I also
> tried using the USB cable, with no changes.
Curious! Have you tried a factory reset? (Backup phone using nokia's
software..)
I do remember getting the same (incorrectly spelled!) error message a
few times, when I used the wrong channel. What is your sdptool output?
Mine is below. Have you tried channel 13 or 14 instead?
I also got this when the bluetooth stack on the phone (or PC) was in a
bad state, which seems to happen after a while when you trigger a lot of
'Sync errors'. Try restarting the phone.
FWIW, I tried syncing the calendar using Nokia's software under Windows,
but since I don't have Outlook installed, it can't synchronize it.. :(
/Simon
Browsing 00:1D:6E:BD:57:A1 ...
Service Name: AVRCP Target
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10000
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service RecHandle: 0x10001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Service Name: OBEX Object Push
Service RecHandle: 0x10002
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 9
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: Dial-Up Networking
Service RecHandle: 0x10003
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Imaging
Service RecHandle: 0x10004
Service Class ID List:
"Imaging Responder" (0x111b)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 15
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Imaging" (0x111a)
Version: 0x0100
Service Name: Audio Source
Service RecHandle: 0x10007
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x100
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0100
Service Name: Hands-Free Audio Gateway
Service RecHandle: 0x10008
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105
Service Name: Headset Audio Gateway
Service RecHandle: 0x10009
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: AVRCP Controller
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x1000a
Service Class ID List:
"AV Remote" (0x110e)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: SyncMLClient
Service RecHandle: 0x1000b
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
Service Name: OBEX File Transfer
Service RecHandle: 0x1000c
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 11
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
Service Name: Nokia OBEX PC Suite Services
Service RecHandle: 0x1000d
Service Class ID List:
UUID 128: 00005005-0000-1000-8000-0002ee000001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 12
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00005005-0000-1000-8000-0002ee000001)
Version: 0x0100
Service Name: SyncML DM Client
Service RecHandle: 0x1000e
Service Class ID List:
UUID 128: 00000004-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 13
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000004-0000-1000-8000-0002ee000002)
Version: 0x0100
Service Name: Nokia SyncML Server
Service RecHandle: 0x10010
Service Class ID List:
UUID 128: 00005601-0000-1000-8000-0002ee000001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 14
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00005601-0000-1000-8000-0002ee000001)
Version: 0x0100
|
|
From: Evgeni G. <sar...@di...> - 2008-02-07 13:40:38
|
On Thu, 07 Feb 2008 14:29:18 +0100 Simon Josefsson wrote: > Curious! Have you tried a factory reset? (Backup phone using nokia's > software..) Uhm, no Windows here, will need to find someones laptop for that. > I do remember getting the same (incorrectly spelled!) error message a > few times, when I used the wrong channel. What is your sdptool output? > Mine is below. Have you tried channel 13 or 14 instead? Mine looks exactly the same, channel 13 gives an error, 14 just hangs (phone gives the usual error) > I also got this when the bluetooth stack on the phone (or PC) was in a > bad state, which seems to happen after a while when you trigger a lot of > 'Sync errors'. Try restarting the phone. Did so many times :( > FWIW, I tried syncing the calendar using Nokia's software under Windows, > but since I don't have Outlook installed, it can't synchronize it.. :( Hm, will fetch a Windows box now, and look what's up there. |
|
From: Evgeni G. <sar...@di...> - 2008-02-07 14:58:31
|
On Thu, 7 Feb 2008 13:54:04 +0100 Evgeni Golov wrote: > Received an transport error: Request not successfull: 67 > > That's what I get, also on Debian unstable, libsyncml 0.45 and the > same software version on my e51, same for Calendar and Notes :( > The phone just says "Systemfehler" (german for system error). I also > tried using the USB cable, with no changes. Just to complete the confusion, I took a E65 and my old 6230i for testing. E65 fails with exactly the same error (however it has an old firmware and is not mine, so I won't update it). 6230i works fine (as long there is no keypad lock active and you use channel 11 instead of channel 10...) So what the hell is going wrong on the E-series (yeah, they do sync fine to windows :() |
|
From: Simon J. <si...@jo...> - 2008-02-07 15:35:12
|
Evgeni Golov <sar...@di...> writes: > (yeah, they do sync fine to windows :() I just tried syncing in iSync on Mac OS X, and it can synchronize calendar and contacts too. When I synchronize both using opensync and isync, I get lots of duplicates in the contacts, but that may be the duplicate filtering logic in opensync that is broken. /Simon |
|
From: Michael B. <mic...@cm...> - 2008-02-07 16:11:20
Attachments:
smime.p7s
|
Evgeni Golov schrieb: > On Thu, 7 Feb 2008 13:54:04 +0100 Evgeni Golov wrote: > >> Received an transport error: Request not successfull: 67 >> >> That's what I get, also on Debian unstable, libsyncml 0.45 and the >> same software version on my e51, same for Calendar and Notes :( >> The phone just says "Systemfehler" (german for system error). I also >> tried using the USB cable, with no changes. > > Just to complete the confusion, I took a E65 and my old 6230i for > testing. > E65 fails with exactly the same error (however it has an old firmware > and is not mine, so I won't update it). > 6230i works fine (as long there is no keypad lock active and you use > channel 11 instead of channel 10...) > > So what the hell is going wrong on the E-series (yeah, they do sync > fine to windows :() The new Nokia phones support SyncML 1.2 and 1.1 whilst the old phones understand 1.1 only. The question is now how robust or failure tolerant are the different implementations? My M600i from Sony Ericsson is some kind of really sensible if I make small mistakes in the code - like don't sending the last package if the mobile sends no map (I fixed this today) - then the phone reports an error. This is a totally correct behaviour. The old phone which only implement 1.1 are sometimes more tolerant. Finally which protocol version do your mobiles use? BTW does the 6230i support NumberOfChanges? I discovered another bug related to this today. Even if a phone reports SupportNumberOfChanges then it only MAY send NumberOfChanges but the server MUST send it (OMA DS 1.2 Section 9 Two-Way Sync). Additionally three parallel threads are not always helpful ;) Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Christian H. <Chr...@co...> - 2008-02-07 15:06:34
|
Simon Josefsson schrieb: >> That's what I get, also on Debian unstable, libsyncml 0.45 and the >> same software version on my e51, same for Calendar and Notes :( >> The phone just says "Systemfehler" (german for system error). I also >> tried using the USB cable, with no changes. Could you try with setting the Nokia Language to english? I remember there was some discussion on this... Christian -- Christian Hilgers |ConSol* Tel. +49.2102.994-423 |Consulting&Solutions Software GmbH Fax +49.2102.994-411 |Berliner Str. 101, 40880 Ratingen email: Chr...@co... |WWW: http://www.consol.de |
|
From: Evgeni G. <sar...@di...> - 2008-02-07 15:16:30
|
On Thu, 07 Feb 2008 16:06:18 +0100 Christian Hilgers wrote: > Could you try with setting the Nokia Language to english? > I remember there was some discussion on this... Tried so, "System error"... Same on a N95 :/ |
|
From: Michael B. <mic...@cm...> - 2008-02-07 16:01:06
Attachments:
smime.p7s
|
Simon Josefsson schrieb: > Michael Bell <mic...@cm...> writes: > >>> Could the vformat problem explain why calendar syncing doesn't work, >>> when contact syncing works? >> Yes, I have myself heavy problems with OCS. Our vformat code creates >> several duplicates with the same UIDs internally. OCS detects this and >> returns errors while normal contact syncing works. > > Would this result in 'ERROR' in trace logs? I enabled tracing, but I > don't see any errors in those logs. The problem seems to be on the > phone, which fails and disconnects. This is not a library error and so this can happen without a big ERROR in the trace logs. > I've searched for this problem a bit, and it seems to happen to a lot of > people, even with Nokia's own software. And as far as I can tell, only > when syncing the calendar. So I do suspect it is a phone bug after all. > I'll see if I can find a Windows machine and test syncing on it. > > What worries me is that others have been able to work around this bug by > erasing their entire calendar and starting from scratch, but I can't > even get one simple calendar entry to sync properly. Those people > typically end up with 'Sync Error' after a few sync's though, and have > to erase the calendar again. Empty calenders could be a problem until today for OpenSync's syncml plugin. I discovered a bug which can cause problems when there are no changes. Now the OMA DS client and server code is more separated. > It doesn't build: > > /home/jas/src/libsyncml/tools/syncml-http-server.c: In function ‘main’: > /home/jas/src/libsyncml/tools/syncml-http-server.c:369: error: ‘SmlTransportHttpServerConfig’ has no member named ‘interface’ Sorry, I commited in libsyncml/trunk/libsyncml and so the tools directory was not commited. You are only missing one line ... Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Simon J. <si...@jo...> - 2008-02-07 17:38:40
|
Michael Bell <mic...@cm...> writes: >> I've searched for this problem a bit, and it seems to happen to a lot of >> people, even with Nokia's own software. And as far as I can tell, only >> when syncing the calendar. So I do suspect it is a phone bug after all. >> I'll see if I can find a Windows machine and test syncing on it. >> >> What worries me is that others have been able to work around this bug by >> erasing their entire calendar and starting from scratch, but I can't >> even get one simple calendar entry to sync properly. Those people >> typically end up with 'Sync Error' after a few sync's though, and have >> to erase the calendar again. > > Empty calenders could be a problem until today for OpenSync's syncml > plugin. I discovered a bug which can cause problems when there are no > changes. Now the OMA DS client and server code is more separated. That may have fixed the problem for me, although my calendar wasn't empty... I think I tried libsyncml from svn before, without success. >> It doesn't build: >> >> /home/jas/src/libsyncml/tools/syncml-http-server.c: In function ‘main’: >> /home/jas/src/libsyncml/tools/syncml-http-server.c:369: error: ‘SmlTransportHttpServerConfig’ has no member named ‘interface’ > > Sorry, I commited in libsyncml/trunk/libsyncml and so the tools > directory was not commited. You are only missing one line ... Works fine now. I even got calendar to work. Next step is to get msynctool/opensync to do sane syncing. /Simon |
|
From: Simon J. <si...@jo...> - 2008-02-07 16:54:09
|
Simon Josefsson <si...@jo...> writes: > jas@mocca:~$ /usr/local/bin/syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" --dumpinfo I got it working! Building latest libsyncml from svn, the above command works, see below. msynctool doesn't work reliably, and conflict handling seems very weird (I get tons of duplicates), but at least I can now read out both the entire list of contacts and calendar from my E51. Evgeni, which libsyncml version are you using? Build it from svn was relatively easy, in case you haven't tried it already. I don't understand why our E51 with the same software version behave differently though. /Simon connection with device succeeded Received an Alert for the DS Server at Calendar: Type: 200, Last 20080207T164937Z, Next 20080207T165100Z Slowsyncing Just received a new session with ID 1 Session 1 reported final. flushing Received an reply to our Alert Going to receive 23 changes Session 1 reported final. flushing Received a added entry 8 of size 302 and type text/x-vcalendar Data: BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT UID:lC5jWD6o4EEig56AwF8ca1 SUMMARY:Gris DTSTART:20080208T110000Z DTEND:20080209T140000Z X-EPOCAGENDAENTRYTYPE:APPOINTMENT CLASS:PRIVATE SEQUENCE:0 X-METHOD:NONE LAST-MODIFIED:20080207T124510Z PRIORITY:2 X-SYMBIAN-LUID:8 END:VEVENT END:VCALENDAR Received a added entry 9 of size 306 and type text/x-vcalendar ... Received an reply to our Sync: 200 Session 1 reported final. flushing Session 1 has ended |
|
From: Simon J. <si...@jo...> - 2008-02-07 18:18:46
|
Simon Josefsson <si...@jo...> writes: > Simon Josefsson <si...@jo...> writes: > >> jas@mocca:~$ /usr/local/bin/syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" --dumpinfo > > I got it working! Building latest libsyncml from svn, the above command > works, see below. Sorry, that was with libsyncml 0.4.6, not from svn. /Simon |
|
From: Simon J. <si...@jo...> - 2008-02-12 10:18:17
|
To summarize what I learned from this thread, I added some information about E51 on the following wiki's: http://opensync.org/wiki/Model_E51 http://www.opensync.org/wiki/DeviceCompatibilityList http://en.opensuse.org/OpenSync/SyncML-OBEX-Client#Nokia Thanks to everyone who helped. /Simon |
|
From: Evgeni G. <sar...@di...> - 2008-02-12 17:01:30
|
On Tue, 12 Feb 2008 11:17:59 +0100 Simon Josefsson wrote: > To summarize what I learned from this thread, I added some information > about E51 on the following wiki's: Thanks for that, as I don't have success with my e51, I wanted to ask, if you have MMSync installed on your phone? |
|
From: Simon J. <si...@jo...> - 2008-02-12 22:59:46
|
Evgeni Golov <sar...@di...> writes: > On Tue, 12 Feb 2008 11:17:59 +0100 Simon Josefsson wrote: > >> To summarize what I learned from this thread, I added some information >> about E51 on the following wiki's: > > Thanks for that, as I don't have success with my e51, I wanted to ask, > if you have MMSync installed on your phone? Yes. I installed it relatively recently, possible even while I was debugging and testing opensync. I think it was installed via the Nokia Windows software? If so, I installed that in the middle of opensync testing. Do you think it is relevant? Hm. I just removed MMSync from the phone, and syncml-obex-client 0.4.6 still works. I also tried to restart the phone, with same results. Did you also try to connect over cable? Hm. Maybe we could compare all version information, under the battery my e51 contains the following: RM-244 E51-1 pyarm-244 661v-rm244 code 0554357. Does your differ in any way? /Simon |
|
From: Simon J. <si...@jo...> - 2008-02-12 23:15:49
|
Evgeni Golov <sar...@di...> writes: > On Tue, 12 Feb 2008 11:17:59 +0100 Simon Josefsson wrote: > >> To summarize what I learned from this thread, I added some information >> about E51 on the following wiki's: > > Thanks for that, as I don't have success with my e51, I wanted to ask, > if you have MMSync installed on your phone? To test the theory that something in my phone has changed, which made opensync start working, I tried libsyncml 0.4.5. That version caused me problems before when syncing the calendar. It now works, and I can't reproduce my original libsyncml problem. So maybe installing Nokia's Windows software installed more than just MMSync? If you haven't already found a windows machine and installed the nokia software, you might want to try it. Perhaps I should try a factory reset and see if I can start from scratch... Alas, fixing all the configuration and software installations is a pain. I'll consider it when I have some time. /Simon |
|
From: Evgeni G. <sar...@di...> - 2008-03-02 22:37:09
|
Hey Simon, just for the record, it works now. But hell, don't ask me why. I played a bit today, and it gave the usual errors, then I tried the same with an openSUSE 10.3 installation and it worked. After that it worked in my Debian Sid too. Fuckin phones :/ Regards Evgeni |
|
From: Simon J. <si...@jo...> - 2008-03-02 23:03:11
|
On 2 mar 2008, at 23.37, Evgeni Golov wrote: > Hey Simon, > > just for the record, it works now. But hell, don't ask me why. > I played a bit today, and it gave the usual errors, then I tried the > same with an openSUSE 10.3 installation and it worked. After that it > worked in my Debian Sid too. Fuckin phones :/ Heh. That's similar to how I got mine working. Libsyncml didn't work initially, with any version, and then I tried other versions and tried more things, and somehow got it working. When I then tested versions I had tried before that didn't work, they worked. Now the syncing part works every time, although the rest of opensync has some bugs that prevent me from actually using it for non-debugging or non- backup purposes. I'm wondering if this is everyone's experience with the E51, or if it Just Works for everyone else and we were unlucky. /Simon |