Android 15.0.0 Release 6 (AP4A.241205.013)
# -----BEGIN PGP SIGNATURE-----
#
# iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ1IssQAKCRDorT+BmrEO
# eGMPAJ0QCkI3LO8goenx8IVscY5slyvypwCfZPPsAYYuAObV7/M/d1gUi/BEM6k=
# =igbk
# -----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 Herbert Xue (6) and others
# Via Android Build Coastguard Worker (48) and others
* tag 'android-15.0.0_r6': (72 commits)
Set auto prefer idle task name
Delete TARGET_CPU_VARIANT_RUNTIME.
Add input event profile to mitigate input latency of input threads
zuma: avoid vector<const T>
16kb: Filter out zram.ko for dev options
Support 16KB data reset
Deprecate preloaded_nanoapps.json
Revert "Disable incremental boot_otas"
Add persist to CopyEfsTest
Fix CopyEfsTest for symlinks
Delete PRODUCT_FULL_TREBLE_OVERRIDE.
Delete PRODUCT_FULL_TREBLE_OVERRIDE.
Switch from the BFQ to the mq-deadline I/O scheduler
extended_log: update directory permissions for zuma
Revert "Add soong config use_google_qns in device/google/zuma/de..."
Control the "init_dpm.sh" to be built in zuma devices
Add soong config use_google_qns in device/google/zuma/device.mk
Control GoogleDialer built from zuma/proprietary/GoogleDialer
Restore preferred_idle_mask to the default setting
audio: set util_clamp_min for s/w spatializer to avoid glitches
...
Change-Id: Ib335f5799d9c86adc8f9e9c9d1764814f00dc5ca
Commit 49895bb361e74ffe92a3c0b76f988c8e4697b5c1 in device/google/gs101
failed to remove these overlays. Since this tree was created from
device/google/gs101, this results in the following issue on pantah:
* Pull down status bar
* Try to adjust brightness, network settings open instead
This is caused by the 171px offset that causes the status bar
to overlap the brightness slider.
Test: Reliably adjust brightness, confirm with "Show layout bounds"
from developer settings.
Change-Id: I1b97a28c257cb5b0faba830f29e9058d2dbe50fa
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the 6 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save RAM.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
This reverts commit 70087f4c9e.
Reason for revert: fix breakage in next build with build-time flag in
selinux policy.
Bug: 339241080
Test: tested on Shiba trunk_staging and next builds
Flag: android.hardware.usb.flags.enable_udc_sysfs_usb_state_update
Change-Id: Ifb7764be792494810388858b8672ac7793ed0d42
To extend battery life, modify the display dim configuration to enter
the dimming state more aggressively. The screen should dim at
minimum(20 seconds, timeout * 0.33) before the screen actually timing
out.
Screen timeout (secs) | Dim duration before | Dim duration After
15 3 4.95
30 6 9.9
60 7 19.8
120 7 20
300 7 20
600 7 20
Bug: 315246849
Test: Build & Verify the dim duration with each setting.
Change-Id: I79939290b6a355cf41d43f54a653c533ea833d26
