-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
模块列表重启自动消失 #2520
Comments
补充一下:关闭默认卸载模块可以正常显示,但是之前是打开默认卸载模块是没问题的 |
看日志是ksu的loop设备被某个进程在全局命名空间umount了,请安装debug版ksu然后抓日志 |
log.zip |
在hyperos 2.0.200.4beta更新后,经过同样步骤,已经无法复现该问题,同时测试开启默认卸载模块后,不会出现模块列表为空的问题。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please check before submitting an issue
Describe the bug
近日在某次澎湃系统更新后,
或者某个模块更新后,ksu内的模块列表消失重装ksu排查:安装任意模块都会触发这个问题,使用alpha面具测试不触发模块列表消失
To Reproduce
安装ksu并修补后,不做任何操作立即安装任意模块,重启,模块列表消失,查看/data/adb/modules发现目录为空,可以正常安装新的模块,安装的模块有效
Expected behavior
No response
Screenshots
No response
Logs
日志一:KernelSU_bugreport_2025-03-21_17_49.tar.gz
重启前做了以下操作:安装asoulopt模块
日志中包含了以下操作:安装asoulopt模块,卸载asoulopt模块,安装zygisknext模块
Device info
MarketName = Xiaomi 14 Pro
DeviceName = shennong
Model = 23116PN5BC
Brand = Xiaomi
Manufacture = Xiaomi
Board = shennong
Soc = SM8650
ModDevice = shennong
Characteristics = nosdcard
Pad = false
Large Screen = false
FingerPrint = Xiaomi/shennong/shennong:15/AQ3A.240627.003/OS2.0.106.4.VNBCNXM:user/release-keys
Locale = zh-CN
Language = zh_CN
AndroidId = 6afcbf66c806d63f
DeviceToken = 379F1918D733EA89308010BC6D568FE298159393
AndroidSdkVersion = 35
HyperOsVersion = 2.0
SystemVersion = OS2.0.106.4.VNBCNXM
InternationalBuild = false
BaseOs = null
Host = pangu-build-component-system-525129-lq9dl-cnbpl-c0d62
BuildDate = Fri Mar 7 23:19:18 CST 2025
Signature = 46:4C:5C:9D:A2:8C:AE:E6:B3:28:8D:AE:13:2C:A3:6D:52:A1:64:89:E0:95:CF:7B:52:AC:A7:11:F0:93:82:3C
SignCheckPass = true
KernelSU version: 12018 (kernel) + 12018 (ksud)
内核版本:6.1.75-android14-11-gd57efa708101-ab12102151
Additional context
No response
The text was updated successfully, but these errors were encountered: