But maybe this was already the case before the patch…
Yes, it was.
That’s because AccountsActivity uses Toolbar widget while AccountActivity uses old action bar. The former makes a true shadow via the elevation API, the latter–a fake shadow via a drawable. Why Google can’t make them look similar is a different question.
Hello, it would be nice, if I can configure two links in davdroid for the same calendar.
As example, if you have an owncloud at home, you can use your internal address 192.169.XXX.XXX
And on tour davroid switches automatically to the external address https:yourdamoin.de
It looks like even applying the patch given in the FAQ on an AOSP build of Contacts no longer works as it seems Google has removed group support totally. I’ve also tried the OmniRom version of Contacts and a number of third party address book/contacts apps found on Play Store. Some that claim support for groups or categories turn out to only be able to hide/show various accounts.
We have thought about that ourselves, and find it an interesting and challenging task. After some thoughts, we have found several reasons why it would be better to make a separate app for WebDAV file synchronization. The algorithms are quite different, but the dav4android library could be reused.
Unfortunately, file synchronization is much more complex and error-prone (because of conflicts where we don’t have the stateful information like we have it from the Contacts and Calendar Providers), but it should be possible.
Also, there are some challenges and caveats: for instance, file transfers would have to be resumble, and as far as I know, there’s no way to resume PUT requests (= file uploads). The newer PATCH method is not always supported and has some disadvantages.
Unfortunately, Android doesn’t provide a possibility for apps to query the last sync time. In previous versions, the “Manage accounts” popup started the same activity as you can see in (Android) Settings / Accounts / DAVdroid.
If my Webdav server is having a problem and the sync fails, Davdroid has no way of letting me know that the sync failed.
DAVdroid always shows error notifications on hard errors (i.e. always except for connection problems).
Hi, I also would like support for custom event synchronization.
The app Contact Editor (free/pro) from Marten Ganda has support for custom events. You can give them any name. These events are also correctly handled by my calendar apps and the Birthday Adapter app.
BUT, only on the device on which I altered the contact. When synchronizing with other devices or when the account is created again on the same device, the custom events are gone.
I use Carddav, caldav sync only if it support oneway sync from server to device.
I had already that often the problem that some apps change contact information and with two way sync all this changes will done also on the server without any real control. For example some apps like whatsup change the contact picture to an picture the user uploaded but this picture is often didn’t show the persons portrait. So I use a carddav and caldav server and change this information only through the webpage of this server. Then I regulary let a carddav, caldav sync tool download all information to my Android device. This way I will never get an destroid contact database.
May I ask you whether your sync tool will support one way sync as an option in the future? How does your tool sync contact pictures? Will they also synced in high quality?
DAVdroid synchronization is working fine, when I add a DAVdroid account by manually enter the URL and the user name (second option). I’d really like to profit from the automatic service discovery (only enter e-mail and password and let’s go!), but unfortunately this is not working.
I set up a radicale server behind and apache wsgi “proxy” and I set up correctly the SRV and TXT record for automatic discovery. the caldav and carddav url in my case is for now https://radicalewebserver/cal/. accessing the caldav server with curl works as expected. current-user-principal is https://radicalewebserver/cal/user/.
It seems to me that the automatic service discovery by only entering the email and password doesn’t do a preemptive authentication, but in my scenario the user needs to authenticate for successfully accessing https://radicalewebserver/cal/, what i need to get a valid current-user-principal.
https://tools.ietf.org/html/rfc6764#page-5 says To facilitate “context paths” that might differ from user to user, the server MAY require authentication when a client tries to access the “.well-known” URI (i.e., the server would return a 401 status response to the unauthenticated request from the client, then return the redirect response only after a successful authentication by the client).
So isn’t that something which should be implemented? Or am I doing something wrong?
Owncloud and Contact/carddav is really a sad story:
Beginning as a good alternative to Google/Apple Cloud it started a spiral downward after the maintainer of the contact app had left Owncloud community in April 2014. Some people from OC Core takes the pain to keep this worn-out horse more or less standing in the fast changing OC environment in the following months.
But in February 2015, when Owncloud version 8 was born, this old horse was outsourced and separated from the OC Core.
In Summer 2015 with contactplus a fresh alternative with long missed new features was entering the ballroom.
With the old contact app as a pain in the neck the prima ballerina contactplus was even nominated as a official replacement of the dead horse in autumn 2015. But it was a short dance as the maintainer of contactplus stepped out quite suddenly in November 2015.
So everybody with Owncloud is still “riding” on this worn-out horse called contact app - and desperately waiting for the carddav interface to be reintegrated again into the Core of OC. World premiere is expected for March 2016 with OC 9.0.
Why I write this long story in a DAVDroid forum?
Because during the last month DAVDroid suffer from this home-made problems of the OC carddav interface, especially with the new release of DAVDroid pointing out all the bugs of the OC Contact app. But it is always the bearer of bad news to be blamed with the problems.
So did I too, because it takes some time to realize the above mentioned OC context.
But nevertheless - and with regard to the subject of this forum item: I am still in favour of Owncloud!
It takes a lot of pain to find the correct patches for the current OC Contact App, but right now my OC Server is running very smoothly in combination with DAVDroid on several Android Clients syncing different address books of different users.
And with regard to the future of the OC carddav interface: there is a light at the end of the tunnel - ups - meaning the dawn…