If the build is invoked off-tree, like:

    . build/envsetup.sh
    export OUT_DIR=/some/other/dir/out
    export DIST_DIR=/some/other/dir/dist
    breakfast chagalllte
    mka \
        target-files-package dist

the bootanimation.zip is correctly generated in $OUT_DIR.

However, if the user overrides directories after breakfast, i.e:

    . build/envsetup.sh
    breakfast chagalllte
    mka \
        OUT_DIR=/some/other/dir/out \
        DIST_DIR=/some/other/dir/dist \
        target-files-package dist

the destination path of intermediate bootanimation.zip is still
controlled by $ANDROID_PRODUCT_OUT which is set by build/envsetup.sh.
This leads to a copy error and a failed build.

The fix overrides $ANDROID_PRODUCT_OUT by the always-known PRODUCT_OUT
(make variable defined in build/core/envsetup.mk), making it error-prone
to environment variable declaration.

Also, the "sh" invocation is replaced with generic make-variable
$(shell).

Change-Id: Ic94d1b538fc01946b628f9b5d776548a03acde97
Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Change-Id: I958a6bfd1087f5437f4074e614198bb622d476ce
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>

* Some TWRP releases expect -t parameter.

Change-Id: I5f4a55883b94e821bfcef06df7d121db1d6145a4

Change-Id: I6f37adc955856fa78e719eb30249800abe80020c

* The macros used in the file formerly called "qcom_utils.mk" are
  actually generic and not QCOM-specific. Move the QCOM_BOARD definitions
  to a QCOM-specific location, and name the remaning macros something more
  generic.

Change-Id: I6747bc9201e56b456caf251122057d7dbc233f1c

* There's actually not a whole lot QC-specific about these macros,
  make them available at definition.mk inclusion time rather than
  relying on BoardConfig to include them.
* Don't create a dependency on QCOM macros from a makefile
  that is included very early in the build process.

Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67

* Regenerated using development/tools/privapp_permissions/privapp_permissions.py

Change-Id: I9f49e92dbf92dc545dee782124d45db1e70df471

* http_prebuilt.mk appears to be long gone.

Change-Id: I8ca584fc1e468bb47164984bb363f0cf29750e68

* Instead of nesting ifeq/else/ifeq/else/endif/endif construction, make
  allows the more readable ifeq/else ifeq/else/endif construction. Use it
  instead.

Change-Id: Ifd2635929799db593e04a13827f05c97e95487e4

* These shouldn't be executable.

Change-Id: Idcb4e46f0ac69116b4837cd31f9f2e506b41a3f2

* Sort the file while we are at it.

Change-Id: I8dec9ece1c1523dcb77421b6912bbef91efb1485

Change-Id: I245138b19448a193f8cbd12d5d26db295a4f4cdd

Change-Id: I5f70280e72613a8f850cb3263c45e95e80cb8b3c
Signed-off-by: Erfan Abdi <erfangplus@gmail.com>

These configuration options are set based on the Google configurations
located in kernels
(ex. https://github.com/LineageOS/android_kernel_google_wahoo/blob/lineage-16.0/build.config)

This is composed of 2 parts:

Revert "kernel: Correct CROSS_COMPILE_ARM32 toolchain"

This reverts commit c77bb3a5.
This breaks builds when building with upstream commit
ad15006cc78459d059af56729c4d9bed7c7fd860. That commit fixes LD being
used from outside the path, however androidkernel toolchains don't
have elfedit. Google specifically doesn't use androidkernel, so we
need to follow them on this.

Set CROSS_COMPILE_PREFIX to aarch64-linux-android- for clang builds

Upstream commit ad15006cc78459d059af56729c4d9bed7c7fd860 makes the
kernel build system use GCC toolchains for elfedit, so we have to
actually use a real GCC toolchain, not the androidkernel one.

Change-Id: I79ac4ac47d3ba6c2abbc5ce40e56ed5c707295b4

 *From https://android.googlesource.com/device/google/wahoo/+/android-8.1.0_r29/apns-full-conf.xml
 *Removed A LOT of defunct APN settings. Most are MVNO's that use the major networks.
 *t-mobile -> Telekom
 *eplus & Blau & BASE -> o2

Change-Id: I7552ee091262bc53bb394d9fa89cdee1bdccb84f

Change-Id: I4ca1327604848a2b83a06f78655a68e53b9cb148
Signed-off-by: Joey <joey@lineageos.org>

Change-Id: I16a89aa555e62f105d888e87cb43afd26606076b

Change-Id: Icfb58abdda66636e220187269d32475e917eb11f
Signed-off-by: Joey <joey@lineageos.org>

Currently we handle the DTBO images from start to finish, including
AVB footers, and just drop them in $(PRODUCT_OUT)/dtbo.img when done.
While this works for the most part, we are limited in what we can do
with the DTBO images. For example non-A/B device recovery images must
have a copy of the DTBO image appended to recovery (see AOSP docs:
https://source.android.com/devices/bootloader/recovery-image ). This
means that we need to pass the pre-AVB dtbo image into
BOARD_PREBUILT_DTBOIMAGE in order to let the AOSP build system handle it.

This commit reworks the way the DTBO images are built, placing them at
$(PRODUCT_OUT)/dtbo-pre.img instead and setting BOARD_PREBUILT_DTBOIMAGE
to that path so the AOSP build system can pick the images up and sign
them and append to recovery (for applicable devices).

Change-Id: I8819d7cd92ba298de67dbc7f6b321917ba8524f1

 * The option is available in Status bar settings,
   as per our additions. Remove duplicate to improve UX.

Change-Id: I60a737617f192f5f0699ce50cfc3edc52c862492

 * Based off: https://android.googlesource.com/device/sample/+/master/etc/apns-full-conf.xml

Change-Id: Ie724a1f7f26d5bbcefb4459c5f92fcbc7c8bbff8

Change-Id: I02c8548ca4ac156846da1e4a0839240978b90e57
Signed-off-by: Joey <joey@lineageos.org>

* used by google bonito
* https://android.googlesource.com/device/google/bonito/+/refs/tags/android-9.0.0_r39/device-bonito.mk#18

Change-Id: Idd0b4640ee4896c86b25a5457fe889c28e49a283

Change-Id: Ia141fec1168e21726718cf11da83bb5ca0f68a56

Change-Id: I11f4d524a628f3fddb3a6a0c6fe645922123fc89

The lack of these whitelisted permissions causes a bootloop
when upgrading from earlier OS versions on devices that enforce
the whitelist.

Change-Id: I76b8fad5f0c49a7d008d19e7a116b5f19c75f739

* References : operators sites

Change-Id: If9b8df78bc5b35fa71432535dfae1a256e6beb62

This patch fixes the error generated path of modules in modules.dep.

Tested on Redmi Note 5(whyred).

Before:
/vendorlib/modules/test-iosched.ko:
/vendorlib/modules/mpq-adapter.ko:
/vendorlib/modules/ufs_test.ko: /vendorlib/modules/test-iosched.ko
/vendorlib/modules/rdbg.ko:
/vendorlib/modules/br_netfilter.ko:
/vendorlib/modules/gspca_main.ko:
/vendorlib/modules/mpq-dmx-hw-plugin.ko: /vendorlib/modules/mpq-adapter.ko

After:
/vendor/lib/modules/test-iosched.ko:
/vendor/lib/modules/mpq-adapter.ko:
/vendor/lib/modules/ufs_test.ko: /vendor/lib/modules/test-iosched.ko
/vendor/lib/modules/rdbg.ko:
/vendor/lib/modules/br_netfilter.ko:
/vendor/lib/modules/gspca_main.ko:
/vendor/lib/modules/mpq-dmx-hw-plugin.ko: /vendor/lib/modules/mpq-adapter.ko

Change-Id: I84d51f4c418fda0d99890db0fd5d976c42f54295

Update KT IMS apn for VoLTE

reference site:
https://android.googlesource.com/device/sample/+/refs/tags/android-9.0.0_r35/etc/apns-full-conf.xml#25304

Change-Id: Iaa7924aeb6038e7ecefe56042bc19af0b0db82c2

Change-Id: I8546d20098a0d117c5349dbeb73cfe1e72030990

Change-Id: If184d3e3c5e4545e8baba665366b59390718ac02
Signed-off-by: Christopher N. Hesse <raymanfx@gmail.com>
(cherry picked from commit 70e7015d73b8fdd5258732863012f7b06d8347f5)

Change-Id: Ie3103db1fcdd41e70024fceaf96d070f2d66577c

Added here:
https://github.com/LineageOS/android_build/blob/lineage-16.0/target/product/full_base_telephony.mk

Change-Id: If94b53efa9612bec8ef296a9d6df86add3b0f7c1

The ManagedProvisioning xml's were moved in Pie.
Also added missing managed_device and managed_user xml's.
This fixes 'Android for Work'.

REF: https://github.com/LineageOS/android_packages_apps_ManagedProvisioning/commit/ebe73b6e94e65fc82fde2c482844a05deb84e806
     https://github.com/LineageOS/android_frameworks_base/commit/b6a9f94d6718894fdd382708a9d87696f055e71e

Change-Id: If911b4ee1890600e47af73c7fe0fcca4dc73eb26

* Call the build system's build-image-kernel-modules function instead of
  redefining all of it inline ourselves.

Change-Id: Ifc4bd3c452393389a14174f4cc29a8f7ef064b93

Change-Id: Idb61ddbfd630401da09a0c3207aaab7e25bc4b14

* Check for any actual kernel modules, rather than just the presence of
  kernel modules being enabled as a kernel feature.

Change-Id: I6b7e82d5c59dd57621d9f9e2d1fd606997790d1c

* The directories used by the kernel module install rules are performed
  as part of the rules in the kernel build itself. This is likely a
  leftover from before kernel module install was separated.

Change-Id: Iee2f73a0f8e0f274b1c2931ba57277ff14d7f5cc

* The Pixel DTBO generation step should also be guarded by the full
  kernel build flag.

Change-Id: I06d230b1b32ad9d974f90bfe6ae82008f4454d83

Change-Id: I9c90de7820308542c7bb15605df519976dd04e0b