OTA docs: meshcore-tth and its -ota images are experimental, not for regular users
build / ci-image (push) Successful in 13s
build / build (push) Successful in 11m0s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
tthandClaude Opus 5.5 committed 2026-11-17 01:56:56 +01:00
1 parent 233e6bb6d3
commit 8939cef7c1
2 files changed
+12 -1

No files matched your search

+4 -1
View File
@@ -53,7 +53,10 @@ in this README describes upstream and still applies.
*Firmware update (OTA)*, for nodes on an `-ota` image of
[meshcore-tth](https://git.rfa.cz/tth-pub/meshcore-tth): the delta for the
node's image comes from the latest release by itself; optionally on a side
channel, off the shared mesh. See
channel, off the shared mesh. **Experimental, not for regular users:**
meshcore-tth and its `-ota` images are a rolling release on MeshCore `dev`
(about twice a day, no stable channel, no rollback), for nodes you can
reach. See
[documentation/ota-updates.md](documentation/ota-updates.md).
- **Fix:** `shared_preferences_android` pinned to 2.4.28 — 2.5.0 crashes on
start under R8 (black screen).
+8
View File
@@ -7,6 +7,14 @@ against the image the node runs, the node checks it and rewrites itself.
Classic MeshCore firmware has no such command; the tile is there, but the
update stops with "not an -ota build".
> **Experimental, not meant for regular users.** meshcore-tth is a personal
> development fork, and its `-ota` images track MeshCore `dev`
> and a new release comes roughly twice a day; there is no stable channel, no
> second bank and no automatic rollback. A bad image that still boots runs
> until you push the next one; one that does not boot needs USB/BLE DFU in
> hand. Update only nodes you can reach, and try each release on one of them
> first. Details: [docs/ota.md](https://git.rfa.cz/tth-pub/meshcore-tth/src/branch/main/docs/ota.md).
## How to
1. Log in to the repeater as **admin** (Contacts → long-press → Manage).