From a62c9b3d8be0348c6147021d356ed5b2f1808a45 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 19:36:00 -0647 Subject: [PATCH 1/2] AGENTS: a plugin's link in ~/.config/omarchy/plugins outranks the package On the Pixel 9a, bring-up links to hand-edited copies of the quick settings and switcher plugins kept those copies running through every shell upgrade, so the notification shade never showed. The gotcha says where to look and how to relink. --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index c9c703357..2119384d9 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -199,6 +199,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **Chromium needs `--force-device-scale-factor` on the phone,** even with the mobile user agent: its window layout won't go below about 500 px and the panel is 480 px wide in logical pixels, so without it the window runs off the right edge. Sites get phone layouts from the user agent. - **The screensaver runs in a terminal, so focusing it pops up the on-screen keyboard:** `patches/omarchy/0006-*` turns `org.gnome.desktop.a11y.applications screen-keyboard-enabled` off for the screensaver and back on afterwards (from an EXIT trap in the launcher, since omamobile-omarchy 0.1.9), and `omamobile-osk-guard` (omamobile-shell 0.2.19) turns it back on whenever it is off with no screensaver running. If the keyboard stops appearing, check that key first. - **Vendor chroots:** bootstrap binaries such as `servicemanager` use `/system/bin/bootstrap/linker64` as their interpreter. `extract-vendor-chroot` links it to the runtime APEX linker. Run the chroot by path, without `env chroot`. +- **A plugin's link in `~/.config/omarchy/plugins/` decides which copy runs, and it outranks the package.** `omamobile-setup-user` links every `/usr/share/omamobile/shell/plugins/omamobile.*` there, so package updates reach the user; a bring-up that pointed one of those links at a hand-edited copy kept that copy running through every later upgrade. On the 9a, `omamobile.quicksettings` pointed at a 10-17 copy with no notification shade, and `omamobile.switcher` at a 10-22 copy, until 2026-11-01. If a shell change doesn't show on a phone, check `ls -l ~/.config/omarchy/plugins` first, and relink with the setup script's loop (`for p in /usr/share/omamobile/shell/plugins/omamobile.*; do ln -sfn "$p" ~/.config/omarchy/plugins/"${p##*/}"; done`). - **Quickshell plugins:** - live reload can keep the old code, so run `omarchy-restart-shell`; - pointer handlers declared directly on a window get no events, so put them on an Item inside it; From 1c83767dd17e7715c7197f8d08f73aeb362b59cb Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sun, 1 Nov 2026 07:26:33 -0647 Subject: [PATCH 2/2] AGENTS: the review of #243: the gotcha points at the setup service and its marker On the palmtop the user unit was skipped at every login for want of the profile marker, which is why the hand links survived. The line says how to check that, why to relink with the loop rather than the script, and links the NOTES entry. --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 2119384d9..77b5264a3 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -199,7 +199,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **Chromium needs `--force-device-scale-factor` on the phone,** even with the mobile user agent: its window layout won't go below about 500 px and the panel is 480 px wide in logical pixels, so without it the window runs off the right edge. Sites get phone layouts from the user agent. - **The screensaver runs in a terminal, so focusing it pops up the on-screen keyboard:** `patches/omarchy/0006-*` turns `org.gnome.desktop.a11y.applications screen-keyboard-enabled` off for the screensaver and back on afterwards (from an EXIT trap in the launcher, since omamobile-omarchy 0.1.9), and `omamobile-osk-guard` (omamobile-shell 0.2.19) turns it back on whenever it is off with no screensaver running. If the keyboard stops appearing, check that key first. - **Vendor chroots:** bootstrap binaries such as `servicemanager` use `/system/bin/bootstrap/linker64` as their interpreter. `extract-vendor-chroot` links it to the runtime APEX linker. Run the chroot by path, without `env chroot`. -- **A plugin's link in `~/.config/omarchy/plugins/` decides which copy runs, and it outranks the package.** `omamobile-setup-user` links every `/usr/share/omamobile/shell/plugins/omamobile.*` there, so package updates reach the user; a bring-up that pointed one of those links at a hand-edited copy kept that copy running through every later upgrade. On the 9a, `omamobile.quicksettings` pointed at a 10-17 copy with no notification shade, and `omamobile.switcher` at a 10-22 copy, until 2026-11-01. If a shell change doesn't show on a phone, check `ls -l ~/.config/omarchy/plugins` first, and relink with the setup script's loop (`for p in /usr/share/omamobile/shell/plugins/omamobile.*; do ln -sfn "$p" ~/.config/omarchy/plugins/"${p##*/}"; done`). +- **If a shell change doesn't show on a phone, check that `omamobile-setup-user.service` runs at login and that its marker exists.** The user unit re-links every `omamobile.*` plugin into `~/.config/omarchy/plugins/` at each login, so a package update reaches the user; it runs only if `~/.local/state/omarchy/done/omamobile-shell-profile` exists, which firstboot creates. On the 9a, whose user was set up during bring-up, the marker was missing, so the unit was skipped at every login, and two plugin links still pointed at hand copies (`omamobile.quicksettings` at a 2026-10-17 copy with no notification shade, `omamobile.switcher` at a 2026-10-22 copy) while four plugins weren't linked at all. Check with `systemctl --user status omamobile-setup-user` and `ls ~/.local/state/omarchy/done/`. Relink with the script's loop (`for p in /usr/share/omamobile/shell/plugins/omamobile.*; do ln -sfn "$p" ~/.config/omarchy/plugins/"${p##*/}"; done`), not the script: without its markers it would copy the package's `shell.json` over the user's and repeat every other once-only step, such as appending the cursor and keyboard lines to the Hyprland files again. [tegu NOTES](device/tegu/NOTES.md#2026-10-31-and-11-01-leftovers-on-the-palmtop-from-bring-up) - **Quickshell plugins:** - live reload can keep the old code, so run `omarchy-restart-shell`; - pointer handlers declared directly on a window get no events, so put them on an Item inside it;