-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
安装/更新模块重启会导致解锁时重启 #2537
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
Comments
04-08 09:18:15.966 8743 8743 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 8743 (apexd), pid 8743 (apexd) 怀疑是对loop设备的处理影响到了apexd。建议在post-fs-data阶段setenforce 0然后抓日志。 |
我在post-fs-data修补过/apex(但是变更的模块并不包含修补/apex也会触发这个问题),我去掉看看 |
log.zip |
所以去掉可以吗 |
没什么用,得先想办法把apexd的tombstone记录下来 |
是的,去掉之后确实不会在出现解锁重启了。 |
好奇怪,我又重新把修改/apex的模块放上去但是又没有触发这个问题,懵逼了,我再看看 |
是这个么,这两个文件的最后修改时间就是这条日志的09:18 我改动过的是/apex/com.android.permission和/apex/com.android.wifi |
不是这个 |
是这个么,在/data/tombstones目录下面的Process name is /system/bin/apexd, uid is 0, not key_process |
Please check before submitting an issue
Describe the bug
安装模块->点击重启->在锁屏界面等待不会重启->解锁立即黑->循环,只要解锁就重启
解锁后重启前adb logcat日志
log.txt
在重启时按三下音量-尝试进入安全模式,此时候可以成功解锁进入系统,但是kernelsu并没有进入安全模式,模块也正常更新了,一切正常。
To Reproduce
No response
Expected behavior
No response
Screenshots
No response
Logs
No response
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: