Re: [SyncEvolution] "No working configuration found"
On Fri, 2010-07-09 at 07:51 +0100, Ansgar Machalický wrote:
Hi Patrick, hi all,
I'm back on the issue and tried to set up my phone with the template for
a w595.
Am Montag, den 05.07.2010, 15:59 +0200 schrieb Patrick Ohly:
> Try setting up the phone with the template in
> http://syncevolution.org/wiki/sony-ericsson-w595
>
> For that simply copy the content of the text box into a local
> ~/.config/syncevolution-templates/w595.ini file, then use either the
> command line or the sync-UI to set it up.
That folder did not exist. Shouldn't it?
No.
Anyway, I've copied the
template to that folder after making it, but using the UI this template
doesn't show up.
Argh, it's not "consumerReady". Sorry for that. Obviously the whole
syncevo-phone-config => Wiki => user process still has teething issues.
Add consumerReady to the config.ini part as follows and it'll show up in
the sync-ui:
=== config.ini ===
peerIsClient = 1
remoteIdentifier = PC Suite
consumerReady = 1
We could ask the users to set that flag in the syncevo-phone-config
output once they are satisfied with the quality of syncing, but I doubt
that this would work in practice.
Should the flag be added by syncevo-phone-config right away? I think so,
because a user who downloads the template does so in order to use it,
regardless whether it is ready or not (which we haven't defined anyway
for phones).
I created an issue to track this:
http://bugs.meego.com/show_bug.cgi?id=3803
*********************************************************
ansgar@ThinkPad:~$ syncevolution --template ?
That's for SyncML servers. "syncevolution template ?W595" (or any other
device name) will look for device templates.
The '--configure --template "Sony Ericsson W595" --sync-property
syncURL=obex-bt://<mac address> w595' will create the config.
--
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.