Proxies — experimental

Status

SOCKS5 belongs to experimental Preview, not the DNS-only Release build. This is a description of boundaries, not a ready public VPN setup recipe. No public APK has been published.

What was tested

Specific physical scenarios on a Samsung device running Android 13, with selected participants and Wi-Fi, transferred a complete HTTPS response through an external Happ SOCKS5 provider, including checksum, end-of-response and connection closure. A separate unavailable-proxy test had no hidden Direct fallback; recovery was tested using a new session.

Those results apply to a particular test build and scenario. They do not verify every current build, app, network or automatic recovery of every connection.

Limitations

• The experimental path is IPv4/TCP for selected apps.
• General UDP/QUIC, IPv6 and fragmented-packet support is not claimed.
• Tests used SOCKS5 CONNECT without username/password; UDP ASSOCIATE is not claimed.
• Fresh YouTube media delivery through the proxy remains unconfirmed.
• DNS uses a separate DoH path; a DNS result does not prove the TCP route.

In testing, Happ was an external Proxy Only provider outside the NetScope scope. This does not permit two simultaneous VPN services. Detailed proxy setup is deferred until the user scenario and APK are approved. See VPN conflicts.