Vector daemon crashes with DeadSystemException (BR_DEAD_REPLY)

Steps to reproduce/复现步骤

1. Flash KernelSU-Next (tethered/temporal root, bootloader locked) + Zygisk Next 1.4.5 + Vector canary-3107 on the device below.
2. Soft reboot.

Expected behaviour/预期行为

VectorDaemon starts and establishes bridge into system_server

Actual behaviour/实际行为

VectorDaemon crashes with an uncaught DeadSystemException during a subset of boots, immediately after a libbinder transaction returns BR_DEAD_REPLY. Full sequence from verbose log:

10:43:07.246 E/SystemServiceRegistry: SemDisplayQualityFeature.ENABLED:true,PLATFORM:LSI
10:43:07.249 D/ShellFrameworkInitializer: initial SemPrivilegeManager
10:43:07.250 E/libbinder.IPCThreadState: Binder transaction failure. id: 606305, cmd: BR_DEAD_REPLY (29189), error: -3 (No such process)
10:43:07.250 W/libbinder.IPCThreadState: call to talkWithDriver in joinThreadPool returned error: -9 (Bad file descriptor), FD: -1
10:43:07.251 D/AndroidRuntime: Shutting down VM
10:43:07.251 E/AndroidRuntime: FATAL EXCEPTION: main
DeadSystemException: The system died; earlier logs will point to the root cause
10:43:07.251 E/VectorDaemon: Uncaught exception in Daemon
DeadSystemException: The system died; earlier logs will point to the root cause

DeadSystemException carries no further stack trace, only that some binder call the daemon made during this window came back dead.

Corresponding kmsg from the same boot:
[ 356.172023] !@Boot_EBS_F: start zygote from appmain
[ 356.1xx-356.3xx] init: Untracked pid received SIGKILL (repeated ~50x)
[ 356.302643] servicemanager: Service 'serial' originally registered from SID u:r:system_server:s0 but it is now being registered from SID u:r:ksu:s0. Multiple instances installed?

Xposed Module List/Xposed 模块列表

Crash occurs during daemon startup before any Xposed module can be scoped/loaded

Root implementation/Root 方案

Temporal root - Root my galaxy (CVE-2026-43499)

System Module List/系统模块列表

Zygisk Next 1.4.5 (836-b13d58a-release)
Vector canary-3107

Vector version/Vector 版本

canary-3107

Android version/Android 版本

Android 16 (API 36), Samsung Galaxy S24 (SM-S921B, Exynos 9945), firmware S921BXXSFDZF2, kernel 6.1.157-android14-11, stock OEM ROM (One UI)

Version requirement/版本要求

• I am using the latest debug build from GitHub Actions./我正在使用 GitHub Actions 中最新的调试版本。

Logs/日志

vector-deadsystemexception-issue.md

Start with the attached vector-deadsystemexception-issue.md and reproduce the soft reboot on the listed Android 16 device and module versions. Trace VectorDaemon startup around the BR_DEAD_REPLY and DeadSystemException; done means the daemon no longer crashes during the affected boots and establishes its bridge into system_server.