Repository navigation
Conversation
…is loaded omamobile-setup-user appended the dofile of hypr/phone.lua to looknfeel.lua, which Omarchy's hyprland.lua requires; a hyprland.lua of the user's own that never loads looknfeel.lua left the phone rules out, and with them the above_lock layer rule, so the fingerprint target sat under the session lock and the owner aimed blind. The step now appends to hyprland.lua when it doesn't load looknfeel.lua, and never twice. Test added.
…is lit Restores this pull request's change: the merge at b3ceaf1 resolved to main's tree and dropped it. 0.2.46 and 0.2.47 are held by derekross#183 and derekross#197. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks, a clear diagnosis. On the 7 Pro nothing changes, because Omarchy's hyprland.lua requires looknfeel.lua, and your test covers the gate case. #99 went in first as 0.2.48, so I landed this as 0.2.49 on main, authored by you (the PR shows as closed because the commit went in directly). When the 9a next runs the setup from the package, could you paste |
|
Thanks for landing it as 0.2.49. From the palmtop now, with the line still the hand-added one (the package's setup-user hasn't run here yet): |
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel #196, #197, #426); fingerprint moves to WIP (kernel #207; the package side, #458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel #192, #206; #414). - Pixel 6 Pro: GPU scaling and cooling (kernel #189) and UFS suspend (kernel #188) merged. - Pixel 9a: GPU levels merged through kernel #96; GNSS's moving-car session (#114) and the link driver (kernel #185). - Pixel 7a: Bluetooth's device tree merged (kernel #98). The Pixel 8 Pro's row is left to #472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…is loaded (derekross#197) Omarchy's hyprland.lua loads the look-and-feel rules from looknfeel.lua, so the phone rules go to whichever file the loaded config actually requires; on the Pixel 7 Pro (Omarchy 4.0.6) that is still looknfeel.lua, so nothing changes there. Renumbered to 0.2.49 at merge, after derekross#99 took 0.2.48. Closes derekross#197 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel derekross#196, derekross#197, derekross#426); fingerprint moves to WIP (kernel derekross#207; the package side, derekross#458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel derekross#192, derekross#206; derekross#414). - Pixel 6 Pro: GPU scaling and cooling (kernel derekross#189) and UFS suspend (kernel derekross#188) merged. - Pixel 9a: GPU levels merged through kernel derekross#96; GNSS's moving-car session (derekross#114) and the link driver (kernel derekross#185). - Pixel 7a: Bluetooth's device tree merged (kernel derekross#98). The Pixel 8 Pro's row is left to derekross#472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Symptom, on the Pixel 9a today: the lock screen never showed the fingerprint target over the sensor, only the PIN pad's small icon, so the owner aimed blind and the bridge never saw a touch inside the sensor's circle; with the panel's LHBM circle lit by hand he unlocked at once, and
omarchy-shell shell call omamobile.fingerprint state ''during a verify showed the plugin active with its target window up (anomamobile-fingerprintlayer at the sensor), so the plugin itself was fine.Cause: the target's layer is drawn above the session lock only through
hl.layer_rule({ namespace = "^omamobile-fingerprint$", above_lock = 1 })in hypr/phone.lua, and omamobile-setup-user loads that file by appending adofileto the user's looknfeel.lua, which Omarchy's hyprland.lua requires. The 9a's hyprland.lua is the bring-up gate that never loads looknfeel.lua (and its user setup unit has never run, which is a separate matter for the device notes), so phone.lua never ran there, and the target sat under the lock. The same would hit any user who replaced hyprland.lua.Change: the phone-rules step appends the dofile to hyprland.lua when the user's hyprland.lua doesn't load looknfeel.lua, and never adds it twice (checked by content across ~/.config/hypr/*.lua). test/setup-user.sh gains the case. Version 0.2.47 (main is at 0.2.45, #183 takes 0.2.46).
Test on a phone: with hypr/phone.lua loaded (
grep phone.lua ~/.config/hypr/*.lua), lock, thenfprintd-verifyor the lock's own fingerprint prompt: a faint fingerprint in a ring sits over the sensor on the lock screen (hyprctl layerslistsomamobile-fingerprintwhile the verify runs).