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.
- Channel chat: when the message filter hides or collapses loaded messages
and the list is too short to scroll (so the load-older trigger can't
fire), load older pages automatically until it can scroll, storage runs
out, or 20 pages have loaded. Past that cap an empty channel offers a
"Load older messages" button instead of a dead end.
- Notifications: incoming channel messages notify after awaiting
translation; marking one as spam meanwhile replaced the stored copy but
not the captured one, so the spam still notified. Check the stored
message's filter state before notifying.
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.
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.
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.
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.
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.
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.
'Show link images in all chats by default' (default off) applies to
every channel and contact without an explicit per-chat choice: the
per-chat setting is now unset/on/off and resolves to perChat ?? default.
The 'Load images from links' master switch still overrides it.
Keep refreshing channels before clearing so in-flight queue messages
can't write the history back, but decide whether the channel is still
held while ignoring the deleted slot, and clear even if the refresh
fails or is incomplete.
The firmware's CMD_ADD_UPDATE_CONTACT adds the key when it isn't in the
contact table. Screens that stay open after a contact is removed (e.g. a
repeater admin screen after the repeater's keys were changed and the old
contact deleted) sync the path before every send, so the next command,
status or telemetry request silently added the old contact back. Skip
path and flag writes for contacts no longer in the contact list.
removeContact now waits for the radio's reply and only drops the contact
locally when the radio confirms (or reports it doesn't have it), so a
lost command no longer leaves a contact that the next sync restores.
Failures are shown to the user. The delete dialog warns when the radio
auto-adds that contact type, since the contact returns on its next
advert.
- Detect mentions on the original text, as @[name] or a whole-word @name
- Save and restore the full mode map in review mode
- Open the mode picker from the chat bell and show the mode in its tooltip
- Share one mode picker sheet; fix the stale sheet context
- Persist modes by name and skip unknown entries
- Keep writing muted_channels so older builds keep the user's mutes
- Remove the muteChannel/unmuteChannel/isChannelMuted shims
- Update notifications docs to match the behaviour
- Respect the notifications-enabled setting
- Notify only the lowest newly crossed threshold
- Ignore implausible readings (boards without a battery sensor report 0 mV)
- Wait for the device identity so the saved chemistry is used
- Require two consecutive low readings before alerting
- Re-arm and clear alerts on any link reset, not just explicit disconnect
- Cancel stale notifications on re-arm and link reset
- Scope notification ids per device and name the device in the body
- Use the connector's shared NotificationService
- Presets no longer reset the path hash size; the unused preset field is gone
- Confirm the new path hash size from the refreshed DEVICE_INFO and show a
specific error when the radio does not apply it
- Log path hash size with the other radio settings and on manual edits
- Add MeshCoreConnector.supportsPathHashMode and use it in both screens
- Use the same 0-2 mode values and helper text as the other selectors
- Add channels_notifyAll, channels_notifyMentionsOnly, channels_notifyNone to all 18 language ARB files
- Add channels_notificationSettings to all ARB files for consistency (was missing in 16 languages)
- Remove redundant "(@)" suffix from mentions only mode
- All translations verified for accuracy
- Special fix: Slovak "Iba spomienky" -> "Iba zmienky" (mentions, not memories)
- Update all localization Dart files via flutter gen-l10n
- Update documentation table with proper icons
- Update untranslated.json
- Add ChannelNotificationMode enum with all, mentionsOnly, muted options
- Replace mutedChannels Set with channelNotificationModes Map for per-channel settings
- Add mention detection for @username in channel messages
- Update channels list and chat UI with notification mode selector
- Add localization strings for new notification modes
- Automatic migration from old mutedChannels to new system
- Update user documentation
- Preserve backward compatibility with existing mute/unmute API
- Opt-in upload of header-only packet records and repeater/room server
adverts to map.meshcoreopen.org about once a minute; payloads, channel
and DM hashes and transport codes are stripped on the phone, locations
snapped to a ~2 km grid, install ID rotates daily
- One-time opt-in dialog on first radio connection; toggle and status in
App settings
- Local / Online / Both switch on the map screen with online repeater
hexagons, links, add-to-contacts and manage
- Node purchase banner on the connect screen (affiliate link, disclosed)
- Privacy policy and network map documentation
- Translations for all locales
- Image entries are stamped with their channel ID before the migration is
marked done, so an interrupted run repeats it instead of leaving them
unstamped (and invisible) forever.
- Channel message/data frames that arrive before this session's slot map
is confirmed are held and replayed once it is. Current firmware only
sends them in reply to SYNC_NEXT_MESSAGE, which already waits; this
guards against a stale saved map filing them under the wrong channel.
Channel messages, settings, region, order and images were persisted by
radio slot index, so a slot reused for a different channel inherited the
old channel's history and settings (#359).
- Channel.storageId: first 8 bytes of SHA-256("meshcore-channel:" + psk).
- All per-channel stores key by channel ID; in-memory state stays by slot.
- The connector keeps a slot -> channel ID map, diffs it against the saved
map on every channel sync and reloads slots whose channel changed.
- Queued channel frames wait until this session's map is confirmed.
- One-shot per-radio migration from slot keys, using the cached channel
list the legacy data was written under; rerun-safe if interrupted.
- Deleting a channel clears its data; a channel removed elsewhere keeps its
history and gets it back when re-added. A PSK edit keeps its place in
the custom order.
- Slots sharing a PSK share history and settings.
- Image entries record their channel ID; a slot change resets that slot's
in-progress reassembly.
- Extract reusable widgets (chat composer/send pipeline, message bubble
frame, reaction chips, path map scaffold, radio settings dialog,
translation settings section, map POI clusters, nav tiles, etc.) and
slim down the screens that used them
- Map: hide/remove markers with restore, confirm before setting node
location, POI clustering, semantics labels
- Map cache: cancellable downloads and a bulk tile limit
- Repeater: unsaved-changes guard, CLI search/copy/share transcript,
framed-command debug preview, disconnected banner
- Confirm before clearing chats and debug logs
- Keep cached unread totals in sync on per-contact/channel updates
- Move remaining hardcoded strings into l10n and translate the 98 new
keys into all 17 non-English locales
Merge dev (#588 share location, #436 discovered-contact import/export)
into fix/review-fixes-and-issue-batch. Conflicts: keep the node-scan
button alongside dev's import/export menu; take dev's marker label
prompt.
Share location (#588):
- Never share a missing or 0,0 radio position; hide the chat action and
show "Your radio has no location set"
- Sanitise marker labels ('|' -> '/', newlines -> spaces) on every path
- One shared MarkerLabelDialog owning its controller/focus node, with
keyboard submit, replacing three copies
- Map pins default to "Point of interest" again; "Share my location"
uses the node name
- Location shares honour the send cooldown and handle send errors
Discovered-contact import/export (#436):
- Per-entry decoding with imported/skipped/invalid counts; reject keys
that are not 32 bytes; skip in-file duplicates and the radio's own key
- Strip routing paths on import and stop exporting them; clamp future
timestamps; enforce the discovered-contact cap; require a connection;
2 MB file limit
- Export via in-memory XFile (fixes web); pass sharePositionOrigin for
iPad (also GPX export and image save); macOS user-selected read-write
entitlement for save dialogs
Docs: cover share location, import/export, node scan, TCP reconnect,
channel auto-resend options, arrival ordering, badge, password length
and image limits.
Translations for all new strings in every locale.
Resolve pubspec.yaml conflict (keep dev's share_plus ^13.3.1 and
file_selector), regenerate localizations, and add the missing
map_labelUpdateHint translation for all locales.
Review fixes:
- Keep stored message history beyond the 200-message window; stop
messages leaking between radios; reset link/session state on disconnect
- Accept firmware's 176-byte RX frames over USB/TCP
- Hold APP_START during contact sync; contact-sync watchdog; replay DMs
from not-yet-known senders; tombstone late command replies; finish
channel sync on ERR_NOT_FOUND; fail region-scoped sends cleanly
- DM retry watchdog when RESP_CODE_SENT never arrives; late repeater CLI
replies; ACK hash collisions; UTF-8-safe name truncation
- Image pipeline: delete-during-decode, lifecycle cancels, decoder memory
release, entry cap, dead worker recovery, atomic model writes
- Storage: deterministic reaction hash across web/native, Smaz
double-decode, per-entry parsing, per-radio path history and regions,
review-mode data isolation
- UI: safe channel slot selection, byte-length name limits, double-send
guard, mounted checks, localized hardcoded strings
- Skip persisted-store reload on repeat SELF_INFO
Features:
- Radio default flood scope (firmware ver 11+) and explicit unscoped
sends (ver 12+)
- Scan for nearby nodes (#570)
- Optional distinct first-hop repeater counting for channel resend (#589)
- Optional region next to hop count (#580)
Issues:
- Message text follows system font size (#569)
- Repeater/room password field accepts 20 chars (#576)
- TCP auto-reconnect and keepalive (#571)
- Order feeds by local receive time; flag future timestamps (#584)
- Coding rate help text (#568), French "Favoris" (#575)
- iOS/macOS app badge now clears
Translations for all new strings in every locale.
- Default evictDiscoveredContactsEnabled to true so the 500-entry cap stays
in effect unless the user opts out
- Evict until under the cap when adding, so an oversized list recovers
- Pass the cap into the localized subtitle instead of hard-coding 500
- Fix German title and subtitle wording
- Save: block double taps, send radio config first, show an error if
persisting the setting fails
- Restore untranslated.json to match dev
Store reviewers have no MeshCore radio, so they could not reach any
screen past Connect or test the Android Auto messaging notifications.
- Long-press the "MeshCore Open" title on the Connect screen to enter
review mode on any platform
- A simulated radio speaks the companion protocol as a fourth transport,
so sync, messages, ACKs, notifications and notification replies run
through the normal code paths
- Seeded contacts, channels and history; a new incoming message every
45 s, auto-replies a few seconds after sending, and a banner with
"Send test message" and "Exit"
- Review data uses its own fixed key scope and is cleared on entry, exit
and at startup; the review scope never adopts legacy unscoped keys,
and channel mutes changed during review are restored
- Code lives in lib/review_mode/ with tests in test/review_mode/
- Message notifications use Android MessagingStyle with Reply, Mark as read,
and Mute channel actions, so they work in Android Auto and on watches
- Replies go through the normal send path (length limits, SMAZ, Cyr2Lat,
retries), split into up to 3 messages, and report failures
- Declare Android Auto notification support and register the action receiver
- Add a bell icon to channel chat to mute/unmute; unify the channel mute key
so unnamed channels mute correctly
- Update README and docs for Android Auto support
floodScopeKeyForRegion treats `foo` and `#foo` as the same scope, so a
region listed both ways matched every packet twice and was always reported
as ambiguous. Also consider the default region when resolving.
- Updated LoRa airtime calculations in `lora_airtime_test.dart` to reflect new reference values.
- Introduced new tests for LDRO behavior and preamble symbol calculations.
- Added `contact_path_width_test.dart` to validate path hash width handling in contacts.
- Enhanced `model_changes_test.dart` to ensure legacy data migration works correctly.
- Created `remote_node_stats_test.dart` to decode and validate remote node statistics.
- Implemented `map_marker_parse_test.dart` for parsing marker text with coordinate validation.
- Developed `map_tile_cache_key_test.dart` to ensure API keys are excluded from cache keys.
- Added `message_retry_failure_test.dart` to test message retry service behavior on failures.
- Extended `path_history_service_test.dart` to preserve learned state across path attempts.
- Enhanced `received_image_store_test.dart` to handle concurrent writes and review fixes.
- Implemented `repeater_command_service_test.dart` to validate command response handling.
- Created `store_tolerant_parsing_test.dart` to ensure stores skip malformed records gracefully.
- Cleared untranslated JSON file for localization updates.