Blokada occasionally de-activates on its own

Me, too. Blokada+ 5.11 Android randomly disconnects. Only notifications I get from the app are when Blokada DNS stops working.

As previously recommended I have Don’t Sleep! running. WiFi on and connected to my GB router private 803.11ac network which is provisioned at 255 MBps via GB cable modem with fiber to our demarc.

…802.11ac network…

It’s nice to know that I’m not the only one who has experienced this behavior from Blokada. However, I don’t even get a notification when the Blokada DNS service stops working. I just wake up and find the little key icon missing from the top bar on my home screen.

I have phones running Android 7 (LG) which is fine, and vanilla (unmodified) Android 9 and 10, which both exhibit this behaviour. On the same phones, so does DNS66, Adlock, and Adguard full, with its native VPN extension. All phones are unrooted, which doesn’t help, and often isn’t now practicable for an ordinary-level user, and the old devs who used to be expert in the field have given up. My suspicion falls on the os. Clearly it’s a workaround to get ad blocking to work, and hardly encouraged by Google! So it’s flakey; which is hardly a selling point to buy, as I have done, is it? But we do it to help the devs and they need all the encouragement they can get! We just have to bear with it, whilst the devs do their best.

I agree that 5.11 seems to have regressed to needing a reset several times a day or every couple of days, putting Blokada well behind Adguard (which can now run for up to a few weeks) in terms of reliability. Adguard is the bigger operation, and better resourced. But these things change, and come and go. Blokada used to be significantly better. For most of us it’s a luxury, not a matter of life and death, after all, and one of life’s little inconveniences.

I’m just fortunate in being able at the moment to swop between Blokada and Adguard, depending on which is the better-behaved on the day!

1 Like

Same thing happens to me. Frequent disconnects of 5.11 Android. Metro by T-Mobile Stylo 4, Android 8.1.

Don’t Sleep running as recommended,

Blokada 5.11 DNS disconnected while writing this, despite being set Always On, etc.

Sometimes first DNS disconnected then Blokada+ dropped, both with no notification. DuckDuckGo continued to run but ads appeared.

1 Like

A post was merged into an existing topic: Not working on crunchyroll

My original post related to Blokada 4, but some of the subsequent posts mention Blokada 5. It appears that whatever is causing this deactivation issue is common to both versions. I mention this in the hope that it may give someone a clue to solving this problem.

It’s been over a month since my original post and so far no one seems to have an answer for this problem which I and others are having. Have I posted it in the wrong place?


It’s most likely not an app issue but your standard battery saving mode on android. Did you already enable “always on VPN” on your device.

Hi, @PC,

Thanks for your question, but I posted regarding that back in March in Post #8:

In case it helps to make things clearer, I’m including the following screenshot:

As you can see, this is what I get when I tap on “Always-on VPN.” The gear icon to the right of the Blokada VPN gives me two choices, Delete or Dismiss, neither of which I want.

I appear to be at a dead-end. Where do I go from here?


P.S. - BTW, the problem seems to be happening less often lately; don’t know why.

As of right now I’m absolutely clueless. It seems like your system is being very, very funky.
Could you please name the device again? Did you already provide logs of the issue happening to with a short but precise issue description?

To be precise, I’m using Blokada 4.11.1. As to the logs, I have not submitted any logs yet, so I downloaded the log file which turned out to be 5.3 MB! However, since I’ve not experienced this problem as often lately (for whatever reason), would it make more sense for me to wait until the problem occurs again, then send in an abbreviated log that includes that period of time, rather than sending a 5.3 MB wad of text data for the tech folks to wade through?


Certainly a log of when it occurs is preferable, difficult to find the problem if it’s not happening :wink:

I agree. :+1: I was willing to send in the 5.3MB log file if that was preferred, as the problem almost certainly occurred within that time, but 5.3MB of text is a lot of text to have to trawl through! I thought it would be kinder and more practical to wait for the next occurrence, then send in just that smaller section of the log file.

UPDATE: I’ve sent in a log after a deactivation event and it’s being looked at. Fingers crossed!

1 Like

UPDATE: There was some initial email discussion with Blokada tech support, but no answer yet.

UPDATE: I sent in another log six days ago after another deactivation event, but haven’t received a reply yet from Blokada.

Just something I’ve observed. It seems to help to keep Blokada (and other similar apps) alive, not just turning off battery saving options, but data saving options too, in phone settings, if we can.

Thanks for that thought. I have battery saving turned off, but I’m not sure where in Settings to find the data saving options you mentioned. I’m running Android 6.0.1.

That’s the problem. Android’s setting options aren’t consistent, between different phones, let alone versions. The earliest phone I have runs Android 7, with no specific data save option, but my Android 8 phone has the option on the quick settings pull down tile, but not in the full settings menu, as far as I can see. My Android 7 phone though has no issue with Blokada, its been running consistently for months, until I have to restart the phone for other reasons. Even the cleaning maintenance options don’t affect Blokada.

I have the problems on Android 9 and 10, with both Blokada and Adguard. But, perhaps strangely, they will crash constantly, usually after a phone reset, then settle down after a few days, until the next cycle starts. With Adguard that interregnum can be a few days to a few weeks. Mysterious, so the app devs have my sympathy.

The other thing I’ve noticed is that another app set to always use location service, rather than the option only when using the app, seems to cause a Blokada Plus crash, maybe when both are trying to use the location service at the same time, but it might be just poor design.

I can’t see my logs showing any obvious “cause”, but I can’t find a way round the issue that when the app crashes, logging stops.