BMS For Android: Call Blocking Recognizes Legitimate Telephone Calls As Suspicious/Unwanted Calls

Gjoksi

Hello.

My specs:

Samsung Galaxy A34 5G (SM-A346B/DSN)

Android 15 With Latest Android Updates Installed

One UI 7.0

Android Security Patch Level July 1, 2025

Google Play System Update July 1, 2025

BD Mobile Security 3.3.276.2517

Since yesterday, the Call Blocking feature started to recognize legitimate telephone calls as suspicious/unwanted calls:

Those 2 are just an example, there are many others.

Those telephone numbers are legitimate and they are in my contact list.

They come from people i personally know and already had a telephone calls / messages with them.

Also, that +389 is the legitimate code for my country.

NOTE:

THIS STARTED HAPPENING SINCE YESTERDAY, WHEN MY APP UPDATED TO VERSION 3.3.276.2517. THIS WASN'T CASE WITH THE PREVIOUS VERSION OF THE APP. IN BETWEEN, I DIDN'T CHANGE ANY SETTINGS IN THE APP.

I submitted a ticket to Support, ticket from Chat 1010445211.

Regards.

@Alexandru_BD @camarie @dvsls @agozob

Find more posts tagged with

Comments

Macgigabit

Device Google pixel 8a

Android 16 update 05 August.

Bitdefender version also 3.3.276.2517

I have a similar issue.

Recently installed bitdefender and call blocking is off BUT it still blocks calls from numbers and claims what's app calls are blocked calls from unknown numbers when actually they are known and they are not blocked ...

Alinah

This mistake is called False Positives, it can be solved by these steps -

Find the call: that was mistakenly blocked or marked as spam.
Select the option to report the mistake . This might involve tapping a "Not spam" button, an "Unblock" option, or marking it as a legitimate call.
Provide feedback: if prompted to help improve the blocking system's accuracy for future calls.

Macgigabit

II don't understand why it should even be taking the action when call blocking is "off"

AlFifi_Defender

Hi @Gjoksi , @MacgigabitMR , and @Alinah ,

Thank you all for sharing your experiences — this issue is indeed concerning, especially since it started only after the latest update (3.3.276.2517). It’s clear this is not an isolated case, and your detailed feedback helps highlight the scope.

From my perspective:

•False Positives: As @Alinah pointed out , this is a classic case of false positives, and reporting them directly within the app is the right first step to help the Bitdefender team fine-tune detection.

•Behavior Change After Update: Since multiple users noticed it began right after version 3.3.276.2517, this strongly suggests a regression in the call classification module. It may be misinterpreting local dialing codes or cached contact data.

•Call Blocking OFF Issue: The fact that blocking behavior is occurring even when Call Blocking is disabled is especially important — it means the app is still intercepting calls at some level, which should be flagged for urgent review by the developers.

My suggestion for users in the meantime:

1.Ensure contacts are fully synced and updated in both the phone app and Google/Cloud accounts.

2.When a legitimate call is flagged, immediately mark it as “Not spam / Legitimate” to provide corrective feedback.

3.If the issue persists, temporarily disable the feature and rely on native call blocking until a hotfix is issued.

Bitdefender’s Call Blocking is a great addition, but these kinds of early false positives can discourage adoption — so I believe quick attention from the dev team will go a long way.

Thanks again everyone for raising this. Hopefully, we’ll see a corrective patch soon.

Regards,

AlFifi_Defender 🇸🇦

“Together we shield smarter.” 🛡️

Gjoksi

Hello again.

It seems that this is a know issue:

Regards.

AlFifi_Defender

Thanks a lot @Gjoksi 🙏

Appreciate you sharing this official reply — it helps everyone stay in the loop.

Good to know Bitdefender has acknowledged the issue and that a fix is already in the works. That’s the kind of transparency and active development we like to see 💪

I’ve bookmarked the support link you included as well — helpful for others facing the same problem.

Looking forward to the upcoming update in Google Play. Until then, let’s keep sharing workarounds and supporting each other.

— AlFifi_Defender 🇸🇦

🛡 “Together we shield smarter.

Drags

I hope this is solved soon it blocked a call from a hidden number which turned out to be from my GP surgery. Not helpful when waiting for test results

AlFifi_Defender

You’re absolutely right, @Drags — that’s frustrating.

When critical calls like those from a GP surgery get blocked, it stops being just a tech issue — it becomes a real-life problem with consequences.

Let’s hope the upcoming fix from Bitdefender prioritizes smarter detection logic, especially for trusted and essential services.

Thanks for sharing your experience — it reinforces how important this fix truly is for all of us.

— AlFifi_Defender 🇸🇦

🛡 “Together we shield smarter.

Drags

Do we have a date for this to be fixed?

AlFifi_Defender

Hey @Drags ,

You’re absolutely right to ask — knowing when the fix is expected helps ease the frustration.

From the official support statement shared earlier, it seems Bitdefender is aware and already working on a solution. Unfortunately, no exact release date has been confirmed yet.

What we do know:

•The issue began with version 3.3.276.2517

•A corrective update is “in the works” and should arrive soon via the Google Play Store

In the meantime, here are a few things you could try:

•Report the number as a false positive inside the app to help improve detection.

•Temporarily turn off Call Blocking when waiting for critical calls.

•Keep an eye on the Play Store for the upcoming patch.

Let’s hope the fix comes very soon. We’ll stay on top of it—and keep supporting each other.

— AlFifi_Defender 🇸🇦

“Together we shield smarter.