Quote:
Originally Posted by mergen3107
@popej
You can also go to AFWall settings and enable the reboot daemon workaround. This is just in case, so when the device reboots with Wi-Fi AFWall+ activates before the actual internet traffic kicks in.
|
Hey guys, it seems to me like AFWall+ is not starting reliably at boot even with root, Startup fix through /data/adb/service.d/, auto startup enabled in app management, batt optimizations off. I have to manually open the app to get the "Firewall Enabled" notification to come on. Before I do, I can see in AdAway and PCAPdroid (which i also have to manually start despite setting it to load on boot) that there are connections being made and data being sent.
The only way I have seen that does anything is editing the hosts file, but this is per ip and not per app.
Is AdAway (Hosts file) solution, good enough to redirect to 127.0.0.1 all the ***.boox.com traffic instead (or alongside AFWall+)?
How can I get AFWall+ to start automatically and do what it is supposed to do?
I wish I could just disable internet permissions for certain apps, but Xprivacy is long dead.
Thanks!