#Alarm clock on my phone update

I’m moving to a different alarm app for now. I thought I was just sleeping through it, but I’ve tested it during the day and it is not reliably working. Alarm is now quite often not sounding at all. I just recently accepted the Android system upgrade. I have used this alarm for years with no problem. And indeed, a quick look at the apps review section in the Play Store says it all. Usually, one would expect such issues to be addressed, but it seems nothing changed.īut what could be causing the problem? Apparently, one Redditor thinks its something to do with the settings of the Google Clock app.

#Alarm clock on my phone update

This is happening despite these devices having received a newer software update with January 2020 security patches. I think there is some widespread issue here. Alarm volume was oddly low but not 100% muted, maybe at like 10% (though i would prefer it higher), still I think I would have heard it if it went off. First time it happened the alarm volume was all the way off and I saw a “missed alarm” message. I’ve faced this issue twice in the last week.

But going by the latest developments, it seems the issue is quite widespread than thought. Late last year, we covered a similar story related to the various Pixel models.Īt the time, it was thought that the alarm issue was limited to a few devices. Matter of fact, it’s not the first time that PiunikaWeb is reporting on alarm issues related to a Google Pixel phone. The latest, for instance, is preventing the Google Clock app from sounding alarms on various Pixel models. Time and again I’ve pointed out that Google Pixel software can at times surprise with the kind of bugs it picks up along the way. Original story (published on January 15, 2020) follows: New updates are being added at the bottom of this story…….