MeshCore

Changelog

All stable released beta alpha

0.9.18 Windows alpha

2026-09-05 · 1 file

The first Windows build. Windows 10 and 11, 64-bit — the same client as the Linux one, from the same source.

  • It installs for your account only, so it never asks for an administrator password, and updates replace it without one either.
  • Your messages live in %LOCALAPPDATA%\meshcore-desktop. Uninstalling MeshCore does not delete that folder — it is the only copy of them.
  • Bluetooth pairing is Windows' own job: add the radio in Settings › Bluetooth & devices, type its passkey there, then connect from MeshCore.
  • There is a Report a bug button on the About page. It shows you exactly what will be sent before it goes, and nothing identifying you is attached.

If a radio on USB does not appear, Windows is probably missing a driver for it rather than anything being wrong with the cable. A Heltec V3 — and most ESP32 boards — talks through a Silicon Labs CP2102, and Windows has no driver for that chip built in: until one is installed the board makes no COM port at all, which looks from in here exactly like an unplugged radio. Silicon Labs' CP210x VCP driver is the fix, and after installing it the radio appears by itself. Boards that present as a plain USB serial device, such as the RAK4631, need nothing.

0.9.18 Android (.apk) alpha

2026-09-04 · 1 file

  • Report a bug, from inside the app. There is a button on the About page now. It shows you exactly what will be sent — the version, the diagnostics block, a screenshot if you attach one — and lets you take any of it off before it goes. Nothing identifying you is attached, the contact box starts empty, and no screenshot is ever taken by itself: a screenshot of this app usually has other people's messages in it.
  • Fixed: the chosen update channel was drawn the same as the others, so Released, Beta and Alpha all looked unselected. Android only.

Replaces 0.9.17, which went out before the reporting button was finished.

0.9.18 Linux (.deb) alpha

2026-09-04 · 1 file

  • Report a bug, from inside the app. There is a button on the About page now. It shows you exactly what will be sent — the version, the diagnostics block, a screenshot if you attach one — and lets you take any of it off before it goes. Nothing identifying you is attached, the contact box starts empty, and no screenshot is ever taken by itself: a screenshot of this app usually has other people's messages in it.
  • Fixed: the chosen update channel was drawn the same as the others, so Released, Beta and Alpha all looked unselected. Android only.

Replaces 0.9.17, which went out before the reporting button was finished.

0.9.17 Android (.apk) alpha

2026-09-04 · 1 file

  • The update channel is remembered again. Choosing Beta or Alpha did not survive closing the app: the setting was read before the archive was open, found nothing, and fell back to Released every launch. Android only.

Everything else is as 0.9.16, which this replaces.

0.9.17 Linux (.deb) alpha

2026-09-04 · 1 file

  • The update channel is remembered again. Choosing Beta or Alpha did not survive closing the app: the setting was read before the archive was open, found nothing, and fell back to Released every launch. Android only.

Everything else is as 0.9.16, which this replaces.

0.9.16 Android (.apk) alpha

2026-09-04 · 1 file

A correction to the version number. Builds briefly went out numbered 9.1.x. That was a mistake: this line is 0.9.x, and it continues from 0.9.14 where it left off. The 9.1.x builds have been withdrawn and are no longer offered on any channel.

If you are running one of them, this build has to be installed by hand — the updater will not offer it to you. It never offers a lower version number than the one you are running, deliberately, because the archive migrates forward only and going back is not something it could carry out. Install this once and automatic updates work again from here.

Nothing else changed from the withdrawn builds. What they contained:

  • Each client checks its own update feed, so the desktop and the phone no longer have to share one version number.
  • Messages the phone received were being thrown away. Every message arriving over the radio failed a database constraint and was discarded silently, while the notification still appeared. Those are gone — the radio deletes each message as the app takes it — but from here they are kept, and a refused write says so instead of being silent.
  • Channels are read from the radio properly. The phone asked for four channel slots; radios have forty.
  • A tablet looks like a tablet. Navigation rail down the left and the conversation beside the list, as on the desktop. Phones are unchanged.
  • Administer a repeater from the phone over a USB-C cable.
  • The Radio page has moved into Settings › Radio.

0.9.16 Linux (.deb) alpha

2026-09-04 · 1 file

A correction to the version number. Builds briefly went out numbered 9.1.x. That was a mistake: this line is 0.9.x, and it continues from 0.9.14 where it left off. The 9.1.x builds have been withdrawn and are no longer offered on any channel.

If you are running one of them, this build has to be installed by hand — the updater will not offer it to you. It never offers a lower version number than the one you are running, deliberately, because the archive migrates forward only and going back is not something it could carry out. Install this once and automatic updates work again from here.

Nothing else changed from the withdrawn builds. What they contained:

  • Each client checks its own update feed, so the desktop and the phone no longer have to share one version number.
  • Messages the phone received were being thrown away. Every message arriving over the radio failed a database constraint and was discarded silently, while the notification still appeared. Those are gone — the radio deletes each message as the app takes it — but from here they are kept, and a refused write says so instead of being silent.
  • Channels are read from the radio properly. The phone asked for four channel slots; radios have forty.
  • A tablet looks like a tablet. Navigation rail down the left and the conversation beside the list, as on the desktop. Phones are unchanged.
  • Administer a repeater from the phone over a USB-C cable.
  • The Radio page has moved into Settings › Radio.

0.9.2 beta

2026-09-03

  • A plain message when no radio is attached, instead of a silent empty window.
  • Bluetooth that pairs.

0.9.3 beta

2026-09-03

  • The downloaded update installs itself, and says plainly that it has not taken effect until the app is restarted.

0.9.14 beta

2026-09-03

  • Bluetooth asks for the passkey. Pairing no longer sends you to bluetoothctl. Four faults were behind this, and the one that made it impossible was ordering: the code window opened before pairing started, so every code typed was one attempt out of date.
  • After a failed pairing the client no longer dials anyway and announces "Connected" for a radio that never agreed.
  • Administer a repeater over a cable. Identify, read the full configuration, and run the CLI with the dangerous commands gated.
  • The radio search no longer probes — and reboots — a repeater held on a cable. It asks get role once, which a companion radio ignores.

0.9.0 beta

2026-09-02

  • First-run onboarding, and a country question that drives the radio presets.
  • Update checking.
  • Day separators and advert marks in the chat.