Adhell 3 is the latest and most actively developed fork of the AdHell/AdHell2/SABS family. Unlike its predecessors, it is exclusively available as a source package (no pre-compiled APK), allowing users to customize it as much or as little as they wish. A minimal level of technical know-how is required. But I assume you all know the basics about it, and if not, you can get it from GitHub.
Furthermore, everything worked as it should have earlier; the adblocker was working normally. A lot of Chrome users have noticed that ad blocking doesn’t work on DNS or host-based AdBlockers. These host-based AdBlockers include AdAway, Adhell 3.1.1+, SABS, and more. For this, there can be many reasons, such as enabled DNS sync and unvalidated firewall rules. So, let’s figure it all out and fix it.
How to Fix SABS or Adhell 3 Chrome Not Working, Crash, and Troubleshoot Chrome Performance Issues on Android for DNS Adblockers Like Adaway?
Our last paragraph listed a few reasons why SABS or Adhell 3 is compatible with Chrome for Android and Samsung Internet. The major potential fix we found was changing the chrome flags. The reason is Chrome Flag is a dedicated section for Chrome users to add additional features to their devices. Recalling the Chrome flags, we see that DNS Async is enabled, causing this issue. So, first, fix that.
By enabling Chrome flags, you can activate Chrome features that aren’t enabled by default. Sometimes, though, there are Chrome features we find useful and wish to disable. Like here, we don’t want DNS Async. Because it is causing an error while using Adhell 3. So, let’s check out the below instructions to disable it.
- On Chrome, visit chrome://flags.
- From there, search for DNS.
- Under DNS settings, set the Async DNS option to disabled.
- Lastly, close the tab, and you are done.
One more thing that you should do is flush your DNS cache. When it was initially enabled, it collected a few cache files. So, if you want Adhell 3 to function properly, you must clear the cache even if you have disabled it. To clear the DNS cache, follow these steps.
- Visit chrome://net-internals on your Chrome.
- Search for DNS in the given search bar.
- Now select the DNS tab and clear the cache files there.
- Lastly, restart Chrome, and you’re ready to use Adhell 3.
Besides that, Fixing Adhell 3 not working on Chrome for Android and Samsung Internet can be done by adding com. android.chrome|*|53 (Android) and com.sec.android.app.sbrowser|*|53 (Samsung Internet) to the blacklist as a firewall rule. This will block port 53 for Chrome, allowing DNS-based ad blockers to work. Remember to toggle firewall rules off and on for the changes to take effect. You can add that through Chrome Settings >> filters on Google Chrome >> Manage sites >> Blocked.
Conclusively, these are the basic things you need to do to get Adhell or SABS to work with Chrome. In case you experience another issue, make sure you have installed the right package of Adhell 3. If you want to have a clearer view, you can reinstall Adhell 3 to give it a fresh start.
FAQ
Ans. There could be many reasons but usually, firewall validation and enabled DNS Async is the main issue.
Ans. You can do that by disabling the AdBlock services.
Ans. This is because your computer has been infected with a form of malware called adware.
Ans. There is no space for illegal here; it is completely legal.
