Bug 91943 - sync with SyncML-Server (like www.mobical.net)
Summary: sync with SyncML-Server (like www.mobical.net)
Status: CONFIRMED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-23 10:40 UTC by Konstantin Sysel
Modified: 2021-03-10 20:05 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-5227-0.html (5.23 KB, text/html)
2021-03-10 20:05 UTC, Nikolai Försterling
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Sysel 2004-10-23 10:40:22 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    SuSE RPMs
OS:                Linux

I want to sync my contacts, my calendar and to-do-list with a SyncML-Server like www.mobical.net, so that i can sync my mobilephone with.
Comment 1 automailer 2004-11-16 11:17:39 UTC
Definite one. SyncML ist the standard in many newer phones and syning my phone/pda with my groupware is a prime productivity issue...
Comment 2 Niklas Zimmermann 2005-07-24 20:16:12 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Andreas Schallenberg 2008-11-09 15:21:35 UTC
I think this is an issue of increasing importance for industrial use
of KDE. Funambol would be another example for a server.
Comment 4 Nikolai Försterling 2009-01-13 17:15:09 UTC
The sync thing already works with Kontact and eGroupware, you can also sync your WM-phone with the funambol-client to/from eGroupware.
Just a few issues/limitations described here:
http://bugs.kde.org/show_bug.cgi?id=180564
Comment 5 François Rey 2009-07-05 13:49:45 UTC
Anyone interested in having a KDE centralized sync tool should vote for this wish:
https://bugs.kde.org/show_bug.cgi?id=107681
I put my vote behind this wish. However it does not seem to be adressing the need for direct sync with a pda/phone device, only with a syncml server.

On that other wish mentioned above I made a comment that talks about Sync Evolution because it's on the way to become a more feature rich tool
(direct sync and server sync) thanks to intel funding its developer Patrick
Ohly (see
http://www.estamos.de/blog/2009/05/13/syncevolution-09-beta-1-full-time-project-using-synthesis-syncml-engine/).
"While the project is currently mostly targeting Moblin+Evolution, it was
always meant to be open for other contributions", quoted from
http://www.estamos.de/blog/2009/07/01/gran-canaria-desktop-summit-2009-talk-about-syncevolution/

So how about joining forces and taking advantage of the momentum?
I'm putting my vote behind this and hope others will follow...
Comment 6 at 2011-09-26 18:54:07 UTC
together with the Funambol-Server Akunambol should do the job:
https://projects.kde.org/akunambol

For my needs Funambol is overkill - I'd prefer to use syncEvolution's builtin syncevo-http-server 
check the last comment: (In reply to comment #5)
> https://bugs.kde.org/show_bug.cgi?id=107681
Comment 7 Justin Zobel 2021-03-09 05:46:48 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 8 Nikolai Försterling 2021-03-10 20:05:08 UTC
Created attachment 136568 [details]
attachment-5227-0.html

Hi,

for quite some time i use syncthing on my Linux desktops as well as my Android phone and 
additionally KDE Connect for data exchange.
I gave up finding a proper solution for syncing addresses, phone numbers and calendar events, 
thus no longer wish for a solution via SyncML

BR


Am Dienstag, 9. März 2021, 06:46:48 CET schrieb Justin Zobel:
> https://bugs.kde.org/show_bug.cgi?id=91943
> 
> --- Comment #7 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for the bug report.
> 
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm that the issue still persists.
> 
> If this bug is no longer persisting or relevant please change the status to
> resolved.