The releases are built from the version tag by Github, as soon as one “drafts a new release”. I’ll do so in future and add the signed APK as a binary, too (for archiving purposes).
Either via URL (see http://dmfs.org/wiki/index.php?title=Auto-provisioning )
or via a prepared config file
The dav url (seperate vor card/cal/task)
The Password (hashed?)
The Server Cert (For self signed)
Of course the Privisioning shall allow combinations of above where the rest ist completed with the ui
Something like that is already in development for DAVdroid! This will greatly simplify the setup process. See #148 for more details.
Indeed, support for well-known URIs is coming, and support for current-user-principal is already available.