Re: [SyncEvolution] Nokia N85 sync status

>> 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: > I'm not sure how how to test this... What is an example problem I > should be looking for? I'd try to compare the CTCap that libsynthesis is sending to the Nokia (with showctcapproperties=yes) with the devInf the Nokia sends back. That will probably show what's different. If you have traces (best would be 1:1 WBXML message dumps) of these two cases, please just send them to me so I can have a look. As there are already some mechanisms to make Nokia devices happy, it might need only a little tweak in the engine to catch the N85 et. al. as well.