On Mon, 2012-06-04 at 14:34 +0200, Bleck wrote: Such problems are not uncommon, but this particular combination seems new. You can run a "--sync refesh-from-local loglevel=4 funambol" with the SyncEvolution command line and check the resulting log file in ~/.cache/syncevolution to see whether the missing phone number was sent to the Funambol server. If it was, then you need to continue your investigations there and/or in the sync between Android and Funambol server. SyncEvolution itself should support the TYPE=CELL;TYPE=PREF combination. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Mon, 2012-06-04 at 17:33 +0200, Bleck wrote: It's plain C++ internally. What you need to watch out for is the part where the original vCard gets encoded again as vCard, based on the internal representation. Basically search for the last occurrence of your telephone number. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.