4 Commits

Include renames

Author	SHA1	Message	Date
FreeTLab	9c7cf4e261	fix(alarm): anchor snooze to the ringing occurrence, never a future one ... posponerAlarma anchored the snooze to snoozeOrigen ?? proximaEjecucion, but once the native fire path works, the fire-time sync records the handled occurrence and recalculation advances proximaEjecucion to the NEXT day before the user can even tap snooze on the still-ringing screen. "Posponer 3" therefore armed the snooze a full day out (captured on-device: snoozeCountdown remaining=1443 minutes). The bug was invisible before because the broken delivery path never advanced proximaEjecucion while ringing — each fix unmasked the next. The anchor is now the newest occurrence that is not meaningfully in the future (shared 90s imminence window): snoozeOrigen for re-snoozes, proximaEjecucion on the watchdog path where it is still today's just-due occurrence, ultimaEjecucionGestionada on the native-fire path where the sync recorded the ringing occurrence, then now. ServicioAlarmas exposes ahora() so the anchor uses the same injectable clock as the rest of the scheduling math. Test fixtures that snoozed half an hour before the ring — a state the ringing screen can never be in, since it is posponerAlarma's only production caller — now move the clock to ring time, preserving their original expectations.	2026-07-12 23:17:26 +02:00
FreeTLab	6acbd7ca93	fix(alarm): handle snooze reschedule failures instead of silently dropping them ... posponerAlarma() and posponerProximaDesdePreaviso() called the native scheduler with no error handling, unlike guardarAlarma(). When the native call failed (e.g. revoked exact-alarm permission), the exception escaped before notifyListeners() ran, leaving the alarm list stuck on stale data with no real alarm scheduled and no snooze countdown notification. Both methods now mirror guardarAlarma()'s pattern: permission pre-check, try/catch into _error, and an unconditional notifyListeners() so the UI always reflects the outcome. Failures surface via SnackBar in the ringing screen and in app.dart's postpone-next handler.	2026-07-01 00:22:58 +02:00
Javier Bautista Fernández	481944815f	fix(alarm): unfreeze snooze modal and add per-minute snooze countdown ... The snooze button was fire-and-forget without error handling: if posponerAlarma threw (e.g. native scheduleAlarm returns false on a device without exact-alarm permission), _dismissScreen never ran. The stuck modal also kept _alarmaSonandoActiva true, which made the next ring get ignored. _posponer/_detener now dismiss in a finally and stop audio defensively. Add a native, AlarmManager-driven snooze countdown notification that re-posts every minute ("Rings in N min", 3->2->1) while the engine is dead. scheduleSpec drives scheduleSnoozeCountdown for snoozes (instead of the 30-min pre-notice). Localized text and button labels travel Dart->Kotlin as {minutes} templates, same pattern as preNoticeTemplate. Notification actions: "snooze again" (snoozeAgain, anchored to now) reports back via the existing snoozed event; "stop" (cancelSnooze) records a handled occurrence for cold-start reconciliation and emits a new snoozeCancelled event handled in EstadoAlarmas. Adds snoozeCountdown/snoozeAgainAction keys across all 13 locales and a test for the snoozeCancelled event. Kotlin changes are static-reviewed only; no Android build environment available here.	2026-06-30 15:27:05 +02:00
FreeTLab	f3e9487215	feat(alarms): native reliability fixes and end-to-end snooze ... - Use mediaPlayback|systemExempted FGS type with FOREGROUND_SERVICE_SYSTEM_EXEMPTED so alarms fire on Android 14+ (FOREGROUND_SERVICE_ALARM does not exist in the SDK) - Deduplicate fire notifications: the foreground service FSI notification is the single owner; receiver path removed - Notification channel v2 with alarm sound URI and USAGE_ALARM attributes, one-time guarded migration from legacy channels - Pass fallback station through the MethodChannel (NativeAlarmSpec schemaVersion 3) with a three-stage audio chain: primary -> fallback station -> bundled WAV - Native fade-in volume ramp honoring fadeInSegundos when the app is killed - Request battery-optimization exemption once, tracked with a persisted asked-once flag - Fix snooze end-to-end: native ACTION_SNOOZE now reports back to Flutter (snoozed event + cold-start sync), snooze anchor unified to occurrence+minutes on both sides, periodic recalc no longer erases an active snooze - Add snooze buttons (3/5/10/custom) to the ringing screen with shared audio teardown - Redesign ringing screen on PluriWaveScaffold with reduced-motion-aware entry animation (new PluriAnimate helper) - Alarm editor: live next-trigger preview, searchable station pickers (primary and fallback), configurable snooze duration, volume floor down to 0 - New alarm strings localized across all 13 locales - New unit/widget tests for the snooze flow, alarm bridge payloads, ringing screen and editor (77 tests green) - SDD artifacts for the app-quality-and-native-alarms change (explore, proposal, spec, design, tasks, apply progress)	2026-06-11 15:33:30 +02:00