Messages you may see#
BrainAccess Mobile surfaces short status messages as banners and snackbars while you scan, connect, stream, record and update firmware. This page covers the messages you are most likely to see, grouped by where they appear rather than listed exhaustively.
Message |
Meaning |
|---|---|
Bluetooth is off / Bluetooth is off — turn it on to connect. |
Turn Bluetooth on in Control Centre or iOS Settings |
Bluetooth permission / Bluetooth permission needed / Bluetooth permission is needed — grant it in Settings. |
Grant Bluetooth access in iOS Settings → BrainAccess Mobile |
Couldn’t find |
A remembered-headset reconnect attempt timed out |
Couldn’t reconnect |
A reconnect during a mode transition failed; check the headset and try again |
The Bluetooth link dropped unexpectedly |
|
Saved |
Recording stopped; the file was saved, or no samples reached the writer |
Recording failed — … Partial file kept. / Recording failed — … Nothing was recorded. |
Usually storage or file-system trouble. BDF may keep completed seconds; CSV may be discarded |
Recording failed to start: … |
The recording file could not be opened or armed |
Recording metadata file could not be written. |
The recording’s |
Some markers may not have been stored in this BDF — CSV keeps every marker. |
More than the BDF annotation capacity was requested in one or more data records |
The headset refused these settings — open Config, check the sample rate and gain, then try again. |
Firmware 3.7.0 or later rejected the configuration and would have streamed its defaults instead |
The headset could not start streaming — try again; if it keeps failing, power it off and on. |
Firmware 3.7.0 or later reported that its signal converter failed to start; the connection is still up |
A mode switch is in progress — try again in a moment. |
Another mode switch for that headset is still completing |
This recording was interrupted before it was finalised — N s of it was recovered. |
A BDF session ended abnormally; completed records are openable |
Snapshot saved: |
A viewer screenshot was saved, or could not be written |
Finish the current contact check before starting another — only one runs at a time. |
Stop the running contact check before starting a new one |
The update server returned no firmware information. |
The firmware check reached the server but got nothing back |
Couldn’t check for firmware updates — check your connection and try again. |
Network problem reaching the update server |
Couldn’t read the headset’s power settings. |
The headset didn’t report its auto power-off setting, so it was left unchanged; try again from Config |
Couldn’t remember the power-off time — storage is unavailable. |
The headset accepted the auto power-off time but the phone couldn’t save it, so it will not be re-applied on the next connect; free up storage and set it again |
After an update, the reconnected headset reports the new version |
|
The headset kept or restored its old firmware after the update; run the update again |
|
The headset or the update reported a version the app could not compare; check Installed on the Firmware updates screen |
|
Firmware for this headset’s board (…) isn’t available in this version of the app. |
No published firmware image is built for this headset’s board (for example the original HALO); the app won’t install another board’s image |
This headset doesn’t report which board it has, so the app can’t pick a matching firmware image … |
The headset’s firmware is too old to report its board; the app can’t verify an image fits |
Could not open |
A recording could not be opened for review; the reason follows |
See also#
Troubleshooting — fixes for the symptoms behind many of these messages.