-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fossify Phone (Contact Tab) and Contacts App not showing any contacts #28
Comments
In which memory do you keep contacts? |
I am using bitfireAT/davx5-ose to access them via carddav. |
Thanks! Please just change the title that you're writing about Contacts tab. Phone doesn't use Contacts app to get the contacts, these are two separate apps. |
As the Fossify Contact app has just been released, I have been able to confirm that this bug is also present in the Contact app. |
Just want to add that I did not have this issue on android 13, only on android 14 (custom rom) |
Confirm, can't see my synced Contacts. App Version 1.0.1. |
I tried to debug this problem and (at least for me) it boils down to this line of code in the commons library (https://github.com/FossifyOrg/Commons/blob/master/commons/src/main/kotlin/org/fossify/commons/helpers/ContactsHelper.kt#L825). The accounts are correctly read (https://github.com/FossifyOrg/Commons/blob/master/commons/src/main/kotlin/org/fossify/commons/helpers/ContactsHelper.kt#L821) and iterated over but the call to Afterwards, in this line (https://github.com/FossifyOrg/Commons/blob/master/commons/src/main/kotlin/org/fossify/commons/helpers/ContactsHelper.kt#L840) Since I'm not really familiar with Kotlin and/or Android Development I'd be glad if a developer could help. (Especially, since I'm not familiar with the development environment, I wasn't able to add a local copy of the commons library to my the contacts app and manipulate the code to gain further insights.) Edit: On a side note - There currently is no open issue in the FossifyOrg/Contacts app regarding this issue. Therefore I hijacked this topic, since the bug seems to be within the commons library (or within GrapheneOS?). |
It also affects when receiving a call, no saved contact displays, only their real number. |
I can confirm that after upgrading from LOS 20 (Android 13) to LOS 21 (Android 14) my synced contacts are not shown any more. App version 1.0.0. |
I have the same problem with CARDDAV contacts. |
I'm experiencing a similar issue. For me some synced contacts accounts are showing (with Davx), but I have contacts from tutanota (tuta) and those are not showing whereas they appear in the Google Contacts app (which I'd rather not use). Fossify Contacts 1.0.1 |
Just a note: this also affects the calendar app's contact birthday/anniversary import feature |
Could this be (highly) prioritized, please? Incoming calls are shown as numbers only and I can't tell who is calling. |
My contacts are synced using davx5, and this is a problem for Fossify Contacts and Fossify Dialer but only after activating a new profile. I have two profiles: the main profile I don't run any Google services nor apps from the Play Store, that is the profile with the problem. In the profile where I run Google services I installed the Fossify Contacts app and it displays my contacts just fine. Before using two profiles I was running the sandboxed google play services, and it was all fine. As others report, GrapheneOS' contacts and dialer apps can see my contacts form davx5 just fine. |
I'd like to add that, the Phone app is unable to read contacts from AOSP Contacts which has DavX based storage. Not sure if in order to use Fossify Phone App, I have to use Fossify Contacts as well or can use any other Contacts App. Edit: as @lmcj-xyz mentioned, in a profile with Sandboxed GSF is installed, the issue doesn't seems to arise. |
Mi A3, custom Android 13. Any workarounds for now? |
In addition to my comment above, it's worth to notice that only Phone and Contacts fail to see my davx5 contacts after uninstalling the sandboxed Google Play services, but Messages can see them without a problem. Edit: This may be related to the Phone app showing my contacts only in the call history. |
Just updated to version 1.2.0 and the issue still persists |
Same for me. |
I could not reproduce the issue on two Android 14 devices. I can't install GrapheneOS at the moment but I have a few ideas so I'll need someone to test things for me. Here is another APK with a potential fix: phone-4-foss-release-issue-28.zip (GitHub doesn't support APKs so just rename the .zip to .apk and install, do not extract it) |
Still does not work for me. Any specifics I/We should test? |
@naveensingh It seems like it only affects Android 14 devices which don't have Google Play services installed (see #28 (comment)). I did not test it on a GApps enabled device. |
@irgendwie , actually, I think I should mention that I'm on Android 11, stock version (never tinkered with... so far...), with Google Play services enabled, and I'm affected as well ... Interesting. |
Your problem however seems to be related to syncing contacts from specifing app (Tutanota) or am I mistaken? Cause you've written above:
|
@chesio indeed. I have 2 contact accounts syncing on this phone:
My understanding was that Fossify was syncing OK in most cases (eg. My "DAVx5 case"), and other times not (eg. My "Tuta case" and other people's issues in this thread). Do you think it's actually 2 different issues? |
I would say it is a different issue although it manifests itself in the same way (no contacts showing). Almost all of the commenters in this thread are reporting having problems on Android 14 with custom ROM. Your problem sounds different, so I would recommend that you open a new issue. It might be easier to solve and if someone else is also having issues with Tutanota app, a dedicated issue will be easier to find for them. |
Same issue here with latest Graphene on a 6a. |
Fix FossifyOrg/Phone#28 (Missing contacts) According to doc ContentResolver.getIsSyncable returns value >0 if it is syncable, 0 if not, and <0 if the state isn't known yet.
Same problem here. No problem with stock app. |
+1 |
Same here. Google Pixel 7 Pro wtih GrapheneOS contacts synchronized with a davx account No problem with stock app Fossify Contacts show contacts only when Google Play Services installed |
I am having the same issue. My contacts appear in the stock contacts app and in Contacts You app. But they don't show up on Fossify Phone. I'm on GrapheneOS (Android 14) without any Google Play services, and I'm using etesync to store contacts. |
Added comment in Fossify Contacts which is similar issue and likely related. Comment |
Same issue here on grapheneos with android 15. After removing all google services, it shows only contacts from simcard in contacts tab. History shows all calls and names of contacts, but on contact tab they are not shown. |
I think that Fossify Phone is a app that everyone use most often. So we hope that it's possible to fix that issue in nearest time. |
It should be fixed in the next update. |
@naveensingh: Thanks. I tried it with android studio. After the last update the contacts are shown. |
It's out now: https://github.com/FossifyOrg/Phone/releases/tag/1.3.0 |
Thank you for things you are doing for all of us! |
Checklist
Describtion
No Contacts are visible. The issue started with one of the later versions of the former Simple-Dialer and Simple-Contacts app and seems to persist here. Strangely The correct names are shown in the call history. There was an issue for Simple-Contacts (SimpleMobileTools/Simple-Contacts#1044) which seems to be the same issue.
As mentioned in a comment here the versions Simple-Dialer 5.18.0 and Simple-Contacts 6.22.4 are working as intended. I did double check and this holds true for me too.
I suspect this will be a problem in the Fossify Contacts app too.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
See all contacts.
Screenshots
Screenshots can be found in the old issue here: SimpleMobileTools/Simple-Contacts#1044
Helpful Links
Device info (please complete the following information):
The text was updated successfully, but these errors were encountered: