Login, `ver`, `fw status` (and `fw ver` for the release lookup), then the
outcome: "up to date: the node already runs <tag>, no update needed" or
"update available: <tag>, delta N B", with the node's version on top. It
stops before `fw begin` and before the side channel, so no chunks go on air.
OtaTransfer.checkOnly, OtaState.available; OtaResult carries the release
tag and the `ver` reply.
Refs #28
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
documentation/ota-updates.md: how to, options, the side channel, what the
node checks, and where the reference implementation lives. README: the
fork's feature list and its fork-only files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With no file chosen, the node's target (`fw ver`) and image (`fw status`
/ `fw base`) pick the delta from manifest.json of the latest public
release on git.rfa.cz; it is checked against SHA256SUMS (the node checks
the manifest signature itself). Choosing .mcfw files stays for own
builds.
Bench 16. 11. 2026: a node on v1.18.0+tth.20261115.2 got the delta to
20261116 found and downloaded by the app, over the side channel.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A "Firmware update (OTA)" tile in the repeater hub (admins, tth fork
switch kOtaUpdate) pushes a delta of a meshcore-tth -ota image over the
mesh: the package that starts from the node's image is picked from the
chosen .mcfw files, binary chunks with text as the fallback, an airtime
budget, verify and apply. Optionally on a side channel: the node goes to
another preset by tempradio, the companion follows (checked), the chunks
go zero-hop and both come back at the end.
A port of the reference engine of the tth.meshcore Ansible collection
(module_utils/meshcore_ota_engine.py); test/services/ota/ota_vectors.json
is its test-vector file. Bench 16. 11. 2026: the connector over TCP to a
USB companion, side channel 866.0/SF7, applied a 2.7 kB delta, 20 s
airtime, companion back on its preset.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Conflicts resolved by hand, our fork changes carried over:
- MainActivity.kt: keep the unread widget hooks next to upstream's
scroll capture (attach and detach both).
- app_settings_screen.dart: upstream wrapped the list in
MeshSettingsTileTheme; image-message and translation sections stay
gated on kOnDeviceMl (ML-free build).
- channel_chat_screen.dart: upstream split build() into methods; took
theirs and re-applied the terminal-theme list padding.
- chat_composer.dart: both imports (terminal_theme, radio_guard).
- mesh_nav_tile.dart: upstream's meshTileTitleStyle, with the smaller
terminal-theme title kept.
flutter analyze clean, flutter test 1522 passed (CI image, local).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream od 6. 11. pinuje environment.flutter na 3.47.9 a pub get jinou
verzi odmítne; cirruslabs/flutter vyšel naposledy jako 3.44.0 (květen).
Základ zůstává kvůli Android SDK a Javě, SDK Flutteru se nahradí
oficiálním tarballem připnutým sha256. Obraz 4,5 -> 7,5 GB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Konflikt v lib/screens/channel_chat_screen.dart: upstream přidal do
_buildMessageBubble parametr showFilterBanner (filtr spamu), my tam máme
terminálový styl. V terminálovém režimu se banner (není spam / skrýt)
vykreslí nad řádkem zprávy, jinak by filtrované zprávy přišly o akce.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream's theme system (two-color custom themes, holiday themes, picture
icons, chat backgrounds) next to the tth terminal theme:
- a user's custom theme wins; without one, themeMode 'terminal' is still
the dark theme (main.dart);
- MeshTheme.buildFrom (terminal base) builds with the stock bubble, icon
and map extensions, like dark()/light();
- terminal avatars also show a theme slot's glyph; the bottom bar stays
44 px without labels in the terminal theme, 76/60 otherwise;
- map overlays: terminal panels stay square and black, otherwise
upstream's palette/follow-theme logic; channel list keeps the terminal
padding.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the NDKs baked in the CI image was 14 G in grg-runner's 48 G
RAM-backed image store: it filled the store (run 54264, Gradle "No space
left on device") and the runner cleanup evicts such images under
pressure, so it would have been rebuilt most runs.
The image is now Flutter + node + cache paths only (seconds to build);
the SDK packages Gradle installs (NDKs, CMake, build-tools, platform)
are their own actions/cache entry, stored on the runner's disk, keyed by
the Gradle build files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every build started from the bare Flutter image: Gradle installed two
NDKs, build-tools, platform 35 and CMake (~4 min) and resolved all its
dependencies from scratch (assembleRelease 13-17 min).
.gitea/ci/Dockerfile adds those SDK packages, the Android engine
artifacts and node (for JS actions). The ci-image job builds it into the
Docker of the big runner, tagged by the Dockerfile hash, and reuses it
otherwise. actions/cache keeps the Gradle home (with the build cache on)
and the pub cache. The build warns when Gradle still installs an SDK
package, i.e. when upstream moved to a new NDK.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Conflict in repeater_settings_screen.dart: upstream #614 made the
fetch-on-open of the settings screen opt-in (autoFetchRepeaterSettings,
off by default) - what our kFetchRemoteOnOpen did there. Take upstream's
setting so its toggle works; kFetchRemoteOnOpen stays for status,
telemetry and neighbours.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream made publicGateway a required parameter of
MessageUrlImageFutureBuilder; the terminal-theme bubbles in chat and
channel chat are ours and did not pass it, so the merge did not compile.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Conflicts: the manifest keeps our unread widget receiver and drops the
Android Auto meta-data, which upstream moved to the androidAuto source set
(fe7e72a). Rename detection had moved our unread_widget_info.xml into that
source set with it; it stays in main. _mapChip is gone upstream with the
map overlay declutter (ed5884e), so our terminal-theme restyle of it goes
too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The third line reads "cmp off" (amber) when the companion is
disconnected and "app off" (red) when the app is closed: at once from
MainActivity.onDestroy, or when the bridge's 5-minute heartbeat has been
missing for 15 minutes (process killed). The widget now refreshes every
30 minutes so it notices the latter. Counts dim while the app is off.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Opening a repeater's settings, status, telemetry or neighbours no longer
sends anything over the mesh; each screen waits for its refresh button.
On the settings screen alone the fetch-on-open was a dozen CLI requests,
every time it was opened. Switch: kFetchRemoteOnOpen in lib/tth_fork.dart.
The node's own telemetry is local and still loads on open.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A terminal-style Android widget (UnreadWidget.kt):
dm 3
ch 12
bt 87%
Counts turn green when non-zero, the battery red at 20 % and grey when
the companion is disconnected (last known level kept). Tapping opens the
app. HomeWidgetBridge pushes the values over a method channel only when
they change; they are kept in SharedPreferences so the widget survives
the app being closed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The contacts/channels/map switch bar loses its rounded corners, labels
and 16 px of height; the map's search field, zoom column, legend, stats
and source switch become square black panels. Node markers stay round.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
In the terminal theme only:
- MeshCard becomes a flat row with a rule underneath: no margin, no
corners, 8/4 padding. Channel and contact lists, settings groups and
every other card shrink to about half their height.
- AvatarCircle is just the glyph (icon or initials, at most 20 px), the
contact emoji avatar likewise.
- MeshNavTile and SectionHeader: smaller icons, padding and type.
- Text line height 1.2 instead of Material's 1.4-1.5.
- A reply in a channel is one dim line above the message,
"↳ <nick> quoted text…", instead of the boxed preview; the
"replying to" banner above the composer loses its padding.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A fourth theme choice "Term" next to System/Light/Dark:
- black surfaces, green accent, JetBrains Mono, no rounded corners,
compact density and paddings, no ink splash (lib/theme/terminal_theme.dart,
built on MeshTheme's dark theme with the shapes overridden);
- channel and direct chats render each message as one IRC line across the
whole width: "14:02 <nick> text [2 hops] ✓", no avatar, no bubble, own
messages on the left too. Route, region, repeat and delivery status
follow the text inline; the tracing path stays on its own line.
The upstream bubble code is untouched: both chat screens branch to a
separate builder when MeshStyle.of(context).terminal, so the nightly
upstream merge does not collide with it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- GifMessage gets autoLoad; chats pass their "images from URLs" switch
(off by default), so a received GIF code no longer fetches from Giphy
until tapped. Reply quotes follow the channel setting.
- Translation and image-message settings are hidden (kOnDeviceMl in
lib/tth_fork.dart): without the native runtimes they cannot work and
their buttons would only download models of up to 835 MB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5.0 (Pigeon JNI) reaches SharedPreferencesApiRegistrar.getAll only
through JNI, R8 strips it, and the app dies with NoSuchMethodError
before the first frame (black screen). Verified on a phone: 2.4.28
starts normally.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.gitea/workflows/build.yml merges upstream dev, runs the tests, builds
a signed arm64 APK in ghcr.io/cirruslabs/flutter and publishes a release
for Obtainium (one per HEAD, newest 5 kept). upstream-sync.sh is the
shared copy from the other forks; setup-signing.sh creates the key and
stores it as CI secrets. README gets an Obtainium QR code.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace llamadart, flutter_onnxruntime and flutter_langdetect with
API-compatible stubs via dependency_overrides, so llama.cpp, LiteRT-LM
and ONNX Runtime are not packaged. Translation and the neural image
codec become unavailable; both are off by default upstream.
Also drop non-arm64 prebuilt plugin libraries at packaging time.
APK: 340 MB -> 39.5 MB, flutter test 909/909 passing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>