[SyncEvolution] Sync with SailFish OS via Bluetooth
Patrick Ohly
patrick.ohly at intel.com
Mon Nov 14 20:28:11 UTC 2016
On Mon, 2016-11-14 at 20:27 +0100, deloptes wrote:
> Patrick Ohly wrote:
>
> >> How can I get a working template/config for the device
> >
> > I would start with the Nokia template.
> >
>
> This is what I did - it loops in ObexTransportAgent::wait(): iteration for
> quite some time, but I guess I have to remove PC suite parameter and who
> knows what I also have to modify.
That doesn't look good :-(
Is the phone still supported? Is it possible to see logs from the phone
side or get someone to describe how the phone is supposed to be used for
syncing via SyncML?
> >> I tried phone-setup, but the python script dies with an error.
> >
> > Which one?
> >
> > The script hasn't been used much, I suspect. The only remaining phones
> > with SyncML support were Nokia, and those typically all used the same
> > settings.
>
> syncevo-phone-config
>
> syncevo-phone-config --bt-address
> 94:XX:XX:XX:XX:8D --advanced --create-config=aquafish
> Running test with test data inside /tmp/syncevo-phone-config1_7yeN/data and
> test results inside /tmp/syncevo-phone-config1_7yeN/cache
> Starting test for 1188 configurations...
> Start 1/1188 test
> [DEBUG 00:00:00] checking password property 'databasePassword' in
> datastore 'addressbook' of config 'test-phone' with user identity ''
> [ERROR 00:00:00] addressbook: backend addressbook is ambiguous, avoid the
> alias and pick a specific backend instead directly
That error comes from not knowing whether the Evolution or TDE backend
is supposed to be used by the script. After a quick look at the script
it seems that this cannot be specified. For you, the easiest solution
probably is to disable the Evolution backends when compiling
SyncEvolution.
--
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.
More information about the SyncEvolution
mailing list