• We’re seeing performance issues in the latest app version on some phone models. In certain cases, this may cause missed calls and reduce blocking quality. Our team is already working on a fix. If you have any helpful information about this issue, please email us at info@callfilter.app

    The fix is ready, and update 1.32.6 will be available soon.

Recent content by hexaae

  1. H

    BUG: added to Whitelist and then removed, it still stays whitelisted in call history

    It's a bug because it was marked as unknown (letting me choose) in the history. Then, minutes later, I accidentally changed it to Whitelisted from the history. I didn't mark it as Whitelisted at call time. To be clear: - didn't respond to the call (yellow in the call history) - accidentally...
  2. H

    BUG: added to Whitelist and then removed, it still stays whitelisted in call history

    Example: I have accidentally marked a recent call X as "Whitelisted". Once I remove it from my Whitelist, it still stays as Whitelisted (green) in the call history and the X call menu also acts acts as whitelisted.
  3. H

    Please don't mark as Block non-contacts in call history

    Thank you. Yes, but if you have many calls in the list it can be tedious... while a quick glance in the list of blocked numbers and then check manually ONLY those few blocked by "Block non-contacts" flag is more feasible. ATM instead callfilter marks everything as "Block non-contacts" when the...
  4. H

    Please don't mark as Block non-contacts in call history

    Please can you give a higher priority to the other blocking reason flags in the call history, leaving ”Block all non-contacts” as the last matching reason for those phone calls not classified as SPAM? If call X is spam, verified from the database or online results, the program will show it as...
Back
Top