Firmware updates#

The Firmware screen updates the software running on the headset itself. Open it with the Firmware button on a connected headset, or by tapping the amber Update pill when one is shown. It is available only on headsets that support over-the-air updates — headsets without OTA support have no Firmware button. Connect a headset first (see Connect a headset).

The screen#

The screen shows two cards:

Firmware — the Installed and Latest versions, a Check for updates button, and either a green Up to date row or an amber Update firmware button.
Device — model, serial number, hardware and firmware versions, manufacturer, battery and charging state.

Latest versions come from BrainAccess over the internet; without a connection the value reads unknown (never “up to date”, so a network problem cannot be mistaken for being current). Downloaded images are checksum-verified before anything is sent to the headset.

Each firmware image is built for one headset board. The app offers an update only when the board the headset reports matches the published image; otherwise Latest reads not available and the screen says Firmware for this headset’s board (…) isn’t available in this version of the app. A headset that doesn’t report its board gets no update from the app.

Before you update#

The app checks two preconditions and refuses to start until both are met:

No recording in progress — Stop the recording before updating firmware — the update restarts the device and would cut the file short. (See Recording.)
Battery above 30%, or plugged in — Charge the headset above 30% (or plug it in) before updating — it is at N%, and losing power mid-transfer leaves a partial image.

During the update#

Once it starts, the screen takes over and steps through Preparing update…, Requesting update mode…, Transferring firmware… (with a percentage and KB counter), Finalizing…, and Applying update…. Expect about a minute in total.

Warning

Do not interrupt an update. Keep the app in the foreground, keep the headset powered on and nearby, and do not let the phone die. Back is deliberately ignored while the transfer runs.

When it finishes#

The headset switches itself off — this is expected. Power it back on and reconnect, then check the Installed version to confirm the new firmware.

If it fails#

You get a specific reason (no connection, checksum mismatch, headset not ready, and so on) and a Retry update button. A failed or interrupted update is not applied: the headset keeps its current firmware, so you can simply try again. A checksum mismatch means the downloaded image did not match its published fingerprint and was not installed — try again later or contact support rather than retrying repeatedly.