Hello.
Is the current Avast Mobile Security compatible with Android Oreo v8.0.0?
Why asking and not looking up the requirements ?
Because avast mobile security does not seem to handle the new Oreo method for installing apps for unknown sources. It states that install from unknown sources is enabled. However Oreo now handles it on an application level; you specify whether an application, such as Chrome or Google drive, is allowed to download apks from unknown (not Google play store) sources.
Also there were issues with the web browser component.
Also the page you mentioned, which I did read, just states android 4 upwards instead of stating something like android 4 to 7.
Also you would be better if instead of assuming all posters are too lazy to read, you actually started to learn to be more polite!
Asking a question has nothing to do with being polite or not.
I pointed you to the information as avast is providing it.
For questions and things not handled in the FAQ or on the avast website you need to contact avast.
You asked, in your original reply, why I was “… not looking up the requirements …”
Often forum users have more up to date knowledge that articles that are yet to be updated.
You could have easily answered yes, no, don’t know, it’s undergoing test etc.
All your answer has accomplished is losing Avast a customer, as it has made me remove Avast mobile security and not convert to the premium version.
I can’t say if it is tested, working etc as I don’t have a device with that Android version and do not work for avast.
Hi, best you wait for Tereza…
Hi, please be nice to one another, OK? 
@Canard, our app is not fully compatible yet, but we are working on it. Your comment has been very helpful, and I hope you can give our app one more chance, thanks!
Do you have ETA for Oreo compatibility? I have not been able to update the virus definitions since Sep 6, 2017.
My last virus database update was 170918-04 (18 Sep 2017) a manual check for virus definitions update only resulted in ‘Virus definitions update failed.’
And my last update was 170916-0*. Was that when I updated to Oreo? I don’t remember, but it could be.
Also I get the “Virus definitions update failed” warning.
I urge Avast to correct this misbehaviour. Or at least tell us how to act.
Whilst I didn’t record the actual date my phone updated to Oreo, it could possibly be close to the version and date I gave “170918-04 (18 Sep 2017).”
I would say it is not compatible with Oreo. I constantly get updates failed. never had a problem before Oreo. Last time I reported it they said they were working on being compatible with Oreo. I guess that didn’t work out.
Time to look for another product, sorry but if it doesn’t update its useless
Hi, there was an incompatibility issue, it has been fixed since AMS version 6.6.0, but on some devices the AMS needs to be reinstalled to make the fix work.
Disabling and waiting a while didn’t work on my phone, but a reinstall did resolve it.
Just checked my smartphone (Nexus 5x) on Android 8. Updates are not occurring automatically or manually. The only way to get the latest definitions is to constantly reinstall the software. Hope this is soon solved.
Yes it is - been fixed for v6.7.0, which has already been rolled out to a part of our userbase, the rest should by finished by the end of next week.
Thanks Tereza … look forward to getting this version.
Cheers Ron
The end of which week? I’m still on 6.6.0 and the updates are failing again. Also, the app keeps crashing.
I now have 6.7.1, you could try uninstalling avast and then install again from google play.