L×Box

ArShinTech · Tools

Verified safeOpen sourceExclusive

Download APK

—

No reviews reviews

downloads

7.0

android

AI summary

VPN client powered by a sing-box fork with AmneziaWG 2.0 and native XHTTP. Supports multiple proxy protocols, smart routing, load balancing, and per-app traffic profiling. Note: requests broad permissions including location, camera, microphone, and access to all installed apps.

Generated by AI. May contain inaccuracies.

Screenshots

About this app

Android VPN client powered by sing-box-lx — a sing-box fork with AmneziaWG 2.0 and native XHTTP. Multi-subscription, smart routing, built-in speed test.

Features • Servers & Subscriptions — manage proxy sources in one place • Get WARP — one-tap Cloudflare WARP, keys generated on-device • Subscription auto-update — 4 triggers, hard gates against spam • Home Screen — connect and manage nodes • Quick Connect — toggle VPN without opening the app (v1.5.0) • Routing — unified rule model (v1.4.0) • Load balancing — spread traffic across a pool of servers (v2.7.0) • Wi-Fi-aware routing — different rules on different networks (v1.7.3) • Detour Servers — chain proxies for extra privacy • DNS Settings — full control over name resolution • DPI Bypass — bypass censorship • Haptic Feedback — vibro on VPN events • Speed Test — measure your connection • Statistics & Connections — see what's happening • Per-app traffic profiler — trace any app's network in real time (v1.7.0) • On-device core profiling (pprof) — catch CPU spin & memory leaks (v2.7.0) • VPN Settings — tune the engine • Config Editor — for power users • App Settings — personalize

Supported Protocols: + VLESS + VMess + Trojan + Shadowsocks + Hysteria2 + TUIC v5 + NaïveProxy + SSH + SOCKS + WireGuard / AmneziaWG + MASQUE (Cloudflare WARP) + XHTTP

vpn network tool privacy open source proxy client sing-box

What's new

v2.20.3Aug 5, 2026

Nothing changes for you — the app behaves exactly as v2.20.1 and v2.20.2 do. Two native libraries no longer carry a build id that changed on every build, which is what kept the F-Droid build from matching ours byte for byte.
🔧 Build — the linker no longer stamps a build id Every .so normally carries a .note.gnu.build-id section: twenty bytes that identify the build. The NDK asks for the sha1 variant, which sounds content-derived and therefore stable.
It is not. LLD hashes the input to the link step, not the resulting file — object files, debug data, things that never reach the .so. Two builds of the same code in different environments get different ids while producing identical libraries.
Measured on libdartjni.so, comparing the F-Droid build of v2.20.1 with ours: the two files differ by exactly twenty bytes, at offset 0x2e0. That is the build id itself. Section tables, .text, .rodata — everything else is identical.
An id that changes without the code changing is no use for debugging either: it cannot lead you to the right symbols. So the Android build now passes --build-id=none to every subproject that compiles native code through CMake, dropping the section entirely — the same thing other ZXing-based apps in the F-Droid catalogue do.
The flag lives in android/build.gradle.kts rather than in the F-Droid recipe, because the catalogue builds this same project: one source covers both sides.
🧪 Tests Behaviour did not change, so no new tests. flutter analyze and the existing suite pass; llvm-readelf -n confirms the section is gone from both libdartjni.so and libflutter_zxing.so