Long background activity in Shadowrocket doesn’t necessarily mean the app is constantly working hard. Battery use depends on traffic, signal strength, connection retries, and routing rules. This guide focuses on iPhone and iPad, covering Settings → On Demand, the trade-offs of keeping a connection active, and how to compare fixed time periods to distinguish connection settings from network issues. Menus and system battery reports may differ on other platforms, so don’t assume the same menu path applies.
What drains battery in the background: connection time isn’t workload
Once connected, Shadowrocket uses the system network extension to process traffic routed through the tunnel. Other apps can still generate network activity through syncing, streaming, and file transfers, even when Shadowrocket isn’t open on screen. Leaving the app doesn’t disconnect it, and background activity time alone doesn’t tell you how much extra battery was used.
On iPhone or iPad, open the battery usage page in Settings. Check the selected time range, then compare screen activity and app usage over that same period. The battery usage percentage shows an app’s share of consumption during the selected period; it doesn’t mean the battery’s capacity dropped by that many percentage points. Reporting methods and displayed details can vary by system version, so also check the device’s overall battery level over time.
- Ongoing traffic: Video streaming, cloud backups, and large downloads increase both wireless communication and data processing. Don’t attribute all the resulting battery use to keeping the connection active.
- Weak signal and network switching: Unstable cellular reception, weak Wi-Fi coverage, and switching between networks can lead to retransmissions and reconnects.
- Connection maintenance: Some protocol or server configurations use keepalives and handshakes. The actual frequency depends on the configuration; protocol names alone don’t tell you how much battery they use.
- Additional activity: Repeated latency tests, bulk availability checks, and frequent subscription updates all generate extra requests. Track these separately when troubleshooting.
On Demand controls connection triggers, not battery usage
Settings → On Demand configures when the system establishes or resumes a connection based on specified conditions. It isn’t a power-saving mode, nor does it mean the proxy automatically stops when the screen locks. If a condition still matches, the connection may remain active. After a manual disconnect, a matching condition may also trigger a new connection.
Think of this in two separate layers: On Demand determines when to connect, while Global Routing determines how traffic is handled once connected. Switching to Direct doesn’t disconnect the connection, and choosing Config doesn’t necessarily make the system remove the tunnel when no proxy rule matches.
Proxy routes traffic through a proxy; Direct connects directly; Config applies the rules in the selected configuration. Scene involves scene-based settings, so check the active scene rather than treating it as a fixed power-saving mode. The traffic retained by the system and the scope of specific features depend on the current client and system behavior.
Choosing between On Demand, an always-on connection, and manual connections
Here, an always-on connection means leaving the connection enabled in Home—not keeping the app open on screen. On Demand doesn’t guarantee less connection time: if its conditions are met on the networks you use every day, it may behave much like an always-on connection.
On Demand with specific conditions
RecommendedEnable triggers only for network conditions where automatic connection is genuinely needed, then check what happens when you leave those conditions. This works well when your requirements are clear and you’re willing to test a network switch. It doesn’t guarantee a specific battery saving.
Best for: connection needs tied to specific network conditions
Keep the connection active
Leave the connection enabled in Home and let the selected rules handle traffic. This reduces the need to switch it on and off manually, but ongoing traffic, retries, and network quality still affect battery use. Connection time alone isn’t enough to judge which option is better.
Best for: all-day connectivity with fewer manual steps
Disable automatic triggers and connect manually
Turn off On Demand, enable the connection in Home when needed, and switch it off when finished. This gives you clear boundaries and makes comparisons easier, but it’s easy to forget to reconnect and leave later requests using the network without the tunnel.
Best for: short sessions and troubleshooting unexpected reconnects
First decide when it’s okay to disconnect
List the network conditions that require a connection and those where disconnecting is acceptable, then configure On Demand. If you need a connection on every network you use daily, focus first on traffic and reconnects instead of adding unnecessary switching just because the feature is called “On Demand.”
Setup: change one trigger condition at a time
Before making changes, save your current configuration and note the server selected in Home and the Global Routing setting. Available options in On Demand may vary by system and client. The steps below use Settings → On Demand and refer to the network conditions actually shown on your device; they don’t assume options that may not be available.
-
Record the current settings
Open Home and note the connection status, selected server, and Global Routing setting. If you use Config, also record the currently selected configuration file so its rules don’t change midway through the test.
-
Disable automatic triggers
Go to Settings → On Demand and disable automatic triggers first. Then return to Home and disconnect. Check whether later network requests turn the connection back on. This gives you a repeatable baseline for manual control.
-
Set one condition
Return to Settings → On Demand and use the network conditions available on the page to choose where automatic connection is needed. If your page supports Wi-Fi name conditions, check each name carefully; networks with similar names aren’t necessarily the same network.
-
Test network switching
In an environment where testing is permitted, switch from Wi-Fi to cellular and then back to Wi-Fi. After each switch, check the connection status in Home and visit the same test page. Record any repeated reconnects or interruptions.
-
Check what happens when the screen is locked
On the same network, lock the screen for a fixed period, then unlock it and check the connection status. Locking the screen doesn’t necessarily disconnect the tunnel. If the result isn’t what you expected, review the trigger conditions first; don’t change protocols and rules at the same time.
If the connection comes back on just after you turn it off, go to Settings → On Demand and check whether it’s still enabled. Tapping the connection switch in Home repeatedly only changes the current state; it doesn’t remove the automatic trigger conditions.
Compare battery use: measure overall change over a fixed period
There’s no single battery-saving percentage that applies to every device. Battery health, signal, temperature, and app traffic all affect the result. The 30-minute period below is simply a convenient test duration, not official performance data. If the battery indicator doesn’t show enough detail, extend the test and repeat it. Don’t use the results to estimate precise hourly battery use.
| Test group | Connection settings | Keep consistent | What to record |
|---|---|---|---|
| A: Disconnected manually | On Demand off; connection off in Home | Same network and location; screen locked for 30 minutes | Battery level at start and end, signal changes, background downloads |
| B: Always connected | On Demand off; connection on in Home | Same server and Config; screen locked for 30 minutes | Battery level at start and end, disconnects, unexpected traffic |
| C: On Demand | Enable a verified On Demand condition | Use the same server and rules as in group B | Battery level at start and end, actual connection status, number of triggers |
After disconnecting in group A, some apps may not complete their usual requests, so they use less traffic. That means the difference between A and B can’t all be attributed to Shadowrocket’s own overhead. More importantly, check whether groups B and C completed the same tasks, and whether C actually reduced unnecessary connections rather than causing apps to fail and retry repeatedly.
- Before testing, pause large downloads, system updates, and photo syncing, or make sure each group performs the same tasks. Don’t run bulk latency tests during the test.
- Repeat the test on Wi-Fi and cellular separately. Don’t combine results from different signal conditions.
- If the device gets warm, note whether it was charging, navigating, or streaming video at the time. Looking only at an app’s battery share can hide these concurrent workloads.
- Look for repeatable patterns, such as “repeated reconnects after switching to cellular,” rather than using a one-time 1% difference as proof that a setting saves battery.
Prioritize reconnect issues before changing protocols
If extra battery drain consistently coincides with repeated connections after switching networks, first adjust the trigger conditions and check network stability. Compare other settings only after the connection is stable and the tasks are consistent.
Rules, protocols, and subscriptions: keep other variables constant
Rules in Config determine the route used for each request. DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches IP ranges, GEOIP matches results from the GeoIP database, and FINAL handles requests that didn’t match earlier rules. Rules are generally evaluated from top to bottom. Moving an overly broad proxy rule higher up may change how traffic is routed, but you can’t assume that changing one rule will reduce battery use by a specific amount.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,DIRECT
This example explains syntax and order only; it isn’t a complete configuration. PROXY must match a policy name available in your configuration. 192.168.0.0/16 covers one private network range, not every local network address. Don’t overwrite your existing configuration just to test battery use. First check whether the actual destination matches the rule you expect.
- Keep the protocol unchanged: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard have different settings and transport behavior. There’s no universal battery-use ranking based on protocol names, and you shouldn’t swap one Type for another while keeping the same fields.
- Don’t change keepalives blindly: If your provider’s settings include keepalives, don’t remove them just to reduce request frequency. An interval that doesn’t suit your network may cause more connection failures and handshakes instead.
- Test subscriptions separately: Get your subscription link from your service provider. Importing or updating it is separate from On Demand. Avoid repeated updates during battery tests, then check for changes after the test is complete.
- Check whether direct connections work: Direct changes how traffic is routed; it doesn’t guarantee that a destination is reachable on your current network. Failed direct connections can cause apps to retry, undermining the expectation that turning off the proxy will save battery.
FAQ: disconnecting, screen lock, and background activity
Why does it reconnect right after I turn it off?
First, go to Settings → On Demand and disable automatic triggers. Then return to Home, turn off the connection, and observe what happens. If it still turns back on, check the VPN configuration currently in use by the system and any device management policies. Don’t repeatedly delete and recreate the configuration instead of identifying the cause.
The VPN indicator is still showing after I lock the screen. Does that mean it’s using a lot of battery?
The VPN indicator means a connection is active; it doesn’t mean large amounts of data are continuously being transferred. Use the fixed-period method above to check overall battery use and background tasks while the screen is locked. If you see unusual drain, check downloads, syncing, and repeated reconnects before comparing connection settings.
Will force-closing the app stop it completely?
Don’t rely on closing the app from the app switcher as a way to disconnect. To stop the connection, first disable automatic triggers in Settings → On Demand, then turn off the connection in Home and check the system connection status. This distinguishes closing the app from stopping the tunnel.
Why didn’t On Demand improve battery life?
First check whether the trigger conditions are met all day, then compare the actual connection status in groups B and C. If both stayed connected and handled the same traffic, little or no difference is normal. If group C repeatedly reconnects, narrow the range of trigger conditions before testing again.