-
Notifications
You must be signed in to change notification settings - Fork 6
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
emulate magisk boot process wrong #6
Comments
Thanks for sharing your insights, I will look into it when I can. |
This was koushsu init.rc implementation and @axonasif use it back in Magisk 21.x days, it used to work but now isn't anymore. He can't check because he don't have a device to test so I'll modify the init and see if it boot on my PS-x86 build when I have time. |
Find a way (Use In Topjohnwu's emulator.sh:
|
There's already one |
Oh i noticed that almost emulator has Permissive Selinux mode |
Rusty-magisk don't stop boot process if magisk in post-fs-data are not completed
Follow topjohnwu's Magisk Documentation, in post-fs-data stage, boot process must be stopped until all Magisk jobs are completed or 40 seconds timeout is reached.
Also the road from post-fs-data to late_start happened in very short time and magisk post-fs-data jobs may not be completed yet, maybe there are processing post-fs-data module script but late_start was triggered.
That can make some modules cannot be working well if the user install many module
Compare init.rc between Magisk on my phone and init.rc in rusty-magisk.
The text was updated successfully, but these errors were encountered: