Measurement Data¶

The test results are structured as an object. The actual results depend on the type of test being run. In the following, we will describe the results for the different tests.

General Fields¶

The results from our mobile SDK are aligned with the results you get from our Surfmeter Automator solution. They are only slightly different in a few minor aspects due to the different environments (mobile vs. desktop).

For a general overview of the data structure, see our reference.

Here are additional fields that are specific to the mobile SDK:

Connection and Location Traces¶

Android and iOS use the same top-level trace names and common field names. Both collectors run only for the duration of a test.

The SDK records an initial connection snapshot when the operating system reports the network state. It adds another entry whenever an available connection value changes. Timestamp changes alone do not create duplicate entries.

Location updates are separate entries in geolocation_trace. Missing permissions or unavailable location data do not fail the test.

The listener-facing report has this shape:

{
  "connection_detail_trace": [
    {
      "type": "WifiConnectionDetail",
      "is_internet_reachable": true,
      "is_connection_expensive": false,
      "ip_address": "192.0.2.14",
      "subnet": 24,
      "ssid": "Example Lab",
      "bssid": "00:11:22:33:44:55",
      "client_time": "2026-09-09T12:00:00.000Z",
      "client_time_skewed": "2026-09-09T12:00:00.000Z"
    }
  ],
  "geolocation_trace": [
    {
      "type": "MeasurementGeolocation",
      "latitude": 48.2085,
      "longitude": 16.3721,
      "accuracy": 4.8,
      "speed": 0.2,
      "client_time": "2026-09-09T12:00:01.000Z",
      "client_time_skewed": "2026-09-09T12:00:01.000Z"
    }
  ]
}

The upload layer converts these arrays to the nested attributes expected by the Surfmeter server. Apps should use the listener-facing names shown above.

geolocation_trace¶

Each entry describes one location update.

Android location detail depends on ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION. See Android permissions.

iOS records only precise locations. Denied access, disabled Location Services, reduced accuracy, or the absence of an update produces an empty trace and does not fail the test. See Measurement Context and Privacy on iOS.

connection_detail_trace¶

These fields are shared across Android and iOS where the operating system makes them available:

iOS Fields and Limitations¶

The iOS SDK can add these fields:

iOS does not provide public App Store APIs for Wi-Fi RSSI, frequency, or link speed, or for cellular signal strength and cell identity. These Android fields are omitted instead of estimated. See Measurement Context and Privacy on iOS for the complete permission and disclosure requirements.

Android Basic Network Fields¶

Android Wi-Fi Fields¶

Android Mobile Network Fields¶

GSM details:

LTE details:

5G NR details:

Android can also provide WCDMA, CDMA, and TDSCDMA fields. See the general connection-data reference for the complete radio-field matrix.

Diagnostics¶

Further, there is a diagnostics: object containing diagnostic information – but this is experimental and may be changed in the future. It currently contains the following:

• test_settings: Object with test-specific settings
• client_version: Version of the Quality SDK used (same as above)

ExoPlayerQualityTest¶

For the statistic values, see here.

VideoQualityTest¶

For the statistic values, see here.

WebQualityTest¶

For the statistic values, see here.