diff --git a/device/tegu/FINGERPRINT-PLAN.md b/device/tegu/FINGERPRINT-PLAN.md index 3c9bdf88d..f04e6a023 100644 --- a/device/tegu/FINGERPRINT-PLAN.md +++ b/device/tegu/FINGERPRINT-PLAN.md @@ -1,7 +1,7 @@ # Fingerprint plan (tegu / zumapro): fingerprint unlock on the palmtop -Status (2026-10-28): **F0 and F2-F5 passed (F4, the first RPMB write, on 2026-10-27 under D1 = A); F6a and F6b passed; F6c waits for the factory calibration, which the owner fetched on 2026-10-28.** Earlier: **research and plan only, nothing run on the palmtop for +Status (2026-10-29): **works on the owner's kernel: F0-F10 passed. The enrolled finger matches and other fingers don't, through the HAL and through fprintd, and the lock screen unlocks by fingerprint.** It runs on `7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`, the integration tree, with tg4c's LHBM loaded by hand. That LHBM isn't in the published tree yet: it's open as derekross/linux-omarchy-mobile#126, on the panel's own bands, which need no DSI reads (the reads are derekross/linux-omarchy-mobile#125, used only for the overdrive experiments). It also needs the bridge and runner fixes in #135. (F4, the first RPMB write, ran on 2026-10-27 under D1 = A.) Earlier: **research and plan only, nothing run on the palmtop for fingerprint.** Stage 16 of ALL-HARDWARE-PLAN (private). The Pixel 7 Pro stack works ([cheetah FINGERPRINT-PLAN](../cheetah/FINGERPRINT-PLAN.md), opt-in); this plan says what carries over to the Pixel 9a and what is new. @@ -533,3 +533,69 @@ needs them. and its id stay in the owner's private reference folder, never in the repository or a log. Next: hand it to the TA from Linux, without writing `mfg_data`. +- 2026-10-28, afternoon: the HAL injects the calibration itself + (`DataSynchronizer::injectMtCali`). It reads a 112-byte header from offset + 0 of `/dev/block/by-name/mfg_data` and logged "No SA calibration present" + on the zeros. The file `get-cal-url` names has exactly that layout: magic + `0xca11ca11`, version 1, and at 0x6c the payload length (file size − 112). + With the file written at offset 0 of the chroot's private `mfg_data.img` + copy (the real partition untouched), the "No SA calibration" line is gone + and the HAL sets `vendor.gf.cali.state = 1`. Next: enrollment (F8/F9, the + owner's finger). + +## F7-F8 results (2026-10-28, evening, `7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`) + +- **F7 seen by eye.** LHBM, ported into the upstream-form `panel-google-tg4c` + (`allow_lhbm=1`, `local_hbm_mode` and `local_hbm_max_timeout` on the + backlight device), lit + the circle at 120 Hz, and the owner saw a white circle at the sensor. +- **F8 passed: a finger is enrolled.** With the factory calibration in + the chroot's `mfg_data.img`, the bridge (rebuilt for the runner's + `--panel`) and `omamobile-fp-ctl enroll`: FINGER DOWN, ACQUIRED, and + PROGRESS counting down from 12 to 0, then ENROLLED. +- **F9 doesn't match yet.** Every authenticate touch comes back ACQUIRED 2 + (PARTIAL), with the HAL logging `valid_area=100` but `image_quality=29`. + A 300 ms LHBM settle changed nothing. Lead: the port wrote only `0x87 0x05`. + Google's tg4c first writes the LHBM brightness, the panel's own RGB values + per band read from 0xD1 on CMD2 page 2 plus an overdrive offset chosen by + the gray level under the circle, and then the LHBM gamma + (`0x6F 0x07; 0x87 0x01-0x04` by brightness). +- **F9, later that evening.** + DSI reads now work (`gs-dsim-cmd` read support: the read request needs + `DSIM_PKTHDR_BTA`, bit 24), so the LHBM brightness bands are read from the + panel and written with overdrive group 0 and the gamma. PARTIAL stayed. + The HAL's log then showed three bridge and runner bugs (omamobile-fingerprint + 0.1.11, PR #135): the HAL got raw touchscreen positions (10x panel pixels, + 5432,17847 for the 540,1756 circle), it captures at + `onPointerDownWithContext` (before `onUiReady`, while the circle was still + dark), and it parses the refresh rate after the `@` in + `panel0-backlight/state` (`on: 1080x2424@120`; a bare `on` logged "Failed + to parse refresh rate"). With all three fixed, enrollment completes and + authenticate captures come back GOOD and reach the matcher, but every one + is NOMATCH at `image_quality` 15-26, at screen brightness 1500 and 3628 + alike. Lead one: Google overdrives only the first stage. After the + effective delay (2 frames, 3 with IRC off) `tg4c_set_local_hbm_mode_post` + writes the normal bands, so stock captures under the normal circle, while + the port kept overdrive group 0 the whole time. From 2026-10-29 the + palmtop runs `lhbm_od=4` (the normal bands, read from the panel), and the + next step is to re-enroll and match under it. Other leads: whether the circle reaches LHBM luminance at all (nobody has yet + compared it with the shell's drawn target); the HAL's raw capture dump + (`vendor.gf.debug.dump_data=1` wrote nothing). Many misses lock the sensor + out (`LOCKOUT -1`); `omamobile-fp-ctl resetlockout` clears it. + +## F9-F10 results (2026-10-29, `7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`) + +- **F9 passed.** With `lhbm_od=4` (the normal LHBM bands read from the + panel, which is where Google's tg4c sits after its first-stage + overdrive) and a fresh enrollment, `omamobile-fp-ctl auth` gave MATCH on + the first touch twice. A different finger gave NOMATCH. +- **F10 passed.** fprintd was masked on the palmtop's own root: a link + to `/dev/null` from the same batch as the 9a's other bring-up masks + (ModemManager, NetworkManager, omamobile-aoc, omamobile-fp), made by the + private bring-up root it was installed from. Nothing in this repository + masks it. Unmasked, it + finds the bridge's device, `fprintd-enroll` completes (20 stages), and + `fprintd-verify` matches. Locked with `omarchy-shell lock lock`, the + palmtop unlocked with the enrolled finger, and refused a different finger + several times. The libfprint driver still names the device "Pixel 7 Pro + under-display fingerprint sensor". diff --git a/device/tegu/MODEM-PLAN.md b/device/tegu/MODEM-PLAN.md index 191187207..a5bbf463f 100644 --- a/device/tegu/MODEM-PLAN.md +++ b/device/tegu/MODEM-PLAN.md @@ -8,7 +8,9 @@ trains Gen1 x1 and enumerates as 144d:a5a5; M3-M5 passed: CPIF and cbd boot it to **ONLINE** (Gen3 x2) with working IPC (pktproc), no SIM yet; G1-G2 passed: gnssd loads Kepler's firmware and talks CHPP over SPI; G3 partial: our HAL client starts sessions, but Kepler's core faults at -engine start. Next: a stock GNSS capture, IOCC, the SIM. +every engine start, with the RF rails on (2026-10-28) and with the AoC told +the GNSS type (2026-10-28, evening) alike. Next: `strace` gnssd across an +engine start, a stock GNSS capture, IOCC, the SIM. The staged plan (sections F, K, U and runbooks M0.2-M6, G1-G4) is below, with each step's results under it. Kernel branches `omamobile-tegu-modem` and `omamobile-tegu-gnssif` (section K). @@ -542,6 +544,35 @@ startNmea 25; callbacks location 4, NMEA 5). longer stops the profile. Until M6 qualifies the power-off, don't stop the modem profile by hand; reboot with someone at the palmtop. +### G3, third try: rails on (2026-10-28, `7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`, round ps1 DTB with ldo9s-11s on) + +[V] With LDO9S-11S on, Kepler loads, reaches OPERATIONAL and no longer +logs "FCAL Part 1 is not done yet": the RF front end calibrates now. The +gnss-slsi HAL and our client start a session (capabilities 0xe7df, start +and startNmea ok, status SESSION_BEGIN then ENGINE_ON), but every engine +start still ends in the same fault: "KEP M7 HARDFAULT ... LR,PC 600B5B39 +0000062C" (16 times in 10 minutes, ENGINE_ON/ENGINE_OFF each time), no +NMEA. So the rails were one missing piece, not the fault itself. Indoor or +outdoor doesn't matter yet: the engine crashes before it searches. +The G3 script's HARDFAULT count missed these (gnssd wrote them outside its +window). + +### G3, fourth try: the AoC told the GNSS type (2026-10-28, evening, gn3 DTB) + +[V] With `&aoc { gnss-type = <2>; }` (kAOCGnssType, as Google's +`zumapro-phone-ignss.dtsi`), Kepler loads, goes OPERATIONAL, and the +gnss-slsi HAL and our client start a session (startNmea ok, "the HAL asks +for a location"). But every engine start still ends in the same "KEP M7 +HARDFAULT ... LR,PC 600B5B39 0000062C" (20 in 4 minutes), so the type isn't +it. In the register dump, R3 = 0x62D and PC = 0x62C: the M7 jumped +through a function pointer holding 0x62D, a Thumb address near zero, which +looks like an entry nobody filled in. Other leads from the logs: +`aiding_timemark_reader_thread: open() errno:2` (gnssd can't open its +time-mark device), `TGT_MEMS initInterface: fromBinder() failed` (the HAL's +sensor service is missing), and `libsighandler.so` not found. Next, attended +and on the charger, with the modem up: `strace -f` gnssd across one engine start, to see which +files and devices it opens or fails to open (observation only). + ### Suspend with the modem on (2026-10-27, early morning, same kernel) - **What ran:** s2idle on `7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`