Confused about Calendar and Contacts sync support with Google?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Describe the bug
I'm unsure whether microG is intended to support Calendar and Contacts sync with Google. From what I've found here:
https://github.com/microg/GmsCore/issues/705#issuecomment-464712729
and other places, then support is considered 'out of scope'. However, my calendar does sync, but contacts does not at all - but, the default contacts app in /e/OS look as if it should sync (it reports my Google account, as does the Google contacts app).
So, if calendar is working, is that intended - and are there plans - for contacts to work? Or, is it still 'out of scope'?
If it's not a bug that contacts do not sync, what's the recommended work-around for contacts: use DavX5 or the instructions under 3.1.1 here:
https://shadow53.com/archive/android/no-gapps/setup-guide/3/
and only following the procedure for contacts?
Thanks
To Reproduce
Steps to reproduce the behavior:
- Install /e/OS
- Try to sync with Google calendar and Google contacts
Expected behavior
Some indication of what microG intends (sorry, if that's under my nose somewhere)
System
Android Version: 9
Custom ROM:
https://leech.binbash.rocks:8008/e-os/pie//h815/e-0.17-p-20210607-CUSTOM-h815.zip
https://forum.xda-developers.com/t/rom-unofficial-p-f500-ls991-h81x-us991-vs986-e-os-bye-google-hello-privacy.4142021/post-83196371
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked issue comment and the reported /e/OS Android 9 setup details first. Determine from the project's documented scope whether Google Calendar and Contacts synchronization is intended, and document the supported behavior or workaround; no source files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100