Android VPN picks: Background reliability and app-specific routing tested

Android battery management can stop VPN apps in the background and drop connections. This hands-on comparison tests background reliability, battery exemptions, and per-app proxies, with tips for choosing a client.

When choosing an Android VPN, start with two checks: does it reconnect after the screen locks or the network changes, and does each selected app use the expected route? Test background reliability, battery exemptions, and per-app routing separately. This guide explains how to compare clients on the same device without treating test conditions as results for a specific model or app.

Android VPN Comparison: First Check Whether It Keeps Working in the Background

A VPN icon means Android still has a VPN session; it doesn’t mean the remote server is reachable. A persistent foreground-service notification doesn’t prove traffic is still being routed, either. Conversely, if a video stops playing after the screen locks, that may be the app’s background playback policy—not a dropped tunnel. After waking the device, open a page that needs a live connection and doesn’t just show cached content, then retry in the original app. Record failure in both places differently from failure in the original app alone.

Same-Device Test Conditions and What to Record
TestControl conditionsWhat to record
Connection while screen is lockedKeep the server, protocol, and lock duration the same; don’t change the network connectionAfter waking the device, does it work right away, reconnect automatically, or require a manual reconnect?
Battery optimization exemptionTest with the default system settings first, then relax only the client’s battery restrictionsRepeat the screen-lock test and note whether the problem occurs only with the default settings
Network switchingKeep the same route configuration; test switching from Wi-Fi to mobile data and backDo new requests work? Does an existing session need to be reopened?
Per-app routingWith the same configuration, test apps included in and excluded from the VPNDo the two apps use the expected routes?

Before comparing clients, make sure they can use the same protocol and server. Importing the same subscription doesn’t mean both clients selected the same route; check automatic server selection and default routing mode, too. If you can’t match the test conditions, describe the result as “this client-and-route combination works better on this device.” Don’t attribute differences in the route to a client’s ability to stay connected in the background.

Background reliability tested: Lock the screen, then test network switching

  1. After connecting, confirm a request works in the foreground. Note the system battery settings, server, protocol, and current network. Pause other apps that use Android’s VPN interface, such as firewalls running in local VPN mode, so they don’t replace the active session during the test.
  2. Return to the home screen and lock the device. Don’t force-stop the client or clear recent apps. Let the device go into standby as it normally would. After waking it, open the test page before launching the VPN client; opening the client may trigger a reconnect and hide a recovery problem.
  3. Once you’ve recorded the screen-lock test, switch between Wi-Fi and mobile data. Use a new request to check whether the tunnel recovers. If a new page loads but an existing call or remote session has ended, record those outcomes separately; a dropped existing session doesn’t by itself mean reconnecting failed.
  4. Repeat any unexpected result under the same conditions. If the VPN indicator disappears and the app is no longer running, check background management first. If the indicator remains but new requests fail, confirm the switched-to network works, then check tunnel recovery, server connectivity, and DNS resolution.

Locking the screen, swiping an app out of recent apps, and using “Force stop” in system settings are different actions. Android versions also handle dismissed tasks differently. If you normally clear recent apps, test that separately; don’t mix force-stop results into your everyday screen-lock comparison. More useful tests reflect situations you regularly encounter, such as leaving the device idle on a desk or switching networks during a commute.

Battery Optimization Exemptions: Change Only Restrictions That Explain the Problem

System settings such as “Battery optimization” and “Background activity” may be separate from a manufacturer’s auto-start controls, and they don’t all do the same thing. If the VPN repeatedly disconnects after the screen locks with default settings, open the app’s details in system settings and look for battery usage or background activity options. If an “Unrestricted” option or equivalent is available, change it for the VPN client only, then repeat the test under the same conditions. If the default settings are already reliable, there’s no need to relax restrictions.

If relaxing battery restrictions doesn’t help, revert the change. Check auto-start or the client’s start-on-boot setting only when the problem is specifically that it doesn’t connect automatically after startup. If it fails only when switching networks, focus on whether the client restores the tunnel rather than continuing to disable battery-saving options. Also weigh any improvement in background reliability against standby battery use; a persistent notification for a short time isn’t proof the test passed.

“Always-on VPN” and “Block connections without VPN” are separate settings. The latter can prevent apps that are meant to connect directly from accessing the internet. If some apps need a direct connection, retest with your specific Android version and client; don’t mistake a blocking policy for a routing-rule failure.

App-specific routing tested: Check each app’s actual route

First check whether the client offers “VPN for selected apps” or “Bypass VPN for selected apps.” The first option includes the listed apps; the second excludes them. Domain- or IP-based routing matches destinations after traffic enters the client—it doesn’t replace including or excluding apps. Keep in mind that when an app opens an external browser or a system component handles a request, that other component may be the one making the network connection.

Prepare two browsers that can each open the same IP-check page. Record the public IP shown before connecting, then connect and confirm the test page uses the VPN route. Include one browser and exclude the other. If the client needs to rebuild the VPN to apply the app list, save the settings and reconnect. In each browser, open my IP and check again. Avoid opening the link from a chat app, which could send both checks to the default browser. If the client also has destination-based routing rules, make sure they don’t force the test page to connect directly; otherwise, you can’t tell whether the app list is working.

Different IP addresses show that these checks took different routes, but they don’t prove that every request, address type, or DNS query from an app follows the same path. To check for DNS leaks, separately review Android’s Private DNS, the browser’s Secure DNS, and the client’s DNS settings to see whether the resolver matches your expectations. Don’t infer the DNS route from the IP’s region, or treat the use of a public resolver alone as proof of a leak.

Choosing an Android VPN for Your Needs

  • ✅ Commuting and remote work: Choose a client that restores new requests automatically after a network switch, then check whether your work apps recover easily if an existing session drops.
  • ✅ Video and everyday browsing: Choose a client with clear app inclusion and exclusion settings and routes you can verify. Test actual playback and page loading instead of checking only whether the home page opens.
  • ❌ Don’t choose based only on the number of supported protocols. Protocol support doesn’t guarantee that the current subscription will import correctly or predict how the connection will perform in standby.

Before importing, check that the client supports the subscription format provided by your service. After importing, confirm the selected server and protocol work before testing background reliability. If the configuration has multiple servers, use a fixed one for your first comparison so automatic switching doesn’t affect the result. Subscription links may contain access credentials; don’t share the full link in screenshots when asking for help. For questions about system permissions or importing a configuration, see the guides.

Bottom line: Prioritize a setup that reconnects with the default battery settings and lets you verify per-app routing. If a setup becomes reliable only after relaxing the client’s battery restrictions, keep the change only if its standby battery use is acceptable. If you can’t confirm the routes used by your regular apps, don’t rely on it for per-app routing.

Start Free