BioWake — Smart Body Battery Alarm

Stop waking up exhausted. BioWake alarms at your recovery peak. Most alarms fire at a fixed time — ignoring whether your body is ready. BioWake reads your Garmin Body Battery every 5 minutes during a wake window you set (e.g. 06:00 – 07:30), and wakes you the moment your recovery score hits your personal goal. Sleep your full natural cycle. Wake up energised. HOW IT WORKS 1. Set your wake window (e.g. "no earlier than 06:00, no later than 07:30") 2. Set your Body Battery goal (e.g. 80%) 3. BioWake monitors in the background — no battery drain on the main app 4. When your Body Battery reaches the goal inside your window — alarm fires 5. Safety net: if the window closes without hitting the goal, the alarm still fires WHAT YOU SEE - Large, pure-black clock (OLED-safe, minimal glow while you sleep) - Live Body Battery % with glowing arc ring (green / amber / red) - Recovery trend indicator (rising / stable / falling) - Your wake window and goal shown at a glance - Full-screen alarm with escalating vibration + alert tone - Snooze 5 min with UP button SETTINGS (tap screen, press SELECT/UP, or long-press MENU) - Wake Start time - Wake End time - Body Battery Goal (10 – 100%) - Vibration strength: Gentle / Standard / Strong / Vibe Only (silent) - Test Alarm — preview the alarm any time - Reset Today — allow the alarm to fire again on the same day COMPATIBLE DEVICES Works on all Garmin watches with Body Battery and SensorHistory: Fenix 6/7/7X/8, Epix 2 / Pro, Forerunner 255/265/955/965/970, Venu / Venu 2 / Venu 3, Vivoactive 4/5, MARQ, Enduro, Instinct 2 Free forever. Support the developer at: https://buymeacoffee.com/neutralworks

v1.1.4 — Reliability & battery-life fix - Fixed: On some devices (especially Forerunner 945), the background check could fail to run, so the alarm never fired. The background service is now correctly scoped and runs reliably. - Fixed: Significantly reduced overnight battery usage. A scoping issue caused the full app to load on every 5-minute background check; now only the lightweight service loads. Thanks to user Jan N. for the detailed report!