Kaspersky Internet Security has the following known issues and possible solutions on Meizu devices:
Kaspersky Internet Security may not work correctly when the device is in the sleep mode. To fix this, go to Settings > Device > Power Management > Energy consumption > Optimization of energy consumption > Sleep mode management and allow Kaspersky Internet Security to keep working in sleep mode.
Some steps may be different, depending on the device model and version of the operating system.
Kaspersky Internet Security may not start after the device is restarted or the app is unloaded from memory. To fix this, grant Kaspersky Internet Security permission to autorestart.
Kaspersky Internet Security may be unloaded from device memory. For the app to work correctly, lock the app in memory.
For example: on Meizu M5 Note Flyme 6, go to Security > Permissions > Run in background > Kaspersky Internet Security > Allow running in background.
Some steps may be different depending on the device model and version of the operating system.
MEIZU M2 MINI:
The caller ID info in the pop-up window may not be displayed on a Meizu M2 Mini with Flyme 5.
MEIZU PRO 6 PLUS:
Kaspersky Internet Security may not get access to permissions on Meizu Pro 6 Plus with Android 6.0.1, thus the app cannot work properly. To fix this issue, please upgrade to Android 7.x. Otherwise, do the following:
Go to Settings > Apps > Kaspersky Internet Security > Permission management.
Grant all permissions by setting permissions to ON, or tapping a permission name and then selecting Allow from the list.
On Meizu devices, the secret code for Anti-Theft must not contain more than 4 digits.
If you set the secret code which is more than 4 digits long, you will not be able to unlock the device with it. In this case, you will have to contact the Meizu service center to restore access to the device.
After you send the Mugshot command through the Anti-Theft feature to a Meizu device, the device may display a request on accessing the camera or location service instead of blocking the device. It is confirmed that the issue occurs on Meizu MX4.