Smartphones are truly indispensable given how they’ve subsumed all the other gadgets in our lives. They are used by many as buzzers to wake up, and as such a possible alarm bug on Android Oreo is quite worrying.

The crux of the issue is how some Android Oreo devices are not playing a sound or waking the screen when an alarm set through the default Google Clock app is scheduled to go off. Additionally, other users note they are not even receiving a “Missed alarm” notification either.

So far, Oreo users on a Pixel and Nexus 5X have reported being affected by the bug. This problem does not seem to be widespread as a quick test on a Pixel running the September security patch has everything functioning perfectly.

Those who have encountered the issue recommend a variety of suggestions to possibly remedy the problem. The most common being that a reboot every so often should keep the bug away. Others note that using a third-party alarm app does not seem to trigger the issue.

Meanwhile, some are suggesting that the issue only arises when using custom media files as an alarm sound. Most notice that the default tones will always ring at the end of an alarm.

Google Clock was updated to support Oreo early last month and also introduced a darker theme and new icon. Given the complaints for such a critical function, Google will soon likely patch it.

Check out 9to5Google on YouTube for more news:

FTC: We use income earning auto affiliate links. More.

Check out 9to5Google on YouTube for more news:

You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel

About the Author

Abner Li

Editor-in-chief. Interested in the minutiae of Google and Alphabet. Tips/talk: