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
Set InputDispatche and InputReader prefer idle explicitly, which is a
workaround and should be removed after they become ADPF.
Bug: 366146314
Flag: NONE init rc file change does not support flags
Test: tasks set as expected
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a6c71987d597d0d575b62f6a65807c1bcd08ee87)
Merged-In: I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced
Change-Id: I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced
Bug: 347122505
Test: check the priority and latency of input thread in Perffeto
Flag: NONE early device setting updates
Change-Id: I3977722564241817575d94b2d2023eac6939ce1c
We didn't add the formattable flag to ext4 fstab entry because init
only uses the first entry for re-formatting, but now init can choose
the right fs type base on page size, we can add the formattable flag.
Now data resets in 16KB mode would go back to ext4.
Test: th
Bug: 356202847
Change-Id: Ieb01c2592b3bb8e3342b2b6178ee73c0fb8a4288
The mq-deadline I/O scheduler is more stable than BFQ. Additionally, the
boot time is shorter with the mq-deadline I/O scheduler. It only changes the scheduler on new kernel.
Bug: 186902601
Test: forrest build
Change-Id: I51605b32afb4340d416fe4923570bb3f4af24ab8
Signed-off-by: Ocean Chen <oceanchen@google.com>
The preferred_idle_mask is changed during boot time, but it does not
restore to the default setitng as in powerhint, so some node may keep
the wrong value when framework restarts.
Bug: 248621289
Test: build pass
Flag: NONE init rc file change does not support flags
Change-Id: I892b99b79ff2dd9c02cc874026b43b06bded6f59
In case of always, we always enable hdcp regardless of drm status.
Bug: 359951297
Flag: EXEMPT bugfix
Change-Id: I04b5174be296d93a9f898929706785d50116d7a7
Signed-off-by: Ji Soo Shin <jisshin@google.com>
Remove irrelevant copy and paste content. None of the zuma
devices ever included these services and these sockets are
not doing anything.
Bug: 234559097
Test: presubmit
Flag: EXEMPT dead code removal
Change-Id: I8664262708b89016227d7df076e7c8d70a53de07
This change is to allow the CPU Idle Histogram Stats to be dumped in
bugreports so that there is more insight into the idle behavior of
devices in the field.
Test: Build/Flash
Test: Collect histogram log
Bug: 344908619
Flag: EXEMPT bugfix
Change-Id: Ib6e4772737a8c1f22ac8ba31c40099baeab43853
Signed-off-by: Vishvam Mazumdar <vmazumdar@google.com>
This reverts commit 721a8358c6.
Reason for revert: 24Q3 has been cut, relanding the original commit ef68e9b578.
Change-Id: I7882ebafd66d126df9ccbe2124617fbf4ed73eb5
Bug: 347272991
The graphics hal might need to access /persist early in the boot
process. So mount persist early for 4K devices.
Test: boot 4K device
Bug: 338504890
Change-Id: I4b2a0a61ebaff5d85a4daac445d81ae3d21aa9c3
Previously, we rely on mount points to copy files out of
efs partitions. Switch over to dump.f2fs to read directly
from block device without mounting. This allows us to copy
files out of efs partition in both 4K and 16K mode.
Test: Boot dev option enabled ext4 device
Bug: 340965747
Change-Id: I9d3f3d5200adc31f13298488b5be068b0fe7c7f4
This reduces the amount of computation needed on critical
boot path for F2FS devices. Boot time is expected to improve
with this patch.
Bug: 341216848
Test: boot device with ext4 and f2fs
Change-Id: I7311a22a7bf9773d3909656d98cc578a43cb9477
Products using 16KB kernel may wish to boot into 16KB mode
directly. To do this, these targets would need to use ext4
as their default fs type for /data and /metadata . Add
a build time flag which would install ext4 fstabs.
Test: th
Bug: 339337171
Change-Id: I53de1599bbff583b45ca2bf6d3e3efb83957913e
Common fstab entries(everything but /metadata and /data) are
moved to a separate fstab file.
This allows us to create an ext4 variant of the same fstab later.
Test: device boots
Bug: 339337171
Change-Id: I3129551c98b14473c776f2cf3dee1b81fc0c84b3
Since /persisit was previously mounted during eraly-init stage,
this CL delays the /persist mount to post-fs-data stage.
Actions which depends on the /persist partition are also moved.
Bug: 319335586
Change-Id: I6bcc775f16331905c6896f3a2ec5bbea9e20744f
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: Ide78be316778acfc5c582c4a7b78853796cf4c1e
