This guide is for users who have set up Shadowrocket on an iPhone or iPad and want to investigate battery drain while the screen is locked. Start with the system battery history to identify when the drain occurs, then test Ping checks, automatic connection, and a persistent VPN connection separately. If you only use the VPN occasionally, begin with manual connections. If it needs to reconnect automatically, narrow the On Demand conditions to match your network needs.
Use Battery settings to find when power is being used
Open Settings → Battery and check the date or time when the battery drained. If you can select a time range on the chart, select it first, then review the app activity list. The percentage shown for Shadowrocket is its share of battery use within the selected period; it does not mean the app directly reduced the battery level by that many percentage points. To investigate drain while the screen is locked, first check the battery graph and screen activity, then see whether Shadowrocket had background activity during the same period.
- Record the starting and ending battery levels. Choose a period with no charging and little or no screen use. Note the battery level at the start and end, whether the device was on Wi-Fi, and whether it switched to cellular during the test. A weak signal during a commute is not directly comparable to stable Wi-Fi overnight.
- Check activity over the same period. Review Shadowrocket’s background activity in the app list, and also look for photo syncing, system updates, and downloads from other apps. Background activity indicates that an app was active; it does not mean it continuously sent data to a proxy server. Nor does it justify attributing all VPN-related system power use to one app.
- Separate VPN status from battery changes. Return to Home at the start and end of each test and note the connection status. A VPN indicator only shows that a tunnel is established. If screen use differed significantly between the periods you are comparing, you cannot attribute the battery difference to the VPN just because its status changed.
How to compare: choose two similar screen-off periods
If the drain happens mainly while switching networks during a commute, retest on a similar route for a similar duration. Don’t use an overnight standby test at home as the comparison.
On Demand controls when the tunnel connects—not how each request is routed
In Shadowrocket, open Settings → On Demand and review the enabled triggers. iOS starts the VPN connection when their conditions are met. Once the tunnel is established, traffic inside it is handled according to the current Global Routing setting. With Config, a rule can send a request through DIRECT, but that does not close the established tunnel. On Demand also does not disconnect the VPN as soon as you leave the app. If the current network continues to meet the conditions, the VPN may stay connected for an extended period.
- For occasional use: Turn off On Demand, connect manually from Home when needed, and disconnect when finished. This lets you control whether the tunnel is active during the test. This approach isn’t suitable for services that need continuous access through the tunnel.
- Connect automatically on specific networks: Review the network conditions available in the current settings and keep only the triggers you need. For example, if you only need automatic connections on cellular, don’t also set your usual Wi-Fi networks to trigger a connection. After changing the settings, switch networks to verify the behavior.
- For extended use: If your work requires a continuously available tunnel, keep the VPN connected and first reduce unnecessary checks. Repeatedly disconnecting and reconnecting isn’t necessarily more battery-efficient than maintaining a stable connection, especially when reconnects require repeated handshakes or the signal is weak.
Reduce Ping checks and separate probe activity from connection drain
Ping and connectivity tests used to compare response times actively send requests. The exact probe method depends on the test feature and is not necessarily ICMP. Repeated bulk tests increase short-term network activity. On cellular, even infrequent background requests can keep the radio from returning to a low-power state. Short-term drain from a manual test round does not explain ongoing battery loss throughout the rest of the night.
- When the connection is working, don’t repeatedly test every saved server just to refresh latency numbers. If you have trouble accessing a service, test only the server currently in use and note the time, network, and whether the request timed out.
- If your current policy group uses automatic checks, confirm they’re necessary for your needs. If you can adjust them, increase the interval or disable nonessential checks—but change only one at a time. If your configuration doesn’t use automatic checks, there’s no need to look for a universal Ping frequency setting.
- For a retest, leave your existing On Demand and routing settings unchanged so you can isolate the effect of probe frequency. If stopping manual bulk tests reduces drain only while the screen is on, separately check for reconnections while the screen is locked in the next round.
How to interpret a Ping timeout
Error: The request timed out.
What it means: If this system network error appears in the diagnostic log, the request didn’t complete within the allotted time. The message alone can’t tell you whether the network was unstable, the remote server responded slowly, or the probe target was unreachable.
What to do: On a stable network, test the server currently in use once, then check whether requests for the service you actually need are also failing. Don’t increase the Ping frequency to decide whether the connection has recovered.
Retest under the same conditions: On Demand, always-on, or manual
Keep the network, device location, and test duration consistent. For example, run two screen-off tests of about two hours each on the same Wi-Fi network. Keep Low Power Mode, charging, downloads, and backups consistent too. Establish a baseline using one connection setup, then change only one factor in the next round. To assess the effect of automatic reconnections, run a separate test switching between Wi-Fi and cellular; don’t mix those results with standby data from stable Wi-Fi.
| Connection setup | What to record | When to keep this setup |
|---|---|---|
| Manually disconnected | Turn off On Demand, then disconnect from Home. Record battery drain while the VPN is not in use. | If the battery still drains during similar periods while disconnected, first check other app activity, sync tasks, and network signal. |
| On Demand | Record which networks meet the conditions, when the network changes, and the connection status before and after each switch. | If automatic connections also trigger on networks you use regularly but don’t need the VPN on, narrow the trigger conditions and test again. |
| Manually connected and left on | Stay connected on a stable network, don’t run tests during the observation period, and check that your services work as expected. | If you need continuous access and the battery use is acceptable, keep the VPN connected. If the drain mainly occurs during network changes, investigate reconnections first. |
Battery levels are shown as whole numbers, so a one-percentage-point difference in a single test isn’t enough to tell which setup uses less power. If you see a difference, reverse the test order and run another round to check whether the result consistently follows the same setting. If screen-off drain remains similar with automatic checks and On Demand disabled and the VPN manually disconnected, shift your investigation back to system activity rather than continuing to change servers or routing rules.
Recommendation: choose based on whether you need automatic connections
For occasional use, connect and disconnect manually. If automatic connections are needed only on some networks, narrow the On Demand conditions. If your work requires a continuous connection, leave the VPN connected and first reduce nonessential tests. Keep the settings needed for your work when retesting; there’s no need to aim for zero background activity.