Module toggles are grayed out, no action available in modules, and granted su privileges reset after a reboot

[biggsx]

Please check before submitting an issue | 在提交 Issue 前请检查

• I searched the issues and didn't found anything relevant | 我已经搜索了 Issues 列表，没有发现于本问题相关内容
• If the patch fails or the image cannot be booted after flashing the new boot.img, visit KernelPatch to clarify your doubts | 修复失败或刷入修补后镜像不能启动，请前往 KernelPatch 提问
• I will upload the bug report file in APatch Manager > Settings > Send logs | 我会上传 Bug Report 文件从 APatch 管理器 > 设置 > 发送日志
• I know how to reproduce the issue, which might not be specific to my device | 我知道如何重新复现这个问题

Version requirements | 版本要求

• I'm using the latest CI version of APatch Manager | 我正在使用最新 CI 版本

Bug description | 描述 Bug

As described in title.
I loaded in modules on the APModule tab in the manager, and they appear uninteractable besides the trash/delete button. There aren't any other buttons available.
As for the su privileges issue, all the toggles on the Superuser tab get reset after a reboot, even though the apps granted su actually have su before rebooting.

Reproduce method | 复现方法

APatch was installed and flashed successfully using the fastboot method described on the documentation site. This was done using the manager version v11142, lastest release at this time, then manager was updated using the apk of version 11183 obtained from this github, and I updated KernelPatch and AndroidPatch through the updated manager.

Expected behavior | 预期行为

The expected behavior is being able to interact with the modules in the APManager tab, like having their action buttons available, and for the Superuser tab to remember which apps were granted su.

Actual behavior | 实际行为

Toggles are grayed out and uninteractable.
Toggles in the Superuser tab are reset and apps lose su.

Screenshots | 截图

Logs | 日志

APatch_bugreport_2026-02-04_23_28.tar.gz

Device name | 设备名称

Nothing Phone 3a, model A059

OS version | 系统版本

LineageOS 23, Android 16

APatch version | APatch 版本

11183

Kernel version | 内核版本

6.6.114-android15-8-4k-g5c93c919cca4

KernelPatch version | KernelPatch 版本

0.13.0

Other information | 其他信息

This issue has my same issues, however is marked as completed (and fixed?) yet the issue persists.

[Admirepowered]

Is the super user effective? If it is confirmed that the super user is effective, we will fix it later. If the super user is not effective, remote debugging may be required

[biggsx]

If by effective, you mean that superuser is granted successfully by the toggles in the Superuser tab, then yes, su is effective. I can confirm this because granting Shizuku su privileges lets it start successfully. The issue is that these privileges are revoked upon a reboot, and I need to go back to the Superuser tab and regrant them.

[mrsrimar22]

same thing happened to me, AP not installed notification appeared, module toggles were greyed out and su list didn't shown properly after boot, but su is effective and this problem disappeared after closing and then reopening the manager, log looks normal in kmsg and logcat, apatch ver 11186 last main CI build

[Admirepowered]

https://github.com/Admirepowered/APatch/actions/runs/21983807093 try this and upload log