I guess due to my stupidity and you overlooking this in the code reviewHmmm... if filter UDP is off (and filtering is on) why is packet.allowed then false in ServiceSinkhole.java?
I guess due to my stupidity and you overlooking this in the code reviewHmmm... if filter UDP is off (and filtering is on) why is packet.allowed then false in ServiceSinkhole.java?
I did no code review before because I am unable to read and understand the green/red gitHub diff listings and always have to download all source code first ... which I try to avoid. This GitHub thing makes me crazy ... and no, I will not spend time on that.I guess due to my stupidity and you overlooking this in the code review
No worries, I will fix it.I did no code review before because I am unable to read and understand the green/red gitHub diff listings and always have to download all source code first ... which I try to avoid. This GitHub thing makes me crazy ... and no, I will not spend time on that.
Your choice. Technically ok I think.
You can disable automatic updates for one app too. Just find the app in the Play store and use the three dots overflow menu.Hallo
is it by any means possible to push the Google Play version to Google Play only at least one week later than at Github's?
I use the Github version with its hosts filter on my two devices and I have it also installed on my friends two devices.
Each time an update is coming on Github (which is very, very often!!!) I hurry up to update all four devices, in fear that in the meantime an automatic Google Update would overwrite the good Github versions with the bad GP Update, before my manual update.
It is unfortunately not an option to disable automatic updates on Google Play, which would make me even more work.
I love active developed apps, no question, but daily updates is really difficult.
Could you at least hold the Google Play Updates back for a while then?
I have not tested yet, how long it takes, till a Google Play Update is available though, as I always hurry up to update from Github. Maybe its already a week back?
To see the shell in the app list, you may have to enable 'Show apps without internet' in the filter.I just updated and found out I can't ping from shell with last beta version 2.246.
Notification pops up to allow it but it points to application Shell with ID 2000 and it's empty.
Setting UDP filtering ON/OFF doesn't help.
EDIT: 2.247 same
Oh! This is new for me. Great feature of Google PlayYou can disable automatic updates for one app too. Just find the app in the Play store and use the three dots overflow menu.
To see the shell in the app list, you may have to enable 'Show apps without internet' in the filter.
As I cannot reproduce this and there seem to be no other people with this problem, I really don't know. The only thing I can think of is that there is a bug in your Android version/variant.
Please make sure power saving is disabled.I have been seeing this with my installation of Netguard as well, probably starting around one of the February releases: first few days, memory use is OK, but at some point, it jumps to 700Mb+ to over a gigabyte, and my phone slows down to a crawl.. At this point, the power management app built into my version of Android 8.1 pops up and informs me that Netguard is using most of my device memory and gives me the option to kill the app. If I kill it and restart, things are good for another couple of days..
I have filtering turned on, as well as logging, all the subnet stuff turned on. No notifications. Again everything seems to work fine for at least a couple of days, and then out of the blue, it starts eating memory. Netguard is designated as an always-on VPN in the system settings if that makes any difference.. I pulled logcats for Netguard, but there's nothing interesting that I can see, and the size of the file is also not huge and would not account for the memory use..
Other factors: Since I started seeing the memory issues, I have had two Android 8.1 system updates and I have also completely reset and wiped my phone once (the wipe did not fix the memory issue, but it did fix an OS issue which resulted in Netguard and a few other programs not saving the power optimization off setting and also not self-restarting after a reboot), so I can't rule out an OS bug, but the memory issues really did start appearing relatively recently, so if the core of Netguard has not changed, then perhaps a setting in the build tools or something external like that???
Good news: I have just made NetGuard working on my brand new Google Pixel 3a XL edit: with Android Q!
NetGuard works flawlessly on Android Q. Maybe even better than before because there is now an official Android API to map traffic to apps.Does it work flawlessly? This is only reason I think I have not upgraded to q beta.
Which version works? This is great news
My best guess this is being caused by a bug in your Android version.The only solution to prevent the high RAM consumption of Netguard over time is here - besides the periodic restart - to disable filtering. Unfortunately, this has some negative "side effects", especially due to the system-wide advertising prevention.
Filtering UDP traffic requires filtering traffic.Thanks Marcel. Those are great news about Android Q!
One question: if I don't use "filter traffic" (off) and I was using it that way before, with the new "Filter udp traffic" seen in grey color and deactivated, am I blocking udp traffic or I MUST activate "Filter traffic" now?.... If that's the case, I think it would be great to block udp without allowing to filter traffic, or maybe it's not possible.