diff --git a/device/tegu/FINGERPRINT-PLAN.md b/device/tegu/FINGERPRINT-PLAN.md index f04e6a023..28e3b777c 100644 --- a/device/tegu/FINGERPRINT-PLAN.md +++ b/device/tegu/FINGERPRINT-PLAN.md @@ -409,7 +409,7 @@ needs them. | LHBM on tg4c | 120 Hz only; brightness sets read from the panel; dim captures without overdrive | | Touch scale and geometry | 10x touch coordinates; sensor location unknown until F6 | | gpp1 shared with touch reset | a wrong pin write drops the touchscreen | -| LDO15S | always-on on stock; our S2MPG15 description must not switch it off as unused | +| LDO15S | always-on on stock; our S2MPG15 description must not switch it off as unused. One exception, on purpose: SLEEP-PLAN S2 turns it off for a single boot to measure its share of the sleep drain, with the fingerprint service and anything that starts the trusted app or `storageproxyd` stopped before the push and until the rollback (an enrolled template lives in Trusty) | | HAL dependencies | display, sensors, power, HIDL thermal; expect a few shim/prop iterations at F6c | ## F0 results (2026-10-27, night) diff --git a/device/tegu/SLEEP-PLAN.md b/device/tegu/SLEEP-PLAN.md index 148b32977..168d7f129 100644 --- a/device/tegu/SLEEP-PLAN.md +++ b/device/tegu/SLEEP-PLAN.md @@ -170,9 +170,7 @@ a G3 (GNSS) session: GNSS is off for this boot. S2 turns LDO15S off on purpose, for this one boot, although FINGERPRINT-PLAN's Risks table says our S2MPG15 description must not switch it off as unused: the sensor is unpowered for the boot, and that -is the point of the measurement. FINGERPRINT-PLAN (on -'s branch) gets the -matching note as a follow-up once it is on main. Steps: +is the point of the measurement. FINGERPRINT-PLAN's Risks table names this exception. Steps: 1. **Before (read-only).** On the running DTB, 60 s or more after boot, save `/sys/kernel/debug/regulator/regulator_summary` to @@ -187,8 +185,8 @@ matching note as a follow-up once it is on main. Steps: that starts the trusted app or `storageproxyd` (the `omamobile-fp-stage` transient unit, `omamobile-fp-chroot start …` by hand, fprintd) are disabled or masked before the push and put back after the rollback. - F6c is still writing secure objects, and nothing in Trusty should meet - a sensor with no power while the calibration question is open. Check + An enrolled template lives in Trusty, and nothing in Trusty should + meet a sensor with no power. Check after the boot: `systemctl list-units 'omamobile-fp*'` empty, no `storageproxyd` process. Don't start the modem in this boot: the S5300's GNSS supplies are off. Nothing on the palmtop starts the modem