MeshCore DeskOS D1L 1.8.0
DeskOS 1.8 is the stable full-feature release for the SenseCAP Indicator D1L.
- Phone channel sends wait for radio acceptance, and a stalled radio has a bounded recovery path.
- Newly received phone messages carry their stored hop count; nearby channel messages no longer receive a fixed 63-hop placeholder.
- Contact telemetry has more Bluetooth worker stack space. USB input is buffered so longer commands and contact imports survive busy startup and storage work.
- Shared Chats, paged Contacts, Profile editing, six editable quick replies, saved drafts, quoted replies and the local clipboard improve everyday use.
- Prepared SD storage retains history and offline map data. Signed local updates verify the package and written image before selecting the inactive firmware slot.
- The update screen reports a completed rollback and refreshes its security counter after an accepted boot. Receipt-write failures are reported as errors.
Install
Use Update DeskOS in the Canadaverse flasher to preserve an existing device's identity and settings. A fresh installation requires the full ESP32 image, the included RP2040 bridge and a prepared FAT32 card. The product's preparation tools never format cards.
The complete ZIP includes the installation guide, firmware, bridge, signed update files and checksums. The signed-SD ZIP places its three files under deskos/updates/ at the card root.
Verified build
Source: 4299398ef4a9d5802ddb5a28acd9bf2b18d49680.
Actions run 35473411754 passed every job: 2,632 host checks with seven platform skips, 37 package checks, native protocol/conformance checks, and the ESP32/RP2040 builds. Package checksums and the production update signature were independently verified.
On the preceding d3e3e01 candidate, the physical D1L passed the preserving USB installation and all 12 consecutive 177-byte USB command tests. The exact production RP2040 bridge, unchanged in this package, was flashed and checked. A fresh card passed its capacity check, a 1 GB write/read test and filesystem checks; the original 64 contacts were restored and saved.
That candidate also passed direct Public reception, Public transmission, an acknowledged DM, and live repeater guest status and telemetry. A route-trace request received no reply.
On d3e3e01, the official MeshCore Android app 1.49.0 (77) reconnected using its saved secure bond and a 517-byte MTU. A fresh nearby Public message displayed Direct, an outgoing Public message displayed Sent, and a DM displayed Delivered with its reply received. Repeater login, live status and a read-only command response also worked. Repeated ordinary-contact telemetry requests did not restart D1L; the minimum measured Bluetooth worker stack margin was 3,728 bytes. The phone and D1L settings were restored after testing.
The final 4299398 package passed preserving USB installation with identity and settings retained. It also passed signed-SD signature/image verification, the full inactive-slot write and readback check. Interrupting its first boot returned D1L automatically to the previous working slot; the corrected firmware reported Rolled back and kept the security counter unchanged.
Reinstalling the same signed package then passed normal boot acceptance into the new slot, with the security counter correctly recorded as 1789856862. All 64 contacts, their saved names and flags, the device settings and the saved phone DM survived. A fresh Public message was received directly and a new DM was acknowledged. The production flasher console verified the final image, radio, bridge and SD through one USB connection. The physical Home screen showed Mesh Ready, Wi-Fi Online, SD Ready and Attention OK.
Scope
The official-phone observations above remain tied to d3e3e01; the final correction changed only update handling, its tests and documentation. Phone, radio and interface code was unchanged afterward. Ordinary-contact telemetry returned no data, and a successful route-trace response was not observed.
SD updates can take tens of minutes. Storage work can also delay DM confirmation: the final test was acknowledged in 38 seconds, and a transient SD timeout subsequently cleared. Older messages cached by the phone keep their historical hop labels. Telemetry and discovery results depend on responding peers and their permissions. This release keeps the documented English-only interface, 138-byte message limit and exclusive Wi-Fi/Bluetooth modes. It does not claim complete WadaMesh parity or support for every advanced companion command.
See the product page and the release's user guide and compatibility documentation for the supported workflows.