On Do, 2010-10-21 at 23:17 +0100, Callum Macdonald wrote:
Patrick Ohly <patrick.ohly@...> writes:
> As Tino said, Your problem sounds exactly like the issue in the commit
> above, which should have been solved in 1.0.99.7. Can you double-check
> that the data that is sent to the phone as part of updating a contact
> does not contain the X-EVOLUTION-SLOT parameter?
>
You're exactly right. It was that problem. I had another problem (data
corruption on the phone) which threw me off. However, for anyone else finding
this in the future, I did have to run `syncevolution --remove <config>` first.
Then, I was able to create a new sync profile with the type "Nokia" and it
worked fine.
The only effect of recreating the config is that it'll do a slow sync
directly after recreating the config. The same effect can be achieved on
the command line with "syncevolution --sync slow <config>", without
recreating the config. "--sync refresh-from-server" may also help (wipes
out data on the phone and copies it from the computer).
Can I report success on a Nokia E52 somehow on the wiki?
Sure, please do. See
http://syncevolution.org/wiki/phone-compatibility-template
--
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.