Repository navigation
MeshCore DeskOS D1L 1.9.1
MeshCore DeskOS D1L 1.9.1
DeskOS 1.9.1 improves SD save responsiveness and checks the complete saved file before replacing its previous copy. Messages, drafts, contacts, nodes, routes and retained packet segments now use the bridge's existing verified transfer instead of reopening and flushing the card for every 192-byte chunk.
On the attached D1L, four contact-preference saves had a median of 4.27 seconds, compared with 8.21 seconds on 1.9.0: 48% less time in this comparison. These measurements are specific to this device and card. No SD write failures were recorded across the eight retained stores during acceptance.
Installation
Choose Update DeskOS in the Canadaverse flasher to preserve an existing DeskOS identity, contacts, settings and SD data. The complete ZIP includes both ESP32 installation paths, the production RP2040 bridge, signed SD update, checksums and instructions. The separate signed-SD ZIP uses the correct deskos/updates/ card paths. Firmware and preparation tools never format cards.
The data format and paired RP2040 firmware are unchanged from 1.9.0. Use the paired bridge supplied with the release. Save completion still requires the final rename, and interrupted or failed verification keeps the previous primary file. Failed cancellation cleanup remains a visible storage error.
Verification
Exact source: a41f4f0264e98f245d35a6f914c28aee21d2e905.
Actions run 37848186029 passed all five jobs, including 2,640 host tests, seven platform skips, 37 package tests, protocol conformance and both firmware builds. The exact signed Actions package was checksum-verified and installed on the D1L. The same source also compiled successfully on the Pi with ESP-IDF 5.5.4, using one compiler job and a 768 MiB memory limit; native storage checks passed on the Pi and Windows.
The preserving installation retained the identity, all 64 contacts, original settings and the eight recent DM rows captured before installation. The production flasher verified the exact image, radio, bridge and SD readiness through one USB connection. A verified private recovery copy was retained before installation.
Actual Windows Bluetooth tests passed secure authenticated/bonded access with MTU 517, contact synchronization, shared contact rules, Public radio transmission, two matching direct-message confirmations (25.06 and 15.72 seconds) and self telemetry. The D1L remained on the same boot throughout acceptance, with 7,992 bytes of Bluetooth-worker stack headroom. Original settings were restored.
Scope and limits
The phone was not used for this release. These are real Windows Bluetooth protocol/device tests, not a final official Android or iOS app retest. The signed updater and bridge are unchanged; a new physical signed-SD installation is not claimed. Earlier physical signed-SD installation and rollback are documented with 1.8.0.
The 1.9 controls and parity limits continue to apply. Slow-card behavior remains possible; delivery confirmation still waits for the acknowledgement to be saved. Remote telemetry and TRACE responses depend on the peer and route and were not requalified here. Additional languages/layouts, optional sensors, structured replies and the wider WadaMesh application suite remain future work.