Skip to content
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

Open
shsui5379 opened this issue Sep 3, 2022 · 8 comments
Open

Blokada not letting traffic through after Doze #947

shsui5379 opened this issue Sep 3, 2022 · 8 comments
Assignees
Milestone

Comments

@shsui5379
Copy link

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.

@kar
Copy link
Contributor

kar commented Oct 31, 2022

Thanks for reporting this. I have recently released an update that is meant to address it. Could you confirm if it works for you?

https://github.com/blokadaorg/blokada/releases/download/android-v22.4.7/app-five-release.apk

@kar kar self-assigned this Oct 31, 2022
@kar kar added the type-B Bug label Oct 31, 2022
@kar kar added this to the 22.4.7 milestone Oct 31, 2022
@Abdull
Copy link

Abdull commented Nov 1, 2022

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.

@shsui5379
Copy link
Author

v22.4.7 appears to have resolved this bug

@shsui5379
Copy link
Author

After updating to latest stable v22.4.14, this bug came back

@Abdull
Copy link

Abdull commented Nov 15, 2022

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.

@shsui5379
Copy link
Author

In my case, the Security Patch Level had no effect on the bug's reproducibility

@shsui5379
Copy link
Author

Stable v22.4.20 appears to have resolved this bug for me again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants