Hi Jussi, On Feb 15, 2010, at 23:49 , Jussi Kukkonen wrote:
> 2. Addressbook sync itself seems to work but there is a major problem: the > vcards from the phone contain very little data: no phone number or email for > example. This is bug #8868. PC Suite snooping may be required before fixing. This might be due to the device not understanding the CTCap correctly. We had that with other Nokias some time ago. I added the (debug aid only) <showctcapproperties>no</showctcapproperties> config option (place it within <server>) then, which globally suppresses sending any CTCap. With this, the Nokias did send all fields, along with their own devInf, which then can be compared with the devInf we would send. If I remember correctly, Nokia did (does?) expect a strange way of representing the possible TYPE enum values (as <property> rather than <valenum>, depending on SyncML version. See comment in mimedirprofile.cpp:4637: > // For some older 1.1 devices (in particular Nokia 7610), enum > values of default params > // in pre-MIME-DIR must be shown as param NAMES (not enums). > // But newer 1.2 Nokias like E90 need proper TYPE param with > valEnums (when run in 1.2 mode. E90 is fine with 7610 style for 1.1) > // So: normally (fEnumDefaultPropParams==undefined==-1), we > show 7610 style for 1.1 and E90 style for 1.2. > // <enumdefaultpropparams> and ENUMDEFAULTPROPPARAMS() can be > used to control this behaviour when needed > So, depending on the time the device queries the server devinf (before or after it gets the device's devInf and can possibly apply remote rules), the <enumdefaultpropparams> remote rule option might help here. Best Regards, Lukas Zeller ([email protected]) - Synthesis AG, SyncML Solutions & Sustainable Software Concepts [email protected], http://www.synthesis.ch _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
