Sources
- Install the OEM firmware package for each Snapdragon machine
- Find the Snapdragon OEM firmware packages by what they provide
- Refresh the Snapdragon device tree list before every boot image build
- Show the disk unlock prompt on Snapdragon X2 machines
- linux-omarchy-aarch64: add the Anduril BlueChip (#2237)
- Refresh the Snapdragon device tree list before every boot image build (#17934)
- review-comment by
greptile-apps[bot]
- review-comment by
greptile-apps[bot]
Snapdragon firmware installation and boot images follow hardware changes
dhh merged
birkskyum's OEM firmware installation work into quattro in omacom/omarchy#17389. It installs available machine-specific packages before the remaining Windows firmware extraction step and migrates existing installations, retaining pending work until firmware setup and the boot image rebuild finish. The companion ISO change discovers firmware packages by what they provide, carrying them in the Arm offline mirror without maintaining another list of machine names.
Two further birkskyum proposals merged by
dhh address black screens during boot. omacom/omarchy#17662 adds early display dependencies for Snapdragon X2 disk unlock prompts. omacom/omarchy#17934 refreshes the managed device-tree list before every boot image build, so kernel changes can introduce or rename a tree without leaving it out of the image. This matters for the dedicated Anduril BlueChip tree committed to the package repository in omacom/omarchy-pkgs@3fcd5d2393fa, which also enables its Goodix touchscreen.
greptile-apps[bot] identified failed-write and interrupted-migration hazards in the device-tree refresh proposal. The resulting committed change checks writes before replacing boot settings and records an owed rebuild before changing the list. These are quattro changes and package-repository commits, rather than evidence of a stable Omarchy release.
Snapdragon X2 audio profiles reach the edge package repository
ryanrhughes merged
birkskyum's omacom/omarchy-pkgs#2246 into master, adding a pinned upstream ALSA configuration package for aarch64. It supplies the Glymur dispatcher and profiles for the Zenbook A14 X2 and Yoga Slim 7x Gen 11, addressing the missing profiles that leave PipeWire offering only dummy output.
The change also moves the Surface Pro 11's tuned profile into its own folder, avoiding file conflicts while preserving its muted start, speaker ceiling and microphone-first setup. github-actions[bot] reported both packages live in edge/aarch64 in omacom/omarchy-pkgs#2246:issuecomment-6695210111; this establishes edge package availability, rather than a stable Omarchy release.
Osaka Jade recovery preserves theme overrides after upgrades
dhh merged
omarchybot's omacom/omarchy#17746 into quattro to repair upgrades that left Osaka Jade without a palette and broke foot, kitty and alacritty terminals. The migration restores the theme from its separate repository before the existing theme refresh, preserving user overrides and linked backgrounds. If fetching fails, it applies Jade Horse while leaving the user's theme directory untouched.
omarchybot subsequently reported a backport to 4.5.1 in omacom/omarchy#17746:issuecomment-6690413386. The supplied record confirms the quattro merge and that backport report; it does not establish publication of a stable release.
Dictation fixes address blocked upgrades and Hex recording that would not stop
A quattro commit with dhh listed as a participant, attributed to David Heinemeier Hansson, changes the Superwhisper shortcut migration so it does not depend on a compositor reload check. omacom/omarchy@9d883445bd99 explains that an older running compositor could reject newly upgraded configuration keys, roll back the shortcut change and stop the update.
A separate quattro commit with ryanrhughes listed as a participant, attributed to Ryan Hughes, fixes Hex push-to-talk remaining active after release. omacom/omarchy@ad4977b6a610 sends the stop directly instead of relying on a status check that could miss short recordings, preserves genuine stop errors and uses the universal clipboard paste path for transcripts. These are committed fixes on quattro.
Monitor ownership handoff gains immediate settings restoration
crmne's open omacom/omarchy#7000 proposes a default-on monitor-management switch so an external manager can take ownership without Omarchy's automatic paths overwriting its layout. The current proposal also suppresses saved display-panel settings during the handoff while keeping those settings on disk.
During review, greptile-apps[bot] pointed out that handing control back would not immediately restore saved settings.
crmne responded in omacom/omarchy#7000:discussion_r4491768329 that the command now reloads Hyprland when moving from off to on, restoring saved settings and the clamshell rule immediately, with regression coverage for the transitions. The proposal remains open.
Notch-aware bar layout receives a 16-inch MacBook test report
dhh's open omacom/omarchy#17744, opened on November 5, proposes splitting the bar's center sections around a notch of known width. Indicators can end to its left while the clock begins to its right, and users can move widgets across the notch through the layout configuration. External monitors retain centered placement.
jotenakis2 reported testing the branch on a 16-inch M2 Pro MacBook on November 6 in omacom/omarchy#17744:issuecomment-6694215120. They reported passing bar tests, roughly equal clearance on both sides and no QML errors, using a manual notch-width override. This is a contributor's test report; the panel still needed its platform width entry for automatic placement, and the proposal remains open.
Changelog browsing moves from a terminal pager into a shell overlay
EFrMG reported replacing the terminal-based viewer in open omacom/omarchy#16809 with a stock QML overlay. The Update menu and changelog command summon release notes grouped by feature version, with version tabs and keyboard navigation, allowing users to read changes without opening a browser.
In omacom/omarchy#16809:issuecomment-6692846945, EFrMG described shell crashes triggered by changing versions while inline images loaded, and an initial workaround using image links, separate release documents and delayed selection commits. Later,
EFrMG reported addressing review feedback, and
greptile-apps[bot]'s updated review said the five previous findings were addressed. The review's latest commit description also mentions release images and theme colors. The overlay remains an open proposal.
Security-key lock-screen unlock remains under review
donvince opened omacom/omarchy#17947 to unlock the shell's lock screen by touching a configured FIDO2 key through a separate PAM service. Existing users would need to rerun security-key setup. The proposal does not include PIN verification, so the configured key alone can unlock the session.
greptile-apps[bot] found that some wake paths resumed fingerprint authentication without resuming key authentication.
donvince reported fixing monitor-arrival and resume-from-sleep handling in omacom/omarchy#17947:issuecomment-6698600730. The proposal remains open: the author reports limited hardware testing, and the later review still requests on-screen checks and captures of the key-only and combined fingerprint layouts.
Autoinstall drives could finish machine setup with custom commands
xymbol opened omacom/omarchy-iso#397 to run custom commands as root in the newly installed system near the end of installation. Commands can use scripts and other files from the configuration drive through CIDATA, supporting setup tasks such as preparing a kiosk.
greptile-apps[bot] flagged an initial approach that copied the drive into live RAM.
xymbol reported replacing it with read-only mounts in omacom/omarchy-iso#397:discussion_r4492070722. The reviewer also retracted a remaining test-harness concern after accepting the explicit release-ISO flag as its source of truth. The feature remains an open proposal.
Gmail Notifier is published after notification privacy revisions
Gmail Notifier, eprompc's multi-account unread-mail bar widget, was published through omacom/omarchy-plugin-marketplace#13746. During the November 6 review,
HANCORE-linux confirmed earlier fixes but identified private mail metadata passing through notification command arguments, where another local account with command-line visibility could capture it. A switch to Omarchy's notification helper still forwarded sender and subject through process arguments.
eprompc then reported version 0.3.0 using in-process Gio D-Bus notifications and libsecret access, preserving existing authorizations through upgrades and rollback.
github-actions[bot] recorded a passing automated baseline for that revision and confirmed publication in omacom/omarchy-plugin-marketplace#13746:issuecomment-6696217254. The publication and baseline checks explicitly do not constitute a security audit.
