Desktop pick / Multiple cores
v2rayN
A good fit for starting with a desktop system proxy or managing multiple subscription groups in one place. On first use, import a subscription, make sure its configurations appear in the list, and select one. Enable the system proxy, then test the connection in an app that uses the system proxy settings. This helps determine whether the configuration is failing or the app is bypassing the proxy.
To route traffic selectively, review the rule order and matching outbound settings in the GUI. If only one app bypasses the system proxy, check whether it has its own proxy settings before enabling TUN. TUN changes how traffic enters the client; it cannot add support for protocols or transport options the core does not support.
Android pick / Xray
v2rayNG
A good fit for importing subscriptions or share links on Android, and for configurations that specifically rely on Xray features. After adding a subscription URL, update its group, then select a working configuration from the list. A successful import only means the client read the data; the connection also depends on the configuration fields, remote server, and current network.
Approve Android VPN permission when connecting for the first time. If only certain apps fail, check the per-app proxy list and whether the selected mode includes or excludes those apps, then review the routing mode. If another app using the system VPN interface is running, check which client currently handles traffic before switching; a permission conflict can look like a subscription problem.
Android alternative / v2fly
v2flyNG
Best suited to existing V2Fly configurations or comparisons with other v2fly environments. Before switching, keep the subscription groups, routing rules, and per-app settings from the original client. After importing the subscription again, test a known-working configuration first, then restore settings one at a time. Importing a subscription does not migrate the full setup.
Both Android clients can manage subscriptions, but being able to import a share link does not mean the core can run every option in it. Avoid moving configurations with Xray-specific security layers or flow-control fields directly to v2flyNG. When troubleshooting, check the protocol, transport, and security layer first, then see whether the logs show a parse error or a timeout after the connection attempt.