Commit Graph
285 Commits
Author SHA1 Message Date
makiolaj cb5cd5123b docs(roadmap): keep the Wear OS note to what holds
Ringing notifications are foreground-service notifications, so making
them non-ongoing wouldn't bridge them; CompanionDeviceManager carries no
data; and watches pair through their makers' apps. Say only what holds
and note that a watch build has no F-Droid channel.

Refs #27
2026-10-22 11:03:44 +02:00
makiolaj 0213af1260 docs(roadmap): correct what a watch gets today
Ring and timer notifications are ongoing, which Wear OS doesn't bridge,
and bridging needs Google's Wear OS app anyway. Quote the privacy policy
exactly, drop the unchecked "only channel" claim, and list bridging the
ring as an option of its own.

Refs #27
2026-10-22 11:01:02 +02:00
makiolaj 95bb2d14ec docs(roadmap): record why a Wear OS companion is blocked on Play Services
A companion needs Google's Wearable Data Layer, which is a proprietary
service the privacy policy and the F-Droid build rule out. The roadmap
entry now records that constraint, what the bridged notifications
already give a watch, and the options if it is picked up.

Refs #27
2026-10-22 10:59:35 +02:00
makiolaj af70ee1b6a fix(screensaver): keep the fading frame when the clock returns to a spot
A spot the clock comes back to, after the time is set back, is now the
newest frame, so the copy fading out is never the one dropped. A
keyboard dock or a connected keyboard no longer recreates the in-app
screen saver either.
2026-10-22 09:15:07 +02:00
makiolaj cba16c940c fix(screensaver): fade only on a move, survive dock and theme changes
The in-app screen saver also handles uiMode, density, font scale and
locale changes in place, so docking it or the dark-theme schedule no
longer recreates it at night brightness. Only a move crossfades; a new
next alarm or a settings change redraws in place, and the outgoing copy
keeps its own minute. The AM/PM split skips quoted pattern text, and
rememberLocalTimeFormatter reads the same currentLocale() as the screen
saver.
2026-10-22 09:04:25 +02:00
makiolaj be2c0ada04 fix(screensaver): match night brightness across hosts, end on leave
The dream now turns its window down to the same near-zero brightness as
the in-app screen saver, not just to the system's dim level, and builds
its ComposeView from the window's context rather than the service's.
The in-app screen saver finishes once it is no longer shown, so waking
the phone shows the lock screen, and rotating it into a stand no longer
recreates it. The outgoing minute of the crossfade is hidden from screen
readers.
2026-10-22 08:51:40 +02:00
makiolaj ba1172b822 fix(alarms): keep a settling card from overshooting past its rest 2026-10-22 08:43:26 +02:00
makiolaj 4765b8e088 fix(screensaver): keep both screen saver activities out of the app's task
The settings screen Android's screen saver list opens gets a task of its
own and stays out of recents, so it never lands in or clears the app's
task, and its bars follow the app's theme. The on-demand screen saver is
noHistory, so leaving it by Home does not bring the app back to it later,
and it only touches the keep-screen-on flag when charging starts or stops.

The next-alarm line uses the same 12/24-hour rule as the big readout,
joined to the day by a translatable string; the minute's crossfade shows
the old minute fading out rather than two copies of the new one.
2026-10-22 08:39:07 +02:00
makiolaj 40c71a49f7 fix(timers): delete on the application scope, and wait for storage in the delete tests
The timer list's delete now outlives a back press the same way the alarm list's does. The instrumented delete and Undo tests wait for the row to change in storage, because that work runs outside Compose's idling.
2026-10-22 08:35:14 +02:00
makiolaj 23f2ee94ea fix(screensaver): start dim, lock on time and keep room to drift
Both hosts start at night-mode brightness and only brighten once the
settings say so, and the screen stays black until the settings and the
appearance are both read, so a dark room is never lit by a loading frame.
The on-demand screen saver lets the phone lock on its usual timeout and
stays up over the lock screen, so a phone left charging is not left
unlocked. The digital readout takes 70% of the shorter side, leaving
room to drift across it.

The next alarm is one localized date-time skeleton instead of a
hand-joined day and time, the date uses floret's localizedDateFormatter,
and the 12/24-hour pattern is shared with rememberLocalTimeFormatter.
2026-10-22 08:29:02 +02:00
makiolaj 3b488ef6fc fix(tiles): follow the quick-timer tile's whole model, and clear stranded timers
WidgetSync now redraws the quick-timer tile on its own model rather than
on the timers alone, so a duration restored from a backup reaches it too
and no writer has to ask for a redraw by hand.

A transient timer the tile created but never got running is deleted on
the next tap instead of sitting idle in the Timers list for good.

The tile model loses its unused action enum: an Active supertype carries
the timer id every reset needs.
2026-10-22 08:26:09 +02:00
makiolaj ddec2d8ed1 fix(alarms): open the ring screen when the editor's Delete is refused
Deleting a ringing alarm from the editor is refused, and a refused tap did nothing visible. It now opens the ring screen, the same way out the list's card offers.
2026-10-22 08:25:12 +02:00
makiolaj 712b606779 fix(alarms): keep the upcoming notice off watches, and check past the grace
The notice is local-only, so its Dismiss is never bridged to a watch where the phone's unlock does not apply. The closing and skip-spending checks land a second past the fire grace, since onFire still accepts a fire at exactly the grace.

Fixes #16
2026-10-22 08:21:33 +02:00
makiolaj 9839520b7b refactor(alarms): one date formatter, and a picker year range sized to its date
The list and editor now format a date through the same helper as the
widget, and the date pickers keep their default years unless a stored
date lies beyond them, instead of always spanning to 9999.
2026-10-22 08:20:19 +02:00
makiolaj beeca29f74 fix(tiles): redraw on clock and zone changes, and tighten the tile surfaces
The tiles' refresh now rides WidgetSync's collectors instead of a second
copy of them, and SystemEventReceiver asks both tiles to redraw on a time
or zone change, where the times they show move without any write.

The quick-timer tile remembers its timer before starting it, so a failed
start can't leave a timer it cannot see, and shows the timer's stored end
rather than one re-derived from two clocks on every read.

The tile preferences screen closes on anything but QS_TILE_PREFERENCES,
runs in its own task, and asks for a redraw after saving a duration. The
tiles and the next-alarm widget share one 12/24-hour time formatter and
the widgets' launch intent.
2026-10-22 08:19:49 +02:00
makiolaj d744fa8d98 fix(screensaver): address review findings
The dream's settings activity is named by class alone, so the gear opens
the installed build rather than always the production package. The
screen saver now formats time with the app's own 12/24-hour rule and the
shared currentLocale(), sizes the numerals with the AM/PM marker counted,
dates a next alarm a week or more away, and gives the analog face the
time as its description. The screen saver header in Settings > Clock
waits for its rows, and BackupSettings.screenSaver is required.
2026-10-22 08:18:35 +02:00
makiolaj 7adda73a79 fix(alarms): keep the editor's Delete off a ringing alarm too
With its confirmation gone, one tap on the editor's Delete would have
silenced a ringing alarm round its dismiss challenge, which the list's
swipe is already kept from doing; the ring screen is the way out. The
list's delete now runs on the application scope like the editor's, a
thrown-away card ignores a new drag, and the timers snackbar clears the
live pill on an empty tab.
2026-10-22 08:15:52 +02:00
makiolaj 5ad9bd02d6 fix(alarms): spend a pending skip only after its fire grace
The upcoming check that spends a skip dismissed in advance now wakes once the skipped occurrence's fire grace is over rather than at the occurrence itself, so it can never get ahead of a fire still in flight for it.

Fixes #16
2026-10-22 08:13:31 +02:00
makiolaj c5de9becdf fix(alarms): spend a date on the ring that used it, and harden date input
A dated one-shot whose time was moved later while it was snoozed rang a
second time that day, because closing the cycle only asked whether the
date was still ahead. It now keeps the alarm on only for a date after the
day that rang, and a one-shot switched off as its cycle closes lets its
date go.

The date pickers accept every year a stored date can have, so a far date
from a backup can no longer crash the editor. The widget formats its date
with the list's own formatter, and a backup's leftover date on the wrong
kind of alarm is ignored instead of rejecting the file.
2026-10-22 08:11:35 +02:00
makiolaj da9854abf8 feat(tiles): Quick Settings tiles for the next alarm and a quick timer
"Next alarm" reads the next-alarm widget's model and shows the weekday
and time of the next alarm, or "No alarms"; a tap opens the Alarms tab,
behind an unlock on a locked device, through the PendingIntent overload
of startActivityAndCollapse on API 34+.

"Quick timer" is the quick-timer widget's twin: at rest it shows its
duration and a tap starts a transient timer through the timer engine;
while that timer is active the tile is on, shows when it ends (or that
it is paused or done), and a tap resets it. It works on a locked device,
as the timer notification does. Its duration is a new backed-up setting,
chosen by long-pressing the tile, with the widget's bounds and picker.

Both are active tiles, redrawn by TileSync when the state they mirror
changes rather than bound on every panel open. No new permission.

Fixes #26
2026-10-22 08:09:14 +02:00
makiolaj fdb725e64c fix(alarms): spend a skip at its occurrence again
Keeping a skip armed through its fire grace let the editor's switch or another dismissal inside those two minutes ring the skipped alarm late, or be absorbed. The resolver goes back to spending the skip at its occurrence and recording it as handled, and the upcoming check wakes at an armed skip's occurrence so the list stops saying "skipping next" on time.

Fixes #16
2026-10-22 08:07:52 +02:00
makiolaj 1e29226364 feat(screensaver): add a screen saver with a dim night mode
A DreamService shows a full-screen clock, the date and the next alarm,
digital or as the world clock's analog face, on black. Night mode dims
every colour towards black and turns the display down; the clock moves
to a new spot each minute so nothing burns in. It wakes only on the
minute and on a time, zone or 12/24-hour change.

The tabs' settings gear becomes an overflow menu with "Screen saver" and
"Settings". An app cannot start the system's dream without a system
permission, so that item opens an activity with the same content, which
keeps the screen on only while charging. Style and night mode live in
Settings > Clock and in the dream's own settings screen, and are carried
in backups; older backups restore the defaults.

Fixes #25
2026-10-22 08:07:44 +02:00
makiolaj 5f3b97b32a fix(alarms): refuse a list delete of a ringing alarm in the engine
The list's delete re-checks for a ring under the engine lock, so a
swipe released as the alarm fires cannot silence it round its dismiss
challenge. An Undo whose snackbar is already up no longer goes stale
on a rotation after a long accessibility timeout, and a deleted card is
thrown clear of the screen edge.
2026-10-22 08:05:25 +02:00
makiolaj 301ce2fec9 fix(alarms): keep a one-shot on when it was given a date mid-snooze
Dismissing a snoozed one-shot switched it off even when the user had
just scheduled it for a later date from the editor, so the date never
rang. Closing a cycle now leaves a one-shot on while its date is still
ahead.
2026-10-22 08:01:36 +02:00
makiolaj a88e696d52 fix(alarms): spend a skip only after its fire grace
The resolver now keeps a skip armed until its occurrence is out of the fire grace too, so a reschedule in those two minutes cannot spend it early and let a fire already in flight ring the dismissed alarm; onFire refuses that fire by the armed watermark. The notifier also cancels notices it posted itself, which the platform may not list as active yet.

Fixes #16
2026-10-22 08:00:38 +02:00
makiolaj 697678b226 fix(alarms): drop an Undo offered while no list could show it
A delete can finish while no list is on screen, such as the app sent
home the instant the editor's Delete was tapped. Its Undo is now
dropped unshown once it is 30 seconds old, instead of surfacing hours
later. Alarms and timers share one UndoSlot for this. A card whose
swipe is re-enabled mid-settle still slides home.
2026-10-22 07:54:43 +02:00
makiolaj 247dbcb751 fix(alarms): name a pause's last day, and switch on an alarm given a date
"Paused, back on" named the day after the pause, which for a weekday
alarm can be a Saturday it never rings on. A pause under way now reads
"Paused through Wed, Oct 28".

Picking a date on a switched-off alarm switches it on, the pause picker
cannot confirm a range that is already over, a spent pause stored with
its ends reversed is cleared too, and the widget formats its date in the
app's own locale.
2026-10-22 07:53:11 +02:00
makiolaj 93f6fdf98d test(prefs): cover the automatic local clock's round trip and restore
Also reuse ZoneOffsetFormat.gmtLabel for the Etc/GMT names rather than
a second formatter, and bring the city-fallback docs up to date.
2026-10-22 07:52:47 +02:00
makiolaj b4af164826 fix(alarms): spend a dismissed skip on time, and ring a re-armed handled alarm
The upcoming check now also wakes once a noticed occurrence's fire grace has run out, so a notice cannot outlive a late fire, and once an armed skip's has, so the list stops saying "skipping next" about an occurrence already gone. onFire is back to checking only the armed skip: the resolver deliberately re-arms a handled occurrence that a clock moved backwards put back in the future, and that one must ring.

Fixes #16
2026-10-22 07:51:57 +02:00
makiolaj b79b38bd2b fix(worldclock): fix Etc/GMT names at the fallback, not per caller
The previous rule named every non-place id by its current offset, which
renamed legacy ids such as Japan, called Etc/UTC "GMT" and made a CET
row's name change at DST. Only the Etc/GMT+-n ids have a misleading
last segment, so ZoneCatalog.cityFallbackFor now flips just those to
their real offset. That also reaches the zone picker's device row,
which takes its name from the same fallback.
2026-10-22 07:44:54 +02:00
makiolaj 62da327771 fix(alarms): bring a card home when its swipe is disabled mid-gesture
A card whose alarm starts ringing during a drag or the throw-away
animation slides back instead of staying displaced, and the delete is
re-checked after the animation, so it cannot land on a ringing alarm.
2026-10-22 07:44:28 +02:00
makiolaj 1dcd743e5b fix(alarms): keep a skip on the next ring after any edit, and say when a pause ends
Moving the time or changing the days left a pending skip pointing at the
old sequence, so the skipped day could ring at its new time. Every editor
change that can move a fire time now re-arms the skip.

A pause under way now reads "Paused, back on Thu, Oct 29" instead of
naming its last day, which read as the day it ends before. Reopening a
begun pause keeps its start, the date pickers take their bounds from the
clock when they open, and the dismiss chooser shows the scheduled date and
pause like the list does.
2026-10-22 07:43:30 +02:00
makiolaj f570bdefb7 fix(alarms): keep the upcoming notice off a locked screen below Android 12
The Dismiss action's unlock requirement is honoured only from Android 12, so on 10 and 11 the notice is now secret on the secure lock screen rather than dismissible by whoever holds the phone.

Fixes #16
2026-10-22 07:41:05 +02:00
makiolaj 40b4c9e2e4 fix(worldclock): name offset-set zones by their real offset everywhere
The Etc/GMT-n naming fix only covered the local row. A home that
follows a device set by UTC offset still put "GMT-9" under a UTC+9
face. The rule now lives in the one place every row and the face take
their city from.
2026-10-22 07:38:49 +02:00
makiolaj 1253c0fc55 fix(alarms): no fire for an occurrence already accounted for
A natural fire whose instant equals the skip or the handled-occurrence watermark is ignored, so a dismissal racing a reschedule cannot ring. Dismissing a repeating alarm persists its resolution before arming the skip, so an unspent old skip cannot absorb it. The deferred notice sync runs even if starting the ring throws, the swipe record is one synchronised read-modify-write, and it stays out of backups.

Fixes #16
2026-10-21 20:26:50 +02:00
makiolaj 471cbdabd8 fix(alarms): re-arm a skip when the pause changes, and clear spent dates in place
A skip armed under one pause kept its watermark when the pause changed,
so removing the pause left the alarm silent until the old pause's end.
The engine now re-arms a pending skip after a pause edit.

Spent dates and pauses are cleared with targeted, conditional updates
instead of a whole-row rewrite. SET_ALARM ignores a date or pause that
has already gone by when looking for an alarm to re-use, the editor
re-reads the clock when a date picker opens, and the next-alarm widget
shows the year for a date in another year.
2026-10-21 20:25:28 +02:00
makiolaj f46b7e1e37 fix(worldclock): keep the local row's day label and legacy city names
The local row prepends "Local time" to the offset and day, so on a
phone a one-line summary cut off the day ("Tomorrow"), the part that
matters most on a long trip. It now wraps to two lines. Only Etc/
offsets and bare abbreviations are named by their offset; a legacy
place id such as US/Pacific keeps its place name. The picker's home
selection now derives from the same settings subscription the tab
uses.
2026-10-21 20:24:24 +02:00
makiolaj af12b7bb34 fix(alarms): keep a ringing card out of the swipe, and Undo off the ViewModel scope
A ringing alarm's card no longer swipes or offers Delete: it leads to
the ring screen, and a swipe must not get round the dismiss challenge.
A drag cancelled before release (a ring screen opening on top) never
deletes. Undo restores on the application scope, since a claimed Undo
has no second chance. Closing a cycle and deleting share one teardown.
2026-10-21 20:22:25 +02:00
makiolaj 1333001aa9 fix(worldclock): name an offset-set local row by its real offset
A device set by UTC offset rather than by city reports an id like
Etc/GMT-9, which is UTC+9; the local row took its last segment as the
city and read "GMT-9". It is now named by its actual offset. LocalClock
takes the already-resolved home zone rather than resolving it a second
time, the tab reads both of its settings from one subscription, and the
local row falls back to the unknown-zone sentence for TalkBack instead
of an empty time.
2026-10-21 20:18:10 +02:00
makiolaj dedcbd5dfd fix(alarms): a consumed skip stays handled, and only a swipe hides a notice
A skip spent on its occurrence now becomes the handled-occurrence watermark, so a second resolution inside the fire grace cannot ring the skipped alarm after all. The upcoming notice records a swipe through its delete intent rather than inferring one, so a reboot or a blocked channel no longer hides it for good; its Dismiss asks for an unlock, and a Dismiss for a switched-off alarm clears its notice.

Fixes #16
2026-10-21 20:18:05 +02:00
makiolaj b1a45db54a feat(alarms): schedule an alarm on a date, pause a repeating one
A one-shot alarm can now ring on a chosen date, and a repeating alarm
can be paused for a range of days. Both are local dates: the date is a
floor and the pause a hole in the occurrence sequence, so DST and zone
changes resolve as for any other alarm. A missed date behaves like a
missed one-shot, and each clears itself once it can no longer change a
candidate. Picking a repeat day clears the date, as in Google Clock;
"skip next" stays the quick version of a pause.

The editor uses the M3 date and date-range pickers, which offer no past
day. The list, the next-alarm widget and the self-check read the
resolver, so they follow. The schema goes to v4 with a migration, and
the backup format to v2, which still imports v1 files. SET_ALARM no
longer re-uses an alarm that carries a date or a pause.

Fixes #21
2026-10-21 20:16:34 +02:00
makiolaj ef26d433e1 fix(alarms): let an unanswered Undo lapse, and make delete and restore atomic
A snackbar the screen leaves unanswered (another tab, Settings, the app
closing) now counts as expired, except across a rotation. Held back, it
could restore a snapshot from hours ago, ring a long-gone timer, or
land on top of a backup restored in the meantime. One shared
UndoSnackbarEffect does this for alarms and timers.

The engines' delete and restore run non-cancellable, so a caller
cancelled half-way cannot leave a restored alarm unscheduled. The
editor writes the label still in flight before it deletes, so Undo
brings back what was typed.

The swipe counts the touch-slop overshoot, keeps a card flung back
towards the start, slides a card home if its row is still there a
second after the delete, and no longer recomposes on every drag frame.
2026-10-21 20:13:09 +02:00
makiolaj 755150881b refactor(worldclock): share the row text between saved and local rows
The local-time row copied the saved row's name, summary and time
layout. Both now draw it through one RowText, so a change to how a
row looks lands on both. The Settings hub's Clock entry also names the
new switch, so it can be found from the list.
2026-10-21 20:11:46 +02:00
makiolaj 5b35ef65d4 fix(alarms): keep the upcoming Dismiss away from the fire
A fire broadcast already in flight when a skip was armed on its occurrence is now ignored, and a Dismiss that lands once the occurrence is due is stale. The notices are synced after the ring starts on the fire path, and a swiped-away notice stays gone across a process restart. A switched-off alarm answers NotFound.

Fixes #16
2026-10-21 20:09:47 +02:00
makiolaj f5388042c6 feat(worldclock): show local time automatically while travelling
Issue #24 asks for Google Clock's "automatic home clock": a temporary
Home row while the device is somewhere the time differs from home. In
Google Clock that works because the hero clock is local time. Clockula
is the other way round: the hero face is home (the stored home zone, or
the device's zone when none is stored), every row is read against home,
and with a stored home the face already shows home time on a trip. A
Home row would only repeat the face; what goes missing while travelling
is the local time.

So the feature is turned round. With a home zone stored and the device's
zone on a different UTC offset right now, the tab shows the device's
zone as a temporary "Local time" row between the face and the saved
cities. It is never stored, sits outside the reorderable column, has no
move or remove actions and does not count towards the 24-city cap. The
comparison is the current UTC offset, as Google's is, so Paris with
home in Berlin shows nothing. The row is hidden when a saved city is
already on the device's offset. It is rebuilt on every tick from the
same device-zone read the face uses, so it appears and disappears
within a tick of a time-zone change while the tab is open.

Home that follows the device can never differ from it. Settings > Clock
gets an "Automatic local clock" switch (on by default) under the home
zone row; while home follows the device the row is dimmed and its hint
says it needs a home time zone. The switch is stored as
automatic_local_clock and included in backups. Files written before this
change restore it as on.

Fixes #24
2026-10-21 20:06:13 +02:00
makiolaj 2feed2ee35 feat(alarms): swipe to delete, with Undo
An alarm card swipes away towards the end edge, or deletes from its
"Delete" accessibility action, and the list's snackbar offers Undo.
The editor's Delete drops its confirmation for the same Undo, routed
through a singleton so the list can answer it after the editor pops.
Timer cards get the same Undo for their corner delete.

AlarmEngine.delete stops a ringing alarm and clears a snoozed one's
notification under the engine lock; restore puts the row back under
its own id with its ring state and reschedules. A ringing alarm comes
back dismissed, never ringing; a finished timer comes back reset.

The swipe is hand-rolled so the end-to-start drag stays with the tab
pager.

Fixes #20
2026-10-21 20:02:00 +02:00
makiolaj e43339c386 feat(alarms): notify before an alarm rings, with Dismiss
Two hours before a natural occurrence (AOSP DeskClock's lead), a silent
"Upcoming alarm" notification offers Dismiss, and the alarm's row shows
the same Dismiss as a chip. Dismissing is dismissUpcoming's own branches:
a repeating alarm skips that occurrence, a one-shot is switched off.

The notices are synced at the end of every reschedule, after the real
registration, and a third AlarmManager slot on its own request code
wakes when the next window opens. The sync is wrapped so a notification
failure can never stop a ring. Dismiss names the occurrence and is
refused once the alarm is ringing or has moved, so it can't get round
the dismiss challenge. No challenge is asked before the ring, as in
Google Clock.

Fixes #16
2026-10-21 20:01:21 +02:00
makiolaj d70d0c78da test(worldclock): make the seconds tests mean what they say
The no-re-emission check now waits for the write to be readable before
asserting, and the seconds switch has its own settings test instead of
riding in the clock-defaults one. WorldClockSource.state takes its
refresh signal without a default, and ARCHITECTURE.md's slice count
and alignedTicks guarantee match the code.
2026-10-21 19:57:19 +02:00
makiolaj 706a384704 fix(alarms): word the alarm-set snackbar once per announcement
Every write re-read the engine and re-worded a standing announcement,
so tapping Mon-Fri while the snackbar showed restarted it on each tap,
as did a label keystroke across a minute. The words now come from the
first read; later writes can only take the snackbar down, when the
alarm stops ringing. The settled announcement still replaces it once.

Deleting no longer retracts by hand: a deleted alarm already reads as
nothing to say.

Refs #19
2026-10-21 19:51:47 +02:00
makiolaj 78da94d775 fix(worldclock): leave a fitting margin and drop the zone-cache reset
The fitted seconds size keeps five percent spare, since hinted glyph
advances do not scale exactly. The receiver no longer resets the
process's default zone: that was speculative, and it changed global
state from a UI flow. The settings state takes the seconds flag without
a default, and a garbled KDoc sentence is fixed.
2026-10-21 19:48:30 +02:00