Affiliate links on Android Authority may earn us a commission. Learn more.
Google Pixel phones have a long-standing bug with the Clock app that prevents alarms from going off on time. It has hampered users’ experience for years now, and we can trace reports back to as early as 2021. While Google claimed to have fixed it, newer reports keep cropping up every now and then, and that hasn’t changed.
We’ve spotted newer reports coming from Pixel users about the alarm not firing when intended. According to screenshots shared by users, these missed alarms occur for an “unknown reason.” Mysterious reasons that Google had promised to address, but hasn’t.
For reasons far too obvious, missing an alarm can have serious consequences, as was the case for another Pixel user who was fired from their job after the alarm didn’t go off. The reason, however, was less mysterious — rather not mysterious at all; their Pixel got too hot for the alarm to go off.
We’ve reached out to Google to ask whether its teams are aware of the alarm bug still spooking Pixel users, and we’ll share what they say when we get a response. Meanwhile, we’ve spotted other reports of alarms failing to wake Pixel users up. In these cases, while they do go off on time, alarms are not heard for yet another mysterious reason.
According to one of them, no sounds come from alarms, timers, or the stopwatch, even when the phone is in silent mode. Audio otherwise works fine, even while choosing an alarm tone. For another one, there are audio issues across several apps, including the Clock app. These two issues seem too discrete and unrelated for it to be difficult to pin down a common cause or associate them with the “unknown reason” issue mentioned above.
We will still hold off for some clarity until we hear from Google. In the meantime, we would love to hear from you if you also have similar issues with alarms on your Pixel phones.
Thank you for being part of our community. Read our Comment Policy before posting.
