For Android users noticing significant battery drain while connected, disconnections when the screen is off, or uncertainty about allowing background activity. Start by comparing battery use under consistent conditions, then check reconnects, background permissions, and per-app proxy settings. The goal is to keep the apps you need connected—not to disable every battery-saving feature.
Separate battery share from actual battery drain
Seeing v2rayNG near the top of Android's battery screen doesn't mean it used that share of the phone's total battery. Android versions may show an app's share of the battery used during a period or use another estimate. The VPN interface passes app traffic to the Xray core, and the system may attribute some network activity to the VPN app. Check the reporting period and the phone's overall battery drop before looking at app rankings.
For example, if your phone drops from 80% to 76%, it used 4 percentage points of its battery. If Android reports that v2rayNG accounts for 25% of the usage during that period, that does not mean it used 25% of the phone's total battery. This illustrates how reporting works; it is not a measured battery-use figure for the client. Battery age, screen brightness, and cellular signal strength also affect results.
These figures describe a test plan, not a performance guarantee. Record three scenarios: proxy off with the screen locked, proxy connected with the screen locked, and proxy connected while performing the same task. The task could be opening the same set of web pages. Don't compare a video-streaming test directly with a screen-off idle test.
- Test in the same location and on the same network. Don't measure while charging.
- For each test, note the starting and ending battery level, signal strength, background downloads, and any change in phone temperature.
- Pause temporary tasks such as app store updates, but don't stop essential messaging services just for the test.
- If a short test shows a difference of only 1 percentage point, extend the observation period. Whole-number battery readings aren't precise enough for fine-grained conclusions.
Check traffic, network conditions, and reconnects separately
Android VPN mode in v2rayNG adds traffic forwarding, protocol encapsulation, and encryption and decryption work, but battery use isn't determined by the protocol name alone. Video streaming, photo syncing, and downloads keep the wireless radio busy. With a weak signal, cellular networking itself can use noticeably more power—even when the proxy configuration hasn't changed.
| What you notice | Check first | How to compare |
|---|---|---|
| Data transfer never drops to zero | Downloads, backups, video, and background sync | Pause tasks, lock the screen, and see whether traffic drops |
| Mobile data heats the phone; Wi-Fi doesn't | Cellular signal and network switching | Repeat the same test on stable Wi-Fi |
| Repeated connection failures in the log | Node reachability, DNS errors, and network interruptions | Try another known-working node and check whether the errors stop |
| Disconnects with the screen off, reconnects when it turns on | Battery optimization, background limits, and system sleep | Change only v2rayNG's background permissions first |
Open Logs from the v2rayNG sidebar and compare entries with the time the issue occurred. Menu locations may vary by version, so use the labels in your current app. A single timeout doesn't prove repeated reconnects; repeated timeouts for the same destination, DNS failures, or connection closures within a short period are worth investigating. Before sharing logs, redact server addresses, subscription URLs, and user identifiers.
Stop repeated failures first
If connection errors keep appearing while the phone is locked and idle, fix the node or network before comparing battery use. Changing battery settings at this point can make a connection problem look like a background-permission issue.
Don't infer battery life from the VMess or VLESS label alone. Transport, security settings, server configuration, actual traffic, and network quality all affect the workload. v2rayNG uses the Xray core; v2flyNG uses the v2fly core. Their configuration support and options aren't interchangeable, and without testing under the same conditions, one shouldn't be treated as a battery-saving alternative to the other.
Use battery optimization exemptions only when needed
Allowing background activity mainly helps the service stay active when the screen is locked; it doesn't make the same amount of traffic use less power. Strict background limits may reduce runtime, but can also delay messages and interrupt connections. If the connection stays stable with the screen off, leave the defaults in place. Relax restrictions one at a time only if you can reproduce background interruptions.
-
Open app info
Long-press v2rayNG on the home screen and select App info. You can also go to Android Settings → Apps → See all apps → v2rayNG.
-
Check battery settings
On common Android 13 screens, go to App battery usage or Battery and check whether the app is set to Unrestricted, Optimized, or Restricted. If the connection drops with the screen off, try changing Optimized to Unrestricted and test again.
-
Check background permissions
Some systems also offer settings such as Autostart, Allow background activity, or a battery-optimization exemption. Change only the settings v2rayNG needs; don't remove restrictions for every app. Names vary by device.
-
Check the persistent notification
In App info → Notifications, check that service notifications are allowed. The notification helps you monitor the app's status. Hiding it doesn't stop the service or save battery.
-
Test with the screen locked
Return to v2rayNG, stop and reconnect, then lock the screen for 30 minutes. Make a real request from the app you're testing, and check the connection status and logs.
Some manufacturers put the same permissions under Battery → App launch management, or use Unrestricted instead of Unrestricted battery usage. There isn't one path that fits every device. Even with app restrictions relaxed, Android sleep, network policies, and manufacturer-specific background management can still affect connectivity. An exemption doesn't guarantee a persistent connection.
Use per-app proxy settings to avoid unnecessary traffic forwarding
Per-app proxy settings control which apps send traffic through Android's VPN interface. Routing rules then decide whether connections handled by the core use the proxy, connect directly, or are blocked. These are separate controls. An app can enter the VPN and then be routed directly, which may still involve local forwarding. If an app doesn't need the VPN at all, exclude it from the per-app selection.
In common v2rayNG versions, open Settings → Per-app proxy from the sidebar, enable it, and select apps. Some versions list Per-app proxy directly in the sidebar. Read the mode description before selecting apps, especially whether Bypass mode is enabled. The same selection can mean the opposite thing in the two modes.
| Mode | What selecting an app does | Best for |
|---|---|---|
| Proxy only selected apps | Selected apps use the VPN; unselected apps use the system network | Only a few apps need the proxy |
| Bypass selected apps | Selected apps bypass the VPN; all other apps use it | Most apps need the proxy, with only a few exceptions |
| Per-app proxy disabled | The VPN generally receives app traffic, which is then handled by the core's routing rules | You need the VPN to handle all traffic, then want to refine routing |
- Start by selecting just one high-traffic app that definitely doesn't need the proxy. Then stop and reconnect so the app selection takes effect.
- Make a request from both a selected and an unselected app. Existing connections may persist, so fully close and reopen the app if needed.
- Web pages opened in a browser, external download managers, and system services may belong to different apps. Don't assume selecting the browser covers all related traffic.
- Apps that bypass the VPN use your local network connection. Exclude an app only if you're comfortable with that.
If only a few apps need the proxy, narrow the VPN scope first
If only one browser needs the proxy, try the Selected apps mode first. Don't exclude messaging apps that still need the proxy just to lower v2rayNG's battery ranking. Any savings depend on the traffic those apps actually use, not on the number of apps selected.
Don't use forced background keep-alive as a substitute for troubleshooting
Always-on VPN and Block connections without VPN in Android's VPN settings control connectivity; they aren't battery-saving options. Always-on asks the system to keep the selected VPN active. Blocking connections without a VPN restricts network access when the VPN is unavailable. If a background policy stops the service while this is enabled, the phone or affected apps may lose internet access—not just access to proxied websites.
- Need the VPN to handle traffic continuously? First confirm the connection stays stable with the screen locked, then enable Always-on VPN if needed. On many devices, go to Settings → Network & internet → VPN and tap the settings icon next to v2rayNG.
- Only need it for a short session? When you're done, stop the connection in v2rayNG. It's easier to verify the current state than repeatedly force-stopping the app.
- Want to block traffic without the VPN? Make sure you're comfortable losing internet access if the VPN stops, and note where to find the setting again.
- Seeing repeated reconnects? Check your Wi-Fi, node, and logs first. Don't change the protocol, DNS, routing, and background permissions all at once.
Updating subscriptions, testing real connections, and running bulk speed tests all generate extra network activity. When investigating idle battery drain, stop any manual batch tests first. If the current version or another tool runs scheduled tasks, note when they occur. Keep logging at the level needed for troubleshooting; continuous verbose logging adds output and isn't suitable as an everyday setting.
Android generally allows only one VPN service to handle the standard VPN slot at a time. During testing, keep just one VPN service running to avoid another network tool taking over and causing repeated disconnections. If the phone still heats up after stopping v2rayNG, check system downloads, hotspot use, weak signal, and other apps instead of adding more client settings.
Common questions about battery drain and screen-off disconnects
Will setting v2rayNG to Unrestricted immediately reduce battery use?
No. It lets the service run more reliably in the background; it addresses restrictions, not power use. Keep the setting and compare whole-phone battery drain over two rounds using the same network and tasks. If the connection was already stable and battery use increases, switch back to Optimized and keep monitoring.
The connection drops when the screen locks and returns as soon as it turns on. What should I change first?
First check the app's battery setting and background data permission, then review logs from the time of the disconnection. If no apps can get online, also check Android's Block connections without VPN setting. Don't mistake a disconnection caused by this protection for a node failure.
Why can't other apps connect when I proxy only the browser?
First make sure Bypass mode isn't enabled, which would reverse what your selections mean. Then check Android's VPN lockdown setting. Note the original settings, revert one change at a time, and reconnect. Don't try to mask a mode mismatch by selecting more apps.
Battery use improved after switching nodes. Does that prove the protocol was the problem?
No. Changing nodes also changes the route, server load, and connection success rate. Keep the network, tasks, and observation period the same. Check whether reconnect errors have decreased before comparing transport settings.
Keep a record of settings you can revert: battery mode, background data permission, per-app mode, selected apps, and Always-on VPN status. Change one setting per round and record connection stability and whole-phone battery drain. If idle use remains unusually high under the same conditions, report it with redacted logs, your Android and v2rayNG versions, and test steps—not just a screenshot of the battery ranking.