When was this device last restarted?
It is one of the first questions in any troubleshooting conversation, and usually nobody has a real answer. Android hides uptime in Developer options and keeps its boot log behind ADB, a tool few users or administrators have at hand.
RebootMonitor logs every restart automatically, the moment it happens, and turns the raw uptime value into a report anyone can read on the device in seconds. No app has to be opened for a reboot to be tracked.
Detected automatically
The app listens for Android's boot-completed signal and logs the exact time of each restart.
No duplicate entries
Android's own boot counter makes sure a single restart is never recorded twice.
Live uptime
Days, hours and minutes since the last restart, read from the system clock whenever you open the app.
Drill into any day
Tap a square in the monthly heatmap to see the exact reboot times of that date.
What's in the report
Status, uptime and the last days on the main screen, and the full history one tap away.
| Section | What it shows |
|---|---|
| Status | "Good" or "Reboot recommended", following your reminder interval (7 days by default) |
| Uptime | Live counter: days, hours and minutes since the last restart |
| Last 7 days | A color-coded row per day, with the exact reboot time if one occurred (14 days when the reminder is set to 14) |
| History | A summary with the longest stretch without a reboot, a tappable monthly heatmap and a monthly overview, up to 12 months back |
What it looks like
Where it helps
- Confirming that a restart you asked for really happened, and when, for example after a fix or an update.
- Spotting a device that has quietly run for weeks, or one that keeps rebooting on its own.
- Backing up a support conversation with an actual number instead of "it's been a while".
Stays on the device
- The history lives in a local database. Nothing is uploaded, synced or exported.
- Only two permissions:
RECEIVE_BOOT_COMPLETEDandPOST_NOTIFICATIONS. No account, no analytics, no internet access needed. - Entries older than 12 months are cleaned up automatically. Uninstalling the app removes the history.
Frequently asked questions
How does RebootMonitor detect a reboot?
It listens for Android's RECEIVE_BOOT_COMPLETED broadcast, which the system sends once at the end of every startup, and records the current time. The device's boot counter makes sure the same restart is never logged twice.
What exactly does RebootMonitor mean by uptime?
The time elapsed since the device's last restart, read from the Android system clock. It resets to zero every time the device actually reboots. It is the same value Android keeps in Developer options, shown on its own screen along with the history.
How far back does the history go?
Up to 12 months. The monthly heatmap and the monthly overview cover the full year, and older entries are cleaned up automatically after that.
Can I export the report as a file?
Not currently. The report is meant to be read on the device itself, in line with RebootMonitor keeping all data local instead of generating files or sending data elsewhere.
Does the history reset if I reinstall the app?
A normal update keeps it. A full uninstall removes it, because the history is never backed up off the device by design.
Is this a fleet-wide monitoring dashboard?
No. RebootMonitor shows uptime and history on the device itself, for whoever is holding it. There is no central server or cross-device dashboard, by design. See reboot monitoring for managed fleets for how that works in practice.
See when your device last restarted
Install RebootMonitor and the first restart after that is already logged.