Setup‐Deprecated

option 1: (DEPRECATED) just use an Android makefile

this option is marked deprecated and should not be used anymore. Please switch to option 2 which is the only recommended approach these days.

add the following in your device/<vendor>/<model>/device.mk (or any other existing device mk file):

# Enable extendrom
# !never use quotes here!
ENABLE_EXTENDROM := true
<add-any-EXTENDROM-flag> := <EXTENDROM-flag-value>

$(call inherit-product, vendor/extendrom/config/common.mk)

obviously change <add-any-EXTENDROM-flag> := <EXTENDROM-flag-value> with the extendrom feature(s) you want to add.

Example:

# Enable extendrom
# !never use quotes here!
ENABLE_EXTENDROM := true
EXTENDROM_PACKAGES := \
    F-Droid \
    AuroraStore

add the following section to your device/<vendor>/<model>/vendorsetup.sh:

########### extendrom section ###########
$PWD/vendor/extendrom/er.sh

option 3: (DEPRECATED) mix Makefile & vendorsetup.sh

extendrom is flexible enough to also mix both options above.

Just be aware that vendorsetup.sh will take precedence - so always wins when a flag has been defined with both options.

(DEPRECATED) Android makefile / mixed with vendorsetup.sh

whenever you change something in device/<vendor>/<model>/<device>.mk you HAVE TO apply these changes first.

The regular build process should always be like:

source build/envsetup.sh  # (initializes 
the android build aliases)
lunch lineage_j5y17lte-user # (initializes the makefiles including the extendrom changes)
source build/envsetup.sh # (activates the extendrom settings)

mka otapackage
# (or mka eos when buildin /e/)

Note:
brunch or breakfast will work as well ofc