When choosing an Android VPN, check whether it stays active in the background, reconnects after network changes, and handles split tunneling as expected. Don’t judge an Android VPN test by connection speed alone: if web pages load during the day but messages stop arriving when the screen is locked, check the client and system settings before switching servers.
This guide offers checks you can reproduce on your own device, not unverified speed rankings. Menu names for background activity, battery, and auto-start vary by manufacturer. Follow the setting descriptions below, then verify the results in the app itself.
Choosing a client: Start with the connection mode
Android’s VpnService lets an app create a virtual network interface and route selected system traffic through the client. A VPN icon in the status bar only indicates that a connection is active; it doesn’t prove that every app or domain is routed through the remote server. The client may still send some connections directly according to its rules.
An HTTP proxy in Wi-Fi settings works differently: it relies on apps honoring the system proxy settings and doesn’t take over the entire device. If a browser works but a game doesn’t, first check which mode you’re using, then investigate protocol support, rules, and the remote server.
| Method | How traffic reaches the client | Best for | What to check |
|---|---|---|---|
| Wi-Fi HTTP proxy | Connections are sent by apps that honor the proxy settings | Testing apps with explicit HTTP proxy support | Other apps may ignore the settings |
| VPN mode with rule-based routing | The system sends traffic to a virtual interface, where the client applies its rules | Everyday browsing alongside apps used in mainland China | Rule order, DNS, and default route |
| VPN mode with an app list | The allowlist or exclude list determines which apps use the interface | Routing only selected apps through international servers | List behavior, associated apps, and reconnection requirements |
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different proxy protocols or solutions that a client may support. Their names alone don’t indicate how reliably an Android app will stay active in the background. Support depends on the client’s core and version, and the subscription format must be compatible. First confirm what the service offers and what the client can parse; then check the connection settings.
Choosing a client: For everyday use, look for clear routing documentation, app lists, and diagnostic logs. If you just want to connect and go, start with the service’s Android app. Protocol names and feature counts are no substitute for testing with the screen locked and after network changes.
Keeping a VPN active in the background: Check battery restrictions first
Android’s Doze mode, app standby, and manufacturer-specific background management can affect network activity, scheduled tasks, and process lifetime. Clients that use a foreground service usually show an ongoing notification, but that doesn’t mean all battery restrictions are lifted. Likewise, a missing notification doesn’t prove the connection has stopped.
Start by noting what happens: does the client process disappear after the screen locks, or does it stay running while the target app times out? If the process disappears, check background restrictions first. If it stays running, also check network changes, DNS, the remote connection, and the target app. The fact that reopening the client restores service doesn’t identify the cause on its own.
- Open the client’s app info. Check battery settings and change strict restrictions to allow background activity, or select the equivalent “Unrestricted” option. This may increase battery use, so adjust it only for clients that need a persistent connection.
- Check manufacturer-specific controls. If your system has separate auto-start, background activity, or sleeping app settings, make sure the client isn’t being put to sleep. Locking the app in the recent apps screen can help, but it doesn’t replace battery settings.
- Check data and notification permissions. If Data Saver is enabled, allow the client to use background data where supported. Keep connection status notifications on so you can tell if the service has stopped.
- Test recovery after locking the screen. Confirm the connection works, lock the screen, then return to the same app and note whether you need to reconnect manually. Keep the server and rules unchanged to verify whether the battery setting helped.
Android’s “Always-on VPN” setting can help keep a selected VPN enabled, provided the client supports it. It doesn’t guarantee that the app will never be stopped. “Block connections without VPN” blocks traffic that bypasses the interface. Before enabling it, understand what happens to connectivity if the VPN drops, and test whether local services and excluded apps are affected.
Split tunneling: App lists and routing rules work at different levels
Split tunneling first determines which apps send traffic through the VPN interface. Routing rules then decide whether connections reaching the client are proxied, sent directly, or blocked. Adding a browser to an allowlist doesn’t mean every browser request goes through the remote server; domain or address rules may still send some traffic directly.
An allowlist usually means “only selected apps use the VPN,” while an exclude list usually means “selected apps bypass the VPN.” These behaviors are opposites, so check the client’s own description. Some clients need to rebuild the VPN interface after you change the list. Existing long-lived connections in the tested app may also need to be closed and reopened.
- ✅ Check whether the mode means “proxy only selected apps” or “bypass selected apps”; don’t rely on checkmarks alone.
- ✅ Reconnect after changing the app list, then reopen the target app to avoid interference from existing connections.
- ✅ Check whether sign-in opens an external browser or another app; linked apps may not be included in the same list.
- ✅ Check rule-match logs to confirm the route used by the target connection, not just the client’s main toggle.
- ❌ Don’t change the app list, DNS, and server at the same time; changing several things makes it harder to find the cause.
Apps with the same name in personal and work profiles may run in separate environments. An IP check in a regular browser only reflects that browser’s request at that moment; it can’t confirm that other apps are routed through the VPN. For apps without a built-in test page, check the client logs for the app, destination address, and matching rule. The available details depend on the client.
DNS and network changes: A connection icon doesn’t guarantee access
DNS determines how domain names are resolved, while connection rules determine how traffic is routed afterward. They need to work together. Android Private DNS, a browser’s secure DNS, and a client’s DNS settings may all be active at once. Which path a request takes depends on the system version, app implementation, and routing configuration; enabling one setting doesn’t automatically eliminate every risk of DNS leaks.
A DNS leak occurs when DNS requests don’t use the intended route and are exposed to an unintended resolver. Start by checking the DNS settings recommended by your client, then test the browser and target app separately. A website-based test only provides a clue about that particular test; it can’t show how every app on the device behaves.
When you switch from Wi-Fi to mobile data, the underlying network and IP address may change, invalidating existing connections. If the client doesn’t reconnect promptly, the VPN icon may remain visible even though pages won’t load. Try reconnecting in the client first, then check whether the target app is holding on to an old session. Don’t assume every failed reconnect is caused by your account or server quality.
Android generally doesn’t let regular apps create multiple VpnService-based connections at the same time. Local ad blockers, firewalls, and other network tools may also use this interface. If your original connection disappears after enabling another tool, check for an interface conflict before repeatedly reinstalling the client.
Testing method: Compare settings, not speed rankings
For a reproducible comparison, keep the target app, server region, and local network as consistent as possible, and change only one setting per round. This guide doesn’t include measurements for specific devices. Use the template below to record what you actually observe; don’t treat examples as test results.
| Test | Action | What to observe | Check first if it fails |
|---|---|---|---|
| Recovery after screen lock | Connect, lock the screen, then reopen the same app | Whether the process is still running and requests resume | Battery restrictions and background permissions |
| Network changes | Switch between Wi-Fi and mobile data | Whether it reconnects automatically and old connections are invalidated | Network permissions and reconnection logs |
| App list | Open selected and unselected apps separately | Whether behavior matches the allowlist or exclude list | List mode and rule order |
| DNS routing | Check DNS behavior without changing other settings | Whether the resolver and rule matches behave as expected | Private DNS, app-level DNS, and client settings |
Compare connection type and background reliability separately. Direct, relay, and IEPL dedicated connections describe different network paths or transport methods; they don’t determine how Android manages a process. Even with a dedicated connection, a terminated process will drop the VPN. A server label alone can’t guarantee access to a particular service.
How to narrow down the issue: If it fails after locking the screen, check background settings first. If it fails after switching networks, check reconnection. If only one app fails, check the app list and rules. Pinpointing the layer at fault is more effective than repeatedly switching clients.
Importing subscriptions and using V9VPN
Create a V9VPN account with a username and password—no email address required. Sign in to get the Android client and subscription. Download the client from a valid link in the dashboard; avoid installers from unknown search results. Whether a third-party client can import your subscription depends on the format provided in the dashboard and the client’s supported formats.
Subscription links may contain account credentials, so store them as sensitive information. After importing, check that the configuration parsed correctly and the server list updated. Then grant the system VPN permission and test access. Don’t post the full subscription link in public forums or online conversion tools. If you need help, redact the link token and account details.
Coverage across 120+ countries, 210+ routes, and no limit on the number of devices connected at once are V9VPN service and device policies; they don’t guarantee compatibility with any particular app. Access depends on your local network, client configuration, and the target service’s region and account rules.
Monthly plans are ¥9.9 / 60GB, ¥18 / 250GB, and ¥28 / 500GB. Data resets monthly on the activation date; data packages don’t expire and remain available until used. If you use the service across multiple devices, choose based on your total usage—not the unlimited device count, which doesn’t mean unlimited data. V9VPN offers a 14-day no-questions-asked refund. See the Plans page for details.
For initial setup, see the Guides. You can use My IP to help check your browser’s exit IP. If the problem persists, tell support your device OS, client version, whether it occurs after locking the screen or switching networks, and any error details with sensitive information removed. These details are more useful for troubleshooting than simply saying “it won’t connect.”