With google as the only calendar and contacts provider the synchronization worked fine and I never noticed this setting.
I guess Google apps are always allowed to do anything 😉
Good to hear that it now works.
Please add support for task syncing.
First I wanted to thank you for your great app!
It would be nice if you could implement this.
Currently we trying to resolve one of our Issues with Mirakel. So we are searching for a sync provider with support for VTODO.
We have already implemented a parser for the VTODO’s: See here. If you want, you can merge it in your project.
If you have questions about this, don’t hesitate to ask us.
Working right now at using dmgs taskProvider, since populating calendars as equal to populating vtodo and vjournal it would take me till the end of week to get some working code. I worked with TaskProvider alot these days
I had also begun to work onto integrate this with Mirakel.(Some changes are already done see https://github.com/weiznich/davdroid).
The content-Provider from Mirakel should work with the constants of dmfs after the current changes, Only the uri would be diffrent(due to there can’nt be two providers with the same uri)
we would definitly got problem with syncing that stuff, so i assume you should better it that way:
Do a separate LocalTodo class for parsing object into contentprovider database so we can separate logic of contentproviders, and later just check of system availability of contentproviders to write stuff into
also start of my work is here - https://github.com/khades/davdroid/ i just would make it syncronise ANY fields, then i would add more fiels, that actually implemented in taskProvider, and later i would extend taskProvider for storing extended attributes
Just a side note: looks like the missing VTODO support also slows down overall calendar synchronization, as all VTODO resources are downloaded, parsed and discarded during each sync (because they are never added to the local collection).
@oliver See also issue #32 – downloaded VTODOs should be added to a collection, and (ideally) all not-parsed entities should be added to another collection (to avoid further downloads).
We published a first alpha with working VTODO-Sync
We had tested with Mirakel as contentprovider, but it should also work with dmfs.
i have working vtodo-sync as well, but i tend to extend dmfs task provider alot, so i have too much dirty code
https://drive.google.com/file/d/0B_Nj0E_VORYEU2NCMElGeTlWOU0/edit?usp=sharing - modified davdroid, also available in my clone repo (dont have davical fix yet)
https://drive.google.com/file/d/0B_Nj0E_VORYEeFFLQzZzZE5iVk0/edit?usp=sharing - task app with modified provider
also my mail i send to davdroid support was ignored,i wrote about problems i had with developing davdroid extension
Didn’t get any mail, please re-send or (better) post here.
i have wokring code for tasks provider dmfs , but i cant finish it since i am forced to do other features, that extends core dmfs task provider(property table like relations, categories etc), is it ok for me to push request partial support?
Really looking forward to tasks support Big thanks to @weiznich for the implementation - hopefully it’s going to get integrated soon?
It will definitely come to DAVdroid. As you can see in our road map  it is currently planned for 0.8 series. We should get to 0.6 in January hopefully!
+1 for this. more important to me than those other issues planned for .6 and .7.
+1 for task support !