@headwind-mdm We've been focused on Android 15 QPR2 and the new hardware virtualization app but we can get to this soon.
headwind-mdm
- 13 hours ago
- Joined a month ago
- Edited
Hello,
you might find this guide I wrote useful: https://gist.github.com/soupslurpr/40601841ea537dbe0aff511a411a6b8a
For an emulator, I believe you just run
emulatorafter runningm, but the full docs for that are at https://developer.android.com/studio/run/emulator-commandlineheadwind-mdm If the build machine doesn't have enough memory, all sorts of things go wrong, and the error reporting does not implicate memory exhaustion, so the errors appear random and nonsensical.
I recently did an emulator build (i.e., without extracting vendor files for a device) on a machine with 12 GB of physical memory, but it used 40 GB virtual and took multiple days.
headwind-mdm Please advise how to fix these build issues.
You could look in your system logs to see if the OOM killer is running... but it would probably be better overall to get machine with at least 32 GB of physical memory, with 64 GB being a safer bet. And I would still recommend configuring a swap partition (better than a swap file).
headwind-mdm You can submit a pull request here:
https://github.com/GrapheneOS/platform_packages_apps_SetupWizard2
Filed an issue about it here:
https://github.com/GrapheneOS/platform_packages_apps_SetupWizard2/issues/35
We have a build guide for GrapheneOS here:
