-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[Feature Request]Add support for android AVD #2581
Comments
|
@linuxandria try to see this issue #2551, shakalaca has developed a script for patch AVD and android x86, for me the patch for android x86 is working, so I think also AVD is good. |
@ematrix would be nice to be able to provide manager with the necessary files and automatically do the needful patches. Or emulator.sh fixed to better support it |
|
@linuxandria it's funny I posted similar issue here https://github.com/topjohnwu/Magisk/issues/2471 |
build.py emulator |
There is of course the script in scripts/emulator.sh but that is rather tedious to have to execute on each boot, and renders testing modules kinda worthless since they aren't going to be mounted properly, nor boot scripts ran.
As of this moment, checking on a sdk29 official AVD from Android studio, there is a ramdisk.img that could be theoretically patched, if Manager actually supported the format. I tried using commands taken from boot_patch.sh, but it gets stuck at [loading ramdisk.cpio] (which does exist in the directory magiskboot is ran from).
I'd like to see either
A) Manager supports patching (of course not flashing, you'd have to copy the ramdisk back into place yourself) ramdisk.img natively
B) Some sort of documentation on how we can get a (mostly if not fully) working environment in the official AVD.
I'm only suggesting the official AVD from google because there are any combination of other emulators that may or may not have a ramdisk or weird hacks to get things working (not to mention android x86 doesn't want to launch the gui for me), but the AVD will always have a universal setup for each release, and would be very useful for me as a module developer because I wouldn't have to either buy a second device for testing or test on my daily driver. It could also be useful if you want to test out certain mods on a device that is easily disposable or your not sure if it's 100% safe.
The text was updated successfully, but these errors were encountered: