On Do, 2011-01-20 at 00:51 +0000, Kip Warner wrote:
On Mon, 2011-01-17 at 09:24 +0100, Patrick Ohly wrote:
> Note that SyncEvolution automatically finds the right channel. There
> should never be a need to specify it explicitly.
Hey Patrick. If I remove the explicit channel specifier from the
bluetooth address in the syncURL field, I get the following while being
prompted on the phone to accept a connection and hitting yes...
$ syncevolution nokia_e71
[INFO] todo: inactive
[INFO] memo: inactive
[INFO] calendar+todo: inactive
[INFO] calendar: inactive
[INFO] Server sending SAN
[ERROR] OBEX Request 3 got a failed response Forbidden
[INFO] Server sending SAN
[ERROR] OBEX Request 3 got a failed response Forbidden
[ERROR] ObexTransprotAgent: Underlying transport error
Synchronization failed,
see /home/kip/.cache/syncevolution/nokia__e71-2011-01-19-16-48/syncevolution-log.html for
I'm afraid the phone simply refuses to talk to us. There's no
information available explaining why. You could try with enabling
"calendar+todo" instead or perhaps in addition to "addressbook".
If all fails, you might try the syncevo-phone-config script. Be prepared
to loose your data on the phone if you do!
syncevo-phone-config --bt-address <BT MacAddress> \
--advanced --create-config nokia_e71_auto
This will do a lot of trial-and-error attempts to sync. Somehow I doubt
that it'll work, because Nokia phones tend to be very consistent about
using the same parameters, which is what is in the default Nokia
template already.
--
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.