LSposed Manager Error Resolution Guide

Steps to Reproduce/复现步骤

When attempting to open LSposed manager, an error occurs. The user followed issue #123 as a solution but encountered further errors in the logs which seem to be causing the issue.

The logs display the following error messages:

11-24 13:58:12.083  1394  2469 E AndroidRuntime: FATAL EXCEPTION: binder:1394_5
11-24 13:58:12.083  1394  2469 E AndroidRuntime: PID: 1394
11-24 13:58:12.083  1394  2469 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method getUsers(ZZZ)Ljava/util/List; in class Landroid/os/IUserManager; or its super classes (declaration of 'android.os.IUserManager' appears in /system/framework/framework.jar!classes3.dex)
11-24 13:58:12.083  1394  2469 E AndroidRuntime:  at h2.d(Unknown Source:19)
11-24 13:58:12.083  1394  2469 E AndroidRuntime:  at h1.onTransact(Unknown Source:797)
11-24 13:58:12.083  1394  2469 E AndroidRuntime:  at android.os.Binder.execTransactInternal(Binder.java:1441)
11-24 13:58:12.083  1394  2469 E AndroidRuntime:  at android.os.Binder.execTransact(Binder.java:1385)
11-24 13:58:12.083  1394  2469 E LSPosedService: Uncaught exception
11-24 13:58:12.083  1394  2469 E LSPosedService: java.lang.NoSuchMethodError: No interface method getUsers(ZZZ)Ljava/util/List; in class Landroid/os/IUserManager; or its super classes (declaration of 'android.os.IUserManager' appears in /system/framework/framework.jar!classes3.dex)
11-24 13:58:12.083  1394  2469 E LSPosedService:  at h2.d(Unknown Source:19)
11-24 13:58:12.083  1394  2469 E LSPosedService:  at h1.onTransact(Unknown Source:797)
11-24 13:58:12.083  1394  2469 E LSPosedService:  at android.os.Binder.execTransactInternal(Binder.java:1441)
11-24 13:58:12.083  1394  2469 E LSPosedService:  at android.os.Binder.execTransact(Binder.java:1385)
11-24 13:58:12.084  1394  2469 I lspd    : System.exit called, status: 1
11-24 13:58:12.084  1394  2469 I AndroidRuntime: VM exiting with result code 1.
11-24 13:58:12.102  1681  3071 E LSPosed-Bridge: service is dead
11-24 13:58:12.103 10350 10359 I AndroidRuntime: VM exiting with result code 0, cleanup skipped.
11-24 13:58:12.219 10386 10386 D nativeloader: Load <a href="http://libframework-connectivity-tiramisu-jni.so">libframework-connectivity-tiramisu-jni.so</a> using APEX ns com_android_tethering for caller /apex/com.android.tethering/javalib/framework-connectivity-t.jar: ok
11-24 13:58:12.228 10386 10386 D nativeloader: Configuring clns-9 for other apk /data/app/~~yYUAW7DS0gUb75dvvW4Elw==/org.lsposed.manager-By7znjQmkLh2nl7cRaTR9Q==/base.apk. target_sdk_version=36, uses_libraries=, library_path=/data/app/~~yYUAW7DS0gUb75dvvW4Elw==/org.lsposed.manager-By7znjQmkLh2nl7cRaTR9Q==/lib/arm64, permitted_path=/data:/mnt/expand:/data/user/0/org.lsposed.manager
11-24 13:58:12.587  2853 10338 D nativeloader: Load /data/app/~~TPIgx9wFiWTvXRmRKNuElQ==/com.google.android.gms-hXuwMUSkpoYhdfmZhv0cUg==/base.apk!/lib/arm64-v8a/libbrotli_native.so using class loader ns clns-9 (caller=/data/app/~~TPIgx9wFiWTvXRmRKNuElQ==/com.google.android.gms-hXuwMUSkpoYhdfmZhv0cUg==/base.apk): ok

Expected Behavior/预期行为

The user expects to be able to open LSposed without encountering any errors.

Actual Behavior/实际行为

The LSposed manager crashes and shows a message indicating that LSposed is not installed.

Xposed Module List/Xposed 模块列表

None yet

Root Implementation/Root 方案

KernelSU Next is being used for rooting.

System Module List/系统模块列表

None yet

LSPosed Version/LSPosed 版本

1.10.2

Android Version/Android 版本

16

Version Requirement/版本要求

Logs/日志

The logs provided above show a fatal exception in the Android runtime related to a missing method getUsers in the IUserManager interface. This error seems to be the root cause of the issue where the LSposed manager crashes when opened.

Troubleshooting Steps

  1. Update LSposed: Ensure that you are using the latest version of LSposed from the provided GitHub Actions link.
  2. Check Compatibility: Verify that the version of LSposed you are using is compatible with your Android version (Android 16).
  3. Rooting Method: Confirm that KernelSU Next is properly installed and functioning as expected.
  4. Reinstall LSposed: If the issue persists, try reinstalling LSposed manager.
  5. Check Logs: Look for additional error messages in the logs that might provide more insight into the issue.
  6. Community Support: If the problem continues, seek assistance from the LSposed community or GitHub repository for further guidance.

By following these steps, the user should be able to identify and potentially resolve the issue preventing LSposed manager from opening properly.