Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
- **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;
Expand Down