An alarm that does not arrive or is not heard almost always traces back to one of a small number of device or system settings — not the app itself. Work through these in order.
Power and connectivity
- Is the phone powered on and charged?
- Does it have a network connection — Wi-Fi or mobile data — at the time the alarm is meant to fire?
- Has it been restarted recently without reopening the app at least once?
Permissions and sound
- Are notification permissions still granted? They can be revoked by a system update or an accidental tap.
- Is Focus or Do Not Disturb active? These operate independently of silent mode and can still block delivery.
- Has the alarm sound or volume been changed in the app or on the device?
Battery and background limits
- Is the app affected by battery optimization or a manufacturer power-saving mode? See Battery settings blocking Android alarms for the Android-specific detail.
- Has background activity been restricted for the app in device settings?
Pairing and account state
- Is the pairing still active on both devices? A disconnect on either side stops delivery silently.
- Was the alarm actually sent — check the Activity history on the parent side before assuming it did not arrive.
After checking all of this
Send a test alarm after making any change, and retest after operating system updates, app updates, or a new phone — settings like these do not always carry over. And keep a backup routine regardless: WakeKids is a convenience tool for family mornings, not a substitute for a second alarm on days that truly cannot slip.