Menu
▾
▴
opensync-users
|
From: Nicholas P. <nic...@ni...> - 2008-01-07 18:33:15
|
I hope this isn't too off-topic. I'd like to copy the messages (SMS, MMS, some in folders, some in the INBOX) to my PC from Nokia N73 S60 phone. Has anyone used SyncML to do this? The Windows PC Suite backup fails to back them up, and the on-phone 'Backup' facility fails too (with an out-of-memory error.) Thanks and regards, Nick |
|
From: Brian J. <br...@do...> - 2008-01-07 19:15:42
|
Nick, I am only able to backup my SMS messages to my computer using the PC Suite software. I'm not sure if backing up MMS is possible. Two things you might want to try doing: 1. Update your phone's software (Nokia has provided a Nokia Software Update tool to assist with this process) 2. Update your PC Suite software and/or the Nokia Connectivity Cable driver (in Windows) Currently I do not believe it is possible that we can back up anything other than regular text messages (SMS) because the sync profile on the phone does not have the capability of doing anything other than contacts, calendar, notes, bookmarks, etc. I am currently playing with opensync to see if it is possible to synchronize text messages, however, I think I am close, but am not having much luck. I will respond to the mailing list if I do get it working. - Brian On Mon, January 7, 2008 10:33 am, Nicholas Piper wrote: > I hope this isn't too off-topic. > > > I'd like to copy the messages (SMS, MMS, some in folders, some in the > INBOX) to my PC from Nokia N73 S60 phone. > > > Has anyone used SyncML to do this? The Windows PC Suite backup fails > to back them up, and the on-phone 'Backup' facility fails too (with an > out-of-memory error.) > > Thanks and regards, > > > Nick > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl > ace _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users > > |
|
From: Daniel G. <dg...@su...> - 2008-01-07 19:24:43
|
On Montag 07 Januar 2008, Brian Johnson wrote: > I am currently playing with opensync to see if it is possible to > synchronize text messages, however, I think I am close, but am not having > much luck. I will respond to the mailing list if I do get it working. It's up to the device. Just check the device capabilities of the device. Unfortunately there is currently no easy way to gain those information with any application based on libsyncml. The most "easiest" way would be to just use syncml-obex-client and trigger a regular sync with a known to work mimetype (like. text/x-vcard) and additionally call syncml-obex-client with --devinfo. This will force the device to send the capabilities of the device. Set SYNCML_LOG and check the recievced-*.xml files for CTCap or similar nodes. Look for entries like: text/x-vMessage If you find text/x-vMessage or somehihng simliar just try: syncml-obex-client --slow-sync text/x-vMessages RandomLocalDatabaseName .... This likely only works for Series 60. Good luck. best regards, Daniel |
|
From: Nicholas P. <nic...@ni...> - 2008-01-08 00:52:14
|
Daniel, On Mon, 07 Jan 2008, Daniel Gollub wrote: > On Montag 07 Januar 2008, Brian Johnson wrote: > > I am currently playing with opensync to see if it is possible to > > synchronize text messages, however, I think I am close, but am not having > > much luck. I will respond to the mailing list if I do get it working. > It's up to the device. Just check the device capabilities of the device. > Unfortunately there is currently no easy way to gain those information with > any application based on libsyncml. The most "easiest" way would be to just > use syncml-obex-client and trigger a regular sync with a known to work > mimetype (like. text/x-vcard) and additionally call syncml-obex-client > with --devinfo. This will force the device to send the capabilities of the > device. Set SYNCML_LOG and check the recievced-*.xml files for CTCap or > similar nodes. Look for entries like: It looks like CTCap for me only shows the mimetypes of the databases I've selected already, so I can't discover new ones this way. What I did learn today, is that the S60 --identifier is not matching the phone synchronisation profile name, but actually the "Host address"! > text/x-vMessage > > If you find text/x-vMessage or somehihng simliar just try: > > syncml-obex-client --slow-sync text/x-vMessages RandomLocalDatabaseName .... I think "syncml-obex-client --identifier 'my sync' -b 00:19:79:CE:B8:FD 10 --wbxml --sync text/x-vMessages sms" may work, however the phone just shows "Connecting" for ages. I think maybe I have too many entries on the phone? I cleared the INBOX into folders, but maybe it still uses those (I hope so, actually.) Eventually the sync with text/x-vMessages shows "Operation time-out" on the handset. The received-0.xml log is at http://pastebin.com/m200e5897 (ignore the − parts, sorry.) I can't delete all the messages to try with a cleaner handset, because I can't back them up... However, for syncing more types of my content, "Lifeblog" seems to be a database on the phone with MMS, photos, SMS, etc. etc. I just don't know what mimetype to use in the obex-client? I tried "application/atom+xml" and "application/x.atom+xml", as well as text/xml, application/xml, etc. Maybe I need to set up Lifeblog on a Windows PC and sniff a sync with that. Nick |
|
From: Daniel G. <dg...@su...> - 2008-01-08 08:23:30
|
On Dienstag 08 Januar 2008, Nicholas Piper wrote: > It looks like CTCap for me only shows the mimetypes of the databases > I've selected already, so I can't discover new ones this way. > > What I did learn today, is that the S60 --identifier is not matching > the phone synchronisation profile name, but actually the "Host > address"! Arg, yes - that could be as well.. since the latest syncml-obex-client might already send it's own capailities in advance. SyncML Spec says that the device then only should reply supported capabilities by the device... Not quite sure if syncml-obex-client is already sending the (own) entire capabilities in advance or not.. it's up to your version of libsyncml. Michael Bell that recently lots of development in this area ... we need have to introduce finally same proper discovery function for syncml-obex-client tool (and OpenSync plugin). Not quite sure how hard this is to implement. > > > text/x-vMessage > > > > If you find text/x-vMessage or somehihng simliar just try: > > > > syncml-obex-client --slow-sync text/x-vMessages RandomLocalDatabaseName > > .... > > I think "syncml-obex-client --identifier 'my sync' -b > 00:19:79:CE:B8:FD 10 --wbxml --sync text/x-vMessages sms" may work, > however the phone just shows "Connecting" for ages. I think maybe I > have too many entries on the phone? I cleared the INBOX into folders, > but maybe it still uses those (I hope so, actually.) > > Eventually the sync with text/x-vMessages shows "Operation time-out" > on the handset. The received-0.xml log is at > http://pastebin.com/m200e5897 (ignore the − parts, sorry.) Looks interesting... could you check SYNCML_TRACE as well.. might me that the xml parser or assembler fails and libsyncml fails to recover from the parser/assmebler error... > > I can't delete all the messages to try with a cleaner handset, because > I can't back them up... Does libsyncml send at least another package back to the device? Is there an sent-N+1.xml? > > However, for syncing more types of my content, "Lifeblog" seems to be > a database on the phone with MMS, photos, SMS, etc. etc. I just don't > know what mimetype to use in the obex-client? > > I tried "application/atom+xml" and "application/x.atom+xml", as well > as text/xml, application/xml, etc. > > Maybe I need to set up Lifeblog on a Windows PC and sniff a sync with > that. This would help for sure... best regards, Daniel |
|
From: Michael B. <mic...@cm...> - 2008-01-08 11:00:00
Attachments:
smime.p7s
|
Daniel Gollub schrieb: > Arg, yes - that could be as well.. since the latest syncml-obex-client might > already send it's own capailities in advance. SyncML Spec says that the > device then only should reply supported capabilities by the device... Why should this happen? > Not quite sure if syncml-obex-client is already sending the (own) entire > capabilities in advance or not.. it's up to your version of libsyncml. > Michael Bell that recently lots of development in this area ... we need have > to introduce finally same proper discovery function for syncml-obex-client > tool (and OpenSync plugin). Not quite sure how hard this is to implement. The syncml-obex-client is in fact a SyncML server according to the protocol. The name is a little bit misleading. I can only test the http stuff and here always the SyncML client sends the first DevInf. I use SyncML over http over bluetooth and sniff it with wireshark. If you do this with OBEX instead of http then you should see which sends the first devinf. 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: Daniel G. <dg...@su...> - 2008-01-08 11:10:31
|
On Dienstag 08 Januar 2008, Michael Bell wrote: > > Arg, yes - that could be as well.. since the latest syncml-obex-client > > might already send it's own capailities in advance. SyncML Spec says that > > the device then only should reply supported capabilities by the device... > > Why should this happen? AFAIK, syncml-obex-client has hardcoded datasore support for text/x-vcard, text/x-vcalendar and text/plain. If those got set with --slow-sync or --sync say got set as preferred type. Shouldn't be that enough that libsyncml would send the capabilities in advnance.. not quite sure about the latest changes in libsyncml. I have to take a look on that... > > > Not quite sure if syncml-obex-client is already sending the (own) entire > > capabilities in advance or not.. it's up to your version of libsyncml. > > Michael Bell that recently lots of development in this area ... we need > > have to introduce finally same proper discovery function for > > syncml-obex-client tool (and OpenSync plugin). Not quite sure how hard > > this is to implement. > > The syncml-obex-client is in fact a SyncML server according to the > protocol. The name is a little bit misleading. I can only test the http > stuff and here always the SyncML client sends the first DevInf. Yeah the naming is indeed confusing, it's more related to the transport role. The actually correct name would be: syncml-server-obex-client Maybe we should rename the process and the plugin. Same for the http transport plugins... to sum it up it would be possible to have: syncml-client-obex-client syncml-server-obex-client (aka. syncml-obex-client) syncml-client-http-client (aka. syncml-http-client) syncml-server-http-server (aka. syncml-http-server) Correct? best regards, Daniel |
Thanks for helping keep SourceForge clean.
X