csagan5

The "Bromite adblock engine" was what was used up to v76 and was originally based on NoChromo engine.

The native Chromium adblock engine is the subresource filter and works with the modern NetworkService; this has already been answered on XDA, but basically it is more efficient and has a bit more features (CSS filtering).

AdAway uses hosts-based blocking, it is less precise than the one in Bromite but more powerful because it can block access also of any app; it is very similar to an IP-based firewall.

For most users Bromite itself will be sufficient; I see you are also using the SystemWebView, so I don't think you need to run AdAway, you can save CPU usage and battery without it. I suggest you try disabling/uninstalling it, there should be no difference in your experience.

Bromite author here (https://www.bromite.org ); I was contacted some time ago about the possibility to maintain a modified version of Bromite with a customised /e/ home page and list of search engines. Nothing particularly murky there, but after some Q/A I did not want to proceed with this type of cross-branding because fundamentally I do not want Bromite to be using or be affiliated with any cloud service and I concluded that /e/ invites users to swap Google for /e/ as a cloud services provider.

Now to the reason why I am commenting here: there is no GPL violation for the patches used in their /e/ browser but I find it a bit disappointing that nowhere it is mentioned that the browser is a complete Bromite build, minus the logo and renamed to '/e/ Browser'.

Most users are assuming that it is a Chromium fork developed by /e/ and will never reach the Bromite open source project, which is basically the way the project is kept alive.