Hi, On miui you need to lock the dns66 first... If you want to clear all at recent app. You can do this by swiping down dns66 at the recent app and there's an option to lock it.... Hope it helps
when enabling the domain filters I am getting confused by the dots. Yes, I have read the explanation in this forum, but didn't help. Just to make sure I get this right: Entering the domain filter and selecting one filter list (i.e. adaway), I have to mark it with a green dot to be enabled. After refreshing it will download the filter list and block ads according to list. OR: Do I have to mark the filter list with a red dot to be enabled???
In videos and further explanations I see both. So please, anybody explains this detailed and straight forward to me... Big Thanks!!!
Did anyone ad further filter lists (country Germany) he can recommend?!
For hosts, red means Deny, as in "Deny access to stuff listed in this entry.". Green means "Allow", you can use it to unblock an earlier entry (so you could add a hosts file as deny, and then unblock individual hosts). It's conceptually a very simple table driven firewall-like thing - look at all the allow/deny rules, the last one wins (in firewalls, usually the first rule wins, but oh well, that would have made unblocking a bit annoying).
Not sure about German ad blocking lists. I don't recall any issues with just using the default ones.
An Android memory leak? No idea. In name resolving stress tests, Android studio shows me heap sizes increasing to 20 MB; but then the GC kicks in and it's back to 12MB again. Same for reconnecting. Right now Android says 48 MB used, 78 MB top in the last 3 hours. Studio says 14MB allocated, 5 MB free. After some more reconnecting, I'm at 15MB allocated, 9MB free (so really no change in my memory use, but Android keeps increasing the overall heap size).
Obviously there can be high memory usage if there are a lot of connectivity changes events: Android is garbage collected, and does not focus on memory usage. A garbage collector means that if you reconnect, your memory usage doubles, as both the old and the new memory is kept around until a garbage collection event. And garbage collection might also differ between devices. Generally, there is no need to collect garbage until there is memory pressure - just wasting the memory is faster and more energy friendly.
This release works around a memory leak in the
pcap4j library: The pcap4j library contains a
cache of properties for the packet factory, but
the cache has no upper bound and thus grows
indefinitely - see kaitoy/pcap4j#86.
It also updates all dependencies to their
Julian Andres Klode (7): WhitelistFragment: Correctly display changed toggle after scroll Configuration: Fix reading the itemsOnVpn array README.md: Add link to XDA Switch JSON I/O from JsonReader/JsonWriter to GSON strings: Some formatting cleanup Hack in the message for incomplete updates version 0.5.0 Julien Lepiller (1): French translation Naofumi Fukue (1): japanese translation Nikolay Buzovsky (1): Russian translation
I have some ideas for your app and provided you some new blocklists. I was wondering if you could hack together pi-hole to work on our local phones or take some of their features and add it to your app.
Please see feature request: