Sent from my GT-N7100 using Tapatalk
As others have pointed out, posting some logs is essential, but then so is explaining exactly how "AdAway isn't working".
There isn't any problem as such you mentioned. It is installing, the host files are all there, it stays enabled and all free apps are popping up ads which used to be blocked without any trouble in Cyanogen OS 12. However, I just moved to AICP last night, the problem there was, I was using both inbuilt add blocker and adaway, which was maybe conflicting with each other, so disabled the inbuilt add blocker, kept adaway enabled, and working like charm, I have noted down the link which was shared by another user for capturing logcat, once I move back to Cyanogen OS 12.1 I will post it. I went across couple of posts in Reddit as well where people were talking about adaway not working on COS12.1, maybe cyanogen inc is pushing ad some other way than conventional ? However I understand none of these speculations are useful without proper logs.
There was discussion between AICP and Exodus devs about blacklisting Adaway and other ad blockers. Maybe they already started. Their built-in adblocker was a joke anyway.
I mentioned in an earlier post that AdAway's menu isn't accessible on Android TV devices running Android 5.1 or higher. This hasn't been much of an issue so far but now I'm noticing that the MLB.TV app on the Nexus Player does not load videos when AdAway's hosts file is in use. I cannot access the "Log DNS Requests" function to figure out what needs to be whitelisted. If AdAway can be updated to meet Google's full material design specs, then its menu should be visible on Android TV running Android 5.1 and higher.
|ad block, adaway, adblock, adblocker, source|
|Thread Tools||Search this Thread|