Thanks Piero. For the docker way I found instructions but not yet for the repo way… can you guide me?
Not directly because i have no experience building /e/, (only postmarketOS that is less complex),
i fantasm to build /e/ for 3 years but hasn’t hardware nor bandwidth, i recently aquired a PC 4x3,3Ghz 8Gb, and just ordered a modem, so maybe in some weeks/months ?..
Look like others encountred the same issue :
https://forum.xda-developers.com/search/66780135/?q=PRODUCT_PACKAGES&o=relevance
Have you tried vendor e ?
A Ubuntu (/Debian) environment which built standard LineageOS would need to be sure to have the full package list starting on line 156 in the dockerfile https://gitlab.e.foundation/e/os/docker-lineage-cicd/-/blob/master/Dockerfile.community.
apt-get install -y bc bison bsdmainutils build-essential ccache cgpt clang cron \
curl flex g++-multilib gcc-multilib git git-lfs gnupg gperf imagemagick kmod jq \
lib32ncurses5-dev libncurses5 lib32readline-dev lib32z1-dev libtinfo5 liblz4-tool \
libncurses5-dev libsdl1.2-dev libssl-dev libxml2 \
libxml2-utils lsof lzop maven pngcrush \
procps python python3 rsync schedtool squashfs-tools software-properties-common wget xdelta3 xsltproc yasm \
zip zlib1g-dev
My guess is that (for unknown reasons, loosely speaking) repo init has not yet pulled in the full /e/ repositories.
That list looks like one which I expect to find in /vendor/lineage/config/common.mk
I runned repo sync again and do not have this error anymore… but other build errors I’m following up 
1 Like
Up to now I could fix a lot of build errors, but now I’m stucked with the errors with the eOS Apps…any ideas?
[ 62% 60072/96027] Verifying uses-libraries: prebuilts/prebuiltapks/AccountManager/davx5-ose-4.2.6-ose-release-unsigned.apk
FAILED: out/target/common/obj/APPS/AccountManager_intermediates/enforce_uses_libraries.status
/bin/bash -c “(rm -f out/target/common/obj/APPS/AccountManager_intermediates/enforce_uses_libraries.status ) && (build/soong/scripts/manifest_check.py --enforce-uses-libraries --enforce-uses-libraries-
status out/target/common/obj/APPS/AccountManager_intermediates/enforce_uses_libraries.status --aapt out/host/linux-x86/bin/aapt --optional-uses-library androidx.window.extensions --optional-use
s-library androidx.window.sidecar --dexpreopt-config out/target/product/gts210wifi/obj/JAVA_LIBRARIES/androidx.window.extensions_intermediates/dexpreopt.config --dexpreopt-config out/target/product/gts21
0wifi/obj/JAVA_LIBRARIES/androidx.window.sidecar_intermediates/dexpreopt.config prebuilts/prebuiltapks/AccountManager/davx5-ose-4.2.6-ose-release-unsigned.apk )”
zipro W 08-09 19:58:41 386936 386936] Error opening archive prebuilts/prebuiltapks/AccountManager/davx5-ose-4.2.6-ose-release-unsigned.apk: Invalid file
ERROR: dump failed because no AndroidManifest.xml found
error: Command ‘[‘out/host/linux-x86/bin/aapt’, ‘dump’, ‘badging’, ‘prebuilts/prebuiltapks/AccountManager/davx5-ose-4.2.6-ose-release-unsigned.apk’]’ returned non-zero exit status 1
[ 62% 60075/96027] Verifying uses-libraries: prebuilts/prebuiltapks/AdvancedPrivacy/Advanced_Privacy-1.14.0-e-release.apk
FAILED: out/target/common/obj/APPS/AdvancedPrivacy_intermediates/enforce_uses_libraries.status
/bin/bash -c “(rm -f out/target/common/obj/APPS/AdvancedPrivacy_intermediates/enforce_uses_libraries.status ) && (build/soong/scripts/manifest_check.py --enforce-uses-libraries --enforce-uses-li
braries-status out/target/common/obj/APPS/AdvancedPrivacy_intermediates/enforce_uses_libraries.status --aapt out/host/linux-x86/bin/aapt --optional-uses-library androidx.window.extensions --opti
onal-uses-library androidx.window.sidecar --dexpreopt-config out/target/product/gts210wifi/obj/JAVA_LIBRARIES/androidx.window.extensions_intermediates/dexpreopt.config --dexpreopt-config out/target/produ
ct/gts210wifi/obj/JAVA_LIBRARIES/androidx.window.sidecar_intermediates/dexpreopt.config prebuilts/prebuiltapks/AdvancedPrivacy/Advanced_Privacy-1.14.0-e-release.apk )”
zipro W 08-09 19:58:41 386938 386938] Error opening archive prebuilts/prebuiltapks/AdvancedPrivacy/Advanced_Privacy-1.14.0-e-release.apk: Invalid file
ERROR: dump failed because no AndroidManifest.xml found
error: Command ‘[‘out/host/linux-x86/bin/aapt’, ‘dump’, ‘badging’, ‘prebuilts/prebuiltapks/AdvancedPrivacy/Advanced_Privacy-1.14.0-e-release.apk’]’ returned non-zero exit status 1
[ 62% 60076/96027] Verifying uses-libraries: prebuilts/prebuiltapks/Apps/AppLounge-2.5.8-release.apk
FAILED: out/target/common/obj/APPS/Apps_intermediates/enforce_uses_libraries.status
/bin/bash -c “(rm -f out/target/common/obj/APPS/Apps_intermediates/enforce_uses_libraries.status ) && (build/soong/scripts/manifest_check.py --enforce-uses-libraries --enforce-uses-libraries-status o
ut/target/common/obj/APPS/Apps_intermediates/enforce_uses_libraries.status --aapt out/host/linux-x86/bin/aapt --optional-uses-library androidx.window.extensions --optional-uses-library androi
dx.window.sidecar --dexpreopt-config out/target/product/gts210wifi/obj/JAVA_LIBRARIES/androidx.window.extensions_intermediates/dexpreopt.config --dexpreopt-config out/target/product/gts210wifi/obj/JAVA_L
IBRARIES/androidx.window.sidecar_intermediates/dexpreopt.config prebuilts/prebuiltapks/Apps/AppLounge-2.5.8-release.apk )”
zipro W 08-09 19:58:41 386939 386939] Error opening archive prebuilts/prebuiltapks/Apps/AppLounge-2.5.8-release.apk: Invalid file
ERROR: dump failed because no AndroidManifest.xml found
error: Command ‘[‘out/host/linux-x86/bin/aapt’, ‘dump’, ‘badging’, ‘prebuilts/prebuiltapks/Apps/AppLounge-2.5.8-release.apk’]’ returned non-zero exit status 1
[ 62% 60077/96027] Verifying uses-libraries: prebuilts/prebuiltapks/BlissIconPack/app-release-unsigned.apk
FAILED: out/target/common/obj/APPS/BlissIconPack_intermediates/enforce_uses_libraries.status
/bin/bash -c “(rm -f out/target/common/obj/APPS/BlissIconPack_intermediates/enforce_uses_libraries.status ) && (build/soong/scripts/manifest_check.py --enforce-uses-libraries --enforce-uses-libraries-
status out/target/common/obj/APPS/BlissIconPack_intermediates/enforce_uses_libraries.status --aapt out/host/linux-x86/bin/aapt prebuilts/prebuiltapks/BlissIconPack/app-
release-unsigned.apk )”
zipro W 08-09 19:58:41 386942 386942] Error opening archive prebuilts/prebuiltapks/BlissIconPack/app-release-unsigned.apk: Invalid file
ERROR: dump failed because no AndroidManifest.xml found
error: Command ‘[‘out/host/linux-x86/bin/aapt’, ‘dump’, ‘badging’, ‘prebuilts/prebuiltapks/BlissIconPack/app-release-unsigned.apk’]’ returned non-zero exit status 1
[ 62% 60078/96027] Verifying uses-libraries: prebuilts/prebuiltapks/BlissLauncher/BlissLauncher-1.14.0-apiS-release.apk
FAILED: out/target/common/obj/APPS/BlissLauncher_intermediates/enforce_uses_libraries.status
/bin/bash -c “(rm -f out/target/common/obj/APPS/BlissLauncher_intermediates/enforce_uses_libraries.status ) && (build/soong/scripts/manifest_check.py --enforce-uses-libraries --enforce-uses-libraries-
status out/target/common/obj/APPS/BlissLauncher_intermediates/enforce_uses_libraries.status --aapt out/host/linux-x86/bin/aapt prebuilts/prebuiltapks/BlissLauncher/Blis
sLauncher-1.14.0-apiS-release.apk )”
zipro W 08-09 19:58:41 386943 386943] Error opening archive prebuilts/prebuiltapks/BlissLauncher/BlissLauncher-1.14.0-apiS-release.apk: Invalid file
ERROR: dump failed because no AndroidManifest.xml found
error: Command ‘[‘out/host/linux-x86/bin/aapt’, ‘dump’, ‘badging’, ‘prebuilts/prebuiltapks/BlissLauncher/BlissLauncher-1.14.0-apiS-release.apk’]’ returned non-zero exit status 1
19:59:12 ninja failed with: exit status 1
I am not sure … a bunch of lines like this makes me think of
repo forall -c ‘git lfs pull’ --are you doing this after every repo sync ?
Mentioned Week 14, 2023: Development and Testing Updates
See the “hidden” paragraph
ROM Builders - Unofficial and Custom
repo forall -c ‘git lfs pull’ did not work. I download the prebuilds app now manually and restarted build… finger crossed
1 Like
94%…
ERROR: Dex2oat failed to compile a boot image.It is likely that the boot classpath is inconsistent.Rebuild with ART_BOOT_IMAGE_EXTRA_ARGS=“–runtime-arg -verbose:verifier” to see verification errors.
23:32:14 ninja failed with: exit status 1
I suppose I ran out of memory?
The command runs with no trace to the terminal.
After completing a repo sync, you will have to run repo forall -c ‘git lfs pull’
Running the command directly after repo sync may help to ensure you have a connection to the server.
Re Dex2oat error … as I found by a search
export CPU_SSE42=false
Thanks guys for all your help. I commented out in /lineageOS/art/build
the two msse4.2 lines to
// “-msse4.2”,
but might also forget to write `export CPU_SSE42=false in the terminal.
And the good news is, build was now successful:
[100% 96027/96027] build bacon
Package Complete: out/target/product/gts210wifi/e-1.14-t-20230810-UNOFFICIAL-gts210wifi.zip
3 Likes
I will test in the next days…
Here are the instructions again:
Is there a chance, that the version T813 of the S2-Tablet gets re-supported by /e/os? That would be really great since this Tablet is still in 2023 a powerful and very slim & light peace of Hardware…
There are probably no official maintainer
This rocks! Thank you ronnz98 for getting this started!!
I’m still using the very same tab (Exynos 5433) on my home network and could not agree more – it is very powerfull, slim and light.
This could be the to be announced /e supported tablet 
I will report back, once I got it running – any issues so far?
Cheers
This goes to:
(gts28vewifi)
Released 2016
Specifications
SoC Qualcomm MSM8976 Snapdragon 652
It should be:
Info about gts210wifi | LineageOS Wiki
Samsung Galaxy Tab S2 9.7 (Wi-Fi) (gts210wifi)
Released September 2015
Specifications
SoC Samsung Exynos 5433
Up to now I could not get the [UNOFFICIAL e-1.14-t] (gts210wifi) 3G/32G
to boot. I would even show up e logo.
Anyone able to help me with debugging?
The latest LOS20 version for this device from 13-AUG does work fine
Are you using TWRP?
It has a file manager, does logs during flashing… you can mount system read only and look for logs, from when it tried to boot, maybe!?
Or do you have adb working during the black screen?
yes I’m using TWRP. Unfortunately I cannot connect via USB (charging does work though).
I did install via SD card.
I will try again and search for log files. The logs during flash looked fine
Do you have version number and, or link, please?
(I only asked about TWRP, after someone here said he had never heard of it – only ever learned adb, I gues)
I am still working on several S7 and S7edge, so not tried flashing the tablet, yet.