-
Notifications
You must be signed in to change notification settings - Fork 28
Fix timing and Android 15 support #61
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
base: master
Are you sure you want to change the base?
Conversation
Added a loop to wait for the zygote64 process before executing critical certificate operations. This prevents race conditions during module initialization and ensures compatibility with the system boot sequence.
…cleanup and safety checks Updated the script to enhance temporary directory management for handling Android 14 APEX CA storage: - Changed `rm -f` to `rm -rf` to ensure proper cleanup of temporary directories. - Replaced hardcoded paths with a reusable `TEMP_DIR` variable for clarity and maintainability. - Added a loop to ensure safe unmounting of the temporary directory, preventing "Device or resource busy" errors.
|
For some reason this cause my phone to be stuck on boot screen. Using KernelSU-Next with Zygisk Next. |
|
I thought only administrators had the permission to approve, and I was curious so I clicked it. Sorry about that |
Same to me, OnePlus Ace 3,KernelSU by 5ec1cff |
It is a question of nonsense, cause magisk modules is only designed for magisk. Ksu has its own rules, even though it might be compatible with some magisk modules. |
Almost all incompatibilities are caused by modules not being designed according to standard templates. |
|
Hello! There's a lot issues with this PR. First, it will definitely hang on 32-bit devices, and in case that umount permanently fails. Second, it does some refactoring, not only targets issues. And at last, if we assume that on some configurations, zygote is being spawned while running this script, not before, then additional research is needed about parent process on that configuration. If it is PID 1, then simply evaluating P.S. KernelSU issues are not relevant to this PR since they are present on master too, see #62 |
sfionov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my previous comment
Seems unvisible. |
|
@larsmartens hey, can you rebase with Android 16 support? |
You can use https://github.com/ys1231/MoveCertificate |
This pull request addresses critical issues observed in the AdGuard certificate module logs, ensuring proper functionality and compatibility with the Android 14/15 APEX CA directory.
Context and Observed Issues
I noticed that the module often simply didn't apply the changes and, after examining the logs, identified the same errors as in this timing-related issue, as well as another one related to unmounting:
Timing Issues:
zygote64process was initialized, causing the module to stall in an indefinite loop:Temporary Directory Cleanup Issues:
Fixes Implemented
Timing Fix for zygote64 Initialization
zygote64process before proceeding with critical operations.Enhancements for Android 14 APEX CA Directory Handling
rm -fwithrm -rffor proper directory removal.TEMP_DIRvariable for improved readability and easier future maintenance.Testing
zygote64to initialize before performing operations.Impact