Also fix KERNEL_MAKE_FLAGS not being used by the kernel make command

Change-Id: I8786d6c1de6652f87a02c990c4b56f62b0cc0203

* It's not behaving properly and I don't feel like fixing it.

Change-Id: I634a9abe99299d66a94f9d1ff7d8011476646933

Change-Id: I869d9d24a61088762ea5cb1a3cc655ef11b0c521

Change-Id: I52c7b124ff8364464643c51b3f17dba4e4e49435

Change-Id: I149508317c4f0312e88faf5324275867e79e35e9

Change-Id: I1ca080e5addcc0876d7346f3cf09db8e8af39312

(config_tether_upstream_automatic=true)

Test: as follows
    - built, flashed, booted
Bug: 32163131
Bug: 62648872
Bug: 63282480
Bug: 110118584
Bug: 110260419

Change-Id: I604cda53d6d37a33de3e3ccc65c0da781d21278b

* It doesn't exist anymore.

Change-Id: I6f855f097febbc986dd8d94d862f154842641d1b

Required for new commits on frameworks/native

* Fix lag during screen recording on some platforms
* Fix screen flickering after disconnecting from Android Auto on some platforms

Change-Id: Ia0ed0bbfda44fb5ccb184ace854ec1bf9a7d819a

Change-Id: I1ec1ae4618f6f2a511a34ca0673600a65f9a971f

... in order to make them selectable in charging sounds settings.
This way the user can go back to the default sound.

Change-Id: Iced4614baddd9033e0772e4a4221ed48dea6fc57

 * Removed long ago.

Change-Id: Ic0becb9b0e2120ff8032fb046d6b0f211b82813f

dictionary is built from 4y old dictionaries which are in LatinIME
https://github.com/LineageOS/android_packages_inputmethods_LatinIME/blob/lineage-16.0/dictionaries/pl_wordlist.combined.gz
https://github.com/LineageOS/android_packages_inputmethods_LatinIME/blob/lineage-15.1/dictionaries/pl_wordlist.combined.gz
using dicttool,
dicttool build was possible thanks to
https://android.googlesource.com/platform/packages/inputmethods/LatinIME/+/a92d0f926269264e578c9162c5df230cafb99b7c

Change-Id: I4bffbb10e06c904ad58877ff920e581caa958d67

* For addonsu.

Change-Id: Ic4c701cdfe1126870258182df631192e06527fe5

* cough * someone forgot to update permissions whitelist again.

Change-Id: Iedcdb0568ea1b9924144841a8d20ca6f05bbe29b

* Note: msmnile is treated like msmnile because unlike other Qualcomm
  codenames msmnile does not expand to 8150.

Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c

* This fixes dirty boot image rebuilding on devices
  with CONFIG_LOCALVERSION_AUTO=y and any driver
  set to =m.
* Basically appending `cat include/config/kernel.release`
  to modules path makes sure that our find does not
  return old modules which would make cp fail with
  'cp: will not overwrite just-created' message.

Change-Id: Ifb79d33b95d7671d8b2d6633644c8b8290d1f442

Co-authored-by: Erfan Abdi <erfangplus@gmail.com>
Change-Id: I4881658d303b6c5c7f0b141beb50c1e9100af611

* These are pretty useful for debugging config.fs
  changes without rebuilding full system/vendor image.

Change-Id: I68fdeb2dc7c9f225784b55425407657645e34ac8

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