The webical itself is not deleted

The app uses a self-created parser which more. More complex features supported than the iCalendar parsers of other applications. – Imports appointments, alarms and attendees directly from iCal files (*. Ics) and applications. – Imports appointments, alarms and participants directly from Microsoft calendar files (*. Vcs) and applications. – Export appointments, alarms and attendees stored on the device to iCal files (*. Ics). – Take a quick look at the appointments stored in iCal files without importing them. – Updates old and new appointments from iCal file. – iCalendar files are connected in this app. – Time zone are fully supported. Supports creation. Removal of calendars from the device. – Finger-friendly interface – loading, parsing and importing iCal files directly from the Internet from various sources. – The app supports self-created certificates. – Supports synchronization to and from a server that provides calendar information using HTTP / HTTPS (WebDAV for two-way sync). – Supports synchronization to and from a server that provides calendar information using the CalDAV protocol. – Easy and fast configuration by an automated finding of your calendars at the server (CalDAV) – Supports synchronization from and to a server which offers calendar information with the FTP / FTPS protocol. – Supports downloading / handling webcal / webcals feeds. – Background sync of calendar information. – Automatic background syncs can be triggered periodically by the app itself or it can be started by external apps like Tasker. – Search for updates. – Logging, no secrets. See at any time what is happening and why – Supports self-signed certificates and certificate-based client\server authentication – Advanced filtering of information – Supports devices with multiple CPU cores and allows faster processing, download, etc. Of calendar data. – Multiple languages: Currently German, English, Spanish and French. – If you are interested in translating the app into other languages, please contact me.

Interesting features for bulk orders:

– Configure and distribute server connections automated by adb, webpages, emails, etc. – Configure general settings through adb, websites, emails, etc. Distribute configurations quickly to your users. Protect it from changes. – Special licensing techniques

Requirements:

Android 2.2 or newer.

Note :

If you have a list of information z.B. A list of iCalendar (.Ics) files, try to press with your fingers longer on an element. Then you get in most cases a context.Menu in which you can then select a specific matching action.

Initial configuration:

Most of the time Android based devices use more than one calendar. The app therefore allows to define a calendar with which the appointments should be synchronized. To do this, please use the options. If the user does not select a calendar and still starts the import of calendar information, the app will automatically select one, if possible.

Basic synchronization flow:

The app always uses two steps. Firstly the analysis step (Process WebiCals resp. Process local files). During this step it will try to find calendar information z.B. The app will ask you to select a file or (depending on the configuration) will download another calendar information from the network by itself. After that the information will be parsed/analyzed. After that prepared for import. The information that went through the analysis step can now be imported in the import step (Import button). For some network calendars (WebiCals) both steps are done in a single process. An additional start of the import step is then no longer necessary.

Dummy Sync Account:

The app will automatically create a dummy sync account when you use the app to create a new calendar. This sync account will be linked to the created calendar, preventing Android from removing the calendar on its own. If you press this button, all active WebiCals will be analyzed. The network calendars stored there will be edited. Depending on the configuration of WebiCals, either only appointments are downloaded and analyzed which can be imported afterwards or (if you use WebiCals with active two way sync option) it will also analyze changes to and from the device resp. Transfer server. An additional start of the import step is then no longer necessary with such WebiCals.

Analyze local files:

To work with iCalendar information, you need to analyze it beforehand. By pressing the button you can open an iCalendar (.Ics) file on your Android device or on the Internet. After you have analyzed some information, the import button will be available. You can also view the analyzed information by selecting the "Analyzed data" button, in the menu.

Import:

After you have analyzed information, it can be imported by pressing this button. Depending on your configuration, the information will be imported in different ways and to a different calendar. You can find more information in the options section of this guide.

Export Appointments:

If you press this button, the app will export all the events stored in your calendar (you can select a specific calendar to export in the options). The calendar will be exported to a file with the name (CalendarName).Icalendarbackup.(DateAndTime).Ics, which will be stored in the CalendarSync folder on your phone.

Show log information:

Here you can see a list of all status messages produced by the application. These are used to debug the app and you can run the app "while working" watch if you are interested. You can also save the log files by pressing the "Save log" button press. These are stored in a folder called CalendarSync on your phone and have the name Log.(DateAndTime).Txt. You can also send me the current log. After that I can analyze the log information regarding possible problems. To do this, press the "Send log information to developer" button.

How to parse/import a local iCalendar (.Ics) file:

By pressing the "Analyze" button buttons, select a file using the context menu to parse it. After that please press the import button. It is also possible that you open the files directly such as.B. Music files. To do this, you must send the file similar to z.B. Simply open an MP3 in your favorite file explorer. After you have clicked on the file, my app will be suggested to process the file further. With my app, you can also z.B. Open and process email attachments directly.

Calendar management:

They can also use my app to create new calendars on their device. You can access this function by pressing the menu button on the main screen and selecting the "Calendar management" option Select button. These calendars can then be used for the synchronization of z.B. Webicals are used. The created calendars are independent from Google. Appointments in these calendars are not transferred to Google servers! The calendars created are independent of Google. Appointments in these calendars are not transferred to Google Server!

How do I synchronize with a calendar data source from the Internet:

You have to define a WebiCal for your server (calendar data source in a network like the Internet). This works if you press the menu button. Then the function "Create new WebiCal" select. If your server is a web server, use HTTP/HTTPS as the source type. If you use a CalDAV server, please use CalDAV. If you use a FTP server, please use FTP/FTPS. After that, you can use the "Process WebiCals Press the button in the main window or you can call the context menu on the WebiCals overview. Afterwards please press the "Import Button. With CalDAV/FTP/WebDAV it is not only possible to transfer calendar data to the device but changes on the device can also be transferred back to the server. If the two way sync is activated, the import will be done automatically during the processing of the WebiCals.

How to link already existing appointments with a WebiCal:

Already existing appointments can be assigned to any WebiCal of the app (a WebiCal is always a configured external calendar data source, z.B. A calendar on a server). Select Assign appointments. The appointments are then assigned to this WebiCal. At the next synchronization to be transferred to your server. The appointments are then assigned to this WebiCal. Transferred to their server during the next synchronization process.

How to configure automatic synchronization:

There are two ways to use CalendarSync to automatically synchronize different Internet sources. First of all always configure the internet sources, you can find information about this above. Both types of sync take place in the background without user interaction. To do this, you need to enable automatic synchronization in the option settings. Select an automatic sync period. If you select a period of one hour, the app will synchronize all defined and active internet sources every hour. In order to use this mode, the device must be restarted once after activating the option. For this you need to use an app like "Tasker" have installed. Allow in the options the "External auto sync" Option. This app can now start CalendarSync to synchronize your defined internet sources. According to a user of Tasker, the following configuration works: Add a "send intent (under "Other") with: Action = com.Icalparse.Autosync.Serviceautosync Extra = com.Icalparse.Force:true Target: Service

The Llama app can also be used in this way. For this create an entry with Intentmode:Start Service, Packetname:com.Icalparse, class name:com.Icalparse.Autosync.Serviceautosync and an extra entry with the keyname force (type bool) which is set to true. Attention: For the test version of the app a different package name must be used. Therefore instead of com.Icalparse please com.Icalparse.Use free, the rest of the settings remain the same. You can also combine the two options of automatic synchronization.

Set synchronization interval for automatic synchronization:

The app supports two types of synchronization intervals. First the global synchronization interval which can be set in the app settings (option group: AutoSync). This is used by default by each WebiCal. Additionally, this global setting can be overridden for each WebiCal individually if z.B. Calendar data source every hours. The other one should be synchronized every day. To do this start the app> Press menu button> Show created WebiCals> Long press on the respective WebiCal (list entry) and select Edit. Scroll down a bit and there you can choose an individual synchronization interval or you can decide to use the global interval again. Additionally the WebiCals can be excluded completely, but a manual sync is still possible.

What are WebiCals:

Webicals are used to define internet sources for your calendar information. If you use the "Process WebiCals" button Press the button in the main window, all active WebiCals will be loaded and analyzed. Also the feature of automatic synchronization will synchronize all active WebiCals. You can also define WebiCal as inactive, so it will not be parsed automatically. By default all newly defined WebiCal are active. The setting Primary within a WebiCal also works in a similar way. This can be used if you want to synchronize multiple WebiCals with the same Android calendar. Defines on which server a new appointment added to this calendar should be stored. To set WebiCal to inactive use the Show defined WebiCals menu item and press and hold the WebiCal you want to edit.Here you can also select an inactive WebiCal from the list and analyze it using the context menu entry "Analyze" start the processing.

Explanation of some common questions about WebiCals:

Primary WebiCal – Only visible when the WebiCal is edited:

Multiple WebiCals can be configured to store appointments in the same calendar. If a new appointment is created now, it will land on the server whose WebiCal is defined as primary.

Active WebiCal – Only visible when the WebiCal is edited:

If this setting is deactivated then it will not be taken into account during manual sync of all WebiCals (Process WebiCals on main screen) and during autoamtic sync. But in the WebiCal overview the synchronization can still be triggered specifically.

Two way sync:

The two way sync is switched off by default, if it is not activated there will be no two way sync. For WebiCals where the two way sync is not active you have to click on Process WebiCals first for a manual sync. Then click on the Import button below (unless Autoimport is enabled). The automatic synchronization will of course include the WebiCal configured like this.

Connection type local file:

Use this connection type if you want to use WebiCal to connect regularly with a contact file available locally on the device (.Vcf) to synchronize. This file can then be z.B. Also be synchronized via Dropbox or other cloud apps. You must specify the path to this file in the URL field. The app will always start in /mnt/sdcard/ when searching for the path. Therefore for a file which can be found in the following path /mnt/sdcard/testfolder/test.Vcf only the following must be entered /testordner/test.Vcf. For files which are not stored under /mnt/sdcard/ the import step can be used .. (.. Goes back one step in the folder hierarchy) operator can be used to adapt the default start point. Therefore for the following path /mnt/sdcardXX/testordner/test.Ics, the following should be entered /../sdcardXX/testfolder/test.Ics. If you want to import a specific file only from time to time, it is easier to open it in your favorite file management app. Simply navigate to the file. Then click there. My app will then be suggested or even start automatically. If you start the analysis of the file. In this case with WebDAV/HTTP. FTP the complete path to the file must be specified. Example of such a URL at FTP:ftp(e)(s)://meinedomain.At/myfolder/myfile.Ics If ftps:// is specified for an FTP connection then an encrypted connection will be established using the implicit encryption mode. If ftpes:// is specified then a connection will be established using the explicit encryption mode. Example of such a URL for WebDAV/HTTP:http(s)://meinedomain.At/myfolder/myfile.Ics example of such a URL when syncing with a local file: For the connection type local file, see above. For the connection type CalDAV you can find tips for very many servers under the section CalDAV provider.

Caldav WebiCals two way sync:

If you have defined CalDAV WebiCals and you want to transfer changes from the server to the device and changes from the device to the server you have to activate the following settings in the options. When creating the WebiCal you have to check "Two way sync" must be set. When you start the Process WebiCals step, all active and appropriately configured CalDAV WebiCals will transfer the changes to the device and then the changes from the device to the servers. Since all the work is done in this step, the import step is no longer necessary.

FTP WebiCals two way sync:

If you have defined FTP WebiCals and want to transfer changes from the server to the device and changes from the device to the server you have to activate the following settings in the options. When creating the WebiCal you have to check the box "Two way sync are set. When you start the WebiCals processing step, all active and configured FTP WebiCals will transfer the changes to the device and then the changes from the device to the servers. Since all the work is done in this step, the import step is no longer necessary. The calendar file you want to synchronize with must already exist on the server! The path to the file must be specified in its full extent. Example of such a URL:ftp(s)://meinedomain.At/myfolder/myfile.Ics Please note that FTP is not designed to support multiple simultaneous/parallel changes to files. This can lead to the fact that a synchronization cannot be carried out completely if a two-way sync is carried out by different users/devices at the same time. So if you want to allow several different users to synchronize on one calendar I recommend using a CalDAV server. It is also problematic if you use properties in your appointments which are not supported by Android (e.G.B. Saving binary files in the appointments) this information can be lost.

HTTP/WEBDAV WebiCals two ways synchronization:

If you have defined HTTP/WEBDAV WebiCals and want to transfer changes from the server to the device and changes from the device to the server you have to activate the following settings in the options. When creating the WebiCal you have to check the box "Two way sync" be set. When you start the WebiCals processing step, all active and properly configured HTTP/WEBDAV WebiCals will transfer the changes to the device and then the changes from the device to the servers. Since all the work is done in the analysis step, the import step is no longer necessary. The calendar file you want to synchronize with must already exist on the server! The path to the file must be specified in full extent. Example of such a URL:http(s)://meinedomain.At/myfolder/myfile.Ics Please note that WebDAV is not intended to support various simultaneous/parallel changes to files. This can lead to the fact that a synchronization cannot be carried out completely if a two-way sync is carried out by different users/devices at the same time. So if you want to allow several different users to synchronize on one calendar I recommend to use a CalDAV server. It is also problematic if you use properties in your appointments that are not supported by Android (z.B. Storing binary files in the appointments) this information can be lost.

How can two independent calendar sources be synchronized with each other (z.B. A Google with an Exchange calendar among each other or with your own calendar server):

With the current version of the app there are two ways how this can be realized:

For the first method:

For the second method (CalendarSync connects two calendars that already exist on the device):

For the synchronization with Outlook there are several possibilities in interaction with the app with Android:

1)Outlook can use calendars as .Ics file (File> save calendars) or contacts in a .Export and import vcf file. Therefore you export the appointments/contacts in one of the two programs (my app or Outlook), copy the file to the other device and then import it there with the other program. So a two way sync is possible. 2)Use z.B. Caldav (for appointments) or CardDAV (for contacts). In this case a two way sync is possible over the network. But Outlook can't do this by itself, so additional plugins like CFOs are needed. My app already brings everything necessary by itself to integrate the Android device into this solution. Two way sync is possible. You can either run a server by yourself or use free providers like web.En. 3)Using WebDAV (for appointments). Here is then over a network a two way sync possible. Because Outlook can not do this by itself, you need additional plugins like iCal4OL. My app already brings everything necessary by itself to include the Android device in this solution. Compared to option 3 no complex calendar server is necessary, also free web storage which is available from many providers is sufficient. 4)Publish calendars to a WebDAV server without additional plugin allows read access to the Outlook calendar and is supported by Outlook by default. Free WebDAV storage like the one from GMX is possible or also self operated solutions. 5)If you use Office Online you can share calendars, you will get a URL starting with webcal://. You can configure these in CalendarSync. So the appointments will be transferred to your device automatically.

Automatically find the calendars (CalDAV):

The app can automatically find all calendars on your server and configure them. To do this, start the app> Press the menu button> Choose new WebiCal create. Start with the guided configuration for CalDAV Server. Enter your username, password and the URL of the server. Now test the connection to the server. The app informs you whether the server was found, the loding data was correct, etc. If everything is ok you can proceed with the search of the calendars. Now select the calendars you want to configure. Press Create WebiCal. The app creates the appropriate configuration. Android calendar to store the appointments. You can now start your first manual synchronization or configure an automatic synchronization. Existing WebiCals (configured servers) can be exported. Import them again later. To do this, start the app> press the menu button> Choose to show created WebiCals. Then press the menu button again. Create backup of all WebiCals select. You can now decide if the login passwords should be exported as well. The backup is stored in the main folder of the app (by default named CalendarSync, configurable in the settings). From there it can then z.B. Copied and imported to a new device. If you choose the option Restore WebiCal Backup then all backups stored in the main folder will be listed and you can choose which ones to restore. In the event of a recovery, the app generates the appropriate WebiCals. Creates the corresponding Android calendars. The restored configuration can be used for synchronization immediately. If the backup was created without the login passwords you need to edit the restored WebiCals. Enter this so that CalendarSync can access the server.

Transfer settings from trial to full version

Existing WebiCals (configured servers) and associated metadata can be exported from the trial version and later re-imported/transferred to the full version. To do this, start the app> press the menu button> Select Show created WebiCals. Then press the menu button again. Select Transfer WebiCals to Pro Version. The backup will be stored in the main folder of the app (by default named CalendarSync, configurable in the settings). If you select the option Restore WebiCal Backup (in the WebiCal overview of the full version) then all backups stored in the main folder are listed and you can select which ones should be restored. During a restore, the app creates the appropriate WebiCals and takes over the existing calendars and appointments. The restored configuration can be used for synchronization immediately.

If you have already analyzed a WebiCal or an iCalendar file, here you have the possibility to get an overview of the analyzed information. If you long press on a list entry, you get a context menu with the button called Details. If you press this button, you have the possibility to get more detailed information about the appointment/entry.

Create new WebiCal:

Here you can create a new WebiCal. You can define a URL (where calendar information can be found) and, if necessary, set a username/password combination that will be used to access the information. You also need to define a source type z.B. Whether the iCalendar information is sent to a web server (HTTP or. Webdav), an FTP server or a CalDAV server. For webcal/webcals calendar feeds please use HTTP/HTTPS as source type. If you select CalDAV as source type, you can choose a CalDAV provider. Most of the time the general provider is only sufficient. A special provider is needed to z.B.B. If the server software has certain known errors. In this case the server needs a special treatment. Similarly it is also possible to select a WebDAV provider if you have selected HTTP as the connection type. Under "Choose Calendar you can define a calendar of the device which WebiCal should use for synchronization. If no calendar is selected or the selected calendar is deleted, the general calendar defined in the options is automatically used. If no calendar is selected in the options, the app will try to find a calendar on its own. You can edit your WebiCals using the context menu on the display WebiCal window.

Show created WebiCals:

Here you can get an overview of your previously created WebiCals. If you long press on a list entry you get the following options:

Delete:

Deletes the WebiCal. When you delete a WebiCal, the associated appointments are also removed (from the device not from the server)!).

Analyze:

Loads and processes this WebiCal.

Edit:

Here you can edit the WebiCal e.G.B. Change the password or deactivate the WebiCal.

Purge:

Removes all appointments from the device (not from the server) which were previously imported from this WebiCal!). The WebiCal itself is not deleted.

Manual:

Shows the instructions.

Calendar management:

Here are rather rarely used functions bundled. For example creating or deleting a device calendar. If you delete a calendar all corresponding appointments will be removed too.

Options:

Here you can configure the application.

What can be set in the options:

Remove before import:

If enabled, appointments previously imported with this app will be deleted before a new appointment is imported.

Do not delete old information:

If enabled, appointments imported with this app will NOT be deleted when a new appointment is imported. Appointments that are already on the device will be updated. If you import appointments from a WebiCal without activated two way sync, the removal will be executed anyway but not as with the above option for all appointments but only for those which are really no longer present within the server data.

If you deactivate both options, no import is possible. These two settings have no effect on WebiCals which have enabled the two way sync because here the corresponding operations can be derived directly from the changes in the calendar data.

Calendar for import:

Select which calendar should be used for the import. All calendars available on your device will be displayed. If the name of the calendar can not be read NA will be displayed.

Restricted subscriber import:

If this setting is activated the number of participants which will be imported per appointment will be limited. This is useful if you have appointments with many (hundreds) participants. An example would be appointments on which all or. Many employees of a company participate. How many participants should be imported can be set in the lower option "Maximum number of participants" be set.

Maximum number of participants:

Defined maximum number of participants to be imported. In order to use this option, the "Import limited subscribers" setting above it must be enabled be active.

Ignore subscribers:

If this option is enabled, the participants contained in the processed calendar data will not be imported/synchronized.

Ignore alarms:

If the option is enabled, the alarms included in the processed calendar data will not be imported/synchronized.

Synchronization of calendar files with WebiCals:

Appointments which are imported from local calendar files z.B. .Ics files (z.B: from emails, etc. Therefore appointments which were NOT transferred by means of a WebiCal) are synchronized with two way Sync WebiCals. This will allow z.B. Dates from .Ics files are transferred to a CalDAV server.

Check if new version is available

If enabled, the app will check if an update is available during the startup of the application and inform you about it if necessary.

Auto Import:

If enabled, every iCalendar information (no matter if from a WebiCal or a file) you analyze will be imported automatically.

Notifications:

If enabled, important information will be displayed whenever the app is not visible during the analyzing/importing process. This is useful when you start analyzing/importing calendar information and then put the app in the background.

Disable all notifications:

If the option is enabled, notifications about the current app status will no longer be generated.

Prevent sleep mode:

If enabled, the app will prevent the device from sleeping during manual actions. Z.B. While calendar information is being imported/parsed. During the automatic synchronization, the sleep mode is automatically prevented. This is useful when you want to analyze/import huge/complex calendar information, and your device is programmed to stop working after some z.B. Minutes switches to power saving mode. If you enable this option of the app, it can continue the process in such a situation.

Postpone appointment start/end by days

Shifts the start/end of appointments by one day during import. This is only necessary for some devices.

Move appointment start/end by hours

Shifts the start/end of appointments by hours during import. This is useful when you get calendar data from other countries which do not contain timezone information.

Self-create calendar owner email

When you create a new calendar with my app, an email address is associated with it. This can be defined here. For newly created appointments, this address is specified as the owner. If you do not define a valid owner the following is used: "[email protected]"

Notes

The app displays various notices z.B. At the first start. These are normally displayed only once. Here you can set if a hint should be displayed again.

Workarounds

The app implements solutions for bugs in different (also vendor dependent) Android versions. Some of them can be disabled/enabled here.

You need a valid license to enable the following options:

Calendars for export:

Select which calendar to use for export to a local file (export button). Show all calendars that are available on your device.

Custom import/export folder path:

Custom path for the folder where exported calendars, log files, etc. Are stored. Be saved. The path must start and end with a /. All folders specified in this path must already exist. If the path is not correct or a folder does not exist, the default path (/CalendarSync/) will be used. By default the search for the specified path starts in /mnt/sdcard. Therefore the defined path /CalendarSync/ will be redirected to /mnt/sdcard/CalendarSync/. If you do not want to use in /mnt/sdcard/ but z.B. /mnt/sdcard2/CalendarSync you have to specify the following path /../sdcard2/CalendarSync/. The /../ is used to go back one step from the start of the default path /mnt/sdcard/ to /mnt/.

Use Autosync:

The app periodically syncs all active WebiCals in a background operation. You can control the intervals between syncs with the following options.

Synchronization in working time:

If enabled, the autosync will only be performed if it falls in the time between 6 am to 6 pm.

Autosync period:

Set how often the app should sync with the configured active WebiCals.

Save Autosync Log:

When the option is activated, the app automatically saves logs of the automatic synchronization process.

Allow external autosync:

If enabled, the app allows external apps like Tasker to trigger automatic synchronization using CalendarSync. Further above I have described how z.B. Tasker can be configured.

Autosync only with WIFI/WLAN connection:

If enabled, the app will only start an automatic or externally triggered synchronization if a WIFI/WLAN connection is available.

Filter calendar data:

If enabled, iCalender information is filtered while it is being analyzed. Only appointments that fit the filter are then available for importing. For filtering you can define a time period and the app will only import values that occur during a specified time period, you can define this starting from a specific month/year to a specific month/year. Even dates with complex recurrence rules are handled correctly.

Show statistics:

If enabled, the app will display statistical information about the most recent two way synchronizations performed by WebiCals (z.B. How many appointments were detected as deleted on the server).

Configuration of the period filter:

Use this option to set the option defined above. If your filter settings are nothing correct z.B. Start time is after end time, filter is not applied.