Difference between revisions of "C+ Dav Synergy Connector"
(Created page with "The legacy synergy connectors were not open sourced, so we had to create our own. CalDav and CardDav are now the standards with the broadest server support for syncing calenda...") |
|||
| Line 71: | Line 71: | ||
# Go to Impostah => Acitivities, select "Service persistent" in the first field | # Go to Impostah => Acitivities, select "Service persistent" in the first field | ||
# Look for acitivites with "org.webosports.cdav" in their name, select them and remember their activityIds. | # Look for acitivites with "org.webosports.cdav" in their name, select them and remember their activityIds. | ||
| − | # For each of those ids run this command from the command line: | + | # For each of those ids run this command from the command line (replace X with the activityId!): |
| − | luna-send -n 1 -a org.webosports.cdav.service palm://com.palm.activitymanager/cancel '{"activityId": X}' | + | luna-send -n 1 -a org.webosports.cdav.service palm://com.palm.activitymanager/cancel '{"activityId": X}' |
These steps are only necessary if something goes horribly wrong and make sure you have a clean start without visiting the doctor. Otherwise you might have phantom events/contacts and activities remaining in the database. Usually all of this should happen automatically. But there might be bugs in those procedures. | These steps are only necessary if something goes horribly wrong and make sure you have a clean start without visiting the doctor. Otherwise you might have phantom events/contacts and activities remaining in the database. Usually all of this should happen automatically. But there might be bugs in those procedures. | ||
| − | + | == Change log == | |
| − | + | [Changelog|https://github.com/webOS-ports/org.webosports.service.contacts.carddav/blob/master/ChangeLog] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 10:22, 27 June 2014
The legacy synergy connectors were not open sourced, so we had to create our own. CalDav and CardDav are now the standards with the broadest server support for syncing calendars and contacts, so we created a synergy connector for them. An incomplete list of servers supporting caldav and carddav:
- ownCloud
- iCloud
- Yahoo
- eGroupware
- SoGo
Important notes
webOS 2.1.1 and 2.1.2
Only webOS 2.2.4 and webOS 3.0.5 (and LunesOS) are supported. If you have a Veer with 2.1.X, you can try to patch your sync framework to the version of 2.2.4. It worked for me on my Veer that currently is my daily driver. It might have side effects on other synergy connectors, though.
Sync fix for stable upload
Also, please tripple check that you do not have the patch "System: Sync fix for stable upload" installed. It WILL run the connector in an endless loop eating up all your battery and your data volume quite fast!
First sync
The first sync can last very long, especially if the account has many entries on the server and the connection is not very stable. Please leave it for some time, best would be overnight on a good WiFi.
Status of the Software
Two-way sync of contacts and calendar events is implemented. Multiple calendars and addressbooks are supported and will be automatically discovered. The calendars will also show up in webOS, so you can define different colors for them.
A complex mechanism for auto discovery is implemented. Servers are probed for a lot of different options. That "should" make configuration a bit easier. Additionally there are multiple account templates for popular services like iCloud, Google or Yahoo where you do not have to worry about finding the right URL.
There is a C+Dav app that has some functionality, you can trigger a "slow" sync, a discovery and also manually trigger the synchronization. This is only for convenience.
How-Too
Installation
Install the software fitting your device either using Preware, Quick Install or palm-install. I strongly advise first to test the downsync only version with new servers. Personally I only test on ownCloud, currently. All others are more or less untested.
Configuration
After installation go to the Accounts app on your device and create a new account. You'll see a bunch of new account templates starting with "C+DAV". Select one of those matching your service or the general one. If there is a special account for your server, please use it. It will make your life much easier.
In the next scene fill in all fields. For the generic one the URL is the most important one. If the server type is known and can be detected (for example the URL includes owncloud), then the software will take care of finding the right URL. If not, you need to supply an URL that "speaks" webdav (carddav and caldav rely on webdav), so we can use it to check the credentials and ask it for the users principal and home folders. For most servers it is not necessary to give a full calendar URL or something. Some examples:
- owncloud: https://server/path_to_owncloud/remote.php/caldav
- egroupware: https://server/path_to_egroupware/groupdav.php
If credentials are correct, you can create the account. webOS will now try to sync your data. Sometimes this fails on the initial sync. You can manually (re-)trigger a sync using the calendar or contacts app or the C+Dav app. If that brings up all your data, you are fine and can test more functions.
Account templates =
The account templates exist for two reasons. On the one hand they make configuration easier on the other hand webOS does not allow multiple accounts of the same type with the same username, which can get a bit nasty if you use your e-mail address on multiple services. There are currently a number of account templates:
- Google: This uses OAuth2.0 authorization (including support for two factor authorization), which is required for calendars now. Calendar & Contacts should work.
- iCloud: Testing is hard, because it seems I can't create a free iCloud account. No known issues, though.
- Yahoo: The servers are strange. Calendar & Contacts should be working.
Trouble shooting
If anything goes wrong, please contact me ( garfonso at mobo.info ) and maybe already attach a log.
Sending logs
Logging goes to the system log ( in /var/log/messages ). You can watch the log using Lumberjack. Please use a custom filter for "cdav". The nicest way is to select "Follow log" and then trigger a sync or discovery where I can see the errors (probably by creating events / contacts, if you have issues with upsync). Another possibility is to copy the file from the device and cut the relevant parts from it or use the command line like this:
cat /var/log/messages | grep cdav > /media/internal/cdav.log
This will create a cdav.log file in your media partition which you can e-mail me.
Clean the device
If you want to clean your device, please follow these steps in the right order:
- Delete all c+dav accounts in the device manager
- Reboot the device
- Uninstall the c+dav connector (for example via Software manager)
- Use Impostah to clean the on device database, to do this, start Impostah, select databases, then on the upper field select "Persistent".
- From the second list first select org.webosports.cdav.account.config and then select "Delete all" from the app menu.
- Do the same for org.webosports.cdav.account.calendar and org.webosports.cdav.account.contacts.
- After that, do the same for the other org.webosports.cdav.* you find in the list
- Go to Impostah => Acitivities, select "Service persistent" in the first field
- Look for acitivites with "org.webosports.cdav" in their name, select them and remember their activityIds.
- For each of those ids run this command from the command line (replace X with the activityId!):
luna-send -n 1 -a org.webosports.cdav.service palm://com.palm.activitymanager/cancel '{"activityId": X}'
These steps are only necessary if something goes horribly wrong and make sure you have a clean start without visiting the doctor. Otherwise you might have phantom events/contacts and activities remaining in the database. Usually all of this should happen automatically. But there might be bugs in those procedures.
Change log
[Changelog|https://github.com/webOS-ports/org.webosports.service.contacts.carddav/blob/master/ChangeLog]