Blokada: Autostart after reboot is unreliable

[x2k13]

Moto X Play, Android 7.1.1, Blokada 2.2.3

Checked the start-on-boot switch to on.
Expected behaviour: Blokada loads after reboot.
Actual behaviour: Blokada doesn't load at all.

Starting the app manually everytime for now...

[peterroth]

Did you check if your ROM let the app start on boot? In some cases (for example on Miui) the app won't start automatically, even it is enabled in Blokada. In such cases, you have to enable it in the ROM settings.

[x2k13]

Moto X Play uses (near-) Vanilla Android, no skins or any other OEM overlays. There isn't any additional option to enable apps to be started on boot, only the app needs to do the request. Thanks for the hint, though. I have several other apps starting on boot without issues.

[x2k13]

Update:

Had the F-Droid 2.2.3 apk installed, removed it and installed the one from the first post of the xda thread (2.2.3-origin-slim). Looks like it's working now. Might be the F-Droid build being borked somehow.

Leaving this open for additional information.

[kar]

Did some more investigations on this. Notes to self:

• [x] Read https://developer.android.com/about/versions/oreo/background.html
• [x] Use JobScheduler from BootReceiver to start a JobService to start VpnService and promote to foreground
• [x] Adapt KeepAliveService to also work with periodic JobScheduler
• [x] Ensure KeepAliveService is a foreground service

[kar]

This should be fixed in 3.0.0 (not the preview). Feel free to reopen if you'll see problems still.

[chrisclark99]

For some reason adding Blokada to my notification toggles fixed this in Android 8.1.0