Skip to content

Documentation v1.3.1

Create a Rootless Android Mobile Proxy

Use an Android phone as an authenticated HTTP or SOCKS5 proxy exit node without root or inbound router port forwarding.

Use only with authorization. Protect the endpoint and device AuthToken, monitor cellular data usage, and follow the mobile carrier’s and destination service’s terms.

  1. Install the official Localtonet app from Google Play.
  2. Sign in to Localtonet and obtain the device-specific AuthToken from the dashboard. Do not publish it, send it through an unsecured channel, or include it in screenshots.
  3. Open the Android app, authenticate with the device token, and wait for the phone to appear as connected in the dashboard.
  4. Open the Proxy Server page. Select the connected phone’s AuthToken and an available relay server or region.
  5. Select HTTP or SOCKS5. When available, configure a unique username and password and share them only with authorized users.
  6. Create the proxy, then press Start. Copy the assigned public host, port, and credentials after it is running.
  7. Enter those values in an authorized client that supports the selected protocol. Keep the phone and app connected while using the proxy.

Rotate the mobile connection

  1. Follow the current app prompts for airplane-mode automation. On supported non-root devices, Localtonet may need to be selected as the default assistant.
  2. If the dashboard provides rotation intervals or a reset link, use them only after confirming that airplane-mode control works on the phone.
  3. Run resets between test jobs because they interrupt active network sessions and may temporarily affect calls, messages, hotspot clients, or other applications.
  4. Verify the observed exit IP after every reset. Reconnection does not guarantee a new address; the carrier may assign the same IP again.

Verify and secure the proxy

  • Confirm the phone is using cellular data. If Wi-Fi is active, traffic may exit through the Wi-Fi network instead.
  • Stopping the proxy or disconnecting the phone makes the endpoint unavailable.
  • Do not expose the endpoint, credentials, or AuthToken in public screenshots, issue trackers, or untrusted client-side code.
  • Stop or delete the proxy when the session is complete.
support