Choosing an Android VPN: Check for Dropouts, Then Test Routing

When comparing Android VPNs, test background reliability and per-app routing separately. A new request should still work after you unlock your phone to confirm the connection is active; only the selected apps should use the assigned route to confirm routing works as expected. Battery optimization is one factor to check when investigating background dropouts, not a routing switch.

This comparison focuses on what to check on the same device with different settings—not on ranking brands by speed. When comparing clients, keep the device, network, route, and protocol the same, and change one setting at a time. If two clients can't use the same route and protocol, the results only show how each setup performs on your device; they can't isolate the client as the cause.

How to Compare Background Reliability, Battery Optimization, and Per-App Routing
What to check How to test How to interpret the results
Background reliability Compare a new request with the screen on and after unlocking from the lock screen, without opening the VPN client first. If it only works again after you reopen the client, check background restrictions or the reconnect mechanism.
Battery optimization Repeat the lock-screen test with the system defaults, then with the app's background restrictions relaxed. Keep the change only if the connection repeatedly recovers more reliably with restrictions relaxed.
Per-app routing On the same network, test apps included in and excluded from the VPN. Included apps should use the expected route; excluded apps should connect directly or be blocked by the system as expected. A connection icon alone can't confirm this.

Background reliability: Distinguishing lock-screen dropouts from network-switch reconnections

  1. Start with a baseline while the screen is on. Connect to the VPN, open the network check in a test browser, and note the exit IP. Then refresh a page you normally use. If it already fails with the screen on, check your network and route before changing battery settings.
  2. Test the lock screen on its own. Keep the network unchanged and lock your phone for a typical amount of time. After unlocking, don't reopen the VPN client yet. Send a new request in the test browser and check the exit IP again. Seeing a previously loaded page doesn't mean you're still connected.
  3. Test a network switch on its own. Keep the screen on and switch from Wi-Fi to mobile data, then test the reverse. Check whether new requests fail briefly and recover on their own, or require a manual reconnect. If the target network also fails without the VPN, troubleshoot the network first.

The system's VPN icon shows that a VPN session is active; it doesn't guarantee the remote route is currently working. If your browser works after unlocking but the exit address has reverted to the one used without the VPN, background reliability hasn't been confirmed. Conversely, if browser requests work but notifications are delayed, don't rush to change routes: background restrictions on the messaging app may be delaying them.

Battery optimization: Relax restrictions only for apps that need it

Retest with the system defaults first. If the problem mainly occurs after locking the screen, open the client's battery or background activity settings through the system's app info and look for options to allow background activity or remove restrictions. Menu names and available options vary by device maker. Change only this client setting, keep the route, lock-screen duration, and network the same, then compare results.

If relaxing restrictions makes the connection more reliable after locking the screen, keep the exception and monitor battery use during normal use. If there's no improvement, restore the defaults and check whether the client can reconnect on its own. If failures happen only after switching networks with the screen on, first check whether the new network works and whether the client reconnects after the network changes.

Per-App Routing: Check Which Apps Use the VPN

Read the client's list labels carefully. “Proxy selected apps only” means an allowlist: apps you don't select generally won't use the VPN. “Skip selected apps” means a blocklist: selected apps generally won't use it. Choosing which apps can enter the VPN is different from choosing how traffic is routed by domain or destination address once it enters. Even an allowlisted app may connect directly to a test site if the client has a rule for it.

  • ✅ Keep the network unchanged, disconnect the VPN, and note the test browser's direct exit IP.
  • ✅ Compare two browser apps that can be selected separately: include one and exclude the other. Save, reconnect as prompted by the client, and send a new request to the same test page.
  • ✅ Then test the app you actually plan to use, including key actions such as signing in, syncing, or making a call. A browser's exit IP doesn't prove that other apps use the same route.
  • ❌ Don't assume routing is broken just because an excluded app can't connect. If the system's “Block connections without VPN” option is enabled, excluded apps may be unable to connect directly.

If both browsers show the same result, first check that you interpreted the list correctly, then see whether the client has a rule to route the test site directly. If an app opens a link in an external browser, the browser may be making the request; check how that browser is routed. An exit IP check only shows the route used for that request—it doesn't mean DNS queries took the same route.

Make your final choice based on how you use it

For meetings and messaging, prioritize recovery after a network switch: test whether a real session continues after a brief interruption instead of checking only whether a web page loads. If you want only work apps to use the VPN, make sure the actual apps sending requests can be selected, then check that local apps still connect as expected. If you'd rather lose connectivity than connect directly when the VPN drops, test the system's blocking option separately; it isn't a background reliability feature.

Before switching clients, check that it supports the protocols and import formats included with your subscription. Being able to paste a link doesn't mean the client can parse the configuration. Keep your subscription URL private; don't include it in public screenshots. Once you've confirmed the configuration works, use the default settings to test the lock screen, network switching, and per-app routing. Note any problems and the changes that fixed them. After a system or client update, retest the scenarios that previously failed to see whether those settings are still needed.