Steps to reproduce/复现步骤
Neozygisk (v2.3-287) used together with Vector 2.0 (3023) does not work properly on Android 16 devices. In Magisk, NeoZygisk shows no abnormalities, but Vector crashes on launch with errors. After installing the manager APK, it reports that Vector is not installed. Vector only works if Magisk’s built-in Zygisk is enabled. However, the same configuration works normally on Android 12 devices.
Switching to the forked version of NeoZygisk resolves the issue:
[https://github.com/HSSkyBoy/NeoZygisk/actions/runs/22952594887]
Expected behaviour/预期行为
NeoZygisk works normally when used together with Vector 2.0.
Actual behaviour/实际行为
Vector 2.0 fails to start properly.
Root implementation/Root 方案
Magisk
System Module List/系统模块列表
NeoZygisk
Vector
Scene
爱玩机工具箱
音量键急速救砖
NeoZygisk version/NeoZygisk 版本
NeoZygisk-v2.3-287-f2beaea
Android version/Android 版本
Android16
Version requirement/版本要求
Logs/日志
Using ChatGPT to analyze the Magisk logs shows:
“Zygisk + modules are incompatible on Android 15 (API 36) → causing zygote restarts → abnormal Activity startup → Intent falls back to system handler.”
How can I provide more detailed logs to help you better identify the issue?
:Magisk 30.7(30700) daemon started I:* Device API level:36 ** post-fs-data mode running I :* Initializing Magisk environment 2 I :* Running post-fs-data.d scripts 2 I: zygisk_vector: ignore * Running module post-fs-data scripts 6 I:zygisksu: exec [post-fs-data.sh] 61 scene_systemless: exec [post-fs-data.sh] WorkSettingPro: exec [post-fs-data.sh] zygisk_vector: ignore : scene_systemless: loading module files :bind_mount '/product/bin/init.qti.display.sh' remount '/debug_ramdisk/.magisk/worker/product/ ** late_start service mode running * Running service.d scripts * Running module service scripts zygisksu: exec [service.sh] scene_systemless: exec [service.sh] workSettingPro: exec [service.sh] RescueBrick: exec [service.sh] ** zygote restarted ** ** zygote restarted zygote restarted ** boot-complete triggered ：* Found preinit dir: /metadata/watchdog/magisk
Steps to reproduce/复现步骤
Neozygisk (v2.3-287) used together with Vector 2.0 (3023) does not work properly on Android 16 devices. In Magisk, NeoZygisk shows no abnormalities, but Vector crashes on launch with errors. After installing the manager APK, it reports that Vector is not installed. Vector only works if Magisk’s built-in Zygisk is enabled. However, the same configuration works normally on Android 12 devices.
Switching to the forked version of NeoZygisk resolves the issue:
[https://github.com/HSSkyBoy/NeoZygisk/actions/runs/22952594887]
Expected behaviour/预期行为
NeoZygisk works normally when used together with Vector 2.0.
Actual behaviour/实际行为
Vector 2.0 fails to start properly.
Root implementation/Root 方案
Magisk
System Module List/系统模块列表
NeoZygisk version/NeoZygisk 版本
NeoZygisk-v2.3-287-f2beaea
Android version/Android 版本
Android16
Version requirement/版本要求
Logs/日志
Using ChatGPT to analyze the Magisk logs shows:
“Zygisk + modules are incompatible on Android 15 (API 36) → causing zygote restarts → abnormal Activity startup → Intent falls back to system handler.”
How can I provide more detailed logs to help you better identify the issue?
:Magisk 30.7(30700) daemon started I:* Device API level:36 ** post-fs-data mode running I :* Initializing Magisk environment 2 I :* Running post-fs-data.d scripts 2 I: zygisk_vector: ignore * Running module post-fs-data scripts 6 I:zygisksu: exec [post-fs-data.sh] 61 scene_systemless: exec [post-fs-data.sh] WorkSettingPro: exec [post-fs-data.sh] zygisk_vector: ignore : scene_systemless: loading module files :bind_mount '/product/bin/init.qti.display.sh' remount '/debug_ramdisk/.magisk/worker/product/ ** late_start service mode running * Running service.d scripts * Running module service scripts zygisksu: exec [service.sh] scene_systemless: exec [service.sh] workSettingPro: exec [service.sh] RescueBrick: exec [service.sh] ** zygote restarted ** ** zygote restarted zygote restarted ** boot-complete triggered ：* Found preinit dir: /metadata/watchdog/magisk