LSPosed-Irena: a GPL-3.0 LSPosed fork for Android 8.1 to 16
Useless LSPosed Framework Fork
At a glance
- What is it?
- LSPosed-Irena is a Zygisk module that provides an ART hooking framework with Xposed-compatible APIs. It targets Android 8.1 through 16, installs through Magisk, and keeps its community discussion off the repository.
- Who is it for?
- Adopt LSPosed-Irena if you already run Magisk v26+ with ZygiskNext on Android 8.1 to 16 and you want an LSPosed build whose release cadence you can follow through its Telegram channel and GitHub Actions. Do not adopt it if you need a documented support forum, an official website, or guarantees about module compatibility: the README states this fork will not have community discussion, and it accepts bug reports only from the latest debug build.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 131 days ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 24, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What LSPosed-Irena changes on a device, and who it is for
LSPosed-Irena is a fork of LSPosed, which is itself a fork of EdXposed, and it keeps the Xposed programming model: modules change how the system and apps behave without modifying any APK. The README quotes the original Xposed description to explain why that matters. All changes happen in memory, so deactivating a module and rebooting returns the device to its previous state, and several modules can alter the same part of the system at once, which is not possible when each one ships a patched APK. That property is the whole reason the framework exists.
The audience is narrow and specific. You need a rooted Android device, Magisk v26 or newer, and either ZygiskNext or Zygisk enabled in Magisk. The README recommends ZygiskNext. Supported versions run from Android 8.1 to 16, so a device on Android 7 or below is out of scope. Developers writing modules are the second audience: the README states that a module built on the LSPosed framework is fully compatible with the original Xposed Framework, and a module built for Xposed will work with LSPosed. That two-way compatibility is the practical reason to pick this over a bespoke hooking setup.
The repository description calls it a useless LSPosed Framework Fork. Treat that as a joke in the project metadata rather than a technical claim, but it does signal the posture of the fork: it does not try to sell itself.
How the hooking pipeline is put together
The chain has four links, and each one is a separate project. Magisk makes root and module loading possible. ZygiskNext injects code into the zygote process. LSPlant is the ART hooking framework that actually replaces method behaviour. Dobby handles inline hooking. LSPosed-Irena sits on top and exposes the XposedBridge API surface that modules compile against.
The repository layout reflects that separation. There is a core/ directory for the framework, a daemon/ directory, a magisk-loader/ directory that packages the module for Magisk, a dex2oat/ directory, a hiddenapi/ directory, a services/ directory, and an app/ directory for the manager. A libxposed/ directory sits alongside them. The build is Gradle-based, with build.gradle.kts, settings.gradle.kts, gradle.properties and the Gradle wrapper at the top level. Java is the primary language.
One detail worth noticing in the credits: xz_embedded is listed for decompressing the debug_info section into stripped libraries. That tells you the framework carries debug information into an environment where libraries are normally stripped, which is what makes readable stack traces from hook failures possible. The README does not explain this further, and it does not document how hook failures are surfaced to the user.
Installing LSPosed-Irena through Magisk and opening the manager
The README gives a six-step install. The order matters, because the framework cannot load without a working injection path.
First install Magisk v26 or newer, then install ZygiskNext from its own releases page, or enable Zygisk inside Magisk. The README recommends ZygiskNext. Next, download LSPosed-Irena and install it in the Magisk app, then reboot. After the reboot, open the LSPosed manager from the notification, or install manager.apk from inside the zip file if the notification does not appear.
Those five steps are the whole procedure as written, and the README does not add a verification command or an uninstall step. From the manager you enable modules and pick which apps they apply to. The README closes the install section with the line "Have fun :)", which is the full extent of the post-install guidance. There is no documented first-run walkthrough, no explanation of scope selection, and no troubleshooting section for the case where the notification never arrives. For canary builds the README points to the GitHub Actions workflow on the dev branch instead of the releases page.
Where this fork is the wrong choice
The support model is the first constraint. The README states plainly that this fork will not have community discussion. There is no forum, no chat for users, and no homepage field on the repository. Help comes from GitHub issues and a Telegram channel, and the issue policy is strict: only bug reports from the latest debug build are accepted, and issues must have an English title. A Chinese-speaking user who cannot write an English title is directed to a translation tool. If you want a fork with a discussion venue, this is not it.
The second constraint is the release gap. The two releases listed are 2.0.0 on 2026-05-14 and 1.9.2 on 2024-10-17. That is roughly nineteen months between them. The last push to the repository was on 2026-05-22, so development activity is not continuous in the way a stable release channel implies. Anyone who needs predictable, dated releases should read that gap carefully before committing.
The third is the ordinary risk of hooking frameworks. The README does not document rollback, does not describe what happens when a module misbehaves, and does not list known incompatibilities. The general undo path is described in the quoted Xposed text: deactivate the module and reboot. That covers module-level mistakes, not a framework that fails to boot. If a device is your daily driver and you have no recovery plan, the framework's own documentation gives you nothing to work with.
LSPosed-Irena against other LSPosed forks
The search data around this project is dominated by fork comparisons, particularly against JingMatrix's fork. The README does not describe that fork, so the honest comparison is about what this repository documents rather than a feature-by-feature table.
The difference that is visible is distribution and support. LSPosed-Irena ships releases through its Telegram channel at @lsposed-irena and through GitHub Actions for canary builds, and it explicitly declines to host community discussion. A fork that runs a discussion venue is making a different bet: it accepts the moderation cost in exchange for user feedback. This one trades that away for a lower-maintenance model. Which is better depends on whether you need to ask questions in public.
The second difference is version reach. This fork states support for Android 8.1 to 16. If your device is on an Android version outside that range, the README gives no path forward, and no compatibility shim is mentioned. The third is the module repository: the README points developers at the Xposed-Modules-Repo and says modules submitted there can be downloaded inside LSPosed. That is an inherited part of the LSPosed ecosystem rather than something this fork built.
Licence terms and what a fork obliges you to do
The repository is licensed under GPL-3.0, and the README states it as GNU General Public License v3. The full text sits in the LICENSE file at the repository root.
The practical consequence for anyone building on this code: GPL-3.0 is a copyleft licence, and distributing a modified version generally requires releasing the corresponding source under the same terms. The README does not add any exception, and it does not describe a separate commercial licence. This is not legal advice, and the exact obligations depend on how you distribute, but a fork of a GPL-3.0 project that ships as a Magisk module inherits that licence rather than escaping it.
Upgrade cost is the other maintenance question. Because the framework loads into the zygote process and hooks ART, an Android version bump can change the internals it depends on. The README lists Android 16 as supported, and the 2.0.0 release is dated 2026-05-14, so that support is recent relative to the version range. The README does not describe a compatibility policy for future Android releases, and it does not state how quickly new versions are picked up.
Editorial conclusion
Adopt LSPosed-Irena if you already run Magisk v26+ with ZygiskNext on Android 8.1 to 16 and you want an LSPosed build whose release cadence you can follow through its Telegram channel and GitHub Actions. Do not adopt it if you need a documented support forum, an official website, or guarantees about module compatibility: the README states this fork will not have community discussion, and it accepts bug reports only from the latest debug build. Before flashing, verify the Android version of your device, confirm ZygiskNext is installed or Zygisk is enabled in Magisk, and check the release page for the 2.0.0 build dated 2026-05-14.
Frequently asked questions
What does LSPosed-Irena do?
It is a Zygisk module that provides an ART hooking framework with APIs consistent with the original Xposed, built on the LSPlant hooking framework. Modules using it can change system and app behaviour in memory without modifying any APK.
Is LSPosed-Irena safe to use?
The README does not make a safety claim. What it does say is that all changes happen in memory, so deactivating a module and rebooting restores the original system. It also requires Magisk v26+ and ZygiskNext or Zygisk, which means root access is a precondition.
How do I remove LSPosed-Irena?
The README does not document an uninstall procedure. The closest guidance is the quoted Xposed description: deactivate the module and reboot to get the original system back, which covers modules rather than the framework itself.
What is the difference between Xposed and LSPosed-Irena?
LSPosed-Irena delivers APIs consistent with the original Xposed, and the README states that a module based on the LSPosed framework is fully compatible with the original Xposed Framework, and vice versa. The difference is delivery: Xposed is the original framework, while this is a Zygisk module built on LSPlant.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/re-zero001-lsposed-irena)