How do you use a VPN on Android? The basic steps are to install a trusted client, import the configuration provided by your service, allow Android to establish a VPN connection, then verify your exit IP and app access. A “Connected” status only means the client has established a connection; it doesn’t guarantee that all traffic is routed as expected. This guide walks through the process and separates issues related to installation, permissions, background activity, and split tunneling.
Before you install: check the client and configuration source
Open the download section in your service dashboard and read the Android instructions. B2VPN’s client download is available on the dashboard download page. Don’t judge an installer’s safety by its filename in search results, and avoid modified apps from unknown sources in chat groups. If the provider publishes verification details, use them to check the file.
The client and route configuration are different things: the client runs the connection, while the configuration provides server, authentication, and routing details. Some clients fetch routes after you sign in; others require a subscription import. Check which method your dashboard uses. Don’t enter your account password into the authentication field for an arbitrary node.
Third-party clients also need a compatible configuration format and protocol. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC aren’t interchangeable names; even the same protocol can vary in compatibility depending on the transport or client core. Follow the client instructions in your dashboard. This guide doesn’t assume that B2VPN supports all of these protocols.
- ✅ I got the client from the service dashboard or the developer’s official release channel.
- ✅ I confirmed how to use it: account login, subscription import, or manual configuration.
- ✅ I checked that the subscription format is supported by the client and haven’t changed the connection parameters.
- ❌ Don’t post subscription links, account passwords, or screenshots containing authentication details in public forums.
Install and launch: grant the necessary permissions
If you install from a package, Android may ask you to allow your current browser or file manager to install apps from unknown sources. Verify the source before granting permission, then turn off that app’s installation access once setup is complete. Menu names vary between Android versions; try searching Settings for “Install unknown apps.”
After opening the client, sign in or import your configuration, then tap Connect. Android will show a VPN connection request explaining that the app can handle network traffic. Check that the app name matches the client you just installed before allowing it. This permission lets Android create the VPN interface; it doesn’t grant access to unrelated data such as your contacts or photos.
Most apps that use Android’s VPN interface can’t run at the same time under the same user profile. Ad blockers, local firewalls, and other VPN tools may already be using it. If connecting shuts down another app, disable the conflicting tool and test again instead of repeatedly reconnecting in the current client.
Import a subscription: check that the configuration is complete
A subscription link usually provides a set of routes and their configurations; it isn’t a regular web link. If opening it in a browser displays text or a download prompt, that doesn’t necessarily mean the link is broken. Use the import option in your dashboard or client whenever possible. If you need to copy the link, copy it in full, keep all query parameters, and leave out any punctuation from surrounding chat text.
- Open the configuration or subscription section in your client and choose the option to import from a link. The exact label depends on the client.
- Paste the subscription URL from your dashboard, save it, and update the configuration. Check that routes are available to select.
- If you get a format error, first check whether the subscription type matches the client instead of switching routes repeatedly.
- Select a route listed in your dashboard and connect. Keep the default transport and authentication settings, then test access.
If the import succeeds but no routes appear, check your account status, whether the subscription URL is still valid, and whether your current network can reach the subscription server. If the configuration shows a web page or sign-in page, you probably need to get the correct link from your dashboard. An update failure and a connection failure happen at different stages, so troubleshoot them separately.
A subscription URL may contain credentials linked to your account, so protect it like a password. If it’s exposed, use the reset option in your dashboard, replace the old URL in your client, and update the configuration again. Deleting the local configuration won’t invalidate a link that has already been shared.
Background battery settings: prevent disconnects when the screen is locked
If the connection works until you lock the screen, Android may be restricting background activity. A Wi-Fi handoff or an interruption on the route could also be the cause. First test with the same network while locking the screen, then decide whether to adjust battery settings. Changing too many options at once makes it harder to identify the problem.
In the app info screen, look for Battery, Background activity, or Battery usage settings. Allow the client to run in the background or add it to your device’s battery optimization exceptions. Some devices also have a separate auto-start option; enable it if the service instructions recommend it. Locking the app in the recent apps screen may help, but it doesn’t replace the battery settings.
Check whether Data Saver is restricting background access too. Allow the client to transfer data in the background, then switch from Wi-Fi to mobile data to see if the connection recovers automatically. If you need to reconnect manually after switching networks, check the client’s reconnect settings before assuming the subscription is invalid.
“Always-on VPN” and “Block connections without VPN” are separate system settings. The latter blocks network access when the tunnel is unavailable, which may suit users who specifically want that behavior. While troubleshooting for the first time, first make sure the connection is stable and understand what happens if it drops before enabling this option.
Verify it’s working: cross-check your exit IP, DNS, and apps
Before testing, check whether the client is in global mode or using split tunneling. In rule-based mode, some requests may go direct, so seeing your local exit when visiting a site in your region may be expected. To reduce variables, temporarily switch to the client’s global mode for testing, then restore your usual rules.
| Check | How to test | What it tells you |
|---|---|---|
| Exit IP | Visit the same network test page before and after connecting | Whether requests from that browser are using a different exit |
| DNS routing | Compare DNS test results with the client’s DNS settings | Whether DNS requests follow the expected routing policy |
| Target app | Reopen the app you need and try the intended action | Whether the app is routed as expected |
| Background recovery | Lock the screen and wake the device, then test after switching networks | Whether background activity and reconnection work properly |
Use the network test page to check for a change in your exit IP. IP geolocation databases can be out of date, so don’t assume a route is wrong based only on the city shown. A change in your browser’s exit also doesn’t mean every app on your device is using it.
A DNS leak occurs when DNS requests don’t follow the expected protected route and instead go to a local or otherwise unintended resolver. Seeing a public DNS provider on a test page doesn’t by itself prove there’s a leak. Also check the client’s DNS mode, query routing, and your browser’s secure DNS settings.
Android Private DNS, encrypted DNS in your browser, and DNS built into the client can all affect test results. Don’t leave security settings disabled just to make a test page look consistent. Note your original settings, adjust them according to the client’s instructions, and repeat the same test. If your network supports IPv6, check its route too so you don’t verify only one traffic path.
Split tunneling and routes: configure them for your needs
App-based routing decides which apps use the tunnel, while rule-based routing directs requests according to conditions such as domains and addresses. They’re not the same thing. Some clients let you proxy only selected apps; others let you bypass selected apps, which reverses what a checked box means. If your browser works but one app doesn’t, check this setting first.
If switching temporarily to global mode fixes the target app, focus on rule matching and app exclusions. If global mode doesn’t help, check the route, authentication, and the target service itself. Some apps keep old connections or cached location data, so fully close and reopen them after changing rules before testing again.
Don’t choose a route by its name alone. Direct, relay, and IEPL refer to different transmission paths or delivery methods, not specific proxy protocols, and the labels alone don’t determine the experience. Results also depend on your local network, exit load, and the target service. Compare availability using the same app on the same network before choosing a route for everyday use.
Common issues: troubleshoot by stage
Import works, but the connection keeps failing
First check that your device clock is correct and your account is active, then review the client’s error message. For an authentication error, check the configuration or update the subscription. For a timeout, determine whether the current network can reach the server or whether the remote connection is failing. Test on both Wi-Fi and mobile data, and try another route from your dashboard if available. Don’t disable certificate verification to bypass an error.
Connected, but no pages will load
Disconnect the client first and confirm that your regular network works. If the public network requires a web sign-in, complete its normal access process. Then check whether “Block connections without VPN” is enabled, another local VPN is conflicting, or DNS settings differ from the client’s instructions. Change one setting at a time and repeat the same test.
Only one service says your region isn’t supported
A working exit doesn’t guarantee that a target service will accept it. Your account region, location permissions, cached data, and the platform’s own access policies may all affect the result. Don’t assume a region error means installation failed, and avoid repeated sign-ins that could trigger extra account checks. For streaming issues, see the streaming access guide for more information.
If you still can’t identify the issue, open a support ticket from your dashboard. Include your device OS, client name, the error, and whether it occurs during import, connection, or app access. Before sending logs, redact subscription URLs, authentication details, and other private information. Don’t upload an unchecked copy of your entire configuration.
B2VPN account and data policies
B2VPN doesn’t require an email address. Create an account with a username and password, with no device limit. B2VPN provides apps for Android, Windows, iOS, macOS, and Linux. Client interfaces and system permissions vary by platform, so Android menu instructions may not apply elsewhere.
Monthly plans include ¥9.9 / 60GB, ¥18 / 250GB, and ¥28 / 500GB, with data resetting each month on the activation date. Data packages include ¥158 / 300GB, ¥358 / 1000GB, and ¥658 / 3000GB; they last until used and never expire. Choose based on your usual app usage—unlimited devices doesn’t mean unlimited data.
B2VPN’s privacy claim is anonymous, no-logs service. This doesn’t mean activity after signing in to a website can’t be linked to that site’s account. You can request a full, no-questions-asked refund within 7 days of your first payment. See the plans page for prices and access options, and the quick start guide for setup and connection instructions.