Aidlab Docs

Appearance

Troubleshooting ​

Use this checklist when a sample app builds but does not discover a device or does not receive data.

No device found ​

  • Use a physical phone or computer with Bluetooth 4.0+ support. Simulators and emulators cannot connect to Aidlab devices.
  • Make sure the device is charged, awake, and close to the computer or phone.
  • Wear the device correctly. Some streams start only when the device detects a valid signal.
  • Disconnect the device from other apps before scanning from your integration.
  • On mobile, make sure Bluetooth is enabled and the app has Bluetooth permissions.

Permission denied ​

  • Android 12+ requires runtime Bluetooth permissions such as BLUETOOTH_SCAN and BLUETOOTH_CONNECT.
  • Android apps that scan for BLE devices may also need location permission depending on Android version and app configuration.
  • Apple platforms require NSBluetoothAlwaysUsageDescription in Info.plist.
  • Browser-based or desktop tests must run in an environment that supports Bluetooth access.

Connected, but no samples ​

  • Call collect(...) with the data types you want to receive after the connection callback.
  • Confirm that the requested data type is supported by your device and firmware in Data Types and Events.
  • Check whether the stream needs the device to be worn, whether electrodes have contact, or whether the sensor is enabled.
  • Enable SDK logging to confirm that the connection and collection command are being sent.

Device disconnects ​

  • Keep the device close to the phone or computer and avoid connecting from multiple apps at the same time.
  • Add reconnect and backoff logic in production apps.
  • On Android, account for battery optimization and background execution limits.
  • On iOS, configure the required Bluetooth background modes if your app must continue in the background.

Firmware mismatch ​

  • Compare the firmware requirement in Data Types and Events with the firmware version reported by your device.
  • Update the device firmware from the official Aidlab app when a required stream is not available.
  • If the same code works on one Aidlab device but not another, check hardware revision and firmware first.

Stale pairing or Bluetooth cache ​

  • Turn Bluetooth off and on, then restart scanning.
  • Remove the device from the OS Bluetooth settings if it was previously paired manually.
  • Restart the phone or computer when the OS Bluetooth stack keeps reporting stale devices.
  • Reinstall the sample app if mobile permissions were denied permanently.