@aibd, do i need to add vendor/e/ from steadfasterFX in the local manifest because this error ?
antec@antec-p6-2038fr:~/android/e/R$ source build/envsetup.sh > envsetup_01.txt
bash: /home/antec/android/e/R/vendor/extendrom/get_prebuilts.sh: Aucun fichier ou dossier de ce type
or simply and fastidiously create a vendor/extendrom/get_prebuilts.sh ?
envsetup_01.txt say : including device/samsung/serranoltexx/vendorsetup.sh
.
awaiting some inputs on this subject, i tried a “classic” MINIMAL_APPS build, but with the same result as for the precedent “normal” FULL_APPS build :
Out of space? Out of inodes? The tree size of /home/antec/android/e/R/out/soong/.temp/tmp9wfvCO is 1909398528 bytes (1820 MB), with reserved space of 0 bytes (0 MB).
The max image size for filesystem files is 1572864000 bytes (1500 MB), out of a total partition size of 1572864000 bytes (1500 MB).
Sorry to miss the live event ! As output size is unchanged I have to think that MINIMAL_APPS was not applied ?
Yes you do, otherwise nothing with a EOS_ can happen.
Did your /e/ build rewrite your device.xml with a roomservice.xml, if yes we can say that is a good manifest – then two more projects in your proposed build:
It was as I was learning to set up vendor_e properly that I depended on envsetup.txt and breakfast output to see that my environment was correct. My last envset.txt https://paste.tchncs.de/upload/falcon-crow-eagle
(Unexplained, but I found that you should get the environment right before you call envset.txt)
I find you have to be fussy with consistent use of “quote marks” for variables.
Interesting footnote envsetup.txt confirms the use of
Did not get the workstation with 32gb yet, so I may go with 8gb and older i7 for now too…
Found this on github, also recommendations for zram there
Workarounds for building Q on 8GB RAM environment:
At the start of the build:
[ 99% 138/139] /mnt/ssd/aosip/out/soong/.bootstrap/bin/soong_build /mnt/ssd/aosip/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
To avoid huge metalava compilation times, compile the api-stubs-docs and other packages manually first then continue with mka bacon etc
For example this is what I’m using now in aosip:
. build/envsetup.sh && lunch aosip_wayne-userdebug && mka api-stubs-docs && mka hiddenapi-lists-docs && mka system-api-stubs-docs && mka test-api-stubs-docs && mka kronic
Each of those api-stubs-docs, hiddenapi-lists-docs etc took around 4-7 mins
Increasing of heap from soong directory or other env exports are not required
Total combined build time in my system (Ryzen 1600 with a 8gb ddr4 stick) is around 2hrs now compared to 5hrs previously
For errors while building metalava check #metalava
Workarounds for building R on 8GB RAM environment:
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
To avoid huge metalava compilation times, compile the api-stubs-docs and other packages manually first then continue with mka bacon etc
For example this is what I’m using now in LineageOS:
. build/envsetup.sh && lunch lineage_joyeuse-userdebug & mka api-stubs-docs & mka module-lib-api-stubs-docs & mka system-api-stubs-docs & mka test-api-stubs-docs & mka bacon
Each of those api-stubs-docs, module-lib-api-stubs-docs etc took around 4-7 mins
Increasing of heap from soong directory or other env exports are not required
sorry guys, i feel that my eyes are too tired…
interested by zRAM, lost in steadfasterFX documentation and no more understanding forein language (english nor linux)
i will stop for now with building and PC
and probably come back sunday evening
even following the forum from far on my s4mini during the childs’s week-end.
In CUSTOM_SLIM-bacon Post #1 you will see I did extra minimal apps a different way by editing /vendor/lineage/config/common.mk – If you experiment with this method you would not need to call or setup extendrom.
that’s a neat workaround, just compiling those repos first. But if it catches on you’ll juggle more and more of them. I did pickup on hardcoded metalava heap sizes before for low mem builders - and how to set your own - [UNOFFICIAL BUILD] Samsung Galaxy S6 (zerofltexx) - #59 by tcecyk
I also see secondhand 16GB DDR3 DIMM go for < 20€, making zram or soong edits moot
And as my 5 year old was looking for some stuff I saw my old PC stowed away long time ago:
Operating System: KDE neon
Processors: 4 × AMD A6-5200 APU with Radeon™ HD Graphics
Memory: 11.1 GiB of RAM
Graphics Processor: AMD KABINI
Manufacturer: Hewlett-Packard
Will go with 2 × 320Gb SSDs in a zfs - stripe, zRam, try docker and as you know I also like older Samsung’s, so maybe we get to work on those together…
Got it to 16Gb RAM and just a single 500Gb SSD; minimal Ubuntu 22.04 Server and Docker from snaps
$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e3d1ecb2cba4 registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community "/bin/sh -c /root/in…" 8 hours ago Up 8 hours goofy_jemison
make@hp-s1:~$ sudo docker attach e3d1ecb2cba4
... A new version of repo (2.36) is available.
... You should upgrade soon:
cp /srv/src/R/.repo/repo/repo /usr/local/bin/repo
>> [Sat Sep 16 06:41:07 UTC 2023] Starting build for jactivelte, v1.14-r branch
>> [Sat Sep 16 06:41:07 UTC 2023] ANDROID_JACK_VM_ARGS=-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx16G
>> [Sat Sep 16 06:41:07 UTC 2023] Switch to Python2
@piero Docker-Way for this device went through, I got a build (my first) So thanks to the Team who put all this together!
As my old AMD A6-5200 is a mobile quad-core SoC for low-end laptops from 2013,
I did not think it would make it — well at least I got it up to 16Gb Ram.
I could write a tiny howto, on how I put the system together — minimal Ubuntu Server 22.04 + Docker from Snaps!?
[Sat Sep 16 23:34:24 UTC 2023] Moving build artifacts for jactivelte to ‘/srv/zips/jactivelte’
[Sat Sep 16 23:34:37 UTC 2023] Finishing build for jactivelte
[Sat Sep 16 23:34:37 UTC 2023] Cleaning source dir for device jactivelte
23:34:42 ************************************************************
23:34:42 You are building on a machine with 15.1GB of RAM
23:34:42
23:34:42 The minimum required amount of free memory is around 16GB,
23:34:42 and even with that, some configurations may not work.
23:34:42
23:34:42 If you run into segfaults or other errors, try reducing your
23:34:42 -j value.
23:34:42 ************************************************************
23:35:46 Entire build directory removed.
in “nmon”, i only see activity on my main Hard Drive sdc1 (/) and sdc3 (swap). i don’t see any activity on my dedicated to /e/build Hard Drive sdb1 (where sources are stored) is it because it is mounted in “/home/antec” ( for permissions reasons) and not to directly “/” ? do ineed to mount it directly to “/” ( but with user permissions)
In general one would attempt a first build where the available components for the whole project were the same Android version. Then Android version can be set with repo init.
You did your research, so I should assume it is correct.
Here is an example where I attempted to mix revisions
in my local_manifest, i have deleted reference to the two additional devices covered by the build codename but with outdated branch (serranoltespr and serranolteusc) because repo sync stay stuck for a while at 99% related to those devices
antec@antec-p6-2038fr:~/android/e/R$ source build/envsetup.sh > envsetup_01.txt
find: ‘/home/antec/android/e/R/out/target/product’: Aucun fichier ou dossier de ce type
find: ‘/home/antec/android/e/R/out/target/product’: Aucun fichier ou dossier de ce type
find: ‘/home/antec/android/e/R/out/target/product’: Aucun fichier ou dossier de ce type
because there is no existing /out/target folder.
source build/envsetup.sh > envsetup_01.txt
including device/samsung/serranoltexx/vendorsetup.sh
e[0;31mbash stack trace (first occurence is likely where you should look at):e[0m
e[0;31mERROR: last command ended with status >1< at line >142<e[0m
including vendor/e/vendorsetup.sh
… auto-detected CPU count: 4
… will use this thread count: 3
not exporting special var CCACHE_COMPRESS as it is an unset variable
not exporting special var CCACHE_NOCOMPRESS as it is an unset variable
emptied MIRROR ><
emptied OTA_URL ><
emptied CUSTOM_PACKAGES ><
!!!
******** /e/ - set JAVA ********
!!!
[lun. 18 sept. 2023 06:28:36 CEST] Determining correct OpenJDK version for v1-r
… checking if we need to switch Java version
… skipping touching java as we use a shipped one (/home/antec/android/e/R/prebuilts/jdk/jdk11/linux-x86)
[lun. 18 sept. 2023 06:28:36 CEST] Using Java JDK /home/antec/android/e/R/prebuilts/jdk/jdk11/linux-x86
!!!
******** /e/ - INIT ********
!!!
[lun. 18 sept. 2023 06:28:36 CEST] Preparing build environment
[lun. 18 sept. 2023 06:28:36 CEST] DEBUG: ROOT_DIR is set to: >/home/antec/android/e/R/.e/root<
Set cache size limit to 100.0 GB
!!!
******** /e/ - POSTSYNC ********
!!!
[lun. 18 sept. 2023 06:28:36 CEST] Setting “UNOFFICIAL” as release type
[lun. 18 sept. 2023 06:28:36 CEST] Adding keys path (/home/antec/android/e/R/.e/keys)
Switch back to Python3
antec@antec-p6-2038fr:~/android/e/R$ source build/envsetup.sh > envsetup_01.txt
find: ‘/home/antec/android/e/R/out/target/product’: Aucun fichier ou dossier de ce type
find: ‘/home/antec/android/e/R/out/target/product’: Aucun fichier ou dossier de ce type
find: ‘/home/antec/android/e/R/out/target/product’: Aucun fichier ou dossier de ce type
antec@antec-p6-2038fr:~/android/e/R$ breakfast serranoltexx
Looking for dependencies in device/samsung/serranoltexx
Looking for dependencies in device/samsung/serrano-common
Looking for dependencies in device/samsung/qcom-common
Looking for dependencies in hardware/samsung
hardware/samsung has no additional dependencies.
Looking for dependencies in device/samsung/msm8930-common
device/samsung/msm8930-common has no additional dependencies.
Looking for dependencies in kernel/samsung/msm8930-common
kernel/samsung/msm8930-common has no additional dependencies.
Out of space? Out of inodes? The tree size of /home/antec/android/e/R/out/soong/.temp/tmpdSgQ9X is 1771503616 bytes (1689 MB), with reserved space of 0 bytes (0 MB).
The max image size for filesystem files is 1572864000 bytes (1500 MB), out of a total partition size of 1572864000 bytes (1500 MB).
12:44:33 ninja failed with: exit status 1
failed to build some targets (05:30:05 (hh:mm:ss))
.
but difference is less than the last time
Out of space? Out of inodes? The tree size of /home/antec/android/e/R/out/soong/.temp/tmpP4gD4X is 1909393408 bytes (1820 MB), with reserved space of 0 bytes (0 MB).
The max image size for filesystem files is 1572864000 bytes (1500 MB), out of a total partition size of 1572864000 bytes (1500 MB).