Android 8.0 Oreo Causing Alarm Clock Issues, Random Reboots for Some Users

Android Oreo started rolling out to Pixel and Nexus devices a few weeks ago, but despite all the testing ahead of its launch there have been a number of bugs pointed out by users. Now, some users who have updated their Pixel and Nexus devices to the new Android version are now facing a problem with the Google Clock app, with its alarms not working properly. Moreover, other users have also reported that Android Oreo update is causing random rebooting in the middle of normal operations on their devices.

In an emailed complaint to Android Police, a reader reported the issue whereby the alarm clock on his Pixel device, running on Android Oreo, would go off if the alarm is set to less than an hour, while it won't if the same has been set to a further time. While this may have been a one-off occurrence, several other users mentioned the same issue in reviews on the Google Clock app's listing on GooglePlay. Several annoyed users have mentioned how the bug made them late for work.

Besides, the Android Oreo bug list got one more entry where other users last week began to report that their Pixel and Nexus devices performed random reboots amid normal operations since they upgraded to Android Oreo. Android Police says that some of their own staff members also started facing the issue, only to find out that it was widespread when they witnessed Pixel and Nexus device owners decrying the issue on Twitter. The issue was expected to be done away with in the latest September OTA that the devices received, but that apparently has not happened.

This random rebooting issue was also later thought to be loosely related to some YouTube issues on Android Oreo. The Picture-in-Picture (PiP) mode seemed to have caused reboots for a bunch of users, reports Android Police. However, later it was discovered that this YouTube PiP rebooting issue was a separate issue altogether, which was reported to have been fixed internally via a statement issued in Google Tracker forum.

Some of the workarounds that people have retorted to the aforementioned issues are switching to a different alarm clock app from Google Clock in the first case, while in the second case rolling back to Android Nougat worked for some users. But apart from these methods, there's not much you can do to except waiting for Google to address these issues with fixes.

Recently, a number of Android 8.0 Oreo users reported that their Pixel and Nexus devices were forcefully using mobile data even if their devices were connected to Wi-Fi. Later, other users were reportedly facing deactivation of mobile data automatically on some devices after they were updated to Android Oreo.