blokada will auto start after boot or reboot
blokada does not autostart after boot or reboot
Need to open the app on time to reconnect to vpn
(All setting tried, also tried permanent vpn on vpn setting)
Blokada version
3.4.100500 downloaded from F-Droid
Device model
ONEPLUS A6003 (Oneplus 6)
Android version / ROM
Oreo 8.1.0 / OxygenOS 5.1.8 (Non-rooted)
How long have you been using Blokada?
1 day
How long time ago has the problem started to happen?
Since I started to use
How often does this problem happen to you?
every times I try to reboot the devices
Do you have other VPN app? Do you know if you have internet connection when your phone boots up? What happens if you disable "Online only" and restart your phone?
Thank you for your reply.
1)Do you have other VPN app?
Originally have dns66, I uninstalled it, reboot and try again, same result
2)Do you know if you have internet connection when your phone boots up?
The WiFi sinigal icon show up in less than 1 second after boot
3)What happens if you disable "Online only" and restart your phone?
Same result, does not autostart until I open the app
Friend, you're saying that you've turned on "always on VPN" in VPN setting? That what you mean by "permanent VPN" right? It should work.
Do you have any app ops in settings? You might check if by chance its disabled there.
Lastly, toggle the "keep alive" option in blokada. If the permanent notification is annoying, hide it or reduce to low importance from device's notification options.
Thank you for your advice.
All app ops are on
keep alive is on
always on VPN is enabled
still having the same result, the always on VPN still it was disconnected after reboot.
I can confirm this behavior on Oneplus 5 stock non-rooted OOS. Blokada doesn't autostart, manual start required which is rather annoying. DNS66 autostarts fine.
DNS66 autostart also works fine on my device
FWIW: On OnePlus 5T, autostart works fine for me. App version 3.4.100500 via F-Droid, phone model A5010, OxygenOS 5.1.3, Android 8.1.0.
No special permissions, battery optimizing enabled, only setting in app enabled is Start on boot.
Maybe this solves the problem.
We should add
<action android:name="android.intent.action.QUICKBOOT_POWERON" />
to the core.BootReceiver.
Can you all please check if you experience the same behaviour with the new, 3.6 version? The start-on-boot feature is improved there.
This problem seems to be fixed in 3.6 version, auto start works fine even without turning on the "always on VPN" in VPN setting
FYI, I am using Android 9 right now
great to read, thanks for the feedback.