Repository navigation
omamessages 0.2.2, omaphone 0.2.3: the apps activate the Phone and Messages agent over D-Bus - #399
Merged
Merged
Conversation
…ssages agent over D-Bus 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. 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
…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
…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
…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.
Package bumps to the tagged app releases (omamessages v0.2.2, omaphone v0.2.3), which ask the session bus to activate
omatel-agentbefore deciding it isn't running (derekross/omamessages#1, derekross/omaphone#2). Seen on the 7 Pro's fresh install on 2026-11-03: the banner "Messages service isn't running" with the agent simply not enabled yet. #394 (merged) also enables the agent at every login.Checksums from the GitHub tag tarballs.
tools/pr-check origin/mainpasses.🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d