Everybody who has any interest in Android OS is currently talking about Android Q beta that has been released just recently. The developers' blog post provides a lot of food for thought, but it doesn't answer the most important question: how does Android Q affect AdGuard? :) Read on to find out.
First of all, we feel obliged to say that a lot of things which we consider important were done right in this beta. We are particularly happy with all the privacy-related improvements that are coming to Android (for example, giving users more control over apps). However, some of the changes affect AdGuard in a negative way, and you should be aware of them before the update rolls out.
The main issue is that now it is harder to detect what app is connecting to AdGuard. Why is this so important? AdGuard is not just a simple DNS-level ad blocker. It is a fully-featured firewall, so it's crucial to be able to distinguish traffic between the apps. The same applies to HTTPS filtering — it won't be possible for the same reasons.
Good news is that in the latest AdGuard v3.0 beta this issue is partially fixed, depending on your preferred filtering mode:
- in local VPN mode, everything will work as it should
- in rooted local proxy mode, the firewall functionality and HTTPS filtering are still crippled, but they are going to be fixed by the time Android Q gets officially released
- in no-root proxy mode, the same issues exist, and we will not be able to fix them unless something changes in the future versions of Android Q. We recommend to avoid this filtering mode.