ShizuStore

ShizuWall

AhmetCanArslan

4.7.1 · GitHub

Download APK
Network Android 11+ 1 week ago GPL-3.0 Recommended
4.4k ShizuStore
123k GitHub
2.5k Stars
9 MB Size

More about this app

Open-source app firewall that doesn't depend on VPNs or root

ShizuWall Icon

ShizuWall

Android firewall without VPN.
Privacy-first, local-only, powered by Shizuku / local ADB daemon / Root.

English · Türkçe · Deutsch · Italiano · Português · Čeština · Русский · العربية · हिन्दी · 中文 · 日本語

 

Downloads (GitHub) Repo size Minimum SDK

Get it on Google Play Get it on F-Droid

Buy Me A Coffee

Works with

Android 11+ and one of these backends:

  • Shizuku (forks are supported)
  • LibADB: pairs over Wireless Debugging, no computer needed
  • Root

Why ShizuWall

  • No VPN: no packet interception, no persistent tunnel.
  • Per-app control: blocks networking per app, including work-profile and clone copies.
  • Private: offline-first, no analytics, no telemetry.
  • Quick access: Quick Settings tile, widget and floating button.
  • Automation: controllable through broadcasts from adb, Tasker, MacroDroid and similar.

Screenshot

ShizuWall main screen

How It Works

ShizuWall drives Android's connectivity chain 3, a platform mechanism that controls network access per package:

cmd connectivity set-chain3-enabled true                                # firewall on
cmd connectivity set-package-networking-enabled false <package.name>   # block
cmd connectivity set-package-networking-enabled true <package.name>    # unblock
cmd connectivity set-chain3-enabled false                               # firewall off

Android clears these rules on reboot.

Automation

Every broadcast needs an active backend. apps is a CSV list of app keys: a bare package name targets user 0, a prefixed one such as 150:com.example.app targets the copy in that work profile or clone space.

Firewall: shizuwall.CONTROL

Extra Type
state boolean, required true = block, false = unblock
apps string, optional Apps to block or unblock. Without it the broadcast toggles the whole firewall.
# Firewall on (state false turns it off)
adb shell am broadcast -a shizuwall.CONTROL -n com.arslan.shizuwall/.receivers.FirewallControlReceiver --ez state true

# Block an app and its work-profile copy (state false unblocks them)
adb shell am broadcast -a shizuwall.CONTROL -n com.arslan.shizuwall/.receivers.FirewallControlReceiver --ez state true --es apps "com.example.app,150:com.example.app"

With apps, the selection in the app follows: state true selects the apps and turns the firewall on if it was off, state false unselects them and leaves the firewall on. In whitelist mode apps addresses the allow list, so the two states are reversed.

New app: shizuwall.APP_INSTALLED

Reports a newly installed app, so the new-app policy and notification apply to it as if ShizuWall had detected the install itself. ShizuWall only sees installs in its own profile, so this is how to cover the others.

adb shell am broadcast -a shizuwall.APP_INSTALLED -n com.arslan.shizuwall/.receivers.AppInstalledReceiver --es apps "com.example.newapp"

No rule is applied while the firewall is off. Apps without the INTERNET permission are ignored.

Profile: shizuwall.PROFILE

Activates a saved profile: its app selection, firewall mode, per-app modes and Show system apps setting.

Extra Type
profile string Profile name, as shown in the profiles sheet.
profile_id string Internal id; checked first and unaffected by renames. The profile's Automation dialog shows the ready-made command.
force_enable boolean, optional Turn the firewall on after switching even if it was off.

One of profile or profile_id is required. If neither matches, nothing changes and a toast reports it.

adb shell am broadcast -a shizuwall.PROFILE -n com.arslan.shizuwall/.receivers.ProfileControlReceiver --es profile "Work"

Disclaimer

ShizuWall is provided "as is", without warranty. It relies on advanced system permissions, and the developer is not responsible for system instability, data loss or side effects of blocked networking. Always verify which apps you block.

Official sources are Google Play, F-Droid and this repository only. APKs from anywhere else are unaffiliated and used at your own risk. ShizuWall has no official website.

INTERNET is requested only for wireless debugging pairing (LibADB).

License

GPLv3. The bundled tracker signature data is licensed separately under ODbL v1.0, see TRACKER_DATA_LICENSE.md.

Credits

  • Shizuku: privileged command execution.
  • LibADB: wireless debugging and daemon connection.
  • Exodus Privacy: tracker signature database. ShizuWall bundles a trimmed copy and never contacts their API.
Close

How Shizuku is used

Can block internet per app, toggle firewall chain, detect foreground app and manage profiles via `Shizuku user service and shell`.

This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.

How this app uses Shizuku

Shizuku provides the privileged backend for the firewall, foreground awareness and profile shortcuts, without needing VPNs.

  • Block and allow apps: selected apps have internet blocked or restored per user, including allowing an app from a notification action and automatic block and allow as the foreground app changes, applied through the privileged service and with cmd connectivity set-package-networking-enabled shell commands through Shizuku.
  • Turn firewall chain on and off: the global firewall chain is enabled, disabled, reapplied or checked with cmd connectivity set-chain3-enabled and cmd connectivity get-chain3-enabled shell commands through Shizuku and with a direct system call through the privileged service when the firewall is toggled or reconciled.
  • Detect foreground app: the currently visible app is queried on demand and watched continuously through the privileged service, which reads the activity task system service, to support foreground aware firewall modes.
  • Dismiss notification shade: the status shade is collapsed with the cmd statusbar collapse shell command through Shizuku after activating a profile from a tile, when that option is enabled.
  • Open app settings for other users: the system app details screen for a secondary user is opened with an am start shell command through Shizuku from the app info dialog.

Android APIs or commands used

  • IConnectivityManager.setUidFirewallRule
  • IConnectivityManager.setFirewallChainEnabled
  • IConnectivityManager.updateMeteredNetworkDenyList
  • ServiceManager.getService
  • IActivityTaskManager.getTasks
  • IActivityTaskManager.registerTaskStackListener
  • cmd connectivity set-package-networking-enabled
  • cmd connectivity set-chain3-enabled
  • cmd connectivity get-chain3-enabled
  • cmd statusbar collapse
  • am start

Notable details

The same firewall rules and foreground detection can use a local daemon over LADB or a helper process instead of Shizuku, depending on the working mode chosen in the app.

Close

Changelog

What's new for version 4.7.1

Changelog

Added

  • Update check in settings

Changed

  • Reorganized settings layout

Fixed

  • Hybrid mode per-app selection #170
  • List gaps when toggling hide options

Full Changelog: https://github.com/AhmetCanArslan/ShizuWall/compare/v4.7...v4.7.1

Close

Permissions

16 permissions requested

  • android.permission.QUERY_ALL_PACKAGES
  • android.permission.POST_NOTIFICATIONS
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.INTERNET
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.FOREGROUND_SERVICE
  • android.permission.FOREGROUND_SERVICE_DATA_SYNC
  • android.permission.FOREGROUND_SERVICE_SPECIAL_USE
  • android.permission.SYSTEM_ALERT_WINDOW
  • android.permission.USE_BIOMETRIC
  • android.permission.WAKE_LOCK
  • com.arslan.shizuwall.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
  • moe.shizuku.manager.permission.API_V23
  • android.permission.WRITE_EXTERNAL_STORAGE
  • android.permission.READ_PHONE_STATE
  • android.permission.READ_EXTERNAL_STORAGE
Close