NetGuard app (still) does not work- as a FYI, somewhere along the line the internal network stack is borked, and NOT the fault of /e/ or this unofficial build.
WiFi still spontaneously disconnects (even with Location “on”)- again, likely related to the above and not the fault of the OS or this build.
No change to the persistent and pernicious “echo” problem with this device while using the native dialer or “Simple Dialer”. However, as a reminder, this audio issue is NOT present while using the “calling” functions of Signal or Telegram.
If there’s anything else I run across, I’ll post another update.
Hmm weird, I have the same model and it doesnt recognise my sim at all, thinks theres 2 slots instead of one and the imei is “unavailable”. Any other rom i try works fine though, dunno whats causing this
Good day, I’ve been trying to create an up-to-date e/os rom for zerofltexx via Docker for days. But I always get the same error. Can someone please tell me what else I need to do to make it work? I have already tried a few things, but honestly I do not know where the error is or what else I need to do.
Here is the docker output from today:
>> [Sat Nov 26 14:56:42 UTC 2022] Starting build for zerofltexx, v1-q branch
15:07:14 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
15:07:15 dumpvars failed with: exit status 1
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos5 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos5
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos7420 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos7420
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_openmax from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_openmax
error: Cannot fetch LineageOS/android_kernel_samsung_exynos7420 from https://github.com/LineageOS/android_kernel_samsung_exynos7420
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos5 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos5
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos7420 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos7420
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_openmax from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_openmax
error: Cannot fetch LineageOS/android_kernel_samsung_exynos7420 from https://github.com/LineageOS/android_kernel_samsung_exynos7420
error: Cannot checkout LineageOS/android_hardware_samsung_slsi-cm_exynos: ManifestInvalidRevisionError: revision refs/heads/lineage-17.1 in LineageOS/android_hardware_samsung_slsi-cm_exynos not found
error: in `sync --force-sync hardware/samsung hardware/samsung_slsi-cm/exynos hardware/samsung_slsi-cm/exynos5 hardware/samsung_slsi-cm/exynos7420 hardware/samsung_slsi-cm/openmax kernel/samsung/exynos7420`: revision refs/heads/lineage-17.1 in LineageOS/android_hardware_samsung_slsi-cm_exynos not found
Device zerofltexx not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_samsung_zerofltexx
Default revision: lineage-17.1
Checking branch info
Using fallback branch: lineage-15.1
Checking if device/samsung/zerofltexx is fetched from android_device_samsung_zerofltexx
Adding dependency: LineageOS/android_device_samsung_zerofltexx -> device/samsung/zerofltexx
Using fallback branch lineage-15.1 for android_device_samsung_zerofltexx
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies in device/samsung/zerofltexx
Adding dependencies to manifest
Checking if device/samsung/zero-common is fetched from android_device_samsung_zero-common
Adding dependency: LineageOS/android_device_samsung_zero-common -> device/samsung/zero-common
Using fallback branch lineage-15.1 for android_device_samsung_zero-common
Syncing dependencies
Looking for dependencies in device/samsung/zero-common
Adding dependencies to manifest
Checking if hardware/samsung is fetched from android_hardware_samsung
Adding dependency: LineageOS/android_hardware_samsung -> hardware/samsung
Using default branch for android_hardware_samsung
Checking if hardware/samsung_slsi-cm/exynos is fetched from android_hardware_samsung_slsi-cm_exynos
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_exynos -> hardware/samsung_slsi-cm/exynos
Using default branch for android_hardware_samsung_slsi-cm_exynos
Checking if hardware/samsung_slsi-cm/exynos5 is fetched from android_hardware_samsung_slsi-cm_exynos5
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_exynos5 -> hardware/samsung_slsi-cm/exynos5
Using default branch for android_hardware_samsung_slsi-cm_exynos5
Checking if hardware/samsung_slsi-cm/exynos7420 is fetched from android_hardware_samsung_slsi-cm_exynos7420
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_exynos7420 -> hardware/samsung_slsi-cm/exynos7420
Using default branch for android_hardware_samsung_slsi-cm_exynos7420
Checking if hardware/samsung_slsi-cm/openmax is fetched from android_hardware_samsung_slsi-cm_openmax
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_openmax -> hardware/samsung_slsi-cm/openmax
Using default branch for android_hardware_samsung_slsi-cm_openmax
Checking if kernel/samsung/exynos7420 is fetched from android_kernel_samsung_exynos7420
Adding dependency: LineageOS/android_kernel_samsung_exynos7420 -> kernel/samsung/exynos7420
Using default branch for android_kernel_samsung_exynos7420
Syncing dependencies
Looking for dependencies in hardware/samsung
hardware/samsung has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/exynos
hardware/samsung_slsi-cm/exynos has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/exynos5
hardware/samsung_slsi-cm/exynos5 has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/exynos7420
hardware/samsung_slsi-cm/exynos7420 has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/openmax
hardware/samsung_slsi-cm/openmax has no additional dependencies.
Looking for dependencies in kernel/samsung/exynos7420
kernel/samsung/exynos7420 has no additional dependencies.
Done
15:08:18 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
15:08:18 dumpvars failed with: exit status 1
15:08:20 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
15:08:20 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_zerofltexx'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
>> [Sat Nov 26 15:08:20 UTC 2022] Failed build for zerofltexx
>> [Sat Nov 26 15:08:20 UTC 2022] Finishing build for zerofltexx
>> [Sat Nov 26 15:08:20 UTC 2022] Cleaning source dir for device zerofltexx
15:08:22 Entire build directory removed.
#### build completed successfully (2 seconds) ####
>> [Sat Nov 26 16:08:10 UTC 2022] Starting build for zerofltexx, v1-q branch
16:16:28 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
16:16:29 dumpvars failed with: exit status 1
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos5:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_hardware_samsung_slsi-cm_openmax:
fatal: couldn't find remote ref refs/heads/lineage-17.1
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420: sleeping 4.0 seconds before retrying
fatal: couldn't find remote ref refs/heads/lineage-17.1
LineageOS/android_kernel_samsung_exynos7420:
fatal: couldn't find remote ref refs/heads/lineage-17.1
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos5 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos5
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos7420 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos7420
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_openmax from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_openmax
error: Cannot fetch LineageOS/android_kernel_samsung_exynos7420 from https://github.com/LineageOS/android_kernel_samsung_exynos7420
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos5 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos5
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_exynos7420 from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos7420
error: Cannot fetch LineageOS/android_hardware_samsung_slsi-cm_openmax from https://github.com/LineageOS/android_hardware_samsung_slsi-cm_openmax
error: Cannot fetch LineageOS/android_kernel_samsung_exynos7420 from https://github.com/LineageOS/android_kernel_samsung_exynos7420
error: in `sync --force-sync hardware/samsung hardware/samsung_slsi-cm/exynos hardware/samsung_slsi-cm/exynos5 hardware/samsung_slsi-cm/exynos7420 hardware/samsung_slsi-cm/openmax kernel/samsung/exynos7420`: revision refs/heads/lineage-17.1 in LineageOS/android_hardware_samsung_slsi-cm_exynos not found
Device zerofltexx not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_samsung_zerofltexx
Default revision: lineage-17.1
Checking branch info
Using fallback branch: lineage-15.1
Checking if device/samsung/zerofltexx is fetched from android_device_samsung_zerofltexx
Adding dependency: LineageOS/android_device_samsung_zerofltexx -> device/samsung/zerofltexx
Using fallback branch lineage-15.1 for android_device_samsung_zerofltexx
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies in device/samsung/zerofltexx
Adding dependencies to manifest
Checking if device/samsung/zero-common is fetched from android_device_samsung_zero-common
Adding dependency: LineageOS/android_device_samsung_zero-common -> device/samsung/zero-common
Using fallback branch lineage-15.1 for android_device_samsung_zero-common
Syncing dependencies
Looking for dependencies in device/samsung/zero-common
Adding dependencies to manifest
Checking if hardware/samsung is fetched from android_hardware_samsung
Adding dependency: LineageOS/android_hardware_samsung -> hardware/samsung
Using default branch for android_hardware_samsung
Checking if hardware/samsung_slsi-cm/exynos is fetched from android_hardware_samsung_slsi-cm_exynos
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_exynos -> hardware/samsung_slsi-cm/exynos
Using default branch for android_hardware_samsung_slsi-cm_exynos
Checking if hardware/samsung_slsi-cm/exynos5 is fetched from android_hardware_samsung_slsi-cm_exynos5
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_exynos5 -> hardware/samsung_slsi-cm/exynos5
Using default branch for android_hardware_samsung_slsi-cm_exynos5
Checking if hardware/samsung_slsi-cm/exynos7420 is fetched from android_hardware_samsung_slsi-cm_exynos7420
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_exynos7420 -> hardware/samsung_slsi-cm/exynos7420
Using default branch for android_hardware_samsung_slsi-cm_exynos7420
Checking if hardware/samsung_slsi-cm/openmax is fetched from android_hardware_samsung_slsi-cm_openmax
Adding dependency: LineageOS/android_hardware_samsung_slsi-cm_openmax -> hardware/samsung_slsi-cm/openmax
Using default branch for android_hardware_samsung_slsi-cm_openmax
Checking if kernel/samsung/exynos7420 is fetched from android_kernel_samsung_exynos7420
Adding dependency: LineageOS/android_kernel_samsung_exynos7420 -> kernel/samsung/exynos7420
Using default branch for android_kernel_samsung_exynos7420
Syncing dependencies
Looking for dependencies in hardware/samsung
hardware/samsung has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/exynos
hardware/samsung_slsi-cm/exynos has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/exynos5
hardware/samsung_slsi-cm/exynos5 has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/exynos7420
hardware/samsung_slsi-cm/exynos7420 has no additional dependencies.
Looking for dependencies in hardware/samsung_slsi-cm/openmax
hardware/samsung_slsi-cm/openmax has no additional dependencies.
Looking for dependencies in kernel/samsung/exynos7420
kernel/samsung/exynos7420 has no additional dependencies.
Done
16:17:31 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
16:17:31 dumpvars failed with: exit status 1
16:17:35 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
16:17:35 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_zerofltexx'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
>> [Sat Nov 26 16:17:35 UTC 2022] Failed build for zerofltexx
>> [Sat Nov 26 16:17:35 UTC 2022] Finishing build for zerofltexx
>> [Sat Nov 26 16:17:35 UTC 2022] Cleaning source dir for device zerofltexx
16:17:38 Entire build directory removed.
#### build completed successfully (4 seconds) ####
>> [Sat Nov 26 17:44:24 UTC 2022] Starting build for zerofltexx, v1-q branch
17:51:21 Build sandboxing disabled due to nsjail error.
e[1mbuild/make/core/product_config.mk:223: e[31merror: e[0me[1mCan not locate config makefile for product "lineage_zerofltexx".e[0m
17:51:22 dumpvars failed with: exit status 1
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.
... A new version of repo (2.29) is available.
... You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
This line indicates that you have set the BRANCH_NAME variable to lineage-17.1), which is fine if you are building LineageOS, but for /e/ there is no such branch. For /e/OS you need to use a branch or release name like v1-q (which will build whatever is the latest code code in the v1-q branch (which is Android 10 (Q)/LOS 17.1) or v1.5-q which should build the version that was officially released as version `v1-5-q
Thank you very much for your answer dear petefoth! I really appreciate it very much! I am very grateful for your help! I think I already considered that, because I always specified ROOMSERVICE_BRANCHES=lineage-15.1 in the Docker command. Please excuse me, I forgot to include in my previous post the Docker command I am using.
But as luck would have it, I have now found the error. At least, that’s how it seems. I’ve actually discovered what I was doing wrong before. I don’t know if I’ll make it to a finished rom now, but things are looking good at the moment. And I’ve never been as far along in that regard as I am now. It was just a little careless mistake that cost me days of research. I’m really embarrassed about it now. That’s what I did wrong:
So the problem was that Docker could not find my local-manifest.
Thanks again for your answer dear petefoth! It is quite possible that I will need your help again later.
I’ll keep you and everyone else here up to date about my attempt.
Thanks to tcecyk, the previous problem with “clang” that appeared at about 26% of the build is solved. The build is now almost finished, but the build stopped again at 97%. And it gives the following error:
I see the compilation has a few hardcoded Xmx (java max heap space) values and some that are (or should be?) inherited from java/config/config.go. You can tweak them.
Thank you so much dear tcecyk! Thanks to your information it worked now! Because the last problem was indeed that I have too little Ram on my computer. Now I simply built the build again without any further changes (only the change for “clang” “ld”) with a rented and suitable server. And it worked! This is now the first time that I managed (of course only with your generous help) to create a build myself. That makes me very happy! And I am very grateful to you dear tcecyk! Because without your help I would never have done it! Humans like you are so wonderful!
So the build works, as far as I can judge, at least as good as the old 0.18-q build from last year from itsclarence, with the difference that it is now a current 1.7-q build with all its advantages.
The only downside is that I don’t know how to prepare and modify the build to enable SELinux. Unfortunately SELinux is disabled in the build. And I was told by someone that it is very important for security that SELlinux enforcing is enabled and working. I have hope that you can show me, dear tcecyk, how this works. Because you are the absolute expert here, I think! If SELinux could still work, I would be so happy.
Do you also know how to configure with SELinux in e/os build dear tcecyk? That would be great!
I would have loved to share the 1.7-q build for the zeroflte here. Unfortunately, I had to find out that the posts here from me, which contain a link to a file, are marked by other users as spam and then deleted from the forum. This is exactly what happened to my post where I linked to the log file of the old build of mine. For reasons unknown to me, this post of mine was marked as spam and deleted by the system. Which of course is complete nonsense, because the link and the file only contained the docker logfile of the build. Very sad the whole thing. Because of this, I can’t post any more posts with links to files here now, so not even to the 1.7-q build. I tried that just now, but the function to share links has now been blocked for me by the forum. Which I find very unfortunate, because I would like to make the build available to the community.
If someone here is interested in the new 1.7-q build for zeroflte / zerofltexx International GSM (SM-G920F, SM-G920FD, SM-G920I), he can write me here via the forum with a private message. Then I will send them the link to the e/OS 1.7-q build for zeroflte privately. I have already uploaded the build on a server, anyone with the link can download the build.
thanks for the praise, though I too rely on others all the time. Still curious on what kind of specs/memory you tried to build on in the first place - I think the metalava memory issue is solveable, with some trickery building on 8G is possible at least until Android 10.
SELinux: for your device you probably have a device repo and a device-common repo, in the latter is a “sepolicy/” folder that is included, adding device specific rules to the linageos generic sepolicy. You control this in the BoardConfig.mk and BoardConfigCommon.mk makefile. You’ll have somewhere a parameter setting selinux to permissive (as here), to only log denials rather than enforce them. Removing that line will enable SELinux proper.
First, @eisy I commend you on your efforts- they are first rate and congratulations on completing an updated build for this device- astonishing! Regarding SELinux, as I recall even the builds by @itsclarence did not have SELinux enabled.
I will PM you for the build link as soon as I find my S6 and charge it. With your permission, I should be able to post the link in the thread so that your work can be shared with all here.
Greetings to all who are still monitoring this thread. As outlined above, @eisy has prepared an UNOFFICIAL updated build for the zerofltexx SM-G920F and has granted me permission to share it here:
I can confirm that the build updates @itsclarence unofficial 0.18 build to 1.7-Q with all MicroG (version 0.2.25.223616-46) self-checks showing operational. SELinux is disabled with Android platform security patches showing “Up to Date”. The vendor security patches of course are “Out of Date”.
Please note that this build is for the S6 SM-G920F zerofltexx only at this time and there is no support provided.
Kudos once again to @eisy for the work put into updating this device within the /e/cosystem.
First of all: Thank you dear mcmd for your help and support! That is very nice of you! I appreciate your dedication very much.
And now I also have some great news:
The nice support here in the forum has unlocked me to link files here in the forum. And I also managed to compile the builds for the following other devices specifications today: zerofltecan, zeroltexx and zeroltecan. And I already uploaded them for interested people and for the e/OS community. Unfortunately still without SELinux enforcing. But the SELinux enforcement is then the next step I will work on.
The current builds I have created so far can be downloaded here:
I noticed that the battery of my smartphone drains much faster than with the old 0.18 build. Have you also noticed this? Am I just imagining it, or is it really like that? And if so, what is the reason? What is responsible for this? Can you recommend me an app, which is good to detect the battery consumption? I would like to find out if I can slow down the battery consumption.
on completing an updated build for this device- astonishing! Regarding SELinux, as I recall even the builds by