1.5.1

Changelog

• Fix the issue that Magisk mounted apps are not displayed
• Update some strings
• Remove workaround for modules who get module's apk path from classloader's DexFile's name.

更新日志

• 修复 Magisk 挂载的应用不被显示的问题
• 更新一些字符串
• 移除从类加载器的 DexFile 名字获取模块 apk 路径的兼容。（旧版QQ复读机可能无法使用）

1.5.0

Changelog

• Fix manager white screen
• Support split-apk modules (LSPosed will choose only one apk with xposed_init to load)
• Fix manager crash when launching an uninstalled module from notification
• Load modules with SharedMemory (it can speedup app cold launch) ²
• New manager icon
• Fix incorrect update notification in the first installation
• Fix some apps not showing in the scope list in some rare cases
• Show notification of module uninstallation
• Prevent modules from hooking inner methods (methods from XposedBridge's classloader)

更新日志

• 修复管理器白屏
• 支持 split apk 形式的模块（LSPosed 会加载第一个带 xposed_init 的 apk）
• 修复从通知打开已卸载模块时候的崩溃
• 使用 SharedMemory 加载模块（这可以加快 app 冷启动速度）²
• 新的管理器图标
• 修复第一次安装错误的更新提示
• 修复在极其罕见情况下某些应用不显示在作用域列表
• 卸载模块时显示通知
• 防止模块 hook 内部方法（与 XposedBridge 同一个类加载器的方法）

---

¹ For some weird devices that prevent installing apps from the root user, please install the manager from /data/adb/lspd/manager.apk or manager.apk from the zip file manually.
² Some modules get modules' apk path using reflection of its classloader, it's not recommended and unstable since the apk path from classloader no longer exists when using SharedMemory to load modules. Please use the documented way (from IXposedHookZygoteInit.StartupParam.modulePath) instead. See #856 as well.

¹ 对于阻止从根用户安装应用的设备，请手动从 /data/adb/lspd/manager.apk 或 zip 文件中的 manager.apk 安装管理器。
² 一些模块使用反射从类加载器获取模块路径，这是不稳定的，在使用 SharedMemory 加载模块后这里已经不存在模块路径。请使用文档中的方法（从 IXposedHookZygoteInit.StartupParam.modulePath 获取）。详见 #856。

1.4.7

Changelog

• Fix system injection failure on some devices

更新日志

• 修复某些设备上的系统框架注入失败

1.4.6

Changelog

• Fix completely broken native hook since v1.4.5
• Rework module repository implementation which brings better markdown support, fancier README rendering, and module update detection
• Fix a few crash issues

更新日志

• 修复上个版本完全坏掉的 native hook
• 重构模块仓库实现，带来了更好的 markdown 支持和自述文件渲染，并支持模块更新检测
• 修复一些崩溃问题

1.4.5

Changelog

• Fix crash when failed to load a dex
• Fix updating of pm-hidden modules
• Fix updating modules after soft-rebooting
• Fix manager crash on tablet devices

更新日志

• 修复加载 dex 失败后的崩溃
• 修复被 pm hide 的模块的更新
• 修复软重启后模块不更新
• 修复平板下管理器崩溃

1.4.4

Changelog

• Fix app crash or bootloop when the module returns a mismatched value
• Fix the issue that duplicated modules are displayed when installing modules
• Refactor the manager to use AndroidX Navigation
• Log when the hooked app crashes, helping module developer better debug their modules

更新日志

• 修复当模块返回不匹配值时应用崩溃或无法开机
• 修复安装时显示重复模块的问题
• 使用 AndroidX Navigation 重构管理器
• 在被 hook 应用崩溃时输出日志，帮助模块作者更好调试模块

1.4.3

Changelog

• Remove multiple internal native hooks, which brings better performance
• Fix manager installation on Pixel devices with Android 12
• Fix compatibility of Android 8.1
• Show the user name in manager instead of the user id¹

更新日志

• 移除多个内部的 native hook，带来了更好的性能
• 修复 Pixel 设备在 Android 12 下的管理器安装问题
• 修复 Android 8.1 的兼容
• 在管理器不再显示用户 id 而是显示用户名¹

1. If surprised by the user name, you can change it from Settings-System-Advanced-Multiple users. The route may vary from ROM to ROM.
   如果对用户名感到意外，可以在设备的设置-系统-高级-多用户界面修改用户名，不同系统的位置可能不一样。

1.4.2

Changelog

• Fix module scope can only be set on one user
• Fix in some devices users are not fully listed

更新日志

• 修复模块只用于只能在一个用户上设置
• 修复某些设备上不能列出所有用户

1.4.1

Changelog

• Fix in MIUI dual modules added by manager will be deleted by reboot
• Automatically switch user when launching apps or modules of secondary users.
• Support launching modules with android:showForAllUsers="true" without switching user
• Fix Riru installation check
• Fix activation of modules from non-primary users

更新日志

• 修复 MIUI 下管理器添加的双开模块重启被自动移除
• 启动次用户模块或者应用时自动切换用户
• 支持不切换用户下启动带 android:showForAllUsers="true" 的模块
• 修复检查 Riru 安装
• 修复非主用户下模块的激活

1.4.0

Changelog

• Fix in a rare case system modules not working
• Workaround for that some low-quality modules stick post-fs-data.sh
• Update native hook API
• Follow some changes on Android S (support S Beta 1 now)
• Restrict hidden API bypass to modules' classloader only
• Add an option to help modules to hide their icons on Android Q+
• New way to better support dual apps/multi-users¹

更新日志

• 修复极小概率的系统模块无法生效
• 解决某些低质模块卡死 post-fs-data.sh 的情况
• 更新 native hook 的 API
• 跟进一些 Android S 上的修改（兼容 Android S Beta 1）
• 限制仅模块类加载器允许绕过隐藏 API
• 添加选项帮助模块在 Android Q+ 上隐藏图标
• 支持双开、多开应用的新策略¹

1. Previously LSPosed only recognize modules from the primary user. However, this strategy is not good and leads to some problems: some modules require getting installed app lists for configuration but they cannot do so across users; some require reading themselves from the hooked apps but they cannot do so from non-primary users; some users want to configure modules differently on different users which is not feasible previously. Thus LSPosed now requires every module to be installed to the user on which the apps they want to hook are installed. Some devices restrict modules from installing onto some users. In such a case, you can install them from the manager (but it's not recommended). Notice that the module won't take extra space if you install it on different users: there will only be one apk.
   之前 LSPosed 仅识别安装在主用户的模块，该策略并非完美且导致诸多问题：一些模块需要获取安装应用列表以进行配置，但是该列表无法跨用户获取；一些模块需要从被注入应用获取本身，这样会在非主用户无法正常工作；一些用户希望分用户对模块进行配置，这也无法实现。于是，LSPosed 现在要求模块必须安装到对应用户上以注入到该用户上的应用。某些设备不允许模块安装到某些用户上，此时可以利用管理器安装（非万不得已时不推荐）。注意，安装在其他用户的模块不会占用额外空间：永远只有一个 apk。