Okay Great that it works now!

The build was an official update from ~last summer. I didn’t update for a while, but I will do so this evening and hope that everything keeps working and the issue really was caused by a bug in the current build.

@rfc2822 said in Unable to add ical sources persistently: I don’t know, because as far as I know, there is no documentation for Privacy Guard. Or is there something like that? So far, I couldn’y find any myself. But I’ll ask around. I did read a post on Reddit by a member of the LineageOS team, stating that Privacy Guard is based on AppOpsManager. Not sure if that helps or sheds any light. Would be interesting whether other apps suffer from from the same problem. On my phone it’s only ICSDroid that fails to behave properly. I’m also keeping in mind that it could be something on my phone. I tried adding an ICSDroid account from the accounts menu. That brings me into the app, allowing me to add a calendar resource, but no ICSDroid account will show when that process is finished. That’s odd, but I guess something outside the app. @gui1ty said in Unable to add ical sources persistently: Or do I need to disable Privacy Guard completely? That, I found out, is not achieved easily. Once enabled during initial phone setup, it can only be turned off per app.

Hello, Did you disable Privacy Guard for DAVdroid? Is there an “auto-start”, “run in background” etc. permission in Android settings / Apps / DAVdroid / Permissions?

@rfc2822 turns out there is a setting in the privacy guard to restrict app from modifying the calendar. And the calendar storage app had no permission to do so I probably took the permission, or maybe it was never set. Not sure

@fhollerweger I only know that Privacy Guard has to be disabled for DAVdroid since I know about Privacy Guard (we even had a FAQ article about that in the beginning). So I assume that if DAVdroid with enabled Pricacy Guard has worked some time, this was by chance and maybe even a Privacy Guard bug. After all, Privacy Guard’s task is block access to contacts and events and thus DAVdroid. If you find anything about why its behaviour has suddenly changed, please let us know

@rfc2822 said in checksum error while sync contacts to second user account on same phone: Can you provide exact steps to reproduce the problem? I checked the configuration today once again and found that the special data privacy settings for DAVDroid in LOS 14.1 where activated and reading of contacts was forbidden. After I have changed the configuration the error disappeared. Thanks for your help!

Thanks for the links and information!

Thank you that link helped. The Problem is gone now. However OpenTask should ask for permission instead of letting the user unknowing he has to request them by hand through the settings.

@rfc2822 Oh, I see. Thanks for the explanation!