[BW-SLEEP-02] Show sleep countdown in system media controls and add shake grace/sensitivity #77

Open
opened 2026-09-22 00:03:21 +02:00 by alexander · 5 comments
Owner

Product intent

Make an active sleep timer glanceable from Android system media controls, including the collapsed/background surface, and make shake-to-restart usable at the exact moment the timer expires.

Requirements

  • While a sleep timer is active, show its authoritative remaining time in Android system media controls/notification, not only as a timer action icon.
  • Preserve the existing timer action that extends the playback-owned timer.
  • On Android 13+ use MediaSession/MediaItem metadata rather than relying on notification-provider-only customization, because System UI owns the media card.
  • When shake-to-restart is enabled, allow a shake for a configurable grace period after natural timer expiry to restart the timer and resume playback.
  • Default grace period: 10 seconds.
  • Grace period must be configurable and may be turned off.
  • Add configurable shake sensitivity with Low / Normal / High choices. Normal must preserve the current threshold.
  • Motion sensing must never remain active indefinitely: it is allowed only while a timer is active or during the bounded post-expiry grace period.
  • Manual cancellation, book change/service teardown, or disabling shake-to-restart must not leave a stale grace window.
  • A grace-period restart after an automatic scheduled timer expiry is explicit listener intent and must preserve the existing schedule invariants.

Acceptance

  • Compact/background Android media controls visibly include the active sleep countdown.
  • Expanded controls retain the sleep timer action and authoritative countdown.
  • Shake within the configured grace period after natural expiry resumes playback and starts the same timer mode again.
  • Shake after the grace deadline does nothing and sensing is stopped.
  • Grace Off stops sensing immediately when the timer expires.
  • Sensitivity changes are persisted, immediately affect active sensing, and are covered by deterministic threshold tests.
  • Existing timer, schedule, notification-button, history, rewind, and sync behavior remains covered.

Primary owner: Playback & Lifecycle Agent.
Review lenses: Android System & Auto Agent; Test & Acceptance Agent.

## Product intent Make an active sleep timer glanceable from Android system media controls, including the collapsed/background surface, and make shake-to-restart usable at the exact moment the timer expires. ## Requirements - While a sleep timer is active, show its authoritative remaining time in Android system media controls/notification, not only as a timer action icon. - Preserve the existing timer action that extends the playback-owned timer. - On Android 13+ use MediaSession/MediaItem metadata rather than relying on notification-provider-only customization, because System UI owns the media card. - When shake-to-restart is enabled, allow a shake for a configurable grace period after natural timer expiry to restart the timer and resume playback. - Default grace period: 10 seconds. - Grace period must be configurable and may be turned off. - Add configurable shake sensitivity with Low / Normal / High choices. Normal must preserve the current threshold. - Motion sensing must never remain active indefinitely: it is allowed only while a timer is active or during the bounded post-expiry grace period. - Manual cancellation, book change/service teardown, or disabling shake-to-restart must not leave a stale grace window. - A grace-period restart after an automatic scheduled timer expiry is explicit listener intent and must preserve the existing schedule invariants. ## Acceptance - Compact/background Android media controls visibly include the active sleep countdown. - Expanded controls retain the sleep timer action and authoritative countdown. - Shake within the configured grace period after natural expiry resumes playback and starts the same timer mode again. - Shake after the grace deadline does nothing and sensing is stopped. - Grace Off stops sensing immediately when the timer expires. - Sensitivity changes are persisted, immediately affect active sensing, and are covered by deterministic threshold tests. - Existing timer, schedule, notification-button, history, rewind, and sync behavior remains covered. Primary owner: Playback & Lifecycle Agent. Review lenses: Android System & Auto Agent; Test & Acceptance Agent.
Author
Owner

Canonical acceptance staging — 2026-09-24

Reviewed main / acceptance APK source: 88ae231ddc01897d83e24968bed5443ea861aedd
Merged implementation: PR #84, accepted head 585ab7a4586b7764d0da977150f3230de9bcd8ca, merge commit ca080a875f95e7e50a3944e1810cf9c76194c167.
Exact-head CI: Forgejo run #265 / backend run 1195 — success: verifyDebug, 2597 tests / 0 failures, ktlint 0, detekt 0, Android Lint 0 errors/0 warnings, Room schemas current.
Later shared-service regression evidence: PR #89 exact head passed run #270 with 2606 tests / 0 failures and the full quality gate; current-main push run #271 passed at 88ae231d....

Acceptance matrix — implementation / automated evidence

  • PROVEN — automated: the playback-owned SleepTimerState.remaining is the authoritative countdown source. PlaybackService observes it and republishes both metadata and media-button state on every change.
  • PROVEN — automated: Android 13+ compact/background text projection is built through current MediaItem/MediaMetadata, preserving/restoring the ordinary byline and replacing rather than compounding countdown ticks.
  • PROVEN — automated: the active timer action remains a real session command and is eligible for both the forward compact slot and overflow/expanded presentation. Layout tests prove it coexists with Car/Headset and skip controls rather than deleting transport actions.
  • PROVEN — automated: post-expiry shake grace defaults to 10 seconds, supports Off, and is bounded to a maximum of 10 seconds.
  • PROVEN — automated: Low / Normal / High sensitivity exist; Normal is the pre-setting 12 m/s² above gravity threshold, High is easier and Low harder.
  • PROVEN — automated: grace/sensitivity settings persist; the active sensor listener is re-registered when sensitivity changes.
  • PROVEN — automated: sensing exists only while a timer is running or while an unclaimed bounded post-expiry grace is valid.
  • PROVEN — automated: natural expiry can create grace; a valid grace shake resumes through the canonical playback owner and starts the same timer mode again rather than issuing raw Play.
  • PROVEN — automated: a shake at/after the half-open grace deadline does nothing; Grace Off stops sensing immediately at expiry.
  • PROVEN — automated: manual cancel tears the timer/sensing state down.
  • PROVEN — automated: book replacement, service/player replacement, newer Play/Pause/seek/Stop/media-replacement intents and expired claims revoke stale grace authority.
  • PROVEN — repository/product decision: turning shake-to-restart off invalidates grace authority and reconciles the sensor owner immediately; no independent “enabled” sensor lifecycle exists outside SleepTimerController.
  • PROVEN — automated: scheduled-timer grace preserves the current schedule contract: a claim cannot commit after its civil occurrence has ended; a valid pre-end shake can restart while a post-end shake cannot.
  • PROVEN — automated: race coverage exists for rapid double shakes, suspended session creation/freshness, stale service generations and automatic-expiry persistence.

What CI cannot prove

There is no trustworthy physical evidence yet for actual Android System UI rendering, real accelerometer thresholds, screen-off behavior or Bluetooth/headset behavior. Green CI is not being treated as a substitute.

Acceptance APK

Forgejo Build APK run #272 produced:

  • artifact bookwave-debug-0.10.6.1-2272
  • APK bookwave-debug-0.10.6.1-2272.apk
  • package org.homebord.bookwave.debug
  • exact source 88ae231ddc01897d83e24968bed5443ea861aedd
  • signer verified against the configured BookWave keystore
  • artifact build only; no ceremonial rerun of verifyDebug.

Required physical matrix

Use the APK above and record the observed value/state at each step, not only “pass”.

  1. Start audiobook playback and start a sleep timer.
  2. Inspect compact Android system media controls: remaining time must be visibly readable and change.
  3. Inspect expanded controls: timer action must still be present and actionable.
  4. Let the countdown advance/extend it; verify both surfaces follow the playback-owned remaining state.
  5. Put the app in background and turn the screen off; re-open controls and verify the same timer state.
  6. Let a short timer expire naturally; playback must pause per the ordinary timer contract.
  7. With shake enabled, Grace = 10 s, Normal sensitivity: shake inside grace → playback resumes and the same timer mode starts again.
  8. Repeat and shake after grace → nothing happens.
  9. Set Grace = Off; expire and shake immediately → nothing happens / sensing has ceased.
  10. Exercise Low / Normal / High with deliberately different movement strength; setting must persist and High should trigger more easily than Normal, Normal more easily than Low.
  11. Cancel a timer manually; movement afterwards must not reveal leftover grace/sensing.
  12. Change book and, where practical, recreate/tear down playback service while grace could otherwise exist; no stale shake restart may survive.
  13. Disable shake-to-restart while a timer is active and during a grace opportunity; motion must stop having effect.
  14. Repeat representative timer/expiry behavior through Bluetooth/headset and confirm playback remains sane.
  15. When combined with #33, include an automatically scheduled timer and verify its grace cannot revive it after the applicable schedule occurrence has ended.

Host/device-dependent criteria above are all STILL REQUIRES PHYSICAL TEST. The Android 13+/System UI wording is specifically not accepted until the actual device renders it.

This matrix should be run in the same device session as #33 rather than creating a second overnight/screen-off exercise.

Result

READY FOR PHYSICAL ACCEPTANCE

## Canonical acceptance staging — 2026-09-24 **Reviewed main / acceptance APK source:** `88ae231ddc01897d83e24968bed5443ea861aedd` **Merged implementation:** PR #84, accepted head `585ab7a4586b7764d0da977150f3230de9bcd8ca`, merge commit `ca080a875f95e7e50a3944e1810cf9c76194c167`. **Exact-head CI:** Forgejo run #265 / backend run 1195 — success: `verifyDebug`, **2597 tests / 0 failures**, ktlint 0, detekt 0, Android Lint 0 errors/0 warnings, Room schemas current. **Later shared-service regression evidence:** PR #89 exact head passed run #270 with **2606 tests / 0 failures** and the full quality gate; current-main push run #271 passed at `88ae231d...`. ### Acceptance matrix — implementation / automated evidence - **PROVEN — automated:** the playback-owned `SleepTimerState.remaining` is the authoritative countdown source. `PlaybackService` observes it and republishes both metadata and media-button state on every change. - **PROVEN — automated:** Android 13+ compact/background text projection is built through current `MediaItem/MediaMetadata`, preserving/restoring the ordinary byline and replacing rather than compounding countdown ticks. - **PROVEN — automated:** the active timer action remains a real session command and is eligible for both the forward compact slot and overflow/expanded presentation. Layout tests prove it coexists with Car/Headset and skip controls rather than deleting transport actions. - **PROVEN — automated:** post-expiry shake grace defaults to **10 seconds**, supports **Off**, and is bounded to a maximum of 10 seconds. - **PROVEN — automated:** Low / Normal / High sensitivity exist; Normal is the pre-setting **12 m/s² above gravity** threshold, High is easier and Low harder. - **PROVEN — automated:** grace/sensitivity settings persist; the active sensor listener is re-registered when sensitivity changes. - **PROVEN — automated:** sensing exists only while a timer is running or while an unclaimed bounded post-expiry grace is valid. - **PROVEN — automated:** natural expiry can create grace; a valid grace shake resumes through the canonical playback owner and starts the same timer mode again rather than issuing raw Play. - **PROVEN — automated:** a shake at/after the half-open grace deadline does nothing; Grace Off stops sensing immediately at expiry. - **PROVEN — automated:** manual cancel tears the timer/sensing state down. - **PROVEN — automated:** book replacement, service/player replacement, newer Play/Pause/seek/Stop/media-replacement intents and expired claims revoke stale grace authority. - **PROVEN — repository/product decision:** turning shake-to-restart off invalidates grace authority and reconciles the sensor owner immediately; no independent “enabled” sensor lifecycle exists outside `SleepTimerController`. - **PROVEN — automated:** scheduled-timer grace preserves the current schedule contract: a claim cannot commit after its civil occurrence has ended; a valid pre-end shake can restart while a post-end shake cannot. - **PROVEN — automated:** race coverage exists for rapid double shakes, suspended session creation/freshness, stale service generations and automatic-expiry persistence. ### What CI cannot prove There is no trustworthy physical evidence yet for actual Android System UI rendering, real accelerometer thresholds, screen-off behavior or Bluetooth/headset behavior. Green CI is not being treated as a substitute. ### Acceptance APK Forgejo **Build APK run #272** produced: - artifact `bookwave-debug-0.10.6.1-2272` - APK `bookwave-debug-0.10.6.1-2272.apk` - package `org.homebord.bookwave.debug` - exact source `88ae231ddc01897d83e24968bed5443ea861aedd` - signer verified against the configured BookWave keystore - artifact build only; no ceremonial rerun of `verifyDebug`. ### Required physical matrix Use the APK above and record the observed value/state at each step, not only “pass”. 1. Start audiobook playback and start a sleep timer. 2. Inspect **compact** Android system media controls: remaining time must be visibly readable and change. 3. Inspect **expanded** controls: timer action must still be present and actionable. 4. Let the countdown advance/extend it; verify both surfaces follow the playback-owned remaining state. 5. Put the app in background and turn the screen off; re-open controls and verify the same timer state. 6. Let a short timer expire naturally; playback must pause per the ordinary timer contract. 7. With shake enabled, Grace = 10 s, Normal sensitivity: shake **inside** grace → playback resumes and the same timer mode starts again. 8. Repeat and shake **after** grace → nothing happens. 9. Set Grace = **Off**; expire and shake immediately → nothing happens / sensing has ceased. 10. Exercise **Low / Normal / High** with deliberately different movement strength; setting must persist and High should trigger more easily than Normal, Normal more easily than Low. 11. Cancel a timer manually; movement afterwards must not reveal leftover grace/sensing. 12. Change book and, where practical, recreate/tear down playback service while grace could otherwise exist; no stale shake restart may survive. 13. Disable shake-to-restart while a timer is active and during a grace opportunity; motion must stop having effect. 14. Repeat representative timer/expiry behavior through Bluetooth/headset and confirm playback remains sane. 15. When combined with #33, include an automatically scheduled timer and verify its grace cannot revive it after the applicable schedule occurrence has ended. Host/device-dependent criteria above are all **STILL REQUIRES PHYSICAL TEST**. The Android 13+/System UI wording is specifically not accepted until the actual device renders it. This matrix should be run in the same device session as #33 rather than creating a second overnight/screen-off exercise. ## Result **READY FOR PHYSICAL ACCEPTANCE**
Author
Owner

Physical acceptance finding — compact/expanded countdown is not visible

Physical device acceptance has now exercised the previously unproven System UI criterion and it fails.

Observed:

  • an active sleep timer does not show a visible countdown in the expanded media notification;
  • the collapsed/minimized/top System UI media surface also does not show a visible countdown.

This converts the prior “READY FOR PHYSICAL ACCEPTANCE” item into a concrete implementation defect. The timer itself is working; the failure is presentation/projection.

Current-main diagnosis at 134fd99e9cb617d676f279f3a88b969baa9a2cff:

  • PlaybackService does observe the playback-owned SleepTimerState and republishes each timer change;
  • the custom timer action carries the remaining time only as CommandButton.displayName, which System UI is free to render as an icon-only action;
  • SleepTimerMediaMetadata currently appends the countdown only to MediaMetadata.artist;
  • the physical device demonstrates that the relevant compact/expanded System UI presentation is not rendering that artist/byline projection as visible countdown text.

Repair direction:

  • make the countdown a primary metadata field that System UI actually surfaces, with the timer first so narrow/collapsed rendering cannot truncate it away;
  • use a clock-style countdown (12:34, 0:42, 1:05:06) rather than a verbose label;
  • preserve and restore the exact original book title/display-title when the timer stops;
  • retain the existing timer action and all timer behavior unchanged;
  • add deterministic metadata/formatting regression tests, while keeping physical System UI rendering as the final acceptance gate.

Implementation branch: mcp/issue-77-visible-sleep-countdown.

## Physical acceptance finding — compact/expanded countdown is not visible Physical device acceptance has now exercised the previously unproven System UI criterion and it **fails**. Observed: - an active sleep timer does **not** show a visible countdown in the expanded media notification; - the collapsed/minimized/top System UI media surface also does **not** show a visible countdown. This converts the prior “READY FOR PHYSICAL ACCEPTANCE” item into a concrete implementation defect. The timer itself is working; the failure is presentation/projection. Current-main diagnosis at `134fd99e9cb617d676f279f3a88b969baa9a2cff`: - `PlaybackService` does observe the playback-owned `SleepTimerState` and republishes each timer change; - the custom timer action carries the remaining time only as `CommandButton.displayName`, which System UI is free to render as an icon-only action; - `SleepTimerMediaMetadata` currently appends the countdown only to `MediaMetadata.artist`; - the physical device demonstrates that the relevant compact/expanded System UI presentation is not rendering that artist/byline projection as visible countdown text. Repair direction: - make the countdown a primary metadata field that System UI actually surfaces, with the timer first so narrow/collapsed rendering cannot truncate it away; - use a clock-style countdown (`12:34`, `0:42`, `1:05:06`) rather than a verbose label; - preserve and restore the exact original book title/display-title when the timer stops; - retain the existing timer action and all timer behavior unchanged; - add deterministic metadata/formatting regression tests, while keeping physical System UI rendering as the final acceptance gate. Implementation branch: `mcp/issue-77-visible-sleep-countdown`.
Author
Owner

Sleep countdown System UI repair — PR #93 ready for physical acceptance

Repair is implemented on PR #93 at exact HEAD bcf302309d988765dfdfd1a8b6de610159aa6b18.

Behavior

  • while the sleep timer is active, primary media metadata is projected as a compact clock first, e.g. 12:34 · Book title;
  • both title and displayTitle carry the countdown so compact/minimized and expanded Android System UI media surfaces do not depend on a secondary byline or custom-action text;
  • the author/byline remains unchanged;
  • each tick rebuilds from preserved original metadata, so timer prefixes do not compound;
  • timer cancel/expiry restores the exact original title/display-title;
  • timer semantics and the existing sleep action are unchanged.

Automated evidence

Exact HEAD bcf3023:

  • automatic Quick run #314: PASS;
  • manual Standard run #316: PASS;
  • verifyDebug: PASS;
  • unit tests: 2627 / 2627, 0 failed;
  • ktlint: 0 findings;
  • detekt: 0 findings;
  • Android Lint: 0 errors, 0 warnings;
  • Room schemas: current.

Installable physical-test APK

Privileged APK run #318 built the same exact branch HEAD:

  • artifact: bookwave-debug-0.10.6.1-2318;
  • APK: bookwave-debug-0.10.6.1-2318.apk;
  • package: org.homebord.bookwave.debug;
  • source: bcf30230;
  • configured signing identity: 270b96a3214c58c0…;
  • APK signer verification: PASS, exact configured-keystore match.

The PR workflow's ordinary debug signer was deliberately not used for this physical APK, avoiding the prior update-certificate mismatch.

Remaining physical acceptance

Keep #77 open until the APK proves:

  1. active countdown is visible in the compact/minimized/top media surface;
  2. active countdown is visible in the expanded notification;
  3. countdown changes while active;
  4. cancelling/expiry restores the ordinary book title;
  5. APK upgrades the existing BookWave debug install without a signing-certificate error.

PR #93 is mergeable and currently 0 commits behind main.

## Sleep countdown System UI repair — PR #93 ready for physical acceptance Repair is implemented on PR #93 at exact HEAD `bcf302309d988765dfdfd1a8b6de610159aa6b18`. ### Behavior - while the sleep timer is active, primary media metadata is projected as a compact clock first, e.g. `12:34 · Book title`; - both `title` and `displayTitle` carry the countdown so compact/minimized and expanded Android System UI media surfaces do not depend on a secondary byline or custom-action text; - the author/byline remains unchanged; - each tick rebuilds from preserved original metadata, so timer prefixes do not compound; - timer cancel/expiry restores the exact original title/display-title; - timer semantics and the existing sleep action are unchanged. ### Automated evidence Exact HEAD `bcf3023`: - automatic Quick run #314: PASS; - manual Standard run #316: PASS; - `verifyDebug`: PASS; - unit tests: 2627 / 2627, 0 failed; - ktlint: 0 findings; - detekt: 0 findings; - Android Lint: 0 errors, 0 warnings; - Room schemas: current. ### Installable physical-test APK Privileged APK run #318 built the same exact branch HEAD: - artifact: `bookwave-debug-0.10.6.1-2318`; - APK: `bookwave-debug-0.10.6.1-2318.apk`; - package: `org.homebord.bookwave.debug`; - source: `bcf30230`; - configured signing identity: `270b96a3214c58c0…`; - APK signer verification: PASS, exact configured-keystore match. The PR workflow's ordinary debug signer was deliberately not used for this physical APK, avoiding the prior update-certificate mismatch. ### Remaining physical acceptance Keep #77 open until the APK proves: 1. active countdown is visible in the compact/minimized/top media surface; 2. active countdown is visible in the expanded notification; 3. countdown changes while active; 4. cancelling/expiry restores the ordinary book title; 5. APK upgrades the existing BookWave debug install without a signing-certificate error. PR #93 is mergeable and currently 0 commits behind main.
Author
Owner

Physical acceptance follow-up — compact title scrolls on every countdown tick

Physical testing of PR #93's first repair shows that the countdown is now visible, but the compact/minimized System UI presentation is still not readable enough.

Observed:

  • the compact media title contains the countdown plus the book title;
  • because the metadata is refreshed every second, the long primary title restarts/updates its marquee every second;
  • the text therefore keeps moving before it can be read comfortably.

Product direction from physical acceptance:

  • while a sleep timer is active, make the primary media title only the compact countdown (for example 12:34 or 1:05:06);
  • do not append the book title to that primary field while active;
  • preserve the ordinary book metadata internally and restore it exactly on cancel/expiry;
  • keep the author/byline and timer behavior otherwise unchanged.

Repair applied on PR #93. The implementation now publishes only the timer into both title and displayTitle while active, specifically to avoid a long marquee restarting on every one-second update. Physical acceptance remains open until this revised presentation is tested on-device.

## Physical acceptance follow-up — compact title scrolls on every countdown tick Physical testing of PR #93's first repair shows that the countdown is now visible, but the compact/minimized System UI presentation is still not readable enough. Observed: - the compact media title contains the countdown plus the book title; - because the metadata is refreshed every second, the long primary title restarts/updates its marquee every second; - the text therefore keeps moving before it can be read comfortably. Product direction from physical acceptance: - while a sleep timer is active, make the primary media title **only the compact countdown** (for example `12:34` or `1:05:06`); - do not append the book title to that primary field while active; - preserve the ordinary book metadata internally and restore it exactly on cancel/expiry; - keep the author/byline and timer behavior otherwise unchanged. Repair applied on PR #93. The implementation now publishes only the timer into both `title` and `displayTitle` while active, specifically to avoid a long marquee restarting on every one-second update. Physical acceptance remains open until this revised presentation is tested on-device.
Author
Owner

Timer-only compact media title — revised candidate ready for physical test

Physical feedback showed that 12:34 · Book title was technically visible but not readable in compact System UI because the one-second metadata updates kept restarting/updating the long marquee.

PR #93 has been revised accordingly.

Exact candidate HEAD: 5118bfc2683e11f28b2514e7a6f0cd56a6ad0bf1

Behavior now:

  • while the sleep timer is active, both primary title and displayTitle are only the compact countdown (for example 12:34 or 1:05:06);
  • the book title is not appended to the active primary title, so there is no long text to scroll/restart each second;
  • author/byline remains unchanged;
  • cancel/expiry restores the exact original title and display title;
  • timer behavior itself is unchanged.

Verification:

  • Quick run #320: PASS;
  • Standard run #321: PASS on exact HEAD 5118bfc…;
  • stable-signed physical-test APK run #322: PASS.

Physical-test APK:

  • artifact: bookwave-debug-0.10.6.1-2322;
  • APK: bookwave-debug-0.10.6.1-2322.apk;
  • package: org.homebord.bookwave.debug;
  • exact source: 5118bfc2;
  • signer: 270b96a3214c58c0…, verified against the configured BookWave keystore.

Remaining acceptance is on-device readability of the timer-only compact/top surface plus normal restoration when the timer ends.

## Timer-only compact media title — revised candidate ready for physical test Physical feedback showed that `12:34 · Book title` was technically visible but not readable in compact System UI because the one-second metadata updates kept restarting/updating the long marquee. PR #93 has been revised accordingly. Exact candidate HEAD: `5118bfc2683e11f28b2514e7a6f0cd56a6ad0bf1` Behavior now: - while the sleep timer is active, both primary `title` and `displayTitle` are **only the compact countdown** (for example `12:34` or `1:05:06`); - the book title is not appended to the active primary title, so there is no long text to scroll/restart each second; - author/byline remains unchanged; - cancel/expiry restores the exact original title and display title; - timer behavior itself is unchanged. Verification: - Quick run #320: PASS; - Standard run #321: PASS on exact HEAD `5118bfc…`; - stable-signed physical-test APK run #322: PASS. Physical-test APK: - artifact: `bookwave-debug-0.10.6.1-2322`; - APK: `bookwave-debug-0.10.6.1-2322.apk`; - package: `org.homebord.bookwave.debug`; - exact source: `5118bfc2`; - signer: `270b96a3214c58c0…`, verified against the configured BookWave keystore. Remaining acceptance is on-device readability of the timer-only compact/top surface plus normal restoration when the timer ends.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alexander/Audiobookshelf-Manager-Claude#77
No description provided.