V3.1.0-Beta

Fix bugs
Reduce logs when detail logs off
Support system data isolation manage
Don't need to reload config every time when upgrading system service version
Known issues: On some A13 devices, the app may show system service not running after booted sometime, but hide will still work. If changed some config, you need to open app as soon as booted to sync config. We are still investigating this bug.

修复 bug
减少未开启详细日志时的日志记录
支持修改系统数据隔离设置
系统服务版本更新后不再需要每次重载配置
已知问题：在一些安卓 13 的设备中，开机一段时间后 app 可能显示系统服务未运行，但隐藏功能实际是工作的。如果修改了配置，需要重启后尽快打开一次 app 来同步。目前原因正在调查中

App data isolation prevents detection from /data/data/pkg
Vold app data isolation prevents detection from /sdcard/Android/data/pkg

Both require Android 11 and above

V3.1.1
Fix bugs
Reduce logs when detail logs off
Support system data isolation manage
Don't need to reload config every time when upgrading system service version
Fix system service not running on some A13 devices

修复 bug
减少未开启详细日志时的日志记录
支持修改系统数据隔离设置
系统服务版本更新后不再需要每次重载配置
修复在一些 Android 13 手机上系统服务未运行的问题

V3.2
Fix crash on Android 14
Prevent a detection from system service
Update translations

修复 Android 14 上闪退
避免一个系统服务的检测
更新翻译

V3.3
Support Android 15
Fix possible crash because of Data Isolation
Improve compatibility

支持 Android 15
修复 Data Isolation 功能可能造成的闪退
增强兼容性

V3.3.1
Improve compatibility
Migrated data storage to resolve issue with some roms which allow ls /data/system

增强兼容性
迁移数据目录位置，以解决部分 rom 允许 ls /data/system 的问题

V3.4
Remove support for Android 9-
Workaround a package visibility gap in A15
Add a warning dialog for vold app data isolation

移除对 Android 8.1 及更低版本的支持
变通处理一个 Android 15 上的包可见性问题
增加了 vold app 数据隔离警告对话框

V3.5
Address startActivity() exploit below A13
Rework hook for getArchivedPackage()
Improve logging performance

处理低于 A13 的 startActivity() 漏洞
重写 getArchivedPackage() 漏洞修复
提升日志性能

BTW: All ads removed
另外，移除了所有广告

V3.6
Implement aggressive intent filter
Fix a few UI bugs

实现激进的意图过滤器
修复一些界面问题

V3.6.1

Always enable ActivityStarter hook
Support edge-to-edge
Fix minor issues

永远启用 ActivityStarter 钩子
支持边到边
修复一些小问题

经研究，某些加固（如 Protectt.ai）通过直接启动对应应用主界面（如 KernelSU 管理器）的方式进行检测。由于直接启动活动并不在软件包可见性的限制范围内，用户需要手动启用激进的意图过滤器，HMA 才能拦截。之前我认为这种方式会破坏用户体验，因此加固不会使用，看来我高估它们的底线了。

举个例子说明为什么默认不启用该功能：如果用户对京东启用了白名单，且未将微信加入可见应用列表，则若未开启激进的意图过滤器，京东是可以直接拉起微信支付的；若开启了激进的意图过滤器，京东则无法拉起微信。因此，建议用户在任何时候都只使用黑名单模式。

此外，AOSP 仍存在大量软件包可见性问题（如我们昨天发现，通过传递错误的 display id 可以在不启动应用的情况下探测软件包存在性），考虑到谷歌认为非跨用户的软件包可见性问题均为低危，在可预计的将来，HMA 将仍是必需品。

—————————————

Research has shown that certain app protections (such as Protectt.ai) detect application existence by directly launching the target app’s main activity (for example, the KernelSU Manager). Since directly starting an activity is not restricted by the app visibility limitations, users need to manually enable the aggressive intent filter to intercept it. I previously thought this approach would harm user experience, so protections wouldn’t use it—but it seems I overestimated their restraint.

Here’s why this feature is not enabled by default: for example, if a user has used whitelist mode on JD (Jingdong) but has not added WeChat to the list of visible apps, if the aggressive intent filter is off, JD can still directly launch WeChat. If the aggressive intent filter is on, JD cannot launch WeChat. Therefore, it is recommended that users always use blacklist mode only.

In addition, AOSP still has numerous package visibility issues (for example, as we discovered yesterday, it is possible to know the existence of a package without launching the app by passing an invalid display ID). Considering that Google regards non-cross-user package visibility issues as low risk, HMA will remain essential for the foreseeable future.