Release DeskOS 1.8.0 for production - #360
Merged
Merged
Conversation
n30nex
marked this pull request as ready for review
September 20, 2026 01:57
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promote DeskOS 1.8 to stable with the phone-send, receive-hop and telemetry fixes, current documentation, and signed update packages.
The physical release check also reproduced lost USB commands: a normal health query passed, but the second 177-byte padded query timed out on the running D1L. The console used the polling UART path without a receive ring buffer. Initialize a 1 KiB driver buffer before startup and storage work, and use the driver-backed console for both normal operation and reset recovery.
The signed-update boot path now publishes the committed rollback result, refreshes the security counter after confirmation, and reports receipt-write failures instead of announcing success. Previously, an actual automatic rollback left the update screen at Idle and an accepted boot left the displayed counter stale.
Validation on current source 4299398: all 16 focused native signed-update tests passed. Actions 35473411754 passed every job, including 2,632 host checks, 37 package checks, protocol/conformance checks and both firmware builds. Checksums and the production signature were independently verified.
The exact final image passed preserving USB installation, signed SD installation, automatic rollback with the correct displayed result, reinstallation and normal boot acceptance with security counter 1789856862. Identity, settings, 64 contacts/names/flags and the saved phone DM survived. Fresh Public reception was direct; a new DM was acknowledged in 38 seconds. Storage recovered from a transient timeout, and the normal Home screen and production flasher console passed on the final image.
Official Android 1.49.0 testing remains tied to preceding d3: saved secure pairing, Public send/direct receive, delivered DM and reply, and repeater login/status/commands passed without reboot. Phone, radio and interface code was unchanged afterward; the final change touched only update handling, its tests and documentation. Ordinary-contact telemetry returned no data and TRACE received no peer response. SD transfers and durable DM confirmation can be slow; these limits are retained in the release notes.