-
Notifications
You must be signed in to change notification settings - Fork 386
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
Unable to load the superuser list 无法加载超级用户列表 #283
Comments
This is Kernel |
在通过 RootService 获取应用列表的时候直接触发 art 崩溃了,看起来是联想魔改了什么东西导致的。暂时的工作重心不会放在这里,但在未来的某一天里可能会修复。如果可以的话希望可以提供 /system/framework/framework.jar 和 /system/framework/services.jar |
感谢,我们会在有空的时候进行研究,到时候可能会有新版本让你帮忙测试 |
libsu uses Android's native IPC mechanism, binder, for communication between root service and the main application process. However, some OEMs' dirty hack of framework code made it unstable. Like #283, it made libart crash. No app loaded. Signed-off-by: GarfieldHan <[email protected]>
你好,非常感谢,我测试了下可以加载超级用户列表了,还测试了些其它功能,我发现 隐藏Apatch管理器 功能会闪退,无法成功隐藏,和安装magisk模块好像有问题。 |
libsu uses Android's native IPC mechanism, binder, for communication between root service and the main application process. However, some OEMs' dirty hack of framework code made it unstable. Like #283, it made libart crash. No app loaded. Signed-off-by: GarfieldHan <[email protected]>
因为是 topjohnwu 的 libsu 在 bind RootService 的时候出现的 library 崩溃,所以我换到了 pms 获取应用列表的方案,但是团队内部对于我的修改表示特别反对(据他们说是 至于隐藏 APatch Manager 功能闪退,关键日志如下:
不难看出你的系统实在是太糟糕了,目前暂时没有解决方案。 安装 APM 模块时出现 OS ERROR 22 是已知问题,不仅仅是你的系统你的设备出现了,后面会想办法修复,到时候可能还需要您的帮忙测试。 因为这个问题已经解决掉了,所以我将关闭这个 issue。关于安装 APM 模块时出现 OS ERROR 22,你可以再另行开一个 issue。 |
The issue seems to persist here. Also I can't export the logs to my storage |
But my issue seems different |
Do you have similar issue when using other root required app which is using We couldn't fix this since it was caused by topjohnwu's libsu. It would be better if you provide contexts to libsu's issue page. |
Ah yes. For example GMS Flags which uses libsu is unable to load any data. Should I open an issue on libsu repository is what you mean by providing context to libsu's issue page? |
|
I mean just open an issue on libsu instead. |
Yeah, I opened one yesterday waiting for a reply to it at the moment. What I find strange is that solutions like KernelSU doesn't have this issue. Are we sure there isn't something with the APatch implementation? |
Not even su in termux works, throws permission errors. Modules can't seem to install either. And I can't share the logs. I tried saving it with total commander and it complains that it can't open it for reading |
I've also opened an issue here regarding other problems I have: |
libsu uses Android's native IPC mechanism, binder, for communication between root service and the main application process. However, some OEMs' dirty hack of framework code made it unstable. Like bmax121#283, it made libart crash. No app loaded. Signed-off-by: GarfieldHan <[email protected]>
libsu uses Android's native IPC mechanism, binder, for communication between root service and the main application process. However, some OEMs' dirty hack of framework code made it unstable. Like bmax121#283, it made libart crash. No app loaded. Signed-off-by: GarfieldHan <[email protected]>
Please check before submitting an issue
Describe the bug
Unable to load the superuser list
Reproduce method
Unable to load the superuser list
Expected behavior
Unable to load the superuser list
Actual behaviour
Unable to load the superuser list
Screenshots
No response
Logs
APatch_bugreport_2024-03-11_09_06.tar.gz
Device Name
moto G51
OS Version
android 11
APatch Version
10533
Kernel Version
5.4.86
KernelPatch Version
0.10.3
Additional context
APatch_bugreport_2024-03-11_09_06.tar.gz
The text was updated successfully, but these errors were encountered: