"Block Calls From NOT Stored Contacts" doesn't work

[Just-Regis]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.10.0

Affected Android/Custom ROM version

Android 10

Affected device model

Xiaomi Mi 9

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Go to settings
2. Enable "Block Calls From NOT Stored Contacts"
3. Receive a call from an unknown number

Expected behavior

Call from an unknown number should be blocked

Actual behavior

Call from an unknown number isn't blocked

Screenshots/Screen recordings

No response

Additional information

Adding the number to the blocked list doesn't work too.
From my side, the blocking feature doesn't work at all. I have to use another app to do so.

[naveensingh]

Have you set Fossify Phone as the default Caller ID app?

[Just-Regis]

Yes

[naveensingh]

Adding the number to the blocked list doesn't work too.

That should still work because the calls are dropped by the system when the full number is specified.

From my side, the blocking feature doesn't work at all. I have to use another app to do so.

Are you sure about Fossify Phone being the default Caller ID? Only one app can be granted the Caller ID app role at any given time, so if your other app (or default phone app) is set as the default caller ID app, blocking in Fossify Phone won't work.

Also, does it fail to block all numbers not saved in your contacts or some specific ones?

[naveensingh]

One more question:

How many contacts do you have on your device?

[Just-Regis]

One more question:

How many contacts do you have on your device?

185

[Just-Regis]

Adding the number to the blocked list doesn't work too.

That should still work because the calls are dropped by the system when the full number is specified.

Sorry, I'm not sure about that part. I have to do some others tests.

From my side, the blocking feature doesn't work at all. I have to use another app to do so.

Are you sure about Fossify Phone being the default Caller ID? Only one app can be granted the Caller ID app role at any given time, so if your other app (or default phone app) is set as the default caller ID app, blocking in Fossify Phone won't work.

Also, does it fail to block all numbers not saved in your contacts or some specific ones?

Yes, I'm. The other app it's just a call blocker.
I would answer "all" because I'm receiving call from all kind of number (calling centers, fake mobile numbers starting with the same numbers of my own, etc...).

[naveensingh]

Yes, I'm. The other app it's just a call blocker.

Any third-party app (dialer or not) that blocks calls must be the default Caller ID & spam app for blocking to work. So if that other app is currently working, Fossify Phone can't. I'm not sure exactly where the preference is located in settings on your specific device, but the general path is Settings ➜ Apps ➜ Default apps ➜ Caller ID & spam app:

If you are up for it, I'll send you a test build later with a potential fix.

[Just-Regis]

Any third-party app (dialer or not) that blocks calls must be the default Caller ID & spam app for blocking to work. So if that other app is currently working, Fossify Phone can't. I'm not sure exactly where the preference is located in settings on your specific device, but the general path is Settings ➜ Apps ➜ Default apps ➜ Caller ID & spam app:

As you can see, Fossify phone is my only caller ID :

FYI, I use NoPhoneSpam for call blocking.

If you are up for it, I'll send you a test build later with a potential fix.

Yes, no prob

[naveensingh]

The screenshot you have shared is where you set the default dialer/phone app. The Caller ID & spam app role is different from the default phone app.

And by the way, that app's pretty outdated and does not seem to be using the modern call screening APIs (Caller ID & spam role), but as shown in my previous screenshot, the default can be "None", so it's possible Fossify Phone is not set as the default Caller ID app on your device (but it is set as the default Phone app).

Blocking in this case will also fail if Fossify Phone doesn't have permission to read contacts.