emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Hardy <peter@hardy.dropbear.id.au>
To: emacs-orgmode@gnu.org
Subject: Re: Org agenda to Android calendar without Google Calendar in the middle
Date: Sun, 07 Mar 2021 19:17:48 +1100	[thread overview]
Message-ID: <m2eegr9y37.fsf@graphite.lan> (raw)
In-Reply-To: <-fshgnt-thqhvr-31u7zfz3ivnk8mvqye2uz9zw-tuycxo-73uvw1hi81vh-ba2oiremxgy82rxhhu-olnl5q720wg1r013ho-4eas3scsh8ux-43iiqd-6bgwlf-ovbvo2-6cjpsqwf3gbd-8bpw0rmsm22j.1615101495465@email.android.com>


‪‪jamshark70@zoho.com‬‬ writes:

> The org manual page about syncing my agenda to my phone seems to rely pretty heavily on an
> online Google Calendar as an intermediary (including org-caldav, if I'm understanding the readme
> correctly.) This means the "normal" way to sync org with Android may simply not work for me.
>
> Ideally, I'd prefer to use a local web server that I control. How would I do that? (Or, is it
> impossible? Which might be the case if the Android calendar will sync only to Google and nowhere
> else.)

org-caldav does *not* rely on Google Calendar. The documentation does
talk about it a lot, probably because that's a major use case and the
authentication is a little more tricky. But any caldav server will work
fine.

I personally use org-caldav to sync to calendars hosted on a private
Nextcloud installation. But others such as radicale should be fine as
well.

An alternative Android app that you might like to look at is
Orgzly. I've used it a little, syncing my org files to my phone over
webdav and having Orgzly send a daily notification of tasks due that
day. It seems to work well for my meagre needs.

--
Pete


  reply	other threads:[~2021-03-07  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07  7:18 Org agenda to Android calendar without Google Calendar in the middle ‪‪jamshark70@zoho.com‬‬
2021-03-07  8:17 ` Peter Hardy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-08 13:20 James Harkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2eegr9y37.fsf@graphite.lan \
    --to=peter@hardy.dropbear.id.au \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).