Have you explicitly tried pinging any block hosts? I had an issue where the provider was doing something with my data connection that bypassed the host file. But it worked on WiFi. Check with a ping in your shell. It may be an OS OR a provider issue.
I use Chrome and I have no ads.
I don't use other browsers like Opera, etc
I did have problems with Chrome but on an older version of Xiaomi.eu than what I'm using now.
I did find solution, it had nothing to do with AdAway (AdAway was properly filling hosts file - that's what AdAway only does and what is only responsible to do in the root mode), it was a problem with the ROM + Chrome, and only on WiFi connections whose DHCP pushed DNS server 1.1.1.1/1.1.0.0 or 8.8.8.8/8.8.0.0 (I had to ignore DHCP and put the other DNS server for that WiFi connection in the Settings/WiFi on the phone)
Few other users had similar problems on Mobile Connections and posted about, and their solution
Eg, I tested at that time by playing with disabled Hosts sources, I only set one or two sites like CNN.com manually to to Black list in AdAway, then I inspected was the site really added to hosts file, I tested then to open the site in Chrome, and so on.
In Chrome, there is a local "URL" where you could see which DNS server it uses and how it resolves the given URL (like that CNN.com), hence you can catch when Chrome ignores the hosts file and opens the site that was actually properly blocked in hosts fike), etc
I did post a lot about like 3/4 months ago when I was debugging for myself. If you dare you can search for the posts, study, and similarly investigate yourself. Since I solved for myself at that time and since with the new ROM I don't have the problem (I didn't need the workaround I used with the older ROM), I don't remember further details...
Last edited:
SchWeinSAuG
Senior Member
If the System is Read-Only then AdAway cannot write over the /system/etc/hosts and it works fully systemlessly - hence when module is disabled, there is no more mounting over the original hosts file
However, I really don't know about peculiarities with LOS. Or you have another module that also affects hosts file
Take the root explorer (like MiXPlorer and check /system/etc/hosts
What do you see in that file? Do you know how it looked original that you could compare to know if now is still different
@alaminus I dont think you have answered @zgfg question, although it was almost stated as an assumption. Is you system partition read-only?
If not, then, if you once ran Adaway in root-mode before switching to sytemless, then your host file in system has been changed, and switching systemless off will only return you to already last modified (by Adaway) host file
If not, then, if you once ran Adaway in root-mode before switching to sytemless, then your host file in system has been changed, and switching systemless off will only return you to already last modified (by Adaway) host file
Last edited:
Not entirely true for some reason.
A little over a year ago, I was asked to test AdAway (root mode) on official linage build(s) without the "systemless hosts" module.
Part of my side of the conversation.
With a custom rom (lineage) there will be free space in system.
This is by design so users can install addons like GApps.
Depending on how much free space you have left in system, is how large your hosts file can be.
The hosts file will be truncated when no more space is left.
Due to the GApps package that I had installed, there was not much free space in system.Checked on Pixel 5a with AdAway-6.0.2-20220616.
Lineage 19.1 - OpenGApps - Magisk v25101 [Snapshot June 20th].
The three defualt hosts sources show they are installed and 108522 blocked.
It seems the hosts file is limited to a size of 4096 directly writing to system.
Code:
barbet:/ $ la -laZ /system/etc/hosts
-rw-r--r-- 1 root root u:object_r:system_file:s0 4096 2022-06-24 19:19 /system/etc/hosts
With the systemless hosts module active, the file size is not limited.
Code:
barbet:/ $ la -laZ /system/etc/hosts
-rw-r--r-- 1 root root u:object_r:system_file:s0 3483938 2022-06-24 19:24 /system/etc/hosts
Using the defualt hosts sources.
Without the systemless hosts module, the hosts file ends at truncated line # 106.
127.0.0.1 01-allseason.net.
vs
127.0.0.1 01-allseason.net.daraz.com
With the systemless hosts module, the hosts file ends at line # 108531.
127.0.0.1 zzzyyzzzyyyzyyzyyyzzyyzyzzzzzzzzyyzzyyyyyzyzyyzzyzpol7196.cmkaarten.nl
Actually it ends at 108532 with an empty line.
With that said.
---
A far as I know..
The only way to restore the original hosts file would require a clean flash.
Lineage uses an addon.d script to backup and restore the hosts file when updating, so a dirty flash would only backup and restore the hosts file you currently have.
You can use AdAway to generate a basic hosts file that would be the same, save for the header info.
Code:
# This hosts file has been generated by AdAway on: 2023-08-13 10:10:48
# Please do not modify it directly, it will be overwritten when AdAway is applied again.
# This file is generated from the following sources:
127.0.0.1 localhost
::1 localhostTo do this..
1. Disable the systemless hosts module and reboot.
2. Open AdAway (root mode) and deselect all the hosts sources.
3. Apply.
Then you can enable the systemless hosts module and reboot.
From there, the new hosts file should be systemless as long as you have the module active.
Hope it Hope it helps more than confuse.
Cheers.
Last edited:
Thanks for the analysis.Not entirely true for some reason.
A little over a year ago, I was asked to test AdAway (root mode) on official linage build(s) without the "systemless hosts" module.
Part of my side of the conversation.
With a custom rom (lineage) there will be free space in system.
This is by design so users can install addons like GApps.
Depending on how much free space you have left in system, is how large your hosts file can be.
The hosts file will be truncated when no more space is left.
Due to the GApps package that I had installed, there was not much free space in system.
With that said.
---
A far as I know..
The only way to restore the original hosts file would require a clean flash.
Lineage uses an addon.d script to backup and restore the hosts file when updating, so a dirty flash would only backup and restore the hosts file you currently have.
You can use AdAway to generate a basic hosts file that would be the same, save for the header info.
Code:# This hosts file has been generated by AdAway on: 2023-08-13 10:10:48 # Please do not modify it directly, it will be overwritten when AdAway is applied again. # This file is generated from the following sources: 127.0.0.1 localhost ::1 localhost
To do this..
1. Disable the systemless hosts module and reboot.
2. Open AdAway (root mode) and deselect all the hosts sources.
3. Apply.
Then you can enable the systemless hosts module and reboot.
From there, the new hosts file should be systemless as long as you have the module active.
Hope it Hope it helps more than confuse.
Cheers.
Btw, I answered him then "I really don't know about peculiarities with LOS"
However, if System is not read-only on LOS but only limited in free space, @alaminus could also (if just to restore original hosts file):
- uninstall AdAway
- uninstall Systemless hosts (Magisk app, Modules screen)
- reboot
- manually edit /system/etc/hosts file to contain only:
Code:
127.0.0.1 localhost
::1 localhostOr (if not having enough free space at the moment when saving) to delete the hosts file and to create new one with localhost (and local domain) only
Btw, it can be checked in /vendor/etc/fstab.* file, if /system is "ro" or "rw" (read-only or read-write) and how many free space was left
One would think but...
You can not modify system directly because it is mounted read-only.
For some reason, AdAway has direct write access to the hosts file on lineage.
Not sure if it a leftover from older Android (when system was mounted RW).
¯\_(ツ)_/¯
Current Google Pixel(s) builds still set 0644 permission for the hosts file.
read-write for owner, read only for group and public.
Pixel 7a - [13.0.0 (TQ3A.230805.001, Aug 2023)]
Code:
lynx:/ $ ls -laZ /system/etc/hosts
-rw-r--r-- 1 root root u:object_r:system_file:s0 56 2008-12-31 18:00 /system/etc/hosts
lynx:/ $AdAway gives an error and can not write to the hosts file since there is no free space in system.
The second atempt give an error and tells you to install the systemless hosts module.
The second atempt give an error and tells you to install the systemless hosts module.
---
Back to Lineage.
Pixel 3a XL - Lineage 19.1 (12L) [lineage-19.1-20230812-nightly-bonito]
Code:
[ip@lost ip]$ adb shell
bonito:/ $ ls -laZ /system/etc/hosts
-rw-r--r-- 1 root root u:object_r:system_file:s0 248 2023-08-13 10:10 /system/etc/hosts
bonito:/ $ cat /system/etc/hosts
# This hosts file has been generated by AdAway on: 2023-08-13 10:10:48
# Please do not modify it directly, it will be overwritten when AdAway is applied again.
# This file is generated from the following sources:
127.0.0.1 localhost
::1 localhost
bonito:/ $ rm /system/etc/hosts
rm ro /system/etc/hosts (y/N):y
rm: /system/etc/hosts: Read-only file system
1|bonito:/ $ ls -laZ /system/etc/hosts
-rw-r--r-- 1 root root u:object_r:system_file:s0 248 2023-08-13 10:10 /system/etc/hosts
bonito:/ $ su
bonito:/ # whoami
root
bonito:/ # rm /system/etc/hosts
rm ro /system/etc/hosts (y/N):y
rm: /system/etc/hosts: Read-only file system
1|bonito:/ # echo "WTF">/system/etc/hosts
/system/bin/sh: can't create /system/etc/hosts: Read-only file system
1|bonito:/ # exit
1|bonito:/ $ exitWith root adb enabled under Lineage dev options.
Code:
[ip@lost ip]$ adb root
restarting adbd as root
[ip@lost ip]$ adb shell
bonito:/ # rm /system/etc/hosts
rm ro /system/etc/hosts (y/N):y
rm: /system/etc/hosts: Read-only file system
1|bonito:/ # echo "WTF">/system/etc/hosts
/system/bin/sh: can't create /system/etc/hosts: Read-only file system
1|bonito:/ # exit
[ip@lost ip]$Cheers.
PS.
Code:
[ip@lost ip]$ adb shell
bonito:/ $ grep 'system' /vendor/etc/fstab.sdm670
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
system /system ext4 ro,barrier=1 wait,slotselect,avb=vbmeta,logical,first_stage_mount
system_ext /system_ext ext4 ro,barrier=1 wait,slotselect,avb,logical,first_stage_mount
bonito:/ $That's strange. "ro" in fstab should make chmod 6xx (writable for system group) pointlessOne would think but...
You can not modify system directly because it is mounted read-only.
For some reason, AdAway has direct write access to the hosts file on lineage.
Not sure if it a leftover from older Android (when system was mounted RW).
¯\_(ツ)_/¯
Current Google Pixel(s) builds still set 0644 permission for the hosts file.
read-write for owner, read only for group and public.Pixel 7a - [13.0.0 (TQ3A.230805.001, Aug 2023)]
Code:lynx:/ $ ls -laZ /system/etc/hosts -rw-r--r-- 1 root root u:object_r:system_file:s0 56 2008-12-31 18:00 /system/etc/hosts lynx:/ $AdAway gives an error and can not write to the hosts file since there is no free space in system.The second atempt give an error and tells you to install the systemless hosts module.
---
Back to Lineage.
Pixel 3a XL - Lineage 19.1 (12L) [lineage-19.1-20230812-nightly-bonito]
Code:[ip@lost ip]$ adb shell bonito:/ $ ls -laZ /system/etc/hosts -rw-r--r-- 1 root root u:object_r:system_file:s0 248 2023-08-13 10:10 /system/etc/hosts bonito:/ $ cat /system/etc/hosts # This hosts file has been generated by AdAway on: 2023-08-13 10:10:48 # Please do not modify it directly, it will be overwritten when AdAway is applied again. # This file is generated from the following sources: 127.0.0.1 localhost ::1 localhost bonito:/ $ rm /system/etc/hosts rm ro /system/etc/hosts (y/N):y rm: /system/etc/hosts: Read-only file system 1|bonito:/ $ ls -laZ /system/etc/hosts -rw-r--r-- 1 root root u:object_r:system_file:s0 248 2023-08-13 10:10 /system/etc/hosts bonito:/ $ su bonito:/ # whoami root bonito:/ # rm /system/etc/hosts rm ro /system/etc/hosts (y/N):y rm: /system/etc/hosts: Read-only file system 1|bonito:/ # echo "WTF">/system/etc/hosts /system/bin/sh: can't create /system/etc/hosts: Read-only file system 1|bonito:/ # exit 1|bonito:/ $ exit
With root adb enabled under Lineage dev options.
Code:[ip@lost ip]$ adb root restarting adbd as root [ip@lost ip]$ adb shell bonito:/ # rm /system/etc/hosts rm ro /system/etc/hosts (y/N):y rm: /system/etc/hosts: Read-only file system 1|bonito:/ # echo "WTF">/system/etc/hosts /system/bin/sh: can't create /system/etc/hosts: Read-only file system 1|bonito:/ # exit [ip@lost ip]$
Cheers.
PS.
Code:[ip@lost ip]$ adb shell bonito:/ $ grep 'system' /vendor/etc/fstab.sdm670 # The filesystem that contains the filesystem checker binary (typically /system) cannot # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK system /system ext4 ro,barrier=1 wait,slotselect,avb=vbmeta,logical,first_stage_mount system_ext /system_ext ext4 ro,barrier=1 wait,slotselect,avb,logical,first_stage_mount bonito:/ $
Or, could it be that the AdAway's hosts file was installed by LOS recovery?
I have my older phone (Xiaomi, originally released with A9 and upgraded to A11)
/system is "ro" in fstab and with no root app I could write to the System
However, I mounted /system as read-write in TWRP and then, by using TWRP Advanced, File Manager, hard debloated (deleted their folders) several System apps. It made me free room and I was able then to hard-overwrite /system/etc/hosts file again from TWRP - by manually overwriting with current at that time AdAway's hosts file
Although not up-to-date with the always updated AdAway's /data/adb/modules/hosts/system/etc/hosts file, it still helps me to get rid of ads when I boot with stock boot.img and/or when I disable Magisk, boot it in Core only mode or with Systenless hosts module disabled
However, on my other, newer hone, I can only flash over the whole Super, I cannot delete or replace System files or folders from TWRP - by no means, TWRP could not really mount /system as writable
Last edited:
I *think* a true Read-Only system partition is defined by the hardware. As far as I am aware, there is no ROM or change to ROM source (eg FSTAB), that could make my Pixel 4A 4G allow or enable a read-write system partition. I could be wrong, but I think its in the hardware.
However, it is device specific, and on some other devices & ROMs, it will be imitated through software only. Even my older devices would boot with a RO system partition and would require a root enabled change to RW; and of course, root to then do the actual writes.
However, it is device specific, and on some other devices & ROMs, it will be imitated through software only. Even my older devices would boot with a RO system partition and would require a root enabled change to RW; and of course, root to then do the actual writes.
All partitions together (Boot, System, Data, etc), would be 'hardware'. If read-only by hardware, it would be like compact-disks, what they shipped, not even OTA would be able to overwrite, there would be no factory reset, nothing
It's not 'hardware'. That whole storage is divided to partitions by file-systems. They can be formatted as ext4 (system partitions), f2fs (usually data although on some devices it could be also f2fs), vfat - together with all attributes (ro or rw, encryption params, sizes, etc) it's described in the file-system table /vendor/etc/fstab.*
Btw, you can find a thread on XDA, I think it's dead now but they made it working (general concept, there are practical complications for various phones and ROMs):
- copy the firmware to PC
- reformat storage without read-only attributes (system partitions must be also expanded, otherwise there is no use of making them writable if they are full - data partition pays the price and must be shrunk)
- flash everything back
And you have the same ROM back but with fully writable Systems partitions
I think you misunderstood what I said. Its the limitation is built into the hardware level, which could mean the software internally on the hardware. I have yet to see any ROMs on these newer devices include a commit to switch over their current/actual/defrault system partition to Read-Write.,
As for the thread (I think I saw it), that is NOT the same as making the original system partition RW. I used to use a similar approach back on my first Android device, which had a tiiiiny internal memory (inc system). On that device the system partition was mounted/moved onto an external RW sdcard; with a boot scr[pt. That old thread (I think I saw) is partially the reason I think its beyond the ROM (eg FSTAB) to switch to a RW system partition on the running OS. And in that case, the original system partition remains as RO. PS On my old device, In later ROM builds, the moving of the partitions to use the SDCard, was baked directly into ROMs and you had to have an EXT4 partition on an external SDCard.
Do not forget the ROM does not speak directly to the hardware, it passes through/integrates with BLOBs supplied by the manufacturers, which are closed source. Those closed source BLOBs can partition hardware RW mem, to whatever they desire/wish.
If it was that simple, there would be a commit kanged around between ROMs changing it. Or even a Magisk script changing the FSTAB. So many people with custom ROMs would love to go back to the old days to modify the system partition. I have not seen such a commit.
Good afternoon:
I am hearing about a possible bug in Adaway, in its latest version. And the automatic turning.
It turns out that I have an acquaintance who says that when he turns the mobile, and the screen turns by itself. The total of blocked sites disappear, if Adaway is creating or copying a host. This process stops.
He says he has Lineageos 19.1 on a Google Pixel (Adaway with Magisk and systemless) . But he says it also happens to him on a Samsung with Android (Adaway without root).
Let's see if I can get more details on what is happening to him; as we didn't have much time to talk about this bug happening to him.
But I thought it was timely to comment on it in case the same thing happens to anyone.
Best regards
I am hearing about a possible bug in Adaway, in its latest version. And the automatic turning.
It turns out that I have an acquaintance who says that when he turns the mobile, and the screen turns by itself. The total of blocked sites disappear, if Adaway is creating or copying a host. This process stops.
He says he has Lineageos 19.1 on a Google Pixel (Adaway with Magisk and systemless) . But he says it also happens to him on a Samsung with Android (Adaway without root).
Let's see if I can get more details on what is happening to him; as we didn't have much time to talk about this bug happening to him.
But I thought it was timely to comment on it in case the same thing happens to anyone.
Best regards
How to whitelist androidacy site?
I'm unable to download from Androidacy Module Manager (AMM)
for downloading I have to restore original Host file.
I'm unable to download from Androidacy Module Manager (AMM)
for downloading I have to restore original Host file.
Similar threads
Top Liked Posts
-
1Guys, I'm back with a different issue. Since some time ago I switched from Magisk to KernelSU, the only thing I have to do is to grant root access to adaway, I dont have to install any module (systemless hosts etc...).
The application is working fine, I have been using the whitelist/forward list etc.. with no issues, but suddenly, it's not able to make changes, it shows the error "Failed to install new hosts file". It smells like ksu is not working, but it does for the rest of the applications, actually the current hosts file was generated by adaway.
I have tried to clean the storage, re-enable ksu etc... with no luck. I also haveenabled the verbose logging, but I can't find any log in the file system.
Any idea/suggestion? I'm unsure if the issue is related with ksu, but I think i never happened in the past with Magisk. -
4
Also try turning off adaway's webserver, that plays havoc with some apps3
Yeah, I don't know why that Web Server (proxy) is not disabled by default (it's purpose is to remove the blank boxes where adds should go), but it causes more troubles than goods3
If you are using AdAway in root mode than AdAway only puts lines into the hosts file like:
0.0.0.0 AAA bbb CCC
or
127.0.0.1 AAA bbb.ccv
to block AAA.bbb.ccc site (URLs are not case sensitive)
And automatically updates the hosts file if you enable that
PS: Disable AdAway's Web server in Preferences (I always assume it was disabled, that's first thing to do)
---
If you use AdAway in non-root mode than AdAway does not modify hosts file (it cannot without root) but uses DNS resolutions over a virtual VPN so again to resolve eg AAA.bbb.ccc to the non-routable IP address 0.0 0.0
And in non-root mode, you can whitelist apps for whom AdAway will disable its virtual VPN3
Glad it worked, i was going to give the same answer as @zgfg but suddenly remembered the webserver. -
3359AdAway
AdAway is an open source ad blocker for Android using the hosts file.
Google Play Store notice
According the Google Play Developer Policy, especially the "Device and Network Abuse" section, ad blocker like AdAway violates the "Apps that block or interfere with another app displaying ads." rule and can't be distributed on distributed on the Play Store.
As Free and Open Source Software, AdAway is available from F-Droid Store or this XDA thread :good:
Requirements
This application requires Android 8 or above and does no more require root.
For older Android versions, a rooted device is required.
Changelog
If you don't want to read each announce post of this thread, you can:
- Get a summary of all changes in the project CHANGELOG.md,
- Check any further details though the source code commits.
Downloads
Stable versions are available on GitHub releases and F-Droid Store:
- AdAway 6.1.1 - Latest stable version - check v6 announcement
- AdAway 4.3.6 - for Android versions older than Android 8
- AdAway 3.3 - for Android versions older than Android 4.1 Jelly Bean
The app provides an in-app updater for both GitHub and F-Droid builds.
Keep in mind beta channel is limited to GitHub builds, and F-Droid releases usually have a several days latency.
Problem? Read this
* If you use Chrome and still see ads on web pages, remember to disable the "data saver" or "reduced data usage" browser option.
* Check your APN settings for any proxy, the proxy itself could be allowing ads. Disable the proxy.
* After you install or make any change to AdAway, you must reboot for those changes to take effect.
* If you are still having issues please read and understand all the info in the wiki before asking for help here.
Otherwise, this is the right thread to discuss about it or file a bug report here.
Contributors
PerfectSlayer, Vankog, jawz101
Source Code: https://github.com/AdAway/AdAway170Hi all,
A new year is coming and I wish you all to have nice holidays :victory:
Just few words about this ending year. There was about 12 releases in 2019 which brings you a new UI, a lot of bug fixes, Android 10 support, Gist and GitLab hosting support and better Magisk support.
All of this is possible thanks to the community to help users to discover the app, learn how to use it and report any new bug and also your moral, nice words and thanks you can send to me, and financial support.
Thanks a lot for all donators, GitHub sponsor and the Pixel 2 you sent me to test Android 10 support.
For the next year, I hope to release the next version (V5), at least in beta to start. It's been 9 months since its first lines of code and things are working quite nicely.
It aims to make the app simpler to use for the main use cases, support rooted and non rooted devices and remove old hacks/workaround which are no more needed on recent setups.
But before this big next update, I still have time to fix current issue with a new release
Changelog:
- Fix GitLab hosting support (commit date parsing failed)
- Translation update
Thanks:
Special thanks to @gallegonovato for its helpful bug report and @Vankog for translation update.
Download:
AdAway 4.3.2 on AndroidFileHost (md5: 78fde09a0e92044c45e901bb1cec8e2e)159Hi all,
Long time no see! It's been more than two months since the last update.
I can't say I was not active on the project as I start working on a new version (5.x.y) as a side project.
I won't share the source code yet as it is not ready at all and I don't want to give an ETA but this new version targets the following goals:
- 1. Revamp the UI
- 2. Clean up old support
- 3. Address one of the main drawback of the app
1. The card based UI does not feel right. Welcome card takes too much space, update button / status has a lot of critic. I guess I can do better.
I started a new simpler and lighter design which provide the most useful information on home screen and all main actions to trigger in one tap (no more burger menu).
It is still under heavy development but I hopefully get a friend onboard, specialized in graphics and design, to help me :highfive:
2. In order to simplify the development, I clean up the app and remove support for old features.
I bump target SDK version so I finally get Java 8 language feature (it was released 5y ago…) and move to topjohnwu root library (instead of home made one). It means systemless support is now handled by Magisk and other root solutions will still work.
3. Think of what prevent most of users to use AdAway? Now it's gone!
It's not gone forever. It's still here but there will be a fallback to workaround it.
I won't tell more until the first public beta but I guess you get the point :fingers-crossed:
In the meanwhile, here is a new version!
Feedback:
GitLab, like GitHub do not set LastModified HTTP header so update status is not supported... yet!
Changelog:
- Add Gist and GitLab hosting support for hosts file
- Add option to set default IPv6 redirection
- Improve reboot command
- Improve UI for overlays
- Update translations
Thanks:
Special thanks to @MSF Jarvis and ralayax for theirs contributions and @andy356 for its helpful bug report.
Download:
AdAway 4.2.5 on AndroidFileHost (md5: ab81225745afaaa7646024109de299c0)148Hi all,
Feedback:
It works well here. I failed to reproduce as I change the HTTP client library and how I use it.
But update date for the source you link definitely works now.
Not really. You could choose a lot of different mode.
For example, F-Droid server watches AdAway GitHub repository to find tags which match a specific versioning pattern.
Thank you so much! :highfive:
Thank you too!
Changelog:
- Add hosts source download cache
- Add snackbar notification to update host from DNS request listing
- Update UI from Material Design to Material Theming
- Update gradle, plugins and dependencies
- Fix crash parsing not defined host source last modified date
- Fix native modules build script (required for F-Droid build server)
- Fix Transifex issues
Thanks:
Special thanks to all recent donators! Your help is really appreciated :good:
Download:
AdAway 4.2.0 on AndroidFileHost (md5: 023169e7c345ef7297095793024f8478)144Hi all,
I talked enough about it the past weeks and here it is: the first beta for the next version of AdAway.
As you know, the main feature is the removal of root requirement but it also comes with a lot of improvements like an easier to use UI, a builtin updater, new cache and databases to improve reliability or even a quick pause/resume adblocking button that 3rd party apps can control.
It took me literally a year and 330+ commits to build it (the first commit of this branch was April the 7th) and I hope it will be worth it.
It should allow the app to be viable in the future with root being more and more difficult to achieve at each new Android release and Google hardening SafetyNet checks.
I will try to answer to the most expected questions here so you still can post a link to this FAQ later to lost users.
FAQ:
Does this version replace the v4.x versions?
No. This is still a preview version and does not replace the stable one.
It is available to test it and report issues and feedback before being promoted to stable.
Can I upgrade and revert safely?
Yes. Both v4 and v5 use the same settings export format.
Why does this version targets Android 8+ Oreo only?
Like the v4, v5 is expected to offer support for latest devices.
Android 8 and above represent more than 60% of device distribution and will grew through time.
If you use an older device, root solutions work very well and v4 is here for you (like v2 and v3 stayed for legacy devices).
How the hell does it work without root?
This version provides two adblocking methods: the usual root one using hosts file and a new one using local VPN.
The VPN solution allows to filter and alter connections of your devices without root access.
Is using a VPN safe?
In the case of AdAway, yes. It uses VPN API but does not connect to a VPN server.
In the case of VPN client app, it depends.
To give you more details, a VPN client app uses the VPN API to create a virtual network interface on your device and redirect all your traffic into it.
If you imaginge the VPN like a pipe (the right word is tunnel), client VPN app outputs all your traffic on a VPN server which is able to check what you are doing on the Internet.
With AdAway, your network is not redirected to a VPN server but your device internet connection (same as no VPN). VPN API is only used to get traffic into it to break the connections to ad servers.
Is VPN use battery?
Yes, like everything you do on device.
Witouth root, a VPN service will be running permanently to filter your traffic.
Good news is it will only filter DNS traffic. Not all traffic is redirected into it so it won't be as expensive as you can fear.
Did you come up with this idea alone?
Absolutely not! I spent a lot of hours trying to find altenatives to hosts based adblocking (like routes or private DNS). But nothing was better than VPN based adblocking.
So we (MrRobinson and I) approched Julian Klode, developer of DNS66 more than three years ago to see if we can merge our apps. It wasn't that easy as we don't develop our apps the same way so I ended up by integrating the DNS66 adblocking method into AdAway. It is fine for Julian, his app is Open Source and he himself built it from the core code of AdBuster app (an VPN based adblocking app).
Should we stop using DNS66 for AdAway?
Not at all. DNS66 is a great app and provides some features that AdAway doesn't have (yet?), like DNS settings.
DNS66 is a great app, keep using it if you like it!
If both apps used the same adblocking method a year ago when I start this version, I keep adding feature to the VPN adblocking method and most of them won't be in DNS66.
If Julian ports them back to DNS66, it's great if it can help his app and users!
Is it me or the app put on weight?
Yes, the app significantly grew due to new libraries like VPN related ones and Android Jetpack.
It also stores more data on device: a http cache, a host database, a hosts copy, etc...
I think 15~20mo of storage is still fine.
Changelog:
Without further ado, check the summarized changelog (it was hard to summarize a one year development)
- Add new home screen
- Provides all main controls from one screen
- Displays currently blocked, allowed and redirected domains
- Displays current hosts sources status and control to force apply
- Add non root ad-blocking feature
- Uses a builtin local VPN to filter DNS request to blocked domains
- Based on the work of dns66 by julian-klode
- Allows to excluded system applications and per user applications
- Add builtin updater with changelog display
- Add feature to quickly pause and resume ad-blocking
- Add wizard screen for first run setup
- Add feature to display and filter all blocked, allowed, redirect domains
- Improve preferences screen
- Add broadcast receiver to control ad-blocking from third party applications
- Update Android target to Android 10
- Improve root and shell support
- Split translation files to easier understand their context
- Add GitHub action test and build tasks
Download:
AdAway 5.0.0 beta (sha2: 200fd7789b174735d3af5925b4e568b09475bb3f39a79d24d6617af4b19cd19d)
If you like my work, feel free to support me. Check my sign for donation links. Thanks all! :highfive:
