MeshCore DeskOS D1L 1.9.0

MeshCore DeskOS D1L 1.9.0

DeskOS 1.9 adds practical everyday controls to the SenseCAP Indicator D1L:

• Saved Standard/Large text for message bodies, lists and keyboard characters.
• A paged contact mention picker that inserts the advertised name at the cursor without replacing or sending the draft.
• Contact auto-add rules shared by the touchscreen and official phone app: select roles and a hop limit. Existing contacts keep updating; a full book never silently evicts contacts.
• Optional US/Canada and Europe/UK daylight saving. Message dates use their own timestamp, while radio and security clocks stay independent of the display offset.
• Desktop Bluetooth sessions now initialize from verified security/subscription events when the connection callback arrives late, preserving queued replies.
• Incoming DM acknowledgements can wait for a busy transmitter. A direct message's flood retry keeps its original timestamp, allowing receivers to recognize the same message.

Install

Choose Update DeskOS in the Canadaverse flasher to preserve an existing DeskOS identity, settings and SD data. Fresh installations need the clean ESP32 image, included RP2040 bridge and a prepared FAT32 card. Preparation tools never format cards.

The complete ZIP contains the firmware, bridge, signed update, checksums and guide. The signed-SD ZIP places its three files under deskos/updates/ at the card root. Keep the downloaded files together and follow START_HERE.

Build and device checks

Source: bc2cf4212c5727ae00d0f04667b968fff84940b8.

Actions run 37714163592 passed all five jobs: 2,640 host checks with seven platform skips, 37 package checks, protocol/conformance checks and both firmware builds. The package hashes and production update signature were independently verified. The final ACK and live-clock native regressions also passed on the Pi.

The exact image passed a preserving USB installation on the Pi-attached D1L. The identity, all 64 saved contacts, saved phone DM, Large text and phone-selected contact policy survived. Display offset and daylight-saving behavior were also checked on hardware in this phase. The signed updater and RP2040 bridge sources are unchanged from 1.8.0, whose physical signed-SD install and rollback checks remain documented in that release; a new signed-SD installation is not claimed here.

The final build passed actual Windows-host Bluetooth tests using the official companion protocol: encrypted/authenticated/bonded connection with MTU 517, all 64 contacts synchronized, shared auto-add settings saved and restored, Public transmission with actual radio airtime, two matching DM confirmations (28.20 and 14.64 seconds), and self telemetry. The D1L stayed on the same boot with 7,996 bytes of Bluetooth worker stack headroom. The production flasher console verified the final firmware, radio, bridge and SD through one USB connection. Original device settings were restored.

Official MeshCore Android 1.50.0 (78) was tested on the preceding 3b047fde image: secure reconnect, fresh Public reception labelled Direct, Public Sent, and the shared contact policy worked. Its DM test exposed the timing issue corrected afterward; the phone was released before the final build. Earlier in this phase, live repeater status and repeated ordinary-contact telemetry requests were exercised without a restart. The final Windows run is protocol/device evidence, not a claim of a final Android UI retest.

Actual LVGL renderers and interactions were checked on the Pi, including Large text, contact paging, mention insertion and full-draft rejection. The user confirmed the mention picker on the initial 31af6258 candidate; that UI code is unchanged in the final build.

Scope and limits

Mentions are ordinary name-based text and do not guarantee recipient alerts. Headings and map attribution retain their dedicated font sizes. The interface remains English-only with a 138-byte firmware message limit and exclusive Wi-Fi/Bluetooth modes. Optional sensors, structured replies, additional languages/layouts and the wider WadaMesh app suite remain roadmap work.

SD startup, saving and updates can be slow. DM confirmations remain tied to a saved acknowledgement; the companion now allows an additional two minutes for slow storage before retrying. Radio responses depend on the peer, route and permissions. Ordinary-contact telemetry returned no data during testing; a successful route-trace response was not observed. Older phone-cached messages retain their historical hop labels.

See the product page and the included user guide and parity documentation for supported workflows.