Releases

Meshtastic Android pre-release fixes QR channel imports and firmware updates

A July 2 Android pre-release fixed QR channel imports, car-mode messaging, and nRF USB reconnects, smoothing three daily pain points for Meshtastic users.

Jamie Taylor··2 min read
Published
Listen to this article0:00 min
Meshtastic Android pre-release fixes QR channel imports and firmware updates
Photo illustration

Meshtastic Android’s v2.8.0-closed.3 pre-release landed on July 2, 2026 with commit f9ad82c and leaned hard into reliability work instead of new flash. The update tightened the app’s UI, fixed BLE scan registration failures, stopped docs screenshots from churning in builds, and, most importantly for field use, cleaned up three places where the Android client could get in the way: importing channels by QR, using the app in a car, and reconnecting after firmware updates.

The most user-facing fix is the QR work. v2.8.0-closed.3 now preserves incoming channels when adding from a QR code, which matters because QR sharing is one of the quickest ways to clone or hand off a Meshtastic setup. A bug report opened on October 14, 2025 showed why that mattered in practice: adding channels from QR could remove or replace existing channels instead of appending them. The report came from a user on app version 2.7.2, Android 16, and a Heltec V3 running firmware 2.6.11, a combination that makes the fix feel less like housekeeping and more like a safeguard against wiping out a working node profile.

AI-generated illustration
AI-generated illustration

Car behavior got a smaller but still meaningful round of attention. The release suppresses INVISIBLE_MEMBER in CarScreensTest for the F-Droid build and adjusts notification-only car messaging for production, while leaving templated behavior behind a flag. That points to an Android client that is still being tuned for automotive use, where notification surfaces and packaging rules do not always line up cleanly. For anyone running Meshtastic on the road, the goal is simple: keep the app readable and predictable without making the car experience feel like a separate, fragile fork.

The upgrade path itself also got sturdier. v2.8.0-closed.3 repairs nRF USB firmware update handling and the reconnect flow that follows, which should make device upgrades less nerve-wracking when a node comes back online. That sits neatly beside Meshtastic Android’s dedicated firmware update module for devices that support USB Mass Storage updates, and a longer-running feature request from May 14, 2024 that asked for firmware checks and a download-and-flash option inside the app. Meshtastic’s release process is still deliberately manual, with release.yml triggered by hand and final GitHub Release publishing plus Google Play Console uploads done manually after tests pass on a branch cut from the latest main branch.

Meshtastic calls itself an open-source, decentralized mesh networking ecosystem built around inexpensive LoRa radios for off-grid communication, and the Android client is one of the easiest ways to keep that mesh usable day to day. QR imports that do not clobber channels, car screens that behave, and firmware updates that reconnect cleanly all push the app toward the kind of reliability active field users notice immediately.

This article was produced by Prism’s automated news system from verified source data, official records, and press releases, then run through automated quality and moderation checks before publishing. The system is built and supervised by the people who set the standards it runs under. Read our full AI policy.

Did this article answer your question?

Discussion

More Meshtastic News