system_server hook performance

[mark99i]

Hello everyone!

I am developing an application and a set of hooks (more than 50 logical classes, each containing 1–4 hooks) on legacy Xposed API for a specific platform of a car’s head unit (Geely Ecarx E02 based on Helio P60, Android 9, API 28, Magisk 25.2/30.7 installed)

First, I used LSPosed 1.9.2 with the built‑in Magisk Zygisk (this is currently the “official” supported way to run my app), then I installed NeoZygisk 2.4 + Vector 2.2 for testing.

I’m encountering the same problem: when I enable zygisk+lsposed, the device starts taking longer to boot, and when I include my app in lsposed score system_server, even if no hooks are set in handleLoadPackage on android/system_server, the device takes noticeably longer to boot during the boot animation stage + the first launcher launch (about 3–4 seconds, while the total boot time is about 15–20 seconds before the launcher)..
What could be the problem, and how can this be debugged? Or is this the expected behavior on this old platform?
I can share the logcat -b all files immediately after loading, with the app enabled in score and with it disabled.

For the most part, my hooks are set up on the slow-path and are triggered under certain circumstances (for example, when the user switches the driving mode on their car). Will migrating to API 102 give me any noticeable advantages? I read the changelog, and some features are completely absent there — for example, resource hooks. I’m not interested in new features like hot restart (yes, it will be a bit more convenient for debugging, but that’s it).
Also, I’ll have to release a video showing users how to install the new version of the lsposed engine.

[JingMatrix]

Flash latest CI debug builds of NeoZygisk and Vector, then upload logs exported by Vector manager.

[mark99i]

Flash latest CI debug builds of NeoZygisk and Vector, then upload logs exported by Vector manager.

I’ll be able to do this in a few days.
So far, I’ve recorded 2 logs, and if we trust the AI, 1.6 seconds are spent loading the dex app in system_server, and roughly the same amount of time is spent on createSystemContext() due to the enabled resource hooks. I’ll disable the resource hooks (convert them to regular ones) and check whether anything has changed.

Thanks for the answer.
In version 2.0, one of the testers tried Vector on this platform and encountered device freezing issues. I will install the latest CI debug builds and test them on my own device to identify the problem if it persists.

[mark99i]

Hi @JingMatrix
here log of booting with vector canary debug & neozygisk debug with enabled hooks (hooks package ru.mark99.carapp)
e02-starting-vector-debug.log
could you please check if there’s anything interesting here?
sorry for comment update