Skip to content

Over-The-Air (OTA) Firmware Update

Overview

The firmware update process (OTA) is managed by the SDK via the M2OtaService (accessed from Evs.otaService).

The SDK embeds the glasses firmware update files, and it detects when an update is available.

The SDK implements by default a UI for managing both the update-available notification and the update process.

The firmware data is uploaded to the glasses via Bluetooth, so it is recommended to perform firmware update having 1 meter or less between the phone and the glasses and to disconnect any other Bluetooth devices from the phone.

Warning

The firmware update process should be handled carefully.

Battery Level

It is recommended to perform firmware update when the glasses battery is above 50%.

  • The update will fail if the glasses are under 20% battery.
  • The update will fail if the glasses are under 50% battery and not connected to the charger.

The Update Process

The update process has the following steps:

  1. Check - Upon connection, an update check is performed. If an update exists, the SDK will notify the app about the available update.
  2. Approve - The app/user will approve the SDK to start the update process.
  3. Upload - The SDK will upload the firmware information to the glasses.
  4. Install - The SDK will instruct the glasses to install the update.
  5. Reboot & Reconnect - The glasses will reboot. The SDK will reconnect the glasses.

Using the OTA Stock UI

To open the OTA Stock UI:

Evs.showUI(M2ShowUIOption.DefaultOta)

Evs.shared.showUI(option: M2ShowUIOption.companion.DefaultOta)

OTA Events

The SDK provides callbacks for the OTA lifecycle:

Event Description
onStart Upload has started
onProgress Upload progress update
onError An error occurred
onDone Upload complete, installing
onCompleted Full OTA cycle complete

See Also

  • Glasses - Device info, battery, and system events
  • Communication - BLE connection and data exchange