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 capped, checksum-verified and
rejected on mismatch before anything is sent to the headset.
Each firmware image is built for one headset board, and BrainAccess publishes one per board (HALO
V2 and HALO V3 each have their own). The app picks the image for the board the headset reports;
where none is published for it (the original HALO, for example) 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.
The update check sends source=mobile_app, os=ios, the app version and, when a
connected headset exposes it, the headset model/serial. It never sends EEG or a
CoreBluetooth UUID. See Privacy Policy.
Before you update#
The app checks two preconditions and refuses to start until both are met:
No recording in progress — stop recording before updating firmware; the update restarts the device and would cut the file short.
Battery at least 30%, or plugged in — charge the headset to 30% or plug it in before updating; losing power mid-transfer can leave a partial image.
Live streaming also has to be stopped because OTA recycles the headset link.
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 ignored while the transfer runs.
When it finishes#
The headset switches itself off — this is expected. Power it back on and the app reconnects to it and reads the Installed version, then tells you either that the new firmware is running, or that the headset still runs the old version (a headset can roll back an image that fails to start) — in that case run the update again. A completed transfer alone is not reported as a successful update.
If the app cannot read the version straight away (the headset did not come back in time, or reported a version it cannot compare), the screen reads Update sent rather than finished: power the headset on and reconnect, and the app confirms the version on that connection.
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.
See also#
Connect a headset — the Firmware button appears on a connected, OTA-capable headset.
Recording — stop any recording before updating.
Privacy Policy — firmware-check parameters.