- A mysterious Google assistant error has been reported
- Means that not disturbing the configuration is not recognized
- Important calls and alerts can be lost due to error
The Google assistant could be coming out as Gemini gradually replaces it, but before it leaves the stage, it seems to be causing problems with the calls and alarms that are lost, apparently due to an error of not disturbing.
With reports that emerged first in Reddit, the Android Authority team could also replicate the problem. Essentially, activating not to bother through a voice command by Google Assistant also measures calls and alarms as well.
It means that any personalized adjustment you have made, with respect to specific contacts, applications and alarms that are exempt from the rules of not disturbing, will not apply, so it is possible that several communications and alerts are being lost.
The simple solution is to enable not to bother and its various ways through the configuration and shortcuts of Android, instead of the Google assistant, which should apply the function correctly. However, it could lead users to be trapped.
Configuration modes
Be careful with the Scary New, don’t bother Google Assistant Bug 😰 R/Googlepixel
The problem seems to be linked to the different flavors of not disturbing that they can be configured through not disturbing. If you have a pixel phone, you can find them addressing the configuration and taking advantage of the Modes entrance.
From there, you can customize the options not to bother and configure additional modes, to drive or when you are asleep, for example. Each mode can be configured differently when it comes to applications and contacts exempt from being silenced.
In the Reddit thread previously linked, a user had lost a call of attention alarm, while another had established calls from an old relative with dementia to annul not disturb, but discovered that this did not work as planned.
Until now, Google has not commented on the error, or said anything about a solution: we will update this article if there is an update. Nor is it clear if the error is affecting all Android devices, but it is something to take into account.
