Android

Android lets you set a per-Wi-Fi proxy. The catch: native authentication for HTTP proxies is limited — modern Android prompts for credentials in-app rather than at OS level, so apps that don't honor the system proxy auth dialog will fail.

Per-Wi-Fi proxy (Android 10+)

1. Settings → Wi-Fi → {your network} → Modify network → Advanced options.
2. Proxy: Manual.
3. Hostname: gate.helodata.io (or ISP IP).
4. Port: 7777.
5. Bypass: localhost,127.0.0.1.
6. Save.

[screenshot: Android Wi-Fi proxy form]

Android does not have a field for proxy auth — credentials must be entered when the first authenticated app prompts.

When the OS-level proxy isn't enough

Apps that ship their own networking stack (e.g. many games, some social apps) ignore the Wi-Fi proxy entirely. For those, use either:

• Drony (a free VPN-style app that intercepts traffic and routes via proxy) — works for non-rooted devices and supports auth
• NetGuard or Tasker + AutoTools for app-level rules
• Rooted device + ProxyDroid for true global proxy with auth

These tools route all device traffic through helodata; configure them with:

Field	Value
Type	HTTP or SOCKS5
Host	gate.helodata.io (or ISP IP)
Port	7777
Username	full proxy username (gateway) or helo_s1a2b3c4d5e (ISP)
Password	sub-user password

ADB for testing

adb shell settings put global http_proxy "gate.helodata.io:7777"

To clear:

adb shell settings put global http_proxy :0

Verify

Open the device browser to https://ipv4.icanhazip.com.

Common pitfalls

• App ignoring system proxy — common with apps that pin SSL or roll their own HTTP stack. Use Drony or rooted tools.
• HTTPS targets failing in Chrome on Android — typically a captive portal or DNS issue. Verify with chrome://net-internals/#proxy.
• Per-network setting — moving to mobile data drops the proxy. Re-configure per Wi-Fi network.