HyperCeiler: an LSPosed module that restores and extends HyperOS behaviour on Xiaomi phones

What HyperCeiler changes on a HyperOS phone

HyperCeiler is an Xposed module aimed at people who already run a rooted Xiaomi device and find the stock settings too narrow. The README frames the goal bluntly: the project exists to make HyperOS behave the way its users want, and the scope list shows how far it reaches. It hooks system, com.android.systemui, com.miui.home, com.android.settings, com.miui.securitycenter, com.android.camera, com.miui.gallery and roughly fifty other packages. That spread is the point. Instead of one tweak, the module collects many small behaviour changes across the launcher, the status bar, the security centre, the camera and the update client.

The audience is narrow by design. The README says the module supports Android 15 and 16 HyperOS only, and that it is currently adapted against Android 16 HyperOS 3.0 on phone-class devices. It explicitly does not support heavily modified third-party Xiaomi HyperOS ROMs, heavily modified system software, or some international Xiaomi HyperOS ROMs. If your device runs a custom HyperOS build, the maintainers are telling you up front that your setup is outside the tested range.

The project also states where it is heading. Xiaomi HyperOS 3 or 4 is described as an endpoint, because Xiaomi has been adjusting its own features in response to Xposed modules, so the module's feature set shrinks as the ROM absorbs some of it. That is an unusual thing for a project README to admit, and it is worth taking at face value when you plan around it.

How the module hooks Xiaomi system packages

HyperCeiler is a Java Android application built with Gradle. The repository layout shows an app module, a library module, and the usual settings.gradle.kts and build.gradle.kts at the root, which is the standard shape for an Xposed module that also ships a configuration UI. The APK is both the module and the settings screen: you enable it in LSPosed, then open the app to switch individual features on.

The activation flow in the README is short and specific. Enable HyperCeiler in LSPosed, enable the features you want inside the HyperCeiler app, then restart the scope, which requires root. The scope is the set of packages LSPosed injects the module into. HyperCeiler publishes that list in a table, and the README notes it matches the scope LSPosed recommends. That matters because an Xposed module only affects processes it is loaded into; a feature that touches the launcher will not work unless com.miui.home is in scope.

Because the module targets system processes, the failure surface is wide. A hook that misbehaves inside com.android.systemui can take the status bar down with it, and one inside system can affect the whole device. The README does not document a rollback procedure, so the practical recovery path is the one LSPosed itself provides: disable the module or remove it from scope and reboot.

Installing HyperCeiler and enabling a first feature

There is no store install. The README points to LSPosed for the framework and to the project's GitHub releases for the APK. Start by confirming your ROM: the module supports Android 15 and 16 HyperOS, and the README states that Android 11 to 13 MIUI and Android 13/14 HyperOS 1.0/2.0 are no longer maintained. Older ROMs have separate download links in the README rather than current builds.

Install the APK on the device, then enable the module in LSPosed. The README gives this order explicitly.

# On the device, after installing the HyperCeiler APK:
# 1. Open LSPosed and enable the HyperCeiler module
# 2. Open the HyperCeiler app and enable the features you want
# 3. Restart the scope (root required)

After the reboot, open HyperCeiler and turn on a single feature rather than a batch. The app groups features by target package, and the scope table in the README lists the package names, for example com.miui.home for the launcher and com.android.systemui for the status bar. If a feature does not appear to work, check that its target package is in the LSPosed scope before assuming the feature is broken.

If you want to build from source instead of using a release APK, the repository is a Gradle project with gradlew at the root. The README does not give build steps, so treat the release APK as the supported path and the source tree as the reference for what each feature hooks.

Where HyperCeiler stops working

The support boundary is the first limitation, and the README states it plainly. Android 14 HyperOS 1.0 and 2.0 are archived, and support for Android 14 was removed starting with version 2.6.162. The current release listed by the project is 2.10.166, so anyone still on Android 14 needs an older build, not the latest one. Two beta builds, 2.6.162 and 2.6.163, sit between the archived line and the current release, which suggests the version history is not a clean staircase.

The second limitation is coverage. The README says the module is adapted against Android 16 HyperOS 3.0 on phones and that coverage is not complete, requiring ongoing testing and improvement. A module that hooks fifty-odd packages across a moving ROM will always have features that lag behind a system update. The README also warns that HyperOS 2 will be archived in later maintenance because the gap between versions is large, so the supported surface is shrinking over time, not growing.

The third is the ROM itself. Heavily modified third-party Xiaomi HyperOS ROMs, heavily modified system software, and some international Xiaomi HyperOS ROMs are listed as unsupported. On those builds the hooks may target code that has been moved or replaced. If you run a custom ROM, this is the wrong tool regardless of how well it works on a stock device.

HyperCeiler against CustoMIUIzer and its own predecessor

The README credits CustoMIUIzer and CustoMIUIzerMod, both of which address the same problem for older Xiaomi ROMs. The difference is era. CustoMIUIzer was built for MIUI, and the README links a separate Cemiuiler release for Android 11 and 12 MIUI users, which is the same project lineage under an earlier name. HyperCeiler is the HyperOS branch of that work.

That means the real alternative is not a different product but a different version of this one. If you are on MIUI, the README directs you to Cemiuiler 1.3.130. If you are on Android 13 MIUI or HyperOS 1.0, it points to a specific HyperCeiler 2.5.156 build. If you are on Android 14 HyperOS, you need a build before 2.6.162. Choosing the current release on an older ROM is the most likely way to get a module that installs and then does nothing useful.

The other comparison is against doing nothing. Xiaomi has been folding some Xposed-style behaviour into HyperOS itself, which the README acknowledges when it says the module's feature count is declining as the system absorbs features. On a recent HyperOS build, check whether the setting you want already exists before adding a hook for it.

Maintenance, licence and the cost of upgrading

The repository is not archived, and the last push was on 2026-09-16, so the project is being worked on. That does not mean every feature works on every build; the README is candid that adaptation is incomplete and that HyperOS 2 will eventually be archived. A system update from Xiaomi can change the code a hook depends on, and the module has to catch up. Budget for that: after a ROM update, expect to re-check the features you rely on.

HyperCeiler is licensed under AGPL-3.0, with an MIT_License.md also present at the repository root, which suggests some components carry a different licence. If you plan to redistribute the module or build on its code, read both files rather than assuming a single licence covers the whole tree. This is a description of what the repository contains, not legal advice.

The upgrade cost is mostly version matching. Releases are tagged, and the README's own guidance shows that the correct build depends on your Android version and ROM generation, not simply on the newest tag. Keep the APK version you installed recorded somewhere, because when a feature breaks after a system update, the first question is whether the module version still matches the ROM.

Editorial conclusion

Adopt HyperCeiler if you run Android 15 or 16 HyperOS on a phone, already have root and LSPosed, and want behaviour the stock settings do not offer. Do not adopt it on MIUI, on HyperOS 1.0 or 2.0, on Android 14 builds, or on a heavily modified third-party Xiaomi ROM, because the README states those are unsupported or archived. Before installing, confirm your exact ROM version against the supported list, check that LSPosed is running, and read the scope table so you enable the module only for the packages you intend to change.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. Project website
3. README
4. ReChronoRain/HyperCeiler on GitHub
5. Releases