Meshtastic-Android's own bootloader-OTA quirks manifest (androidApp/src/main/assets/device_bootloader_ota_quirks.json) flags NOMADSTAR_METEOR_PRO (hwModel 96, PlatformIO target rak4631_nomadstar_meteor_pro) as requiresBootloaderUpgradeForOta: true, but there's no corresponding board in src/boards/ here — it's RAK4631-based but tracked as a distinct hwModel from plain RAK4631 (already supported), so it's not safe to assume it can just reuse wiscore_rak4631_board's UF2 as-is.
Reference: https://github.com/meshtastic/Meshtastic-Android/blob/main/androidApp/src/main/assets/device_bootloader_ota_quirks.json
Needs someone with the physical hardware to confirm whether it can reuse the existing RAK4631 board port or needs its own src/boards/ entry.
Meshtastic-Android's own bootloader-OTA quirks manifest (
androidApp/src/main/assets/device_bootloader_ota_quirks.json) flagsNOMADSTAR_METEOR_PRO(hwModel 96, PlatformIO targetrak4631_nomadstar_meteor_pro) asrequiresBootloaderUpgradeForOta: true, but there's no corresponding board insrc/boards/here — it's RAK4631-based but tracked as a distinct hwModel from plainRAK4631(already supported), so it's not safe to assume it can just reusewiscore_rak4631_board's UF2 as-is.Reference: https://github.com/meshtastic/Meshtastic-Android/blob/main/androidApp/src/main/assets/device_bootloader_ota_quirks.json
Needs someone with the physical hardware to confirm whether it can reuse the existing RAK4631 board port or needs its own
src/boards/entry.