Background activity for Shadowrocket on the Battery screen doesn’t necessarily mean abnormal battery drain. Check the time range, overall battery loss, and network activity before comparing On Demand with manual connections. This guide is for iPhone and iPad users who want to reduce unnecessary connections. After troubleshooting, decide whether to keep automatic connections based on when you actually use them.
Start with the Battery screen: usage share isn’t total battery drain
Open Settings → Battery, choose a time range, then review Shadowrocket’s battery usage and activity. Charts, time ranges, and activity details vary by iOS version. Use the same time range when comparing data; don’t compare a day’s usage share with an hour of battery loss.
The percentage next to an app is its share of attributed battery use during the selected period. It doesn’t show how much battery capacity the app used on its own. For example, if the battery drops from 80% to 70% and Shadowrocket accounts for 20% in the app list, that doesn’t mean it caused the entire device to lose 20 percentage points. This example illustrates how the figures are reported; multiplying the numbers isn’t a substitute for measuring actual energy use.
Background activity means the app or a related network extension did work in the background; duration alone doesn’t show that the CPU was under sustained heavy load. Network requests from other apps may pass through the VPN tunnel, and Battery attribution doesn’t mean one app accounted for all network-related power use. Investigate further only if background activity increases, overall battery drain rises noticeably, and you can reproduce the pattern under comparable conditions.
- Check whether the device was charging during that period. Battery levels before and after charging aren’t a continuous discharge sample.
- Check for video playback, calls, photo syncing, or app updates; these activities change network load.
- Note screen-on time, brightness, and whether you were on Wi-Fi or cellular. Don’t rely on the app ranking alone.
- Watch for weak signals and frequent network switching. Wireless connectivity itself affects overall battery drain.
On Demand controls connection triggers; it doesn’t mean constant data transfer
In Shadowrocket, open Settings → On Demand and check the current toggle and configured trigger conditions. On Demand lets the system manage VPN connections based on conditions. Whether a connection is established depends on those conditions and settings. It doesn’t mean that large amounts of data are always being transferred, nor does the toggle alone tell you how much extra battery will be used.
Once connected, actual power use depends on traffic, protocol processing, reconnects, and network conditions. An idle connection and continuous video streaming create different loads; repeated connections on an unstable network also differ from an idle connection on stable Wi-Fi. When troubleshooting, distinguish between automatic connections triggering too often and ongoing data transfer after connection.
Global Routing and On Demand do two different things. The former controls how requests are handled while connected; the latter determines when a connection is initiated based on conditions. In Global Routing, Config applies the configured rules, while Proxy and Direct set the corresponding routing mode. Scene applies the selected scene. Switching Global Routing to Direct doesn’t disconnect the VPN tunnel or replace manually disconnecting.
- Go to Settings → On Demand and note the existing conditions first, so you can restore them if needed.
- Check whether conditions for frequently used Wi-Fi networks, cellular networks, and domains match your current needs.
- Change one condition at a time. Return to Home to check the connection status, then switch networks to verify the behavior.
- To test fully manual control, turn off On Demand first, then disconnect using the toggle on Home.
Compare under the same conditions: don’t change every setting at once
To find out whether On Demand is related to your battery use, compare two observation periods rather than drawing conclusions from one overnight drain. Start with a 60-minute window: keep your current On Demand settings for the first round, then turn off On Demand and connect manually as needed for the second. Sixty minutes is just a convenient starting point, not a measurement standard. Extend the observation if battery use is too low to compare or the system chart lacks detail.
| Item | On Demand session | Manual connection session |
|---|---|---|
| Connection method | Keep the existing trigger conditions and record automatic connections | Turn off On Demand; connect from Home when needed |
| Network conditions | Use the same location and Wi-Fi, or similar cellular signal strength | Keep conditions as similar as possible; don’t switch networks between sessions |
| Activity and routing | Record the apps used, configuration, and Global Routing setting | Keep the same configuration and routing mode; repeat similar tasks |
| Results | Starting and ending battery levels, screen activity, background activity, and connection issues | Track the same items and note the actual time connected |
If the device is disconnected for most of the second session while the first remains connected throughout, the comparison reflects the difference between two overall usage patterns—not just the On Demand toggle. To isolate automatic triggers, keep connection time and activity load as similar as possible, and separately watch for repeated connections when switching networks.
Takeaway: confirm the difference is repeatable before choosing a long-term setup
If idle periods with a manual disconnect repeatedly show less overall battery drain, consider connecting manually during specific hours. If the difference varies, first rule out signal issues and background syncing. Don’t turn off On Demand just to lower its position in the Battery screen ranking.
When battery drain spikes, troubleshoot in this order: connection, retries, configuration
If battery use suddenly increases, first check for changes in your usage or network conditions, then check connection stability. Don’t start by switching protocols or rebuilding the entire configuration. Use service details provided by your own provider. This guide checks an existing connection and doesn’t provide or recommend connection services.
- Find out what’s triggering reconnections. If the connection comes back shortly after you disconnect from Home, check the conditions under Settings → On Demand. Don’t keep tapping the connection toggle and mistake an automatic connection that meets the configured conditions for a faulty switch.
- Compare Wi-Fi and cellular. Observe connection stability in the same location on each network. If the issue occurs only with a weak cellular signal, record the signal and network changes before adjusting rules.
- Stop repeated tests. After one necessary latency or connection test, return to normal use. Repeated tests generate requests and aren’t suitable for measuring idle battery use.
- Check your existing settings. If the logs show TLS or connection errors, check the address, port, authentication details, and system time. The port must match the server; don’t change every port to 443 just because HTTPS commonly uses it.
- Check for configuration changes. If the issue began after an existing subscription update or a change to Config, check the selected connection and configuration. Keep a copy before making changes, and don’t change routing, protocol, and automatic connection conditions all at once.
Error: NSURLErrorDomain Code=-1001
Cause and next steps: This is an Apple network request timeout error code. If it appears in the logs, the request didn’t complete in time; the code alone doesn’t identify a protocol setting as the cause. First find out which request timed out, retry once on a stable network, and check the destination address and port. If it keeps failing, review the existing service details alongside the surrounding log entries. Avoid repeated retries while monitoring battery use.
Error strings can vary by system version and request type, so there’s no need to look for this code if it isn’t present. Recording the exact error, when it occurred, and the network type is more useful than noting only “lots of background activity.” Before sharing logs, remove subscription URLs, credentials, full service addresses, and other personal information.
Choose based on your routine: keep automation or disconnect manually
There’s no single battery-saving setup that works for everyone. Choose based on how continuously you need a connection, how stable your network is, and whether you’re comfortable managing it manually. If you turn off On Demand and forget to connect, app requests will use the network available to the system at the time. If your workflow depends on a VPN, manual mode requires you to check the connection status.
- Only a few scheduled tasks each day: Connect manually and disconnect from Home when you’re done. Turn off On Demand as well to prevent a condition from reconnecting automatically.
- Frequent use of related services throughout the day: Keep On Demand enabled and focus on checking its trigger conditions and connection stability, rather than repeating the same steps for every short task.
- Frequent switching between Wi-Fi and cellular: Check how the connection behaves before and after switching. If you need a connection only on certain networks, narrow the conditions to match instead of triggering it on every network.
- Mostly idle overnight: Once you’ve confirmed that no background tasks depend on the VPN, try a manual disconnect for comparison. Keep photo syncing, charging status, and network conditions as consistent as possible.
Don’t use unnecessary rule changes as a substitute for managing connections. DOMAIN-SUFFIX, IP-CIDR, GEOIP, and FINAL match and route traffic; they aren’t battery-saving switches. If your current Config meets your needs, leave the rules alone and first reduce unnecessary connection time and failed retries. Don’t assume one protocol will always use less battery based on its name alone.
FAQ: background activity and checks after disconnecting
Is Shadowrocket running at full capacity the whole time the screen is locked?
No. In Settings → Battery, select the relevant period and check the device’s overall battery change alongside activity from other apps. Syncing and network requests can continue after the screen locks; background duration alone doesn’t indicate sustained heavy use. Compare observations on the same network to judge what’s happening.
Why does it reconnect a while after I manually disconnect?
Go to Settings → On Demand and check whether automatic connections are still enabled and what conditions are set. To test a manual disconnect, turn off On Demand first, then disconnect from Home. Switch Wi-Fi or cellular once, then check that the connection hasn’t restarted automatically.
Does switching to Direct count as disconnecting?
No. Direct in Global Routing changes the routing mode; it doesn’t remove the current VPN connection. To confirm that you’re disconnected, check the connection toggle on Home and make sure On Demand hasn’t triggered another connection. Restore your original routing settings after the test.
Why is Shadowrocket still near the top of the Battery screen after I disconnect? Should I reinstall it?
Don’t reinstall yet. The Battery screen keeps historical data for the selected period, and disconnecting doesn’t erase earlier usage. Choose an observation period after disconnecting or wait for a new complete period, then compare overall battery drain. Save your configuration and troubleshooting notes first so you don’t lose useful information.
Keep a record you can review: the selected time range on the system Battery screen, starting and ending battery levels, network type, On Demand status, Global Routing mode, and any relevant logs. Fix repeatable connection issues first, then decide whether to use automatic or manual connections long term. Don’t base the decision on one usage percentage.