darken 1dfed1c21c fix(debug): Make the short-recording warning clock-change safe and raise it to 10s ...

The "that recording looks very short" prompt measured duration against the
wall clock, so any adjustment mid-recording decided it: an NTP sync or a
manual clock change moving forward made a three-second recording look like an
hour and skipped the prompt, moving backward trapped a long recording in it
with no way past but "stop anyway".

A live session now measures from a monotonic base taken at the start. Only a
session resumed from the trigger file still uses the persisted wall time -
that file has to survive reboots, which monotonic time does not - and a
negative duration there fails open instead of warning.

The threshold moves from 5s to 10s: a recording stopped that quickly holds
nothing but the recorder starting and stopping, which costs a support
round-trip to re-request. It stays a prompt, not a block, because a crash is
logged and flushed immediately.

2026-08-03 08:30:33 +02:00

..

proguard

refactor: Replace Moshi with kotlinx.serialization

2026-03-09 20:29:19 +00:00

src

fix(debug): Make the short-recording warning clock-change safe and raise it to 10s

2026-08-03 08:30:33 +02:00

.gitignore

Refactoring

2022-09-14 18:00:18 +02:00

build.gradle.kts

refactor(upgrade): Converge GPlay billing on the canonical stack

2026-07-29 14:05:26 +02:00

proguard-rules-debug.pro

Refactoring

2022-09-14 18:00:18 +02:00