8:43 p.m.
Hi everyone.
I'm trying to keep in sync two phones with my evolution, by using syncevolution.
My phones are a Nokia E61 and a Nokia 6220 classic. Both are S60, but E61 is
older than 6220.
It happens to me quite often that after a sync I get data duplication, most
often on the E61. The only way I found to get rid of such duplication would be
to sync one-way from the server to the phone and then to re-sync immediately,
again one-way, from the phone to the server. In such a way, the next two-way
sync would work.
But after such an adjustment, there will be very likely the same problem with
the second phone, so to recover I will have to do the same with the second
phone. And this will lead to problems with the first, and so on.
In brief, the only way to keep all in order is to sync two-way one phone and
one-way the other. Therefore I can never change my PIM data from the phone which
I sync one way: such changes wuould be lost at the first sync.
I'm not sure whether this is a regression: I do remember that everything looked
fine before the last two versions of syncevolution, even though I had other
problems (which are described in the wiki).
Anyone has ever tested syncing with two different phones?
Thank you very much
Giancarlo
9:19 p.m.
On Mo, 2010-11-08 at 09:43 +0000, Giancarlo wrote:
I'm trying to keep in sync two phones with my evolution, by using
syncevolution.
My phones are a Nokia E61 and a Nokia 6220 classic. Both are S60, but E61 is
older than 6220.
It happens to me quite often that after a sync I get data duplication, most
often on the E61. The only way I found to get rid of such duplication would be
to sync one-way from the server to the phone and then to re-sync immediately,
again one-way, from the phone to the server. In such a way, the next two-way
sync would work.
It is not clear to me why you need a "refresh-from-client" sync
immediately after the "refresh-from-server". Everything should be ready
for a normal two-way sync after "refresh-from-server". What happens if
you don't do the "refresh-from-client"?
But after such an adjustment, there will be very likely the same
problem with
the second phone, so to recover I will have to do the same with the second
phone. And this will lead to problems with the first, and so on.
The problem with "refresh-from-client" is that it wipes out all data on
the server. The next sync with your other phone therefore has to delete
all contacts on that phone, which will lead to conflicts if that data
was modified there in the meantime.
In brief, the only way to keep all in order is to sync two-way one
phone and
one-way the other. Therefore I can never change my PIM data from the phone which
I sync one way: such changes wuould be lost at the first sync.
I'm not sure whether this is a regression: I do remember that everything looked
fine before the last two versions of syncevolution, even though I had other
problems (which are described in the wiki).
Anyone has ever tested syncing with two different phones?
I haven't tested it much, but it should work as far as SyncEvolution is
concerned.
--
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.
11:24 p.m.
Il 08/11/2010 11:19, Patrick Ohly ha scritto:
On Mo, 2010-11-08 at 09:43 +0000, Giancarlo wrote:
> I'm trying to keep in sync two phones with my evolution, by using syncevolution.
>
> My phones are a Nokia E61 and a Nokia 6220 classic. Both are S60, but E61 is
> older than 6220.
>
> It happens to me quite often that after a sync I get data duplication, most
> often on the E61. The only way I found to get rid of such duplication would be
> to sync one-way from the server to the phone and then to re-sync immediately,
> again one-way, from the phone to the server. In such a way, the next two-way
> sync would work.
>
It is not clear to me why you need a "refresh-from-client" sync
immediately after the "refresh-from-server". Everything should be ready
for a normal two-way sync after "refresh-from-server". What happens if
you don't do the "refresh-from-client"?
I'm sorry for not being clear enough.
Yes, I meant
a "refresh-from-client" sync
immediately after the "refresh-from-server"
If I don't do this, after the refresh-from-server the next two-way will
duplicate all the entries.
This is definitely strange but it does happen.
> But after such an adjustment, there will be very likely the same
problem with
> the second phone, so to recover I will have to do the same with the second
> phone. And this will lead to problems with the first, and so on.
>
The problem with "refresh-from-client" is that it wipes out all data on
the server. The next sync with your other phone therefore has to delete
all contacts on that phone, which will lead to conflicts if that data
was modified there in the meantime.
Yes I fully understand that. And I agree, this is a crazy way to sync.
> In brief, the only way to keep all in order is to sync two-way
one phone and
> one-way the other. Therefore I can never change my PIM data from the phone which
> I sync one way: such changes wuould be lost at the first sync.
>
> I'm not sure whether this is a regression: I do remember that everything looked
> fine before the last two versions of syncevolution, even though I had other
> problems (which are described in the wiki).
>
> Anyone has ever tested syncing with two different phones?
>
I haven't tested it much, but it should work as far as SyncEvolution is
concerned.
Yes, it seems to be a problem arising due to some interaction between
the synchronization process and the two phones, which belong to two
different generations of S60.
Please note that I'm definitely one of the worst cases you can ever
meet: my data, during almost 10 years, have passed through two different
Palm PDAs, two HPs (actually the first was a Compaq), 3 Nokia. Therefore
the data might have extremely strange entries due to the different formats.
On the pc side, I used the Palm conduit under Linux for the Palm's,
SynCE for the HP's, opensync and finally syncevolution for the 3 Nokia's.
Now I'm expecting a final solution from MeeGo, as soon as it comes out
on a phone.
I cannot fix everything by hand, so I have to rely on robust software.
Thank you for your help.
giancarlo
--
--
-------------------------------------------------
Dr. Giancarlo Iannizzotto, PhD
Associate Professor
DiSIA - Dipartimento di Scienze per l'Ingegneria e per l'Architettura,
Faculty of Engineering,
University of Messina - ITALY -
http://visilab.unime.it/~ianni
elm: ianni(a)ingegneria.unime.it
elm: ianni(a)visilab.unime.it
PGP PUBLIC KEY: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF1A96309
phone: +39 0903977327 ---
--------------------------------------------------
"Let us leave this God of Pointland to the ignorant
fruition of his omnipresence and omniscience:
nothing that you or I can do can rescue him from
his self-satisfaction." Flatland, Section 20.
--------------------------------------------------
5:08 a.m.
Giancarlo Iannizzotto <ianni@...> writes:
> It is not clear to me why you need a
"refresh-from-client" sync
> immediately after the "refresh-from-server". Everything should be ready
> for a normal two-way sync after "refresh-from-server". What happens if
> you don't do the "refresh-from-client"?
>
>
Sorry for replying to my own email: I just want to be more clear.
The issue I described above does not appear _always_ but just sometimes-
I would say, often. I could not understand why it happens.
When the problem does not show up, then the two-way sync works for both phones.
When it shows up, then I get this ping-pong and it goes on for a while,
then it disappears after a number of refresh-from-server and
refresh-from-client syncs.
I'm still trying to recognise a pattern in this behaviour.
I also tried to turn off and on the phones after one-way syncing, with no
changes. Also shutting down the dbus server did not change the situation.
But I should better investigate whether something changes if restart the PC
after a one-way sync: this might indicate that the evolution server (or
something else) needs a restart after a one-way sync.
Don't ask me why.
giancarlo
6:07 p.m.
On Di, 2010-11-09 at 18:08 +0000, Giancarlo wrote:
Giancarlo Iannizzotto <ianni@...> writes:
> > It is not clear to me why you need a "refresh-from-client" sync
> > immediately after the "refresh-from-server". Everything should be
ready
> > for a normal two-way sync after "refresh-from-server". What happens
if
> > you don't do the "refresh-from-client"?
> >
> >
Sorry for replying to my own email: I just want to be more clear.
The issue I described above does not appear _always_ but just sometimes-
I would say, often. I could not understand why it happens.
When the problem does not show up, then the two-way sync works for both phones.
When it shows up, then I get this ping-pong and it goes on for a while,
then it disappears after a number of refresh-from-server and
refresh-from-client syncs.
I'm still trying to recognise a pattern in this behaviour.
I suggest that you disable deleting of session directories (with
maxlogdirs=0) and enable more detailed logging (with loglevel=4) for
both phones. Then when something happens, it is possible to review the
logs, both from the session where a problem was noticed and the previous
one.
--
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.
4330
days inactive
4332
days old
syncevolution@synevolution.org
4 comments
3 participants
participants (3)
-
Giancarlo -
Giancarlo Iannizzotto
-
Patrick Ohly