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>
Send sheet: opens on what recipients will see (the encoded photo decoded
on this device) instead of the original. "Try another version" encodes
the whole photo again with a near-invisible zoom/shift; the generative
decoder reconstructs each version differently, and on Kodak the best of
three raised CLIP agreement from 0.828 to 0.853. The user picks the
version to send; packet count and airtime follow the selection. Version 1
is byte-identical to the previous encode, so the wire format is
unchanged. The sender's bubble shows the chosen version and carries the
AI-reconstructed label.
Repeater echoes: the raw RX log handler now decrypts GRP_DATA as well as
GRP_TXT and counts repeaters re-flooding each chunk of our own images.
The bubble shows the repeat count like channel text, and Packet info
lists each packet. About 15 s after sending, chunks no repeater echoed
are resent once, but only when another chunk of the same image was
echoed, so senders with no repeater in earshot do not double their
airtime. Outgoing entries now record their payload size.
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>
Message, channel and route histories move from whole-blob preferences to
indexed SQLite rows on native platforms, so chats page from storage instead
of loading a full conversation. Web keeps the preferences store. Existing
histories are imported once on the first launch.
Linux and Windows keep the map tile index in SQLite and import the old JSON
index on first use.
Unreadable legacy data no longer blocks saves, migrations or startup: it is
left in place and skipped. If the database cannot be opened, the run keeps
histories in preferences and the next launch merges them in.
Also adds a performance profiling reference and a script that clears the
Dart HTTP profile.
A colour-only style change (selected, unselected or disabled) only
scheduled a repaint, but the text painter takes its style during
layout, so the label kept its old colour until something else caused a
layout. Request layout for every style change.
Offline (read-only) mode
- The last connected radio is remembered; with no radio the app opens on
its saved contacts, channels, messages and unread counts.
- Main screens stay open on disconnect. A Connect button replaces the
battery and signal indicators, with a sheet to reconnect, choose a
radio or stop a pending reconnect.
- While disconnected everything is read-only: the composer becomes a
"connect to send" bar (drafts kept) and controls that change the radio
or stored history are disabled or hidden.
- Resending while disconnected no longer deletes the message; a
different radio no longer shows the previous radio's channels.
- Notification taps open the saved chat while offline.
Chats and menus
- Channel chat menu: notifications, edit channel, delete channel; the
filter row lines up with the others; bell moved out of the app bar.
- DM and room menus: remove from contacts; rooms get room management.
- Search field uses the full app bar; long-press a result to copy.
- Hashtag channel titles no longer read "# #name"; more room around the
radio activity dot.
- Repeat filter: short messages from one sender are caught at the same
count as long ones.
Layout
- Shared menu row (wraps to two lines) and segment label (never splits
a word) used across the app.
- One Scan button on the scanner; consistent settings tile titles;
contact "last seen" wraps instead of truncating; unfetched repeater
settings are dimmed.
Localization
- New European Portuguese locale (pt_PT); regional locales are handled
by the language picker, notifications and the background service.
- Fill 67 missing strings per locale, including backup and restore.
- Keep "Flood" and "Zero Hop" untranslated, shorten "last seen" and
routing labels, and fix mistranslated scan, theme and hop strings.
- Received-image strings, badge and caption come from translations.
- Regenerate the Czech localizations, which were missing strings.
Docs
- Add documentation/design.md (UI reference) and offline-mode.md;
update channel, chat, navigation and scanner docs.
Routing
- Auto routing picks routes by Thompson sampling over faded delivery
stats (24 h half-life, capped evidence), weighted by what the radio
currently hears; retries prefer a different route; last attempt floods.
- Route failures are held until a message's fate is known, so an offline
contact no longer wrecks its route history; failing routes are only
deleted after a week without a delivery.
- Direct (zero-hop) path is a rotation candidate (#643) and a new Direct
mode in the routing sheet; history routes are used for repeater logins.
- Remove the route-weight sliders the new chooser no longer uses.
Chats
- Bulk selection in channel chats (spam / not spam / delete / copy) and
in the Filtered messages list.
- Tapping a search result jumps to the message.
- Swipe-to-reply ignores vertical scrolls.
- Active conversation follows route lifecycle, so covered chats count
unread again.
Notifications
- Tapping a notification opens its conversation.
- Per-conversation coalescing and one alert per queued-message sync.
- Monochrome status-bar icon; background service stops when the app is
swiped away; stale notifications cleared on radio or slot change.
Other
- Online map: opaque links and painted dots for dense areas to avoid an
Impeller GPU crash; expandable hop list on path maps.
- Contact share: clipboard import of shared contacts, "Add again".
- Android: enableEdgeToEdge and scrolling-screenshot support.
- Translations for all new strings; fix mistranslated routing labels.
Message filter:
- Ignore copies of a message already seen (same sender, text and send
second). Switching between companions re-synced messages the first one
had delivered; they missed per-radio storage dedup and were flagged as
repeats.
- Exempt replies and @[name] mentions from repeat detection.
- New "Sends to count as a repeat" setting (2-5, default 2). Each send
must fall within 10 minutes of the previous one.
- Translations for the new strings in all locales.
Holiday animations:
- Only one plays at a time; greetings arriving while one is playing or
within 5 seconds after it ends are dropped, not queued.
- Christmas map "self" marker: Santa hat was upside down.
- Manual path trace validates the request that will actually be sent
(round trips become 2n-1 hops, 3-byte hops go out as 4-byte prefixes)
against the 172-byte frame and 64-hop firmware limits, and disables Run
with an explanation when it does not fit. PathTraceMapScreen also refuses
to send an oversized request.
- Contact-share tokens are never passed through message translation, so
the share cannot be mangled before sending.
- Czech UI locale (app_cs.arb), selectable in the language picker and as a
message translation language; language names added to every locale.
- Fix wrong language names: Slovak shown as Slovenian in it/ja/pt/sl,
garbled Slovak/Bulgarian in pl, Ukrainian in ru, Hungarian in ko/zh.
- Search inside DM and channel chats across the full stored history, with
highlighted matches; filtered channel messages are excluded.
- Path trace by typed hashes (e.g. A1,B2,C3) from the Contacts and map
menus, without needing node locations; the map trace panel can hand its
hops to it.
- Share contacts in chats using the official app's <pubkey:type:name>
format; received cards have a one-tap Add contact button that reuses the
QR card import path.
- Translations for all new strings in every locale; docs updated.
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>
- Check the Ed25519 signature of every received advert (chat, repeater,
room, sensor) via a shared verifyAdvertSignature helper before it can
add or update a contact; forged adverts are dropped
- Rebuild known contact keys after a full contact sync so nodes the radio
dropped reappear in discovery instead of vanishing from both lists
- Remove unused importContact advert parser
- Rule-deleted snackbar now auto-dismisses (persist: false) and snackbar
actions use a high-contrast colour in both themes
- Add-rule dialog keeps the floating label visible with the keyboard up
- Dismiss focus/keyboard before swapping tab routes
- Repeater status: full-width tiles on phones, no shrink-to-fit values,
multi-part stats on separate lines, drop "0 days" from durations
- App bar titles respect the system font size instead of scaling down;
contacts controls grow with text scale; larger nav labels
- Fix duplicated flood value in Japanese duplicates string
False positives
- Same-sender repeats need at least 3 words and 10 characters, so short
replies ("ok", "test") repeated within 10 minutes stay visible.
- Repeated characters needs a run of 20+ of one non-digit character;
"Noooooooo!", separators, a row of emoji and long numbers are chat.
Correctness
- Rules apply to stored messages: adding a rule hides matching messages
already in the chat, and removing or disabling one shows again what only
it was hiding. Other filter reasons are left alone. Also applied when
history is loaded.
- The filter runs after mesh dedup, inside _addChannelMessage, so each
message is evaluated and counted by the duplicate tracker once.
- Channels excluded from filtering no longer feed implicit clean examples
to the classifier.
- Unread counting and the unread anchor treat filtered messages as normal
when filtering is off for the channel.
Performance
- Classifier training runs in a background isolate (injectable trainer for
widget tests); app start-up no longer waits for it.
- Reply previews look up the quoted message through an id index instead
of scanning the channel per bubble.
- The latest-messages channel sort computes each channel's latest visible
message once.
Cleanup
- Use MessageFilterText.isStructuredPayload instead of a screen copy.
Docs: message-filter.md explains how each check works, including the
learned classifier, and drops the outdated "new messages only" limit.
Client-side filter for channel messages, with no model download:
- User rules on message text and/or sender name (contains, whole word,
exact), normalised for case, accents, zero-width and look-alike letters.
- Automatic checks: repeated characters, same-sender repeats within 10
minutes, and the same sentence (>= 6 words) from 3+ senders within 30
minutes. Windows use send times, so synced history is not a flood.
- On-device n-gram classifier trained by Mark as spam / Not spam taps.
Filtered messages are kept, never notify or count as unread, are not
auto-translated or used for channel previews, and are concealed in reply
quotes. They show as a calm, collapsible placeholder that animates open
and closed, or can be hidden completely. Includes a Filtered messages
list, per-channel toggle, settings screen, translations for all locales
and documentation.
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>
- Themes: name + background + accent, derived surfaces/text/bubbles; editor
with live preview; share codes and .jsonl import/export
- Theme icons: swap tab, send, settings, node avatar and map marker icons for
named icons or pictures (lossless JPEG XL)
- Chat backgrounds per channel/DM (color or JPEG XL picture with fade);
themes can set one, optionally for every chat
- Map follows custom themes (panels, accent, tile tint, markers)
- Holiday themes (Halloween, Thanksgiving, Christmas, New Year's) with
generated backgrounds, icons and map markers; automatic switching from
17 days before each holiday
- Holiday greeting animations (bats, turkeys, Santa, fireworks) matched
across all app languages via translation strings
Repeater settings:
- The Advanced and Identity Keys cards store their expanded flag in
PageStorage. Their TextFields' inner Scrollables shared that identifier,
read the bool as a scroll offset and failed to build, which showed as a
large grey box in release builds. Give each card's body its own storage
scope. Regression test added.
Discovered contacts:
- Adverts parse the two optional 16-bit feature fields before the name,
as MeshCore's AdvertDataParser does, so their bytes are no longer read
as the name (a zero byte gave an empty name).
- A nameless advert or removal no longer wipes a known name.
- The discovery tile gives the name the full width (the type chip beside
it squeezed it to nothing at large text sizes); the type moves to the
key line as plain text, and an unnamed node shows its key prefix.
- The node scan sheet's type chip can shrink instead of the name.
Contrast:
- StatusChip draws its label in the normal text color; the icon or dot
keeps the accent, adjusted to 3:1 against its tint. Avatar icons and
initials get the same adjustment. Amber on its tint in the light theme
was about 2:1.
Channel chat:
- Hashtag channels drop the redundant "Hashtag" subtitle label, and the
region action moves into the overflow menu (tapping the title still
opens it) so the channel name keeps its room.
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>
Repeater settings:
- Each setting is declared once in repeaterSettingSpecs (key, section,
input type, range, step, labels); the screen builds its control,
refresh and save command from that list.
- Add flood.max.advert, flood.max.unscoped, rxdelay, cad, adc.multiplier
and extra.sf. adc.multiplier and extra.sf note their hardware limits
(extra.sf is LR2021 only and its get reply has no "> " prefix).
- Settings can be edited before they are fetched; only edited ones are
sent. set radio needs freq, bw, sf and cr together, so a missing one
is reported instead of silently skipping the radio.
- Check tx delays against the firmware's 0-2 range.
- Keep the not-loaded hint's list slot so the Advanced card doesn't
collapse when the first value arrives.
- New "Auto-fetch repeater settings" app setting, off by default: each
get is a LoRa round trip.
Fixes:
- Adding a discovered contact sent its advert time as lastmod, making it
the oldest contact; with overwrite-oldest on a full table the next add
evicted it and it reappeared in the discovered list. Let the radio
stamp its own clock.
- Snackbars replace each other instead of queueing.
Translations: add the new strings in all locales and fix widespread
mistranslations in hu, ko, sk, sl and uk.
- Record delivery observations with the path of the attempt the ACK
belongs to, and skip ambiguous ACKs, so a late direct ACK is not
learned as a flood delivery.
- Remove secondsSinceLastRx from the timeout model: it measured time
since any companion frame, which was near zero at train and predict.
- When a contact's path history is full, evict the lowest-scoring path
instead of silently dropping new discoveries.
A background retry's RESP_CODE_SENT arriving while the path was being
prepared was taken as the telemetry request's ack, so its tag and timeout
replaced ours and a sensor's tagged reply was rejected.
Writing the telemetry time into lastSeen sent the phone's clock back to
the radio as the node's advert timestamp on the next path or flag write,
which could later make the radio's record look newer and drop the fix.
The fix now records its own telemetryFixAt and leaves lastSeen as the
advert time; the map and lists show the later of the two as last heard.
A full contact sync (pull to refresh, reconnect) cleared the list before
the radio resent it, so fixes were lost even for an unchanged advert.
They are now held for the sync and restored onto matching records.
Contact rows give the name its own line (wrapping to two) with route and
last seen below, right-aligned on wide windows. Fixes overflows found by a
new widget test that renders every screen at 320x568 with text scales up to
2.0 and on a desktop window: region dropdown, contacts list, repeater CLI,
status grid and settings card, map cache buttons, and empty states.
Dropdowns truncate long labels, and option sheets and dialogs scroll.
Telemetry replies carried a GPS fix that was only shown on the telemetry
screen, so the map kept the node at its last advert position. The fix now
updates the contact and survives radio contact refreshes until the node
adverts again (compared on the node's own advert clock). The map node card
gains an "Update location" button for companions and sensors; repeaters
and rooms only share GPS with logged-in admins, so they don't get it.
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>
Every received packet copy re-saved its channel's whole history, every
unread change re-saved the channel list, and adverts/path records re-saved
full contact and path-history blobs. Under load the SharedPreferences
backlog starved the Dart event loop (frames and timers stopped), the radio's
offline queue overflowed, and CPU stayed pinned after traffic ended.
- Add CoalescedWrites: keeps the latest write per key and runs them once
per window (750 ms; 5 s for path history). Writes start synchronously so
stores still read the current scoped key.
- Flush before the app is backgrounded, on disconnect, before switching
radios, before the channel slot map changes, before channel history
reloads, before deleteChannel drops a list, and before path history
reloads an evicted contact.
- Cap in-memory channel history at ChannelMessageStore.maxStoredMessages;
storage already kept only that many, but the list grew unbounded during a
session and every save grew with it.
- Cache Contact.publicKeyHex and build pubKeyToHex from a hex-digit lookup; it was
rebuilt on every equality/hash and per-advert contact scan.
Load test (fake TCP radio, 350 contacts, 17 channels, 10-150 packets/s,
Linux profile build): CPU at 10 packets/s 104% -> 45%, recovers to idle
after traffic instead of staying at 160%, and queued messages drained went
from 555 to 3237 over the same run.
A name with invalid percent-encoding (e.g. name=%FF) made
Uri.queryParameters throw from the scanner's validator. The parser now
returns null for it, with a regression test.
Update the channels and additional-features guides for the renamed
"Scan a QR Code" option, the supported channel link format, and its
limits.
The QR scanner only read community codes, so the standard
meshcore://channel/add?name=...&secret=... links used by the official
app and sites like ipnt.uk were rejected as invalid community codes.
The scanner now also accepts channel links. It skips channels already on
the radio, asks before adding, and only uses a free slot after the
channel sync has finished. Also fills in the 59 untranslated strings in
all 17 locales.
Fixes#604