Skip to content

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
derekross merged 2 commits into
mainfrom
release-notes-2026.11.03
Nov 3, 2026
Merged

derekross merged 2 commits into
mainfrom
release-notes-2026.11.03

Conversation

@derekross

Copy link
Copy Markdown
Owner

The docs for the 2026.11.03 release (kernel kernel-2026.11.01, uname -r 7.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.md is 2026-11-DRAFT.md made final, as its own header says: the header comment gone, every 2026.MM.DD replaced, the kernel line checked, and the hardware matrix re-read against docs/DEVICES.md today (Modem works, Fingerprint works, Suspend WIP: it matches). Beyond the mechanical part:

The draft file stays for the next release (tools/release tag points at docs/release-notes/*-DRAFT.md as the starting point).

device/cheetah

NOTES.md gets 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 with carrier_manifest empty, sitd 0.3.29 choosing the SIM's values on auto, the earpiece clean at stage c9 with the boost converter on (so #402 dropped the refusal), #398's B6-B9b passed with no ufshcd_err_handler pass, the Messages agent fix (#394, #399), the open cpif oem_ipc0 "is not opened" lines, and the OMARCHY_PATH gotcha for omamobile-update over 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 scan on the three files, with an empty identifiers list (the maintainer's ~/.config/omamobile/release-identifiers isn'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 before tag.
  • The tag stage's placeholder grep (DRAFT|MM\.DD|TODO|XXX|<[a-z][a-z ._-]*>) finds nothing in the notes, and they name both the kernel tag and uname -r.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

derekross and others added 2 commits November 3, 2026 10:41
… 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
@derekross
derekross merged commit 330a7f2 into main Nov 3, 2026
2 checks passed
@derekross
derekross deleted the release-notes-2026.11.03 branch November 3, 2026 15:52
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant