[Android for Android] v3.0.287β

Not open for further replies.


Quality Assurance / Support Commando
Staff member
Another beta version for AdGuard 3.0 for Android. All the flashy stuff went into the first one, now it’s time to roll up the sleeves and do some good old bug fixing. Doesn’t mean, of course, that there’s nothing to talk about — we went over some of the more notable improvements in greater detail. Also, we can’t but mention that CoreLibs filtering engine grows better and better, this update contains the new CL version.

- [Fixed] Wi-Fi calling doesn’t work with AdGuard #2550

Due to the way Wi-Fi calling is implemented, you will face problems if you try to use it while having an active VPN. Up until this update, AdGuard wasn’t an exception — but it will be now. Without going into technical details (they are available by the link above), let’s just say we found a way to make AdGuard and Wi-Fi calling friends.

- [Added] Problematic devices detection #2458

It seems that more and more smartphone manufacturers follow the questionable trend of killing apps whenever they feel like it. Some brands and models do so more often than others. Fortunately, there are certain steps you can take to improve the situation, and these steps vary depending on your particular device.

AdGuard learnt to detect such problematic smartphone models, and when it gets killed like that for the first time, it will show you a notification that explains what just happened (accompanied by some pieces of advice how to prevent that in the future). It is not a cure-all (if only there was one), but definitely better than nothing.

- [Improved] Added fallback DNS servers #2490

If for whatever reason your current DNS server becomes unavailable (doesn’t matter whether you use one of the servers from the list we provide or a custom one), AdGuard uses your system default DNS as a fallback server. Not an ideal solution, so now you can indicate any DNS server (or even multiple) to be used as a fallback. Go to “Advanced Settings > Low-Level Settings” to set it up.

  • [Changed] License status notifications #2460
  • [Changed] Old notification text in HTTPS Filtering #2510
  • [Changed] The app UI is distorted in Arabic #2547
  • [Changed] “Data saved” value goes beyond the bounds #2549
  • [Fixed] Main stat doesn’t change after resetting the statistics #2506
  • [Fixed] A filter group doesn’t get enabled if a filter is enabled from search #2590
  • [Fixed] Adding AdGuard widget doesn't work correctly #2484
  • [Fixed] Crash after search in Apps Management #2508
  • [Fixed] Battery consumption displayed wrong #2487
  • [Fixed] Browsing security event has wrong status in Filtering Log #2512
  • [Fixed] “Content Blocking" menu is missing #2599
  • [Fixed] Custom launchers break widget's size #2521
  • [Fixed] Incorrect notification is shown after checking for updates when there is no connection #2502
  • [Fixed] Protection is restarted when enabling a filter group with all filters disabled #2589
  • [Fixed] Empty Stealth mode parameters in Filtering Log #2495
  • [Fixed] Landscape orientation UI errors #2612
  • [Fixed] Filters in disabled groups receive updates #2581
  • [Fixed] Recurring warning notifications in Apps Management #2481
  • [Fixed] “I agree with Terms" button is not visible on screens with small resolution #2571
  • [Fixed] Incorrect animation #2597
  • [Fixed] Outdated filters can't update their descriptions #2486
  • [Fixed] Extra icon in Custom filters group section #2592
  • [Fixed] Protection is not restarted after enabling the Custom filters #2517
  • [Fixed] Side menu is always opened after restarting the app #2479
  • [Fixed] Social media filter gets disabled if you skip the onboarding screen after update #2545
  • [Fixed] Support menu bug #2561
  • [Fixed] Switches randomly change their states after screen rotation #2559
  • [Fixed] The license page does not fit on the screen #2464
  • [Fixed] Menu items disappear on the promo screen #2504
  • [Improved] An icon added for the recommended filters on the filter groups screen #2556
  • [Fixed] AG connecting to a proxy which is not added yet #2543
  • [Fixed] Connection is lost when DoH/DoT is enabled #2475
  • [Fixed] DNS appears in Apps management search results #2505
  • [Fixed] IPv6 upstream addresses are used for default DNS providers #2477
  • [Fixed] No internet connection via root proxy on T-mobile #2428
  • [Fixed] Wrong custom DNS server name for DOH stamps #2514
CoreLibs & Crash
  • [Improved] CoreLibs updated to 1.3.207 #2621
  • [Changed] CL version added to the state file #2509
  • [Fixed] Crash after settings importing #2503
  • [Fixed] Crash in the Apps Management settings #2308
  • [Fixed] When selecting a quick install, automatic crash reporting doesn't turn on #2497
  • [Fixed] Compatibility issues
  • [Fixed] Localization issues
  • [Fixed] Stealth Mode settings persist in Filtering Log requests after license reset #2534
  • [Fixed] “Disable Whitelist” doesn’t work #2218
  • [Fixed] Requests highlighting issue #2474
  • [Fixed] HTTPS Filtering settings bug #2582
  • [Fixed] Importing settings from a file does not transfer filter settings #2513
  • [Fixed] Infinite loading after download fail #2560
  • [Fixed] Magisk Manager unable to pass SafetyNet check with AdGuard enabled #1894
  • [Fixed] Settings backup does not contain app settings #2492
  • [Fixed] Cookies TTL can’t be 0 #2548
Last edited:


New Member
There has to be a bug in today's beta build as it wants to update again and again. It's an infinite loop.
Same here. Hit refresh in the app, get notification that update is available with changelog screen, hit update, installs. Hit refresh again, offers update again.

I think it's a problem with the build number It's actually incorrect in the update screen. I'll add a screenshot so you can see. It says 3.291 at the top, and is actually 3.0291. The app is forever finding itself out of date because the update is always a higher build number than what is installed.


Last edited:
Not open for further replies.