Calendar2Server

Power Users

Supported replication patterns

• Android calendars to a single .ics payload upload target.
• Android calendars to a CalDAV collection overwrite target.
• Multiple selected calendars merged into one destination profile.

Runtime architecture

• Calendar provider reader for permitted calendar/event access.
• Sync engine for iCalendar transformation and transfer.
• Background scheduler for automatic runs.
• Secure credential storage and local diagnostics logs.

Important behavior

• One-way only: the app does not write back to source Android calendars.
• Scheduled execution timing is best-effort, not guaranteed to exact minute timing.
• CalDAV overwrite mode replaces remote collection contents.

ICS upload target

• Generates one VCALENDAR payload for selected events.
• POST supports multipart/form-data upload or raw text/calendar.
• PUT uses raw text/calendar.
• Authentication modes: none, basic, and bearer.

CalDAV replicate target

• Discovers existing resources via REPORT with tolerated fallback to PROPFIND.
• Deletes discovered non-collection resources.
• Uploads generated per-event ICS resources.
• This is replace behavior, not incremental patch merge.

Power-user best practices

• Start with manual-only profiles and validate output against a test destination.
• Test CalDAV overwrite on non-production collections before production use.
• Prefer attendee/description stripping unless explicitly required.
• Use Wi-Fi + charging constraints for larger sync windows.
• Review logs periodically when tuning schedule behavior and retries.