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. If not, you can get it from GitHub.
Furthermore, everything worked as it should have earlier; the adblocker was usually working. Many Chrome users have noticed that ad blocking doesn’t work with DNS or host-based AdBlockers. These host-based AdBlockers include AdAway, Adhell 3.1.1+, SABS, and more. There can be many reasons for this, such as enabled DNS sync and unvalidated firewall rules. So, let us figure it all out and fix it.
How can I fix SABS or Adhell 3 Chrome Not Working, Crashing, and Troubleshooting Chrome Performance Issues on Android for DNS Adblockers Like Adaway?
Our last paragraph listed several reasons SABS or Adhell 3 is compatible with Chrome for Android and Samsung Internet. A major potential fix is changing the Chrome flags. The 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, which is causing this issue. So, first, fix that.
By enabling the Chrome flag, you can activate Chrome features that are not enabled by default. Sometimes, though, there are Chrome features we find useful and wish to disable. For example, here, we don’t want DNS async because it is causing an error while using Adhell 3. So, let’s check out the instructions below to disable it.
- On Chrome, visit chrome://flags.
- From there, search for DNS.
- Under DNS settings, turn off the Async DNS option.
- 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 correctly, 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 from there.
- Lastly, restart Chrome, and you are 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 blocklist 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 a clearer view, you can reinstall Adhell 3 to give it a fresh start. So, after doing that, I hope these adblockers will work normally. If any reader still has a question, then ask them all below.
FAQ
Q1. Why is my AdBlock not working in Chrome?
Ans. There could be many reasons, but firewall validation and enabled DNS Async are usually the main issues.
Q2. How do I stop AdBlock blocking?
Ans. You can do that by turning off the AdBlock service.
Q3. Why do I still get pop-ups with AdBlock?
Ans. This is because your computer has been infected with a form of malware called Adware.
Q4. Is blocking AdBlock illegal?
Ans. There is no space for illegality here; it is entirely legal.