Problems with blocking devices on Android

Sometimes my protections is not working properly, why?

In the past we were facing many situations the users reported non-working protection on some phone devices – sometimes the unwanted call (according to the community database or the user’s settings) was not blocked. Actually there are a few main reasons why some application may not work properly – the reasons for this could vary depending on mobile device (and its brand), applications installed on the device itself and version of the operating systems. Let’s check all pre-requisites which should be corrected to have the protection running all the time (also you can check the previously posted articles “How to keep the protection against unwanted calls active“, “Why call blocking does not work on all phones?” and “Should I Answer on Huawei devices” ).

AOS inside

Operating system and smart phones

  • This part is one big pain for all Android developers – the operating system consists of many different resources and open-source parts, which should be used in the same time by all applications installed. To make it all work in the same time, Android OS (Operating System) has set a system of application privileges assigned to each application. The Should I Answer application needs some of them to work properly (for the security applications like Should I Answer we are talking about application which should have higher privileges to protect you all the time) – must be able to catch the incoming and outgoing calls (to be able to block them if needed), needs to read your phone Contacts (to find out which number should be positive for you), must be able to draw a window on the screen etc. For this please always read the installation instructions and the set of privileges we ask for during the installation – and confirm them if you agree. The permissions (system privileges) can be checked for each installed application – just go to the system Settings -> Applications -> select and click the desired application and scroll down to Permissions part (this approach WILL BE DIFFERENT depending on OS version and mobile brand, but the basic is like this). For Android 5.x you will see just the list of privileges there (if you click any of them explanation will raise), for Android 6.x you can manage (revoke / grant) the privileges there. So, if our application raises a message some system privilege or permission is missing, please check this. If there is no chance to change the privileges on your OS, uninstall and install the application again and confirm the set of privileges during the installation. Android forum published the idea of privileges here: “System Permissions” and the list of all is located here: “Manifest.permission
  • The second thing which we must respect for smartphones with OS is that this is not a PHONE – the device is fully working genuine COMPUTER, which has got a microphone and speaker for the calling purposes, but is capable of MUCH MORE different operations where calling is just one SMALL portion. You can install many different applications (and please notice that when you buy your new phone, it comes with a lot of applications pre-installed already) and all of them should run on the same device, using the same (limited) memory and the same (limited) computing capacity of the CPU (computing processor) and GPU (graphic processing unit). Sometimes, when the basic main function (which receiving phone calls and providing outgoing calls is) must be maintained, some of the pre-installed applications try to kill all unnecessary other running applications just to provide system resources for the call itself. Sometimes other applications can cause one application to crash because of some collision on system resources… So, if our application was not able to maintain some call, this can be one of the reasons – try to clear your phone device (restart of your phone once per time is recommended as with every computers) and close all other unnecessary applications which can fight for the same resources. See more below.

Device brand and built-in apps

  • As written above, your smart phone comes with some pre-installed applications by default from the phone manufacturer. Be aware that in most cases there is not a pure Android installed on your device, but many different OS enhancements directly lying on the top of the OS among with other applications from your device brand manufacturer. Mostly the phones from HUAWEI (with EMUI), SAMSUNG, XIAOMI (with MyUI) and others come with its own graphical enhancement and many pre-installed applications which can cause a malfunction of other applications. More to it, most of those brands have a memory managers running in the background and when there is a need for more system resources (e.g. in the time a call is being conducted) these managers suspend or kill any other applications to free the memory and/or CPU. This was reported by many of our users, but there are possibilities how to overcome this problem:
  • Check your phone settings : you should find a system Whitelist (list of protected applications) where you can add any application you don’t want to be touched by the system cleaning. Add the Should I Answer application there. Mostly it can be found under a) Settings (grey gear button) -> Security -> Applications; b) Settings -> Protected Apps; c) Phone Manager -> Settings -> Protected Apps (depends on your OS and mobile brand). THIS ACTION IS CRITICAL for every security application you would like to serve you well on mobiles with OS enhancement.

Memory managers and other installed applications

  • Your mobile is a genuine computer. On any of them more applications are running in the same time, some of them installed by you, some installed by your mobile device manufacturer (such applications will have more system permissions also with a right to postpone or kill other applications). To prevent this actions (which will cause that our application will not be able to provide its functionality properly) a few things can be done:
  • For less aggressive memory managers, we have included a possibility of switching the SIA application to run as a foreground service – such service is not (mostly, but not 100% – depending on the system settings which user can not change) postponed by other applications. If you were facing problems our app was not active to check some calls, please go to the SIA Settings (read the actual Manual ) and set the application as a Foreground service (also check the other advanced settings according to the Manual). Always check this if our app didn’t block any call depending on your app settings – this can be the cause : clash with other application and / or bad settings of our application and/or the system.
  • Other installed security applications such as memory boosters, memory managers, antivirus applications and other security apps can have a privilege to kill or postpone other apps causing their malfunction in a critical time. Most of them have something similar to a system Whitelist. If you are using such applications (most Huawei and Samsung phones have built-in apps of such functionality, you can find them with a broom icon mostly) please check their settings and try to find a Whitelist / List of protected apps and add our application there. Here below is a list of most common applications belonging to this group and a path where to find their Whitelist:
Application Whitelist location
360 Security Settings -> Boost Safe List -> Add
360 Security Lite Settings -> Boost Safe List -> Add”
Clean Master Phone Boost Me -> Settings -> Ignore List -> Task -> Add “+”
CM Security Lite – Antivirus Settings -> Ignore List
Clean Master Lite (Boost) Settings -> Ignore List -> Task -> Add “+” -> Add
CM Security AppLock Antivirus Sandwich -> Settings -> Ignore List
Avast Cleanup & Boost Cleaning -> Memory boost -> select app to protect -> Boost now
DU Speed Booster & Cleaner Phone Boost -> Long hold on App / Click on App -> Add to ignore list
Malwarebytes Anti-Malware Scanner -> Whitelist (next to Scanner Settings)
    Please be aware this list is not complete and the path where to find a Whitelist can vary from version to version.
  • Some users also may have other blocking applications installed and running consequently on the same device. Please be aware that if more blocking applications try to catch the same system events this can cause hardware or memory conflicts – always check if your multiple applications can really work together to your full satisfaction, not stress. Of course we would like to recommend you to use our application solely but for sure the other apps can offer different knowledge database, other functionality etc. Before reporting a problem with our application please try to check if the problem is not a clash with other app fighting for the same resources.

Well, long reading, but be sure the Android developers will add other wonderful (more or less) features to the basic system in the future. With each new version new problems can occur.