Skip to content
Merged
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link
- **Some unattended RTC cycles wake early on the PMIC interrupt** (2 of 20 in S4, 4 of 31 in S5c, at 13-16 s instead of 30 s). Which PMIC event it is hasn't been read yet; count it, don't treat it as a failed cycle. [SUSPEND-PLAN](device/cheetah/SUSPEND-PLAN.md) S4, S5c
- **Volume Up is the one key without an internal pull** (`PUD` 0x0, as on stock), and the first freeze woke 3 s in from it with nobody touching it. It didn't recur in the 51 RTC cycles of S4 and S5c, and it isn't proven to be a false edge; if spurious wakes recur, check gpa8-5's power-down pull before blaming the wake path.
- **UFS ran its error handler around modem power changes** (PA LINERESET indications, recovered without a reset). Stock's DT shows no shared rail, clock or pin. M2.5 narrowed it down: power-on and a running link are clean, but every modem power-off is followed by one recovered UFS error-handler pass (a PA LINERESET, no I/O errors or resets). Stock powers the modem off only at shutdown, so the modem stays on once it is up (M2.6 is open), and a reboot with the modem up costs one such pass. Keep modem tests attended, don't power-cycle the modem, and check `dmesg | grep ufshcd_err_handler` after each step. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M2, M2.5, M2.6
- **Suspend with the modem up is on by default on the 7 Pro, and unqualified on the 9a.** On the Pixel 7 Pro with a kernel carrying linux-omarchy-mobile#232 (kernel-2026.11.15 and later), `omamobile-modem-sit` 0.3.42 and device-cheetah 0.1.60, the modem's sleep inhibitor is skipped and the phone sleeps with the modem up ([SUSPEND-PLAN](device/cheetah/SUSPEND-PLAN.md) M6-D, 2026-11-15: 85 wakes in 45 minutes with data back after every drop). The network drops the internet bearer every few minutes while the phone sleeps; sitd sets it up again (#817), and without that data stays down until a reboot, which is why device-cheetah 0.1.60 conflicts with an older `omamobile-modem-sit`. On an older kernel `omamobile-modem-sleep-policy` keeps the inhibitor, and the owner opts out with `/etc/omamobile/modem-suspend-disable` (from the next boot). On every other phone the rest of this entry stands. The 9a's one try (2026-10-27) also had NFC polling, which alone resets the 9a in s2idle, so the modem's part was unknown. With the sleep fixes (2026-11-09, both link drivers) it neither hung nor reset: CPIF refuses most sleeps (`suspend_cp: abort suspend`, -16, while the CP holds `cp2ap_wakeup`), and the three that were entered woke on the modem within seconds. But one sleep attempt, entered or refused, leaves CPIF unable to reach the CP (`Can't set D0 state`, its command register reading 0xffff) and the phone service timing out until a reboot, while `omamobile-sit status` goes on showing the last state read. So wherever the sleep policy keeps the inhibitor (no device declaration, a kernel without #232, the owner's opt-out), with the modem up nothing passes or goes round it (`systemctl suspend -i`, `rtcwake -m`, a write to `/sys/power/state`) except an attended test on the charger that ends in a reboot. On a 7 Pro that sleeps with the modem up, a sleep goes only through logind (auto-sleep or `systemctl suspend`), never `rtcwake -m` or a write to `/sys/power/state`: those skip the sleep hooks M6 verified (the modem told the screen is off, sitd's PrepareForSleep), and a new modem-up sleep test there (a new kernel, a change to CPIF or sitd's data path) is still the maintainer's. One exception, on W4HO-ham's own 9a only ([#809](https://github.com/derekross/omarchy-mobile/issues/809), agreed 2026-11-15): W4HO-ham's modem-up sleep series may run unattended, a new kernel's first among them, on these terms: on the charger (#758's `modem-sleep-series.sh` refuses and stops off it); every boot that had a sleep with the modem up ends in `systemctl reboot`, never `reboot-to`; a new kernel's first run is at most 10 sleeps and its result is posted before a longer one; the series stops itself on the CP not ONLINE, a UFS error line or an oops, and a hang is left to the cluster watchdog or the owner; the NV partitions stay read-only and are checked against the backup after any boot that hung or reset; the record says which rule each run ran under. CPIF's PM paths are wake-armed in code. A modem-up sleep record checks mobile data after every wake with no other route ahead of it, not once at the end: the 7 Pro's bearer drops showed only so. Keep modem tests on the charger, so upower's critical action doesn't suspend the phone mid-test. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) 6.3, [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) "Suspend with the modem on"
- **Suspend with the modem up is on by default on the 7 Pro, and unqualified on the 9a.** On the Pixel 7 Pro with a kernel carrying linux-omarchy-mobile#232 (kernel-2026.11.15 and later), `omamobile-modem-sit` 0.3.42 and device-cheetah 0.1.60, the modem's sleep inhibitor is skipped and the phone sleeps with the modem up ([SUSPEND-PLAN](device/cheetah/SUSPEND-PLAN.md) M6-D, 2026-11-15: 85 wakes in 45 minutes with data back after every drop). The network drops the internet bearer every few minutes while the phone sleeps; sitd sets it up again (#817), and without that data stays down until a reboot, which is why device-cheetah 0.1.60 conflicts with an older `omamobile-modem-sit`. On an older kernel `omamobile-modem-sleep-policy` keeps the inhibitor, and the owner opts out with `/etc/omamobile/modem-suspend-disable` (from the next boot). On every other phone the rest of this entry stands. The 9a's one try (2026-10-27) also had NFC polling, which alone resets the 9a in s2idle, so the modem's part was unknown. With the sleep fixes (2026-11-09, both link drivers) it neither hung nor reset: CPIF refuses most sleeps (`suspend_cp: abort suspend`, -16, while the CP holds `cp2ap_wakeup`), and the three that were entered woke on the modem within seconds. But one sleep attempt, entered or refused, leaves CPIF unable to reach the CP (`Can't set D0 state`, its command register reading 0xffff) and the phone service timing out until a reboot, while `omamobile-sit status` goes on showing the last state read. So wherever the sleep policy keeps the inhibitor (no device declaration, a kernel without #232, the owner's opt-out), with the modem up nothing passes or goes round it (`systemctl suspend -i`, `rtcwake -m`, a write to `/sys/power/state`) except an attended test on the charger that ends in a reboot. On a 7 Pro that sleeps with the modem up, a sleep goes only through logind (auto-sleep or `systemctl suspend`), never `rtcwake -m` or a write to `/sys/power/state`: those skip the sleep hooks M6 verified (the modem told the screen is off, sitd's PrepareForSleep), and a new modem-up sleep test there (a new kernel, a change to CPIF or sitd's data path) is still the maintainer's. On a 9a test kernel with the sleep guard turned on for zumapro ([linux-omarchy-mobile#258](https://github.com/derekross/linux-omarchy-mobile/pull/258)), 299 of 300 sleeps with the modem registered were entered and woke with the phone service kept (2026-11-13; Wi-Fi connected, mobile data checked at the end), and a refusal cost nothing; that kernel also hung once at a link power-up while awake, so on the 9a the rule is unchanged until a release carries the guard and the 9a's own declaration is decided. One exception, on W4HO-ham's own 9a only ([#809](https://github.com/derekross/omarchy-mobile/issues/809), agreed 2026-11-15): W4HO-ham's modem-up sleep series may run unattended, a new kernel's first among them, on these terms: on the charger (#758's `modem-sleep-series.sh` refuses and stops off it); every boot that had a sleep with the modem up ends in `systemctl reboot`, never `reboot-to`; a new kernel's first run is at most 10 sleeps and its result is posted before a longer one; the series stops itself on the CP not ONLINE, a UFS error line or an oops, and a hang is left to the cluster watchdog or the owner; the NV partitions stay read-only and are checked against the backup after any boot that hung or reset; the record says which rule each run ran under. CPIF's PM paths are wake-armed in code. A modem-up sleep record checks mobile data after every wake with no other route ahead of it, not once at the end: the 7 Pro's bearer drops showed only so. Keep modem tests on the charger, so upower's critical action doesn't suspend the phone mid-test. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) 6.3, [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) "Suspend with the modem on"
- **Never `systemctl restart omamobile-modem` (or stop and start it) to recover a crashed modem.** An in-place restart left raven's CP in BOOTING, and a bring-up that never reaches ONLINE sets a latch that makes the next boot skip the modem. Reboot instead. If a boot skipped it, remove the latch (`rm /var/lib/omamobile/modem-bringup-started`) and `systemctl start omamobile-modem`; `/usr/lib/omamobile-vendor/omamobile-modem-start --retry` also clears it, but run by hand it brings the modem up outside the unit (a stray `rfsd` in your shell's session). From `omamobile-modem` 0.1.13 there is a second marker, `/var/lib/omamobile/modem-up`, written at ONLINE and removed by the unit's clean stop: a boot that hung or reset with the modem up leaves it. The next boot logs "ended without a clean stop" and, from 0.1.19, starts the modem all the same (0.1.13 to 0.1.18 skipped it for that boot); a second unclean end in a row refuses "(held)" until the markers are removed the same way (cheetah [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6). On the 7 Pro the stack starts at boot by default since device-cheetah 0.1.43 ([MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6b); to keep it off from the next boot, `systemctl mask omamobile-modem-boot.target` (`unmask` turns it back on; `disable` doesn't remove device-cheetah's vendor wants link); it also holds a sleep inhibitor until the reboot. [raven MODEM-PLAN](device/raven/MODEM-PLAN.md) D4. The same on the 9a: after the modem profile has stopped, starting it again in the same boot reset the palmtop silently, a watchdog reset with nothing in pstore (the one try was in the rfsd stage). [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) G3. **From `omamobile-modem` 0.1.10, `omamobile-vendor-chroot modem check` refuses once the profile has started this boot** ("the modem profile already started this boot"), so it is no longer a post-install health check while the modem is up: it is read-only and safe to run, but a refusal means the profile ran, not that anything is wrong. After a reboot it says "preconditions met" again.
- **Linux never writes the modem's NV partitions.** The modem chroot profile (cbd, rfsd) refuses to start unless the NV partitions read `ro=1` and none is mounted, and works on checksum-verified RAM copies only. What the modem writes is lost at stop, except its writes to `efs/nv_normal.bin` (expected to hold the carrier profile, network and IMS data; the runbook confirms it) when the NV overlay is on (section 1): those are captured every 30 minutes and at the unit's stop, after the CP is off, and laid over the verified copy at the next start. `reboot-to` (and `bin/omamobile push`) skips that stop, so stop the modem first (section 2) or run `omamobile-modem nv-overlay capture`. Don't give the chroot a real block device. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) "NV overlay"

Expand Down
Loading