Meshcore Android connection


  • I recently switched my Ranger from meshtastic to meshcore.  Now I can't connect to the meshcore app on my Samsung android.  Suggestions?

     



  • When transitioning a device from Meshtastic to MeshCore, Bluetooth connection issues on Android are usually caused by stale Bluetooth bonding cache, missing location permissions, or choosing the wrong firmware type during flashing.

    1. Clear Phone Bluetooth Cache & Unpair
    • Open Settings > Connections > Bluetooth on your Samsung phone.
    • Look for any old saved device entries.
    • Tap the Gear Icon next to the saved device and tap Unpair / Forget.
    • Toggle Bluetooth OFF, wait 5 seconds, and toggle it back ON.
    2. Reset App Permissions & Location Services
    • Android requires Location Services (GPS) and Nearby Devices permissions to scan for Bluetooth Low Energy (BLE) nodes.
    • Go to Settings > Apps > MeshCore > Permissions.
    • Ensure Nearby Devices is set to Allow, and Location is set to Allow while using the app.
    • Turn on your phone's general Location / GPS toggle in the quick settings shade.
    3. Check Device Boot State & Firmware Build

    • Did you perform a full chip erase when flashing? Switching from Meshtastic leaves behind leftover NVS partition data. Flash MeshCore again via flasher.meshcore.io in Chrome, making sure to tick Erase device.
    • Did you flash a Companion BLE build? Ensure you selected the Companion (Bluetooth) firmware role rather than a Serial/USB Companion or Repeater image, as repeater builds do not broadcast BLE pairing mode.
    • Power cycle the Ranger node once after reflashing.
    4. Pair Directly Through the MeshCore App
    • Do not attempt to pair the node using your phone’s system Bluetooth menu first.
    • Open the MeshCore App directly, tap Add Device / Connect, and let the app handle the BLE handshake.

    If you would like our technical team to help you get this resolved, please feel free to reach out via our email, general@specfive.com. 

     

Please login to reply to this topic!