[APP][ROOT/NONROOT][OFFICIAL] AdAway v6.1.0

[Danny1976]

Glad to read that it works now

Always, when you install/remove/disable/enable a module, phone must be rebooted (Magisk takes actions on modules only on reboot)

Also, Magisk mounts the systemless copy of your hosts file (AdAway writes to):
/data/adb/modules/hosts/system/etc/hosts
to
/system/etc/hosts

only on reboot - hence if you add something to Allow list, you should reboot to have the given host really allowed

The same holds for updating hosts sources - your new systemless copy of the hosts file will not be mounted to the system's hosts file until you reboot

For that reason I keep all auto-updates in AdAway disabled and every second day or so I manually open AdAway and let it update hosts sources - then I reboot the phone

Then,also, in the root/hosts phone, AdAway does not need to be given Auto start and Battery not-optimized permissions:
- you manually run the update of hosts sources and then you reboot
- on reboot, Magisk mounts the latest update of the hosts file and Android takes it for the built-in DNS resolver

After that, Magisk does nothing (until it will be updating the hosts file next time)

---

Of course, for the non-root/VPN mode it's the opposite

AdAway runs in the background to maintain the VPN

Also, on updating the hosts sources (or adding to Allow list, etc), AdAway will immediately use the newly updated internal hosts file - no need to reboot there

Thanks for the extensive explanation and educating me. Not many people take the time to educate others and its always good to learn something new. Really appreciated!!! Thanks

 

[joefuf]

Experiencing an issue with AdAway 6.0.3 since I installed the March 2023 security patch where RCS is not working on my Pixel 7 Pro. Even if I have no block lists enabled and the app is just on, it will return an error similar to what this bug captured.

Interferes with Google RCS (Rich Communication Services) messaging · Issue #3121 · AdAway/AdAway

Describe the bug When AdAway is enabled, I am unable to send or receive chat messages using RCS with the Google Messages app. For those who don't know what this is, it's an enhanced version of text...

github.com

Attempts to send an RCS message with Google Messages kicks back the message with an error: "Not sent, tap for options"

I am running the rooted version. After uninstalling and reinstalling, I am not presented with an option to install the VPN version either.

Not sure if it is related but I had similar Magisk issues that I can see were talked about recently on this thread. I had 25210 and rolled back to 25206. All of my other root functions and modules work fine.

I have attempted to add several DNS addresses to the allowed list, but none of them make a difference

https://user-images.githubusercontent.com/6218735/225933402-7ce5b4de-481c-4b97-8c46-ba97f324f9fd.png

Is this a common or known issue?

 

[osm0sis]

Experiencing an issue with AdAway 6.0.3 since I installed the March 2023 security patch where RCS is not working on my Pixel 7 Pro. Even if I have no block lists enabled and the app is just on, it will return an error similar to what this bug captured.

Interferes with Google RCS (Rich Communication Services) messaging · Issue #3121 · AdAway/AdAway

Describe the bug When AdAway is enabled, I am unable to send or receive chat messages using RCS with the Google Messages app. For those who don't know what this is, it's an enhanced version of text...

github.com

Attempts to send an RCS message with Google Messages kicks back the message with an error: "Not sent, tap for options"

I am running the rooted version. After uninstalling and reinstalling, I am not presented with an option to install the VPN version either.

Not sure if it is related but I had similar Magisk issues that I can see were talked about recently on this thread. I had 25210 and rolled back to 25206. All of my other root functions and modules work fine.

I have attempted to add several DNS addresses to the allowed list, but none of them make a difference

https://user-images.githubusercontent.com/6218735/225933402-7ce5b4de-481c-4b97-8c46-ba97f324f9fd.png

Is this a common or known issue?

We had that issue on Lineage on the OnePlus 9 Pro, and it was binder errors they had to hack around from upstream CAF. It was only after a certain amount of uptime, however. No issues with AdAway default list now that the Lineage devs have resolved that.

 

[joefuf]

We had that issue on Lineage on the OnePlus 9 Pro, and it was binder errors they had to hack around from upstream CAF. It was only after a certain amount of uptime, however. No issues with AdAway default list now that the Lineage devs have resolved that.

So you determined that it was an app issue or a block list problem?

I had been just using my own custom block list until now,

AdblockHosts/AdAway default blocklist.txt at main · jeffreyabr/AdblockHosts

Hosts file to block ads. Contribute to jeffreyabr/AdblockHosts development by creating an account on GitHub.

github.com

but even that is resulting in the issue.

I've been across several phones and updated with all of the security patches for the last three years, but this is the first time I've encountered the problem.

I had to uninstall for now, but man do I hate how intrusive mobile ads are. This is the first time I've been without AdAway in a long time. I didn't realize how bad the mobile experience is without it.

 

[Nergal di Cuthah]

I had to uninstall for now, but man do I hate how intrusive mobile ads are. This is the first time I've been without AdAway in a long time. I didn't realize how bad the mobile experience is without it.

I am running the rooted version. After uninstalling and reinstalling, I am not presented with an option to install the VPN version either.

It didn't give you the option of vpn because instead of uninstalling it (which keeps data) you should have cleared data for adaway, then once it's resetup as a vpn import the lists that you exported before clearing data (a step i could have mentioned at thr beginning of this post but i didn't ).

Edit: found this, helps with vpn but not rooted adaway
https://www.reddit.com/r/GooglePixel/comments/a7czep/_/ec20ayi

 

[joefuf]

It didn't give you the option of vpn because instead of uninstalling it (which keeps data) you should have cleared data for adaway,

So I cleared Storage, uninstalled, and rebooted, but when trying to reinstall 6.0.3, it still skips past the Root or VPN step. Is there something else to try? I downgraded to 6.0.2 which gave me the prompt, but had the same RCS issue. It must be something in the March 2023 update then because I've never had this happen before, yet I am surprised to be the only user posting about it. It worked fine on this phone for the first three weeks I had it before the update.

Edit: found this, helps with vpn but not rooted adaway
https://www.reddit.com/r/GooglePixel/comments/a7czep/_/ec20ayi

I guess I can try AdGuard. Haven't used any other ad blocking app in a long time.

 

[Nergal di Cuthah]

I guess I can try AdGuard. Haven't used any other ad blocking app in a long time.

I was more suggesting to white list in vpn mode those apps mentioned in the adguard thread.
ROOT MODE
If you revert to no hosts and reboot does it let you rcs? In that state adaway is doing nothing so i should guess it would work. I'd test myself but don't use google messages or anything with rcs at this point.
You keep saying march 2023 update, do you mean of your android or adaway. Adaway has not been updated in eight months.

Edit: Can you post the host sites you're using. I'm wondering if ads.google are required by rcs since it can send you adverts iirc.

 

[joefuf]

I was more suggesting to white list in vpn mode those apps mentioned in the adguard thread.
ROOT MODE
If you revert to no hosts and reboot does it let you rcs? In that state adaway is doing nothing so i should guess it would work. I'd test myself but don't use google messages or anything with rcs at this point.
You keep saying march 2023 update, do you mean of your android or adaway. Adaway has not been updated in eight months.

I am referring to the Pixel March 2023 security patch. I received this Pixel 7 Pro at the end of February, rooted with Magisk, and installed/configured AdAway just as I'd had it on my Pixel 6 Pro and my 3a XL before that. No issues with RCS until this week when I flashed the March 2023 update and rooted again (had a small issue with Magisk 25210, but was able to uninstall and return to Magisk 25206 to accomplish this).

Back to AdAway, I can't seem to get a clean uninstall of 6.0.3 that will allow me to reinstall and choose between root or VPN. There must be an app data folder somewhere that I am missing that I need to delete.

I had to drop down to 6.0.1 which I haven't had on this phone before. Made it a VPN setup and excluded all system apps except browsers. It sent and received a few RCS messages fine at first, but now it is waiting to deliver when a contact is online. Sent messages to two different people. Took a minute to send, but finally did.

 

[Nergal di Cuthah]

Ok (sorry p6p hasn't gotten march yet so i might be less helpful til rumored march 20)
In chat setting does it say connected. I assume you've not changed phone numbers or sims. Do you have fall back to sms mms turned on (it was default off when i momentarily switched to messages).
I assume you've turned chat off and on. And i assume when you rolled magisk back you also turned back the kernal boot. Running out of troubleshooting tbh.

 

[zgfg]

So I cleared Storage, uninstalled, and rebooted, but when trying to reinstall 6.0.3, it still skips past the Root or VPN step. Is there something else to try? I downgraded to 6.0.2 which gave me the prompt, but had the same RCS issue. It must be something in the March 2023 update then because I've never had this happen before, yet I am surprised to be the only user posting about it. It worked fine on this phone for the first three weeks I had it before the update.

I guess I can try AdGuard. Haven't used any other ad blocking app in a long time.

I think that AdAway v6.0.3 maybe checks if it was granted root - if yes, then it does not prompt to choose root or non-root

When you uninstall AdAway, it also wipes its Data but the root grant nevertheless remains in Magisk db

Hence wipe AdAway Data or uninstall AdAway, but then additionaly open Superuser list in Magisk and remove AdAway

Then (install and) configure AdAway again, it should prompt then for root or non-root mode

 

[Nergal di Cuthah]

grant nevertheless remains in Magisk db

It may also detect systemless hosts is installed running. Because when i was on magisk 25210 (modules don't work with this build) i was able to choose vpn and i didn't clean root grant.

 

[osm0sis]

So you determined that it was an app issue or a block list problem?

I had been just using my own custom block list until now,

AdblockHosts/AdAway default blocklist.txt at main · jeffreyabr/AdblockHosts

Hosts file to block ads. Contribute to jeffreyabr/AdblockHosts development by creating an account on GitHub.

github.com

but even that is resulting in the issue.

I've been across several phones and updated with all of the security patches for the last three years, but this is the first time I've encountered the problem.

I had to uninstall for now, but man do I hate how intrusive mobile ads are. This is the first time I've been without AdAway in a long time. I didn't realize how bad the mobile experience is without it.

Neither. Like I said, it was a ROM issue from upstream CAF that the ROM developers had to hack around. Once that was fixed everything worked fine. I only ever used AdAway default lists but I don't think AdAway had anything to do with it in my case.

 

[joefuf]

Ok (sorry p6p hasn't gotten march yet so i might be less helpful til rumored march 20)
In chat setting does it say connected. I assume you've not changed phone numbers or sims. Do you have fall back to sms mms turned on (it was default off when i momentarily switched to messages).
I assume you've turned chat off and on. And i assume when you rolled magisk back you also turned back the kernal boot. Running out of troubleshooting tbh.

Yeah, it says RCS is connected in Google Messages. Never changed my phone number or SIM card. I can fall back to SMS/MMS, but then I have to turn off/on RCS and disable AdAway to try to get RCS to reengage again.

When I rolled back Magisk, I just uninstalled Magisk, reinstalled the 25206 apk, patched and reflashed the init_boot.img, and I was good with modules again.

I've read about this RCS disable feature, but I have never used it or needed to use it

How to turn off RCS chats

messages.google.com

Not sure if that's what needs to be done or if that is for something else entirely. My old P6P is long gone.

I think that AdAway v6.0.3 maybe checks if it was granted root - if yes, then it does not prompt to choose root or non-root

When you uninstall AdAway, it also wipes its Data but the root grant nevertheless remains in Magisk db

Hence wipe AdAway Data or uninstall AdAway, but then additionaly open Superuser list in Magisk and remove AdAway

Then (install and) configure AdAway again, it should prompt then for root or non-root mode

Interestingly, I went through all of these steps with 6.0.3 installed, and after I wiped storage on the AdAway app (even before I uninstalled the app), it disappeared from the Superuser section of Magisk, so there was nothing to toggle off. I uninstalled again, reinstalled, and it still doesn't prompt for root or non-root. Just skips into the root app upon open and prompts for root permissions.

 

[Nergal di Cuthah]

I note that messages was recently updated

Google Messages tweaked to provide more clarity through minimalism

Sent? Received? Read? Things of the past. With Google Messages Now, we’ve got icons for that!

www.phonearena.com

have you tried adaway enabled older version of messages?

 

[joefuf]

I note that messages was recently updated

Google Messages tweaked to provide more clarity through minimalism

Sent? Received? Read? Things of the past. With Google Messages Now, we’ve got icons for that!

www.phonearena.com

have you tried adaway enabled older version of messages?

Have not. I'm on the beta of Google Messages, so my app gets updates like every other day.

I'm a little hesitant to try that kind of troubleshooting. Without going into it, I have like 20gb of texts on my phone, backing up and restoring everything going back to like 2013 every time I wipe or get a new phone. So Messages will have to cache it all which takes a few hours after a roll back.

I can live with the VPN version for now. Would like to know how to clear user data to get 6.0.3. if the March update comes out for other phones in the next few weeks and it becomes and issue, then I suppose that'll be our answer. If it's still just me, then I guess I'll have to try a new Messages app.

 

[Nergal di Cuthah]

I'm on the beta of Google Messages, so my app gets updates like every other day.

Does it do this on stable? I had no idea you were on beta. I'd look at the change log since you upgraded to android's march 2023 to see if the problem reveals itself.

 

[joefuf]

Does it do this on stable? I had no idea you were on beta. I'd look at the change log since you upgraded to android's march 2023 to see if the problem reveals itself.

I'm pretty technical, but even looking at the March 2023 Security Bulletin, I don't really know what I'd be looking for to determine if there's anything in there that might have caused a conflict with Messages/RCS and AdAway.

Pixel Update Bulletin—March 2023 | Android Open Source Project

source.android.com

If there's a changelog for Messages Beta releases, I'm not aware of it.

Strangely, when I woke up today and several times throughout the day, AdAway 6.0.1 running VPN mode with the latest Messages Beta installed started having the same issue. I couldn't send or receive RCS messages. Had to disable the AdAway app to get anything through.

I unenrolled from Beta for the stable version. Currently have messages.android_20230220_00_RC03.phone_dynamic installed. With the same 6.0.1 VPN version, I'm have the same issue. This version was released on March 7, so that predates the release of the March 2023 Pixel update.

Any other ideas?

 

[ipdev]

I'm pretty technical, but even looking at the March 2023 Security Bulletin, I don't really know what I'd be looking for to determine if there's anything in there that might have caused a conflict with Messages/RCS and AdAway.

Pixel Update Bulletin—March 2023 | Android Open Source Project

source.android.com

If there's a changelog for Messages Beta releases, I'm not aware of it.

Strangely, when I woke up today and several times throughout the day, AdAway 6.0.1 running VPN mode with the latest Messages Beta installed started having the same issue. I couldn't send or receive RCS messages. Had to disable the AdAway app to get anything through.

I unenrolled from Beta for the stable version. Currently have messages.android_20230220_00_RC03.phone_dynamic installed. With the same 6.0.1 VPN version, I'm have the same issue. This version was released on March 7, so that predates the release of the March 2023 Pixel update.

Any other ideas?

Using VPN mode, every now and then, I will notice something is not running correctly.
Mostly when switching between WiFi and Mobile Data.

For the lack of a better description, it is like AdAway VPN stalls.

When it happens, I normally just toggle AdAway off and on.

I do not recall if I had/have issues with Messages (Beta).
Phone (Beta), voice mail sync would sometimes be affected.

Sorry to say I have not had time to investigate and grab logs to make a report about it.

Cheers.

 

[joefuf]

Using VPN mode, every now and then, I will notice something is not running correctly.
Mostly when switching between WiFi and Mobile Data.

For the lack of a better description, it is like AdAway VPN stalls.

Good thought, but no similarity here. I rarely turn on WiFi. Left VPN on longer today and experienced the issue again on stable Messages.

 

[joefuf]

Alright, now I'm back to absolve AdAway. I have no idea what's going on here...

I uninstalled AdAway last night and reflashed the March 2023 Pixel update. Left my phone unrooted overnight, and it was still able to send RCS messages in the morning.

Rooted before breakfast with Magisk 25206 which is the version I installed when I first got this Pixel 7 Pro at the end of February. Still haven't reinstalled AdAway, but I am experiencing the same RCS message issue again. Using stable Google Messages too, not even Beta.

Everything had worked fine on it for the two weeks or so before the March update, AdAway v6.0.3 included. I had the same difficulty with modules not working on Magisk 25210 that everyone else did, so I uninstalled Magisk and rolled back to 25206. In that process of not knowing why my modules weren't working, I had Magisk 25210 patch and flashed the boot.img which I now know is unnecessary, but I also reflashed the stock boot.img after the fact.

So now I'm back to square one without a culprit. Despite being on what I thought was good footing, I started experiencing that "Not sent. Tap for options" issue with RCS in Google Messages. I suppose I can try to wipe my phone and reflash the March 2023 update, but that's going to take all damn day to backup and restore my SMS messages. Hate having to do that and reserve full wipes for major issues.

I know it's now unrelated from the thread topic, but if anyone has any additional ideas or thoughts, I would appreciate the help. I'm stumped.