whatsapp a:hover { background: linear-gradient(#01A507, #069A00); } .whatsapp i { color: #038F02; background: #FFF; text-shadow: none; font-weight: 900; border-radius: 2px; position: relative; left: -3px; margin-right: -4px; padding: 2px; -webkit-font-smoothing: antialiased; } .whatsapp a { font-family: sans-serif; font-weight: 700; text-decoration: none; font-size: 11px; color: #FFF; padding: 7px; background: linear-gradient(#009805, #058400); padding-top: 4px; border-radius: 2px; padding-bottom: 5px; text-shadow: 1px 1px 2px #797272; }

Search Beejay Tech's Blog

Saturday 23 September 2017

Alarms Set via Google Clock not Ringing for some Android 8.0

Alarms ⏰ set via Google Clock �� are not ringing �� for some on Android 8.0 Oreo

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.

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.

This problem does not seem to be widespread as a quick test on a Pixel running the September security patch has everything functioning perfectly. 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.

No comments:

Post a Comment

Kindly Use the Comment Box