Knowledge base
Why background alarms are rare
On iPhone and iPad, a monitoring app can't keep watching the battery or the thermal state after you leave it. iOS pauses the app within seconds. That's why a "charge complete" alarm is hard to build, and why Therbie's Alerts work only while Therbie is running.
What iOS does
- Apps you leave are paused within seconds. A paused app can't read the battery, and iOS stops sending it battery updates.
- Background modes are for their stated purpose only. iOS lets an app keep running for specific jobs, such as playing audio, navigation, or Picture in Picture. Apple's App Review Guidelines (section 2.5.4) allow these modes only for their intended purpose. An app that plays silent audio just to stay awake breaks that rule.
When Therbie keeps running
Therbie keeps running in the background only while one of its features genuinely needs it:
| Feature | What it keeps doing | How often it reads CPU, memory, heat and battery |
|---|---|---|
| Floating monitor open | Updates the window, records History, checks alerts | Every second (every 5 seconds in Low Power Mode or when Hot) |
| A trip recording | Records the trip, plus History and alerts | Every 10 seconds |
| A sensor with Keep logging in the background on (Location or Sound Level) | Logs that sensor, plus History and alerts | Every 10 seconds |
When none of these is running, iOS pauses Therbie like any other app.
What fills the gaps
- Widgets: each time iOS refreshes a Therbie widget, the widget takes a reading and saves it to History. iOS decides when that happens. Apple's WidgetKit documentation says a widget people look at often gets roughly a refresh every 15 to 60 minutes. See Widgets.
- Shortcuts: for an alarm that works with Therbie closed, use a Shortcuts automation built into iOS: Automation › New › Battery Level › Rises Above 80%, then Show Notification. See Shortcuts and Siri.