Ticket #794 (new defect)

Opened 4 months ago

Last modified 4 weeks ago

incompletely synced data records from E90 to file-sync

Reported by: zugschlus Assigned to: bellmich
Priority: high Milestone: 0.40
Component: Plugin: syncml Version: 0.36
Severity: normal Keywords: syncml, capabilities
Cc: felixmoeller

Description

Hi,

with the help of #opensync, I was finally able to get my E90 to sync with msynctool to a file-sync target. Unfortunately, the VCARD files written to the file-sync directory look different from what's on the phone.

For example, the record with my personal data on the phone has fields First Name, Last Name, Mobile, Telephone, Tel (home), a second Tel (home), E-Mail, E-Mail (home) Street (home), City (home).

When syncing, the corresponding VCARD file looks like this: 

  $ cat sync1/134
  BEGIN:VCARD
  VERSION:3.0
  N:Haber pr;Marc;;;
  REV:20080804T102300Z
  $

I had actually hoped to get at least the phone numbers synced.

I'll happily furnish any information that may be helpful in finding out what's going wrong.

Greetings Marc

Change History

08/09/08 22:22:49 changed by felixmoeller

  • cc set to felixmoeller.

please post your configuration: 

# msynctool --showgroup $yourgroup

Thank you.

(follow-up: ↓ 3 ) 08/17/08 23:24:16 changed by tuju

  • milestone changed from 0.40 to 0.38.

(in reply to: ↑ 2 ) 08/17/08 23:54:07 changed by zugschlus

Replying to tuju: I apologize for not getting back any sooner. Here is my configuration:

Group: E90 Member 1: file-sync

Configuration : <?xml version="1.0"?>

<config>

<directory>

<path>/home/mh/tmp/sync1</path> <objtype>contact</objtype> <objformat>vcard30</objformat> <converterpath_config></converterpath_config>

</directory>

<!-- <directory>

<path></path> <objtype>event</objtype> <objformat>vevent20</objformat> <converterpath_config></converterpath_config>

</directory> -->

</config>

Member 2: syncml-obex-client

Configuration : <?xml version="1.0"?>

<config>

<!-- sets the connection type to use. --> <!-- please note that actually OBEX over network is not supported --> <!-- 1 means obex over serial cable --> <!-- 2 means obex over bluetooth --> <!-- 3 means obex over IRDA --> <!-- 4 means obex over network --> <!-- 5 means obex over usb --> <type>5</type>

<!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is selected.

hcitool scan to search bluetooth devices. -->

<bluetooth_address></bluetooth_address>

<!-- (Only for bluetooth) The bluetooth channel to use.

sdptool browse $MAC to search for the correct channel Example: sdptool browse xx:xx:xx:xx:xx:xx | grep "\(Service Name\|Channel\)" -->

<bluetooth_channel></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>

<!-- Some devices use a non-standard compliant AT command.

This special AT command contains for example the datastores which should be synchronized. If you don't know what to do then leave this empy or contact us via the user mailing list.

Some devices are supported by default. If yours is not supported then please open a ticket.

Examples for AT commands:

Samsung: http://www.traud.de/gsm/samsung.htm

-->

<at_command></at_command>

<!-- If your phone needs a special AT command but you don't

know it and it is not supported but you know a similar phone which is supported then you can try to use this potentially working profile by adding this phone's identity here.

at_manufacturer is the answer to AT+CGMI. at_model is the answer to AT+CGMM.

Example: mobile Samsung SGH-Z400

at_manufacturer Samsung at_model SGH-Z400

-->

<at_manufacturer></at_manufacturer> <at_model></at_model>

<!-- 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>

<!-- If wbxml is enabled, defines wether the wbxml should use string tables --> <usestringtable>1</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 --> <maxMsgSize>0</maxMsgSize>

<maxObjSize>0</maxObjSize>

<!-- The old default behavior of OpenSync? was to use the same --> <!-- format like the connecting client. Some clients which were --> <!-- connected with another software expect always the anchor --> <!-- format of this software. Therefore it is possible to --> <!-- configure the behaviour of OpenSync?'s SyncML plugin. --> <!-- --> <!-- 0 ==> number format beginning with 1 --> <!-- 1 ==> timestamp format --> <!-- --> <!-- If it is not a SLOW-SYNC then this option is ignored and the --> <!-- behavior is determined from the cached Last anchor. -->

<useTimestampAnchor>1</useTimestampAnchor>

<!-- 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> --> <database>

<name>Contacts</name> <objtype>contact</objtype> <objformat>vcard21</objformat>

</database>

</config>

08/23/08 20:22:26 changed by dgollub

  • owner changed from dgollub to cstender.
  • component changed from OpenSync to Plugin: vformat.
  • milestone changed from 0.38 to 0.40.

Could you provide trace files? See tracing? - feel free to hide sensitive informations. Do you use any merger/capabilities features?

Could you also try to capture the syncml traffic by running: 

export SYNCML_LOG=/tmp/syncml_log/
msynctool --sync $yourgruop

And extract a complete vcard out of the syncml log ... feel free to strip sensitive information.

I guess this is related to an issue in vformat plugin.

08/24/08 19:19:24 changed by zugschlus

An msynctool --sync E90 generated like 18 MB of trace files. Is there a automated way to remove sensitive information, or to have msynctool only sync the first ten-or-so entries to avoid generate megabytes of debug information that needs to be reviewed for sensitive information?

Greetings Marc

08/31/08 01:58:50 changed by cstender

  • keywords set to syncml, capabilities.
  • owner changed from cstender to bellmich.
  • component changed from Plugin: vformat to Plugin: syncml.
  • priority changed from normal to high.

Sounds like a capabilities bug in syncml.

10/26/08 09:00:45 changed by zugschlus

I'm going to deliver traces with Opensync 0.37 as soon as ticket #874 is resolved, which is currently keeping me from using Opensync/msynctool at all. I'll delete all data from the phone and hope that the traces are shorter then.