Is your feature request related to a problem? Please describe.
Yes, but they are more about usability and personal preference than critical bugs.
-
Regarding Tcping: In recent updates (from v2.2.5 onward), the standalone Tcping menu item was removed. As a user, I sometimes face a situation where the "Real Ping" test returns "-1" for many of my configs. In these cases, I cannot tell if the issue is with the config itself (e.g., TLS handshake failure or application-level blocking) or if the server's IP/port is simply unreachable at the network level. The old standalone Tcping was a quick and reliable way to check the basic TCP connectivity to the server. It helped me determine if the problem was on my side (network/ISP) or if the server was completely dead, without having to wait for a full Real Ping test.
-
Regarding the node count in subscription names: I noticed that in recent versions, the number of configurations is automatically displayed next to the subscription name. I want to be clear that this is not a "visual disaster" or a bad feature; it is simply a matter of personal preference. Some users might find it useful, but for me, it adds a bit of visual clutter that I would prefer to hide if possible.
Describe the solution you'd like
- Restore the standalone "Tcping" menu item (or add it as an optional toggle in the settings). This would allow users to quickly perform a basic connectivity check without running the heavier Real Ping test.
- Add a settings toggle (e.g., "Show node count in subscription name") so that users can choose whether to display this information based on their personal preference.
Describe alternatives you've considered
- I considered downgrading to version 2.2.4 to get Tcping back, but that is not a sustainable solution because older versions lack new features and important security updates.
- I also considered using forked versions like MahsaNG, but I believe the official app should ideally support this basic diagnostic functionality.
Additional context
Since the Tcping logic still exists in the codebase as a "pre-check" for the Real Ping test, bringing back the standalone menu item or a simple toggle should not require a huge development effort.
Thank you for taking the time to consider my request and for your continuous work on this great app.
Is your feature request related to a problem? Please describe.
Yes, but they are more about usability and personal preference than critical bugs.
Regarding Tcping: In recent updates (from v2.2.5 onward), the standalone Tcping menu item was removed. As a user, I sometimes face a situation where the "Real Ping" test returns "-1" for many of my configs. In these cases, I cannot tell if the issue is with the config itself (e.g., TLS handshake failure or application-level blocking) or if the server's IP/port is simply unreachable at the network level. The old standalone Tcping was a quick and reliable way to check the basic TCP connectivity to the server. It helped me determine if the problem was on my side (network/ISP) or if the server was completely dead, without having to wait for a full Real Ping test.
Regarding the node count in subscription names: I noticed that in recent versions, the number of configurations is automatically displayed next to the subscription name. I want to be clear that this is not a "visual disaster" or a bad feature; it is simply a matter of personal preference. Some users might find it useful, but for me, it adds a bit of visual clutter that I would prefer to hide if possible.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Since the Tcping logic still exists in the codebase as a "pre-check" for the Real Ping test, bringing back the standalone menu item or a simple toggle should not require a huge development effort.
Thank you for taking the time to consider my request and for your continuous work on this great app.