Skip to content

fix(ble): show MeshCore devices when platformName is empty - #2

Open
DataArchitectPro wants to merge 1 commit into
mintylinux:mainfrom
DataArchitectPro:fix/ble-scan-advname
Open

fix(ble): show MeshCore devices when platformName is empty#2
DataArchitectPro wants to merge 1 commit into
mintylinux:mainfrom
DataArchitectPro:fix/ble-scan-advname

Conversation

@DataArchitectPro

@DataArchitectPro DataArchitectPro commented Jun 29, 2026

Copy link
Copy Markdown

Summary

  • Fix BLE device list being empty on Android when MeshCore/Heltec devices advertise their name in advName but not platformName
  • Include bonded devices via FlutterBluePlus.systemDevices (Nordic UART Service UUID)
  • Add getBluetoothDisplayName() cache so the picker shows names like MeshCore-… instead of a blank title
  • Extend scan timeout from 3s to 10s

Problem

scanBluetoothDevices() filtered scan results using only r.device.platformName. On Android, BLE scan often leaves platformName empty while the local name is available in r.advertisementData.advName. Bonded devices were also not considered.

Symptom: MeshCore nodes (e.g. Heltec T114) paired in system Bluetooth settings do not appear in Wardrive's "Scan Bluetooth" list, while other apps (e.g. MeshMapper) see them fine.

Related: mintylinux/Meshcore-Wardrive-Android#16 (similar platformName-only filter on WhisperOS).

Changes

  • lib/services/lora_companion_service.dart — scan/filter logic, bonded device lookup, display name helper
  • lib/screens/map_screen.dart — use getBluetoothDisplayName() in the device picker

Test plan

  • Heltec T114 (MeshCore firmware), Android 15 (LineageOS), device bonded as MeshCore-…
  • Wardrive → Connect → Bluetooth → device appears in list
  • Connect succeeds, ping works over BLE

On Android BLE scan, platformName is often empty; the device name is in advName.
Include bonded devices via systemDevices (Nordic UART), cache display names for UI,
and extend scan timeout to 10 seconds.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant