Subject: libsyncml - Teleca SyncML Client support aka. "Samsung"
Newsgroups: gmane.comp.misc.opensync.devel
Date: 2007-09-24 12:09:27 GMT (1 year, 40 weeks, 4 days, 23 hours and 11 minutes ago)
Hi, i got a Samsung D500 and started hacking on libsyncml support. I cc'ed lots of people which tried in the past to get this working - maybe some of them still interested in this topic. As already mentationed the "Teleca SyncML Client" needs hacks to get it synced with libsyncml. Indeed http://www.traud.de/gsm/samsung.htm is the best ressource about that - afaik! I spent the last weekend to get phone speaking some SyncML with me and libsyncml. Stuff which has to be done - mostly from traud.de: #1 Send "AT+CPROT=0" to start the internal OBEX server I wrote a quick n' dirty custom serial obex transport for libsyncml which sends AT+CPROT=0 in advance and starts the OBEX connection. #2 SyncML: Database path seems to be really fixed and some other odd handling is required - see: http://www.traud.de/gsm/samsungAlert.xml #3 OBEX: Final OBEX PUT must have no (end of) body header: I did some dirty PoC hacks in OpenOBEX to act like this - this isn't yet a final solution. The result of my hacks: the phone replied with at least one SyncML package :) ... and stucks again - but shouldn't be that hard to figure out the final bits which have be tuned in libsyncml to make it Teleca SyncML Client friendly. If you apply both patches to latest (svn) openobex and latest (svn) libsyncml you should be able to start a sync with the command line: syncml-obex-client -s /dev/ttyACM0 --slow-sync text/x-vcard CONTACTS --wbxml The patches are my full patchset ... there are lots of garbage implementation inside to fake the initial package 1:1 to the Teleca SyncML Client ... epically the libsyncml patchset doesn't require all changes. Actually only the serial transport stuff should be needed. Not quite sure if this kind of implementation is the correct place for libsyncml - maybe such stuff like post AT+Commands to start a OBEX Server should be part of OpenOBEX - not quite sure. I'll ask the OpenOBEX developers about that... since there are more SyncML Clients/Server which needs some post AT+ commands ... like the Ogo device and some others. The first (and last) received via libsyncml from the Samsung D500 message is attached... Please let me know if you have a Samsung Mobile and interested in getting this working with libsyncml and later with OpenSync. If you need assistance in testing the initial patch set don't hesitate to contact me. best regards, Daniel
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Opensync-devel mailing list Opensync-devel <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensync-devel