@devvv4ever said in Getting different nextcloud user contact dialing a number from my phone keypad:
Remove DAVdroid. Then try to wipe your contacts storage (Android settings / Apps / Contacts storage / Wipe data). This will remove all your contacts from the phone (not on the server of course), also other contacts not accociated with DAVdroid will be deleted. Restart your device and then make a new account with DAVdroid. Maybe this helps you getting rid of these ghost-entries.
Yess! This procedure effectively removed all ghost entries!
In fact in the past the phone was used by my girlfriend who used a different phone book, always davdroid.
Many thanks for your help!
I’m much quieter now that I know it does not depend on a Nextcloud/Davdroid information loss.
We are creating an association to provide Nextcloud/Davdroid for our members so they can use Android without Google. So a problem like this could be worrying!
Sounds like a problem of your calendar app. Did you try aCalendar?
Thanks for your reply.
Yes, you are right, it seems to be a problem from my calendar app.
I checked all the linked articles and it seems that it is the same problem as in.
After your reply i made a few tests and I have to correct my steps to reproduce in my previous posting.
Create an event with thunderbird lightning. This event will be created without a status.
Sync with DAVx5.
Modify the event on your android device with business calendar 2 or the stock calendar app from google.
Sync again with DAVx5.
The event changes to tentative.
I will open a bug report at business calendar 2.
Oh my god!
I just registered here to say: Thank you so much! I was struggeling with this problem for too long. I contacted bitfire in the past but they kept telling me that this would be an owncloud problem. They told me to wait until Owncloud 9 and all the problems would be gone because they completely reimplemented the calendar/contact stack for OC 9,
However, after upgrading to OC 9 the problems remained. Just now I realized that it is an apache issue. Why the frack did they turn off ETags by default in 2.4?
In this thread they say that they didn’t change anything about etags in davdroid, but this is wrong. The support told me that they actually changed the behaviour after version 0.8.something. So I kept using this version before I read the solution on this thread.
Again, thank you!