antec@antec-p6-2038fr:~/android/e/R$ source build/envsetup.sh
antec@antec-p6-2038fr:~/android/e/R$ lunch lineage_serranoltexx-user
antec@antec-p6-2038fr:~/android/e/R$ mka eos
) violated by allow vendor_fm_app bluetooth_prop:file { read getattr map open };
libsepol.report_failure: neverallow on line 10 of system/sepolicy/public/apexd.te (or line 9517 of policy.con
f) violated by allow system_app apexd:binder { call };
libsepol.report_failure: neverallow on line 9 of system/sepolicy/public/apexd.te (or line 9516 of policy.conf
) violated by allow system_app apex_service:service_manager { find };
libsepol.check_assertions: 119868 neverallow failures occurred
Error while expanding policy
15:53:35 ninja failed with: exit status 1
ninja: build stopped: subcommand failed.
#### failed to build some targets (03:07 (mm:ss)) ####
I have seen the output of envsetup.sh remain unchanged with edits. So this output is only really useful on the first run to check for gross error. You got such an error reported by envsetup.sh, Post #138. So the device.xml is not beyond suspicion but likely OK as builds were completing (oversize).
However I expect the envsetup.sh output to include the âextendrom intentionâ. Is that still seen ?
Which of the three options did you use to activate and configure extendrom ?
I prefer Option 2
lunch lineage_serranoltexx-user â is this a sign you are short of sleep ?
eng is suitable as you are âdevelopingâ for device seemingly too small for regular /e/OS.
no, last command was userdebug, but to post on the forum i have copied from an old note
thatâs somrthing i have missed !
.
but not the cause of the error during source build/envsetup.sh
antec@antec-p6-2038fr:~/android/e/R$ source build/envsetup.sh
including device/samsung/serranoltexx/vendorsetup.sh
************************************************** STARTING EXTENDROM **************************************************
ENABLE_EXTENDROM: true
EXTENDROM_PACKAGES: noApps noGmsCore noFakeStore noMozillaNlpBackend noNominatimNlpBackend noGsfProxy noTalkback noVOSK noPicoTTS noeSpeakTTS noMagicEarth noPdfViewer noOpenWeatherMapWeatherProvider noWebCalendarManager noNotes
EOS_EDITION:
EXTENDROM_SIGNING_PATCHES:
EXTENDROM_SIGNATURE_SPOOFING:
EXTENDROM_SIGSPOOF_RESET:
EXTENDROM_SIGSPOOF_FORCE_PDIR:
EXTENDROM_TARGET_VERSION: 11
EXTENDROM_TARGET_PRODUCT: lineage
SRC_TOP: ./
EXTENDROM_PRODUCT_DEVICE=serranoltexx
EXTENDROM_BOOT_DEBUG=
EXTENDROM_DEBUG_PATH=/data/vendor_de (will be suffixed with /boot_debug)
EXTENDROM_DEBUG_PATH_SIZE_FULL=5000 KB
EXTENDROM_DEBUG_PATH_SIZE_CRASH=500 KB
EXTENDROM_DEBUG_PATH_SIZE_KERNEL=500 KB
EXTENDROM_DEBUG_PATH_SIZE_SELINUX=500 KB
ERROR: missing required binary: aapt
bash stack trace (first occurence is likely where you should look at):
ERROR: last command ended with status >1< at line >142<
line 142 :
# check to see if the supplied product is one we can build
function check_product()
{
local T=$(gettop)
if [ ! "$T" ]; then
echo "Couldn't locate the top of the tree. Try setting TOP." >&2
return
fi
if (echo -n $1 | grep -q -e "^lineage_") ; then
LINEAGE_BUILD=$(echo -n $1 | sed -e 's/^lineage_//g')
else
LINEAGE_BUILD=
fi
export LINEAGE_BUILD
TARGET_PRODUCT=$1 \
TARGET_BUILD_VARIANT= \
TARGET_BUILD_TYPE= \
TARGET_BUILD_APPS= \
get_build_var TARGET_DEVICE > /dev/null
# hide successful answers, but allow the errors to show
}
i have pasted the content of your serranoltexx.xml in ./repo/local-manifest/eos.xml
and did repo sync in a terminal openened in the source root
antec@antec-p6-2038fr:~/android/e/R$ repo sync
fatal: duplicate path vendor/extendrom in /home/antec/android/e/R/.repo/manifest.xml
so i deleted ./repo/local-manifest/extendrom.xml
antec@antec-p6-2038fr:~/android/e/R$ repo sync
Fetching: 0% (0/874) 0:00 | ..working..error: hooks is different in /home/antec/android/e/R/.repo/projects/device/samsung/msm8930-common.git vs /home/antec/android/e/R/.repo/project-objects/android_device_samsung_msm8930-common.git
error.GitError: Cannot fetch --force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync device/samsung/msm8930-common` to proceed.
error: hooks is different in /home/antec/android/e/R/.repo/projects/kernel/samsung/msm8930-common.git vs /home/antec/android/e/R/.repo/project-objects/android_kernel_samsung_msm8930-common.git
error.GitError: Cannot fetch --force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync kernel/samsung/msm8930-common` to proceed.
Fetching: 100% (874/874), done in 2m29.829s
Fetching: 0% (0/2) 0:02 | ..working..error: hooks is different in /home/antec/android/e/R/.repo/projects/device/samsung/msm8930-common.git vs /home/antec/android/e/R/.repo/project-objects/android_device_samsung_msm8930-common.git
error.GitError: Cannot fetch --force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync device/samsung/msm8930-common` to proceed.
error: hooks is different in /home/antec/android/e/R/.repo/projects/kernel/samsung/msm8930-common.git vs /home/antec/android/e/R/.repo/project-objects/android_kernel_samsung_msm8930-common.git
error.GitError: Cannot fetch --force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync kernel/samsung/msm8930-common` to proceed.
Fetching: 100% (2/2), done in 4.241s
vendor/fdroid: Deleting obsolete checkout.
Checking out: 100% (874/874), done in 1m29.896s
error: Unable to fully sync the tree
error: Downloading network changes failed.
Try re-running with "-j1 --fail-fast" to exit at the first error.
fatal:
SyncError Aggregate Errors
--force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync device/samsung/msm8930-common` to proceed.
--force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync kernel/samsung/msm8930-common` to proceed.
--force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync device/samsung/msm8930-common` to proceed.
--force-sync not enabled; cannot overwrite a local work tree. If you're comfortable with the possibility of losing the work tree's git metadata, use `repo sync --force-sync kernel/samsung/msm8930-common` to proceed.
If the new serranoltexx.xml is different, there is still no need to have a complete clean out. New sources will come in with repo sync anything which does not match wonât get used.
Nothing can be lost by substituting the new manifest, repo sync --force-sync and onward to see if there is an improvement.
Cannot checkout LineageOS/android_kernel_samsung_msm8930-common:
ManifestInvalidRevisionError: revision refs/heads/lineage-18.1 in LineageOS/android_kernel_samsung_msm8930-common not found
You might continue with repo sync -j1 --fail-fast --force-sync and keep checking / searching the errors, you may get a resolution, or you may decide the environment is contaminated.
i cannot yet exactly list what apps i have removed from official and how, but i have a successfull e-1.16-r build !
i tried to build with at least : BlissLauncher, microG, Browser, Advanced Privacy, Account Manager, eDrive, Message, and without : Apps, Maps, PDFviewer (Mail for the moment)
(it donât have the expected filename, it is not located at the expected placeâŠ)
(â> not in the /out folder, but in /out/target/product/serranoltexx)
(â> not e-1.16-r 20231003-CUSTOM_MINI-serranoltexx.zip, but lineage_serranoltexx-ota-eng.antec.zip)*
it is in /.e/zips/serranoltexx/
⊠now i have to test it ⊠! âŠ
Edit : dirty flashâŠ
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p21 1.4G 1.2G 205M 87% /system/etc/gps_debug.conf
but i can share the screenshoot to to the computer.
i will rebootâŠ
same thing, it is a Launcher issueâŠ
but i can use âleboncoinâ !!!
because i can reach âsettingsâ from the top bar, then âinstalled apps proprietiesâ and load themâŠ
bliss donât appear in the App list, delete Trebuchet cache and data does nothing betterâŠ
i am thinking about a factory reset, Grrr ! not yetâŠ
i install Openlauncher⊠it worksâŠ
i decide to reflash the build⊠wipping cache and dalvic this timeâŠ
boot on OpenLauncher still no BlissLauncher in the App_ListâŠ
i will archive my first own /e/.ZIP and rebuildâŠ
still thinking about the pertinence of a factory-reset ⊠but no.
