Integrity drop to basic when GMS is excluded.

[VisionR1]

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

• [x] I searched the issues and didn't found anything relevant | 我已经搜索了 Issues 列表，没有发现于本问题相关内容
• [x] If the patch fails or the image cannot be booted after flashing the new boot.img, visit KernelPatch to clarify your doubts | 修复失败或刷入修补后镜像不能启动，请前往 KernelPatch 提问
• [x] 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 | 版本要求

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

Bug description | 描述 Bug

So, little of my experience with APatch. If you get 3/3 and you put the GMS in exclude, the integrity down to basic. Only with PIFork with a FP, can working full.

Any modules which replace or delete systemless, again failed integrity (without GMS in exclude 3 red, with basic). Solution again the PIFork with a FP.

Example the bindhosts, if you have it without this, the integrity failed.

So, a possibility for integrity drop to basic when add the GMS to exclude, is because reverse all changes made it by module, like Tricky Store etc.

The Magisk can hide if want only the process gms.unstable.

I think a file for only GMS like .lite_mode (example .skip_exclude), need it to put it in module folder and skip the exclude.

Reproduce method | 复现方法

Superuser and excluded the GMS

Expected behavior | 预期行为

Not cause the integrity fail.

Actual behavior | 实际行为

The integrity fail when the GMS is in excluded.

Screenshots | 截图

No response

Logs | 日志

No response

Device name | 设备名称

Xiaomi POCO X3 NFC

OS version | 系统版本

11

APatch version | APatch 版本

11107

Kernel version | 内核版本

4.14.180-perf-gae096ac9215c

KernelPatch version | KernelPatch 版本

0.12.0

Other information | 其他信息

All the info is simple and above.