Frequently asked questions.
Does MeshCrossway merge Meshtastic and MeshCore into one network?
No. Both editions use two independent radios and preserves each protocol's identity, security and routing. The unified UI is not an automatic protocol bridge.
Can both networks operate at the same time?
Yes. The controller supports simultaneous independent Meshtastic and MeshCore BLE radio sessions. Broader RF coexistence, range and endurance qualification of the final hardware remains ongoing.
Does it need cellular service or internet?
Native LoRa messages and local GNSS/track tools do not require cellular service. Previously cached SD map tiles work offline; downloading uncached tiles and firmware needs Internet access.
Do I have to use a Seeed XIAO/Wio radio?
No. The radio hardware is user-selectable. Heltec V3 is the current development-tested setup. Each chosen device must support the corresponding native Meshtastic BLE PhoneAPI or MeshCore BLE Companion with compatible firmware; compatibility is checked per model and firmware.
Is the hardware finished?
The working software uses a Waveshare touchscreen controller and two independent BLE radios. Final detachable Pod power, enclosure, RF and environmental validation remain in progress. The integrated Rev A PCB is an archived design.
Can I try the interface?
Yes. Download the Android 0.1.0 beta APK to test with compatible radios. It is a development beta, not version 1.0.0. The old browser simulator is retired; the controller photos remain historical evidence.
Does the Android app require the Waveshare controller?
No. Your phone connects directly to the radios. The dedicated touchscreen controller and its local browser companion remain a separate track.
Why Android 0.1.0 while the controller is v0.9.32?
They use independent version sequences. Android 0.1.0 starts from the accepted functional alpha07 baseline. Small changes use 0.1.1, 0.1.2, etc.; larger changes use 0.2.0. Android 1.0.0 has not been released.
Can I flash firmware from the browser?
Yes. The Web Flasher installs v0.9.32 stable on the supported non-B Waveshare ESP32-S3-Touch-LCD-3.5 Rev2.0. v0.9.28, v0.9.25 and v0.9.16 remain recovery choices. Each image is checksum-verified.
Is MeshCrossway an emergency or rescue device?
No. It is experimental open-source hardware/software and should not be relied on as the sole communications method for safety-critical use.