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.	Bluetooth could not keep up; the headset filled the gap
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.	Firmware 3.7.0 or later rejected the configuration and would have streamed its defaults instead
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
<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.	The firmware transfer finished; power the headset back on and reconnect
Firmware for this headset’s board (…) isn’t available in this version of the app.	The published firmware image is built for a different board than this headset’s; the app won’t install it
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 <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

Messages you may see#

See also#