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>
BETA-99.0.0 segfaults when a USB companion transmits as soon as the port
opens, and the Linux release fails to load on Ubuntu 24.04 and Linux
Mint 22 (glibc 2.39). Fixes#600.
fl_open starts SerialThread before Dart installs fl_set_callback. A Seeed
Wio Tracker L1 sends bytes immediately, and the reader called that null
pointer (segfault at ip 0, FlSerial+0x44b8). Vendor MeshEnvy/flserial
e1864de under third_party/flserial. That is the 0.3.5 FFI API this app
already calls (openPort, setCallback, setByteSize8, setDTR), not official
grzesl/flserial 0.7.3. The reader waits until the callback is set, and
the port mutexes are initialized before the thread starts. Merging this
makes zjs81/meshcore-open the owner of that vendored copy.
The release libflserial.so needed GLIBC_2.42 for cfsetispeed and
cfsetospeed, so USB discovery failed on glibc 2.39 before the port
opened. Bind those symbols at GLIBC_2.2.5 and pass the legacy baud values
those symbols expect. 115200 is octal 0010002. glibc 2.42 turned the B*
macros into plain numbers, so passing 115200 to the old symbol would
select the wrong rate.
flutter_onnxruntime 1.9.0 needs libonnxruntime.so.1 from ONNX Runtime
1.28.3. The zip did not ship that file, and the plugin RUNPATH was the
build machine's download directory. The loader uses the plugin path for
this library. The install copies libonnxruntime.so, .so.1, .so.1.28.3,
and libonnxruntime_providers_shared.so into bundle/lib. The plugin build
RPATH is $ORIGIN followed by the download directory: $ORIGIN is bundle/lib
at runtime, and the download directory is what ld needs while linking.
Dropping it makes the release link fail. The executable keeps DT_RPATH
$ORIGIN/lib for its own plugins.
Checked on Ubuntu 26.04.1 (glibc 2.43) with Flutter 3.47.7. Opening
/dev/ttyACM0 at 115200 set both termios2 speeds to 115200 and delivered
data after fl_set_callback (last length 402). The built libflserial.so
has no GLIBC_2.42 requirement. flutter build linux --release succeeded.
With the plugin's absolute build path removed and LD_LIBRARY_PATH unset,
ldd resolved libonnxruntime.so.1 from bundle/lib.
- Uploads carry a consent generation: nothing is sent if sharing is
turned off while a batch is being prepared, and a late response never
touches a queue that was cleared and refilled
- Parse only the signed 32 advert app-data bytes, as the firmware does,
so appended unsigned bytes can't add the hidden marker or change the
name
- Split online map requests that cross the antimeridian into two valid
boxes and merge the results
- README: link the network map next to the website
- 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.
Outgoing image entries were excluded from the maxEntries cap, and age
eviction only marks them evicted, so frequent senders accumulated entries
and sidecars without bound. Outgoing entries with nothing left on disk (or
failed) are now eligible, oldest first.
Rename _ChannelChatRow.timestamp to receivedAt: it already returned the
local arrival time used for sorting and day separators.
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
- Lift the QR scanner's torch and camera controls above the navigation
bar instead of 16 px from the screen edge
- Use light system bar icons on the black QR camera and received-image
viewer, and keep Android's contrast scrim behind three-button
navigation for any other dark route
- Note that Flutter only applies edge-to-edge from Android 10
- Opt Android 14 and older into edge-to-edge so every version lays out
the same way Android 15+ already enforces, and make the navigation bar
transparent (its color is ignored on Android 15)
- Raise minimum versions for packages with relevant fixes:
flutter_blue_plus 2.3.14 (Android connection-state fixes),
mobile_scanner 7.4.2 (scanner stall and camera-start crash fixes),
flutter_map 8.3.2 (crash on NaN marker coordinates),
flutter_onnxruntime 1.9.0 (ONNX Runtime 1.28), share_plus 13.3.1,
flutter_cache_manager 3.4.5, flutter_local_notifications 22.3.1,
package_info_plus 10.2.2
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/