Calendar sources
Via the calendar you can take over sessions from an ICS file and share your own sessions as calendar data. File import and export work without network access. In addition, you can subscribe to a calendar link.
Importing a file
Under Calendar, open the entry Calendar sources via ⋯ and choose Import ICS file. The device's file picker opens after you have chosen or named a source. For this, create a named source, such as "University timetable". The source name has 1 to 80 characters and contains no URL or line breaks. When you later read in a new file of the same calendar, choose the same source. Only within this source does Sapeluno recognise the same sessions again. Identical titles or file names do not merge sessions.
Before the import you see the period, the count and warnings. Unsupported or invalid entries are left out with a reason. Check the preview before you confirm the import. If you cancel, nothing is taken over; a new source, too, is saved only with the confirmed import. For a series without a fixed end, the displayed import boundary is decisive.
Supported are single and all-day sessions, weekly and fortnightly series as well as cancellations and moves of individual sessions. The file must use UTF-8 and be at most 1 MiB in size. Per file, at most 1,000 event entries and 2,000 recurrence days in total apply; supported dates lie between 1900 and 2200, and a session or series spans at most 3,660 days. A session with a time may run past midnight if it ends on the next day before its start time, that is, if it is shorter than 24 hours; it is taken over as described in Sessions past midnight and written with the next day as its end on export. More complex recurrence rules, durations instead of an end time, invitation messages and timed sessions that last 24 hours or longer cannot be taken over. The preview reports such entries. Descriptions, private session notes, attachments, invitations and embedded reminders are not taken over from the file. A calendar import confirms no registration and takes over no grades or complete course materials.
Checking time and time zone
For sessions with a time zone, the time of the source time zone is kept. A session at 10:00 in Europe/Berlin appears as 10:00 in the calendar; a UTC session keeps its UTC time. The app does not secretly convert this display to the device's time zone. The origin names the source time zone. All-day sessions keep their date.
If the time zone is missing, you must explicitly confirm that the given times are to be treated as local times. Times or rules that cannot be represented safely are reported in the preview.
Reading the same source again
Choose the existing source when you read in an updated file. An unchanged file creates no additional sessions. Title, room and series changes are compared with the last state of the source. Your own changes are kept; the origin shows your own values and source values separately. Session notes and tasks stay linked to the session. If the source changes the time or time zone of a series with existing exceptions, the app keeps the previous series state as a precaution and shows the new source values as a conflict. This way, your own or earlier exceptions are not assigned to a wrong original session.
If an old session is missing from the new file, it is not deleted or cancelled automatically. An explicitly delivered cancellation is separate from this. An invalid entry is no reason either to delete a previously imported session. If the file contains rejected entries, the app marks no old session as missing, as a precaution. Valid entries can still be updated. Changes to the source or your own data between preview and confirmation can make a new preview necessary.
Undoing an import
The source shows its imports. For the last still active import you can check and confirm an undo. The preview shows affected sessions and later changes.
Sapeluno reverts only import changes that have remained unchanged. Sessions edited later or sessions with your own content created since then are protected; they are kept, if necessary without a link to the source. The undo is therefore not a blanket deletion of all imported sessions. Check the preview and the result, especially if you have added session notes or tasks in the meantime.
Exporting your own sessions
Select the own sessions you want to share. Imported sessions are not part of this selection. The preview states the scope. Task deadlines, session notes, grades and attachments are not included in this step. The shared calendar text may be at most 256 KiB in size. If the selection becomes too large, share fewer sessions at once. Only your confirmation opens the device's share picker; you choose the recipient yourself.
Your own sessions have no fixed time zone. The export therefore passes their times on as local times. The receiving calendar app can display them according to its own settings. One-off multi-day blocks are written out as individual days with stable identifiers so that later individual changes remain assigned. A calendar export is not a complete backup.
Subscribing to a calendar
Under Calendar → ⋯ → Calendar sources → Subscribe to calendar you enter
a name and the private HTTPS link of your calendar. A webcal:// link is
fetched as HTTPS. Choose the import period and check the preview. For
sessions without a time zone, you confirm the displayed time assumption. The
calendar provider receives a connection from your device in the process;
Sapeluno uploads none of your own notes, tasks or grades.
After confirmation, changes are taken over automatically: roughly every six hours while an internet connection exists, and also when the app is opened if a fetch is due. Android can delay background fetches; after "Force stop" you have to open the app again. Below the source you see the last attempt, the last successful fetch and possible errors. Refresh now fetches immediately. Without internet, the last state remains available; it may then no longer be up to date.
Your own changes and linked session notes are kept. In case of conflicts, the session shows your own values and the source values. Explicit cancellations are taken over; a session that is no longer delivered is not deleted automatically. Invalid calendars do not change the previous state. The chosen period is not extended silently: Replace link or extend period opens a new preview for this.
You can pause automatic fetches and resume them. End subscription removes the link and keeps the sessions. Because this cannot be undone, the app asks first; to follow the calendar again, you need the link anew. If you undo an import, the automatic fetching pauses too. Check the state before you resume it.
Private calendar links are stored protected on the device. They are not part of the backup. After a restore, even on the same device, you must enter the links again and confirm the preview. Supported are HTTPS links without a separate sign-in; redirects to other providers are not followed automatically.
