AeroNet: measure the connection beyond download speed

Suppose a video call stutters on a connection that recently reported a healthy download figure. The number may still have been right. It answered one question, how much data could move in one direction during a short test, while the call may have depended on something else: how quickly packets made the round trip, how steady that delay stayed, or whether the outgoing direction had enough room. Download speed alone does not settle which.

Four measurements, read together

AeroNet is an Android speed test from VMCSoft Digital, published on Google Play under the developer name VMCSOFT. A test reports latency, jitter, download speed and upload speed, shows progress while it runs, and saves the result in an on-device history with its metrics and test settings. There is no account to create. The app asks only for Internet access and network state, as its privacy policy lists.

The four numbers describe different things. Latency is the round-trip delay to the test endpoint. Jitter is how much that delay varies from one sample to the next, which matters for voice, video and anything interactive. Download and upload are throughput in each direction. Outgoing throughput matters for calls, backups and screen sharing when there is not enough of it, so it deserves its own reading rather than an assumption either way. A connection can score well on one and poorly on another, which is why AeroNet shows them side by side rather than reducing a connection to a headline figure.

What a result is evidence of

A speed test measures the path between your device and the test endpoint at that moment, on that network, with whatever else the phone was doing. It is not a guarantee of how every app will perform, since each service has its own servers and route. It does not speed anything up. A low throughput reading, or any result that looks wrong, is a reason to look further, not conclusive proof that a provider is throttling, and a result is not an independent audit of the bandwidth written in a contract. High jitter can degrade real-time sessions, but AeroNet does not determine the cause.

Two practical points follow from how the app works. First, AeroNet is not local-only. It contacts the AeroNet backend to coordinate each test, which the policy says may include requesting temporary download URLs and opening WebSocket connections where needed, and the test traffic itself moves to and from the test infrastructure. The policy notes that backend systems may process temporary test traffic and technical metadata such as request timing and connection state to operate and troubleshoot the service. The history stays on your device and is separate from that metadata; the test itself is a network event. Second, a real test moves real data in both directions. On a metered cellular plan, choose when and how often to run one.

Compare like with like

A single reading tells you little. Record the conditions for each test, repeat under the same conditions where you can, and change one factor at a time. A slow evening on home Wi-Fi next to a quick morning on cellular changes the network and the time at once, so it does not show which network is better or why. When you need to talk to a provider or choose between two networks, bring the set of results and their conditions as context, not as proof of throttling or of contracted bandwidth, rather than the best number you saw once. The Play listing has the current release, and the privacy policy describes what the backend may process.