Skip to content

omamobile-omarchy 0.1.19: fingerprint on the lock only when a finger is enrolled - #171

Merged
derekross merged 1 commit into
mainfrom
fix-170-fingerprint-retry
Oct 30, 2026
Merged

derekross merged 1 commit into
mainfrom
fix-170-fingerprint-retry

Conversation

@derekross

Copy link
Copy Markdown
Owner

Fixes #170.

On a phone with omamobile-fingerprint installed and no finger enrolled, the lock starts a pam_fprintd attempt about 3.4 times a second for as long as it is up. Each attempt fails at once with PAM_AUTHINFO_UNAVAIL and is retried 250 ms later. One night logged 130,164 failed attempts, each reaching fprintd and polkit, and an A/B run in the issue measured about 55-62 mA more draw with the screen off.

The cause is Omarchy 4.0.6's check, fprintd-list "$USER" | grep -qi finger, which also matches "User … has no fingers enrolled …". Because omamobile-fingerprint ships the PAM file and depends on fprintd, only that grep decides, and it says yes.

What changes (omamobile-omarchy 0.1.15, patch 0022): a backport of the probe half of upstream's 879d6583d (omacom/omarchy#7158, so far only in the 4.5 pre-releases).

  • Lock probe: LC_ALL=C fprintd-list "$USER" 2>&1, read by FingerprintModel.classifyProbe(). An enrolled-print row ( - #0: …) means yes; "has no fingers enrolled", or no PAM file, means no; anything else is unknown.
  • Unknown answers never turn fingerprint off. The lock asks again after 1 s, doubling to 40 s, while it is up.
  • omarchy-apply-lock matches the same row, removes the fingerprint PAM file only on a definite no, and keeps it when the probe fails.

Left out on purpose: the rest of 879d6583d (the attempt backoff and "reader unavailable" notice, the fprintd resume hook, the enrollment changes). A phone with a finger enrolled behaves as before: a mismatch still retries at 250 ms. omamobile-fingerprint keeps owning the PAM file (TOUCH-PLAN 0.1).

Version: 0.1.13 and 0.1.14 are taken by open #134 and #162, and patch 0021 by #134, so this takes 0.1.15 and 0022. Whichever merges later rebases version.

Tests:

  • packages/omamobile-omarchy/test/all passes; the series applies with --fuzz=0 to the real aarch64 omarchy 4.0.6-1.
  • New checks run the patched lock's own probe command against a fake fprintd-list (no fingers enrolled, an enrolled print, a failed call, no PAM file) and classify the output, and run the patched omarchy-apply-lock the same way.
  • tools/pr-check and tests/packages (22 suites) pass.

Not yet tested on a phone. On a phone with nothing enrolled, after omamobile-omarchy-patches status shows 0022 applied: lock it, and journalctl --user -f | grep omarchy-lock-fingerprint should show no new attempts. On cheetah, with a finger enrolled, the lock should still unlock with a finger.

🤖 Generated with Claude Code

derekross added a commit that referenced this pull request Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were
  closed because they landed unchanged through kernel #134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the
  2026-10-28 notes. Touch stays WIP: kernel #134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel #133)
  and the kernel option with the touch notes (#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names
  its open kernel PR, #116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133)
  records it scanning through its own UART; kernel #98 and #98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes
  the merged tier 1 auto-sleep (#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open #171, #172, #174-#176.
- Wanted: coral's #52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (#55, #56, #58,
  #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and
  kernel #115, both open.

The Pixel 9a row and the Pixel 9 family line are left to #165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…is enrolled

Omarchy 4.0.6's lock and omarchy-apply-lock decide fingerprint is set up
with `fprintd-list "$USER" | grep -qi finger`, which also matches
"User ... has no fingers enrolled ...". omamobile-fingerprint installs
/etc/pam.d/omarchy-lock-fingerprint and pulls in fprintd, so on a phone
with nothing enrolled only that grep decides, and it says yes. The lock
then starts a pam_fprintd attempt that fails at once (PAM_AUTHINFO_UNAVAIL,
code 9) and retries 250 ms later for as long as it is up: 130,164 failed
attempts in one night on a Pixel 7 Pro, about 3.4 a second, each reaching
fprintd and polkit, and 55-62 mA (roughly 12 % of the phone's draw) in an
A/B run against the PAM file moved aside (#170).

Upstream fixed this in 879d6583d ("Fix fingerprint enrollment and
lock-screen recovery", omacom/omarchy#7158), which is only in the 4.5
pre-releases. Patch 0022 backports its probe half:

- the lock's probe becomes `LC_ALL=C fprintd-list "$USER" 2>&1`, read by
  FingerprintModel.classifyProbe(): yes only for an enrolled-print row
  (" - #0: ..."), no for "has no fingers enrolled" (or no PAM file),
  unknown otherwise; an unknown answer never turns fingerprint off and is
  asked again after 1 s, doubling to 40 s, while the lock is up;
- omarchy-apply-lock matches the same row, removes the fingerprint PAM
  file only on a definite no, and keeps it when the probe fails.

The rest of 879d6583d (the attempt backoff and "reader unavailable"
notice, the fprintd resume hook, the enrollment changes) is left out, so
a phone with a finger enrolled behaves as before: a mismatch still
retries at 250 ms. omamobile-fingerprint keeps owning the PAM file
(TOUCH-PLAN 0.1); with the probe fixed, the file's presence no longer
counts as setup on its own.

test/patches.py runs the patched lock's own probe command against a fake
fprintd-list with the issue's "has no fingers enrolled" text, an enrolled
print and a failed call, and puts the output through classifyProbe; it
runs the patched omarchy-apply-lock the same way. The series applies with
--fuzz=0 to the real aarch64 omarchy 4.0.6-1.

0.1.13 and 0.1.14 are taken by open #134 and #162 (and patch 0021 by

Fixes #170

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross derekross changed the title omamobile-omarchy 0.1.15: fingerprint on the lock only when a finger is enrolled omamobile-omarchy 0.1.19: fingerprint on the lock only when a finger is enrolled Oct 30, 2026
@derekross
derekross force-pushed the fix-170-fingerprint-retry branch from 7823045 to bef0469 Compare October 30, 2026 19:02
@derekross

Copy link
Copy Markdown
Owner Author

Rebased onto today's main, which has the glance lock (0.1.16–0.1.18), and renumbered to 0.1.19. Patch 0022 still applies with --fuzz=0 on top of 0023, and test/all passes.

@derekross
derekross merged commit b95ddb2 into main Oct 30, 2026
2 checks passed
@derekross
derekross deleted the fix-170-fingerprint-retry branch October 30, 2026 19:11
@jkjoplin

Copy link
Copy Markdown
Contributor

Tested on a Pixel 7 Pro (cheetah) with no finger enrolled: this stops the loop.

Setup.

  • Kernel 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be, omarchy 4.0.6-1, omamobile-fingerprint 0.1.8-1, fprintd 1.94.5-2, omamobile-fp disabled.
  • /etc/pam.d/omarchy-lock-fingerprint in place and unchanged: its sha256, size and mtime match the entry in omamobile-fingerprint 0.1.8-1's mtree.
  • Run inside the session, LC_ALL=C fprintd-list "$USER" ended with User <user> has no fingers enrolled for Pixel 7 Pro under-display fingerprint sensor (Omarchy Mobile)., exit 0.
  • Both runs are in the same boot. I locked with omarchy-system-lock and unlocked with the PIN on the screen. The counts are lines with with config "omarchy-lock-fingerprint" in the user's journal.

Before, omamobile-omarchy 0.1.12-1. Locked from 16:37:36Z to 16:41:15Z (3 min 39 s).

  • 748 attempts, 3.4 a second.
  • In the first 30 s: 102 attempts and 102 (code 9) errors.

The install.

  • I built 7823045 on the phone with makepkg and installed it with pacman -U.
  • From 0.1.12 to this branch, the package source changes only in 0022, test/patches.py and version. So this tests 0022 on top of 0.1.12's patches. main's lock changes since then (omamobile-omarchy 0.1.16: a glance view on the phone's lock (time, date, weather, notifications) #176, omamobile-omarchy 0.1.17, omamobile-shell 0.2.41: the lock glance after hands-on testing #181) weren't on the phone.
  • omamobile-omarchy-patches status: result: ok, 20 applied, 0 already in Omarchy; 3 files changed, with 0022 listed under applied:.
  • After pacman -U, the running shell didn't reload. quickshell had the same PID and logged no Configuration Loaded. So I ran omarchy-restart-shell before locking, and the new process loaded the new files. The normal update flow runs that restart (omarchy-update-restart). Installed with pacman -U alone, as here, the test needs it between "status shows 0022 applied" and "lock it".

After, 0.1.15-1 from this branch. Locked from 16:42:25Z to 17:01:02Z (18 min 37 s).

  • 0 attempts.
  • The shell started no PAM session of any config in the first 60 s.
  • An unfiltered 15 s capture of the system bus while locked (dbus-monitor --system) had nothing naming fprintd. In Lock screen retries fingerprint every 250 ms all night when no finger is enrolled #170, a 10 s capture had fprintd receiving GetDevices and ListEnrolledFingers 35 times.
  • The PIN unlock went through omarchy-lock-password: Authenticated successfully.

Not tested:

  • A phone with a finger enrolled. Opting in writes RPMB, and I haven't done that on this phone.
  • omarchy-apply-lock's change.
  • The probe's unknown path and its 1-40 s backoff.
  • 0022 rebased onto main's 0.1.17.

Somnius added a commit to Somnius/omarchy-mobile that referenced this pull request Nov 1, 2026
…ator

Three overlays for the MAX77759 steps of the battery plan, none default,
listed through DTB_OVERLAYS like the other devices':

- battery-clk-test: CMU_PERIC1 and its sysreg, USI11 and the bus still off
  (step M2b);
- battery-i2c-test: also USI11 and hsi2c_11, the bus of the gauge, PMIC,
  charger registers and Type-C controller (M3). They need kernel derekross#163;
- gauge-model: Google's ModelGauge m5 model for the pack, as
  maxim,fg-model and maxim,fg-params on the fuel gauge (M4c).

Without a model the gauge stays in its power-on state (Status 0x0002,
Config 0x2354) and reports a battery temperature stuck at exactly 22.0 C:
the same gauge on a Pixel 7 does the same without its model and reads
33.1 C with it (kernel derekross#171). With default-a1-0k (what Google's driver
falls back to for an unknown pack) loaded through this overlay the driver
logs "battery model loaded (DesignCap 0x994, TaskPeriod 0x2d00)", the
power-on bit clears, and the temperature reads 34.4 C and moves. The pack
(ATL, COS or LSN) is not known yet, so the percentage may be a few points
off; the charge voltage comes from the device tree, not the model.

tools/gen-gauge-overlay.py writes the overlay from Google's stock husky
node, so no number is typed by hand: each stock u32 table cell becomes
two u16 words, the stock parameter bytes become big-endian u16 words in
the order of struct max77759_fg_params. The shipped gauge-model.dtso is
its output for default-a1-0k.

tests/device-overlays compiles all three with dtc -@ (48 overlays ok).
Booted on a Pixel 8 Pro (7.3.0-rc6, slot B): all three, in order.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were
  closed because they landed unchanged through kernel derekross#134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the
  2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133)
  and the kernel option with the touch notes (derekross#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names
  its open kernel PR, derekross#116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133)
  records it scanning through its own UART; kernel derekross#98 and derekross#98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes
  the merged tier 1 auto-sleep (derekross#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176.
- Wanted: coral's derekross#52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58,
  derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and
  kernel derekross#115, both open.

The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…is enrolled (derekross#171)

Omarchy 4.0.6's lock and omarchy-apply-lock decide fingerprint is set up
with `fprintd-list "$USER" | grep -qi finger`, which also matches
"User ... has no fingers enrolled ...". omamobile-fingerprint installs
/etc/pam.d/omarchy-lock-fingerprint and pulls in fprintd, so on a phone
with nothing enrolled only that grep decides, and it says yes. The lock
then starts a pam_fprintd attempt that fails at once (PAM_AUTHINFO_UNAVAIL,
code 9) and retries 250 ms later for as long as it is up: 130,164 failed
attempts in one night on a Pixel 7 Pro, about 3.4 a second, each reaching
fprintd and polkit, and 55-62 mA (roughly 12 % of the phone's draw) in an
A/B run against the PAM file moved aside (derekross#170).

Upstream fixed this in 879d6583d ("Fix fingerprint enrollment and
lock-screen recovery", omacom/omarchy#7158), which is only in the 4.5
pre-releases. Patch 0022 backports its probe half:

- the lock's probe becomes `LC_ALL=C fprintd-list "$USER" 2>&1`, read by
  FingerprintModel.classifyProbe(): yes only for an enrolled-print row
  (" - #0: ..."), no for "has no fingers enrolled" (or no PAM file),
  unknown otherwise; an unknown answer never turns fingerprint off and is
  asked again after 1 s, doubling to 40 s, while the lock is up;
- omarchy-apply-lock matches the same row, removes the fingerprint PAM
  file only on a definite no, and keeps it when the probe fails.

The rest of 879d6583d (the attempt backoff and "reader unavailable"
notice, the fprintd resume hook, the enrollment changes) is left out, so
a phone with a finger enrolled behaves as before: a mismatch still
retries at 250 ms. omamobile-fingerprint keeps owning the PAM file
(TOUCH-PLAN 0.1); with the probe fixed, the file's presence no longer
counts as setup on its own.

test/patches.py runs the patched lock's own probe command against a fake
fprintd-list with the issue's "has no fingers enrolled" text, an enrolled
print and a failed call, and puts the output through classifyProbe; it
runs the patched omarchy-apply-lock the same way. The series applies with
--fuzz=0 to the real aarch64 omarchy 4.0.6-1.

0.1.13 and 0.1.14 are taken by open derekross#134 and derekross#162 (and patch 0021 by

Fixes derekross#170

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lock screen retries fingerprint every 250 ms all night when no finger is enrolled

2 participants