A native Android SOCKS5 proxy that forces every outbound socket onto the cellular network — even when Wi‑Fi is the system default. DataProxy runs entirely on the phone as a SOCKS5 server. Any client on the same network — a laptop, a TV box, another phone — points its SOCKS5 settings at phone-ip:1080, and every TCP/UDP packet that leaves the proxy is bound to the cellular Network handle. The listener itself stays on the Wi‑Fi interface, so inbound clients can reach it without any VPN setup, root, or tethering tricks. laptop / TV / phone │ │ SOCKS5 over Wi‑Fi ▼ 📱 DataProxy ─── TCP/UDP pinned to LTE/5G ──▶ internet ▲ │ DNS resolved via cellular's resolver No VPN service is registered, no iptables rules are touched, and no other app on the phone is affected — only the sockets DataProxy explicitly opens are network‑bound to cellular. Features Cellular pinning per socket. Outbound TCP and UDP are bound to the cellular Network via Network.bindSocket() / bindDatagram() — not a process‑wide hijack. Full SOCKS5 surface. RFC 1928 CONNECT and UDP ASSOCIATE; RFC 1929 username/password auth (optional, live‑toggleable). IPv4 / IPv6 / domain address types. Cellular DNS. Hostnames sent as ATYP=domain are resolved through Network.getAllByName() on the cellular handle, so DNS cannot leak to Wi‑Fi or local LAN resolvers. Live network indicator. Header shows the active operator name and the current radio tech (2G / 3G / 4G / 5G) read straight from TelephonyManager; updates as the device hands over between cells. Auto‑pause on data loss. If cellular drops the listener stays bound and the service enters Paused; when data is back the watcher coroutine flips it to Running automatically. Live metrics. Per‑second up/down speed, cumulative traffic counters, and a per‑client device list (deduplicated by IP, ordered by activity). Foreground service. Keeps running with the screen off, with a persistent low‑importance status notification. Anti‑Kill survival hub. A dedicated screen that surfaces the OEM settings — battery optimisation, auto‑launch, background activity, and the Recents lock — that stop aggressive Android skins from killing the proxy, with live status and per‑vendor deep links. The same prompts are folded into the start‑up permissions dialog. Auto‑start on boot. Optional: the proxy relaunches itself after the phone reboots. Auth subscreen. RFC 1929 username/password, toggle without restarting the proxy. Light / dark / system theming. Per‑theme palette in a Compose composition local; persisted across launches. Material 3 single‑activity UI. One screen, manual tab nav, no scroll on standard phone displays.