Why proxy mode still confuses people on phones
Search traffic around Clash for Android, rule mode, global mode, and proxy mode switch usually comes from the same scenario: the APK is installed, the subscription imports, and the VPN key icon appears—yet a banking app still loads like nothing happened, or a browser suddenly fans all traffic through a node on another continent. On desktop you might blame environment variables; on Android the mental model collapses into “maybe I tapped the wrong thing.”
This article stays in the lane of the official-style Clash for Android experience—the client many shorthand as CFA when comparing with cross-platform forks such as FlClash. The goal is practical: you learn how the dashboard’s Rule, Global, and Direct switches interact with policy groups, what each mode actually does to traffic that Clash manages, and how to confirm results before you escalate into rewriting remote YAML on a phone keyboard.
Clash for Android in one paragraph
Clash for Android wraps a Clash-class core inside Android’s VPN service so applications that respect the OS tunnel can follow programmable rules. Unlike a minimalist one-region VPN button, it expects a structured profile: proxies, proxy-groups, rules, DNS scaffolding, and optionally external rule providers that your aggregator maintains. The UI exposes a subset of that power—enough for day-to-day mode changes and node picking—without turning every passenger on the bus into a YAML engineer.
Keep expectations honest: you still need a legitimate subscription, you still need to comply with local law and network policy, and you still need to maintain battery and permission hygiene. The sections below are about mechanics, not bypass recipes.
Rule, Global, and Direct without mythology
Think of the three headline modes as different answers to the question, “How should Clash choose an outbound for traffic it is allowed to handle?”
- Rule mode is the everyday default for split routing. Clash walks the ordered rule list—DOMAIN, IP-CIDR, GEOIP, MATCH, and friends—until something hits, then sends the flow through the outbound or policy group your YAML names. Domestic streaming, corporate SaaS, and random telemetry domains can coexist without you tapping a switch for each app.
- Global mode is brute-force simplification: eligible traffic that Clash intercepts tends to travel through whatever your profile defines as the global proxy path, which is useful when you want every allowed flow on one chain while you debug or travel on hostile Wi-Fi. It is not “more secure” automatically—it is just less discriminating.
- Direct mode tells Clash to skip proxy outbounds for the governed flows, sending them toward your normal ISP path subject to whatever else your profile still enforces (DNS, fake-ip quirks, or blocking rules can still matter). People reach for it when they need to isolate whether slowness is the node or the rule ladder.
Where you actually tap to change modes
Exact iconography drifts between versions, yet the navigation pattern is stable. After launch, you usually land on a dashboard or home surface where the prominent chip or dropdown lists Rule, Global, and Direct. Tap the mode you want; the change should apply without re-importing the subscription, though some vendor policies also persist the selection per-profile.
If you cannot find the selector, check whether you are still in the profile editor or log screen—many builds tuck the mode switch near the summary card that also shows active node latency. When in doubt, pull the UI downward to refresh state after toggling.
Step-by-step: connect first, then touch modes
Modes only matter once Clash owns a working data path. Use this ordered checklist before declaring “Global broke my LAN printer.”
-
Activate the right profile
Open Profiles, ensure the subscription finished parsing with real nodes, and highlight the configuration you intend to exercise. A stale or empty profile makes every downstream switch meaningless. -
Approve VPN permission once per major change
Android treats Clash as a VPN participant. Denying permission yields toggles that look alive while no tunnel exists. If you revoked access in system settings, re-authorize before testing Rule splits. -
Flip the master connect switch
Wait until the status indicates running service and the key icon shows. If the icon never appears, fix fetch errors or conflicting VPN apps first—mode tweaks will not revive a dead session. -
Set Rule for normal browsing
Return to the dashboard, choose Rule, then load a site you expect to proxy plus a domestic site you expect to skip. Misexpectations here usually mean provider GEOIP lists or custom rules—not CFA bugs. -
Escalate to Global only for diagnosis or travel extremes
Switch to Global briefly. If performance suddenly stabilizes, suspect an over-broad DIRECT rule, DNS misalignment, or a group that keeps landing on weak nodes. Log the evidence, then revert to Rule once you know why. -
Use Direct to confirm baseline ISP reachability
Pick Direct, retest the failing host, then flip back. If Direct still fails, you are often looking at captive portals, IPv6-only networks, or provider downtime—not outbound selection.
Policy groups are not a substitute for Rule mode
Newcomers conflate the dashboard mode with the proxy group list. They relate, but they solve different layers:
- Mode (Rule / Global / Direct) decides how aggressively Clash applies global rule evaluation versus forcing a single outbound path for tunneled traffic.
- Proxy groups (Select, UrlTest, Fallback, Relay chains, and provider-fed bundles, depending on core features) answer, “Which concrete hop or auto-tested cluster fulfills this policy label?”
Typical workflow: leave Rule enabled, open the Proxies tab, expand the group your subscription author labeled for manual switching—often named after regions or tiers—and tap the node you want. UrlTest groups rotate automatically; Select groups honor your finger. If a domain still resolves to DIRECT in logs, changing Selected node inside a downstream group will not magically proxy it until rules send that domain through a PROXY outbound.
When Android itself ignores what Clash chose
Even perfect Rule mode YAML cannot override an app that explicitly bypasses VPN interfaces or ships its own encrypted DNS. Symptoms look like “Clash says connected but this one messenger never updates.” Your triage order:
- Read connection logs while reproducing the issue; confirm whether the traffic appears at all.
- Check whether the app offers an internal “use proxy” toggle or pins HTTP/3 through its own resolver.
- Rule out a second VPN profile, work containers, or OEM “dual app” sandboxes that split networking stacks.
This is why guides that only say “turn on Global” frustrate power users: Global still operates within Android’s VPN contract. If the app never enters the tunnel, you address platform behavior, not Clash semantics.
Battery optimisations that silently drop Rule mode sessions
Some vendors kill the VPN service the moment the screen locks, which feels like modes randomly revert or rules stop applying mid-scroll. Exempt Clash for Android from aggressive background restrictions, disable conflicting power savers during testing, and remember cheap public Wi-Fi setups often block long-lived UDP or QUIC flows that Mihomo-class cores rely on for probing.
Sanity checks that do not require a laptop
Use lightweight evidence rather than vibes:
- IP check pages from the phone browser while on Rule versus Global to see whether WAN identity matches expectation—but interpret cautiously if DNS or split intranet rules interfere.
- In-app connection tables showing policy names; they should align with intuitive buckets (domestic DIRECT, foreign PROXY).
- Ping or HTTP tests from inside Clash if your build exposes them, correlating each attempt with the log line that cites the winning rule.
Troubleshooting patterns that map to modes
Domestic sites slow while Global feels fast
Your GEOIP or domain rules might mislabel traffic, or the default proxy group routes domestic CDN through transcontinental nodes. Stay on Rule, fix grouping, or ask the provider for a profile tuned to your region—do not leave Global on permanently just because it masks mis-tuning.
Everything breaks in Rule, works briefly in Global, fine on Direct
Suspect DNS loops, fake-ip mismatches, or a MATCH rule that points to a dead group. Inspect logs, rotate DNS mode only with notes, and compare against a desktop import of the same subscription.
Only one proxy group misbehaves
Focus inside that group’s Select or UrlTest membership—swap nodes, confirm provider backends, and ensure upstream renamed outbounds did not desync from your local overrides.
FAQ
Should beginners live in Global mode? Only short term. Global hides misconfigured splits and costs bandwidth. Learn how Rule mode expresses intent, then rely on provider-maintained lists.
Does Clash for Android mirror every desktop Clash Verge toggle? No. Phones prioritize VPN ergonomics and battery. Advanced features may appear later or stay desktop-only; match expectations to the build you run.
Can I automate mode switches? Some automation frameworks exist around Tasker-like tooling or remote controllers, but they assume you understand the security implications of exposing the control plane. Default advice: manual switches unless you own the automation stack end to end.
Choosing clarity over opaque VPN knobs
Compared with all-in-one VPN apps that hide routing behind a map pin, split routing clients demand a bit more literacy—but they repay you with predictable behavior once Rule mode and policy groups click. Many minimalist tunnel products either lack granular domain control entirely or dump you into a single exit with no visibility into why latency spikes, which makes debugging on Android feel like guesswork whenever a carrier or café Wi-Fi changes TLS inspection policies.
Clash for Android inherits the same structured rule vocabulary that desktop Mihomo ecosystems use, so the jump from “tap Global because Rule feels scary” to intentional splits is mostly about reading logs and respecting how Android delivers VPN semantics. When your profile is sane, the dashboard toggles finally feel like precision tools instead of mystery meat.
If you want a single curated place to confirm you are on an up-to-date build before fine-tuning modes, open our client download page alongside this workflow and keep your install source consistent across handsets.