Download the App and Import a Subscription

Start by choosing an Android app on our download page, then import the Clash subscription provided by your service provider. The app runs the proxy core and manages connections; the subscription supplies nodes, proxy groups, and rules. Installing the app alone does not provide working nodes. Follow the quick-start guide for detailed instructions.

  1. Choose an installer that matches your device's architecture. Most recent Android phones use ARM64. Check older devices' architecture rather than relying on the Android version alone.
  2. In the app, open the “Configuration” or “Profiles” page and look for an option such as Add Configuration or Import from URL. Paste the subscription URL and download it. Button names vary by app.
  3. Select the configuration you just imported, choose an available node in the proxy group settings, select Rule mode, then tap Start.
  4. Allow the system's VPN connection request. Check the connection status in both the app and Android settings, then test a website that should use the proxy.

Clash for Android is no longer maintained. For modern Clash Meta (mihomo)-based apps, check the minimum Android version and subscription compatibility notes. Battery settings can improve background reliability, but they cannot fix an expired subscription, a faulty node, or incompatible configuration fields.

VPN Permission and Connection Status

The First System Connection Prompt

Android's VpnService is the system mechanism apps use to create a local VPN interface. The app typically receives IP traffic from selected apps through this virtual interface, then passes it to the proxy core for rule-based handling. “VPN” here describes how Android routes traffic; it does not mean every connection goes to the same remote VPN server.

The first time you tap Start, Android asks whether the app can set up a VPN connection and explains that it may monitor network traffic. Check the app name in the prompt before confirming. If you cancel, your configuration and node list may still appear normal, but no VPN interface is created and other apps' traffic will not pass through the client.

  • Permission prompt fails: Close floating windows, screen filters, and apps that overlay other apps, then try again. Some systems block sensitive permissions while the screen is covered.
  • Permission requested again: You may need to confirm again after reinstalling the app, clearing its data, or switching VPN apps. You do not need to reimport your subscription each time.
  • Company-managed devices: Work profiles and device management policies may restrict VPN use. Ask your administrator to confirm the required permissions; battery exemptions cannot override management policies.

VPN Conflicts Within the Same Android User

Android usually allows only one app at a time to use the VPN interface within the same user or profile. Starting another VPN, firewall, or ad blocker that uses a local VPN may replace Clash's connection. Disable the other app's VPN feature and test Clash again. Also check network access separately for cloned apps and work profiles.

After starting the connection, check the system status bar or the VPN page in Settings. A key icon confirms that Android has registered a VPN, but not that the node is working. Also check the app logs, selected proxy group, and whether a webpage actually loads.

Battery Optimization and Background Permissions

There is no single “battery whitelist” setting on every phone. Check four separate controls: battery optimization, manufacturer background limits, auto-start, and locking the app in Recent apps. Adjust these settings only for the client you use; you do not need to disable battery management system-wide.

Setting What it does What it can't do
Set battery usage to Unrestricted Loosens background limits, reducing the chance the app will be delayed or stopped when the screen is off Does not guarantee a continuous network connection; Android and manufacturer policies still apply
Allow background activity Lets the app keep running when it is not on screen Cannot prevent force-stopping or termination under severe memory pressure
Allow auto-start Lets the app start after certain system events The client must also support starting at boot or restoring the connection
Lock in Recent apps Reduces the chance that a “Clear all” action will close the app Locking the app does not guarantee the process will never be terminated

Notification Permissions on Android 13 and 14

Starting with Android 13, regular notifications require runtime permission. Allow notifications from the client so you can check service status, stop the connection, and spot errors from the notification shade. Denying notification permission does not always prevent a foreground service from starting; Android may still show the service while the app is active. A missing notification alone does not mean the process has exited.

Android 14 places additional restrictions on foreground service types and launch conditions. If an older client reports that a foreground service failed to start, check app compatibility and logs first. Toggling battery settings repeatedly will not fix an app that has not been updated for newer system APIs.

Where to Find Settings by Manufacturer

These are examples of menu paths on common Android versions. Menus vary by device model, region, and software update. If you can't find an exact match, long-press the app icon, open App info, and search for terms such as “battery,” “background,” or “start.” Version numbers help identify menu locations; the settings are not limited to these versions.

Pixel and Stock-Like Android 14

  • Go to Settings → Apps → See all apps → select the client → App battery usage. Check options such as “Allow background usage” and “Unrestricted”; exact labels vary by system build.
  • If your system has a separate battery optimization list, search Settings for “battery optimization,” switch to all apps, find the client, and select “Don't optimize” if needed.
  • Turn off global Battery Saver while testing. Stock Android usually has no manufacturer-style auto-start switch, so you do not need to install an extra management app for this.

Xiaomi MIUI 14 and HyperOS 2

  • A common path is Settings → Apps → Manage apps → select the client → Battery saver → No restrictions. Some HyperOS versions put battery options on the App info page.
  • Go to Settings → Apps → Permissions and look for “Autostart” or “Background autostart.” Allow it for the client. Some devices have this switch directly in the app details.
  • In Recent apps, long-press the client's card and tap the lock icon. If you use the system cleaner, check whether it has a separate automatic cleanup rule.

“No restrictions” and locking the app in Recent apps solve different problems. Locking the card while leaving strict battery restrictions in place may still result in a disconnect after a long screen-off period. After changing settings, reopen the client, connect once, and repeat your test.

OPPO ColorOS 14, realme UI 5, and Related OnePlus Systems

  • Long-press the client icon → App info → Battery usage or Power management. Check that “Allow background activity” is enabled.
  • Look for the “Auto-launch” permission in App info or the app management page in Phone Manager. Enable it only if your software version offers it. “Associated launch” is not required for every client.
  • The Recent apps menu usually has a “Lock” option. Super Power Saving mode may use a separate app allowlist, so the regular battery exemption may not apply.

vivo OriginOS 4 and iQOO

  • Go to Settings → Battery → Background power consumption management, find the client, and choose an option that relaxes restrictions, such as “Allow high background power consumption.”
  • Go to Settings → Apps and permissions → Permission management and check “Autostart.” On some versions, you can also find it in i Manager.
  • Open Recent apps and lock the app from its card menu. Check whether scheduled cleanup or overnight battery-saving settings impose additional restrictions.

Huawei EMUI 12 and Versions That Support Android Apps

A common path is Settings → Apps & services → App launch management. Turn off automatic management for the client, then check the options for auto-launch, secondary launch, and background activity. Whether secondary launch is needed depends on the app; the key is allowing normal background activity. On systems with a different app ecosystem, first confirm that the Android client can be installed. Compatibility cannot be determined from the brand name alone.

Samsung One UI 6.1

  • Go to Settings → Apps → select the client → Battery → Unrestricted.
  • Go to Settings → Battery → Background usage limits. Check whether the client is in Sleeping apps or Deep sleeping apps, and remove it if it is.
  • If needed, check the “Never auto sleeping apps” list. Some versions do not offer a separate add option for apps already set to Unrestricted.

How to Retest Screen-Off Disconnects

After adjusting settings, distinguish between a terminated process and a running process with no usable network. If the process was terminated, the VPN status usually disappears and you'll need to start the app again. If the process is still running, the VPN icon may remain while nodes time out, DNS fails, or connections stall. The two cases require different fixes.

  1. Establish a baseline: Connect to the same node while the app is in the foreground and confirm that a webpage loads. Note the client name and version, Android version, and network type. Don't change the subscription during testing.
  2. Short screen-off test: Stay on Wi-Fi, unplug the charger, and turn off the screen for 10 minutes. After waking the phone, check the VPN status and service notification before visiting the same website.
  3. Longer test: If the short test passes, try 30 minutes with the screen off. Note when the issue occurs and look in the logs for VPN stops, connection timeouts, or DNS errors.
  4. Test network switching separately: With the screen on, switch from Wi-Fi to mobile data and wait about 30 seconds to see whether the connection recovers. Don't mix network-switching tests with background termination tests.
  5. Change one setting at a time: Adjust the battery policy first, then auto-start or the Recent apps lock. Repeat the same test conditions each time so you can identify what made a difference.

These are suggested retest intervals, not measured battery-life figures or guarantees that an app will stay active on a particular device. Android Doze depends on whether the device is stationary, whether it is charging, and other system policies. Passing a 10-minute test does not prove that the connection will stay stable all night.

A proxy latency test only shows that a particular test request was reachable at that moment. Web access also depends on rule matching, DNS, IPv6, and the destination service. If only one app fails, check whether it is excluded in the client's per-app proxy list before assuming the entire VPN connection is down.

Always-On VPN and Startup After Reboot

Android's “Always-on VPN” and an app's auto-start option are separate features. On supported devices, go to Settings → Network & internet → VPN, tap the settings icon next to the client, and look for “Always-on VPN.” Some manufacturers require you to search Settings for “VPN,” and not all clients support this feature.

Always-on VPN asks Android to keep the selected VPN active or restart it where possible. It does not guarantee that a node is usable or renew an expired subscription. An app's own startup option depends on its implementation, system broadcasts, and the manufacturer's auto-start permissions. Reconnection after a reboot may also depend on the first unlock and how the app stores its configuration, so test it by restarting the device.

  • Make sure manual startup is reliable before enabling the client's startup-on-boot feature.
  • After rebooting and unlocking the device for the first time, check the VPN status, active configuration, and proxy group. Don't rely on whether the app simply appears in the background.
  • If you want to use Always-on VPN, first confirm that the client supports it, then check whether the connection recovers after a disconnect.

Common Questions and Troubleshooting

The key icon appears after granting permission, but webpages still won't load. Why?

First check that a valid configuration is selected and the proxy group has an available node. Then review the logs for DNS resolution failures or connection timeouts. VPN permission only creates a local interface; it does not verify your provider account, node, or proxy rules. If needed, temporarily test another known-working node for comparison, then switch back to Rule mode.

Will mixed port 7890 fix Android screen-off disconnects?

No. mixed-port: 7890 is a common example of an HTTP and SOCKS5 proxy listener setting; use the port specified in your client configuration. It does not control Android background activity or affect VpnService permission. For normal use on the phone itself, you do not need to enable allow-lan to keep the app active. Allowing LAN access also expands which network interfaces can reach the listener.

Can the app restart automatically after I tap “Force stop” even if it's locked in Recent apps?

Locking an app in Recent apps does not protect it from Force stop. Force stop in Android's App info terminates the app and prevents it from starting automatically; you'll generally need to open it yourself again. To resume, open the client and start it manually, then test boot or network-switch recovery.

What should I do if the battery drains faster after adding an exemption?

Compare battery usage over the same period in Android settings, and distinguish actual network traffic from idle background use. Check for frequent automatic speed tests, verbose logging, or repeated reconnect attempts. Reduce test frequency to suit your needs, and stop the service when you don't need a proxy. Avoid masking connection problems by restarting on a fixed interval of a few minutes; repeated wakeups and reconnects use more power.

If the issue persists, include the client version, Android version, manufacturer software version, logs from before and after the problem, and steps to reproduce it when requesting help. Remove subscription URLs, node credentials, and personal network details before sharing logs. Troubleshooting in this order—configuration, VPN connection, background permissions, then network switching and DNS—usually pinpoints the cause faster than reinstalling repeatedly.