Skip to content

omamobile-shell 0.2.97: the Phone and Messages agent is enabled at every login - #394

Merged
derekross merged 1 commit into
mainfrom
omatel-agent-login
Nov 3, 2026
Merged

derekross merged 1 commit into
mainfrom
omatel-agent-login

Conversation

@derekross

Copy link
Copy Markdown
Owner

Why

On a fresh install of the Pixel 7 Pro (2026-11-03), opening Messages showed "Messages service isn't running: you can read, not send". omatel-agent was installed, with its D-Bus activation file (org.omamobile.Messages1.service, SystemdService=omatel-agent.service) and a user unit that is preset enabled (WantedBy=default.target), but a preset reaches a session only when something applies it, and nothing had: the unit read disabled. systemctl --user start omatel-agent fixed it at once.

What

  • bin/omamobile-setup-user, which runs at every login, now runs systemctl --user enable --now omatel-agent.service whenever /usr/lib/systemd/user/omatel-agent.service exists. Enabling and starting are idempotent, so it is not a once-only step with a marker: a login where the enable fails (firstboot has no user manager) is reported and never fails the script, and the next login does it. With the agent up from login, incoming calls and texts notify with no app open.
  • test/setup-user.sh: three runs against a home with the unit present (two logins, then one with systemctl failing) and the existing runs without it; the unit directory is overridable (OMAMOBILE_USER_UNITS) like the script's other test paths.
  • README row for omamobile-setup-user, version 0.2.97.

Version: main has 0.2.94, #343 claims 0.2.95 and #373 (at 0.2.93 today, below main) will need the next free one when it rebases, so this takes 0.2.97. Whichever of these merges last may need its number moved up.

Companions

The apps' own side of the same bug: derekross/omamessages#1 (0.2.2) and derekross/omaphone#2 (0.2.3) ask the bus for StartServiceByName before deciding the agent isn't running, which covers an app opened in a session where this hasn't run yet. Once those are tagged, packages/omamessages needs pkgver 0.2.2 and packages/omaphone 0.2.3 (separate bumps, not in this PR).

Checks

  • packages/omamobile-shell/test/all: all ok
  • tools/pr-check origin/main: all ok
  • tests/all: running at the time of opening; result in a comment

Not tested on a phone (no phone was touched for this change).

🤖 Generated with Claude Code

https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

…ery login

On a fresh install of the Pixel 7 Pro (2026-11-03), opening Messages showed
"Messages service isn't running: you can read, not send". omatel-agent was
installed, with its D-Bus activation file and a user unit that is preset
enabled (WantedBy=default.target), but a preset reaches a session only when
something applies it, and nothing had: the unit read "disabled", and
`systemctl --user start omatel-agent` fixed it at once.

omamobile-setup-user runs at every login, so it now runs
`systemctl --user enable --now omatel-agent.service` there whenever the unit
is installed. Enabling and starting are idempotent, so this is not a
once-only step with a marker: a session where the enable failed (firstboot
has no user manager) gets it at the next login, and the agent is up from
login on, so incoming calls and texts notify with no app open. A failure
is reported and never fails the setup. Nothing happens without the unit.

The test runs the script three times against a home with the unit present
(two logins, then one with systemctl failing) and once without it, with the
unit directory pointed at a scratch one (OMAMOBILE_USER_UNITS, as the other
test paths are). The apps' own fix, activating the agent over D-Bus when
they open (omamessages 0.2.2, omaphone 0.2.3), covers the app opened in a
session where this hasn't run.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
@derekross

Copy link
Copy Markdown
Owner Author

tests/all: finished, exit 0, 380 ok, no failures.

@derekross
derekross merged commit 6d9f50b into main Nov 3, 2026
2 checks passed
@derekross
derekross deleted the omatel-agent-login branch November 3, 2026 13:55
derekross added a commit that referenced this pull request Nov 3, 2026
…ssages agent over D-Bus (#399)

On a fresh install Messages showed "Messages service isn't running: you
can read, not send" because both apps only asked whether the agent's
bus name had an owner, and nothing had enabled omatel-agent's user unit
yet. Each app now asks the session bus to start the service first
(omamessages#1, omaphone#2) and shows the banner only when that fails.
omamobile-shell 0.2.97 (#394) also enables the agent at every login.


Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 3, 2026
… 0.2.99 over 0.2.97

Main took omamobile-modem-sit 0.3.28 (#364, the unconfirmed-hangup stop)
and omamobile-shell 0.2.97 (#394); #397 lands shell 0.2.98. This branch
keeps 0.3.29 and moves the shell to 0.2.99. tools/sit-sim keeps both
#364's --unconfirmed-hangup and this branch's --imsi-plmn/--no-imsi in
the usage block and the argument list.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
derekross added a commit that referenced this pull request Nov 3, 2026
…0: the Pixel 7 Pro's modem stack on by default (#398)

* omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.98: the Pixel 7 Pro's modem stack on by default

The maintainer's decision of 2026-11-03: the next release ships the modem
working out of the box (calls, texts and data on the tested network, M4.6
through three reboots). The switch of M4.6, omamobile-modem-boot.target,
is now on by default on cheetah, and a boot that can't or shouldn't
start the modem costs as little as possible:

- omamobile-device-cheetah 0.1.43 enables the target with a vendor wants
  link under multi-user.target.wants, as it does for the AoC and Wi-Fi
  units; the four units the target wants get no link of their own, and
  omamobile-modem itself still enables nothing (its test holds it to
  that; tegu and raven are untouched). Off: systemctl mask the target.
  The stack's packages (omamobile-modem-sit, omamobile-mmd) join
  cheetah's ROOTFS_PACKAGES so the release image carries them.
- A phone that isn't provisioned costs nothing: the modem and inhibit
  units carry ConditionPathExists= for the chroot, the NV checksums and
  the board id (what tools/phone-provision puts there), so both are
  skipped, not failed, and the inhibitor isn't held. The inhibitor needs
  its own copy because the modem unit's Requires= pulls it in even when
  that unit's conditions skip it. sitd skips itself without
  /dev/umts_ipc0; sit-data now does too, through a device drop-in:
  without it a condition-skipped sitd counted as started for sit-data's
  Requires=, and the fallback would have failed after 60 s and restarted
  every 10 s all boot. The start script checks the same three paths
  first, for a start by hand.
- The modem-up guard clears itself after one refused boot: a stale
  marker still refuses that boot and logs where to look (journalctl -b
  -1), then moves to modem-up.refused-<time>-<pid> (the last three kept)
  so the next boot starts the modem again. A phone that hangs with the
  modem up every time loses the modem on every other boot at most, never
  for good. /etc/omamobile/modem-hold restores the old hard stop;
  --retry still clears both markers; the bring-up latch keeps its hard
  stop.
- Every refusal leaves one short line in /run/omamobile/modem-refused,
  and the shell's Mobile data tile shows it under its name instead of
  "No modem" (omamobile-shell 0.2.98, tile-state.sh): no new
  notification path, the journal has the rest.

Versions: #372 and #380 claim device-cheetah 0.1.42, #389 omamobile-modem
0.1.14 and #382 0.1.15, main has omamobile-shell 0.2.97 (#394); hence 0.1.43, 0.1.16
and 0.2.98. Docs: RELEASES (ROOTFS_PACKAGES, decision 12 amended,
checklist step 6), the release notes draft (the modem known issue becomes
what works and what still needs a hand), INSTALL, DEVICES, and MODEM-PLAN
M4.6b with the runbook: install, two reboots, a refused-boot drill by
planting a stale marker, the hold flag.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

* omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: review round 2, the modem-up guard bounded

The review of #398 asked for three changes and a few corrections.

The self-clearing modem-up guard was unbounded: a phone that hangs
because the modem is up went up, hang, refused, up, hang, refused, for
ever, with only a tile line on the boots in between. Now the refused
copy the script already keeps is the counter: one automatic retry, then
a hold. refuse_unclean keeps the marker and refuses "(held)" when a
modem-up.refused-* copy exists (no clean stop since the last refusal);
--stopped on this boot's marker removes the copies, so a clean stop
resets the count; --retry clears both markers and the copies. The test's
"four unclean boots in a row" block becomes "the second refusal holds, a
clean stop resets", and M4.6b gets drill B9b for it.

systemctl is-enabled reads "disabled" for a unit started by a vendor
wants link alone (it reports /etc and /run links only), so B6's pass and
stop lines expected the wrong answer and would have stopped a correct
install; B6 now expects "enabled" before and "disabled" after the
disable, and proves the link with ls -l of the /usr/lib link and
systemctl list-dependencies --plain multi-user.target. The README, the
target's header and the install message say the same, so nobody reads
"disabled" and skips the mask. The read-only NV checksum check (M3.5)
opens B6 as well as closing the runbook (AGENTS.md section 1). B8's
is-active expectation is "failed inactive inactive active" (mmd runs).

omamobile-shell takes 0.2.100: main is 0.2.98 after #397 and #373 is
taking 0.2.99. The DEVICES cheetah fingerprint cell reads "works": #358
made it on by default.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

* omamobile-modem 0.1.16: the start script's test stops after the marker decision

The case "the boot after a refused one starts the modem again" (and the
--retry case) ran lib/omamobile-modem-start past the marker refusals and
relied on the machine to stop it: on the laptop and in CI no sleep
inhibitor is held, so the script refused there before any driver. On the
phone, where tools/phone-install-package builds the package as an
unprivileged user, the inhibitor is held, so the test went on into the
real bring-up and failed on /sys/module/pcie_aspm/parameters/policy
(permission denied) and then on omamobile-vendor's "run as root".

The script takes a test-only OMAMOBILE_MODEM_TEST_STOP_AFTER_CHECKS=1
(documented in its header; no unit or install step sets it) and exits 0
right after the marker decision, before the link driver's sysfs read,
the inhibitor wait, the first modprobe and the profile. The two cases use
it and assert the decision itself: exit 0, the stale marker moved aside
with its refused copy kept, no latch written, the earlier reason left
for the tile (it is removed only once every refusal has passed, which
the stop point comes before). The test also checks that the stop point
sits between the marker decision and the sysfs read, the inhibitor and
the latch, and that no unit sets the variable.

Verified: packages/omamobile-modem/test/all as uid 1000, with and
without a systemd-inhibit stand-in that reports the inhibitor held (the
phone's case); tools/pr-check origin/main.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

* release notes: the carrier APNs come from the SIM, not by hand

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>
derekross added a commit that referenced this pull request Nov 3, 2026
…tes file and the day's record (#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, #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

* 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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… agent at every login (derekross#394)

On a fresh install of the Pixel 7 Pro (2026-11-03), opening Messages showed
"Messages service isn't running: you can read, not send". omatel-agent was
installed, with its D-Bus activation file and a user unit that is preset
enabled (WantedBy=default.target), but a preset reaches a session only when
something applies it, and nothing had: the unit read "disabled", and
`systemctl --user start omatel-agent` fixed it at once.

omamobile-setup-user runs at every login, so it now runs
`systemctl --user enable --now omatel-agent.service` there whenever the unit
is installed. Enabling and starting are idempotent, so this is not a
once-only step with a marker: a session where the enable failed (firstboot
has no user manager) gets it at the next login, and the agent is up from
login on, so incoming calls and texts notify with no app open. A failure
is reported and never fails the setup. Nothing happens without the unit.

The test runs the script three times against a home with the unit present
(two logins, then one with systemctl failing) and once without it, with the
unit directory pointed at a scratch one (OMAMOBILE_USER_UNITS, as the other
test paths are). The apps' own fix, activating the agent over D-Bus when
they open (omamessages 0.2.2, omaphone 0.2.3), covers the app opened in a
session where this hasn't run.

Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ssages agent over D-Bus (derekross#399)

On a fresh install Messages showed "Messages service isn't running: you
can read, not send" because both apps only asked whether the agent's
bus name had an owner, and nothing had enabled omatel-agent's user unit
yet. Each app now asks the session bus to start the service first
(omamessages#1, omaphone#2) and shows the banner only when that fails.
omamobile-shell 0.2.97 (derekross#394) also enables the agent at every login.

Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…0: the Pixel 7 Pro's modem stack on by default (derekross#398)

* omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.98: the Pixel 7 Pro's modem stack on by default

The maintainer's decision of 2026-11-03: the next release ships the modem
working out of the box (calls, texts and data on the tested network, M4.6
through three reboots). The switch of M4.6, omamobile-modem-boot.target,
is now on by default on cheetah, and a boot that can't or shouldn't
start the modem costs as little as possible:

- omamobile-device-cheetah 0.1.43 enables the target with a vendor wants
  link under multi-user.target.wants, as it does for the AoC and Wi-Fi
  units; the four units the target wants get no link of their own, and
  omamobile-modem itself still enables nothing (its test holds it to
  that; tegu and raven are untouched). Off: systemctl mask the target.
  The stack's packages (omamobile-modem-sit, omamobile-mmd) join
  cheetah's ROOTFS_PACKAGES so the release image carries them.
- A phone that isn't provisioned costs nothing: the modem and inhibit
  units carry ConditionPathExists= for the chroot, the NV checksums and
  the board id (what tools/phone-provision puts there), so both are
  skipped, not failed, and the inhibitor isn't held. The inhibitor needs
  its own copy because the modem unit's Requires= pulls it in even when
  that unit's conditions skip it. sitd skips itself without
  /dev/umts_ipc0; sit-data now does too, through a device drop-in:
  without it a condition-skipped sitd counted as started for sit-data's
  Requires=, and the fallback would have failed after 60 s and restarted
  every 10 s all boot. The start script checks the same three paths
  first, for a start by hand.
- The modem-up guard clears itself after one refused boot: a stale
  marker still refuses that boot and logs where to look (journalctl -b
  -1), then moves to modem-up.refused-<time>-<pid> (the last three kept)
  so the next boot starts the modem again. A phone that hangs with the
  modem up every time loses the modem on every other boot at most, never
  for good. /etc/omamobile/modem-hold restores the old hard stop;
  --retry still clears both markers; the bring-up latch keeps its hard
  stop.
- Every refusal leaves one short line in /run/omamobile/modem-refused,
  and the shell's Mobile data tile shows it under its name instead of
  "No modem" (omamobile-shell 0.2.98, tile-state.sh): no new
  notification path, the journal has the rest.

Versions: derekross#372 and derekross#380 claim device-cheetah 0.1.42, derekross#389 omamobile-modem
0.1.14 and derekross#382 0.1.15, main has omamobile-shell 0.2.97 (derekross#394); hence 0.1.43, 0.1.16
and 0.2.98. Docs: RELEASES (ROOTFS_PACKAGES, decision 12 amended,
checklist step 6), the release notes draft (the modem known issue becomes
what works and what still needs a hand), INSTALL, DEVICES, and MODEM-PLAN
M4.6b with the runbook: install, two reboots, a refused-boot drill by
planting a stale marker, the hold flag.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

* omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: review round 2, the modem-up guard bounded

The review of derekross#398 asked for three changes and a few corrections.

The self-clearing modem-up guard was unbounded: a phone that hangs
because the modem is up went up, hang, refused, up, hang, refused, for
ever, with only a tile line on the boots in between. Now the refused
copy the script already keeps is the counter: one automatic retry, then
a hold. refuse_unclean keeps the marker and refuses "(held)" when a
modem-up.refused-* copy exists (no clean stop since the last refusal);
--stopped on this boot's marker removes the copies, so a clean stop
resets the count; --retry clears both markers and the copies. The test's
"four unclean boots in a row" block becomes "the second refusal holds, a
clean stop resets", and M4.6b gets drill B9b for it.

systemctl is-enabled reads "disabled" for a unit started by a vendor
wants link alone (it reports /etc and /run links only), so B6's pass and
stop lines expected the wrong answer and would have stopped a correct
install; B6 now expects "enabled" before and "disabled" after the
disable, and proves the link with ls -l of the /usr/lib link and
systemctl list-dependencies --plain multi-user.target. The README, the
target's header and the install message say the same, so nobody reads
"disabled" and skips the mask. The read-only NV checksum check (M3.5)
opens B6 as well as closing the runbook (AGENTS.md section 1). B8's
is-active expectation is "failed inactive inactive active" (mmd runs).

omamobile-shell takes 0.2.100: main is 0.2.98 after derekross#397 and derekross#373 is
taking 0.2.99. The DEVICES cheetah fingerprint cell reads "works": derekross#358
made it on by default.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

* omamobile-modem 0.1.16: the start script's test stops after the marker decision

The case "the boot after a refused one starts the modem again" (and the
--retry case) ran lib/omamobile-modem-start past the marker refusals and
relied on the machine to stop it: on the laptop and in CI no sleep
inhibitor is held, so the script refused there before any driver. On the
phone, where tools/phone-install-package builds the package as an
unprivileged user, the inhibitor is held, so the test went on into the
real bring-up and failed on /sys/module/pcie_aspm/parameters/policy
(permission denied) and then on omamobile-vendor's "run as root".

The script takes a test-only OMAMOBILE_MODEM_TEST_STOP_AFTER_CHECKS=1
(documented in its header; no unit or install step sets it) and exits 0
right after the marker decision, before the link driver's sysfs read,
the inhibitor wait, the first modprobe and the profile. The two cases use
it and assert the decision itself: exit 0, the stale marker moved aside
with its refused copy kept, no latch written, the earlier reason left
for the tile (it is removed only once every refusal has passed, which
the stop point comes before). The test also checks that the stop point
sits between the marker decision and the sysfs read, the inhibitor and
the latch, and that no unit sets the variable.

Verified: packages/omamobile-modem/test/all as uid 1000, with and
without a systemd-inhibit stand-in that reports the inhibitor held (the
phone's case); tools/pr-check origin/main.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

* release notes: the carrier APNs come from the SIM, not by hand

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>
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