@rfc2822 Thanks for taking a look. 20191121T035347Z is exactly 90 days prior to when the request was made. Davx5 is configured to begin searching for events 90 days prior. I assumed CAL:time-range start=“20191121T035347Z indicated the start point for that range. Is that not the case? Nevermind, I misread your reply. I’ll look for broken events in that range and see what I can find. Thanks for your help.
Carddav not working on HTC Desire 500
Installation and setting up the account is no problem.
But the account is not visible in the contact-app and no sync-account is there.
davdroid: 0.5.1 from f-droid
Server: radicale, only one carddav entry
D/AccountTypeManager( 644): Registering external account type=bitfire.at.davdroid, packageName=at.bitfire.davdroid E/ExternalAccountType( 644): Problem reading XML for external package at.bitfire.davdroid E/ExternalAccountType( 644): com.android.htccontacts.model.AccountType$DefinitionException: #phoneticName must be supported
This is a “predetermined design feature of HTC”, please see here:
I found this website on my own this morning.
How stupid could this be? Well, could you easily detect this and throw a warning while creating a new sync-account?
So that people are warned, that this does not work at all?
Yes… It’s a pity with HTC I don’t think rfc2822 will make some platform dependent warnings, but maybe he’s writing here again… All we could do is to disable the HTC Desire 500 and other relevant devices in Google Play. Then people there wouldn’t see the app for their incompatible device. But this still does not help users that get DavDroid from F-Droid.