When to Consider Skipping TUN Mode

TUN mode isn't the only option. If heat and drain are already noticeably affecting daily use, consider switching to system proxy mode instead (configuring the proxy address individually in the apps or browser that need it), trading some coverage for lower system-level overhead. Under system proxy mode, only apps explicitly configured to use the proxy get routed through it, while everything else is completely unaffected — the total matching and forwarding volume drops considerably.

This trade-off fits scenarios where you only need the proxy in a browser or a handful of apps, the device itself is lower-powered and heat-sensitive, or you're only using it temporarily rather than aiming for full coverage. Conversely, if you need to cover every app on the device (for example, some apps have hardcoded domain checks and break when bypassing the global proxy), TUN mode is still the safer choice — in that case, the battery cost is a cost you have to accept, and effort should go into the rule trimming and whitelisting covered earlier, rather than debating whether to use TUN at all.

A Complete Troubleshooting Workflow

1. Open the system battery usage stats and confirm whether the drain share is actually abnormal (see the diagnostic criteria in the first section).
2. Check whether TUN mode is enabled; try switching to system proxy mode for a day as a comparison and observe the drain difference.
3. Take stock of the currently loaded rule sets and update intervals; trim categories you rarely use and extend the update cycle.
4. Check the probe frequency of automatic latency testing inside policy groups and cut unnecessary scheduled probes.
5. Confirm whether the OEM power-saving setting is reasonable: whitelist it if you need long-term background operation, otherwise keep the system default restrictions.
6. Watch the battery curve over the following day or two to confirm drain has returned to a reasonable range before deciding on further adjustments.

Following this order will usually pinpoint the drain to a specific step rather than vaguely blaming "the proxy software." In most cases, the root cause is an oversized rule set or overly frequent background wake-ups — adjusting these two is usually far more effective than debating whether to use TUN mode.