Conversation
|
@AllenChangMusic @jiggs82 please test the lates CI of current branch to see if the support of Android 17 beta 3 is complete now. |
Vector release build still isn't working for me, on lsposed manager says it's not installed |
|
@jiggs82 Please provide logs by uploading the folder |
|
@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 :( |
|
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. |
|
When I use the release build, it crashes, but the debug build works fine. |
3611782 to
0da27d9
Compare
|
@jiggs82 @AllenChangMusic @mmmpipi Please also test the latest CI builds of current branch, before I finally merge it. |
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 |
|
@AllenChangMusic Please upload your debug version logs for the module not working. |
|
@JingMatrix I'm not seeing any specific crash log, but this CI causes IG to crash |
|
@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 |
Flashed latest build and all good here 👍🏻 |
|
@JingMatrix anything you need me to debug or send logs for to help troubleshoot why it's causing crashing? |
|
@AllenChangMusic I think it is a problem of the module. |
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!! |
|
@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.
|
it works fine! thanks |
|
@bikram-agarwal Please if the latest CI build from current pr works for you. |
No, modules tab is again blank when I flash this. |
Implement cli via socket
1. Keep a persistent database connection in PreferenceStore 2. Move class of core outside 3. Use a global coroutines scope in VectorDaemon
We can hand off to dbHelper once it is sure that system services are ready.
|
@CoelacanthusHex Thanks for continued testing, we do need users to test this build constantly. Please try out the latest CI build: https://github.com/JingMatrix/Vector/actions/runs/23792001714 |
Still broken. |
|
@CoelacanthusHex Please test again and upload logs: https://github.com/JingMatrix/Vector/actions/runs/23796827077 |
|
@JingMatrix I'm interested in helping test this PR and send logs but I want to ask this first. I'm currently on Vector 2.0 (3023, API version 100) and have 3 xposed modules: CorePatch, HMA, Revanced Xposed. Will these modules stop working once I install CI build which is using lsposed API 101? |
|
Users don't need to configure it all
|
@owocado all the three module are @CoelacanthusHex Please test CI build |
It is observed on Android 11, the SQLite engine attempts to read global configuration flags (sqlite_compatibility_wal_flags) from Settings.Global during the first database connection. In the daemon process—which is initialized via ActivityThread.systemMain() but not "attached" to the ActivityManagerService—this lookup triggers an IPC call that AMS rejects because the PID is not a registered application, resulting in a "SecurityException: Unable to find app for caller". This commit introduces a workaround that uses reflection to set: - sInitialized = true - sCallingGlobalSettings = true inside android.database.sqlite.SQLiteCompatibilityWalFlags. This forces the framework to skip the initialization logic, bypassing the crashing ContentResolver call and allowing the database to open with default configurations.



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.