Update AdGuard v3.6.3 for Android: Android 12 compatibility and more

Gandalf_The_Grey

Level 53
Verified
Trusted
Content Creator
Apr 24, 2016
4,240
41,332
If you happen to read the release notes of AdGuard for Android on GitHub, you might giggle at the fact that the coming release of v4.0 has become sort of a local meme.

We've been waiting for it passionately and, at times when the release data was delayed, rushed things saying "Well, now it’s definitely the latest version before the Big Release".

But the dawning of a new era as we call it does not rule out the necessity of the intermediate builds and certainly does not invalidate the changes made and all the scope of work done. The changes in the recent v3.6.3 are abundant but they all are ‘under the hood’, so to say. We used to consider such tasks difficult to comprehend and not interesting for a regular user, but truth be told, they are the core of our product.

One thing that's easy enough to understand is Android 12 compatibility. We've tested the new version extensively on the new OS and happy to say that they are 100% compatible. Feel free to try it yourself if you're one of the early testers for the Android 12.

And if you'd like to get into the thick of things, here are some more changes that were introduced in the v3.6.3 update. In this version we focused on updating CoreLibs. Namely, we dealt with the priority of existing modifiers and added several new ones: $denyallow, $redirect-rule, $removeheader, and $specifichide. It might be of interest to users who'd like to create their own ad filters. Besides, we've made userscript exclusions work properly and fixed all issues found.
Release notes:
  • [Fixed] Proxy gets disabled after each AdGuard VPN update #3680
  • [Fixed] Stealth mode settings configured in the setup wizard are not applied #3747
  • [Fixed] AdGuard doesn't let users of the MEGA app log in #3837
  • [Fixed] "NetworkCallback was not registered" error when stopping protection #3870
  • [Fixed] Instagram doesn't work in Local HTTP Proxy mode (root access) #3879
  • [Fixed] NektoMe doesn't work when AdGuard is enabled #374
  • [Fixed] If a phone has access to an IPv6 connection, AdGuard for Android fails to connect to DNS-over-QUIC servers that are only accessible over IPv4 #3927
  • [Fixed] The issue with changing the language in the DNS section #3731
  • [Fixed] Root + Local HTTP proxy slowdown on Android 7 #3844
  • [Fixed] Check proxy connection status error #3848
  • [Fixed] TikTok doesn't work when AdGuard is enabled #3866
  • [Fixed] Wrong exclusions suggested for $removeparam rules in the filtering log #3873
  • [Fixed] Don't pass DNS64 settings to DNSLibs if IPv4 network interface is present #3886
  • [Fixed] Connection issues on Fujitsu devices
  • [Fixed] Issue with an expired security certificate
  • [Fixed] Extend public networks list to force IPv4 default route
  • [Fixed] com.android.browser connection issues on several devices
  • [Fixed] Stealth mode screen can't be scrolled
  • [Enhancement] Updated DnsLibs to v1.6.29 #3952
  • [Enhancement] DNS-over-QUIC (Removed "experimental" label) #3842
  • [Enhancement] Turkey - Turkcell VoWifi new IP address #3864
  • [Enhancement] Fanboy's Annoyance List's Subscription URL is broken #3865
  • [Enhancement] Enable HTTPS filtering by default for Edge Dev, Edge Beta, and Styx Browser #3897
  • [Enhancement] Do not hardcode excluding AdGuard VPN package from filtering #3923
  • [Enhancement] Added Yandex Browser to the list of browsers #3951
 

Gandalf_The_Grey

Level 53
Verified
Trusted
Content Creator
Apr 24, 2016
4,240
41,332
AdGuard v3.6.4 released:
This quick update fixes a bug that could have happened to our long-term users. If you have been using AdGuard for a few years and your security certificate expired, it could have lead to an HTTPS filtering failure. After this update, you will see a notification on the app’s main screen. Tap on it and follow on-screen instructions to reinstall the certificate and resume HTTPS filtering.
 
Top