Checklist
Affected app version
1.3.1
Affected Android/Custom ROM version
Android 14, 13, 12
Affected device model
multiple
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Receive a call from a number that is either stored, or not stored in my phonebook (via Fossify Contacts)
Expected behavior
For a case with stored/known contact, I expect to see at least some contact detail.
For an unknown caller, I thought that I at least should see an actual phone number instead if "Unknown number" which is kinda not accurate (as the number is "known" as presented by network, but not in my address book).
Actual behavior
Observe "Unknown number" displayed on my fitness tracker.
For a less than a second prior to showing "Unknown number", I can barely see smth that looks like an actual phone number.
Screenshots/Screen recordings
No response
Additional information
I don't experience such behavior on stock Samsung dialer (few samsung models, Android 12-14).
as stated in closed #275 , respective app (gadgetbrige, 4.3K stars on github) has all the necessary permissions and works just fine with other dialers.
so it's either integration issue or idk
Checklist
Affected app version
1.3.1
Affected Android/Custom ROM version
Android 14, 13, 12
Affected device model
multiple
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Receive a call from a number that is either stored, or not stored in my phonebook (via Fossify Contacts)
Expected behavior
For a case with stored/known contact, I expect to see at least some contact detail.
For an unknown caller, I thought that I at least should see an actual phone number instead if "Unknown number" which is kinda not accurate (as the number is "known" as presented by network, but not in my address book).
Actual behavior
Observe "Unknown number" displayed on my fitness tracker.
For a less than a second prior to showing "Unknown number", I can barely see smth that looks like an actual phone number.
Screenshots/Screen recordings
No response
Additional information
I don't experience such behavior on stock Samsung dialer (few samsung models, Android 12-14).
as stated in closed #275 , respective app (gadgetbrige, 4.3K stars on github) has all the necessary permissions and works just fine with other dialers.
so it's either integration issue or idk