Android 15.0.0 Release 6 (AP4A.241205.013)
# -----BEGIN PGP SIGNATURE-----
#
# iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ1IssQAKCRDorT+BmrEO
# eO5/AJ9rMGAZO6hpWnAQeLFKjKwpbj1qiACfVRU7e0KtnSmXfn00k3wEc2acjpo=
# =pIC7
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri Dec 6 00:44:01 2024 EET
# gpg: using DSA key 4340D13570EF945E83810964E8AD3F819AB10E78
# gpg: Good signature from "The Android Open Source Project <initial-contribution@android.com>" [marginal]
# gpg: initial-contribution@android.com: Verified 2483 signatures in the past
# 3 years. Encrypted 4 messages in the past 2 years.
# gpg: WARNING: This key is not certified with sufficiently trusted signatures!
# gpg: It is not certain that the signature belongs to the owner.
# Primary key fingerprint: 4340 D135 70EF 945E 8381 0964 E8AD 3F81 9AB1 0E78
# By Krzysztof Kosiński (3) and others
# Via Android Build Coastguard Worker (29) and others
* tag 'android-15.0.0_r6': (30 commits)
Delete TARGET_CPU_VARIANT_RUNTIME.
Add input event profile to mitigate input latency of input threads
gs201: avoid vector<const T>
Delete PRODUCT_FULL_TREBLE_OVERRIDE.
bcl: remove charging debugfs data logging
Switch from the BFQ to the mq-deadline I/O scheduler
extended_log: update directory permissions for gs201
Revert "Add soong config use_google_qns in device/google/gs201/d..."
Add soong config use_google_qns in device/google/gs201/device.mk
Delete mapper4 manifest
usb: correct sys.usb.controller sysprop
The "messaging" package is being removed.
Migrate dump_power_gs201.sh contents into cpp for improved speed
Remove BCL from thermal
Add FSTAB_OWNERS and update OWNERS to include Android.bp
Limit hub tuning when enable_hub is enabled
init: gs201: Mask VDROOP1 for GPU CLK Divider
Upgrade IDisplay to V13
BoardConfig-common.mk: Enable Lazy RCU
Add soong config variable for PowerAnomalySitril
...
Conflicts:
device.mk
dumpstate/dump_power_gs201.sh
Change-Id: I2b565f07529d250f57286faaba3bb694c0551222
Since the TARGET_RECOVERY_UI_LIB for each device is not exactly the
same, and most of the modules in it contain `soong_namespace{}` to
avoid conflicts between different devices, after converting
`librecovery_ui_ext` from Android.mk to Android.bp, it needs to be
changed to a `fully qualified name` in order to correctly use the
corresponding module.
Flag: EXEMPT refactor
Bug: 339143524
Test: m -j librecovery_ui_ext
Change-Id: I1a41a48feb26771127f9603ae5ae226d2de61065
Set the full module path of libacryl_hdr_plugin and the include dir for
lobacryl conversion to soong. It will take effect after aosp/3286932 and
aosp/3287183 merged.
Bug: 370414334
Test: lunch aosp_panther-trunk_staging-userdebug ; m libacryl_hdr_plugin libacryl
Change-Id: I77d3e23d2c8fd956d7207e2aa486577646a18763
Set the full module path of libacryl_hdr_plugin and the include dir for
lobacryl conversion to soong. It will take effect after aosp/3286932 and
aosp/3287183 merged.
Bug: 370414334
Test: lunch aosp_panther-trunk_staging-userdebug ; m libacryl_hdr_plugin libacryl
Change-Id: I77d3e23d2c8fd956d7207e2aa486577646a18763
Disable cgroup kernel memory accounting to avoid unnecessary overhead
similar change ag/22891292 but now back-port to gs201
Flag: NONE kernel config
Bug: 373232814
Test: pts-tradefed run commandAndExit pts -m PtsPerfWbsTestCases
-t com.google.android.perfwbs.pts.KernelModuleTest
and alternative tests on forrest.
Change-Id: I306b3e608655dc9e5f868a1f1a79e60e5b9b40fd
This variable only does something when it differs from
TARGET_CPU_VARIANT. Setting it to the same values doesn't do
anything.
Bug: 368635026
Test: presubmit
Change-Id: I15a3b367df0a5be2de23f535f9f9df0866dd306a
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial gs201 devices (Pixel 7)
launched with API level 33.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: I35bdec5d9e21abb25f12c0ad9681d3dee01aee67
Bug: 340860065
Flag: EXEMPT this is a boot time parameter
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: Id8ce33fac746f3a873c69461f7f9054b274603d9
Placing the fips140.ko at the same level as other kernel modules makes
it easier for automation tools to handle all of them.
Bug: 331791671
Change-Id: I7d69226d594fe068a6ccb99bb5a29620468f4aed
Signed-off-by: Qian-Hao Huang <qhhuang@google.com>
assign system_dlkm.modules.blocklist to BOARD_SYSTEM_KERNEL_MODULES_BLOCKLIST_FILE
located from kernel prebuilts folder
Bug: 267429528
Bug: 322457552
Change-Id: I912f1a8e0df12e4614c74b870921ca0b47b8383e
Signed-off-by: Robin Peng <robinpeng@google.com>
- BOARD_SYSTEM_KERNEL_MODULES_LOAD is for GKI modules
- BOARD_VENDOR_KERNEL_RAMDISK_KERNEL_MODULES_LOAD should not contains GKI modules
Bug: 267429528
Bug: 322457552
Change-Id: Ib5da01f861a34edec07e2a958f153c876e5cef10
Signed-off-by: Robin Peng <robinpeng@google.com>
- Include mediacodec_samsung setting from gs-common
- Enable Codec2 HIDL 1.2 from BoardConfig and update
manifest hidl version for samsung.hardware.media.c2
Bug: 318793681
Test: run cts -m CtsMediaDecoderTestCases
Test: run cts -m CtsMediaPlayerTestCases
Test: run vts -m vts_treble_vintf_vendor_test
Change-Id: I1f947d2eb75bd4d75d9db1d39b0b083d32f8032f
a15331d574
Compile ArmNN shim over the support library.
Remove settings for the old HIDL backend.
The new ones will be in the gs-common folder.
Test: Local run of CtsNNAPITestCases
Test: Local run of VtsHalNeuralnetworksTargetTest
Test: Local run of MLTS Benchmark
Bug: 283724775
Change-Id: Ic9f1c26345e52df8b6ef75e2a8261d71a8950c72
This revert was created by Android Culprit Assistant. The culprit was identified in the following culprit search session (http://go/aca-get/123b2665-83ef-4fd0-904d-a0d8c5782db9).
Change-Id: Ib69a94a6a2a8a087e3c2e7e5539045ec751e4a8f
Compile ArmNN shim over the support library.
Remove settings for the old HIDL backend.
The new ones will be in the gs-common folder.
Test: Local run of CtsNNAPITestCases
Test: Local run of VtsHalNeuralnetworksTargetTest
Test: Local run of MLTS Benchmark
Bug: 283724775
Change-Id: I3652eceb14d06a3e909444edc21ad86d9378bc6c
Currently, all gs201 targets have a system_dlkm image but their
modules are stored on the vendor_dlkm partition. In order to
support the staging kernel, modules have to be split across the
system/vendor_dlkm images.
This fix enables targets to define modules on the system_dlkm image.
If so, the system/vendor_dlkm split will be honored. Otherwise, all
modules will remain stored on the vendor_dlkm image.
Test:
- Build and flash aosp_panther, no errors.
- Build and flash a target defining BOARD_SYSTEM_KERNEL_MODULES, ensure
modules are correctly split across the two dlkm partitions.
Bug: 285177263
Change-Id: I80131d97073ce666a9228a47c2fff94b76139a64
Signed-off-by: Samuel Gosselin <sgosselin@google.com>
USE_ANGLE in moved to core.mk across platform, this patch updated the
usage of it in device.mk.
Bug: 270994705
Test: atest CtsAngleIntegrationHostTestCases
Change-Id: I58d57cd5e58d0a4706e8771ffb5e903795954f19
The pvmfw partition is expected to be kept in sync with the system
partition so, instead of having it as a standalone partition (covered by
vbmeta.img), add it to vbmeta_system.
Bug: 275497314
Test: TH
Change-Id: I2ff0fc14b9c9f8cf09907369a82f16d22a8c8297
Add adaptive haptics config parameter to the build environment
Bug: 198239103
Test: atest VibratorHalCs40l26TestSuite
Change-Id: Id2a9e0d346c4722651f9d0a03e7c4f4aa5ac2861
Signed-off-by: Chris Paulo <chrispaulo@google.com>
In aosp, the name of the variable changed from
FORCE_MULTILIB_FIRST_ON_DEVICE to IGNORE_PREFER32_ON_DEVICE.
So actually modify this so the new devices don't have 32 bit
servers.
Test: Verified that drmserver/mediaserver are 64 bit processes.
Change-Id: I282f5129bcc91d99e924f514b01fc4e7e37e9ea9
When $(TARGET_KERNEL_DIR) contains:
* boot.img
then use those as prebuilt boot images for the target build.
Bug: 242812258
Change-Id: I10ccfaacfc77cc37eee085b27575fae515ceb088
Add support for copying prebuilt kernel modules like fips140.ko into the
vendor kernel ramdisk. These kernel modules are different in the following
ways:
- They do not appear in vendor_kernel_boot.modules.load provided by the
kernel build system.
- We want to put their names at the very beginning of the output
modules.load file to ensure that they are loaded prior to all other
modules.
We define a new Makefile variable named
BOARD_PREBUILT_VENDOR_KERNEL_RAMDISK_KERNEL_MODULES. For every filename
on this list, we verify that the file exists in $(KERNEL_MODULE_DIR),
and if it does, we include its name in the modules.load for the vendor
kernel boot ramdisk.
Bug: 194712883
Change-Id: I91a1d834b32717d32621d0a67da9052324cab20c
