|
From: Daniel G. <dg...@su...> - 2008-01-02 13:28:36
|
On Wednesday 02 January 2008 08:10:55 Brian Johnson wrote: > With that said, when using the > syncml-obex-client command line program, I get the following output (I > assume this is good): > > $ syncml-obex-client -u 0 --identifier "PC Suite 2" --wbxml --sync > "text/x-vMessage" Messages > connection with device succeeded > Received an Alert for the DS Server at Messages: Type: 201, Last , Next > 20080102T065600Z > Just received a new session with ID 1 > Received the DevInf > Session 1 reported final. flushing Interesting. You changed the profile on your mobile to "PC Suite 2" right? Didn't know that there is a relation.. i wonder how determine the available profiles... Could you try --slow-sync instead of --sync as well .. this should get all message (not only the latest one). Just to proof that it's working... > I did notice that the phone responds when using the "text/x-vMessage" mime > type on syncml-obex-client, and I do not know if objtype = data, objformat > = plain corresponds to text/plain, but I somehow need to get msynctool to > use text/x-vMessage. Correct, currently there handling of this mimetype is missing. Actually we should provide another field (e.g. <mimetype>) and drop the <objtype> field. <objtype> isn't needed since the <objformat> is mapped to one objtype already (redundancy). Anyway, i just did an untested hack to just hardcode text/x-vMessage for <objformat> plain, for testing purposes. best regards, Daniel |