Repository navigation
release notes 2026.11.03, device/cheetah NOTES, MODEM-PLAN: the first release's notes, and the day the modem worked through the apps - #405
Merged
Conversation
… release's notes, and the day the modem worked through the apps docs/release-notes/2026.11.03.md is the draft made final for the 2026.11.03 release (kernel-2026.11.01, uname -r 7.3.0-rc6-omamobile-g2219cc6cda77, the kernel of the 2026.11.02 test install): the header comment gone, every 2026.MM.DD replaced, the hardware matrix re-read against docs/DEVICES.md today (Modem works, Fingerprint works, Suspend WIP), and the install paragraph's `<folder>` and `<factory image>` renamed to BACKUP-DIR and FACTORY-IMAGE.zip, which `tools/release tag` would otherwise refuse as placeholders. The modem bullet under "New in the last weeks" now says what works (calls, texts and data on the tested network, the APNs chosen from the SIM), and "Phones already running a development build" says that a provisioned phone's modem stack starts at boot once it has omamobile-device-cheetah 0.1.43, and how to keep it off (systemctl mask omamobile-modem-boot.target). The draft stays for the next release, as its own header says and tools/release expects. device/cheetah/NOTES.md records 2026-11-03 on the reference phone: calls and texts both ways through Phone and Messages (the first text between two Omarchy Mobile phones), IMS registered with no carrier manifest, sitd 0.3.29 choosing the SIM's values on its own, the earpiece clean at stage c9 with the boost converter on, #398's B6-B9b runbook passed with no UFS error-handler pass, the Messages agent fix (#394, #399), the open cpif oem_ipc0 lines, and the OMARCHY_PATH gotcha for omamobile-update over ssh. MODEM-PLAN's status line was from 2026-10-13 ("M4.2 needs a SIM"); it now says what works and what is open, with the old line kept as history, and M4.6b has its result. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
…recovery, and the fresh-install fingerprint record The notes told a user to run omamobile-modem-start --retry, which isn't on PATH and by hand brings the modem up outside its unit; the recovery is the runbook's (clear the markers, restart). The draft's placeholders take the forms the tag stage accepts. The fingerprint cell records today's fresh-install run (T1-T3) instead of "being tested". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…tes file and the day's record (derekross#405) * release notes 2026.11.03, device/cheetah NOTES, MODEM-PLAN: the first release's notes, and the day the modem worked through the apps docs/release-notes/2026.11.03.md is the draft made final for the 2026.11.03 release (kernel-2026.11.01, uname -r 7.3.0-rc6-omamobile-g2219cc6cda77, the kernel of the 2026.11.02 test install): the header comment gone, every 2026.MM.DD replaced, the hardware matrix re-read against docs/DEVICES.md today (Modem works, Fingerprint works, Suspend WIP), and the install paragraph's `<folder>` and `<factory image>` renamed to BACKUP-DIR and FACTORY-IMAGE.zip, which `tools/release tag` would otherwise refuse as placeholders. The modem bullet under "New in the last weeks" now says what works (calls, texts and data on the tested network, the APNs chosen from the SIM), and "Phones already running a development build" says that a provisioned phone's modem stack starts at boot once it has omamobile-device-cheetah 0.1.43, and how to keep it off (systemctl mask omamobile-modem-boot.target). The draft stays for the next release, as its own header says and tools/release expects. device/cheetah/NOTES.md records 2026-11-03 on the reference phone: calls and texts both ways through Phone and Messages (the first text between two Omarchy Mobile phones), IMS registered with no carrier manifest, sitd 0.3.29 choosing the SIM's values on its own, the earpiece clean at stage c9 with the boost converter on, derekross#398's B6-B9b runbook passed with no UFS error-handler pass, the Messages agent fix (derekross#394, derekross#399), the open cpif oem_ipc0 lines, and the OMARCHY_PATH gotcha for omamobile-update over ssh. MODEM-PLAN's status line was from 2026-10-13 ("M4.2 needs a SIM"); it now says what works and what is open, with the old line kept as history, and M4.6b has its result. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d * release notes 2026.11.03, DEVICES, FINGERPRINT-PLAN: the user-facing recovery, and the fresh-install fingerprint record The notes told a user to run omamobile-modem-start --retry, which isn't on PATH and by hand brings the modem up outside its unit; the recovery is the runbook's (clear the markers, restart). The draft's placeholders take the forms the tag stage accepts. The fingerprint cell records today's fresh-install run (T1-T3) instead of "being tested". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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
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.
The docs for the 2026.11.03 release (kernel
kernel-2026.11.01,uname -r7.3.0-rc6-omamobile-g2219cc6cda77, the kernel of the 2026.11.02 test install). No phone was touched.The release notes
docs/release-notes/2026.11.03.mdis2026-11-DRAFT.mdmade final, as its own header says: the header comment gone, every2026.MM.DDreplaced, the kernel line checked, and the hardware matrix re-read againstdocs/DEVICES.mdtoday (Modem works, Fingerprint works, Suspend WIP: it matches). Beyond the mechanical part:omamobile-device-cheetah0.1.43, and how to keep it off (sudo systemctl mask omamobile-modem-boot.target); the fingerprint-at-boot change next to it. The keyring and Hyprland 0.57 notes still apply and stay.<folder>and<factory image>becameBACKUP-DIRandFACTORY-IMAGE.zip:tools/release taggreps the notes for<[a-z][a-z ._-]*>and would have refused them as placeholders.The draft file stays for the next release (
tools/release tagpoints atdocs/release-notes/*-DRAFT.mdas the starting point).device/cheetah
NOTES.mdgets today's entry on top: calls and texts both ways through Phone and Messages (the first text from one Omarchy Mobile phone to another, this 7 Pro to a Pixel 9a), IMS registered withcarrier_manifestempty, sitd 0.3.29 choosing the SIM's values onauto, the earpiece clean at stagec9with the boost converter on (so #402 dropped the refusal), #398's B6-B9b passed with noufshcd_err_handlerpass, the Messages agent fix (#394, #399), the open cpifoem_ipc0"is not opened" lines, and theOMARCHY_PATHgotcha foromamobile-updateover ssh.MODEM-PLAN.md's status line was from 2026-10-13 ("M4.2 needs a SIM"); it now says what works and what is open, with the old line kept as "Earlier status", and M4.6b has its B6-B9b result where the runbook asks for it (B10 and M4.7 are noted as not recorded). The DEVICES cheetah Modem row (rewritten by #388, #398, #402 today) doesn't contradict any of this, so it is unchanged.Checks
tests/all: exit 0 (381 ok).tools/pr-check origin/main: all ok.tools/release --dry-run --version 2026.11.03 scanon the three files, with an empty identifiers list (the maintainer's~/.config/omamobile/release-identifiersisn't on this machine): no MAC, serial, IMEI or builder's home path. The listed-identifier part of the scan is still to run on the maintainer's machine beforetag.DRAFT|MM\.DD|TODO|XXX|<[a-z][a-z ._-]*>) finds nothing in the notes, and they name both the kernel tag anduname -r.🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d