This release brings major interface improvements, new programs and modes, better stability, and a number of important fixes across both the app and backend. What’s new: • Added new programs and dedicated screens: Tor, WireGuard (wireproxy), myproxy, and myprogram • Added the new blockedquic module for forcing selected apps away from QUIC • Added proxyInfo notifications for suspicious app activity and system scanning attempts • Expanded the statistics section so new services are displayed correctly in the process list • Updated management screens for programs, servers, bridges, and connection parameters What’s improved: • Significantly reworked the app interface • Improved adaptation for small screens • Updated the main screen, log block, statistics section, and program list • Added a new full-screen startup experience with animation, loading progress, and a smoother transition into the app • Improved state preservation between tabs and restored list positions after navigation • Optimized client-side API behavior: fewer redundant requests, faster state refresh, and smoother updates What’s fixed: • Fixed layout and interaction issues on small screens • Fixed various build errors and UI regressions • Updated client compatibility with the new boolean-based API logic • Improved proxyInfo handling and related apply requests • Fixed issues in Tor, myproxy, myprogram, and SNI/server management screens • Reduced log flickering, unnecessary screen recreation, and state reset problems Technical changes: • Strengthened iptables/ip6tables reliability and protection logic • Improved backup and restore behavior for network rules • Added safer wait/retry handling for xtables lock situations • Expanded proxyInfo protection to cover more programs and ports • Added a minimal self-healing working folder structure • Improved backend resilience against rule conflicts and network apply failures

ZDT-D is a root module for Android designed for advanced network compatibility, DPI circumvention, DNS handling, and local proxy orchestration. Unlike a classic Android VPN app, ZDT-D does not rely on VpnService as its primary traffic engine. Instead, it uses a root daemon, iptables/ip6tables, UID-based routing, NFQUEUE, and local transparent redirection to selectively pass traffic into different processing pipelines. The project includes: - a local Rust daemon (zdtd) - an Android application for configuration and status control - bundled networking tools for different routing and DPI-bypass scenarios What makes ZDT-D different from a classic VPN A traditional Android VPN usually works through VpnService, creates a virtual TUN interface, and routes traffic through a single VPN pipeline. ZDT-D uses a different model: - works with root privileges - applies rules through iptables / ip6tables - routes traffic by Android app UID - supports NFQUEUE-based packet processing - supports transparent redirect to local services on 127.0.0.1 - can combine multiple engines for different scenarios instead of forcing one global VPN tunnel This makes ZDT-D closer to a root-based transparent traffic manager than to a standard VPN client. Traffic routing model ZDT-D supports more than one traffic handling path. A. NFQUEUE path Used for packet-level processing. Typical logic: - selected Android packages are converted into UIDs - iptables rules are added in mangle - matching traffic is sent to NFQUEUE - userspace processor handles the packets B. Transparent local redirection Used for local service pipelines. Typical logic: - selected Android app UIDs are resolved - iptables rules are attached to OUTPUT - traffic is redirected to local listeners on 127.0.0.1:<port> - local component processes the stream C. DNS handling dnscrypt-proxy can be started before the rest of the pipeline so DNS resolution can be handled in a controlled way. How app selection works ZDT-D does not blindly route all device traffic. It can work with selected applications: 1. package names are collected from user settings 2. package names are resolved into Linux UIDs 3. iptables rules are generated using -m owner --uid-owner 4. only traffic belonging to those apps is redirected or queued This allows more selective routing than a simple "all traffic through one tunnel" design. Runtime protection ZDT-D includes a runtime protector for important service processes. Depending on configuration, it can: - acquire a kernel wake lock - adjust oom_score_adj - work in Off, On, or Auto mode - react differently to screen-on / screen-off states This part is intended to improve service stability during idle or power-managed device states. Privacy ZDT-D does not collect, transmit, sell, share, or use personal data. All configuration, routing, rule management, and runtime control required for the module to work are performed locally on the installed device. The project does not require remote telemetry or analytics for core functionality. If the application connects to external resources, it does so only for actions explicitly requested by the user, such as checking releases or downloading updates from official upstream sources. Safety - Some antivirus products may flag DPI-related tools because they work with low-level network behavior. - ZDT-D is intended for advanced network compatibility, routing control, and research / enthusiast use. - Device compatibility may vary depending on ROM behavior, SELinux handling, kernel options, and root environment. - Some features depend on working iptables/ip6tables support on the device. Notes - IPv6 behavior may differ across devices and firmware builds. - Some functions may depend on the behavior of the root environment and firmware implementation. - For additional usage notes and explanations, see: https://github.com/GAME-OVER-op/ZDT-D/blob/main/INSTRUCTIONS.md The app is available in Russian and English.