What CellRoute is—and what it is not

CellRoute turns a compatible, non-rooted Android phone into a local SOCKS5 and HTTP proxy. A client on the same Wi-Fi—or connected to the phone’s manually enabled hotspot—connects to the phone’s local address and proxy port. CellRoute then creates a separate target Socket for each accepted TCP request and sends that Socket through Android’s available cellular Network.

That compact description contains several important boundaries.

It is an explicit proxy

The client must be configured with the phone address, port and proxy credentials. Only applications that honor this setting participate. An application that ignores the operating system’s proxy, chooses UDP, or uses QUIC can continue to communicate through the client’s own network.

CellRoute does not alter the Android routing table, set a global proxy, provide transparent NAT or capture packets. It does not automatically configure other devices.

It is not a VPN

CellRoute does not use VpnService, create a tunnel interface or claim full-device traffic protection. It also does not require Root, ADB, Shizuku, Magisk or hidden Android APIs.

The distinction matters during troubleshooting. A successful browser test does not prove that every app on the client is proxied. Confirm the proxy behavior of each application you depend on.

It is TCP-only

SOCKS5 CONNECT, HTTP requests and HTTPS CONNECT tunnels are TCP features. SOCKS5 UDP ASSOCIATE, generic UDP forwarding and QUIC forwarding are not supported. HTTPS remains encrypted end to end; CellRoute does not install a CA or decrypt TLS.

Finally, compatibility depends on the phone, OEM, carrier, hotspot implementation and local network. CellRoute can expose accurate status, but it cannot override hotspot client isolation or promise seamless migration of existing TCP connections when the cellular Network changes.