Module

LSPosed and Vector: Xposed modules on Android 15, 16 and 17

LSPosed brings the Xposed module API to modern Android through Zygisk, so modules can change how apps behave without touching system files. The original project has had no release since October 2023 and stops at Android 14. Its maintained continuation is JingMatrix's fork, renamed Vector in 2026, which runs on Android 8.1 through 17.

Last updated 11 sourcesHow we check pages

On Android 15 or newer, install Vector, not the original LSPosed

LSPosed's last release is v1.9.2 from October 11, 2023, and its README lists Android 8.1 to 14. JingMatrix's fork (formerly JingMatrix/LSPosed) was officially renamed Vector in v2.0 on March 22, 2026, and v2.1 added full Android 17 support. Its v2.1 also moved to a new Xposed API with breaking changes, so some older modules need updates.

Status checked .

Setting up LSPosed and Vector: the whole job

  1. Step 1 · 2 minutesTurn on Zygisk and remove old LSPosed
  2. Step 2 · 2 minutesInstall the Vector module
  3. Step 3 · 1 minuteOpen the manager
  4. Step 4 · 2 minutes per moduleEnable a module and choose its scope
Each stage links to its full instructions below.

Which LSPosed do I need?

ProjectStatusLatestAndroid
Vector (JingMatrix, formerly JingMatrix/LSPosed)Maintainedv2.2 stable (Aug 4, 2026); canary builds weekly8.1 to 17
LSPosed (original)Unmaintainedv1.9.2 (Oct 11, 2023)8.1 to 14
LSPosed_mod (mywalkb)Inactive1.9.3 (Mar 8, 2024)8.1 to 15 beta

Install only one. Vector's issue tracker reports bootloops when the old LSPosed module is left installed next to it.

How it works

Vector runs inside app processes through Zygisk and gives Xposed modules hooks into Java methods in memory. Nothing on the system partition changes, which is why a module only affects the apps you choose for it (its scope) and changes take effect when those apps restart. Modules written for the classic Xposed API generally work; Vector v2.1 added the new libxposed API 101, which has breaking changes, and v2.2 added API 102 with hot reload, after which modules run only for the users that installed them.

Its manager has no launcher icon by default. It runs inside another app's process (a “parasitic” manager) and is opened from a notification or the module's Action button in Magisk.

Before you start

You will need

  • Magisk v30.7 or newer with Zygisk on (Settings → Zygisk). On Android 16 QPR2 you need at least v30.7; on Android 17, use v31.1, the first stable release with Android 17 support for Zygisk.
  • No second Zygisk. Vector's guide says only non-Magisk users (KernelSU, APatch) need NeoZygisk, ReZygisk or Zygisk Next.
  • The Vector zip from its GitHub releases. Canary builds are in the project's GitHub Actions and need a GitHub login.
  • USB debugging on, so you can remove modules over adb if something fails to boot.

Know the limits

  • Play Integrity. The PlayIntegrityFork README warns that modules which modify the system, such as Xposed, can trigger Google's DroidGuard detections.
  • Older modules. Modules built only for the new libxposed API need Vector 2.1 or later; some legacy modules may misbehave after the API change.
  • A module runs with your apps' permissions. Install modules only from their authors or the module repository, and scope them to the apps they need.

Install Vector with Magisk

Each step has a Done box so you can keep your place. Your progress is saved in this browser only.

  1. Turn on Zygisk and remove old LSPosed

    2 minutes

    In the Magisk app open Settings and enable Zygisk. If the original LSPosed or another LSPosed build is installed, remove it on the Modules screen and reboot first.

  2. Install the Vector module

    2 minutes

    Download the latest zip from Vector's releases page. In Magisk tap Modules → Install from storage, pick the zip, and reboot.

  3. Open the manager

    1 minute

    After the reboot, tap the Vector notification. If there is none, open Modules in Magisk and tap Vector's Action button. If the manager still won't open, its guide suggests installing manager.apk from the module folder as a normal app, or using the command-line tool at /data/adb/vector/cli.

  4. Enable a module and choose its scope

    2 minutes per module

    Install an Xposed module's app, then in the manager open Modules, enable it, and select the apps it should apply to. Most modules show a recommended scope that is selected automatically. Force-stop the scoped apps, or reboot when a module targets the system framework.

Check that it worked

The manager's home screen shows the framework as active, with the Vector and API versions. If it says not active, see the errors below. Modules are listed with their scope, and the manager's Logs tab shows whether a module loaded into an app.

Errors and fixes

The manager says the framework is not active

Usually a stale manager app left from an older version whose signature no longer matches. Reinstall the manager from the System Status page, or open it through the notification or shortcut. Vector's v2.2 notes add: if you installed the manager as a separate app, uninstall it before updating, because a 2.1 manager cannot talk to a 2.2 daemon.

Modules stop loading on Android 17 or a QPR beta

Vector's issue tracker traced this to a changed zygote signature (“no matching signature for nativeForkAndSpecialize”). The fix comes from the Zygisk implementation, not Vector: on Magisk use v31.0 or newer; on KernelSU or APatch update NeoZygisk or Zygisk Next.

Bootloop after installing Vector

Remove the old LSPosed module if it is still installed, reboot, then install Vector and clear the cache of com.android.shell. To get back into the phone first, use Magisk's Safe Mode (it starts automatically after two failed boots) or run adb shell magisk --remove-modules.

There is no Vector notification

Update Magisk and use the module's Action button in the Magisk app instead.

Zygote crashes on KernelSU Next

The maintainer traced this to mismatched KernelSU Next kernel and manager versions and does not plan a Vector fix. Match the two versions.

Questions people ask

Is LSPosed dead?

The original is unmaintained: its last release was v1.9.2 on October 11, 2023, and its last commit January 2024. Development continues in JingMatrix's fork, now called Vector.

What is LSPosed Vector?

JingMatrix's fork of LSPosed, officially renamed Vector in v2.0 on March 22, 2026. It supports Android 8.1 through 17 and remains GPL-3.0.

Does LSPosed work on Android 15, 16 or 17?

The original only lists Android 8.1 to 14. Use Vector, which supports up to Android 17.

Do I need Zygisk Next or NeoZygisk with Magisk?

No. Magisk's built-in Zygisk is enough; on Android 17 use Magisk v31.0 or newer. The standalone Zygisk modules are for KernelSU and APatch.

Where do I find Xposed modules?

The module repository at modules.lsposed.org, generated from the Xposed-Modules-Repo GitHub organization, lists over 1,200 modules.

Will LSPosed break Play Integrity?

It can. PlayIntegrityFork's README warns that Xposed-style modules can trigger DroidGuard detections.

Is Zygisk Next open source?

No, not since v4-0.9.2. ReZygisk and NeoZygisk are open-source alternatives.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.

Report a problem with this page