Repository navigation
Conversation
|
Thanks for tracking this down. A shade that never appears whatever version is installed is maddening, and "check the plugin links" is a good thing to have written down. Before it goes into AGENTS, I'm not sure the cause is quite what the line says. Since 0.2.15 the package enables If that's the cause, I'd like the gotcha to point there: if a shell change doesn't show, check that the setup service runs at login and that the marker exists. Your relink loop is fine as the immediate fix; please note why it's the loop and not the script (run without the marker, the script would re-seed |
…kage 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.
…ervice 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.
90a8f14 to
1c83767
Compare
|
You were right. On the palmtop:
The line now points there: check that the setup service runs at login and that the marker exists, with both commands. It also says why to use the loop and not the script. Without the markers, So I haven't just touched the marker on the palmtop. The unit would then run all of those steps once over the bring-up setup. The safe repair is to mark every step that's already in effect ( |
|
Thanks for checking. "Condition: start condition unmet … omamobile-shell-profile was not met" settles it, and the new line is much more useful: it sends the next person to the setup service and its marker first. The explanation of why to use the loop and not the script (the Yes please to the Two things I'll handle at merge, nothing needed from you:
One tiny wording point, which I can fold in at merge: the marker is created by the first run of |
…e and its marker (derekross#243) When a shell change doesn't show on a phone, the cause found on the 9a was omamobile-setup-user.service not running at login (its ConditionPathExists unmet), not a plugin link outranking the package. The gotcha now points at the setup service and its marker (W4HO-ham). Closes derekross#243 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ekross#243 and derekross#244 - NOTES no longer calls SUSPEND-PLAN a draft (derekross#802). - The ROADMAP Suspend row says mem_sleep read "s2idle [deep]" before kernel derekross#244 and reads "[s2idle] deep" on the published kernel (derekross#802). - The ROADMAP Time row no longer says "No RTC": the S2MPG14's RTC is rtc0 since kernel derekross#243 (asked for on that PR). - The 2026-11-15 NOTES entry records /proc/cmdline's mem_sleep_default=s2idle with mem_sleep (asked for on kernel derekross#244), and the RTC's probe lines, wakealarm and idle interrupt count (asked for on kernel derekross#243). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…efore H2; NOTES and ROADMAP leftovers H0b (the Wi-Fi and PCIe unload and reload, no sleep) and H1 (`pm_test` freezer, devices and platform through `systemctl suspend`: three successes, no failures) ran attended on Colin's 8 Pro on the published `omamobile` at `82f31d3a7` with device-husky 0.1.13; touch, the display and a played haptic effect after H1 are carried into H2, and H2 to H4 have not run. The plan now says that the UFS `dme-set: attr-id 0x4021` line at resume is expected and not a stop, lists the four brcmfmac noise lines, names the maintainer's go-ahead per stage and device-husky 0.1.14 or later for H2 to H4, and records the sleep configuration in effect. NOTES and ROADMAP pick up the leftovers from #802 and the RTC and `mem_sleep_default=s2idle` facts from kernel #243 and #244. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
On the palmtop (Pixel 9a), the notification shade from the website's third screenshot never appeared, whatever shell version was installed. The cause was
~/.config/omarchy/plugins/omamobile.quicksettings: a bring-up step on 10-17 had pointed it at a hand-edited copy under/var/lib, written before the shade existed.omamobile.switcherpointed at a 10-22 copy the same way.omamobile-setup-userlinks every packaged plugin there so updates reach the user, and a link to a private copy silently pins that copy through every upgrade.After relinking with the setup script's own loop, the shade, the current switcher and the plugins that were missing (back, call, update, access) all came up on omamobile-shell 0.2.56.
This adds the gotcha to AGENTS' Userspace section: where to look first when a shell change doesn't show on a phone, and the one-line relink. Docs only;
tools/pr-checkpasses.