On Mon, May 10, 2010 at 21:48, Dmitry Teslenko <[email protected]> wrote: > ---------- Forwarded message ---------- > From: Dmitry Teslenko <[email protected]> > Date: Mon, May 10, 2010 at 21:48 > Subject: Re: [SyncEvolution] syncing nokia series 40 phones > To: Patrick Ohly <[email protected]> > > > On Mon, May 10, 2010 at 10:05, Patrick Ohly <[email protected]> wrote: >> On Mon, 2010-05-10 at 06:37 +0100, Dmitry Teslenko wrote: >>> Hello! >>> Does anybody have luck syncing with nokia series 40 phone (nokia 3500 >>> for example) via bluetooth? >> >> Yes, the Nokia 7120c is a S40 and works. >> >>> I'm using syncevolution 1.0 beta3. >>> >>> I run syncevo-phone-config for first time and it could pick any >> >> "could not"? >> >>> working configuration, however it could write following items: >>> * contact >>> * note >>> * todo >> >> Sorry, I don't follow. >> >> Can you try to setup the phone using "--template 'Nokia 7210c'" and then >> sync the "addressbook"? >> >> In which sync modes does that work ("--sync refresh-from-server", >> "--sync refresh-from-client", "--sync two-way")? >> >> >> -- >> 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. >> >> >> > > > Ok, I've done so: > syncevolution --configure --template "Nokia 7210c" --sync-property > syncURL=obex-bt://00:1E:A3:F1:18:53 phone > syncevolution --sync refresh-from-server phone addressbook > syncevolution --sync refresh-from-client phone addressbook > syncevolution --sync two-way phone addressbook > > All results were the same: > > [INFO] Server sending SAN > [ERROR] OBEX Request 2 got a failed response Forbidden > [INFO] Server sending SAN > [ERROR] OBEX Request 3 got a failed response Not found > [ERROR] ObexTransprotAgent: Underlying transport error > Changes applied during synchronization: > +---------------|-----------------------|-----------------------|-CON-+ > | | LOCAL | REMOTE | FLI | > | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > | addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > | start Mon May 10 21:43:12 2010, duration 0:04min | > | external transport failure (local, status 20043) | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > First ERROR encountered: OBEX Request 2 got a failed response Forbidden > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? >
I've managed to configure addressbook sync. I've done: --sync-property "remoteIdentifier=PC Suite" --sync-property "SyncMLVersion=1.1" --source-property "type=addressbook:text/x-vcard" notes and calendar+todo syncs now too. I've noticed I have to restart my phone time to time to make sync work. In some cases syncevolution prints "[ERROR] OBEX Request 3 got a failed response Not found" and don't sync but after phone restart it works fine. Big thanks to Patrick Ohly for great software. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
