Please pardon if I’m asking a stupid or rather obvious or already answered elsewhere question, but I’d like to know how can I tell if I’m using the latest compatible version of Blokada 5 (says here “blokada/5.6.0 (android-29 full release arm64-v8a samsung a51 touch api compatible)”) and, if not, how do I update it? The other day I received a notification and clicked to update, but was shown no indication whatsoever that it actually updated (in starking contrast to previous times it did) and my internet connection is extremely precarious, so I’m afraid the download might have been aborted because the internet connection abruptly ceased half-way (or probably right at the beginning).
Q1. Where did you download Blokada from?
A1: The official Blokada website (I wasn’t aware that it could be downloaded from elsewhere)
Q2. Which device do you use? Do you use a custom ROM? Do you know which OS version you are using?
A2: Samsung Galaxy A51 with Android 10. No idea what a “custom ROM” is. Other than that it is Android 10, I’m afraid not.
Q3. Please explain the issue as detailed as possible. Also include patterns you observed (like ‘it only happens on wifi’). The more information the better.
A3: I was given the option to update to the latest release and clicked it, but nothing happened. Generally it reboots Blokada, as if reinstalling it, though the configurations always remain. Also, there was no indication that it even downloaded the update before (not) installing it.
Q4. Since when are you facing this issue?
A4: Can’t really say, it was a while ago, but I just decided to follow up on it today. Sorry, I wish I could be more specific. If I’m right and this isn’t the latest version of Blokada, I would assume the problem happened the day the Blokada version immediately subsequent to 5.6.0 was released.
Q5. Did you already try to solve the issue somehow? If so: please state what you did.
A5: I tried to see if there was a manual update button or a comment about it on the Blokada help forum, and didn’t find any. But admittedly, I might very well have missed it (wouldn’t be the first time).