In Meridian Android SDK version 9.3.0, Meridian enhanced the wayfinding feature by adding Wifi based location to bolster the Aruba Open Location initiative. This technology is known by several names, such as 802.11MC, or Fine Time Measurement (FTM), or Round Trip Timing (RTT). The fundamental concept is that the phone sends a message to the Access Point (AP), which then responds with the time it took to process the request. Using this data, the mobile device computes its distance from the AP. When three or more APs are involved in the process, Meridian uses trilateration to determine the mobile device's precise location. To learn more about FTM, you can refer to this overview article by Google.
To use FTM to get the mobile devices location, please make sure the following criterias are met:
- Enable FTM in Meridian at startup. It is off by default, but can be enabled using setUseWifiLocation.
- The user must accept the following runtime permissions (NEARBY_WIFI_DEVICES and ACCESS_FINE_LOCATION).
- The Aruba APs must have FTM enabled and have been added to Meridian using Beacons Management. It is recommended that the APs use 80MHz for the best results. This article has a list of supported APs.
- The Android device must support FTM. This article has a list of supported devices.
When using FTM, the location dot is orange by default, but can be customized using setCustomColor. Meridian first tries to compute location using Wi-Fi and will fallback to Bluetooth or GPS as necessary. FTM must be enabled before starting the location engine (e.g. loading the first map).
Currently enabling or disabling FTM at runtime is not supported.
This feature is only supported in the Android SDK and not available for the iOS or Web SDK.