-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Find out the commits that failed CorePatch #39
Conversation
Requested by #14, a switch is added to the release version. Patch of msvamp rejected in original repository mywalk added ui interface Co-authored-by: mywalk <[email protected]>
Avoid using a local version of this apache module
Tests passed on Android 13 and Android 15 devices
DexBuilder is updated in the LSPlant repo. Note: we should clean caches of GitHub Actions
8331907
to
7a4cebb
Compare
@happypotter321 Now I have to use the most stupid way to find out which commit breaks CorePatch. |
Just tried the latest Cl build (debug version) and followed the same steps as before, still didn't work for me unfortunately. Are the logs still needed btw? I saved it just in case, here it is. |
7a4cebb
to
02f1e7f
Compare
@happypotter321 It is okay if it still fails. The goal here is try to figure out which commit breaks CorePatch (that is my last resort). |
02f1e7f
to
b5b1c63
Compare
Understood, same result with the build after the previous one I used. Here's the log, |
The GitHub Actions is quite buggy, please try my local build. Edited: It turned out that I misunderstood how Github Actions works with pull-request. My fault... |
b5b1c63
to
77a365d
Compare
That worked: :D |
So far, I found that CorePatch stops working for you once the following logs present:
It seems that some dependency updates breaks CorePatch.
Please continue trying my local builds and upload your log. |
Sure, and yes this one worked too. |
That is cool, so my previous comment was wrong. It is not related to the Please try this local build: |
This one didn't work, yep. |
Then the bug might be caused by LSPlt, which confuses me a lot. |
This one didn't work, just tried it. |
same here, doesn't work too.. fail. before installing an app: com.waze after installing an app: com.waze |
Okay. Then the bug is surely introduced by LSPlt, which might conflict ArtMethod de-optimizing. |
yep it works, the app installed successfully. |
77a365d
to
05dc4a7
Compare
Same here, app installed with that one. |
To temporarily fix this issue, I disable LSPlt in the latest commit. |
05dc4a7
to
ad23736
Compare
Thank you so much, CorePatch works normally now 🫡
before installing: |
@happypotter321 I need your log for the latest CI build debug version to better understand the problem. |
Yep, just tested it and it works. And okay thanks. |
@JingMatrix Of course, here's the logs:
Debug Logs Version:
Debug Logs Version: Sorry, I mistakenly mentioned a pull request. |
This build has same number as builds that don't work - is it safe to download Actions build to test? |
@privacyguy123 Sure. The build name of LSPosed zip archive works in another way, only commits from the main branch will increase that number. We are in a pull-request, so the number stays the same. |
Even if dladdr could not find function name for an address given by art_symbol_resolver, we should still process inline hook.
ad23736
to
82689be
Compare
Hello, everyone. In the latest build, I am try to actually fix the issue instead of a workaround. Please test it and upload the logs if it fails. |
Installing apps with differing signatures all good on my side now :) |
Never mind - you have introduced some regression with this build. Watchdog logs toggled off is now doing nothing and forcing log on/setting persists props every reboot again. I don't understand why this setting would be affected at all by new commits, I see the commit for it in the history. @JingMatrix |
@privacyguy123 Thanks for reporting this issue. |
CorePatch only fails on certain devices (#32 ).
In this branch, I first revert the commit f3beb86, which is known to cause the CorePatch issue on some devices.
After tests results from users for fore-coming commits, I will gradually figure out which commit in the master branch breaks CorePatch.