I’m using 0.5.2 alpha from Samsung store on a Galaxy Tab 3 with Android 4.2.2. I read somewhere that there is a 0.5.3 alpha - when’s it coming to Samsung store?
There’s a special approval procedure for Samsung Store that takes a few days. We have submitted 0.5.6-alpha a few days ago, so it will be available soon.
Apart from the known problems with Groups (what a drag!) I have noticed that when I add a second website (at “Home”) to a new contact entered into the tablet, URL;Type=home is not generated on the UpSync to the server; rather, the second website gets deleted from the Android contact!
Android 4.0 has a so-called EditSchema XML that defines which contact fields are supported. The Android contacts editor parses this file and shows the input fields accordingly. However, for Android 4.0 devices, the number of URLs must be limited to 1 or the contacts editor will crash! So, only one URL must be present per contact or otherwise the editor may crash. That’s why DAVdroid reads only one URL, and if you change a contact, the new contact will be saved with only one URL (discarding the second).
I have seen that the EditSchema allows any number of URLs, but only one gets synced. So this is a bug and it will be fixed
I’ve noticed and read about the depressing problems with adresses (Android supporting only one field, generally passed through as Street). And it’s a nice tweak that on the DownSync the separate fields at least get put onto 3 lines, separated by Newlines. So my question is, could the converse be done? I tried entering an address in the same format, with two newlines, on the tablet, but no, DAVdroid seems currently not to do the converse mapping to address fields for UpSyncing.
Maybe it would be possible, but a) it’s far too complicated and error-prone (every contry has own address formating rules!), and b) DAVdroid is clearly not responsible for address field formatting. The Android contacts provider provides structured addresses, and DAVdroid syncs them. That’s it. Splitting an incorrect “street” field would be the responsibility of the contact editor or Contacts data provider, so if you’d need this, you would have to use another contacts editor app. Personally, I enter addresses only using other DAV clients (Evolution, in my case).
Thanks for a great App, I’d been using CalDAV and CardDAV Sync, which are more mature and offer more settings to play with - but DAVdroid parsing the collection and offering all available items for optional syncing really makes life easy!
We do our best to avoid settings – what can be done automatically should be done automatically. (Yes, I use Gnome and not KDE if you understand this one :))
Well it would be nice to know if ownCloud produced broken VCFs… so, were the cases 1-3 I listed above valid before I changed them manually (use of ITEM1. and ITEM.X-ABLABEL, splitting URLs over two lines and using “” to represent a newline)
Android provides only one address book while it provides multiple calendars. Thus, only one address book can be synced. Creating multiple accounts is an option, but in this case, the user should do so.
The restriction is not by DAVdroid but by Android – there can be only one address book per account.
Using groups would be a possible solution but there are other bugs preventing this (see #48).
I’ll close this issue because I think it’s a duplicate of #51 and it should have been fixed with 0.5.4 (see release notes). Please try with 0.5.4+ (uninstall DAVdroid, install 0.5.4 or later, add account again) and if this issue persists, please comment here and I’ll re-open the issue.
Thanks for the quick answer! This is a bug in OwnCloud, it seems. Not an issue with DAVdroid.
The VCard is indeed 3.0.
In the above example, the address type is ADR;UNKNOWN=X-GPS. In OwnCloud, if I change that address to one of the default options (ADR;TYPE=HOME or ADR;TYPE=OTHER or ADR;TYPE=WORK) and then take a look at the VCard, it has an escaped comma like it is supposed to. After that, everything on the DAVdroid end works correctly.
I will mention this to the OwnCloud people. Thanks again for your help! Wonderful.