Enable FIPS Mode on SLES 15 and Verify the Boot State
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Modes and Routines is a new feature in Samsung's One UI 5 that allows you to open apps and change settings automatically to suit what you're doing.

The One UI 5 update for Samsung Galaxy introduced some new exciting features, including Modes and Routines. These two tools give you new ways to combine phone settings, styles, and layouts for everyday life activities.
Below is the best way to set up and use Modes and Routines on Samsung Galaxy devices.
How to use Modes and Routines on Samsung phones
Modes and Routines are two different ways of achieving the same basic things. Each tool allows you to quickly adjust your Samsung device setup to suit your current needs.
For example, you can select Workout Mode before working out or create a Sleep Routine to open when you're ready to work out. Your device settings will instantly switch to accommodate these situations, be it silent notifications or playing workout music.
The main difference between these two tools is Modes. You can enable it manually or with another task. Routines are like IFTTT applets. It is triggered when specific criteria are met such as location, time, or when a task is performed.
You need to be using One UI 5 or higher on your Samsung Galaxy device to access and edit Modes and Routines using the method below.
The device has a number of Modes available for you to use the first time you access this feature, including Sleep, Workout, Driving and Relax. You still need to configure these Modes before you can use them, but they give you a good starting point.
You can also create Custom Modes for situations that are not suitable for the modes in Preset Modes as follows:
You can delete both Custom Modes and Preset Modes (when configured) by selecting them, tapping the More button (3 dots) and selecting Delete .
Routines are similar to Modes but may be more suitable when you want to change settings to automation. They operate on an If/Then - Condition/Result process.
Previous Routines were created via Bixby, but this feature has been separated from the voice assistant in One UI 5. The process for creating them is similar. Basically, you need to follow these steps:
A new feature of Routines in One UI 5 is the ability to activate a pair of apps instead of just one. When using this option, the app will open in a split screen with one app at the top and one at the bottom.
First, you need to enable Customization Service. You can see a popup confirming turning it on on the Routines screen. If not, you can find it by tapping the More button, then Settings > Customization Service .
Above is how to use Modes and Routines in One UI 5 . Hope the article is useful to you.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.