De1984
2.8.4 · GitHub
More about this app
App firewall without using an VPN; can also manage packages
De1984
Privacy isnโt default. Take it back with De1984 Firewall and Package Control.
The name De1984 is inspired by George Orwellโs novel Nineteen Eighty-Four, reflecting the appโs philosophy of resisting surveillance and reclaiming digital privacy. It symbolizes a reversal of the dystopian control described in the book, empowering users to take back control over their devices and data.
๐ธ Screenshots
โจ Features
๐ก๏ธ Firewall
- Multiple firewall capabilities: iptables, ConnectivityManager, NetworkPolicyManager, and VPN fallback
- Automatic firewall method selection based on device capabilities
- Comprehensive iptables for rooted devices provides kernel-level blocking with superior performance
- ConnectivityManager for Android 13+ devices with Shizuku, no root required
- NetworkPolicyManager with Shizuku on any Android version, selectable manually
- VPN backend as fallback for maximum compatibility (no root required)
- Block apps on WiFi, Mobile Data and Roaming separately with iptables and VPN. Roaming is part of Mobile Data: a Mobile block also blocks Roaming, and blocking or allowing Roaming does the same to Mobile. ConnectivityManager and NetworkPolicyManager block an app on all networks or none
- Block LAN access, enforced only by iptables
- Global firewall policies: "Block All by Default" (allowlist) or "Allow All by Default" (blocklist). Switching the policy resets the WiFi, Mobile, Roaming and LAN rules of every app to the new default, with no confirmation: those per-app exceptions are not kept, while each app's screen-off switch is. Apps on the system-recommended list keep theirs, and critical and VPN apps keep theirs only while "Allow Firewall Critical Packages" is on
- Captive portal detection: change the URLs Android uses to check for a captive portal, or turn the check off (root or Shizuku). This changes system settings, and they stay changed after De1984 is uninstalled
- Screen-off blocking to save battery and data
- Real-time network state monitoring and automatic rule application
๐ฆ Package Management (with Shizuku or root)
- Enable/disable system apps
- Force stop running apps
- Uninstall system and user apps
- Works with Shizuku (no root required) or traditional root access
- Filter packages by system/user apps, enabled/disabled state
- Search functionality for quick package lookup
๐ Privacy First
- Zero tracking or analytics
- No telemetry
- Local-only data storage
- No proprietary libraries
- Buildable from source
- 100% open source (MIT License)
๐ Requirements
- Android 8.0 (API 26) or higher
- For iptables firewall: Root, or Shizuku running in root mode. Shizuku started over ADB runs as the shell user and cannot create kernel rules, so this backend stays unavailable in that mode
- For ConnectivityManager firewall: Shizuku + Android 13+ (no root required)
- For NetworkPolicyManager firewall: Shizuku (no root required). On ROMs that do not implement
POLICY_REJECT_ALLit can only block metered background data, not WiFi - For VPN firewall: VPN permission (no root required, works on all Android versions)
- For package management: Shizuku or root access
๐ Permissions
- ACCESS_NETWORK_STATE: Monitor network connectivity for automatic rule application
- BIND_VPN_SERVICE: Create local VPN for VPN-based firewall backend
- QUERY_ALL_PACKAGES: View all installed apps
- POST_NOTIFICATIONS: Show notifications for new app installations (optional)
- RECEIVE_BOOT_COMPLETED: Start the firewall again after a reboot, if you had turned it on
- ACCESS_WIFI_STATE: Read the network state for per-network rules
- FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE: Keep the firewall services running
- REQUEST_IGNORE_BATTERY_OPTIMIZATIONS: Ask Android not to stop the firewall to save battery (optional)
- KILL_BACKGROUND_PROCESSES: Last fallback for force stop when neither Shizuku nor root works
- moe.shizuku.manager.permission.API_V23: Talk to Shizuku or Sui
- INTERACT_ACROSS_USERS: Read apps in a work, clone or other profile directly. A normal install cannot hold it: when another profile exists, De1984 grants it to itself through root or Shizuku, without asking
- WRITE_SECURE_SETTINGS, CHANGE_COMPONENT_ENABLED_STATE: Not granted to a normal install. De1984 only checks whether they are held, to show the permission status
- REQUEST_DELETE_PACKAGES, INSTALL_SHORTCUT, ACCESS_SUPERUSER: Declared, but no code uses them
- Shizuku or root access: For the iptables, ConnectivityManager and NetworkPolicyManager firewalls, for package management, boot protection and captive portal settings (optional)
โ ๏ธ Good to Know
If you use VPN mode, turn OFF "Block connections without VPN"
In Android's VPN settings, De1984 must not have "Block connections without VPN" (also called lockdown) enabled. De1984's VPN routes only the apps you have blocked through its tunnel โ allowed apps deliberately bypass it and use the network directly. Apps that share a user ID share one verdict, so an allowed app that shares one with an app whose rule blocks goes through the tunnel too. Lockdown tells Android to drop anything that does not go through the VPN, so it blocks exactly those allowed apps. On recent Android versions this switch is turned on automatically when you grant a VPN, so it is worth checking. The app itself does not warn about this.
iptables needs real root, not ADB-mode Shizuku
Shizuku started over ADB runs as the shell user (uid 2000), which cannot create kernel firewall rules. The iptables backend stays greyed out in that mode. It becomes available with root, or with Shizuku itself started in root mode.
AUTO mode never picks NetworkPolicyManager
Automatic selection tries iptables, then ConnectivityManager, then VPN. NetworkPolicyManager is available only by choosing it manually in Settings, and on ROMs that do not implement POLICY_REJECT_ALL it can block metered background data but not WiFi.
๐ค Contributing
Help make this app better. No contribution is too small!
How to Contribute
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
All contributions are valued and appreciated!
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
๐ Support Development
De1984 protects your privacy. You can protect its future!
Late nights for brighter days.
Created by Doru Moraru
How Shizuku is used
Can block apps without VPN, manage packages, protect boot, tune connectivity checks and see work profiles via `Shizuku`.
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
De1984 uses Shizuku to enforce its firewall without a VPN, manage installed apps and change system connectivity settings.
- Block apps without VPN: turn per app network access on or off through Shizuku using the system network policy service and the
cmd connectivity set-package-networking-enabledandcmd connectivity set-chain3-enabledshell commands. - Filter traffic by address: filter internet and local network traffic per app with
iptablesandip6tablesrules applied through Shizuku. - Enable or disable apps: enable or freeze installed apps for a user with the
pm enableandpm disable-usershell commands through Shizuku. - Uninstall and restore apps: remove apps with the
pm uninstallshell command and restore system apps with thecmd package install-existingshell command through Shizuku, and list installed packages withpm list packages. - Stop running apps: stop selected apps with the
am force-stopshell command through Shizuku. - Stay protected after reboot: install and remove a boot time block through Shizuku and reboot the device with the
svc power rebootshell command so the on disk state and live filtering agree. - Customize connectivity checks: read and change captive portal detection mode, server URLs, defaults and restore with the
settings get,settings putandsettings deleteshell commands through Shizuku. - See work and secondary users: enable cross user visibility with the
pm grantshell command through Shizuku so packages in other profiles can be listed and managed.
Android APIs or commands used
INetworkPolicyManager.setUidPolicyINetworkPolicyManager.getUidPolicypm enablepm disable-userpm list packagespm uninstallcmd package install-existingam force-stopcmd connectivity set-chain3-enabledcmd connectivity set-package-networking-enabledsettings getsettings putsettings deleteiptablesip6tablesdumpsys netpolicysvc power rebootpm grant
Notable details
Reading the current connectivity check values can work without Shizuku, changing or restoring them needs Shizuku. Boot protection and address level filtering are unavailable when Shizuku runs in its limited ADB configuration.
Changelog
What's new for version 2.8.4
- Root: iptables waits for the system lock, retries rejected rules (IPv6 too) and repairs drift found by health checks #121
- Root: a cancelled check no longer closes the shared root shell; the log lists rejected UIDs #121
- Firewall: no freeze when turning it on; cancelling the stop dialog no longer starts it
- Tile and widget: a tap while starting now stops it
- "Firewall did not stop" survives app restarts and names the right backend
- VPN permission prompt survives screen rotation
Permissions
19 permissions requested
Sources
2 sources
Sources
2 sources

