p=47049765 Ad Away has been spinning for 10 minutes at the "Applying..." stage.
Even after rebooting and manually installing a hosts file, I'm still able to resolve unwanted hosts.
/data/data/hosts [email protected]:/sdcard # ls -l /data/data/hosts -rw-r--r-- root root 881709 2013-11-04 hosts [email protected]:/sdcard # grep m./etc/hosts 127.0.0.1 [email protected]:/sdcard # ping m.PING s0-2mdn-net.l.(220.127.116.11) 56(84) bytes of data.
The hosts file contains a list of mappings between hostnames and IP addresses.
When an app requests an ad, that request is directed to 127.0.0.1 which does nothing.
If you're not part of the XDA Developers community, don't worry, XDA accounts are free and you can sign up with Google.
Access Point Names) and remove the value in the proxy field. Follow this Guide to find the corresponding hostnames and how to report them.
Finally, there were some suggestions of having Busy Box installed, and it does not seem to want to work.
The phone I'm running is on 7.1 beta, encrypted, with stock recovery, and phh's superuser.
One thing in addtion to @yecarrillo 's points: When ads in chrome are not blocked, the data compression proxy needs to be disabled: https://developers.google.com/chrome/mobile/docs/data-compression https://gist.github.com/ckuethe/da987a09b805ce7e5731 And after a fresh reboot, /etc/hosts does contain the generated list of blocked hosts but I can still ping them, so the resolver is not looking in the hosts file.
On Nexus 4 CM 4.4.2 Ad Away 2.2 and 2.8 both working fine.
Add Redirection Lists to your Hosts Sources to redirect blocked DNS requests to the correct IPs in China.