Skip to content

omamobile-omarchy 0.1.16: a glance view on the phone's lock (time, date, weather, notifications) - #176

Merged
derekross merged 1 commit into
mainfrom
lock-glance
Oct 30, 2026
Merged

derekross merged 1 commit into
mainfrom
lock-glance

Conversation

@derekross

Copy link
Copy Markdown
Owner

On touch-only devices the lock now opens on a glance view, the way a phone's lock screen does. It's built only from Omarchy's own lock parts and the current theme. Swipe up or tap for the PIN pad, which is the lock as it was. On a computer nothing changes.

Patch 0023 (lock-a-glance-view-for-touch-only-devices) adds plugins/lock/LockGlance.qml and LockGlance.js, and keeps LockView's diff small. The glance shows:

  • The time: large, light weight, in Style.font.family. It's 12- or 24-hour by the same rule as the home clock (bar.clockFormat).
  • The date.
  • An optional weather line: read from ~/.local/state/omamobile/weather.json and hidden when that's missing or more than 3 h old. The lock makes no network calls. The home widget doesn't write the file yet; that's a follow-up in omamobile-shell.
  • Notifications: Omarchy's own NotificationCard, static as the history uses it, read from the notifications plugin's state.
    • Grouped by app, newest three, the rest as "N more from …".
    • Nothing shows during do-not-disturb, and nothing on the lock acts on a notification.
    • ~/.local/state/omarchy/toggles/lock-hide-notification-text hides message text.

Behaviour:

  • Only one view at a time: the unused view is visible: false outside a 220 ms change. Only the blurred wallpaper sits behind either.
  • To the PIN view: a swipe up, a tap above the sensor area (the lower third stays clear for the under-display sensor), or a typed key, which is kept in the field.
  • Back to the glance: after 15 s with an empty field, when the lock is shown, and on every lock wake.
  • Kept as it was: a failed attempt stays on the PIN view, and the fingerprint PAM flow is untouched.
  • NotificationCard gets summaryLines, bodyLines and detail properties. Toasts are unchanged.

Version: 0.1.13 (#134), 0.1.14 (#162) and 0.1.15 (#171, patch 0022) are taken, so this is 0.1.16 with patch 0023. The patch also applies with --fuzz=0 on top of 0021 and 0022.

Tests:

  • test/all passes, including a qmltestrunner test against the real patched package (19 cases: glance and PIN switching, one view at a time in both directions, grouping, the hide-text toggle, the computer lock unchanged).
  • tools/pr-check passes.

Tested on the Pixel 7 Pro (2026-10-30, Omarchy 4.0.6, patches applied by the pacman hook):

  • The glance shows the time, date and notifications, in the phone's theme.
  • Two notifications from one app grouped into one card ("2 new, now").
  • Swipe and tap to the PIN pad, the 15 s return, fingerprint unlock from the glance, and PIN unlock all work.

🤖 Generated with Claude Code

…te, weather, notifications)

The phone's lock opened straight on the PIN pad, so seeing the time or
what came in meant unlocking. Patch 0023 puts a glance view in front of
the PIN view on touch-only devices (the lock-keypad toggle): the time
(system monospace, light, following the bar's clockFormat or the
locale), the date, the home screen's last weather reading, and the
notifications grouped by app, with the hint above the fingerprint mark.
A swipe up, a tap above the sensor or a typed key (kept in the field)
shows the PIN view, which is the lock as before plus a small clock. It
comes back after 15 s with an empty field and no input, and whenever the
lock is shown or the screen is woken through the lock's wake call.

Only one view shows outside the short change: the other is
visible: false, so nothing of the PIN view renders or takes touches
under the glance, and only the lock's blurred wallpaper sits behind
either. The lower third stays free of taps for the under-display
sensor, and fingerprint unlock (the Service's PAM flow) is untouched.

Everything is drawn with Omarchy's own parts and the applied theme: the
lock colours, Style fonts, sizes and spacing, and the cards are
Omarchy's NotificationCard used statically, which gains summaryLines,
bodyLines and a detail label (defaults unchanged for toasts). The lock
reads the notifications plugin's persisted toasts and history read-only,
shows none while do-not-disturb is on (no toast shows then either), and
the lock-hide-notification-text toggle replaces the text with the app
name and "Unlock to read". Weather is read from
~/.local/state/omamobile/weather.json and hidden when absent or over 3 h
old; the lock makes no network calls. On a computer the lock is
unchanged. LockView's diff is one property block, a focus guard and a
visible/opacity line on each PIN part, so it rebases with 0003, 0011 and
0014; the patch also applies on top of 0021 and 0022 from the open pull
requests.

test/lock-glance runs the patched LockView with Omarchy's real Commons
and Ui under qmltestrunner (offscreen, Quickshell stubbed): glance first
with no PIN part visible and the reverse, tap, swipe, sensor taps
ignored, digits kept, the idle return, wake, grouping, the hide-text
toggle, do-not-disturb, weather freshness, the clock format and an
unchanged computer lock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross
derekross merged commit a2c58a1 into main Oct 30, 2026
2 checks passed
@derekross
derekross deleted the lock-glance branch October 30, 2026 14:55
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>
derekross added a commit that referenced this pull request Oct 30, 2026
… setting (#185)

On the Pixel 7 Pro the lock glance showed a 24-hour time while the phone
bar and the home clock widget showed 12-hour. The bar's clockFormat in
~/.config/omarchy/shell.json is "ddd MMM d  h:mm AP". Two faults:

- The big glance time used the Qt format "h:mm". Qt counts "h" from 0
  to 23 unless the same format has an AM/PM marker, so even with the bar's
  format read, 2 pm showed as "14:02". It is now built from the hour
  (h % 12 || 12, with minutes) and still leaves AM/PM out. The small
  clock over the PIN view keeps "h:mm AP".
- shell.json was only read while the glance was active (path gated on
  the keypad toggle) and asynchronously. A failed read, such as Omarchy
  replacing the file, cleared the format, and the fallback was the
  session's Qt locale, which is C/POSIX for the shell and so 24-hour.
  It is now read at once (blockLoading, a small file), whatever the
  lock shows, again on every change and whenever the glance comes back.
  A read that fails or catches a half-written file keeps the last
  format.

The 12/24-hour rule stays the one the bar and the home clock use
(omamobile-shell HomeModel.systemTimeFormat): quoted literals ignored,
an AM/PM marker or "h" without "H" means 12-hour. Without a clockFormat
the lock now follows the bar's own default, HH:mm, so all three still
agree; it no longer falls back to the Qt locale. Patch 0023 is revised in
place, as #181 did after #176.

Tests (test/lock-glance, now under LC_ALL=C as the shell runs):
- the maintainer's format is 12-hour before the glance is active, with
  a 1-12 big time without AM/PM and a small clock with it;
- a half-written or missing shell.json keeps the last format;
- HH:mm and no clockFormat are 24-hour;
- the rule (twelveHour, quoted literals), glanceTime at 14:02, 00:05,
  12:30 and 9:41, and barClockFormat's parse.
The FileView stand-in now reads at once with blockLoading, as Quickshell
does. test/all and tools/pr-check pass, and the series applies with
--fuzz=0 to the real aarch64 Omarchy 4.0.6-1 (20 applied).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 9, 2026
…eason (#534)

linux-omarchy-mobile#176 describes the MAX77759's reboot-reason cell and
an nvmem-reboot-mode node on it, so `reboot-to bootloader` writes
0x800000fc (RSBM valid, bootloader) where Google's driver does and ABL
stops in fastboot. The cell's provider is nvmem_max77759, which this
package has blacklisted since the MAX77759 bring-up, so the reboot-mode
driver waited for its supplier and the reason was never written.

Tested on the maintainer's Pixel 7 Pro on 2026-11-08, on #176's kernel
(7.3.0-rc6-omamobile-push1-g8de6aedc7373) with nvmem_max77759 loaded by
hand: reboot-mode bound, the cell read 00 00 00 80, `reboot-to
bootloader` reached fastboot about 4 s later with no buttons (the same
command without the module did not that morning), `fastboot reboot`
returned to slot B with the cell back at 00 00 00 80, and a plain
`systemctl reboot` booted normally. The module autoloads by its
platform:max77759-nvmem alias once the blacklist is gone. On a kernel
without #176's cells it provides nothing anyone uses.

tcpci_maxim and gpio_max77759 stay blacklisted.

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
…te, weather, notifications) (derekross#176)

The phone's lock opened straight on the PIN pad, so seeing the time or
what came in meant unlocking. Patch 0023 puts a glance view in front of
the PIN view on touch-only devices (the lock-keypad toggle): the time
(system monospace, light, following the bar's clockFormat or the
locale), the date, the home screen's last weather reading, and the
notifications grouped by app, with the hint above the fingerprint mark.
A swipe up, a tap above the sensor or a typed key (kept in the field)
shows the PIN view, which is the lock as before plus a small clock. It
comes back after 15 s with an empty field and no input, and whenever the
lock is shown or the screen is woken through the lock's wake call.

Only one view shows outside the short change: the other is
visible: false, so nothing of the PIN view renders or takes touches
under the glance, and only the lock's blurred wallpaper sits behind
either. The lower third stays free of taps for the under-display
sensor, and fingerprint unlock (the Service's PAM flow) is untouched.

Everything is drawn with Omarchy's own parts and the applied theme: the
lock colours, Style fonts, sizes and spacing, and the cards are
Omarchy's NotificationCard used statically, which gains summaryLines,
bodyLines and a detail label (defaults unchanged for toasts). The lock
reads the notifications plugin's persisted toasts and history read-only,
shows none while do-not-disturb is on (no toast shows then either), and
the lock-hide-notification-text toggle replaces the text with the app
name and "Unlock to read". Weather is read from
~/.local/state/omamobile/weather.json and hidden when absent or over 3 h
old; the lock makes no network calls. On a computer the lock is
unchanged. LockView's diff is one property block, a focus guard and a
visible/opacity line on each PIN part, so it rebases with 0003, 0011 and
0014; the patch also applies on top of 0021 and 0022 from the open pull
requests.

test/lock-glance runs the patched LockView with Omarchy's real Commons
and Ui under qmltestrunner (offscreen, Quickshell stubbed): glance first
with no PIN part visible and the reverse, tap, swipe, sensor taps
ignored, digits kept, the idle return, wake, grouping, the hide-text
toggle, do-not-disturb, weather freshness, the clock format and an
unchanged computer lock.

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
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
… setting (derekross#185)

On the Pixel 7 Pro the lock glance showed a 24-hour time while the phone
bar and the home clock widget showed 12-hour. The bar's clockFormat in
~/.config/omarchy/shell.json is "ddd MMM d  h:mm AP". Two faults:

- The big glance time used the Qt format "h:mm". Qt counts "h" from 0
  to 23 unless the same format has an AM/PM marker, so even with the bar's
  format read, 2 pm showed as "14:02". It is now built from the hour
  (h % 12 || 12, with minutes) and still leaves AM/PM out. The small
  clock over the PIN view keeps "h:mm AP".
- shell.json was only read while the glance was active (path gated on
  the keypad toggle) and asynchronously. A failed read, such as Omarchy
  replacing the file, cleared the format, and the fallback was the
  session's Qt locale, which is C/POSIX for the shell and so 24-hour.
  It is now read at once (blockLoading, a small file), whatever the
  lock shows, again on every change and whenever the glance comes back.
  A read that fails or catches a half-written file keeps the last
  format.

The 12/24-hour rule stays the one the bar and the home clock use
(omamobile-shell HomeModel.systemTimeFormat): quoted literals ignored,
an AM/PM marker or "h" without "H" means 12-hour. Without a clockFormat
the lock now follows the bar's own default, HH:mm, so all three still
agree; it no longer falls back to the Qt locale. Patch 0023 is revised in
place, as derekross#181 did after derekross#176.

Tests (test/lock-glance, now under LC_ALL=C as the shell runs):
- the maintainer's format is 12-hour before the glance is active, with
  a 1-12 big time without AM/PM and a small clock with it;
- a half-written or missing shell.json keeps the last format;
- HH:mm and no clockFormat are 24-hour;
- the rule (twelveHour, quoted literals), glanceTime at 14:02, 00:05,
  12:30 and 9:41, and barClockFormat's parse.
The FileView stand-in now reads at once with blockLoading, as Quickshell
does. test/all and tools/pr-check pass, and the series applies with
--fuzz=0 to the real aarch64 Omarchy 4.0.6-1 (20 applied).

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
…eason (derekross#534)

linux-omarchy-mobile#176 describes the MAX77759's reboot-reason cell and
an nvmem-reboot-mode node on it, so `reboot-to bootloader` writes
0x800000fc (RSBM valid, bootloader) where Google's driver does and ABL
stops in fastboot. The cell's provider is nvmem_max77759, which this
package has blacklisted since the MAX77759 bring-up, so the reboot-mode
driver waited for its supplier and the reason was never written.

Tested on the maintainer's Pixel 7 Pro on 2026-11-08, on derekross#176's kernel
(7.3.0-rc6-omamobile-push1-g8de6aedc7373) with nvmem_max77759 loaded by
hand: reboot-mode bound, the cell read 00 00 00 80, `reboot-to
bootloader` reached fastboot about 4 s later with no buttons (the same
command without the module did not that morning), `fastboot reboot`
returned to slot B with the cell back at 00 00 00 80, and a plain
`systemctl reboot` booted normally. The module autoloads by its
platform:max77759-nvmem alias once the blacklist is gone. On a kernel
without derekross#176's cells it provides nothing anyone uses.

tcpci_maxim and gpio_max77759 stay blacklisted.

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.

1 participant