Repository navigation
omamobile-fingerprint 0.1.17, device-panther 0.1.11: fingerprint on the Pixel 7 (from #458) - #485
Merged
Merged
Conversation
The Pixel 7's vendor image ships the 7 Pro's fingerprint files under the
same names (g7.app, the Goodix HAL, the C++ Trusty KeyMint and
Gatekeeper, storageproxyd, trusty_apploader), and its stock dtbo has the
7 Pro's sensor node. What differs is the panel and the touchscreen.
The runner fell back to cheetah on any board but the 9a. Detect
google,gs201-panther and give it g7.app, the C++ KeyMint, its panel
(1080x2400 at 60 Hz, ABL's panel name sdc-s6e3fc3-p10) and its
touchscreen ("FocalTech FT3658"); the touchscreen name is now per phone.
props-panther.conf sets ro.hardware=panther. extract-fingerprint-vendor
takes -d panther with the 7 Pro's file list.
On the Pixel 7 with this package's files copied by hand (not pacman -U),
enrollment and unlock passed (device/panther/FINGERPRINT-PLAN.md, P5). test/all
passes, and fails when panther's touchscreen name is changed.
I used AI help (Claude) to work on this.
…ates The Pixel 7's stock dtbo (board 0x30406) has the same goodixfp node, reset pin and LDO15S supply as the 7 Pro's 0x30306, and its vendor image the same trusted app and HALs. The plan records that evidence, what differs (Trusty not yet started on panther, the S6E3FC3 panel without local HBM in our driver, the FT3658 touchscreen), and the gates P1-P5 with their stop conditions. The overlays enable Trusty, then the sub-PMIC and the sensor, on a kernel with the panther fingerprint DT commit. Compiled with dtc and applied with fdtoverlay: they change exactly the three status properties, and the sensor overlay refuses a DTB without the commit. I used AI help (Claude) to work on this.
The Pixel 7's S6E3FC3 panel gets local HBM in the kernel branch panther-lhbm, behind the same allow_lhbm module parameter as the 7 Pro's s6e3hc4. Add its line to omamobile-fingerprint-lhbm.conf; test/all checks it as it does the other two, and fails when it is removed. On the Pixel 7 the same line ran from a hand-written modprobe.d file, not this package's: the panel lit the circle and enrollment passed (P5). I used AI help (Claude) to work on this.
omamobile-fp's unit loads goodix_fp and its runner loads sg when it needs the RPMB LUN; udev would otherwise load sg for every SCSI device (raw SG_IO nodes past the read-only guard) and goodix_fp whenever the sensor node is enabled. The lines and their reasons are the 7 Pro's. Unlike the 7 Pro's file, Trusty is not blacklisted. There the sound start (omamobile-aoc-start) loads it; this package has no such loader, so with the trusty_* lines nothing would create /dev/trusty-ipc-dev0 and omamobile-fp would be skipped by its condition. Trusty loads from the DT's /trusty node, as it did on the Pixel 7 where P5 passed. test/all checks that both modules stay blacklisted and that no trusty line is added, and fails either way. On the Pixel 7 this file, copied by hand to /usr/lib/modprobe.d (not pacman -U), went through a reboot: Trusty loaded from the DT, omamobile-fp started by itself and the finger unlocked the phone (P5). I used AI help (Claude) to work on this.
Trusty started on the Pixel 7 on 2026-11-03 under the sound bring-up's
overlay ("trusty version", "selected api version: 5", the trusty_ipc
vrings); what P2 still has to show is the device node and the cpu 7
line. Local HBM for the S6E3FC3 is now a local kernel commit, from
Google's GPL panel driver; section 4 says what it does and what to
check on the phone.
I used AI help (Claude) to work on this.
…O15S The camera overlays enable the sub-PMIC too, so the base DTB keeps LDO15S disabled, as it does the camera's LDO12S, and the sensor overlay enables it. P1 to P4 passed on a Pixel 7 on 2026-11-04 (section 6): Trusty answers, its keymaster, gatekeeper and apploader ports accept a connection, and goodix_fp switches LDO15S on while the sensor is open and off after, with no other rail changing. P5 is not run. I used AI help (Claude) to work on this.
With the NDK path of fingerprint/Makefile (r27c), bionic declares pipe2() only under _GNU_SOURCE, and -Werror stops the bridge on the implicit declaration. Define it first, as the shim does. Both programs then build without warnings, and test/all passes with them. I used AI help (Claude) to work on this.
On a Pixel 7, persist:/ss/0 is a 0-byte regular file whose ctime is from the factory (1 Jan 2020), in the 2026-11-03 and 11-04 backups alike: its Trusty never committed TDP, and stock's storageproxyd serves that empty file on every boot (init.gs201.rc links /data/vendor/ss/persist to persist's /ss). The runner refused it, as it refuses a missing /ss/0. Take an empty regular /ss/0 (debugfs stat: regular, Size 0) as an empty TDP copy and record its hash; a missing or unreadable one is still refused, and the existing checks still refuse once the copy or persist:/ss/0 changes. test/preflight covers it, and fails with the old runner. Run on the Pixel 7 on 2026-11-04 and 11-06 (FINGERPRINT-PLAN P5): the stack came up, a finger enrolled and unlocked, and the TDP copy was still the empty file afterwards. I used AI help (Claude) to work on this.
The preflight test now covers the line between an empty persist:/ss/0 and one that can't be read: a dump that yields nothing while stat says a regular file of 4096 bytes, and a /ss/0 that isn't a regular file. Both are refused with no copy and nothing recorded. Removing either the size or the type check from persist_dump_tdp() now fails its case. The Pixel 7's plan: the status line says P1 to P5 passed, the kernel is linux-omarchy-mobile#207 instead of a local branch and commit, the results are section 5 (there was no section 5), the panel driver on omamobile doesn't have local HBM yet, and Trusty gets the 7 Pro's guarded start before a Pixel 7 DTB turns it on by default. I used AI help (Claude) to work on this.
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…he Pixel 7 (derekross#458) (derekross#485) The Pixel 7 Pro's fingerprint stack (Trusty TA, HAL and the guarded runner) on the Pixel 7, with per-device values only where the Pixel 7 differs (panel, touchscreen). The runner accepts an empty persist:/ss/0 as the TDP copy, as stock has served it since the factory; tests pin the line between empty and unreadable (a non-empty file whose dump fails, and a non-regular file, are refused with no copy and no record). P1 to P5 ran on the contributor's Pixel 7: an enrolment that survives a reboot, with the unit starting the stack by itself. device-panther 0.1.11 because main ships 0.1.10. Co-Authored-By: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
angelrenefm's #458, merged onto main with device-panther set to 0.1.11. The branch kept 0.1.10, which main already ships from #475, and git merged it without a conflict, so the collision would have been silent. The maintainer approved the guard change (an empty
persist:/ss/0accepted as the TDP copy) on #458, with the tests that tell empty from unreadable. The review re-ran their mutations.🤖 Generated with Claude Code