* In order to automatically restart the system when pushing SystemUI, the
path must actually be correct
* Since android 10 it's in system/*product*/priv-app and 11 will move
it again, so just match it anywhere
* Make framework also location independent
Change-Id: I4a9eb1edbbb21ab8abe17815c606921f7a538b7f
As md5 is not considered as secure since some time, and sha256 is
industry standard, lets switch over here too.
Change-Id: I22015be20126a4348affa5ef97e2c28fbd7b4717
breakfast may get stuck if the first breakfast for a target is
interrupted before cloning but after adding repositories to local
manifest. Re-doing breakfast skips syncing the repositories if
they're added to the manifest even if not cloned.
Change-Id: Ifefd08fa6da8785c1d5de0b27ac1a08a782f21d6
Makefiles combining core lineage and automotive packages.
Can be included by devices to turn them into Automotive builds.
Emulator targets demonstrate using these makefiles and form a basis for Automotive GSIs.
Change-Id: Ib5d35dfe4de8c459e4e14a7ba6f0b0e682e0d912
The check for official builds now only affects the case where a prebuilt
kernel was actually used, not the case where a device builds a kernel
from source as normal.
The check has also been turned around so that it only fails the build if
it's actually an official build, not an unofficial one.
Change-Id: I1280b16b90589742c2abe7f3f6f5975a3aaeea03
* TARGET_FORCE_PREBUILT_KERNEL should be useful when you don't have ready kernel sources (OEM releasing broken sources or releasing them lately)
* It lets you use kernel sources for userspace generated headers (generated_kernel_headers) while keeping using prebuilt kernel
* Keep in mind that generated kernel headers may not align with the ABI of kernel you're including
* This commit also partially revert commit a836d79, where TARGET_KERNEL_SOURCE would have been unset if TARGET_PREBUILT_KERNEL was defined (we already check in kernel.mk if kernel sources are present anyway)
Change-Id: I84acae890dabb5b9dbd48143ad58f6420c0cef75
* This is needed for VNDK27, and other older,
hackier Treble implementations.
* We can't include `legacy_gsi_release.mk` as it's included
in the `aosp_${ARCH}_ab` targets themselves, unlike the standard
`aosp_${ARCH}` targets which guard `gsi_release.mk`'s inclusion
with `aosp_${ARCH}` product guards.
Change-Id: I16c5983c18110b24eef84e382e0ae6852efb03c3
Mini documentation:
List the names of boot modules in BOOT_KERNEL_MODULES to add them
to vendor_boot.
All modules still end up in their primary location (normally
vendor/lib/modules). Boot modules will be kept here as duplicates.
The list of boot modules is then depmod'ed and copied to the
vendor ramdisk.
The file modules.load is created from
BOARD_$(IMAGE)_KERNEL_MODULES_LOAD as the ordered list of modules
to be loaded form that location, either parsed by a modprobe script
or by init itself (only boot modules)
When using vendor_boot modules, vendor/lib/modules/modules.load
should list all modules but boot modules.
Also don't clear the output directory, because one might want to
push a modules.blocklist there.
Change-Id: I89a4aad42a6585a572812f1d7e89f5d78931e1e6
* Move $PATCHELF exporting from oat2dex to setup_vendor
* Since it requires $HOST to be set, let's make it global, so oat2dex can also use it
Change-Id: I4556a3c19cd01c9b3a68d358d19a361217d9c3c1
Some legacy devices experiences bad lag unless this is disabled.
Disable it with:
TARGET_DISABLE_POSTRENDER_CLEANUP := true
Change-Id: I2b40dc4cbcab06fb293d1f407321af2fae846a51
* We're having a race with the kernel module build and vendor.img
generation, and sometimes when vendor.img wins it won't include
any modules in the image, which leads to all sorts of breakage
Change-Id: I2cdde96530aa8e47351cace76352788cde631058
* Thermal HAL was converted to HIDL service and .mk to .bp,
devices can override it by using a different named service
Change-Id: Ia3e0d86e791555992e7889f33f7d55f224b9a582
- The goal of specifying kernel image name was to whether kernel needs
appended dtb or not, which is not something required if the kernel is
prebuilt
Ref:
[0]: Commit edc1cebc2f
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
Change-Id: I6b43756a2eac59729a67b5f80dac112f8b6bcc5b
The mk files in vendor/qcom/opensource/data-ipa-cfg-mgr were
converted to bp, so this is needed to avoid duplicate module
build errors on devices that use a different data-ipa-cfg-mgr hal.
Co-authored-by: Christian Oder <myself5@carbonrom.org>
Change-Id: Ib4d566e43145745afac0259c95c0a563779fa3bd
* This reverts commits 7ef0e170 and 4ed4605 and removes relevant flags
to prepare for using Soong config variables as per Google's docs
Change-Id: Ib6ae5a8a922104d37f8d0e08242b428eb129785c
This reverts commit f3f7eb2d87.
Support for this in fw/native has been ported in the previous branch
and is very unlikely that will be done or even needed for R.
Change-Id: I9c9709e323d6a27f3c9196887af7ab0ffa1819e9
This reverts commit fd27bb4912.
Should have never been added. This time should be done with a prop.
Change-Id: I72a4563834447d4dbeda66dfb232b0541727cb55
* The new refactored function doesn't work with shell expanded
variables, like our $$modules.
* This is the _easy_ fix.
A proper fix would imply generating the module list into a make variable
from the shell variable, but with kati that looks unfeasable (to me...)
Change-Id: I8198c62fa93ad94d4b9bf7175fe5eea452c243ea
LuK1337
Chirayu Desai
Bruno Martins
Michael W
Julian Veit
marcost2
Timi Rautamäki
Tom Pratt
Sebastiano Barezzi
Tim Schumacher
JamieHoSzeYui
Dhina17
Nolen Johnson
Alessandro Astone
TheMalachite
Michael Bestas
Jan Altensen
Arne Coucheron
Volodymyr Zhdanov
Michael Bestas
Aayush Gupta
razorloves
Pig