Android · Public beta for testing

MeshCrossway 0.2.5 beta.

Two independent mesh radios, one Android interface. Try messages, contacts, maps and tracks with your Meshtastic and MeshCore radios connected together.

This is a beta for testing, not version 1.0.0. The previous radio baseline is functional; Remote Access is new and still requires real phone/computer acceptance. Broader phone, radio, firmware and endurance testing continues.
Download Android beta APK · 0.2.5Release notes and checksums

ARM64 · Android 8.0 or newer · Public GitHub release asset; no Actions login required.

What you need

An ARM64 Android phone, Bluetooth and compatible radio firmware. To use both networks, choose one Meshtastic radio and one MeshCore Companion BLE radio. The dedicated touchscreen controller is not required. Heltec V3 and Samsung S25 are used in development; other combinations need testing.

What is included

Independent dual BLE connections, chats, contacts and channels, offline areas, tracks and GPX, POIs and backup. The HTTPS computer browser now has dedicated Chats, Channels and Nodes tabs plus visual map selection by drawing a rectangle.

Offline use

Native LoRa messaging needs no cellular service. Download the APK and required map areas while online. Confirm that your selected map area and zoom levels are available offline before a trip. Wardriving/MeshMapper uploads are not included.

Install, connect and test local web access

  1. Download the permanently signed 0.2.5 APK and install or update directly over 0.2.4. No ADB or ZIP required for ordinary upgrades. Never uninstall to update; this retains settings, conversations, favorites, tracks and maps.
  2. Allow installation from your browser or file manager when Android prompts.
  3. Grant Bluetooth/nearby-device permissions and location permission for GPS, tracks and scanning where required.
  4. Close other apps using the same radios. In MeshCrossway Settings, choose your Meshtastic radio and your MeshCore radio, then let synchronization complete.
  5. Check each network status, then test sending, receiving and reconnection.
  6. Optional: activate Remote Access from the phone Home card over trusted private Wi-Fi. Choose a 4–8 digit PIN, verify the HTTPS certificate fingerprint shown on the phone, and enter the same PIN in the browser. Open Messages → Chats/Channels/Nodes, or Offline maps → Draw area to select a rectangle and its maximum download zoom. Stop Remote Access when finished; do not expose its port to the internet.
Updating an earlier test build? This beta uses a CI development signing certificate. If Android reports a signing conflict, export JSON history and needed GPX tracks before uninstalling. Uninstalling deletes local app data.

Messages and routing remain independent. An accepted-by-radio send status does not prove end-to-end delivery. Complete historical paths are shown only where captured; private/backlog MeshCore messages and Meshtastic text may not include the full path.

From beta to 1.0.0

0.2.5

Compact Home with side-by-side Meshtastic/MeshCore radio cards, true Bluetooth RSSI dBm/bars, and no repeated section headings. Retains the permanent signing identity, dual-mesh messaging, offline maps and customizable themes. The short PIN remains. 0.2.3 is the permanent-key recovery beta. 0.2.2 and earlier remain historically debug-signed builds. Earlier alpha02–alpha07 labels were development iterations; alpha07 behavior is retained under the new 0.1.0 sequence.

0.2.x → 0.3.0

Corrections and small improvements increment the last number. Substantial features or workflow changes increment the middle number and reset the last number to zero.

1.0.0

Reserved for the first production release after core scope and stability acceptance. It has not been released. Controller firmware keeps its own independent version sequence.

The APK passed build/lint/protocol checks and Android API 29/35 device smoke tests. The functional predecessor was accepted in real-device use; automated tests do not establish compatibility with every phone or radio.

Report a beta issueDetailed Android guideValidation run

Include app version, phone/Android version, radio models/firmware and steps to reproduce. Redact keys, personal messages and precise locations.