Real-World Scenarios

When a Phone Goes Quiet,
Someone Should Know

Guard2 works silently in the background. These scenarios show what that quiet monitoring can mean when a phone goes offline or stays unused — and a family needs to know.

Get It on Google Play Back to Use Cases

Four Typical Scenarios

Four situations our users describe. In each, the answer wasn't a smartwatch or a daily tap — it was simply knowing whether the phone was still alive and being used.

👵

The Sunday Mom Didn't Answer

Lin works in another city; her mother lives alone. One Sunday morning her mother slipped in the bathroom and couldn't get up to her phone. The phone stayed on the floor — powered on, but nobody unlocked it.

By late morning, Guard2's cloud server noticed the screen hadn't been unlocked in over six hours during the daytime monitoring window, and emailed Lin. She called, realized something was wrong, and contacted a neighbor who let the paramedics in.

Guard2's role: No daily check-in to forget. The alert came from the cloud, based on the missing screen-unlock signal — not on Mom remembering to tap anything.

🏔️

When the Phone Died on the Ridge

A father went hiking on a multi-day trail. On day two his phone battery died in a valley with no signal. The phone itself couldn't send anything — it was simply off.

Because Guard2 expects a heartbeat roughly every 20 minutes, when the heartbeats stopped for over two hours the cloud server flagged it and emailed his designated contact. That contact checked his itinerary and alerted the local ranger station.

Guard2's role: Works even when the phone is offline. The alert originates from the server noticing silence — not from the dead phone.

🌍

Three Time Zones and a Quiet Phone

A college student studying abroad. Her parents at home kept texting "did you eat? are you okay?" every few hours out of worry — and felt uneasy every time she didn't reply instantly.

With Guard2, they stopped the constant pinging. If the student's device stayed inactive past the threshold, they'd get one clear email; otherwise, silence meant the phone was simply being used as normal.

Guard2's role: Replaces anxious hourly check-in texts with a single, meaningful signal.

🔇

The One Who Never Texts Back

Some people simply don't text or call back regularly. Family members couldn't tell whether a message had been seen at all, and every silence felt like a warning.

Guard2 offers one honest signal: is the device being used at all? It can tell you the phone is active or has gone quiet — but it cannot confirm whether a specific message was read.

Guard2's role: One honest device-activity signal, with no false certainty about what was read.

A note on these scenarios: The scenarios above are illustrative composites inspired by the situations our users describe; names and details are fictional. Guard2 monitors device activity, not a person's health or physical safety, and is one signal among many — it is not a medical or emergency service. Alerts are evaluated by a cloud server on a periodic cycle (not in real time) and delivered by email.

For Home-Care Providers & Charities

If you look after many people who live alone — residents of home-care programs, elders supported by volunteer networks, or families you serve — Guard2 helps your team keep a quiet eye on all of them from a single inbox.

🏠

Many Devices, One Inbox

Each person's phone reports independently. Your team receives alert emails in one place and always knows exactly which resident's device went quiet.

🤲

No Check-In Burden on Residents

Residents don't need to remember to tap anything every day. No extra chore, no confusion, and no false alarms caused by a forgotten check-in.

🚨

Cover the Moments Staff Can't

Nights, weekends, and gaps between visits. If a phone powers off or stays unused past the threshold, the cloud server alerts you — even when nobody is on site.

📋

Accountability to Families

Email alerts create a simple, timestamped record that a check-in was prompted — helpful when you need to show families that care was coordinated.

Interested in rolling Guard2 out across your program or charity?
Reach out and we'll help you get started.

Contact Us Try It on Google Play

Keep a Quiet Eye on the People You Love

Install once, configure in under a minute, then forget about it.

Get It on Google Play

💬 Share Your Feedback

🔐 Stock Android — No Setup Needed

On stock Android (AOSP / Pixel / Google OS), Guard2 works out of the box — no manual permission configuration required.

✅
Notification Permission

When Guard2 launches, a dedicated permission-setup screen requests notification permission (required on Android 13+ for the short-lived foreground service). Simply tap "Allow" when prompted — that's all. If you ever need to re-enable it: Settings › Apps › Guard2 › Notifications › Allow.

✅
Alarms & Reminders Permission

On the same permission-setup screen at launch, Guard2 also requests the Alarms & reminders (exact-alarm) permission so the 20-minute heartbeat fires on time. Simply tap "Allow" when prompted. If you ever need to re-enable it: Settings › Apps › Guard2 › Alarms & reminders › Allow setting exact alarms.

⚙️ Custom ROM — Permissions

On stock Android (AOSP / Pixel / Google OS), Guard2 works with just the two permissions granted at launch — Notifications and Alarms & reminders. If Guard2 isn't working normally (heartbeats stop, no alerts after a reboot, or the phone shows "no records"), your device's custom ROM is adding extra battery / autostart restrictions on top of stock Android. Enable the additional permissions listed below for your manufacturer.

Follow the REQUIRED steps so the app survives reboot and background kills; the RECOMMENDED steps further improve reliability under aggressive power-saving.

Stock Android permissions first (Notifications + Alarms & reminders, granted at launch), then these additional Samsung (One UI) permissions if Guard2 isn't working:

🔋
Battery — Unrestricted
RECOMMENDED

Prevents One UI power-saving from pausing Guard2 during heavy background activity.

Settings › Apps › Guard2 › Battery › Unrestricted
📡
Mobile Data — Allow Background Data
RECOMMENDED

Reduces the chance of One UI data saver interrupting heartbeats.

Settings › Apps › Guard2 › Mobile data › Allow background data usage › Enable

Stock Android permissions first (Notifications + Alarms & reminders, granted at launch), then these additional Xiaomi (MIUI/HyperOS) permissions if Guard2 isn't working:

🚀
Autostart
REQUIRED

MIUI/HyperOS blocks autostart by default — must be enabled manually.

Settings › Apps › Manage Apps › Guard2 › Autostart › Enable
🔋
Battery Saver — No Restrictions
RECOMMENDED

Prevents MIUI/HyperOS aggressive battery optimization from freezing Guard2.

Settings › Apps › Manage Apps › Guard2 › Battery saver › No restrictions
📡
Unrestricted Data Access
RECOMMENDED

Reduces the chance of MIUI/HyperOS data-saver mode cutting Guard2's background network access.

Settings › Privacy › Special App Access › Unrestricted data › Guard2 › Allow
🔒
Lock in Recent Apps
RECOMMENDED

Prevents Guard2 from being killed when you swipe away other apps.

Open Recent Apps › Long-press Guard2 card › tap Lock (🔒)

Stock Android permissions first (Notifications + Alarms & reminders, granted at launch), then these additional OPPO (ColorOS) permissions if Guard2 isn't working:

🚀
Auto-start Manager
REQUIRED

Enable autostart so Guard2 restarts after a reboot.

Settings › Battery › Auto-start Management › Guard2 › Enable
🔋
Battery — Allow Auto-start / Background
RECOMMENDED

Prevents ColorOS power-saving from freezing Guard2 in the background.

Settings › Battery › App Battery Management › Guard2 › Allow auto-start & background running
📡
Background Data — Unrestricted
RECOMMENDED

Reduces the chance of ColorOS data-saver interrupting heartbeats.

Settings › App Management › Guard2 › Data Usage › Allow background data usage

Stock Android permissions first (Notifications + Alarms & reminders, granted at launch), then these additional Vivo (OriginOS) permissions if Guard2 isn't working:

🚀
Startup Manager
REQUIRED

Allow Guard2 to start on boot via OriginOS Startup Manager.

i Manager › Startup Manager › Guard2 › Enable
🔋
High Background Power Consumption
RECOMMENDED

Prevents OriginOS power-saving from freezing Guard2 in the background.

Settings › Apps & Permissions › App Management › Guard2 › Battery › Allow high background power consumption
📡
Background Data — Unrestricted
RECOMMENDED

Reduces the chance of OriginOS data-saver interrupting heartbeats.

Settings › Apps & Permissions › App Management › Guard2 › Data Usage › Allow background data usage