Client Reviews
A look at what each client does well and where it has limitations in everyday use.
v2rayN: Desktop Subscription Management and Routing
v2rayN is a good fit for managing multiple subscriptions on a desktop. Keep each source in its own subscription group so you can find nodes by source after updating. Configure routing in the graphical interface: choose which destinations should connect directly, then set where other traffic goes. Before changing rules, note their current order and the default outbound. When rules overlap, a broad rule near the top may match first and prevent a later, domain-specific rule from taking effect. See the routing configuration reference for rule fields and order.
For everyday use with browsers and other apps that follow the system proxy, start with system proxy mode. If an app doesn't use the system proxy, consider TUN and check virtual network adapter permissions and conflicts with other network tools. After enabling TUN, test both internet access in the apps you need and access to local network devices. Test each mode separately so you can pinpoint issues.
v2rayNG: Android Subscription Import and Xray Configuration
v2rayNG is a good place to start with an Xray-compatible subscription. Add the subscription URL, update it, select a node, and connect. The first time you connect, Android will ask for permission to establish a VPN. Granting permission only allows the client to route traffic; it doesn't confirm that the server is reachable. Test with the apps you actually use. If only one app is affected, check whether per-app proxy settings include it.
When you use the same subscription on desktop and Android, both devices share the node source, but system proxy, per-app scope, and routing options are stored locally on each device. If the desktop works but Android doesn't, select the same node on both and test the phone over Wi-Fi and mobile data separately. Matching nodes make it easier to tell whether the issue comes from the network or Android's local settings. See the Android setup guide for steps.
v2flyNG: Android Option for V2Fly Compatibility
Consider v2flyNG when your server is configured for V2Fly or your configuration provider specifically requires the V2Fly core. Subscription import is similar in both Android clients, but their cores don't support exactly the same combinations of transport and security settings. For example, nodes that rely on REALITY should be matched to an Xray-compatible client. Seeing a node name in the list doesn't mean every setting will work.
When switching clients, keep the existing settings and first test a few nodes known to be compatible. Then check routing and per-app scope. If both clients are installed, disconnect the current one before starting the other to avoid mistaking an Android VPN service handoff for a core issue. Long-term use on older devices depends on the Android versions and processor architectures supported by the current installer, as well as actual background behavior—not the core's name.