On Android, choose a client based on the protocols, transports, and security layers used by your most common nodes. If your subscription includes VLESS + REALITY, start by checking v2rayNG. If it only uses VMess + WebSocket + TLS and v2flyNG is working reliably, there’s no need to switch just for a different core. If a profile imports but won’t connect, troubleshoot client parsing, core startup, and the remote handshake separately.
Why V2Fly and Xray Developed Separately
V2Ray originated with Project V. The V2Fly community continues to maintain the V2Ray core, while Xray forked from the V2Ray codebase in 2020 and began developing independently, with features such as XTLS. Their shared early codebase explains why the two cores still have many configuration options with the same names. Later protocol extensions, transport implementations, and config formats, however, do not have to stay in sync.
The client and core are separate layers. On Android, v2rayNG uses Xray, while v2flyNG uses V2Fly. Importing links, managing subscriptions, and requesting Android VPN permissions are client-side tasks. Parsing outbound configs, connecting to remote servers, and applying core routing rules happen at the core layer. The local listening port in desktop v2rayN is not the server port for an Android node: even when both devices use the same subscription, don’t copy the desktop port 10808 into the Android remote port field.
v2rayNG or v2flyNG for Android?
v2rayNG · Xray
RecommendedIf your subscription explicitly provides VLESS + REALITY or requires XTLS Vision, first check that your installed version can parse the corresponding share link and retain its node parameters. You can also test existing VMess nodes individually.
Best for: configurations that use REALITY or require Vision
v2flyNG · V2Fly
If your existing subscription mainly uses VMess with WebSocket and standard TLS, and your current client connects reliably, you can keep using it. Before switching clients, make sure there’s an actual feature you need that’s missing.
Best for: keeping a verified, working VMess subscription
Use the nodes you depend on as your selection criteria
With a mixed subscription, importing dozens of VMess nodes doesn’t mean the one REALITY node you rely on will connect. Check that node’s fields first, then decide whether to migrate the entire subscription.
Don’t treat protocol support lists as speed rankings. A node’s latency and throughput depend on the access network, server load, and transport. To compare two clients, test the same node on both, using the same phone and network, and alternate between clients. Record whether the initial connection succeeds and how pages load in practice. Don’t draw conclusions from one-off latency results against different servers.
Subscription Compatibility: Protocols, Transports, and Security Layers
A subscription URL is a way to retrieve configuration, not a protocol. One URL may return multiple nodes, or different formats depending on the device or request. After updating, open a frequently used node’s edit screen and check its protocol, transport, security layer, and any additional parameters required by that combination.
| Node combination | Client choice | Check after importing |
|---|---|---|
| VMess + WebSocket + TLS | Either client is worth considering | Server port, WebSocket path, Host, and TLS server name |
| VLESS + WebSocket + TLS | Test with v2rayNG first; don’t infer VLESS compatibility from VMess | Check that the transport is still WebSocket and the security layer is still TLS |
| VLESS + REALITY with Vision specified by the node | Use v2rayNG first | Check that the server name, public key, short ID, and flow match the original config |
flow is a VLESS flow-control field, and xtls-rprx-vision is a specific value—not a transport type. REALITY is a security layer option, not another name for VLESS. A share link beginning with vless:// identifies the protocol, but it doesn’t mean you can assume Vision is enabled or change TLS to REALITY. The WebSocket Host is the hostname used in the HTTP request; the TLS server name is used during the handshake. Don’t substitute one for the other just because their names sound similar.
What to migrate when sharing a subscription between desktop and Android
Use the same subscription URL, but check each device’s local settings separately
Desktop: v2rayN
- Open “Settings” → “Parameters Settings” and check the local listening port. Don’t enter a local inbound value as a remote node setting.
- Check whether System Proxy or TUN is enabled, and note the routing rule group in use.
Android: v2rayNG or v2flyNG
- In v2rayNG, open “Subscription group settings” from the sidebar and add the URL. Return to the list and update the subscription from the menu. The menu name may vary by version.
- After updating, manually select a known working node and check VPN permission and per-app proxy settings separately.
Node parameters can sync through the subscription. Check local inbounds, DNS, routing rules, and app lists separately on each device.
A complete core JSON file and a standard subscription are different kinds of migration data. A JSON file may include a desktop-only listening address, rule resource paths, or core-specific fields. Even if both cores recognize outbounds and routing, that doesn’t guarantee the entire file will run as-is. If you only need to migrate nodes, use a subscription or share link explicitly supported by the client. Migrate rules and their corresponding outbound tags individually only when you need to preserve custom routing.
Imported but Won’t Connect? Troubleshoot by Stage
- The list is empty: First check whether the subscription update reported an error and whether the URL is still valid. A failed update happens while fetching or parsing the config; changing a node’s port, transport, or flow won’t fix an empty subscription list.
- Nodes are listed, but startup fails immediately: Open the client log and look for unknown fields, unsupported transports, or config parsing errors. If the node requires REALITY, first check which client and core are actually in use, then confirm the security layer was retained after importing.
- Startup succeeds, but the handshake fails: Check that the server address and port match the original config, then verify the TLS server name or REALITY parameters. For standard TLS nodes, also make sure the device’s date and time are correct. Change one setting at a time; don’t hide a name mismatch by disabling certificate verification.
- Connection test passes, but one app fails: First check whether the app is excluded from per-app proxying. Then check whether routing sent it DIRECT or through the proxy, and which DNS path it used. A successful node test only confirms that the test request got through; it doesn’t mean every app uses the same outbound.