|
|
2010-01-13
, 06:41
|
|
Posts: 162 |
Thanked: 25 times |
Joined on Dec 2009
|
#2
|
|
|
2010-01-13
, 10:39
|
|
Posts: 3 |
Thanked: 11 times |
Joined on Aug 2007
|
#4
|
|
|
2010-01-13
, 11:38
|
|
Posts: 40 |
Thanked: 43 times |
Joined on Oct 2008
|
#5
|
Can you, or somebody else confirm that this will work with a local Linux PC without a detour in the cloud, before I go to the trouble of installing that stuff?
Paai
| The Following User Says Thank You to tarek For This Useful Post: | ||
|
|
2010-01-13
, 11:48
|
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#6
|
Can you, or somebody else confirm that this will work with a local Linux PC without a detour in the cloud, before I go to the trouble of installing that stuff?
| The Following User Says Thank You to benny1967 For This Useful Post: | ||
|
|
2010-01-13
, 12:22
|
|
Posts: 42 |
Thanked: 16 times |
Joined on Jan 2010
|
#7
|
For some reason or another I always get confused when I read about syncevolution, syncml and similar. What I /want/ is a solution for syncing the N900 with my local Linux PC running Evolution or Kontakt (the KDE counterpart). But what I find is syncing with some remote cloud service like Google, Funambol or so.
Can you, or somebody else confirm that this will work with a local Linux PC without a detour in the cloud, before I go to the trouble of installing that stuff?
Paai
|
|
2010-01-13
, 13:31
|
|
Posts: 3 |
Thanked: 3 times |
Joined on Dec 2009
|
#8
|
$ syncevolution funambol ... [INFO] CurlTransport Failure: couldn't connect to host
user ~ $ syncevolution -p --quiet funambol syncURL = http://my.funambol.com/sync username = bolle password = - # logdir = # loglevel = 0 # printChanges = 1 # maxlogdirs = 10 # useProxy = 0 # proxyHost = # proxyUsername = # proxyPassword = # clientAuthType = md5 # RetryDuration = 300 # RetryInterval = 60 deviceId = sc-pim-172db7c2-8edb-4ed2-b869-1b1f0a46072a enableWBXML = 1 # maxMsgSize = 20000 # maxObjSize = 4000000 # enableCompression = 0 # SSLServerCertificates = # SSLVerifyServer = 1 # SSLVerifyHost = 1 WebURL = http://my.funambol.com # IconURI = ConsumerReady = 1 [addressbook] sync = disabled type = addressbook # evolutionsource = uri = card # evolutionuser = # evolutionpassword = [calendar] sync = two-way type = calendar:text/calendar! # evolutionsource = uri = event # evolutionuser = # evolutionpassword = [memo] sync = disabled type = memo # evolutionsource = uri = note # evolutionuser = # evolutionpassword = [todo] sync = disabled type = todo:text/calendar! # evolutionsource = uri = task # evolutionuser = # evolutionpassword =
|
|
2010-01-13
, 20:10
|
|
Posts: 150 |
Thanked: 91 times |
Joined on Dec 2009
@ Norway
|
#10
|
| The Following User Says Thank You to hstende For This Useful Post: | ||
![]() |
| Tags |
| calendar sync, maemo 5 |
|
There is lots of information on getting syncevolution working, but I can't find one with a unified guide of how to get it running with N900. As a disclaimer, this is not for the faint of heart. I hope somebody soon comes along who makes the process friendly, but it requires a modest amount of knowledge at this point.
1. Download syncevolution for N900 by adding the following repo:
.config/syncevolution/sync1/config.ini
# the base URL of the SyncML server which is to be used for SyncML; # some examples: # - http://my.funambol.com/sync # - http://sync.scheduleworld.com/funambol/ds # - http://www.synthesis.ch/sync syncURL = http://sync.scheduleworld.com/funambol/ds # user name used for authorization with the SyncML server username = [yourusername] # password used for authorization with the SyncML server; # in addition to specifying it directly as plain text, it can # also be read from the standard input or from an environment # variable of your choice: # plain text: password = <insert your password here> # ask: password = - # env variable: password = ${<name of environment variable>} password = [yourpassword] # full path to directory where automatic backups and logs # are stored for all synchronizations; if empty, the temporary # directory "$TMPDIR/SyncEvolution-<username>-<server>" will # be used to keep the data of just the latest synchronization run; # if "none", then no backups of the databases are made and any # output is printed directly to the screen # logdir = # level of detail for log messages: # - 0 (or unset) = INFO messages without log file, DEBUG with log file # - 1 = only ERROR messages # - 2 = also INFO messages # - 3 = also DEBUG messages # loglevel = 0 # Unless this option is set, SyncEvolution will never delete # anything in the "logdir". If set, the oldest directories and # all their content will be removed after a successful sync # to prevent the number of log directories from growing beyond # the given limit. # maxlogdirs = 0 # set to T to enable an HTTP proxy useProxy = 0 # proxy URL (http://<host>:<port>) # proxyHost = # authentication for proxy: username # proxyUsername = # proxy password, can be specified in different ways, # see SyncML server password for details # proxyPassword = # - empty or "md5" for secure method (recommended) # - "basic" for insecure method # clientAuthType = syncml:auth-md5 # The SyncML server gets this string and will use it to keep track of # changes that still need to be synchronized with this particular # client; it must be set to something unique (like the pseudo-random # string created automatically for new configurations) among all clients # accessing the same server. # myFUNAMBOL also requires that the string starts with sc-pim- deviceId = sc-n900 # Support for large objects and limiting the message size was added in # SyncEvolution 0.5, but still disabled in the example configurations # of that version. Some servers had problems with that configuration, # so now both features are enabled by default and it is recommended # to update existing configurations. # # The maximum size of each message can be set (maxMsgSize) and the # server can be told to never sent items larger than a certain # threshold (maxObjSize). Presumably the server has to truncate or # skip larger items. Finally the client and server may be given the # permission to transmit large items in multiple messages (loSupport = # large object support). maxMsgSize = 0 # maxObjSize = 500000 # loSupport = 1 # enable compression of network traffic (not currently supported) # enableCompression = 0 # A string specifying the location of the certificates # used to authenticate the server. When empty, the # system's default location will be searched. # SSLServerCertificates = # The client refuses to establish the connection unless # the server presents a valid certificate. Disabling this # option considerably reduces the security of SSL # (man-in-the-middle attacks become possible) and is not # recommended. # SSLVerifyServer = 1 # The client refuses to establish the connection unless the # server's certificate matches its host name. In cases where # the certificate still seems to be valid it might make sense # to disable this option and allow such connections. # SSLVerifyHost = 1.config/syncevolution/sync1/sources/addressbook/config.ini
.config/syncevolution/sync1/sources/calendar/config.ini
.config/syncevolution/sync1/sources/todo/config.ini
You should be able to initiate the command now with:
Last edited by chemist; 2010-05-10 at 14:48.