## Unable to trigger parasitic notification on Android 15 Xiaomi HyperOS, Vector 2.2 cannot request module scope inside its own app

[oneroomlife]

Environment

• Device: Xiaomi device
• ROM: Xiaomi HyperOS (Android 15)
• Android version: 15
• Vector version: 2.2
• Root solution: (Magisk)
• Zygisk implementation: (Neozygisk)

Problem description

After installing Vector 2.2 on a Xiaomi device running HyperOS based on Android 15, the parasitic notification cannot be displayed or triggered.

Because the parasitic notification does not appear, the module cannot directly open Vector's scope management page from inside its own app, and users cannot request module scope normally through the app.

However, the same module and configuration work correctly in the following environments:

• Android 16 on Xiaomi devices ✅
• Android 15 emulator ✅

The problem only happens on:

• Xiaomi HyperOS
• Android 15
• Vector 2.2

Steps to reproduce

1. Install Vector 2.2 through Magisk/KernelSU.
2. Enable Zygisk.
3. Install an Xposed module that supports requesting scope from its own app.
4. Open the module application.
5. Try to request Vector scope.
6. The app cannot launch Vector scope management because the parasitic notification is unavailable.

Expected behavior

The parasitic notification should appear normally, and the module should be able to open Vector's scope request interface from its own application.

Actual behavior

• No parasitic notification appears.
• The module cannot request scope automatically.
• No Vector management notification is shown in the notification panel.

Additional information

The issue seems to be related specifically to Xiaomi HyperOS Android 15.

Since it works on:

• Android 15 AOSP emulator
• Android 16 Xiaomi device

I suspect there may be some compatibility issue with HyperOS Android 15 notification handling, background restrictions, or system-level notification behavior.

Questions

1. Is this a known compatibility issue between Vector 2.2 and Xiaomi HyperOS Android 15?
2. Does HyperOS require additional permissions or settings to allow Vector's parasitic notification?
3. Are there any logs or debugging methods I can provide to help locate the problem?
4. Is there any workaround to manually enable the scope request function without relying on the parasitic notification?

Thanks for your work on Vector. I would appreciate any guidance on how to debug or fix this issue.