Does anyone know how to resolve this build error (excerpt):
Full error log:https://share.freepro.com/a243b8a8-02ca-4f7d-8be4-28cd3a239ed6
100% 131/131] analyzing Android.bp files and generating ninja file at out/soong/build.lineage_dreamlte.ninja
FAILED: out/soong/build.lineage_dreamlte.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" --soong_variables out/soong/soong.lineage_dreamlte.variables -o out/soong/build.lineage_dreamlte.ninja
-l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.lineage_dreamlte.build Android.bp
Warning: Module 'androidx.wear_wear' depends on non-existing optional_uses_libs 'wear-sdk'
Warning: Module 'androidx.wear.compose_compose-foundation' depends on non-existing optional_uses_libs 'wear-sdk'
Warning: Module 'webview' depends on non-existing optional_uses_libs 'com.android.extensions.xr'
error: build/soong/fsgen/Android.bp:31:1: module "lineage_dreamlte_generated_system_image" variant "android_common" (created by module "soong_filesystem_creator" variant "android_common"): packaging conflict at lib64/libhidlbase-v32.so:
{lib64/libhidlbase-v32.so {{{.intermediates/prebuilts/vndk/v32/arm64/arch-arm-armv8-a/shared/vndk-sp/system-prebuilts_vndk_v32_arm64_arch-arm-armv8-a_shared_vndk-sp-lib-0/android_arm64_armv8-a/libhidlbase-v32.so libhidlbase-v32.so} out/soong out/soong/.intermediates/prebuilts/vndk/v32/arm64/arch-arm-armv8-a/shared/vn
dk-sp/system-prebuilts_vndk_v32_arm64_arch-arm-armv8-a_shared_vndk-sp-lib-0/android_arm64_armv8-a/libhidlbase-v32.so}} false 0xc56d8c9980 system false 0xc56d8d77c0 {arm64 Arm64 lib64} 0xc56d8c9998 system-prebuilts_vndk_v32_arm64_arch-arm-armv8-a_shared_vndk-sp-lib-0}
{lib64/libhidlbase-v32.so {{{.intermediates/prebuilts/vndk/v32/arm64/arch-arm64-armv8-a/shared/vndk-sp/system-prebuilts_vndk_v32_arm64_arch-arm64-armv8-a_shared_vndk-sp-lib64-0/android_arm64_armv8-a/libhidlbase-v32.so libhidlbase-v32.so} out/soong out/soong/.intermediates/prebuilts/vndk/v32/arm64/arch-arm64-armv8-a/s
hared/vndk-sp/system-prebuilts_vndk_v32_arm64_arch-arm64-armv8-a_shared_vndk-sp-lib64-0/android_arm64_armv8-a/libhidlbase-v32.so}} false 0xc56d8f4030 system false 0xc56d8d7fc0 {arm64 Arm64 lib64} 0xc56d8f4048 system-prebuilts_vndk_v32_arm64_arch-arm64-armv8-a_shared_vndk-sp-lib64-0}
error: build/soong/fsgen/Android.bp:31:1: module "lineage_dreamlte_generated_system_image" variant "android_common" (created by module "soong_filesystem_creator" variant "android_common"): packaging conflict at lib64/libIDDQD_core.so:
{lib64/libIDDQD_core.so {{{.intermediates/vendor/samsung/dreamlte/proprietary/lib/system-vendor_samsung_dreamlte_proprietary_lib-lib-0/android_arm64_armv8-a/libIDDQD_core.so libIDDQD_core.so} out/soong out/soong/.intermediates/vendor/samsung/dreamlte/proprietary/lib/system-vendor_samsung_dreamlte_proprietary_lib-lib-
0/android_arm64_armv8-a/libIDDQD_core.so}} false 0xc56e062360 system false 0xc56e024fc0 {arm64 Arm64 lib64} 0xc56e062378 system-vendor_samsung_dreamlte_proprietary_lib-lib-0}
{lib64/libIDDQD_core.so {{{.intermediates/vendor/samsung/dreamlte/proprietary/lib64/system-vendor_samsung_dreamlte_proprietary_lib64-lib64-0/android_arm64_armv8-a/libIDDQD_core.so libIDDQD_core.so} out/soong out/soong/.intermediates/vendor/samsung/dreamlte/proprietary/lib64/system-vendor_samsung_dreamlte_proprietary_
lib64-lib64-0/android_arm64_armv8-a/libIDDQD_core.so}} false 0xc56e0b1ce0 system false 0xc56e0d4bc0 {arm64 Arm64 lib64} 0xc56e0b1cf8 system-vendor_samsung_dreamlte_proprietary_lib64-lib64-0}
error: build/soong/fsgen/Android.bp:31:1: module "lineage_dreamlte_generated_system_image" variant "android_common" (created by module "soong_filesystem_creator" variant "android_common"): packaging conflict at lib64/libIDDQD_interface.so:
…
error: build/soong/fsgen/Android.bp:31:1: module "lineage_dreamlte_generated_system_image" variant "android_common" (created by module "soong_filesystem_creator" variant "android_common"): packaging conflict at vendor/lib64/soundfx/libaudioeffectoffload.so:
{vendor/lib64/soundfx/libaudioeffectoffload.so {{{.intermediates/vendor/samsung/universal8895-common/proprietary/vendor/lib64/soundfx/vendor-vendor_samsung_universal8895-common_proprietary_vendor_lib64_soundfx-lib64_soundfx-0/android_arm64_armv8-a/libaudioeffectoffload.so libaudioeffectoffload.so} out/soong out/soong
/.intermediates/vendor/samsung/universal8895-common/proprietary/vendor/lib64/soundfx/vendor-vendor_samsung_universal8895-common_proprietary_vendor_lib64_soundfx-lib64_soundfx-0/android_arm64_armv8-a/libaudioeffectoffload.so}} false 0xc56f60f758 system false 0xc56ecb6fc0 {arm64 Arm64 lib64} 0xc56f60f770 vendor-vendor
_samsung_universal8895-common_proprietary_vendor_lib64_soundfx-lib64_soundfx-0}
{vendor/lib64/soundfx/libaudioeffectoffload.so {{{.intermediates/vendor/samsung/universal8895-common/proprietary/vendor/lib/soundfx/vendor-vendor_samsung_universal8895-common_proprietary_vendor_lib_soundfx-lib_soundfx-0/android_arm64_armv8-a/libaudioeffectoffload.so libaudioeffectoffload.so} out/soong out/soong/.inte
rmediates/vendor/samsung/universal8895-common/proprietary/vendor/lib/soundfx/vendor-vendor_samsung_universal8895-common_proprietary_vendor_lib_soundfx-lib_soundfx-0/android_arm64_armv8-a/libaudioeffectoffload.so}} false 0xc56e411d10 system false 0xc56e4473c0 {arm64 Arm64 lib64} 0xc56e411d28 vendor-vendor_samsung_uni
versal8895-common_proprietary_vendor_lib_soundfx-lib_soundfx-0}
21:40:17 soong bootstrap failed with: exit status 1
ninja: build stopped: subcommand failed.
tcecyk
October 11, 2025, 7:07pm
2
do you build in your own environment or is this the community docker image? that one still switches to py2 I noticed. Kind of eying this for when soong hiccups
I use my own environment… still repo.
Might be related to this issue?build/soong/fsgen/Android.bp
1 Like
tcecyk
October 11, 2025, 8:16pm
4
where’s a a15 branched dreamlte device repo?
error: build/soong/fsgen/Android.bp:31:1: module "lineage_dreamlte_generated_system_image" variant "android_common" (created by module "soong_filesystem_creator" variant "android_common"): packaging conflict at lib64/libhidlbase-v32.so:
one place I can find soong/fsgen errors discussed is https://review.lineageos.org/c/LineageOS/android_device_samsung_a71/+/424640/1
piero
October 13, 2025, 6:57am
6
long time without building,
============================================
[100% 2/2] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
error: prebuilts/prebuiltapks/Maps/Android.bp:13:17: unrecognized property "preprocessed"
error: prebuilts/prebuiltapks/AndroidAutoStub/Android.bp:4:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/MdmProvisioner/Android.bp:14:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/AndroidAutoStub/Android.bp:11:17: unrecognized property "preprocessed"
error: prebuilts/prebuiltapks/GmsCore/Android.bp:4:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/FakeStore/Android.bp:4:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/BlissWeather/Android.bp:18:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/BlissLauncher3/Android.bp:71:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/Ntfy/Android.bp:18:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/MurenaMDM/Android.bp:14:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/ParentalControl/Android.bp:15:26: unrecognized property "relative_install_path"
error: prebuilts/prebuiltapks/mapsOverlay/Android.bp:1:1: module "mapsOverlay" already defined
vendor/eos/rro_overlays/mapsOverlay/Android.bp:1:1 <-- previous definition here
error: prebuilts/prebuiltapks/AdvancedPrivacy/Android.bp:34:26: unrecognized property "relative_install_path"
08:30:05 soong bootstrap failed with: exit status 1
#### failed to build some targets (25 seconds) ####
I assume you have an environment older than A12 (/e/OS-S)?
For example if you use /e/OS-R take this version:
1 Like
piero
October 13, 2025, 7:58am
8
ronnz98
October 15, 2025, 5:10pm
10
Another thing, has someone experience extracting vendor files with Python (py) instead of sh?
tcecyk
October 15, 2025, 6:02pm
11
no, when I did this once, I relied on .sh + .txt. Why would you ask? do you have a python script that doesn’t work?
ronnz98
October 15, 2025, 6:10pm
12
Basically it works, but I got errors in terms of missing files and access issues when using the python script. To be honest, I could not yet successfully extract via python - with sh it mostly worked
tcecyk
October 16, 2025, 1:39pm
13
what I last built were always old-ish devices, so I never saw LineageOS ported the shellscript.
I do have a walleye around to test a extract-files.py though. If you post your errors to a pastebin I can compare to the output I get from running this against a walleye. I assume your .py has the same origin
ronnz98
October 17, 2025, 6:19am
14
I’m following the instructions for payload based OTA:
When I run
./extract-files.py ~/android/system_dump/
in my device directory I get
PermissionError: [Errno 13] Permission denied: '/home/ronnz/android/system_dump/system/vendor/lost+found
So I did run it with sudo
sudo umount -R ~/android/system_dump/system/
and get this error then:
OSError: [Errno 30] Read-only file system: ‘adb_keys’
If I mount the folders with read and write permissons I get other errors…
aibd
October 17, 2025, 8:31am
15
Just a thought, on the basis that lost+found is (probably ??) a creation of a PC rather than a true copy of the dump does it work to try to delete lost+found?
ronnz98
October 17, 2025, 9:24am
16
This is what I also tried, but as the folders are read only mounted it does not work
sudo mount -o ro system.img system/
When I mount with read and write access I get different error messages
ronnz98
October 20, 2025, 2:49pm
17
after installing current version of
Contribute to LineageOS/android_tools_extract-utils development by creating an account on GitHub.
it is much better, but depending on quality of sources if it works
tcecyk
October 20, 2025, 3:40pm
18
I thought to ask what image you mount and run this on, every extract-files.py is custom and only a template in the quoted repo.
If there’s still something unanswered I can run the exact script you use on the same image and see if I have any explanation.
(There’s also now more payload dumpers around that I was unaware of - saw that used in the librephone project)
ronnz98
October 20, 2025, 3:50pm
19
tcecyk
October 23, 2025, 1:09am
20
played around with this. extract-files.py is automagic - directly from a lineage device .zip, something not documented in the wiki yet.
For that device (elish), payload type, the wiki still says to readonly mount partitions extracted, but then if you run the current .py code against a system_dump/ dir that has those mounts, any number of write permissions will crop up (around system-as-root) when it tries to move around files.
If you give it just the .zip, it will do the payload extract and dump all script internally. Still had lots of errors for elish, will have a second look. Interesting overall to see this.
See the Nolan comments at (currently) the bottom of (expand all) https://review.lineageos.org/c/LineageOS/lineage_wiki/+/456612
1 Like