Add sensor type 0x969 (HP ZBook Studio x360 G5, 138a:00ab)#2
Merged
SimpleX-T merged 1 commit intoJul 7, 2026
Merged
Conversation
The 138a:00ab USB ID is shared across HP machines but maps to different sensor silicon. The EliteBook 840 G5 reports sensor type 0xd51; the ZBook Studio x360 G5 reports 0x969. Both lack native SensorTypeInfo / SensorCaptureProg entries, and empirically both work when aliased to the 0x199 capture profile -- the on-chip matcher accepts the resulting images. Mirror the existing 0xd51 handling for 0x969: - add 0x969 to line_update_type1_devices - alias 0x969 -> 0x199 in open() - accept the b[0]==3 finger interrupt when real_device_type is 0x969 Verified on an HP ZBook Studio x360 G5: init + calibration + enroll (5 stages, enroll-completed) + verify (verify-match).
This was referenced Jul 7, 2026
SimpleX-T
added a commit
that referenced
this pull request
Jul 7, 2026
Rolls up: - 0x969 support (ggiesen #2, Karloss1234) - post-resume 0x969 recovery (Karloss1234) - 0404 friendlier error at reset_blob (bcoutts, ntoyiakhona06) - del_record db_write_enable fix + flash-full pre-check (Karloss1234) - VerifyStart watchdog for wedged-chip state - README caveats for 0xd51/0x969 Full context in uunicorn#256.
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
2 participants
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.
The
138a:00abUSB ID is shared across HP machines but maps to different sensor silicon. This branch handles the HP EliteBook 840 G5 variant (sensor type0xd51). The HP ZBook Studio x360 G5 uses the same138a:00abPID but a different chip reporting sensor type0x969(identifies as "57K0 ..."), which the0xd51aliasing doesn't cover.It's a 57K0-family part, so it aliases cleanly to the same
0x199capture profile -- confirmed on hardware:bytes_per_line=0x78 repeat_multiplier=2 lines_per_calibration_data=112 line_width=112, identical to0x199. This mirrors the existing0xd51handling for0x969:0x969toline_update_type1_devices0x969->0x199inSensor.open()b[0]==3finger interrupt whenreal_device_typeis0x969Verified end-to-end on an HP ZBook Studio x360 G5: init + calibration + enroll (5 stages,
enroll-completed) + verify (verify-match). Also drives fine through Linux Mint'sfingwitGUI (via open-fprintd).This is the ZBook
00abvariant of upstream uunicorn#181 / uunicorn#238.