[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-13 Thread Max Pyziur
On Thu, 13 Jan 2022, Emanoil wrote: Am Wednesday 12 January 2022 23:14:27 schrieb Max Pyziur: < HTTP/1.1 404 Not Found < Soup-Debug-Timestamp: 1642025460 < Soup-Debug: SoupMessage 1 (0xccd8a0) < Date: Wed, 12 Jan 2022 22:11:00 GMT < Server: Apache < X-Frame-Options: DENY <

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-12 Thread Max Pyziur
On Wed, 12 Jan 2022, Milan Crha wrote: On Wed, 2022-01-12 at 08:03 -0500, Max Pyziur wrote: get.c gcc -o get get.c `pkg-config --cflags --libs libsoup-2.4` Hi, everything after 'gcc', including the 'gcc' itself, is means to be a separate command, thus: $ curl . >get.c $ gcc

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-12 Thread Milan Crha
On Wed, 2022-01-12 at 08:03 -0500, Max Pyziur wrote: > >get.c gcc -o get get.c `pkg-config --cflags --libs libsoup-2.4` Hi, everything after 'gcc', including the 'gcc' itself, is means to be a separate command, thus: $ curl . >get.c $ gcc -o get `pkg-config --cflags --libs

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-12 Thread Max Pyziur
On Wed, 12 Jan 2022, Patrick Ohly wrote: Max Pyziur writes: this is coming from ./src/syncevo/SoupTransportAgent.cpp in void SoupTransportAgent::HandleSessionCallback(SoupSession *session, SoupMessage *msg) what is the linked version of soap you

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-11 Thread Patrick Ohly
Max Pyziur writes: >> this is coming from ./src/syncevo/SoupTransportAgent.cpp in >> void SoupTransportAgent::HandleSessionCallback(SoupSession *session, >> SoupMessage *msg) >> >> what is the linked version of soap you have on your side >> >> $ ldd

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-11 Thread Max Pyziur
On Tue, 11 Jan 2022, Emanoil wrote: Hi, I am not sure if someone is reading here and I have no idea what you are doing, because I am using the bluetooth side of SyncEvolution. However I think if you run with more debugging, you will get more information about the error. Something like:

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-11 Thread Max Pyziur
On Tue, 11 Jan 2022, Patrick Ohly wrote: Max Pyziur writes: On Tue, 11 Jan 2022, Patrick Ohly wrote: Max Pyziur writes: I have replicated it below (earlier email), and have tried syncing via SyncEvolution with KeepContacts. However, no KeepContacts connection is made with SyncEvolution.

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-11 Thread Patrick Ohly
Max Pyziur writes: > On Tue, 11 Jan 2022, Patrick Ohly wrote: > >> Max Pyziur writes: >>> I have replicated it below (earlier email), and have tried syncing via >>> SyncEvolution with KeepContacts. However, no KeepContacts connection is >>> made with SyncEvolution. >> >> What error do you get?

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-11 Thread Max Pyziur
On Tue, 11 Jan 2022, Patrick Ohly wrote: Max Pyziur writes: Greetings, Apologies for yanking my own thread here. I just want to have my another option open. I have contacted Support at KeepContacts regarding the recommended SyncEvolution configuration. They said that it should be exactly

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-11 Thread Patrick Ohly
Max Pyziur writes: > Greetings, > > Apologies for yanking my own thread here. I just want to have my another > option open. > > I have contacted Support at KeepContacts regarding the recommended > SyncEvolution configuration. > > They said that it should be exactly the same as Mobical (note

[SyncEvolution] Re: Syncing a New Android phone (Samsung A52) w KeepContacts

2022-01-10 Thread Max Pyziur
Greetings, Apologies for yanking my own thread here. I just want to have my another option open. I have contacted Support at KeepContacts regarding the recommended SyncEvolution configuration. They said that it should be exactly the same as Mobical (note that Mobical is part of the