A complex bug apparently introduced by the latest update

Hello,

After today’s update on my Android 5.1 phone your call blocker, whenever it’s on, blocks all calls rather than only those that originate from previously blacklisted numbers.
Moreover, once such a legitimate call has been blocked, Avasts sets ring volume to zero and prevents restoring it via physical button or touchscreen slider.
The only workaround is to turn call blocker off and restart the phone.

Not only that I had to troubleshoot why my phone is not available to any caller (blocked silently, in the background and without any visual indication)…
Alas, no settings seem to be available for modifying call blocking policy in the current version of Avast. So now I have to keep the functionality off and cannot block any of the collected spammers’ numbers.

Hope this helps.

Hi, thanks for reporting the problem, it helps a lot. We are now trying to find out what’s going on.

Hi, I have an important question - what format do you use for the numbers you save? Do you use any special characters (like *)?

Sorry for the delay: somehow I have not received any responses via email.

The blocked calls have mostly been local Israeli numbers (when incoming they appear as 0… and are recognized properly even if I have them listed as +972… in my phonebook). However, there has also been a declined call from the US number of a friend of mine. It is registered as +1… in my phonebook; I do not remember whether normally it appears in the 00… or +1… format on the screen when I receive his calls.

So no special characters, only 0/00 or +(country code & phone number).

P.S.I am not sure but I think there used to be an option to change the level of call filtering in the settings of call blocker. Now it’s either “on” or “off” anyway, and I neither messed with the settings prior to detecting the bug nor see now an option to limit the scope of call blocker only to the specifically blacklisted numbers.

Today I’ve received a spam call; upon its termination Avast has offered to block and report the “high volume” caller. Pressing the corresponding button immediately activated the call blocker (for all numbers) and set the ring volume to zero without any indication or ability to restore it, as described in my previous messages above.

Just a few seconds later I happened to receive a call from a number registered in my phonebook. Disturbingly, not only that I was unable to respond (the blocker has dropped the call in a moment) - the number did not appear on my call list in any status: missed, answered or otherwise. So in case one is not looking at the screen exactly while being phoned, the number will only appear in the blocker’s list - and it is by no means apparent that agreeing to suggested report on a high volume call activates the “drop all/silent-without-indication” mode.

Is this a known problem? Should I wait for a future update or attempt reinstalling Avast? (I’d rather not unless there is a way to save the black list and other settings)
Meanwhile I experience no other trouble - just have to keep the call blocker off.

Thanks.

Hi, sorry for the delay in responding. Thanks for your comments, they have helped a lot.
The fix is in progress now and should be ready for the update v6.5.0 - thanks again for your assistance.

Hello,

Same “Call blocker” bug has been reintroduced by the latest update.
The bug and the phone are exactly as described in my original report in this thread.

Thank you in advance for looking into this.

Hi, what exactly is the app version this problem relates to?

Hello,

6.6.0-316428-1e53d8c

Hi, we will need more details, a colleague of mine has contacted you via e-mail.

Hello,

I have sent your colleague a detailed reply from two email addresses (just to make sure he receives it).
If somehow that information hasn’t got through Avast support system to you, I can paste my response in this thread.

Hi, if you have already got in touch with my colleague, I would prefer you discuss/solve the problem with him (dealing with issues by both e-mail and the forum always causes confusion). Thanks for understanding and good luck with solving the issue!