In this guide, we will show you a nifty workaround to fix the issue of being unable to stop the alarm on the latest Android 14 QPR3 Beta. The latest beta build of the Quarterly Platform Release brings in a few noteworthy features. The appearance of the app icon when using the fingerprint, Scanning for deceptive apps, and Circle to Search for beta users [it was rolled out to stable users first, unintentionally!] are just some of the new features that it welcomes abode.
However, being a beta build, it is bound to have a few issues as well, and that has indeed been the case this time around, though it seems to have brought a rather interesting yet equally infuriating bug with itself. Many users have voiced their concern that they cannot turn off or stop their alarm ever since updating their device to the latest Android 14 QPR3 Beta build.
Even force-stopping the clock app does no good and they have to take the nuclear route of restarting their device, which isn’t the most viable or feasible way of addressing this issue. Well, we managed to get hold of a nifty workaround that should help you rectify this bug without the need to restart your device. So without further ado, let’s check it out.
Fix Cannot Stop Alarm on Android 14 QPR3 Beta
After going through numerous user reports, we found out that one thing stood out in common- they all were using a custom ringtone as their ‘wake up’ tone. And this tends to give rise to this issue. So to rectify it, you just need to choose from any one of the preset system tones. Here’s how it could be done:
- First off, launch the Clock app and go to the Alarm tab.
- Then expand your alarm and tap on the current tone.
- Finally, select any tone from the Device Sounds section.
That’s it. This should fix the issue of being unable to stop the alarm on the latest Android 14 QPR3 Beta. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
