Android

The Android app has the same WaterWall as the iPhone app: the same screens, options, messages and server files. The other guides on this site apply to both. This page lists only what differs on Android, and what we tested there.

Where the Android app stands The app is not in a store yet, and you build the test APK yourself. It has the same nine protocols as the iPhone and iPad app.
Where this page comes from

The differences were read from the app's source code at commit e44cf11d. The results are from our tests on 10 November 2026, against the same production server as the iPhone scenarios.

What is the same

What differs

TopiciPhone and iPadAndroid
InstallingTestFlightA test APK that you build; see Installation
SystemiOS or iPadOS 15.0 or laterAndroid 8.0 or later, 64-bit ARM only
PermissioniOS asks to add a VPN configurationAndroid shows a Connection request once, until the app is removed or another VPN app takes over
While connectedThe VPN icon in the status barThe key icon in the status bar. The app does not ask for permission to show notifications, so from Android 13 on it shows none
Ping while connectedAn HTTPS request to gstatic.com, the answer 204An HTTP request through the tunnel to 1.1.1.1 on port 80, any HTTP answer; see How ping is measured
SecretsiOS KeychainEncrypted with a key held by the Android Keystore. The profile file holds no secret, and profiles stay out of device backups
Choosing a fileThe Files appThe system's file picker
On SleepThe phone sleeping and wakingThe screen going off and coming on
IPv6The tunnel carries IPv4 onlyThe same. While the VPN is up, Android gives apps no IPv6 route, so IPv6 traffic does not leave outside the tunnel; a connection to an IPv6 address fails with No route to host
Traffic to the server's own addressWith Raw IPv4 input or WireGuard it goes outside the tunnelIt goes through the tunnel
The app's logNone for a WaterWall connection in TestFlight and App Store builds; Debug builds made for testing keep the app's own linesThe app's own lines and WaterWall's: errors at Normal, more at Expert and Debug. It keeps the last 512 KB when it passes 2 MB
Always-on VPNNot usedTurn it on for the app in Android's VPN settings. Android then starts the app's VPN at once and after every boot, and it connects the profile you used last
After a reconnectiOS applies the VPN settings againAndroid gets a new VPN network, so its DNS cache starts empty and apps see the change, as with any change of network

The Connection request

Android's Connection request dialog for SRP VPN Connect with Cancel and OK buttons
Android asks once. Tap OK.

What we tested

PartVersion
AppSRP VPN Connect 1.2.0, debug APK of commit e44cf11d, with WaterWall 1.5.42, the same app commit as TestFlight build 41, and the signed release APK 1.2.0 (9) of the same commit
PhoneSamsung Galaxy A55 (SM-A556E) with Android 17 (API level 37), on our office Wi-Fi and its own cellular connection
ServerOur production waterwall.service, running the official WaterWall 1.5.42 release as Installation installs it, with the same files as in the iPhone production scenarios, its Let's Encrypt certificate and TLS Server Verification on
TrafficA small test app on the phone, inside the VPN, made two downloads and two uploads at once to a speed test server on the server. Each upload's SHA-256 was compared with what the server received, and the server's log showed the requests arriving through the tunnel

45 of 45 chains and 46 of 46 checks passed.

Every chain of the production server

Each link opens the chain's scenario page, with its server file and the app settings, which are the same on both systems. The times show that traffic moved, and are not a benchmark.

ChainResultTo ConnectedTwo downloads and two uploads at once, 16 MiB each
Raw IPv4 + HTTP/1.1 + TLS (additional-rawip-http1-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s10.6 s
Raw IPv4 + KCP (additional-rawip-kcp.json)VERIFIED — TESTED SUCCESSFULLY7.7 s18.3 s
Raw IPv4 (no outer layer) (additional-rawip-none.json)VERIFIED — TESTED SUCCESSFULLY7.7 s10.6 s
Raw IPv4 + Packet Encryption (additional-rawip-packet.json)VERIFIED — TESTED SUCCESSFULLY7.7 s11.8 s
VLESS + HTTP/1.1 + TLS (additional-vless-http1-tls.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.5 s
VLESS + HTTP/2 + TLS (additional-vless-http2-tls.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.4 s
VLESS + KCP (additional-vless-kcp.json)VERIFIED — TESTED SUCCESSFULLY7.7 s10.7 s
VLESS + MUX + QUIC Stream (additional-vless-mux-quic-stream.json)VERIFIED — TESTED SUCCESSFULLY7.7 s9.6 s
VLESS (no outer layer) (additional-vless-none.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.5 s
VLESS + Obfuscator + HTTP/1.1 + TLS (additional-vless-obf-http1-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VLESS + Obfuscator + KCP (additional-vless-obf-kcp.json)VERIFIED — TESTED SUCCESSFULLY7.7 s10.6 s
VLESS + Obfuscator + TLS (additional-vless-obf-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.6 s
VLESS + QUIC Stream (additional-vless-quic-stream.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VLESS + WebSocket (additional-vless-ws1-none.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.4 s
VLESS + WebSocket + TLS (additional-vless-ws1-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VMess + AEAD (additional-vmess-aead.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VMess + HTTP/2 + TLS (additional-vmess-http2-tls.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.4 s
VMess + KCP (additional-vmess-kcp.json)VERIFIED — TESTED SUCCESSFULLY7.7 s10.6 s
VMess + MUX + QUIC Stream (additional-vmess-mux-quic-stream.json)VERIFIED — TESTED SUCCESSFULLY7.8 s9.5 s
VMess + MUX + TLS (additional-vmess-mux-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.4 s
VMess + Obfuscator + HTTP/1.1 + TLS (additional-vmess-obf-http1-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.4 s
VMess + QUIC Stream (additional-vmess-quic-stream.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.4 s
VMess + Reality (additional-vmess-reality.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.5 s
VMess + TLS (additional-vmess-tls.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.5 s
VMess + WebSocket + TLS (additional-vmess-ws1-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
Raw IPv4 + AEAD (rawip-aead.json)VERIFIED — TESTED SUCCESSFULLY7.7 s11.7 s
Raw IPv4 + QUIC Datagram (rawip-quic.json)VERIFIED — TESTED SUCCESSFULLY7.7 s17.4 s
Raw IPv4 + Reality (rawip-reality.json)VERIFIED — TESTED SUCCESSFULLY7.7 s10.6 s
Raw IPv4 + TLS (rawip-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s11.7 s
Trojan + AEAD (trojan-aead.json)VERIFIED — TESTED SUCCESSFULLY7.8 s8.5 s
Trojan + MUX + AEAD (trojan-mux-aead.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.6 s
Trojan + MUX + Reality (trojan-mux-reality.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
Trojan + MUX + TLS (trojan-mux-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.4 s
Trojan + QUIC Datagram (trojan-quic.json)VERIFIED — TESTED SUCCESSFULLY7.8 s9.6 s
Trojan + Reality (trojan-reality.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
Trojan + TLS (trojan-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.4 s
VLESS + AEAD (vless-aead.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VLESS + MUX + AEAD (vless-mux-aead.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.6 s
VLESS + MUX + Reality (vless-mux-reality.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VLESS + MUX + TLS (vless-mux-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VLESS + QUIC Datagram (vless-quic.json)VERIFIED — TESTED SUCCESSFULLY7.7 s9.5 s
VLESS + Reality (vless-reality.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.6 s
VLESS + Reality (vless-reality.json, SNI typed)VERIFIED — TESTED SUCCESSFULLY7.7 s8.5 s
VLESS + TLS (vless-tls.json)VERIFIED — TESTED SUCCESSFULLY7.7 s8.6 s
WireGuard mode (wireguard.json)VERIFIED — TESTED SUCCESSFULLY7.7 s9.5 s

Everything around the connection

Each of these ran on the phone. The network check moved between its real Wi-Fi and cellular connections, and the sleep checks turned its screen off.

What we checkedResult
Nothing listens at the server's port: the start-up check fails and the app says why, with Auto Reconnect off. WaterWall TCP probe failed after fifteen attemptsVERIFIED — TESTED SUCCESSFULLY
Retry Times 2 with no server: three tries, then the app gives up with the count in its message. Could not reconnect after 2 attempts. (WaterWall TCP probe failed after fifteen attempts)VERIFIED — TESTED SUCCESSFULLY
The power button while connecting stops it, and the next connect still works.VERIFIED — TESTED SUCCESSFULLY
With Auto Reconnect off, losing the server ends the VPN after the health check. WaterWall TCP health probe failedVERIFIED — TESTED SUCCESSFULLY
With Auto Reconnect on, the app keeps trying while the server is gone and comes back without any tap.VERIFIED — TESTED SUCCESSFULLY
Retry Times counts failures in a row: a good connection in between starts the count again.VERIFIED — TESTED SUCCESSFULLY
The selected profile's port is dead, a sibling with the same Server works: the next attempt uses it.VERIFIED — TESTED SUCCESSFULLY
Wi-Fi off moves the connection to cellular, Wi-Fi on moves it back, and traffic works on both.VERIFIED — TESTED SUCCESSFULLY
With Switch to Wi-Fi off, the app does not act on the change itself.VERIFIED — TESTED SUCCESSFULLY
On Sleep Stay: the screen goes off, the connection stays.VERIFIED — TESTED SUCCESSFULLY
On Sleep Pause: closes at screen off and always reconnects at wake, even with Auto Reconnect off.VERIFIED — TESTED SUCCESSFULLY
On Sleep Off with Auto Reconnect: closes at screen off, reconnects at wake.VERIFIED — TESTED SUCCESSFULLY
On Sleep Off without Auto Reconnect: the VPN ends at wake and says why in the log.VERIFIED — TESTED SUCCESSFULLY
A self-signed certificate for the right name: the check refuses it. With the check off the same handshake finishes.VERIFIED — TESTED SUCCESSFULLY
GeoIP in the profile with no database installed: the app refuses to connect and says what to do. GeoIP is enabled but its database is unavailable: A valid GeoIP country database is required.VERIFIED — TESTED SUCCESSFULLY
The GeoIP Routing switch installs the bundled database and selects Iran, as on iOS.VERIFIED — TESTED SUCCESSFULLY
The test server is in Turkey. With TR selected its downloads go direct: it sees this network's own address.VERIFIED — TESTED SUCCESSFULLY
With another country selected the same download goes through the server.VERIFIED — TESTED SUCCESSFULLY
Upload MMDB: a good database replaces the old one; a file that is not one is refused and the old one stays.VERIFIED — TESTED SUCCESSFULLY
Download & Replace: plain http is refused; an HTTPS link is downloaded, checked and installed.VERIFIED — TESTED SUCCESSFULLY
Import Config (.conf) through the file picker fills Server and Port, stores the keys and connects.VERIFIED — TESTED SUCCESSFULLY
Manual Configuration: the keys typed in the fields build the same connection, and Gen makes a pair with its public key.VERIFIED — TESTED SUCCESSFULLY
Direct needs no server: traffic leaves through WaterWall straight to the internet.VERIFIED — TESTED SUCCESSFULLY
After a reconnect the new runtime never gave out the placeholders the system cached, so the cache must not outlive it.VERIFIED — TESTED SUCCESSFULLY
AllowedIPs with host bits set and a search domain on the DNS line, both valid in wg-quick files, connect instead of being refused by Android.VERIFIED — TESTED SUCCESSFULLY
Android asks a process for a stack dump with SIGQUIT, as when an app does not respond; the tunnel must not notice.VERIFIED — TESTED SUCCESSFULLY
The VPN counts as metered only when the network under it does, so apps do not hold back on Wi-Fi.VERIFIED — TESTED SUCCESSFULLY
The loss rule's counters work on a TCP carrier: the app writes a summary of the last minute.VERIFIED — TESTED SUCCESSFULLY
Auto and Manual: connection and transfers work, with the settings in the chain.VERIFIED — TESTED SUCCESSFULLY
The DNS RESOLVER rows: Through the VPN starts with two public servers, Addresses and DNS Servers are saved, a name is refused, Off takes the resolver out.VERIFIED — TESTED SUCCESSFULLY
Native: WaterWall looks names up with the network's DNS, so the probe hears nothing; the download goes through the server.VERIFIED — TESTED SUCCESSFULLY
Direct: the probe is asked for the test server's name from the phone's network, outside the VPN; the download goes through the server.VERIFIED — TESTED SUCCESSFULLY
Through the VPN: the probe is asked for the test server's name by the server itself; the download goes through the server.VERIFIED — TESTED SUCCESSFULLY
GeoIP with TR and the resolver through the VPN: the name is looked up through the server, then the download goes direct.VERIFIED — TESTED SUCCESSFULLY
On: a name gets a placeholder from 100.64.0.0/10. Off: the real address, and the probe uses the real DNS.VERIFIED — TESTED SUCCESSFULLY
A private address: reached straight from the phone with the option on, through the server with it off.VERIFIED — TESTED SUCCESSFULLY
Pull to ping, swipe to ping, the KCP message, the result kept after closing the app.VERIFIED — TESTED SUCCESSFULLY
A second swipe ping leaves the first row with no result, and so does disconnecting during the test through the tunnel.VERIFIED — TESTED SUCCESSFULLY
A long swipe runs the action at once; an open row closes with the next touch, which does nothing else.VERIFIED — TESTED SUCCESSFULLY
The editor keeps what was typed through rotation and dark mode, keeps its scroll position across a sub-screen, and a touch outside closes the keyboard.VERIFIED — TESTED SUCCESSFULLY
After connecting, the row shows the delay through the tunnel; swiping that row measures it again.VERIFIED — TESTED SUCCESSFULLY
The status text opens the log; levels change what it holds; Share opens the sheet; Clear empties it.VERIFIED — TESTED SUCCESSFULLY
A profile made through the screens: its checks, where its secrets go, and that Delete removes them.VERIFIED — TESTED SUCCESSFULLY
While connected the system shows the VPN key and the app's notification.VERIFIED — TESTED SUCCESSFULLY
The tunnel carries IPv4 only. Android keeps IPv6 from leaving outside it while the VPN is up.VERIFIED — TESTED SUCCESSFULLY
The same process connects again: the runtime starts a second and a third time.VERIFIED — TESTED SUCCESSFULLY

The release APK

The signed release APK 1.2.0 (9), the one we hand out, made each profile through the app's screens, as a person would, and connected to 15 of these chains with the same transfers. 15 of 15 passed.

ChainResult
Raw IPv4 + KCP (additional-rawip-kcp.json)VERIFIED — TESTED SUCCESSFULLY
VLESS + KCP (additional-vless-kcp.json)VERIFIED — TESTED SUCCESSFULLY
VLESS (no outer layer) (additional-vless-none.json)VERIFIED — TESTED SUCCESSFULLY
VLESS + Obfuscator + TLS (additional-vless-obf-tls.json)VERIFIED — TESTED SUCCESSFULLY
VLESS + WebSocket + TLS (additional-vless-ws1-tls.json)VERIFIED — TESTED SUCCESSFULLY
VMess + HTTP/2 + TLS (additional-vmess-http2-tls.json)VERIFIED — TESTED SUCCESSFULLY
VMess + MUX + QUIC Stream (additional-vmess-mux-quic-stream.json)VERIFIED — TESTED SUCCESSFULLY
Raw IPv4 + Reality (rawip-reality.json)VERIFIED — TESTED SUCCESSFULLY
Raw IPv4 + TLS (rawip-tls.json)VERIFIED — TESTED SUCCESSFULLY
Trojan + AEAD (trojan-aead.json)VERIFIED — TESTED SUCCESSFULLY
Trojan + MUX + TLS (trojan-mux-tls.json)VERIFIED — TESTED SUCCESSFULLY
VLESS + QUIC Datagram (vless-quic.json)VERIFIED — TESTED SUCCESSFULLY
VLESS + Reality (vless-reality.json)VERIFIED — TESTED SUCCESSFULLY
VLESS + TLS (vless-tls.json)VERIFIED — TESTED SUCCESSFULLY
WireGuard mode (wireguard.json)VERIFIED — TESTED SUCCESSFULLY

Not tested on Android yet