Choose the Android 0.1.0 beta on your phone or the dedicated touchscreen controller. Both use independent Meshtastic and MeshCore Bluetooth sessions. The controller firmware keeps its own v0.10.5 stable baseline; neither edition forwards traffic between networks.
Connect directly to two compatible BLE radios. Use chats, contacts, maps, optional node grouping, track recording, GPX, POIs, offline areas and JSON history backup. The Android app does not require the Waveshare controller.
Not version 1.0.0. Smaller fixes use 0.1.1, 0.1.2 and so on; substantial changes use 0.2.0. A production release will be marked 1.0.0 after core scope and stability acceptance.
Native Meshtastic PhoneAPI and MeshCore Companion BLE sessions, with their own pairing, identities, messages, channels and configuration. Users can choose compatible radios; Heltec V3 is development-tested, and other model/firmware combinations require validation.
GNSS position and clock, street/topographic maps, local street night view, cached SD tiles, tracks, POIs, folders and GPX. Uncached maps need Wi-Fi; live position sharing remains future work.
Use a browser on the same local network for messages, radio settings, route previews, folders and GPX downloads. Manual screenshots are available; continuous remote touchscreen control is not enabled.
Independent marker shapes, sizes and colors; optional grouping; 32-row manual-refresh node lists. Age colors distinguish under 24 hours, 1–7 days and older/unknown observations. A saved 0–365 day limit removes ordinary local discoveries while protecting favorites, conversations and uncertain timestamps.
Automatic 180-degree landscape orientation, saved rotation lock, manual flip/reference correction, brightness and screen timeout. Bluetooth and Wi-Fi can be controlled in settings.
SD work runs through existing storage workers. Bounded console memory records and internal/PSRAM/DMA snapshots support testing. Node deletion reduces populated records; fixed table reservations remain allocated. DMA memory is a subset of internal RAM.
Stable releases retain the exact accepted binary by checksum. v0.9.28 is the previous stable recovery; v0.9.25 and v0.9.16 remain earlier recovery images. Mechanical, battery, RF coexistence and broader endurance qualification continue separately.