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 |
Turn Bluetooth on with Enable |
Nearby devices permission |
Scanning needs the permission; Open settings to grant it |
Bluetooth permission denied — grant it to scan for devices. |
As above |
Location services are off (required to scan on this Android version). |
Android 11 and older: switch location on |
Couldn’t find <name> nearby — check it is on and charged. |
A reconnect attempt timed out |
<name> disconnected. |
The link dropped unexpectedly |
<name> battery low (N%). |
Battery at 15% or less |
<name>: signal loss — N samples gap-filled. |
Some samples did not reach the app. Each gap is filled with zeros flagged as missing, so the timeline stays exact |
Filtering unavailable — showing unfiltered data. |
The display filter could not run; the trace is raw |
Saved m:ss · FORMAT · filename |
Recording finished; Open reviews it |
Recording failed — … Partial file kept. / … Nothing was recorded. |
Usually out of storage. The message says which of the two happened; BDF keeps what it wrote, a CSV may be discarded |
Some markers may not have been stored in this BDF — CSV keeps every marker. |
The recording holds more markers than the BDF annotation budget (about four per second of length) |
LSL failed to start: … |
The outlet could not open its network sockets; check Wi-Fi and switch LSL outlet on again |
<name>: LSL outlet restarted after send errors — same stream ID, receivers reconnect automatically. |
Sending to LSL kept failing, so the app replaced the outlet with an identical one (same name, stream ID and channels). LSL recorders such as LabRecorder reconnect by themselves, typically within two seconds; the file on the computer has a gap of that length |
<name>: LSL outlet stopped after repeated send errors … / <name>: LSL outlet could not be restarted … |
The restart did not help. Switch LSL outlet on again; your LSL setting is not changed, so the next stream starts the outlet as before |
Notifications are off — streaming continues, but the Stop and Marker controls won’t appear in the notification shade. |
Notification permission denied |
Background streaming may stop when the screen is off |
Android refused to keep the session in the foreground; reopen the app |
Busy finishing another operation — try again in a moment. |
Another mode switch is still completing |
The headset refused these settings — open Config, check the sample rate and gain, then try again. |
The headset did not accept the configuration; check the sample rate and gain in Config |
The headset could not start streaming — try again; if it keeps failing, power it off and on. |
The headset did not start streaming; the connection is still up, so you can try again straight away |
This recording was interrupted before it was finalised — N s of it was recovered. |
The session ended abnormally; what survived is open |
Couldn’t reconnect to <name> — … |
A manual reconnect attempt failed; the reason follows. Check the headset is on and in range, then try again |
Reconnect <name> before changing its configuration. |
The link dropped while its settings were open; reconnect first, then re-apply the change |
Couldn’t forget that headset — storage is unavailable. / … those headsets — … |
Removing a remembered headset couldn’t be saved; free up storage and try again |
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 |
<name> didn’t start delivering data — recording was not armed. |
The stream never produced samples, so nothing was recorded; check the headset and start again |
Recording failed to start: … |
The recording file could not be opened for writing (distinct from Recording failed — …, which ends a recording already running); usually a storage or permission problem |
Snapshot saved: <name> / Snapshot failed: … |
A viewer screenshot was saved under that name, or could not be written (usually storage) |
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; try again later |
Couldn’t check for firmware updates — check your connection and try again. |
Network problem reaching the update server |
<name> update sent — the device turned itself off. Power it on and reconnect to confirm the new firmware runs. |
The firmware transfer finished; power the headset back on and reconnect |
<name> now runs firmware <version>. |
After an update, the reconnected headset reports the new version |
<name> still runs firmware <version> — the update to <version> was not applied (the headset rolled back). Try the update again. |
The headset kept or restored its old firmware after the update; run the update again |
<name> reconnected with firmware <version>; could not confirm the update to <version>. |
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 current firmware does not report its board, so the app cannot confirm that an image fits it |
Could not open <file>: … |
A recording could not be opened for review; the reason follows |
Could not open app settings. |
Android would not launch its settings screen; open it by hand from Android Settings |
Stop queued |
You asked to stop while another operation was still finishing; the stop runs as soon as it completes |
See also#
Troubleshooting — step-by-step fixes for the symptoms behind many of these messages.