Same Wi-Fi
- Phone and client join the same Wi-Fi
- Client uses the phone LAN IP and proxy port
- Phone creates target connections over cellular
- Wi-Fi AP isolation may block access
Android cellular egress proxy
Route explicitly configured proxy traffic through your Android phone’s cellular network
Run local SOCKS5 and HTTP/HTTPS proxies on a non-rooted Android phone, then route supported TCP connections through its cellular data network.
Not a VPN. Manual proxy configuration is required.
Official Google Play distribution only—no direct APK or third-party mirrors.
CellRouteCellular ready
Local proxy192.168.x.x : 1080
ClientSOCKS5 / HTTPCellular egress
TCPOnly
DNSCellular
TLSUntouched
01 / Data flow
One explicit route, connection by connection
CellRoute accepts only traffic sent to its proxy listener, resolves destinations on the cellular network, and creates a separately bound target Socket for each TCP connection.
- 01ClientProxy-aware application
- 02Manual proxySOCKS5 or HTTP
- 03Phone ingressWi-Fi / hotspot address
- 04CellRouteLocal TCP proxy
- 05Cellular DNSResolve and check target
- 06Target SocketBound to cellular Network
- 07InternetTCP destination
Choose the ingress that fits your setup
Android hotspot
- User enables hotspot in system settings
- Client joins and uses the gateway address
- CellRoute listens on the hotspot LAN interface
- OEM isolation may block local access
Two familiar proxy protocols
CONNECT
IPv4, IPv6, domain names and username/password authentication. TCP only; no UDP ASSOCIATE.
Proxy + CONNECT
Proxy HTTP requests and open TCP tunnels for HTTPS. TLS is not decrypted.
02 / Network API
Cellular DNS and per-Socket binding
Target names are resolved through the selected cellular Network. Each outbound target Socket is created from that Network’s socket factory—without changing Android’s global route or binding the whole app process.
Learn how it works →DNScellularNetwork.getAllByName(host)
SocketcellularNetwork.socketFactory
Validate the resolved destination, then create the TCP connection.
Safe defaults for a local proxy
Random credentials and Android Keystore-backed encrypted storage
Client and destination controls, including checks after DNS resolution
Restricted private, loopback, link-local, multicast, CGNAT and IPv6 ULA destinations by default
Redacted logs with no bodies, passwords, cookies, authentication headers or TLS plaintext
Useful by default, deeper controls with Premium
The free edition includes authentication, core safety controls, basic status, traffic counters and up to five connections. Premium adds simultaneous protocols, configurable limits, detailed monitoring, advanced ACLs, profiles and timeouts.
Full edition comparison| Feature | Free | Premium |
|---|---|---|
| SOCKS5 / HTTP | Choose one | Run both |
| Custom ports | Included | Included |
| Username/password authentication | Included | Included |
| Maximum connections | 5 | Configurable up to 100 |
| Per-IP limit | Fixed safe value | Configurable |
| Live speed and traffic totals | Included | Included |
| Connection details | — | Included |
| 60-second speed chart | — | Included |
| Traffic history | — | Included |
| Redacted logs | — | Included |
| Advanced client and destination ACLs | — | Included |
| Advanced timeouts | — | Included |
| Configuration profiles | — | Up to 10 |
| Ads | None | None |
Compatibility is detected, not assumed
Android 8.0+ is supported, but simultaneous Wi-Fi or hotspot and cellular behavior depends on the device, OEM, carrier and network. Hotspot client isolation remains Unknown until it can be tested from a real client.
Check compatibility →Designed for local processing
Proxy connections are handled on the phone. CellRoute does not decrypt HTTPS, install a CA certificate or record communication content. The website ships without ads, behavioral analytics or non-essential cookies by default.
Read the Privacy Policy →Questions worth answering before setup
Set accurate expectations about VPN boundaries, hotspot limitations, purchases and reconnection.
Read all 26 answers →Is CellRoute a VPN?
No. CellRoute is a local SOCKS5 and HTTP proxy. It does not use Android VpnService, create a virtual network interface, change the system route table or transparently capture device traffic.
Does CellRoute route all traffic from my client device?
No. Only TCP traffic from applications that follow the manually configured SOCKS5 or HTTP proxy is sent through CellRoute. Applications that ignore the proxy, plus UDP, QUIC and other bypass traffic, continue using the client’s own network.
Does CellRoute require Root?
No. It does not require Root, ADB, Shizuku, Magisk, hidden Android APIs or VpnService.
Does it automatically enable the Android hotspot?
No. You must turn the hotspot on or off in Android system settings. CellRoute can provide a shortcut to those settings but does not control hotspot state.
Can it work when my phone and client use the same Wi-Fi?
Yes, when the Wi-Fi allows clients to reach one another and the phone can keep cellular data available. Configure the client to use the phone’s Wi-Fi LAN address and CellRoute port.
From the CellRoute blog
All articles →Jul 10, 2026
Understanding TCP, UDP and QUIC limitations
Learn why CellRoute supports TCP proxy connections while UDP, QUIC and SOCKS5 UDP ASSOCIATE stay outside its design.
Jul 8, 2026
Troubleshooting Android hotspot client isolation
Diagnose cases where a hotspot client can reach the internet but cannot reach CellRoute's local proxy port.
Jul 5, 2026
Why a proxy app must bind target sockets, not client sockets
Understand Android ingress and egress sockets, cellular Network socket factories and why process-wide binding is unnecessary.
Turn an Android phone into an explicit cellular TCP proxy
Check compatibility first, then follow the setup guide. Do not expose the proxy to unknown users on the public internet.
Official Google Play distribution only—no direct APK or third-party mirrors.