Refactor framework daemon to Kotlin - #597
Merged
Merged
Conversation
JingMatrix
marked this pull request as ready for review
March 26, 2026 18:43
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@AllenChangMusic@jiggs82 please test the lates CI of current branch to see if the support of Android 17 beta 3 is complete now. |
jiggs82
commented
Mar 27, 2026
Vector release build still isn't working for me, on lsposed manager says it's not installed |
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@jiggs82 Please provide logs by uploading the folder |
jiggs82
commented
Mar 27, 2026
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@jiggs82 It seems that Vector CI build is not flashed correctly. |
@JingMatrix debug build works, but release build does not Also... Looks like Vector has issues enabling new modules. And if you uninstall it, and reinstall, you aren't able to enable any modules. May be related to the report in the other thread where it isn't able to create the lspd folder |
Still same issues and yes now I encounter that :( |
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
There are bugs in the refactoring, hence I create pr #603 to fix the issue for the java code before refactoring, to help isolated issues. |
mmmpipi
commented
Mar 27, 2026
When I use the release build, it crashes, but the debug build works fine. |
JingMatrixforce-pushed
the
refactor
branch
2 times, most recently
from
March 27, 2026 15:56
3611782 to
0da27d9CompareJingMatrix
commented
Mar 27, 2026
OwnerAuthor
@jiggs82@AllenChangMusic@mmmpipi Please also test the latest CI builds of current branch, before I finally merge it. |
AllenChangMusic
commented
Mar 27, 2026
Tested and one module - InstaEclipse doesn't work in this version, but did in the previous CI. One thing to note is in LSPosed manager, it keeps complaining there's an update, but it's the old pre-vector version |
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@AllenChangMusic Please upload your debug version logs for the module not working. |
AllenChangMusic
commented
Mar 27, 2026
@JingMatrix I'm not seeing any specific crash log, but this CI causes IG to crash |
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@AllenChangMusic I see logs of containing |
Instagram app just crashes, won't even open. Compared to the previous CI, it opens fine, and you can open the InstaEclipse settings (long holding the search icon in the instagram app), and use the app just fine |
jiggs82
commented
Mar 27, 2026
Flashed latest build and all good here 👍🏻 |
AllenChangMusic
commented
Mar 27, 2026
@JingMatrix anything you need me to debug or send logs for to help troubleshoot why it's causing crashing? |
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@AllenChangMusic I think it is a problem of the module. |
ReSo7200
commented
Mar 27, 2026
Hi, I am the dev of InstaEclipse, this issue was fixed with InstaEclipse 0.5 debug, the user is using it. I will check myself... Thanks for the great LSPosed/LSPatch!! |
JingMatrix
commented
Mar 27, 2026
OwnerAuthor
@ReSo7200 Nice to hear from you, and it is my pleasure to serve the community. Please do tell me if current refactoring (this pr) is causing issues for your module. I will wait for your test result before merging this. |
@ReSo7200 Looking through logcat, seeing these 3 errors consistently popping up, not sure if it's related to the hooking.    |
mmmpipi
commented
Mar 28, 2026
it works fine! thanks |
JingMatrix
commented
Mar 28, 2026
OwnerAuthor
@bikram-agarwal Please if the latest CI build from current pr works for you. |
bikram-agarwal
commented
Mar 28, 2026
No, modules tab is again blank when I flash this. |
CorePath check both of them before injecting. Moreover, we fix a compilation waring of null string.
JingMatrix
commented
Apr 4, 2026
OwnerAuthor
@Dev4Mod and @huynhbaman, thank you for finding out this bug, it is fixed now. |
@huynhbaman LGTM Both legacy and 101's modules are working Here are some logs if needed |
Uh oh!
There was an error while loading. Please reload this page.
Things22
commented
Apr 6, 2026
hi @JingMatrix |
This was referenced Apr 7, 2026
JingMatrix added a commit
that referenced
this pull request
Apr 14, 2026
Modules such as `io.github.mhmrdd.libxposed.ps.passit` [PlayStrong](https://t.me/meetstrong/125) call methods with `libxposed` API signatures via JNI during its initialization, which is bounded to fail if dex obfuscation is always enabled. Vector has removed the user configuration of `Xposed API Protection` (toggling the dex obfuscation option) during its daemon refactoring in #597, for the reason that this option is too technical for most users. Ideally, module developers should extend their module compatibility with dex obfuscation mode, by for example, inheriting Xposed APIs. In any case, we now disable dex obfuscation for debug builds, so that Vector users could test out these modules. P.S.: strong integrity is obtained on my local test with community shared RKA token.
JingMatrix added a commit
that referenced
this pull request
Apr 17, 2026
During the previous refactor #597, we forget to implement the `auto_include` feature.
JingMatrix added a commit
that referenced
this pull request
Apr 20, 2026
During the previous refactor #597, we forget to implement the `auto_include` feature.
JingMatrix added a commit
that referenced
this pull request
Apr 21, 2026
Modules such as `io.github.mhmrdd.libxposed.ps.passit` [PlayStrong](https://t.me/meetstrong/125) call methods with `libxposed` API signatures via JNI during its initialization, which is bounded to fail if dex obfuscation is always enabled. Vector has removed the user configuration of `Xposed API Protection` (toggling the dex obfuscation option) during its daemon refactoring in #597, for the reason that this option is too technical for most users. Ideally, module developers should extend their module compatibility with dex obfuscation mode, by for example, inheriting Xposed APIs. In any case, we now disable dex obfuscation for debug builds, so that Vector users could test out these modules.
Enovale pushed a commit
to Enovale/Vector
that referenced
this pull request
Jul 13, 2026
We rewrite the Vector daemon from Java to Kotlin using a modular design as specified in the daemon README. This transition improves code maintainability and modernizes the codebase. We note below several behavior changes in this refactor. Bug Fixes and Improvements: - Directory Permissions: Correctly configured for XSharedPreference storage. - Database Management: Migrated to Android DatabaseHelper for better versioning and automatic migration from LSPosed database (`v101`). - CLI Tool: Added a command-line interface at `/data/adb/lspd/cli` for managing modules and scopes. Removed Features: - Denylist Filtering: Removed UI warnings for denylist apps, as the Vector functions independently of them. - In-app Updates: UI-based updates removed in favor of root-level manager updates (e.g., Magisk/KernelSU). - Logcat Watchdog: Removed due to lack of practical utility from previous debugging experiences. - Obfuscation Toggle: Xposed API obfuscation is now permanently enabled, while it remains configurable via `DaemonState` at compile-time.
Enovale pushed a commit
to Enovale/Vector
that referenced
this pull request
Jul 13, 2026
During the previous refactor JingMatrix#597, we forget to implement the `auto_include` feature.
Enovale pushed a commit
to Enovale/Vector
that referenced
this pull request
Jul 13, 2026
Modules such as `io.github.mhmrdd.libxposed.ps.passit` [PlayStrong](https://t.me/meetstrong/125) call methods with `libxposed` API signatures via JNI during its initialization, which is bounded to fail if dex obfuscation is always enabled. Vector has removed the user configuration of `Xposed API Protection` (toggling the dex obfuscation option) during its daemon refactoring in JingMatrix#597, for the reason that this option is too technical for most users. Ideally, module developers should extend their module compatibility with dex obfuscation mode, by for example, inheriting Xposed APIs. In any case, we now disable dex obfuscation for debug builds, so that Vector users could test out these modules.
JingMatrix added a commit
that referenced
this pull request
Jul 30, 2026
…om (#809) Flash Vector, open it from the root manager, close it, and there is no way back in. The dialer code registered a filter with no action, which matches nothing, so that branch has been dead since #597; it works again and is rebound to 832867, VECTOR on the keypad. Parasitically the manager is not installed, so the launcher has nothing to show either: the pinned shortcut and the standalone install that #796 dropped return, in an "Opening Vector" section and a first-launch prompt, with `getManagerApk()` handing over the APK the host cannot read. Sixteen new strings, translated into all eighteen languages. The version string now names where a build came from rather than calling every canary "dirty", which it did only because the workflow writes signing credentials into the tracked `gradle.properties`. Repository and commit both come from the pull request's head, since GitHub's defaults describe the run and not the code. Closes#815.
JingMatrix added a commit
that referenced
this pull request
Aug 6, 2026
#882) Constructing a Notification on Android 16 reads an aconfig flag of the systemui container, and the daemon cannot serve that read: it holds an ActivityThread but no application record, so the settings provider is refused it and the constructor throws SecurityException. Setting systemui_is_cached before the first read leaves the flags at their compiled defaults and removes the read. That bypass was gated on SDK_INT >= VANILLA_ICE_CREAM, wider than the release it belongs to, because Xiaomi shipped the change on Android 15 without the SDK level; #96 was such a device, four days before Android 16 DP1 was published. #597 rewrote the test as SDK_INT == 36 and lost that case, which #880 now reports on the same vendor and the same version. Android 17 sets those fields unconditionally, so the test spans 35 to 36, the versions in which the field can exist.
JingMatrix added a commit
that referenced
this pull request
Aug 7, 2026
Handing a module app its `IXposedService` means starting it: the daemon acquires the module's own `XposedService` provider, which brings the process up, and passes the binder in the reply. That reference was never released, and the platform reads an outstanding external reference as a live client — so `OomAdjuster` held every module app at `FOREGROUND_APP_ADJ` with adj type `ext-provider`, never cached, and a host dying while its provider was still launching was restarted for it. The platform bounds those restarts at three per provider record; acquiring again rebuilds the record with the count at zero, which is how #889 reached fourteen process starts in seventy-six seconds, six of them ours. The release has to be unconditional, because the two returns that matter come back null with the reference already registered. Three consequences of the same path. The delivery no longer runs on the uid observer, where one module delayed every other module's binder by eight seconds. A failed send is no longer recorded as a delivered one, and repeated failures are throttled to one attempt a minute rather than one a second. And a delivery is recorded per process rather than per uid — a uid outlives any one of its processes, so the record could otherwise never clear. Separately, `getContentProviderExternal` gained its `tag` argument in Q by replacing the three-argument form, so the unconditional four-argument call has meant no module received its app-side service on 8.1 or 9 since #597. And the `IUidObserver` stub declared four of the interface's eight methods; the rest stayed abstract at runtime, which `oneway` makes fatal rather than reportable. Module apps are no longer immortal, so a scope answer arriving an hour later may find the app gone. The grant itself is written before the callback.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
13 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR transitions the framework daemon from legacy Java to a modernized Kotlin implementation, rebranded as
Vector. The refactor moves beyond a literal translation to implement a more robust, domain-driven architecture.See REAMDE in module
daemonfor more implementation details.