Presence calibration

This page provides setup and calibration instructions for the presence calibration requirements for devices running Android 14 and higher.

To ensure that users' smart devices work well together, it's critical that all devices in the Android ecosystem can determine the relative proximity between devices. Android 14 introduces presence calibration requirements that outline the acceptable performance of available radio technologies used to determine proximity, such as Ultra Wideband (UWB), Wi-Fi, and Bluetooth Low Energy (BLE).

Reference device

To calibrate your device to meet the presence requirements, use one of the following reference devices for all calibrations.

  • (Recommended) A Pixel phone
  • If not using a Pixel phone, use the same make and model device as the device being tested.

Form factors

Presence calibration is important for Android devices of all form factors. For form factors other than mobile phones, to determine the appropriate calibration setup for the device, consider how a user holding a mobile phone (reference device) would be positioned when interacting with the device under test (DUT). For example, when calibrating a TV, place the TV and the mobile phone at an appropriate distance from each other and orient the mobile device so it's facing the front center of the TV screen.

Ranging accuracy tests

For devices running Android 17 and higher, the CtsMultiDeviceGenericRangingAccuracyTests module includes test cases that verify the presence calibration requirements on this page. This module is an automated CTS Verifier (CTS-V) host-side multidevice test that runs from a host machine connected to the DUT and the reference device. The module replaces the manual presence tests in CTS-V. For devices running Android 16 and lower, use the presence tests in the CTS and CTS-V releases for that Android version.

To run the ranging accuracy tests:

  1. Set up the host machine, and set up CTS-V on the DUT and the reference device. For details, see Set up host-side multidevice tests.

  2. Place the DUT and the reference device 1 meter apart, as described in Set up ranging accuracy tests and in the calibration setup for each technology on this page.

  3. Connect both devices to the host machine using USB cables.

  4. From the directory where you unzipped the CTS-V package, launch the CTS-V host console:

    ./android-cts-verifier/android-cts-v-host/tools/cts-v-host-tradefed
  5. In the CTS-V host console, run the ranging accuracy tests:

    run cts-v-host -m CtsMultiDeviceGenericRangingAccuracyTests
    

    The test results appear in the CTS-V app on the DUT under Host-side Tests > UWB Tests > CtsMultiDeviceGenericRangingAccuracyTests.

Each test case in the module collects measurements using one technology, computes accuracy metrics from the measurements, and logs the metrics. A test case passes if it collects the measurements successfully, even if the metrics don't meet the targets. To verify compliance, compare the logged metrics with the targets described in the following sections. If the DUT or the reference device doesn't support a technology, the test case for that technology is skipped.

UWB requirements

Refer to CDD section 7.4.9 for UWB requirements.

UWB calibration setup

Use the following setup to calibrate your device to meet UWB requirements.

General setup requirements

  • Two devices with UWB hardware are required, one as the DUT and one as the reference device.

  • Two tripods to hold the devices are required.

  • The DUT and the reference device must be placed 1 meter apart in a line of sight environment in a nonreflective chamber. Both devices must be positioned in a portrait orientation with the screen facing away from each other.

An example of a UWB calibration setup is shown in Figure 1 and Video 1.

Reference setup for BLE calibration

Figure 1. Reference setup for UWB calibration.

Video 1. Reference setup for UWB calibration.

Verify compliance of CDD 7.4.9 [C-1-6] and [C-1-7]

To verify compliance with CDD 7.4.9 [C-1-6] and [C-1-7], run the ranging accuracy tests and check the metrics logged by the test_uwb_ranging test case.

The test case initiates a UWB ranging session between the DUT and the reference device, and takes 1,000 measurements with each device. For the measurements from each device, the test case does the following:

  1. Computes the range as: range = 97.5th percentile measurement - 2.5th percentile measurement. To meet the requirement, the range must be less than or equal to 30 cm.

  2. Computes the median measurement. To meet the requirement, the median must be between 0.75 m and 1.25 m inclusive.

Wi-Fi Neighbor Awareness Networking requirements

CDD section 2.2.1. Hardware includes requirements for Wi-Fi Neighbor Awareness Networking (NAN) compliance.

Verify compliance of CDD 2.2.1 [7.4.2.5/H-1-1]

To verify compliance with CDD 2.2.1 [7.4.2.5/H-1-1], run the ranging accuracy tests and check the metrics logged by the test_wifi_rtt_ranging test case.

The test case starts a Wi-Fi NAN ranging session between the DUT and the reference device, and takes 100 Wi-Fi RTT measurements. The test case then computes the percentage of measurements that are within ±2 m of the actual distance of 1 m. To meet the requirement for 80 MHz bandwidth, at least 68% of the measurements must be within ±2 m.

BLE RSSI requirements

CDD section 7.4.3. Bluetooth includes requirements for BLE RSSI compliance.

Calibration setup

Use the following setup to calibrate your device to meet the BLE RSSI requirements.

General setup requirements

  • For optimal results, use an anechoic chamber to minimize interference with measurements.

    If not using an anechoic chamber, set up one tripod holding the reference device and one holding the DUT device 1.5 meters from the ground, with similar clearance from the ceiling.

  • Prepare the reference device and DUT device:

    • Ensure both devices are charged enough to complete the tests.
    • Unplug both devices during testing.
    • Remove all cases, attached wires, and other attachments that might affect radio frequency (RF) performance.
  • Attach each device to a tripod with a device holder.

    • Tripods and device holders should have as little metal in them as possible.
    • A small metal spring in device holders is fine.
  • Remove any metal objects between two devices.

Reference setup for BLE calibration

Figure 2. Reference setup for BLE calibration.

Verify compliance of CDD 7.4.3 [C-10-1]

To verify compliance with CDD 7.4.3 [C-10-1], run the ranging accuracy tests with the devices placed according to the BLE calibration setup, and check the metrics logged by the test_ble_rssi_ranging test case.

The test case sets the reference device to advertise at ADVERTISE_TX_POWER_HIGH, and collects 1,000 scans on the DUT. The test case then computes the range of the middle 95% of the RSSI measurements. To meet the requirement, the range must be less than or equal to 18 dB.

Verify compliance of CDD 7.4.3 [C-10-2]

To verify compliance with CDD 7.4.3 [C-10-2]: The chip vendor can measure the channel flatness and identify the differences between cores and channels.

The following are tips on how to identify issues with uncalibrated cores and uncalibrated channels, which are two possible causes of large RSSI spread.

Uncalibrated cores

If the Bluetooth antenna on a device has multiple cores, the cores might have different calibrations. Take some measurements (at least 1 minute worth) and check the scan data. If you see a pattern similar to the one shown in Figure 3, which has regular peaks (as indicated by the circles) due to scanning on multiple cores, there is likely to be an issue with uncalibrated cores and further investigation is required.

Example scan data for device with uncalibrated cores

Figure 3. Example of scan data for a device with uncalibrated cores.

Uncalibrated channels

Transmissions on classic BLE happen on three channels. Each channel might have differences associated with it. The channels are rotated at fixed intervals. Take some measurements (at least 1 minute worth) and check the scan data. If you see a pattern similar to the one shown in Figure 4, there is likely to be an issue with miscalibration on different channels and further investigation is required.

Example of scan data for device with uncalibrated channels

Figure 4. Example of scan data for a device with uncalibrated channels.

Verify compliance of CDD 7.4.3 [C-10-3] and [C-10-4]

Even when a BLE radio chip is perfectly calibrated, the RSSI that a particular device observes depends on the antenna quality and the antenna placement on that particular product (device model). This presents a problem for interoperability between devices.

For example, consider a car unlock use case. An app developer might want to unlock a car when the device is within 1 meter of the car. The developer chooses a threshold of -60 dBm based on their observations with a phone they have, but due to differences in antenna quality and antenna placement, this might not work well with another Android device even if both devices use the same chip.

For interoperability between all devices in the ecosystem, you must measure the Rx offset for each device and adjust the RSSI reported on the device to ensure that the BLE RSSI meets the standard of 1 m at ADVERTISE_TX_POWER_HIGH.

Even when the BLE radio chips are perfectly calibrated, the ideal receiver reads different RSSI depending on the antenna quality and antenna placement on the advertising device. The Rx requirement ensures that all devices are able to advertise with the same resulting strength, all else being equal.

To verify compliance with the Rx and Tx requirement:

  1. Place the DUT 1 m away from the reference device, following the BLE calibration setup. We recommend devices be oriented such that they are parallel to each other with screens facing the same direction.

  2. Run the ranging accuracy tests and check the metrics logged by the test_ble_rx_tx_offset_precision test case.

    The test case runs the Rx and Tx tests at the same time, and collects 1,000 scans for each test:

    • Rx: The DUT scans while the reference device advertises at ADVERTISE_TX_POWER_HIGH.
    • Tx: The reference device scans while the DUT advertises at ADVERTISE_TX_POWER_HIGH.

    To meet the requirement, the median RSSI for both the Rx and Tx tests must be between -65 dBm and -45 dBm.

  3. Calibrate the devices to compensate the Rx offset and Tx power to ensure a median RSSI of -55 dBm.

    • Rx: Adjust the RSSI by setting the bluetooth.hardware.radio.le_rx_path_loss_comp_db system property to the value (dB) that compensates the Rx offset to ensure a median BLE RSSI of -55 dBm at 1 m. The Bluetooth stack adjusts the RSSI to be RSSI plus the value of bluetooth.hardware.radio.le_rx_path_loss_comp_db.

      For details, see le_scanning_manager.cc.

    • Tx: Adjust the Tx power by setting the bluetooth.hardware.radio.le_tx_path_loss_comp_db system property to the value (dB) that compensates the Tx power to ensure a median BLE RSSI of -55 dBm at 1 m. The Bluetooth stack adjusts the Tx power to be Tx power plus the value of bluetooth.hardware.radio.le_tx_path_loss_comp_db.

      For details, see le_advertising_manager.cc.

BLE Channel Sounding requirements

CDD section 7.4.3. Bluetooth includes requirements for BLE Channel Sounding (CS) accuracy. Requirement [C-11-2] specifies that devices that declare FEATURE_BLUETOOTH_LE_CHANNEL_SOUNDING must report the range accurately to within ±0.5 m at the 90th percentile, as calculated with the cumulative distribution function (CDF), at a distance of 1 m.

Verify compliance of CDD 7.4.3 [C-11-2]

To verify compliance with CDD 7.4.3 [C-11-2], run the ranging accuracy tests with the devices placed according to the BLE calibration setup, and check the metrics logged by the test_channel_sounding_ranging test case. Both the DUT and the reference device must support BLE CS.

The test case bonds the DUT and the reference device over BLE, starts a BLE CS ranging session between them, and takes 100 distance measurements. The test case then computes the percentage of measurements that are within ±0.5 m of the actual distance of 1 m. To meet the requirement, at least 90% of the measurements must be within ±0.5 m.