FlashDroid Alerts Arriving Late or Not at All: What to Check

Your child reaches school at 8:10.

The arrival notification appears at 8:24.

Or it never appears.

Before treating that as one problem, split the alert path into two parts:

Did the child phone generate/send the event?

and

Did the parent phone display the notification?

A delay can happen at either side.

Step 1: confirm notifications are allowed on the parent phone

Modern Android versions use notification permissions, and users can disable an app's notifications at any time.

Check the parent phone:

Settings → Apps → FlashDroid → Notifications

Confirm:

• notifications are allowed
• relevant notification categories are enabled
• Do Not Disturb is not suppressing the alert
• OS/vendor notification settings are not blocking background delivery

Android documents the notification runtime-permission model for recent versions.

Source: https://developer.android.com/develop/ui/compose/notifications/notification-permission

Step 2: ask whether the child-side event was fresh

A school-arrival alert depends on location.

If the child phone had:

• no network
• stale location
• battery restriction

the arrival event itself can be delayed.

Check the last child location timestamp.

If location is old, troubleshoot that first: FlashDroid location not updating.

Step 3: check child-phone connectivity

A rule or location event cannot reach the parent immediately if the child phone is offline.

Check:

• mobile data
• Wi‑Fi
• airplane mode
• whether the phone was powered off

After reconnecting, delayed events may appear later.

Step 4: check Doze and background restrictions

Android Doze can defer background network access and work while the device is idle.

Source: https://developer.android.com/training/monitoring-device-state/doze-standby

Some manufacturers add more aggressive battery management.

If alerts are reliable while the child uses the phone but late when it sits idle, inspect app-specific background settings.

Use the brand guide instead of copying menu paths from a different phone:

• Oppo
• Realme
• Motorola
• generic Android

Step 5: check “unused app” behaviour

Android can optimise apps that have not been used for a long time by:

• revoking permissions
• stopping background activity
• stopping notifications

Source: https://support.google.com/android/answer/13627979

For a child-side protection app, verify it is excluded from unused-app pausing if your setup requires that.

Not every late alert means the app failed

An arrival alert is a chain:

1. phone gets a location
2. safe-zone crossing is detected
3. event is communicated
4. parent notification is delivered

Delay in any step moves the final notification.

That is why “the alert was 10 minutes late” should be diagnosed rather than treated as proof of one specific failure.

Test notifications separately from location

Use two tests:

Test A: rule/action notification

Trigger a parent/child event that does not depend on location, if available.

Test B: safe-zone event

Walk or drive across the safe-zone boundary with the child phone online.

If A works and B does not, focus on location.

If neither works, focus on notification/background/connectivity.

What FlashDroid provides

FlashDroid can surface:

• safe-zone arrival/leave alerts
• rule/permission awareness where supported
• relevant child-device events

It cannot make Android ignore all battery-management rules or guarantee zero-delay notifications under every network condition.

See the Android parental-controls guide and child location use case.

Fast fix order

1. Check parent notification permission.
2. Check Do Not Disturb/category settings.
3. Check child phone online status.
4. Check child location freshness.
5. Check child app background/battery state.
6. Check unused-app optimisation.
7. Follow the phone-brand persistence guide.
8. Restart and retest one event.

Separate a missing event from a missing notification

The parent app may sometimes contain the event even when the phone did not show a push notification.

Check the parent app's recent activity or event history if available.

If the event is present there but no notification appeared, focus on:

• notification permission
• notification channel/category
• Do Not Disturb
• parent-phone battery/background settings

If the event itself is absent, focus on the child side:

• child connection
• location freshness
• child app background health

This one distinction can cut troubleshooting time in half.

Test with the screen locked

A notification system that only works while the parent app is open is not behaving the way a parent expects.

After confirming permissions:

1. lock the parent phone
2. trigger one simple alert
3. wait for delivery
4. repeat after the phone has been idle

If delivery becomes unreliable only after idle time, inspect the parent phone's own battery/notification restrictions too.

Do not treat every alert as urgent

Some alerts are informational.

A delayed safe-zone event is different from a live emergency.

If the family needs emergency communication, use normal calls or emergency services rather than relying on a parental-control notification as the only channel.

Sources

• Android Developers — Notification runtime permission
  https://developer.android.com/develop/ui/compose/notifications/notification-permission
• Android Developers — Doze and App Standby
  https://developer.android.com/training/monitoring-device-state/doze-standby
• Android Help — Manage unused apps
  https://support.google.com/android/answer/13627979