Latest version of HMA does not work with Vector

[bege10]

Is your feature request related to a problem?/你的请求是否与某个问题相关？

HMA v3.8 crashes with Vector.

Describe the solution you'd like/描述你想要的解决方案

In the issue I created in the HMA repo Dr-TSNG/Hide-My-Applist#363 (comment) I was told that Vector misses a feature to run new HMA versions. Can that feature be added to Vector?

Additional context/其他信息

No response

[xenouch]

Use HMA-OSS, work fine !

[Keeperorowner]

It's time to throw the closed-source hma in the trash and use the oss version.

[duanluan]

I can reproduce the HMA v3.8 native-library loading failure mentioned in this issue. HMA-OSS seems to work, so I understand that using HMA-OSS may be the recommended workaround. I am adding the details here in case this helps clarify the Vector-side behavior with HMA v3.8.

Environment

• Device: OnePlus PJD110
• Android: 16 / SDK 36
• Root: APatch
  • APatch versionName: 166daa0
  • APatch versionCode: 11142
• Zygisk implementation: Zygisk Next
  • 1.3.4 (746-d1b76b3-release)
• Vector module:
  • zygisk_vector
  • v2.0 (3043)
• Vector Manager:
  • package: org.lsposed.manager
  • versionName: 2.0
  • versionCode: 3043
• HMA:
  • package: com.tsng.hidemyapplist
  • version: 3.8.r499.3a346c0
  • versionCode: 499
• ABI: arm64-v8a

What happens

HMA v3.8 shows that the system service is not running.

Vector does load HMA into system_server, but HMA fails when loading its native library:

Loading legacy module com.tsng.hidemyapplist from /data/app/.../com.tsng.hidemyapplist.../base.apk
Loading class icu.nullptr.hidemyapplist.xposed.XposedEntry

java.lang.UnsatisfiedLinkError: dlopen failed: couldn't map "/data/app/.../com.tsng.hidemyapplist.../base.apk!/lib/arm64-v8a/libhmahook.so" segment 2: Permission denied

HMA v3.8 release notes say:

From this version onward, the framework implementation must allow native libraries to be loaded within system services; otherwise, the module will not work.

So this appears to be the native library loading requirement added by HMA v3.8.

HMA-OSS

I understand from the comments above that HMA-OSS is recommended and appears to work. I am fine with using HMA-OSS as the practical workaround.

Extra comparison test

As a temporary local comparison test, I built a Java-only APK based on the public HMA source.

The test commit is here:

duanluan/Hide-My-Applist@95c2b23

The APK was built with:

versionCode=500
versionName=3.8-no-native.r1.bd5466b

After installing that build and rebooting, HMA starts successfully:

HMA-XposedEntry: Hook entry
HMA-UserService: Initialize HMAService - Version 101
HMA-Service: Hooks installed
HMA-Service: HMA service initialized
HMA-XposedEntry: User service started
HMA-UserService: Send binder to app
HMA-Service: Config synced

This is not a proper HMA v3.8 fix. It is only a comparison test showing that the failing part is HMA v3.8 loading libhmahook.so inside system_server.

Question

Is support for HMA v3.8 native library loading inside system_server expected to be supported by Vector?