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.
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.
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>
pubspec.yaml now pins environment.flutter to 3.47.9, so pub get refuses
other SDKs. Every CI job reads that pin via flutter-version-file,
including the web deploy (was 3.41.2). The AppImage SDK pin moves to
3.47.9 and CI fails if it drifts from pubspec. The Nix shell no longer
bundles Flutter, since nixpkgs only packages 3.47.4; it warns when the
SDK on PATH is missing or the wrong version.
Flutter 3.47 is reported to fix the Impeller/Vulkan crash in
Canvas::GetLocalCoverageLimit (flutter#190919) seen on Pixel 10 and 11
with the 3.44.1 engine. 3.47.8 also updates Dart's root certificates.
pub get on 3.47 adds platform-folder excludes to flserial's analysis
options.
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>
Translation runs GGUF models on llama.cpp. llamadart 0.8.20+ also bundles the
LiteRT-LM runtime, whose iOS GemmaModelConstraintProvider.framework requires
iOS 26.4, so App Store Connect rejects 16.4 builds (ITMS-90208).
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
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>
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.
- 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
share_plus cannot share files on desktop: the Linux implementation throws
UnimplementedError('Sharing files not supported on Linux') unconditionally
(share_plus_linux.dart:22), and Windows throws for builds older than
10.0.17763. exportGPX() swallowed that in its catch-all, so every GPX
export on Linux ended as gpxExportFailed with the file already written to
the documents directory and never cleaned up.
On desktop, write the file where the user asks via file_selector's
getSaveLocation() instead of routing it through the share sheet; a
dismissed dialog maps to gpxExportCancelled. Mobile keeps the share flow.
Verified on Linux with a standalone probe app: SharePlus.share with files
throws UnimplementedError, while getSaveLocation returns the chosen path
and the GPX file is written there.
close(2) on a tty whose output the peer never drained blocks in the
kernel for the line discipline's closing_wait (measured 30.4s on Linux
against a CDC-ACM device that never reads its bulk OUT endpoint, e.g. a
MeshCore board flashed with a BLE-only companion build). FlSerial's
closePort() is a synchronous FFI call, so the whole app froze for that
window on every failed USB connect and on disconnect.
fl_close() only touches process-global native state, so run it through
Isolate.run() and replicate the Dart-side cleanup closePort() does
(stream close, calloc'd I/O buffers, flh reset). Log when the close
exceeds 1s so the "device is not draining" case is visible in the debug
log.
Verified against the wedged device: inline close blocked the calling
isolate for 30476ms with 0 timer ticks; the isolate close took 30302ms
with 302 ticks, i.e. the main isolate stayed responsive throughout.
MeshCoreOne is a companion app that supports emoji reactions, using a
different message format than ours.
This commit adds support for parsing and displaying reactions received
in the MeshCoreOne format.
Their format is described here:
https://github.com/Avi0n/MeshCoreOne/blob/main/docs/Reactions.md
Here's an example:
👍@[entropy]
b3je6qf7
Major differences compared to MeshCore-Open's reaction messages:
- includes the emoji, rather than an index code
- includes the name of who sent the message it refers to
- the hash does not depend on the sender name
- Created a new ExportOptions.plist file to define export settings for app distribution.
- Configured the plist with method, team ID, signing style, symbol upload option, and destination.
This adds a simple UI in repeater management settings for remotely
setting a repeater's private key. A key can be pasted from an external
key generator, or a random one can be generated here, optionally with a
specified prefix.
If a prefix is specified, searching is done in 30ms batches in order
to keep the UI responsive and show the progress indicator animation
smoothly. Searches can be interrupted. An estimation of search length is
given as expected number of generated key pairs. (A future improvement
would be to observe keys per second performance and give time estimates
based on that.)
When it generates a new private key on your behalf, it can tell you
what the corresponding public key will be. Unfortunately, if you paste
one in from another source, it can't compute the corresponding public
key. This is because the standard Dart crypto library doesn't provide
that capability, nor does it give access to the elliptic curve functions
it implements so we could do it ourselves. Our only recourse would be to
copy the source for all those things, and I didn't think it was worth
it.
This will not check the validity of a pasted key, but the remote
repeater will. It does limit it to the correct length and hexadecimal
charset.
Prefixes are limited to 4 characters. There's no technical reason for
this, but users are unlikely to want more, and I think it would just be
a bad experience to allow more and spin for a very long time. If someone
really wants a longer one, they can use an external generator like they
do now.
Possible TODO: rewrite background processing using isolates.
Closes#142.
- Added new localization strings for Swedish, Ukrainian, and Chinese languages in app_sv.arb, app_uk.arb, and app_zh.arb respectively.
- Enhanced the path map UI in channel_message_path_screen.dart for better readability and interaction.
- Improved message retry logic in message_retry_service.dart to prevent double-pumping of queues.
- Bumped version number in pubspec.yaml to 9.5.0+13.
- Cleared untranslated strings in untranslated.json to reflect current localization status.
- Implemented contactTypeIcon and contactTypeColor functions for better UI representation of contact types.
- Created colorForName and firstCharacterOrEmoji functions to enhance contact display.
- Developed PathEditorSheet widget for managing contact paths with a user-friendly interface.
- Introduced RoutingSheet for managing contact routing modes and displaying path history.
- Added a script for generating proof of concept (PoC) payloads for clipboard contact import validation.
- Introduced translation functionality in chat screen, allowing users to translate messages before sending.
- Added MessageTranslationButton to the input bar for enabling/disabling translation.
- Implemented translation service to handle incoming and outgoing text translations using llama models.
- Enhanced message storage to include original and translated text, language codes, and translation status.
- Created UI components for displaying translated messages and managing translation options.
- Added translation model management, including downloading and storing models locally.
- Updated app settings to manage translation preferences and model selections.
- Implemented radio statistics features in multiple screens including chat, channels, and settings.
- Added localization for new strings in Swedish, Ukrainian, and Chinese.
- Introduced a setting to jump to the oldest unread message in chat and channels.
- Enhanced path management and display for contacts and messages.
- Updated app settings to include new boolean for jumping to the oldest unread message.
- Improved battery indicator and radio stats display in the app bar.
- Removed unused wakelock_plus dependency and updated plugin registrations.
Add Linux BLE pairing helper that drives bluetoothctl for pair/trust/PIN
entry, with Completer-based flow control, explicit retry loop, and named
timeout constants.
- LinuxBlePairingService: pair-and-trust with up to 2 retries
- LinuxBleErrorClassifier: map bluetoothctl stderr to user-facing errors
- Conditional import stub for web builds (dart.library.io gate)
- Scanner screen: PIN dialog integration for Linux pairing flow
- MeshCoreConnector: Linux pairing/recovery/reconnect wiring
- l10n: 4 new pairing keys across all 14 locales
- 12 unit tests (pairing service + error classifier)
Train a linear regression model on actual message delivery times to
predict tighter timeouts, replacing worst-case physics estimates.
Features: path length, message bytes, seconds since last RX, flood mode.
Global model with per-contact blending after 10+ observations per contact.
Falls back to existing physics formula when model has insufficient data.