Created
March 18, 2022 06:53
-
-
Save verNANDo57/9c14d529d91e79f3b42fa6bd7b9eba85 to your computer and use it in GitHub Desktop.
Workarounds for building Android 12 on 8GB RAM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Workarounds for building S on 8GB RAM environment: | |
| 1. At the start of the build: | |
| [ 99% 138/139] /mnt/ssd/lineage/out/soong/.bootstrap/bin/soong_build /mnt/ssd/lineage/out/soong/build.ninja | |
| This used to take around 30mins, after enabling zram now it takes around 30secs (thanks to @kdrag0n for the zram idea) which is on par with what happens in 16GB RAM building environments | |
| sudo apt install zram-config for installing zram-config package | |
| sudo nano /etc/fstab and add a # in front of the swap disk if you have one and then reboot | |
| After booting cat /proc/swaps to check if zram is enabled or not | |
| 2. To avoid issues while building metalava (outOfMemoryException: java heap space) | |
| Pick this commit --> https://github.com/verNANDo57/android_build_soong/commit/ffc8846a01fcfc20d6cf8ca701ef73d99f15acad |
Solved: Free ssh server for android building with 16gb ram + swap
https://github.com/chunix64/github-action-sshIs the disksize enough for that?
Enough for boot, recovery, vendor_boot building but not for system.img
Try "distributed build system", idk if it works
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is the disksize enough for that?