One UI 8 makes living with multiple alarms a whole lot easier
TL;DR Samsung's new One UI 8 beta for the Galaxy S25 series improves its alarm group functions.
Users can now add existing alarms to alarm groups.
Further, they can now place an alarm group widget on their home screen, making it much more convenient to control multiple alarms with a single tap.
Samsung rolled out One UI 8 beta program for the Galaxy S25 series, and we're digging through the update to find all the changes. With One UI 8, Samsung is adding some quality-of-life improvements to alarm groups, one of the best features added to One UI 7.
Many people set multiple alarms for tasks like getting up for work or school. If you are one of those (no judgment), you'd know that managing all of these alarms can be a hassle, especially if you want to pause them for a day or two. Samsung introduced the ability to group alarms together with One UI 7, letting users group related alarms to turn them on and off with a single click.
As part of the One UI 8 changelog, Samsung is touting the following upgrades to the alarm group functionality:
Enhanced alarm groups: You can now add existing alarms to an alarm group by tapping the + button on the Alarm group screen. You can also add an alarm group to a widget on your Home screen so you can turn all of the alarms in the group on or off with a single tap.
The first part of this change fixes an annoyance in One UI 7. In One UI 7, the plus button inside an alarm group would create a new alarm within the group rather than letting you add an existing alarm to the group, as you can see in the screen recording below:
With One UI 8, pressing the Plus button within an alarm group lets you choose between adding a new alarm or moving an existing alarm into the group.
Further, as mentioned in the changelog, you can now add an alarm group widget to your home screen. In the screenshot below, you can see widgets for an individual alarm and an alarm group. This makes it highly convenient to toggle an alarm group right from your home screen.
Zac Kew-Denniss / Android Authority
One UI 7 only lets you place a single alarm as a widget, even if that alarm already nests within an alarm group. Now, with One UI 8, you can have complex alarm groups and still easily manage them. These are small quality-of-life changes that make a profound impact on the end user experience.
Got a tip? Talk to us! Email our staff at
Email our staff at news@androidauthority.com . You can stay anonymous or get credit for the info, it's your choice.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Digital Trends
21 minutes ago
- Digital Trends
Watch the Galaxy Z Fold 7 do something amazing in this brutal bend test
Samsung's Galaxy Z Fold 7 became available to buy on Friday, which meant that it also became available for popular tech YouTuber Zack Nelson to subject the handset to his nasty durability test. Nelson set it up nicely by noting the 'fun fact' that none of the phones in Samsung's flagship Fold series have ever snapped in two in the bending part of his durability test. 'However, this new guy, the Samsung Galaxy Z Fold 7, is the thinnest Fold yet, so here's to hoping that it finally happens today,' he quips. At the start of the test, the YouTuber (of the channel JerryRigEverything) comments on how gorgeous the Galaxy Z Fold 7 looks. But of course, by the end of the test, the handset is an utter wreck. As is usual with his infamous durability test, Nelson sets to work with various pointy metal tools to test the susceptibility of the $2,000 foldable handset to scratches and other damage. What quickly becomes apparent is that that the Z Fold 7's inner display is as delicate as its predecessors, scratching as it does at a low Mohs hardness level of just 2. While the phone is not dust-resistant, it does have an IP48 rating, meaning that it offers protection against solid objects larger than 1 mm, a fact that prompts Nelson to dump a handful of grit on the inner display before closing it shut. Yes, you will wince. Then comes the bend test. 'The thinness of this phone is wild,' Nelson says of the 4.2mm-when-open design, at the same time suggesting that the device in his hand will not survive 'for more than a few minutes' as Samsung has 'finally gone too far.' The YouTuber then sets about enthusiastically bending it in the direction in which it most definitely should not be bent. For a moment, the phone looks done for. But then, with all of Nelson's brut force applied, the Galaxy Z Fold 7 does something amazing: It remains intact. 'I'm literally flexing the rear glass panel out of the frame without the glass cracking, without the phone cracking, and without the hinge cracking — literal black magic,' Nelson says, adding: 'The Fold 7 is still able to fold completely shut and is still 100% operational.' It's highly impressive, with the YouTuber quipping that his 'disappointment is immeasurable.' Want to find out more about Samsung's Galaxy Z Fold 7? Then check out Digital Trends' hands-on review.
Android Authority
an hour ago
- Android Authority
Samsung may be killing bootloader unlocking on all phones with One UI 8
Joe Maring / Android Authority TL;DR Samsung appears to be disabling bootloader unlocking in One UI 8 on more devices than before. Previously, only US models lacked the OEM Unlock toggle, but the restriction now seems to be spreading to global models as well. A contributor on XDA Developers discovered that Samsung is likely stripping out the necessary code to unlock bootloaders entirely. Samsung might be quietly locking down its phones even more tightly with the One UI 8 update. A new report from an XDA Developers contributor reveals that Samsung appears to be removing the ability to unlock the bootloader on more devices, including international versions that previously supported it. Samsung phones in the US already lack the 'OEM Unlocking' toggle in Developer Options, effectively preventing users from unlocking the bootloader and installing custom ROMs. But now, it looks like that restriction could apply globally. What's changed? The contributor, salvo_giangri, discovered that Samsung has added a line to the device's bootloader configuration: This line tells the Android system whether the device is allowed to unlock the bootloader. If it's set to 1, the Settings app won't even show the OEM Unlock option, which is the first step in unlocking a phone. In the latest One UI 8 firmware, this line is present even on non-US devices, indicating that the restriction is no longer region-specific. We checked and can confirm that our non-US Galaxy Z Fold 7 does not have the 'OEM Unlocking' toggle in Developer Options. Some folks think this could be a mistake on Samsung's part. However, those running the One UI 8 beta build also report that the option is missing from their devices. Unlocking the bootloader is essential for enthusiasts and developers who want to install custom ROMs or kernels, gain full root access to their devices, or further customize their phones. If you're someone who loves customizing your phone or values the freedom to tinker with Android, then this is a significant step back from Samsung. Anyone planning to update to One UI 8 or buy a new Samsung device running Android 16 should know that this restriction may apply to their devices. That said, we'll reach out to Samsung for an official confirmation on the matter. For now, the bootloader on your current Samsung devices that are not running One UI 8 should still be unlockable, but with new updates and devices, that may no longer be the case.
Android Authority
2 hours ago
- Android Authority
Google says it's working to fix voice commands for your smart lights
Lil Katz / Android Authority TL;DR Google has acknowledged a bug affecting voice commands for smart lights. The company says it is aware of the issue and will share an update soon. Many users say they can still control lights via the Google Home app, but not through Assistant voice commands. Google has confirmed it's investigating a bug preventing users from controlling their smart lights through Google Assistant voice commands. We first reported on the issue over the weekend, as user complaints have continued to pile up on Reddit and Google's support forums in recent days. Android Authority's Rita El Khoury also experienced the problem firsthand, noting that her Nest Audio speaker stopped responding to voice commands to turn off the lights. In a comment posted on Reddit, the official Google Nest account has now addressed the problem: We're aware of an issue with using voice commands to control some lights. We'll share an update as soon as possible, thanks for your patience. While Google hasn't provided a timeline for a fix, it's clear the issue is more than a small glitch. Affected users report various problems, including Google not recognizing light groups, turning off the wrong lights, or responding with silence when given commands like 'Hey Google, turn off the lights.' Most users say the lights can still be controlled via the Google Home app, suggesting that the issue lies specifically with Assistant voice functionality. Some users have found workarounds, such as syncing devices again or removing and re-adding their lighting services, but results vary. 'I had this problem too. I saw someone else post a fix earlier today (Google must have done something that messed things up). You just need to reconnect the service you use for your lights. Go to Google Home app, click the + button to add a new device. Go to the works with Google section and reconnect any of the services you use for the lights. That should work… Maybe,' a user noted on Reddit. However, this may not be an easy fix for those who have multiple lights connected throughout their home. The bug comes at a difficult time for Google's smart home ecosystem, which has been under increased scrutiny from users citing reliability issues. Google has also promised major improvements to the platform in the fall. Until then, users will have to wait for an official fix for this particular problem related to voice commands for connected lights or rely on manual controls as a workaround.
