So let us answer it here; the android encryption is based on dm-crypt and is provided by linux kernel and all the operation is quite tricky. Basic encryption / decryption is done on file system, so mainly /data directory (where applications data and applications are placed) is maintained. There is framework in DVM, which is providing the mount and file operations services with encrypted files. The problem is with the initial password insert, because the system partition is basically still encrypted and the password is not provided - there is some minimal UI for providing it, but, unfortunatelly, it runs with system services and apps, which has to be restarted, file system remounted and services must be triggered to run again with synced data. Here, as you may be can see now, the avast scaner or file shield can experience very difficult times - in case you have crypted your device, our scanner can extensively drain battery (application restart and getting priority in apps race) and CPU; in the worst scenario (encryption key is corrupted) the /data partition is not mounted and no application will be able to run, or, will force close soon. So, generally said, it is safe to use avast on encrypted device, but encryption itself has many traps along.