Google Assistant Glitch May Be Causing Users to Miss Alarms and Calls on Android

A puzzling bug with the Google Assistant has come to light.
This indicates that the Do Not Disturb settings are not being acknowledged.
Key calls and notifications might get overlooked because of the flaw.

Google Assistant might be on the way out as Gemini gradually replaces it, but before it leaves the stage, it seems to be causing problems with calls and alarms being missed – apparently due to a Do Not Disturb bug.

Initially, reports started surfacing on Reddit , the team at Android Authority I was also able to reproduce the problem. Basically, activating Do Not Disturb through a Google Assistant voice command completely silences both incoming calls and alarm notifications as well.

It means any custom tweaks you've made – regarding specific contacts, apps, and alarms that are exempt from the Do Not Disturb rules – won't be applied, so you might be missing out on seeing various communications and alerts.

The straightforward solution is to activate Do Not Disturb along with its different modes via Android’s settings and shortcuts instead of using Google Assistant, as this will ensure the feature works correctly. Nonetheless, this approach might still catch some users off guard.

Setting modes

It appears that the issue stems from the various settings available within the Do Not Distrupt feature itself. For those using a Pixel device, these options can be accessed by navigating to Settings and then selecting the relevant option for Do Not Disturb. Modes entry.

Starting from there, you have the ability to personalize the settings for Do Not Disturb and establish extra modes — such as ones tailored for driving or bedtime. These individualized modes allow different configurations regarding which apps and contacts remain unmuted.

In the Reddit post mentioned earlier, a user forgot about their wake-up alarm, whereas another tried setting alerts from an older family member who has dementia to bypass the Do Not Disturb feature; however, they found out this solution didn’t work properly.

Until now, Google has remained silent regarding the bug, offering no information on potential fixes—should updates become available, we will revise this piece accordingly. Additionally, it remains uncertain whether every single Android device is experiencing this issue; however, it’s advisable to stay vigilant.