Release Notes

This version introduces relatively few changes, most of which were implemented to meet F-Droid publishing requirements.

Key Differences in the F-Droid Build:

No LADB Daemon Support: The F-Droid version lacks LADB daemon support because the daemon generator script (predictably) failed to run on F-Droid’s build servers.

File Size: Due to the exclusion of the daemon components, there is a noticeable difference in file size between the standard and F-Droid releases.

ShizuWall

A lightweight, privacy focused Android firewall application that blocks network connections for selected apps without requiring root access or VPN. ShizuWall leverages Shizuku and libADB to provide powerful network control capabilities. Requires Android 11 (API 30) or higher.

AdvertisementRemove ads, dark theme, and more with

Premium

Screenshots

Why ShizuWall is Different

No Root or VPN Required: Most Android firewalls require either Root access or a VPN service. ShizuWall uses Shizuku or a local ADB daemon, providing native system-level control without the common VPN drawbacks.
Per-app System Networking Control: Uses Android's connectivity service (chain-3) to enable/disable networking on a per-app basis — no packet interception, no VPN tunnel.
Privacy-first Design: The app is offline-first and does not phone home. There is no analytics, no tracking and no telemetry.

Notes

Firewall rules are applied using platform commands and are automatically cleared on device reboot (Android security limitation).That means, rebooting will revert anything done by ShizuWall.
No network calls from the app itself — it does not send any data to external services. The application requests android.permission.INTERNET permission to only support wireless debugging pairing (LibADB) features (connecting to the local ADB daemon). ShizuWall is designed to operate locally and does not initiate any connections to external servers.

Firewall Implementation

(what the app runs via Shizuku or the local daemon)

<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="# Enable firewall framework
cmd connectivity set-chain3-enabled true

# Block specific app
cmd connectivity set-package-networking-enabled false

# Unblock specific app
cmd connectivity set-package-networking-enabled true

# Disable firewall framework
cmd connectivity set-chain3-enabled false">

# Enable firewall framework cmd connectivity set-chain3-enabled true  # Block specific app cmd connectivity set-package-networking-enabled false <package.name>  # Unblock specific app cmd connectivity set-package-networking-enabled true <package.name>  # Disable firewall framework cmd connectivity set-chain3-enabled false

- Action: shizuwall.CONTROL - Component: com.arslan.shizuwall/.receivers.FirewallControlReceiver - Extras: - state (boolean) — true = enable, false = disable - apps (string, optional) — comma-separated package list to operate on. If omitted the app falls back to the saved "selected apps" set. Examples: - Enable firewall for selected apps: adb shell am broadcast -a shizuwall.CONTROL -n com.arslan.shizuwall/.receivers.FirewallControlReceiver --ez state true - Disable firewall for selected apps adb shell am broadcast -a shizuwall.CONTROL -n com.arslan.shizuwall/.receivers.FirewallControlReceiver --ez state false - Enable firewall for specific packages (CSV): adb shell am broadcast -a shizuwall.CONTROL -n com.arslan.shizuwall/.receivers.FirewallControlReceiver --ez state true --es apps "com.example.app1,com.example.app2" - Disable firewall for specific packages: adb shell am broadcast -a shizuwall.CONTROL -n com.arslan.shizuwall/.receivers.FirewallControlReceiver --ez state false --es apps "com.example.app1,com.example.app2"