I have experimented on the command line, so my comments have little to do with the GUI app.
However, both me and @chr1s noticed that connman behaves erratically. There’s no short explanation except that systemctl connman reload doesn’t always work as desired. You’ll have to read all our comments to get a better picture of the weirdness.
@chr1s already added whitelisting (i.e. block all Android apps, then punch holes for apps) to his script.
We were mostly discussing which range of user IDs should be blocked wrt the whitelist approach. Mine is stricter, and currently it disables network connectivity for apps even when they have their holes punched. I suspect one would need to punch one more hole for some android system user, instead of just skipping the first 10 000. But I’m still investigating.
For me the big question is whether this Android firewalling isn’t just security theater if any app can circumvent it by using an Android system user run mechanism instead. Or it could just be an online check.
I need a better on-device network monitoring tool.
tl;dr: just stick with @chr1s script. It’s safe. The added 69-block-android-system-firewall.conf is not part of it.