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
... in order to make them selectable in charging sounds settings.
This way the user can go back to the default sound.
Change-Id: Iced4614baddd9033e0772e4a4221ed48dea6fc57
* Note: msmnile is treated like msmnile because unlike other Qualcomm
codenames msmnile does not expand to 8150.
Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
* These are pretty useful for debugging config.fs
changes without rebuilding full system/vendor image.
Change-Id: I68fdeb2dc7c9f225784b55425407657645e34ac8
* 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
* 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 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 c77bb3a5ba.
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
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 lack of these whitelisted permissions causes a bootloop
when upgrading from earlier OS versions on devices that enforce
the whitelist.
Change-Id: I76b8fad5f0c49a7d008d19e7a116b5f19c75f739
* Add GRALLOC_USAGE_PRIVATE_WFD as valid gralloc bits for all
the platforms and GRALLOC_USAGE_PRIVATE_10BIT_TP only for the
UM 4.9-based platforms. Both are defined in the respective
display HALs (in gralloc/gralloc_priv.h) being the latter
only available for sdm845.
* This results in the same as applying https://goo.gl/SR7sFY,
but it's preferable since it makes use of our own method of
extending the valid gralloc 1.0 usage bits (see commit 59009f8).
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS is extended here on
purpose and as a bitwise OR of all the values in order not to
clear what might have been set in the device trees.
Change-Id: I5536f341e75088cc72ac369065011388f0a6d3f1
* libemoji doesn't exist
* libprotobuf-cpp-full is always built and part of VNDK
* librsjni is always built by renderscript
Change-Id: I379aa405f937d54fc7ab1fb7a120683e91f2bbac
For Example new devices need the new Sprint APNs, so add a new board flag for
them to set that will make the build system add the new APNs to
the APN config XML. If the flag is not set, continue to use the
old APNs.
To add or replace APNs, the custom_apns.py script has been
added. If CUSTOM_APNS_FILE is defined, custom_apns.py
is run and generates a new version of apns-conf.xml.
Change-Id: I7ff12a4342de2a7663b2b66fd627244214a8dc71
Test case: override ro.adb.secure in vendor/extra/product.mk
Before this patch, the override would not affect the resulting
property.
Change-Id: I0deb8a6865030b09ed6ba0ede1658319ca033e67
Kernel source settings should always come at BoardConfig population
time so things that use the variable later don't end up pointing to
an empty or wrong variable.
The following is also squashed in:
Author: Christopher N. Hesse <raymanfx@gmail.com>
Date: Fri Aug 10 00:23:54 2018 +0200
tasks: kernel: Honor prebuilt kernel flag
For devices that want to use a prebuilt kernel, TARGET_KERNEL_SOURCE
would still be set to TARGET_AUTO_KDIR, meaning the build system would
still try to build the kernel if TARGET_AUTO_KDIR was present.
Setting TARGET_PREBUILT_KERNEL indicates this is not wanted, so don't
attempt to do it.
Change-Id: Ic79b3ac1b9c946fd258ada43dce2b08bb74ea0d9
Change-Id: If046b86ff0d18c76898e90295be873a8379f678a
HALs are starting to move to blueprint files, which means that pathmap
ifeqs no longer work. This results in modules with the same name in
different platform HAL directories. Since these modules aren't used or
linked anywhere outside the HAL directories and a device's device.mk,
we can safely use a soong namespace to isolate the different HAL
directories' blueprints. This defines the PRODUCT_SOONG_NAMESPACES
make flag so make knows which namespace to look in as well.
Change-Id: I549e6da863465d79b12c7453aa169d5d963afa52
These variables are usually set in a device's BoardConfig, setting them
in qcom_target is at the very end of the "configuration process" which
results in them being unavailable to plenty of other configuration
"things" (ex. soong namespaces or soong config). Move them to right
after a device's BoardConfig has been found and loaded.
Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
* prepend-product-if-exists was developed specifically to handle some
special cases where Cyanogen Inc configuration ordering needed to be
handled ahead of the standard inclusion order.
Change-Id: Ia3e041fb9e3c84d0763d18e4a401121bc210b976
* Include all debug packages via PRODUCT_PACKAGES_DEBUG.
* Remove oprofiled and sqlite3 from the list, because the former
no longer exists and the latter is already part of
build/target/product/core_base.mk. Also remove gdbserver, since
it's already built by default.
Change-Id: Icde54061cd5a85d381b756364287344c3d216957
(cherry picked from commit e4d54e65cef919a77d51cce721eb741d2e512688)
* otasigcheck doesn't work on encrypted devices and makes
the zip installation fail since oreo.
* The build part of this was never ported to oreo.
This reverts commit aff5e54c4e.
Change-Id: I411f33c1db64844091c1692ef4706ae541925d4f
* Along with it, remove tune2fs as the tool is already part of
build/target/product/core_minimal.mk. Despite Google did quite
a big cleanup in master branch, it's still built by default.
Change-Id: I4cf1178c2f99eda5a45de4ba79705093de5cd9bf
Luca Stefani
jhenrique09
Michael Bestas
LuK1337
Rashed Abdel-Tawab
Isaac Chen
Ethan Chen
Nolen Johnson
Joey
blunden
razorloves
theimpulson
Bruno Martins
Han Wang
dianlujitao
Artem Borisov
Christopher N. Hesse
codeworkx
chrmhoffmann
Aaron Kling