At a glance

For iPhone and iPad. Start in Settings → Battery and compare battery level changes with background activity over the same period. Then narrow the automatic connection conditions in Shadowrocket under Settings → On Demand. If you don't need a proxy on a trusted network, test On Demand. If a work session needs a continuous connection, keep it connected and decide based on how it resumes after locking the screen or switching networks.

Start with Battery: usage share isn't battery drain

Open Settings → Battery and find when the battery level dropped noticeably. Check app usage and activity for that same period. If your iOS version lets you select a time range on the chart, select it before reading the app list. An all-day ranking can't explain a specific drop while the screen was locked. Note the start and end battery levels, whether the screen was on, whether Shadowrocket was connected, and whether you were using Wi-Fi or cellular data.

Battery
Check battery level and activity in Settings
On Demand
Check connection conditions in Shadowrocket Settings
Home
Check the current connection status and Global Routing

The percentage in the usage list is Shadowrocket's share of app battery use during the selected period—not the number of percentage points the battery lost. For example, a 30% share doesn't mean the battery fell from 80% to 50%. If the battery barely dropped overall, a high ranking alone doesn't indicate a problem. Conversely, if the battery keeps draining with the screen locked, check whether network activity was concentrated during that period, even if Shadowrocket wasn't near the top of the list.

First, pinpoint when the battery drains with the screen locked

If noticeable drain only happens while you're watching videos or downloading files with the screen on, leave the connection settings unchanged and test standby drain separately. Only move on to an On Demand comparison if you can reproduce the drain while the device is idle.

On Demand vs. a persistent connection

On Demand determines when iOS manages the VPN connection based on conditions. Global Routing determines how traffic is handled within the connection. Changing Global Routing to Direct, or matching requests to DIRECT in Config, does not disconnect the VPN. To test whether disconnecting affects battery use, check the connection status in Home—don't rely on routing settings alone.

Connection typeBest forWhat to check
Connect on demandYou need a proxy on some networks but can disconnect at other times.After joining a network that needs a proxy, does the first request succeed? On networks that don't need one, does the connection actually disconnect?
Connect manually and stay connectedYou need a proxy throughout your current work session, or interruptions could disrupt a long-running session.Does the connection remain usable with the screen locked? After switching networks, does the existing session continue, or must it reconnect?

Here, a persistent connection means leaving the VPN connected rather than disconnecting it—not keeping Shadowrocket open in the foreground. On Demand doesn't mean “disconnect when the screen locks, reconnect when it wakes”: if the current network still meets the connection conditions, locking the screen won't necessarily end the connection. Either setup may briefly interrupt traffic when you switch networks. Choose based on how your actual work sessions behave.

Set up On Demand: test one familiar network first

  1. Note your current settings

    In Shadowrocket Home, note the selected server, connection status, and Global Routing. Then open Settings → On Demand and record the current toggle and conditions. For this test, don't switch servers or change rules in Config.

  2. Narrow the conditions

    Check the network conditions shown for your device under Settings → On Demand. Test one network that genuinely needs an automatic connection; don't change all the conditions at once. If you don't need a proxy on a particular Wi-Fi network and no app requires a continuous VPN connection, test whether staying disconnected on that network works for you.

  3. Test automatic connection

    Join a network where the connection should trigger, open a page or app that normally needs it, and check the status in Home. If it's hard to tell which of two network conditions applies, disconnect and reconnect to the same Wi-Fi network, then test again. On devices with cellular connectivity, test switching between Wi-Fi and cellular separately.

  4. Test recovery after locking the screen

    Start a session that you normally can't interrupt, lock the screen for a while, then return to the app. Record whether the session still works, needs to reconnect, or requires you to sign in again. Seeing the VPN reconnect doesn't mean the original session has recovered.

  5. Compare equal-length standby periods

    Choose two 60-minute standby periods: in one, connect manually and stay connected; in the other, enable On Demand and confirm that its conditions actually take effect. Use the same location and Wi-Fi if possible, start with similar battery levels, and keep Low Power Mode in the same state. Don't charge the device or start downloads during either period. Record the actual connection status and start and end battery levels—not just the usage ranking.

If the VPN stays connected during both periods, you haven't tested the difference between staying connected and disconnecting. If the battery levels differ by only one percentage point, or one period coincides with a system update, photo sync, or a significant signal change, don't draw conclusions about which setup uses less power. Repeat the test under more similar conditions.

Can't reconnect after locking the screen? Check the network and connection conditions

If the problem only occurs after switching networks, first check whether the new network can open ordinary webpages, then check whether it meets the On Demand conditions. On Wi-Fi that requires a web sign-in, complete the network login first. If ordinary webpages won't load either, troubleshoot network access before changing routing rules.

Error: The VPN server did not respond.

What it means: This system message means no response was received from the server. It doesn't tell you whether the network is unreachable or the server didn't respond. What to do: If manual testing is allowed, note the current conditions, temporarily turn off On Demand, and connect manually from Home on the same network. If you see the same message on a network known to work, ask your service provider to check the server status.

  • Manual connection works, but automatic connection doesn't: First check whether the network you're connected to matches the configured conditions. After changing them, rejoin the network and test the initial connection. Don't count a connection left over from an earlier test as a successful result.
  • Home shows Connected, but one app fails: Check Global Routing first. If you're using Config, check which rule and policy actually match the request. A single app failing doesn't mean the VPN is disconnected.
  • It only fails while moving or switching networks: Test the same session on a stable network. If it works there, evaluate recovery after switching networks separately; don't confuse reconnection issues with battery drain while idle.

Finding the right balance: set up for your network and session length

Start with the smallest change: test disconnecting on a stable network that doesn't need a VPN, and staying connected during work sessions that require continuous access. If your organization manages the settings, or an app requires traffic to pass through the VPN, follow those requirements. Don't bypass them to reduce battery use.

  • Wi-Fi that doesn't need a proxy: Check that the On Demand conditions allow the VPN to disconnect, then test your usual apps. Keep the change only if access works and repeated standby tests show a real reduction in battery drain.
  • Work sessions that need a continuous connection: Connect manually on a stable network and stay connected, then disconnect when you're done. If you need to switch networks, first check whether the app recovers using a task you can interrupt. Don't run your first test during a meeting or remote session.
  • Occasional use where reconnecting is acceptable: Enable On Demand on the networks where you actually need a connection. Check that the first request succeeds and that the connection recovers after the screen is locked. If the first request repeatedly fails, restore the previous settings and check the connection conditions one at a time.

Keep a setup only if it meets both needs: when you don't need a proxy, the connection status in Home matches your expectations; when you do, your apps recover as required after the screen is locked or you switch networks. If a change doesn't consistently reduce battery drain and instead causes more reconnects or sign-ins, restoring the previous settings is the better choice.