ReteClock

Releases

• Sep 25, 2026 0.51.0
  Added: Speech settings, a page of its own on the main menu for everything the clock says aloud — whether a tap says the time, how it reads it, and the voice used for the time and the timer's spoken messages alike. These used to be on General settings, Tapping the clock. Added: your own sentence, a third way for a tap to read the time. Write what should be said with fields in braces — {hour} {min} {sec} {ampm} {year} {month} {date} {day} — in your own language. Numbers are said without leading zeros, month and weekday names in full in the voice's language, and the date in the calendar the clock shows; a line under the field shows what would be said now. Switching back to As written or Numbers only keeps the sentence (issue #62). Added: spoken names for months and weekdays — say any of them your own way, per calendar, apart from the names the clock writes. A switch turns them on and off without losing them. Added: keys of your own for the timer, on Timer settings, Keys. Press any key or button — an e-reader's page buttons, a keyboard key, a headset button, a volume key — to make it start/pause or stop the timer. Off until switched on; then Page Up and Page Down start and pause until you change them. Back is kept for leaving the clock (issue #63). Installs on Android 2.3 and newer. Built for Android 4.4.
• Sep 23, 2026 0.50.0
  Added: a screen orientation setting on General settings — follow the phone (the default, and what the clock always did), follow the sensor, lying down, or standing up. For a screen that cannot be turned, or a device with no rotation sensor at all: a reader or a tablet on a wall. It turns the clock; the settings pages and the screensaver follow the phone as before (issue #61). Added: a choice of how a tap reads the time, on General settings, Tapping the clock. As written — "1:05" — or numbers only — "1 5", with no colon and no leading zero. Some speech engines read a written time character by character, "zero one colon zero five", and two bare numbers are what those read as a time. As written is still the default, and your AM/PM word follows the numbers either way (issue #62). Installs on Android 2.3 and newer. Built for Android 4.4.
• Sep 23, 2026 0.49.0
  Added: OLED care, one switch on General settings that makes the clock as easy on an OLED screen as it can be — black behind everything, the writing in one dim warm colour in the thinnest face the system has, no pictures, the colon blinking and the wander always on, and the writing dimming for a moment around each minute so the wander's step is not seen. Your layout and your settings are untouched: switch it off and your colours, fonts and pictures come back. Added: a choice of voice on General settings, Tapping the clock. One list of every voice installed on the phone — each language on each speech engine — with the one in use marked and "Say the time now" to hear it. On Android 5.0 and newer the list leaves out voices the engine would first have to download or that need the network. The choice is used for the timer's spoken messages too. Changed: a tap now says the time alone — "13:30", or "1:30 PM" — instead of "It's 13:30." A speech engine reads in its own language, and the English words around the time were what a Korean or Persian voice could not read. Fixed: the main menu can be scrolled, so on a small screen or with the phone on its side its lower lines can be reached (issue #59). Fixed: a layout's timer strip drawn along the foot now reaches the bottom of the screen on a phone with gesture navigation, instead of stopping a bar's height short of it (issue #60).

  More…

  Installs on Android 2.3 and newer. Built for Android 4.4.
• Sep 20, 2026 0.48.1
  **A clock nobody had touched said it followed one particular published set.** *Religious settings* decided which set was chosen by looking at the numbers in force, and the app's own defaults — dawn and dusk at 18° — are the numbers the University of Islamic Sciences, Karachi publishes. So a new install showed that set as chosen and wrote Fajr, Asr and Isha beside the app's own names on the sun page. Nobody had chosen it, and this app does not decide a tradition for anybody. The set is now the one that was **pressed**: remembered, and checked against the numbers before it is believed. Until somebody chooses one the page says *Custom*, and no tradition's names are shown. An id stored by 0.46.0 to 0.48.0 was worked out from the numbers rather than chosen, so it is not believed either — choose your set again after updating if you had one. Two smaller things went with it. The line under today's times on *Sunset/sunrise settings* said "18°" whatever set was chosen; it now writes the numbers actually in force — "Dawn at 19.5°, dusk at 17.5°". And a set whose angle is half a degree (19.5° for Egypt, 17.7° for Tehran) left the angle row with nothing lit, as if no angle were set at all; the angle in force now has a chip of its own beside the six quick ones. Nothing else changed: the spoken time of 0.48.0 and everything before it are as they were.
• Sep 20, 2026 0.48.0
  **The clock can say what time it is.** Tap it, and it reads the time aloud — "It's 6:21 AM" — if you have asked it to: *General settings* → *Tapping the clock* → *Say the time when the clock is tapped*. It is off until you turn it on (issue #57). It speaks through the phone's own speech engine, the one the timer's spoken messages use, so a phone with no engine or no voice data for its language says nothing at all. A tap that stopped a ringing bell, an alarm or a timer's cue stays silent: that tap has already done its job, and talking over what it has just silenced is the wrong answer in the dark. What it says is built from the hour and the minute rather than read off the face — the face may be padded to "06", may be hiding its marker for want of room, and may be blinking its colon, none of which a voice can say. It follows this app's own clock, including your 12- or 24-hour setting and any AM/PM words of your own, and on a twelve-hour clock it reads midnight as 12 whatever the face is set to write. **Three more published sets of numbers** on *Religious settings* — Muslims of France (12°/12°), the Spiritual Administration of Muslims of Russia (16°/15°) and the Islamic Religious Council of Singapore (20°/18°) — and every set is now labelled with the name of the body that publishes it. **Nine more cities in Iran** to choose a place by: Karaj, Qom, Ahvaz, Bandar Abbas, Kazerun, Takestan, Yasuj, Aligudarz and Ahar. Both came from pull request #58, sent in by a reader who lives there.
• Sep 19, 2026 0.47.0
  **The published sets of numbers** the sun's day can be read by (issue #56). *Religious settings* now offers them by name — Muslim World League, Islamic Society of North America, Egyptian General Authority of Survey, Umm al-Qura, University of Islamic Sciences (Karachi), Institute of Geophysics (Tehran), Shia Ithna-Ashari — beside Custom. Choosing one fills in its numbers, and the page writes them out: *Dawn 18.5° · dusk 90 min after the evening · afternoon shadow its own height · night ends at sunrise*. Change any of them and the choice becomes Custom. They are carried for convenience, not as a ruling, and the page says to check them once against a timetable you trust. **Three reckonings an angle alone cannot say** came with the sets: dusk as a fixed interval after the evening (Umm al-Qura's 90 minutes), an **evening** event a few degrees below the horizon rather than at sunset (Tehran 4.5°, Shia Ithna-Ashari 4°), and a night that ends at dawn rather than at sunrise, which moves the night's middle. The evening is an event of its own now, and a bell can follow it. **Each set's own names are shown beside the app's** — "Dusk · Isha", "Afternoon shadow · Asr" — on the pages and in the bell editor, with a switch to turn that off. The app's own names still say what each moment is: the app computes the sun, and what a moment is called is the tradition's. Unchanged: the shadow multiple and the far-north rule are separate choices of your own, carried across a change of set; where the sun never reaches the angle the default is still *No time that day*. **Checked on an emulator** (Android 4.4, this APK): a bell following the evening rang on the minute the evening fell, while 0.46.0 — which has no evening event — stayed silent then. The sets themselves are covered by unit tests: each is found again from its numbers, the interval dusk lands where it should, and every set orders the day the way the sun does.

  More…

  SHA-256 of `reteclock-0.47.0.apk`: `f8c448e80da3586ed2042ffdc1dfc92daef2cee4917e8ebb9227349a81eec54e`
• Sep 19, 2026 0.46.0
  **The rest of the sun's day** (issue #56). Besides sunrise and sunset, a bell can now follow **dawn**, **solar noon**, the **afternoon shadow**, **dusk**, or the **night's middle** — halfway from sunset to the next sunrise — each still movable by up to three hours either way and worked out again every day for the place you set. *Sunset/sunrise settings* lists all seven for today, above the week's sunrise and sunset. **Religious settings**, a new page in the main menu, holds the conventions those times are read by, because they are not the app's to choose: how far below the horizon dawn and dusk are taken to be (6, 12, 15, 17, 18 or 19 degrees), whether the afternoon shadow has grown by once or twice a thing's own height, and what to do where the sun never sinks that far. It is not one faith's page — the same decisions shape Jewish zmanim, the canonical hours and Ethiopia's sunrise-counted clock — and every time keeps its astronomical name throughout the app. No timetable of any faith is published here. **In the far north**, dawn and dusk may not happen at all. The default is *No time that day*: the page shows a dash and a bell following it stays silent. The conventions used there are offered instead — the middle of the night, a seventh of it, the angle as a share of it, or the time it had on the nearest earlier day it happened. Where the sun does not rise or set either, there is no night to divide and only the nearest-day rule can answer. **Accuracy.** Solar noon and the twilight angles were checked against a separate calculator (api.sunrise-sunset.org) for Seoul, London, Sydney and the equator; the afternoon event was checked by reading the sun's altitude back and recomputing the shadow. Away from the poles the sun itself is right to a minute or two; the convention is where any difference will come from, and that one is yours. **Checked on an emulator** (Android 4.4, this APK): a bell following dusk at a place whose dusk was four minutes away rang on that minute, while 0.45.1 — which knows sunrise and sunset and nothing else — stayed silent then.

  More…

  SHA-256 of `reteclock-0.46.0.apk`: `50c66a772a1f553f2a182dbc1640894ef23608e94548e25191141749955b531a`
• Sep 15, 2026 0.45.0
  **A tap on the clock now only stops what is ringing** — a bell, an alarm rung on the clock's screen, or a timer's sound — and otherwise does nothing. It no longer dims the screen and no longer wakes sleep mode: press the **moon** to fall asleep or wake. A remote's dim and brighten keys work as before, and brighten also wakes the clock. **Sleep mode's brightness can be typed** as any whole per cent from 1 to 100 (*General settings* → *Sleep mode* → *Brightness while asleep*, then **Set**), besides the quick choices. **"Show a saying along the bottom" moved to the Layout page**, with the automatic layout's other settings, where its sources are cited too. It only ever affected the automatic layout; a layout you draw shows a saying wherever it has a saying box. Everything else in General settings' Clock card stays, because it applies to every layout. **Checked on an emulator** (Android 4.4, this APK): inside a sleep window with 37 % typed, 0.44.0 used 1 % and woke on a tap; 0.45.0 slept at 37 %, stayed asleep after a tap, and the moon woke it and put it back to sleep. SHA-256 of `reteclock-0.45.0.apk`: `f5956faa86cf754a419d894569efa8534f47ad4187ac1a3173792f616debb5e1`
• Sep 14, 2026 0.44.0
  **Bells at sunrise and sunset** (issue #55) — main menu → *Sunset/sunrise settings*. **Set the place once**: *Choose a city…* (region, then country, then city; 204 capitals and large cities), or *Enter latitude and longitude…* for anywhere else. The page shows the next seven days' sunrise and sunset in the clock's own time. **No network and no location permission** are used: the times are worked out on the phone. Choosing a city does not change the clock's time zone. **Any bell can follow the sun.** In the bell editor on *Sounds and bells*, a bell is *At a time*, *Sunrise* or *Sunset*, up to 180 minutes before or after. The time is worked out again every day, so the bell follows the seasons by itself — for bells rung on screen and for bells ticked on *Alarms (experimental)* alike. The page also has buttons to add a bell at sunrise or at sunset. Without a place set, or on a day the sun does not rise or set at that place (far north or south), such a bell does not ring. The place travels in *Import / Export*. **Accuracy**: checked against a separate calculator (api.sunrise-sunset.org) for Seoul, London, New York and Sydney in June and December and the equator at the equinox — all within three minutes.

  More…

  **Checked on an emulator** (Android 4.4, this APK): a place was set whose sunrise was four minutes away, with the bell's old set time hours away. 0.43.0 did not ring at sunrise; 0.44.0 raised its card on the sunrise minute. Not included: sunrise and sunset on the clock face, GPS. SHA-256 of `reteclock-0.44.0.apk`: `9b5c686e6cf13e1bdf5b4f1eda4e4ae346d44ab881d669fea3af2bb4ca475f61`
• Sep 12, 2026 0.40.1
  **Switching the timer on no longer moves a layout you drew** (issue #52). The clock used to shrink the whole arrangement by the width of the timer's strip while the background stayed where it was, so on a layout carrying its own pictures the digits slid off the panels drawn for them. A hidden timer did it too. The editor never showed any of this, because the editor lays a layout out against the whole screen; now the clock does the same, and the two agree. The app's own arrangement still moves over to make room, which is right: the app placed those digits and can place them elsewhere. Only a layout you drew is left alone.

  More…

  **If the strip now covers something** at the edge it sits on, give that layout a **timer** field in the fields list and put it on the edge you want: the layout then keeps that room clear, in the editor and on the clock alike. Checked on Android 4.4 (API 19): the released 0.40.0 was run first and had to fail — the screen below the strip moved; this build did not move it, while the strip still appeared. SHA-256 of `reteclock-0.40.1.apk`: `611f844782c99165f0326d8e4061880c9dbb278999f9f1de78aa6f9b8398ee57`
• Sep 10, 2026 0.40.0
  **The top step for animated backgrounds works, and is offered again.** *Pictures → How good animations may look* has its third step back: **As it came — the file itself**, on Android 9 and up. Nothing is prepared at this step — the picture is handed to Android, which plays it with the frame timing its own decoder intends. The step was in 0.38's settings and was taken out of 0.39 because the code behind its label had not been written. This is that code. **An animated WebP moves.** It could not before: the animation used below this step has been in Android since the first release, and it only ever knew GIF. **Changed:** testing a step that prepares nothing now times Android opening the file rather than a preparation, and reports nothing on disc — because there is nothing on disc. And a step refused because a run stopped answering no longer says the *test* refused it; there are two ways for a step to be refused and only one of them is a test. Nothing changes for a phone that never opens that screen. The default is still *Kind to the phone*, which is exactly what the app has always done, and an older Android is not offered a step it cannot perform.

  More…

  --- Installs on Android 2.3 and newer; API 19 and up is where it is tested. About 500 KB, single-dex, no network, no account, two install-time permissions.
• Sep 9, 2026 0.39.0
  Three things that were finished and waiting, put out together. **A bell can be put off** (issue #27). Give a bell a number of minutes in *Sounds and bells*, and when it rings while the clock is on screen a card comes up with it: **Ring again in 10 min**, or **Stop**. Back is stop, and a card nobody answers closes itself after a minute. Bells you already set are untouched — they carry no number until you give them one. A bell rings while the clock or the screensaver is showing and not otherwise, so a bell put off is forgotten if you leave the clock. That is the honest scope of a clock that is not an alarm, and the rest of the issue stays open. **How good animations may look is now a setting** (RFC-0011). *Kind to the phone* is the default and exactly what the app always did; *Better* makes frames the size of the screen and stores them as WebP instead of raw pixels — a tenth to a thirtieth of the size, paid for with a decode when the frame changes. A step is not saved when it is chosen: the phone bakes the hardest picture you use, plays it timing every frame, and the setting is written only if that survives. An app killed in the middle leaves the step off and the reason recorded. **A field can be taken off in the layout editor** (issue #50). Tap it on the layout, then **Remove**; **Undo** is beside it. **Fixed** (issue #51): the editor drew the shared pool's background while the clock drew the picture the layout itself carries, so a layout with its own pictures was arranged against one background and shown against another.

  More…

  --- Installs on Android 2.3 and newer; API 19 and up is where it is tested. About 500 KB, single-dex, no network, no account, two install-time permissions.
• Aug 29, 2026 0.38.0
  ### Added - **A layout can carry its own pictures** (issue #48, RFC-0010) — a background, and one to fill the writing with. *Layout → Pictures…* ticks them from the shared pool; they are copied into a folder belonging to that layout, and while it is chosen they are what the clock draws. A layout is a simple skin now: arrangement and pictures as one set. - **Import and Export carry them**, as an ordinary folder per layout — `layouts/<layout>/preset.txt` beside its pictures — so a package can be opened, rearranged by hand and put back. - **New layout…** and **Put the starter layouts back**, on each list (issue #49). A layout could only be made by copying one before, so deleting them all left no way back. Putting the starters

  More…

  back only adds: one whose name is already there is refused rather than written over. ### Changed - **A layout is named like a variable in C** — a letter, then letters, digits and underscores. The name is a folder on the phone and an entry in an exported zip, and names that differ only by a space or a bracket collide there. Names beginning with `_` belong to the app: the layouts it ships with are now `_clock` and `_clock_with_month`. Layouts you already have are renamed to fit when they are next read — `The clock` becomes `The_clock` — and their pictures move with them. ### Fixed - **Every sideways layout was exported under the same name.** A package entry may not hold brackets, and the exporter's "(sideways)" was quietly replaced by a fallback — so two layouts wanted one file, and the search for a free name never ended: the app stopped answering in the middle of writing the package. The folder is `<layout> - sideways` now, and the search always ends. - **A package holding layouts and no settings could not be brought in**: the one box that would have ticked them counted only settings, so it was greyed out. It counts layouts too.
• Aug 28, 2026 0.37.0
  ### Added - **The clock can be driven with a remote or a keyboard** (issue #45, RFC-0009). The centre key starts the timer and stops it again — what the reporter asked for — and held down it opens the menu, as a long press on the face does. Up and down dim the screen and hand it back; the media transport keys drive the timer by their labels. Back is still the platform's. - **Every button can be reached with a remote, a keyboard or a D-pad**, and shows a ring when it is the one being pointed at. The app draws most of its own buttons, and a drawn button that answers a tap did not exist to anything but a finger — so a settings screen was a dead end two steps in. - **The app appears on a television's home screen**, with a banner of its own, and no longer says it

  More…

  needs a touchscreen. The same APK is still the phone app. - **A margin for a television that cuts off the edges of the picture** — in the general settings, off unless asked for. It moves the clock, the date line, the saying and the timer's bar in by a twentieth on every side. Modern sets do not overscan; old ones do, and only the person looking at the screen can tell which is which. ### Changed - On a television the timer no longer offers **Vibrate**: there is nothing there to buzz with. The stored answer is untouched, so the same settings carried back to a phone still vibrate. ### Fixed - `SettingsActivity` was declared twice in the manifest.
• Aug 23, 2026 0.33.2
  **"Show AM / PM" now hides the marker everywhere** (#44), not only on the screen that shows the time and nothing else. The switch was written for that screen and answered only there: three of the layouts asked "is this a twelve-hour clock" directly instead of asking the switch, so with the date or a calendar on screen the marker stayed however it was set. Wherever it is off now, nothing is drawn and no room is kept — the time takes the space back. Your existing answer is carried over. The switch has also moved to where it belongs: inside the twelve-hour clock's own box in the general settings, above the choices about what the marker should say. SHA-256 of `reteclock-0.33.2.apk`: 2006bfbb26f4abc500480f7e772ee59f37ce698af959b00bff7985b44eeb3ffc
• Aug 23, 2026 0.33.1
  **Fixes the crash when reordering the date line** (#43), reported against 0.33.0. The rows were dragged, and a dragged row rearranged the list from inside the touch it was still handling — which takes the view out from under the gesture being delivered to it. The four items are moved with an **up and a down arrow** now: no gesture to learn, a target a shaking hand can hit, something a screen reader can announce, and the same behaviour on every Android this app runs on. An order you have already set is kept. SHA-256 of `reteclock-0.33.1.apk`: e8b201d98528399381c1d92066796b76b390bcd0cb53c993e212b4f08f24ccca
• Aug 23, 2026 0.33.0
  Three requests from the same reporter, released together. **A tap dims the screen; the next tap gives it back** (#41) — for the clock left running beside the bed. Only the clock's own window is dimmed: the phone's brightness setting is not touched, no permission is asked for, and giving it back hands the screen to whatever the phone itself is set to, including automatic brightness following the room. **The menu is behind a long press**, and it carries **Close the clock** (#41) — on a phone driven by gestures there may be no Back button and no navigation bar to leave a full-screen clock with. **The physical Menu key opens the settings** (#40), where the phone still has one. It is the only key the clock takes; Back, Home and the volume rocker reach the system untouched. **Landscape: the date is a line under the clock, not a column beside it** (#42), so the time has the whole width. The order of that line — weekday, month and day, year, seconds — is set by dragging, in the general settings under the two "Room for the time" proportions.

  More…

  SHA-256 of `reteclock-0.33.0.apk`: aee1baed604718ef148c290c735bd264db6b22f956aaf9b689055ca7674d0149
• Aug 22, 2026 0.32.0
  ### Changed - **Tapping the app icon opens the clock again** (#39). It opened the settings, with the clock one press away, because a badly chosen picture could make the full-screen clock stop answering and the settings were the only way back to undo it. The app now notices that case instead of guarding against it — a run leaves a mark and clears it once it has been drawing happily, and a start that still finds the mark opens the settings by itself and loads no pictures or imported fonts. So the door no longer stands in the way of every ordinary launch. - **Long-pressing the app icon offers "Settings"** on Android 7.1 and newer, which goes straight there without starting the clock. Older versions reach the settings from the clock, as before.

  More…

  - The switch for the old order is still in the general settings; it is on by default now instead of off, and an answer you have already given is kept. - **"Show a calendar on the clock" is the first thing on the time-and-date screen.** ### Note for anyone building from source The resources are now linked against `platforms;android-34` (the launcher-shortcut attributes do not exist in android-19). The Java is still compiled against android-19, which is what keeps a call to a newer API out. Both platforms are needed; the F-Droid recipe installs both.
• Aug 22, 2026 0.31.2
  ### Fixed - **The hour was drawn too large and cut off when it carried a leading zero** (#38). Text sizes are worked out from the widest string a field can ever show, and the twelve-hour hour was still listed as `1`..`12` after the leading zero arrived — so it was measured against `12` and drawn as `08`. In a font whose digits have their own widths that is a third wider than the cell it was given. Every field is now measured as what it will really write, whichever way the numbers are set. - **The day-first date was measured against month names.** `12/07` fell through to the sample list for `Jul 12`, which is wider, so it was drawn smaller than it needed to be.
• Aug 21, 2026 0.30.1
  ### Fixed - **A sound previewed on the sounds page went on offering *Stop*** long after it had finished — the second half of #29. The screen only redrew when something was pressed, so a sound that ended by itself left the button lying. The player now says when it has fallen quiet and the row follows it, however the sound ended: its own end, a fade, a file the phone could not decode, or the screen being left. - **"What the marker says" showed words the clock does not write.** The four marker buttons read a fixed `AM PM NN MN` regardless of the noon and midnight conventions chosen above them. Each button now says which marker it is and what it will actually read — `At noon · PM` — worked out by the

  More…

  same table the clock itself writes the time with.
• Aug 21, 2026 0.30.0
  A small one, all of it about the twelve-hour clock and the date. **A third date format: `12/07`**, beside `Jul 12` and `07-12` — the way most of the world writes a date. The two numeric forms are told apart by their separator as well as by their order. **The AM/PM marker can be left out while only the time is shown.** A twelve-hour clock without one says nothing about which half of the day it is, so it stays on unless you say otherwise; switched off, the hour and the minute take the room it was keeping. ### Fixed * **The AM/PM marker was cut off and sat lopsided while only the time was shown** (issue #35, thanks @DreamsCaffeines). The line was centred on the screen and the room kept for the marker beside it then hung over the edge, so it was squeezed against it. The room is now measured from the marker's own size rather than as a share of the width, and the time and its marker are placed and centred together. On a tall screen the marker sits close under the minute — it belongs to the time rather than sitting beneath it as a caption. * **The marker buttons did not follow the convention you picked.** Choosing a country's way of writing AM and PM — or changing how noon or midnight is written — left the four buttons above still showing the old words until the settings were left and opened again. Everything in that box describes the rest of it, so all of it now redraws together.

  More…

  Built with JDK 21 and reproducible. SHA-256 `9a7b0eea919c5e77a27ccd5e1842b52b7943184999e6161bcd3e93df7a17f039`
• Aug 20, 2026 0.29.0
  The plainest release in a while, and the busiest. **The app is called ReteClock**, wherever a person reads it — the launcher, the settings, the about line, the store listing. Nothing a machine reads changed: the package id is still `com.reteclock`, so this updates in place, and the APK is still published under the old file name. **Show only the time** (issue #31). The hour and the minute fill the screen — larger than they have ever been, with nothing beside them — plus the AM/PM marker on a twelve-hour clock, and nothing else at all: no seconds, no date, no month grid, no saying. It is what the app looked like on its first day. It hides rather than unsets: everything comes back the moment you switch it off. **A blinking colon** (issue #32). Lit for half a second, dark for the other half, exactly on the second, the way a table clock does it. It applies where the time is written on one line and so has a colon; where the hour and the minute are stacked there is nothing to blink. The digits never move. **The system's colours** (issue #33). White on black in the phone's dark theme, dark on white in its light one, following a change without a restart. It sits beside the two colour pickers, and your own pair is kept for when you switch it off.

  More…

  **Bells can ring several times over.** A two-second chime is easy to miss once and hard to miss three times; a touch on the screen fades it out and cancels the repeats that are left. And a timer that is counting now has the right of way: a bell falling then is passed over rather than queued. ### Fixed * **The themed icon was inverted** on Android 13 and later (issue #28) — a dark plate with bright lettering where every other icon was the other way round. The monochrome layer is now the lettering alone, which is what a themed home screen actually asks for. * **A finished timer looked busy** (issue #29). Play stayed dim and stop stayed lit after the last cue, because a finished run was still being counted as a running one. A control is now lit exactly when it does something. Thanks to `@xmha97` and `@DreamsCaffeines`, whose reports — with screenshots, recordings and a reference clock — are most of this release. Built with JDK 21 and reproducible. SHA-256 `742e5f95dc4db4b06aeabf4e7f14ed3fc82e7cc456d6795743412d9c5038ff97`
• Aug 17, 2026 0.28.0
  **Fixed: an outline nobody asked for, and a picture that would not fill the writing.** On a phone with Android's *high contrast text* switched on (Settings → Accessibility), the platform draws its own heavy outline around every string and throws away the picture a paint carries — so the clock looked outlined whether the outline was on or off, and the picture inside the digits never appeared. The clock now draws its own writing as shapes while that setting is on, which keeps the picture and loses the outline. The Fonts and Pictures pages say the setting is on and what it does in every other app. **A phone on silent stays silent.** The app's sounds went out on the music stream, which Android does not quiet for an app. Now: on vibrate nothing sounds; on silent nothing sounds and nothing buzzes either — bells included. **A timer set to vibrate or to silent says nothing and plays nothing** — no beep, no sound of your own, no spoken message. **Pictures, a folder at a time.** Bring in several at once from the picker, and the Pictures page points at the zip that carries a whole folder — the same one the fonts and the sounds travel in. Built with JDK 21 and reproducible.

  More…

  SHA-256 `de10fa50894a8390840c9d739289555482162eabd1b033fbbd40849a70738182`
• Aug 17, 2026 0.26.0
  A new icon, and the themed icon Android 13 asks for. * The launcher icon is redrawn: **RETE** across the top and **13:24** below it in seven-segment digits, on a white rounded plate. Two tones and nothing else. * On **Android 13 and later the icon follows the home screen's theme** ([#28](https://github.com/rubidus-api/reteclock_apk/issues/28)). The app now ships an adaptive icon whose monochrome layer the system tints: the plate takes the theme's colour and the lettering is a hole through it. * **Nothing changes below Android 8.0.** The adaptive icon sits behind a `-v26` qualifier, so older phones keep the plain icon they had, and the app still installs on Android 2.3. SHA-256 of `reteclock-0.26.0.apk`: ``` e99ed76ae2efaa25a6564c8bfba6d6718a7ce5caf4ce151f9795cce20e67accb

  More…

  ```
• Aug 16, 2026 0.25.2
  **Fixed** - **The picture inside the digits could disappear after an import.** A picture whose name is already taken by different content lands under a free name — `wall-00-2.png` — and the settings arriving in the same package still said `wall-00.png`, so the role was dropped and the digits went plain. The renames are now collected as the files are installed and the names in the settings follow them: picture roles, the slideshow order, and the per-field font choices. - **A new field no longer changes how an existing clock looks.** AM/PM used to be drawn with the hour's paint and the calendar's three parts with the date's; when they became fields of their own they fell back to the app's old single outline flag, which switches an outline on where there was none — or loses one that was there. A field split out of another now inherits that one's bold, italic, underline and outline.
• Aug 16, 2026 0.24.0
  A tidying release: the same settings, arranged to be read. - **The menu a tap on the clock opens is called the Main menu**, and it is the only list of where things are — the general settings no longer link to Fonts, Pictures or Import / Export, which are categories on that menu. - **The four AM/PM markers are one row of short buttons** showing what each marker actually says, with a list of the conventions countries use beside them: the Philippines, Japan, Korea, China, written English, midnight as `00:00`. The first entry is the default this app ships with, so the list is also the way back to it. - **The noon, midnight and date-format options read side by side**, wrapping to the next line, instead of spending a line each. - **The screensaver row joins the other two ways the clock starts**, at the top of the settings.
• Aug 15, 2026 0.22.0
  **Added** - **Restore the starter presets.** A button at the foot of the timer's preset list puts Pomodoro, Tabata, Tea, Ramen and Pasta back, behind a question — it cannot tell an evening's tuning from a preset nobody touched. - **My own dates can state its dates.** The custom summer-time rule was stored, read and obeyed, and never shown: choosing it quietly meant Europe's dates. Each end now has a month, an occurrence, a weekday and a time, with the shift beside them, and a note that both times are standard time. **Changed** - Both READMEs say why prayer times and the direction of Mecca are not in the app, and are not planned: they depend on the exact place, the day's sun and a calculation convention that differs between authorities and schools, and this clock asks for no location, reads no sensors and reaches no network.
• Aug 13, 2026 0.20.0
  * Outline, next to bold, italic and underline, chosen line by line. It is drawn in the opposite of your text colour, so writing keeps its edges over a picture whatever colour that picture happens to be.
• Aug 12, 2026 0.15.0
  * Hiding the timer now empties the strip instead of removing it, so the clock keeps the shape and size it had and the hourglass stays exactly where it was. Switching the timer off entirely still gives the space back. * While hidden, the first item of the hourglass menu offers to show the timer again - and doing so does not disturb a run in progress.
• Aug 12, 2026 0.11.0
  * A stopped timer stayed silent but went on sounding: turning the screen built a new timer strip, and the one it replaced kept ticking in the background. It now stops at once, and a saved run is only taken up by the preset it belongs to. * The three times are written inside the timer bar now — whole length, elapsed, remaining — outlined so they read over the fill, and each written only to the units it needs, so a half hour reads 30:00. * Portrait and landscape read the same way: the bar, then play, pause, stop and the hourglass. * A preset can be set to repeat forever, and interval lengths are entered as

  More…

  hours, minutes, seconds and milliseconds. * The timer settings say so when the phone has no speech engine, instead of falling silent without explanation.
• Aug 11, 2026 0.9.1
  **In landscape, the four lines beside the time are now all the same size.** The seconds, the weekday, the date and the year used to be four different sizes in a fixed hierarchy. They are one size now — and they stay level even when one of them has to shrink to fit the column, which is what would otherwise happen the first time a wide font went on the date. Installs on Android 2.3 and newer; upgrades over any earlier release without uninstalling.
• Aug 9, 2026 0.8.1
  **The image list now shows what each prepared picture costs.** Under each image's name: `ready 1.2 MB` when it has a prepared file, or `played live` when it is in use without one — which is what a picture with transparency, and one imported a moment ago, both look like. Under the list, the total for all of them. The prepared files hold frames ready to draw, which is why the clock never decodes a picture while it runs; they are raw, so the disk they take is worth seeing rather than discovering. Installs on Android 2.3 and newer; upgrades over any earlier release without uninstalling.
• Aug 9, 2026 0.8.0
  **Animated backgrounds now play on old phones.** On a Galaxy Note 2 a GIF background would show but never move; 0.7.0 had stopped it freezing, at the cost of the animation. The expensive part was never the decoding — it was that every frame was scaled onto the screen in software, under a full-screen software layer. - **Pictures are prepared once, in the settings screen**, into frames the size your screen can show and in the format it wants. The clock then decodes nothing at all while it is drawing: playing a picture is a read and a blit. - **A GIF too large to play is made smaller and played**, instead of being shown as a single frame. - **Each frame is drawn into a small buffer and put on screen by the graphics hardware**, so the clock keeps its fast drawing path. - **Setting reteclock as your screensaver is now one button**, under Dock: it says whether it already is, and opens Android's own screensaver screen — which hides somewhere different on every version. Pictures with transparency keep the old path, so the colour behind their holes is still the background colour you chose. Installs on Android 2.3 and newer; upgrades over any earlier release without uninstalling.
• Aug 9, 2026 0.7.0
  **Fixed: an animated GIF as a background could freeze the clock the moment it started**, with no way back into the settings. A show of one image no longer re-reads and re-decodes the file every time it loops — that decode ran on the drawing thread — and a GIF too large to play is shown as its first frame instead. Alongside the fix, three ways back in: - **The home-screen button now opens the settings**, with a button there to start the clock. A full-screen clock has no controls on its face, so this is the one door nothing you import can shut. A switch gives the direct start back if you prefer it; a run that stopped answering opens the settings either way. - **If the clock ever stops answering, the next start leaves your images and imported fonts out** and tells you why, so you can undo whatever caused it. - **Every start shows the bare clock for a few seconds before any image**, so a long press always gets through. And a moving picture that costs more than the phone can afford freezes where it is while the clock keeps ticking. Installs on Android 2.3 and newer; upgrades over any earlier release without uninstalling.
• Aug 4, 2026 0.6.0
  Your colours — but never the same one twice. * **The text colour and the background colour are yours**, each picked from a palette of twenty swatches. * **They can never be the same.** The settings screen refuses the pick — a clock drawn in its own background colour is no clock at all — and even a stored equal pair still draws visibly: the text flips to black or white by the background's perceived brightness. * **The background colour shows wherever no image does**: the imageless clock, the letterbox bars of the show-it-all fit, and the floor a cross-fade lands on. Installs on Android 2.3 and newer; built for Android 4.4 first. The F-Droid build is reproducible: `verify_apks` matches this APK against an unsigned rebuild.
• Aug 3, 2026 0.3.5
  Font collections (`.ttc`) are now named on the settings screen as a kind of font file that works, alongside TrueType and OpenType. They always loaded — there is no extension filter and `Typeface.createFromFile` takes a collection — but the settings screen only offered `.ttf` and `.otf`, so nobody would have tried one. Checked on Android 4.4 before the text was changed. Nothing else in the app changed. The store listing gained five new screenshots and a feature graphic, which do not need a release to reach F-Droid. This APK is byte-identical to what F-Droid builds from source; the two can be installed over each other.
• Jul 31, 2026 0.2.4