Difference between revisions of "CalDAV-Sync account settings"
Line 1: | Line 1: | ||
+ | This is the CalDAV-Sync account settings help. If you don't know what some of these options mean you should probably stick to the defaults. | ||
+ | |||
+ | Unless otherwise noted, all options apply to '''SmoothSync''' as well. | ||
+ | |||
== Help == | == Help == | ||
Revision as of 07:15, 8 June 2012
This is the CalDAV-Sync account settings help. If you don't know what some of these options mean you should probably stick to the defaults.
Unless otherwise noted, all options apply to SmoothSync as well.
Contents
Help
- Get help
- Open this wiki page.
Server settings
- Select calendars to sync
- Use this setting if you want to change the selected calendars or you created new calendars on the server that you want to sync. You can change calendar colors and names here or reset them to the values on the server (if any).
Advanced options
- Use preemptive authentication
- Enable preemptive authentication. Preemptive authentication causes the app to send BASIC authentication headers with every request. If your server accepts BASIC authentication this will reduce the number of round-trips and sync much faster (especially on SSL). Please note, this will send your password unencrypted over the wire (if you don't use SSL), even if your server does not accept BASIC authentication. With SSL this option should be safe to use. Don't enable this option if your server doesn't accept BASIC authentication.
- Fake user-agent
- This option changes the user-agent the app uses. If you were able to setup the account without this option, then you don't need it.
Sync direction
- One-Way-Sync
- This option disables Two-Way-Sync. Only server modifications are considered during sync, modifications on the phone don't get synced to the server.
Sync interval
- Periodic auto sync
- This enables an automatic sync on a regular base.
- Sync interval
- Sets the time between two automatic syncs.
- Enable long term sync
- Enables long term sync. In contrast to a regular sync long term sync allows to sync larger time ranges. To prevent unnecessary traffic and safe battery this will be done on larger intervals.
- Long term sync interval
- Sets the time between two automatic long term syncs.
Sync range
Note 1: modifications on the phone will always be synced to the server, no matter when a created/modified/removed event starts. The sync range is only relevant for the direction server to phone.
Note 2: some buggy servers violate the CalDAV specifications and return less events than they should actually, e.g. older versions of SabreDAV and ownCloud don't report recurring events that start before the past sync range.
- Sync past events up to
- The number of weeks to sync in the past. Earlier events won't be fetched from the server. Recurring events that start earlier will be synced if at least one instance is in the sync range.
- Sync future events up to
- The number of weeks to sync in the future. Later events won't be fetched from the server.
Long term sync range
This is the same as Sync range just for long-term syncs
- Sync past events up to
- The number of months or year to sync in the past.
- Sync future events up to
- The number of months or year to sync in the future.
Date service settings
These options allow to specify on which connection types the app may sync. The app checks the connection type on each sync and won't sync if the current connection is not enabled here.
Global settings
- Enable error reports
- This option enables error reports during sync. If there is any error it will show a notification with an option to send a bug report. Error conditions may happen for many reasons and not all of them are bugs actually (for example if the app can not sync due to bad connectivity). Please consider to read the article about sync errors and possible reasons to see what might have caused a certain error report (not all reports may be caused by bugs in my app, they may be caused by server bugs as well).
- Report connection errors
- This option enables the reporting of connectivity issues. It is meant to debug connectivity issues. Connection errors are not considered to be bugs in CardDAV-Sync. Please do not send occasional bug reports about connectivity issues. If you get many connection errors read connection errors.
- You should not enable this option if everything works fine.
Compatibility options
- Remove 0s alarms
- This option will remove alarms that are set to 0 minutes. This is necessary on some buggy devices that set alarms to zero instead of removing them.
- Fix tentative event state
- This option will set new events to confirmed when syncing them to the server. Some buggy calendar apps create all events tentative
- Enforce DTEND field
- This option will always create events with a DTEND field and will never use DURATION. Enable this option if you're syncing to an Oracle Convergence server.
Experimental features
- Sync attendees
- Enable attendee and organizer sync. This option is experimental since it needs more testing and a few improvements. Anyway, it may already do it's job for many users.
- Sync on display switch-on
- Let the app sync when the display is switched on. Please note that if you're using power saving techniques or battery extender apps that disable your data connection, this might cause a lot of connection errors. The app will wait up to 30 seconds for the device to signal a working data connection, but even when the device signals a working connection it may take a few seconds until the connection has recovered.
- This option will sync at most once in 5 minutes to prevent excessive battery drain. If you switch on the display very often you may still notice a decreased battery time.