A look at the setup

A screenshot from my Redmi Note 13 Pro 4G: the heart battery sits alongside matching status icons, with custom images and colors throughout the Control Center.

Make the status bar yours

• Heart battery: A crisp outline with a bottom-to-top fill that follows the battery level. Ring, Capsule and Default styles remain available.
• Battery colors: Choose normal, charging, low and full colors, with optional automatic tint and matching colors for the clock, Wi-Fi, signal, notifications and shade headers.
• Wave and pulse: Animate the heart while charging, or opt to keep it animated when unplugged. Continuous animation may use more battery.
• Brightness and percentage: Adjust the heart's brightness and show the percentage inside, to the right, or hide it.
• Control Center images: Choose and crop backgrounds for Wi-Fi, mobile data, Bluetooth, airplane mode, the music card, brightness and volume; adjust the images' overall brightness.
• Control Center colors: Pick active and inactive icon colors, plus separate active and inactive card text colors. Optional large Bluetooth and airplane cards add another row.
• Theme backup: Export settings and selected Control Center images as a ZIP from About, then import it to restore or share the theme. Custom fonts are not included.

Install the framework

Use DFRoot or GhostLock for temporary root, whichever supports your device. If you already followed the HyperCeiler + HyperLight setup, reuse your existing root and Vector installation.

Enable the module in Vector

1. Prepare a compatible root and Xposed/Vector environment for your device.
2. Install the HyperLock Extended APK from the project's releases when available.
3. In Vector → Module Management, enable the module and scope it to com.android.systemui.
4. Restart SystemUI or reboot with your root and injection environment active.
5. Open HyperLock Extended, choose Heart and explore the Heart battery and Control Center settings.

Compatibility

Based on HyperDuo, with the Heart mod by Yuilix. I tested the extended features on my Redmi Note 13 Pro 4G (emerald), Android 16, build OS3.0.305.0.WNFMIXM. SystemUI implementations differ, so behavior can vary across devices and ROM versions.

What you'll need

Prepare KernelSU and Zygisk

1. Confirm your exact device/patch level is supported by the chosen root method.
2. Install KernelSU manager and initialize temporary root with DFRoot or GhostLock, whichever supports your device.
3. Verify KernelSU reports root access for the current boot.
4. Install the Zygisk Next ZIP through KernelSU's Modules section.
5. Install Vector's compatible module package through KernelSU as instructed by Vector's release notes.

I had intermittent failures with GhostLock and got better results with DFRoot on my device. Some devices work with GhostLock when DFRoot fails; use whichever works for your kernel. A supported GhostLock profile must match the exact kernel build.

Enable both customization modules

1. Install the HyperCeiler and HyperLight APKs.
2. Open Vector, enable the modules, and use each module's recommended scope list.
3. Use only package targets present on your firmware.
4. Make one simple visual change first and confirm it works.

The following are major HyperLight scope targets noted in the guide. They are references, not a universal recommendation to enable all scopes on every device.

com.android.systemui
miui.systemui.plugin
com.miui.securitycenter
com.miui.personalassistant
com.android.settings
com.xiaomi.subscreencenter
com.miui.aod

Soft restart and verify

After installing the modules, complete the supported soft-restart sequence for your root setup, then check if the modules still working by opening KernelSU>Module> Vector> press on action button, if it does not launch then go to Homepage of KernelSU and soft-reboot once again. After the 2th reboot it is guaranteed to work and then go check whether Vector reports HyperCeiler and HyperLight as active. Some individual changes require a restart of the targeted process, such as SystemUI. After a full reboot without root, I can restore temporary root and my saved patches load again automatically.

Do not assume an active Xposed toggle means every hook works. Xiaomi can rename or remove internal classes and fields between firmware builds.

If nothing changes

Verify the scope, module activation, and target-process restart. Check Vector logs for errors such as NoSuchFieldError or ClassNotFoundException. Those can indicate a hook no longer matches Xiaomi's implementation.

Don't add extra signature-bypass or framework patch modules as a generic fix. Changing more system components makes failures much harder to isolate.

Tools and permissions

These tweaks enable flags that already exist in HyperOS. Most of the listed settings put system commands can be applied through Brevent without root; the separate persist.sys.* property commands require a root-capable shell on this setup. HyperUnlocked is optional and separate from the main blur commands. The native flags survived normal reboots without root on my phone.

Apps you need

For temporary root, use DFRoot or GhostLock, whichever works for your device. Both can provide root for the Termux commands on supported setups.

1. Install Brevent and start its service using the method supported by your device.
2. Install Termux from its official GitHub release and open it once.
3. Start your temporary-root environment. Allow Termux root access in KernelSU → Superuser, or approve its root request when prompted.
4. After granting access, use Restart app for Termux in KernelSU, then open Termux again.
5. Run the su -c property commands below in Termux and approve any root prompt. Run the separate settings commands in Brevent's command runner.

These are already shell commands. Do not add adb shell in Termux or Brevent. Granting permission lets Termux request root; each su -c command runs with root.

Read before changing

Save the original property and settings values. There is no safe universal reset value for every Xiaomi firmware.

su -c 'getprop persist.sys.computility.cpulevel'
su -c 'getprop persist.sys.computility.gpulevel'
su -c 'getprop persist.sys.advanced_visual_release'
su -c 'getprop persist.sys.background_blur_supported'

settings get system miui_control_center_use_advanced_textures
settings get system control_center_blur_style
settings get system use_blur_render
settings get system background_blur_enable
settings get system miui_blur_enable
settings get system miui_advanced_animations

Enable visual-level flags

Run these four commands in Termux after enabling temporary root and granting Termux root permission. These are existing Xiaomi feature flags, rather than replacements for system APKs. I tested them on build 3.0.305.0, and they survived full reboots on my setup. Root is needed to write these properties, while ordinary operation afterward does not require keeping a temporary-root session active. Their names do not mean they physically overclock your CPU or GPU.

su -c 'setprop persist.sys.computility.cpulevel 6'
su -c 'setprop persist.sys.computility.gpulevel 6'
su -c 'setprop persist.sys.advanced_visual_release 1'
su -c 'setprop persist.sys.background_blur_supported true'

Enable blur and textures

Paste these native HyperOS settings into Brevent's command runner. I tested these flags on build 3.0.305.0, and they remained enabled after reboots without root. Whether another Xiaomi build uses each flag depends on its firmware and features.

settings put system miui_control_center_use_advanced_textures 1
settings put system control_center_blur_style 1
settings put system use_blur_render 1
settings put system background_blur_enable 1
settings put system miui_blur_enable 1
settings put system miui_advanced_animations 1

Restart and confirm

Apply the changes, use the restart method supported by your setup, and check Settings → Display & brightness → Advanced textures. For Control Center appearance, open the shade and compare the blur intensity directly.

On the tested phone, the configured native blur/texture flags remained in place after a normal reboot. Root-dependent module effects may disappear until temporary root is restored; in my tests, those saved effects reapplied automatically. Visible results can still vary by hardware, ROM and SystemUI components.

HyperUnlocked

The original guide also references HyperUnlocked v2.3.2 for additional visual features. This is a separate KernelSU module; test the underlying blur settings first so you can tell which change caused an effect.

Restore previous values

Use the original values you recorded in step 02. Do not assume all settings originally contained 0 or false. If a setting did not exist, consider deleting that setting rather than forcing an invented default.

# Replace ORIGINAL_VALUE with your recorded value.
# Examples only:
# su -c 'setprop persist.sys.advanced_visual_release ORIGINAL_VALUE'
# settings put system control_center_blur_style ORIGINAL_VALUE

Downloads

Common questions

HyperUnlocked

The original guide also references HyperUnlocked v2.3.2 for additional visual features. This is a separate KernelSU module; test the underlying blur settings first so you can tell which change caused an effect.

Original write-ups

r/HyperOS / Discussion: HyperCeiler + HyperLight guide ↗

r/AndroidTurkiye / Rehber: HyperOS cihazlar için blur ve gelişmiş dokular ↗