-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blokada not letting traffic through after Doze #947
Comments
Thanks for reporting this. I have recently released an update that is meant to address it. Could you confirm if it works for you? |
My system: Google Pixel 4a on Android 13. I was on blokada 22.4.1 (and earlier versions) when I experienced the issue reported here. But since a couple of days I haven't experienced the issue anymore while still being on 22.4.1. This may or may not have to do with having installed the "Android Security Update 2022-10-05" a couple of days ago. |
v22.4.7 appears to have resolved this bug |
After updating to latest stable v22.4.14, this bug came back |
I'm still on on blokada 22.4.1. For me the bug seems to have come back as well, but in my case the problem seems to have resurfaced since I updated "Android Security Update" from 2022-10-05 to 2022-11-05. |
In my case, the Security Patch Level had no effect on the bug's reproducibility |
Stable v22.4.20 appears to have resolved this bug for me again. |
Blokada 5, ever since the whole rebranding thing in July, doesn't let traffic through (other apps stuck loading and/or claims offline) after resuming from Doze.
In that case, either turn Blokada off then on again, or just wait a while, and traffic will resume again, until next time the device enters Doze.
Blokada is already set to Unrestricted battery use, and Private DNS is Off.
Pixel 6, reproducible on both Android 12.1 July patch and Android 13 August patch.
The text was updated successfully, but these errors were encountered: