[mobileorg-android] Recurring events in the calendar

[Jorge Morais via mobileorg-android]

I have set up calendar synchronization, but my recurring events do not show
up in the Android calendar. Is there support for it? It seems from my web
searching that there is no support. Is there a workaround?

[mobileorg-android on behalf of Eric Fraga]

Post by Jorge Morais via mobileorg-android
I have set up calendar synchronization, but my recurring events do not show
up in the Android calendar. Is there support for it? It seems from my web
searching that there is no support. Is there a workaround?

The one workaround, that I use but for other reasons, is to make copies
of the event with shifted dates:

,----[ C-h f org-clone-subtree-with-time-shift RET ]
| org-clone-subtree-with-time-shift is an interactive compiled Lisp
| function in ‘org.el’.
|
| (org-clone-subtree-with-time-shift N &optional SHIFT)
|
| Clone the task (subtree) at point N times.
| The clones will be inserted as siblings.
|
| In interactive use, the user will be prompted for the number of
| clones to be produced. If the entry has a timestamp, the user
| will also be prompted for a time shift, which may be a repeater
| as used in time stamps, for example ‘+3d’. To disable this,
| you can call the function with a universal prefix argument.
|
| When a valid repeater is given and the entry contains any time
| stamps, the clones will become a sequence in time, with time
| stamps in the subtree shifted for each clone produced. If SHIFT
| is nil or the empty string, time stamps will be left alone. The
| ID property of the original subtree is removed.
|
| If the original subtree did contain time stamps with a repeater,
| the following will happen:
| - the repeater will be removed in each clone
| - an additional clone will be produced, with the current, unshifted
| date(s) in the entry.
| - the original entry will be placed *after* all the clones, with
| repeater intact.
| - the start days in the repeater in the original entry will be shifted
| to past the last clone.
| In this way you can spell out a number of instances of a repeating task,
| and still retain the repeater to cover future instances of the task.
|
| As described above, N+1 clones are produced when the original
| subtree has a repeater. Setting N to 0, then, can be used to
| remove the repeater from a subtree and create a shifted clone
| with the original repeater.
`----