Android 15.0.0 Release 6 (AP4A.241205.013)
# -----BEGIN PGP SIGNATURE-----
#
# iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ1IssQAKCRDorT+BmrEO
# eDIZAJwMTYIKjIAnt4/EG98sVijowfb+9ACeO1gMsXc1bg4Dls3HunIrfCM+sOM=
# =ctpR
# -----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 Wilson Sung (7) and others
# Via Android Build Coastguard Worker (27) and others
* tag 'android-15.0.0_r6': (27 commits)
sepolicy: allow dumpstate to execute dump_power
Make android.framework.stats-v2-ndk app reachable
Change vendor_fingerprint_prop to vendor_restricted_prop
Update SELinux error
[BT] Define vendor_bluetooth_prop
storage: move storage related device type to common folder
Storage: label ufs firmware upgrade script
Label sysfs node power_mode as sysfs_display.
sepolicy: gs201: fix bm selinux
sepolicy: remove dump_power_gs201.sh
Update SELinux error
Revert "Revert "gs201: update shared_modem_platform sepolicy for..."
Revert "gs201: update shared_modem_platform sepolicy for UMI"
Update SELinux error
Update SELinux error
Update SELinux error
gs201: update shared_modem_platform sepolicy for UMI
Update SELinux error
Allow camera HAL to access power_state sysfs
Add kernel vendor_fw_file dir read permission
...
Change-Id: Id50470e50ccd1afb2550f89eff242a99cbbb386b
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
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
Squashed with:
Author: Nolen Johnson <johnsonnolen@gmail.com>
Date: Sun May 9 16:04:34 2021 -0400
Simplify AVB flag logic
* AVB's `--flags 3` argument builds a disabled VBMeta with
disabled hashtree, so no need to set both flags individually.
Change-Id: Ibe9ee322a5af58f13e76d53e18dee49451fe8838
Change-Id: Ie8f1e0929b037b35b5e45c2e31be9253fa0bb097
Virtual AB compression prevents GApps from being installed to
cheetah/panther.
This reverts commit 2bfa6d3ba01856d99c6ffdb64627c6e9391c4a41.
Change-Id: I119b8e042e4cdeec27a19ab5dd4f0666cc115ae1
Certificates extracted from stock vendor_mac_permissions.xml using
adevtool: https://github.com/kdrag0n/adevtool
Change-Id: Iaf59f1548905d16fe7ad231c039ba43941c15710
* In Android 12, Android System Intelligence (com.google.android.as) uses
some of the Private Compute Service (com.google.android.as.oss) services.
The absence of these Allowlists will cause Android System Intelligence
to fail to connect to the network and cause collapse.
* We don't need to extract google.xml to fix it, just extract the AiAi part
Change-Id: I446ae5d243cff134901094f82c90a0bbf3bb4381
The GoogleParts app disables the EUICC app when there's no GMS, but it
doesn't happen quick enough. The crash dialog pops up a few times right
after initial boot up. There's no need to alarm the user, so hide it.
Change-Id: Ia06b336b30a8886bae522c6e8a76a1ca15da5edd
* This avoids EuiccGoogle / GoogleCarrierServices crashing, taking the
whole telephony stack with them when no GMS or GSF is installed.
* Compared to change 274251, this approach is no-op when GAPPS add-on is
flashed before the first boot, and thus should not cause issues with
eSIM when GAPPS is flashed.
* With microG, this also works after installing the microG GMS & GSF
packages and rebooting, although manual activation of the eSIM is
needed via Settings - Network.
* The only downside is that users will still see one or two crashes
during the first boot because our application only starts after the
device is booted.
Change-Id: I4a11c93e855978abbf8d84fdbe4ffc8b2aedc27c
This feature is provided by the ConnectivityThermalPowerManager app that
we extract as a proprietary blob, so we can expose it.
Change-Id: I407e9e2235531fbca0b2c0e48b68105b1e77ad1f
The CarrierSettings app enables/disables carrier apps based on sim
inserted, so use it instead of CarrierConfig.
Change-Id: I163dd615e9d8268c5f94a28ae234a30f74c7e83b
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
All production GS201 devices have CS40L2x haptic driver ICs that support
multiple intensities, so expose the Off/Low/Medium/High vibration
strength options like stock.
Co-authored-by: Michael Bestas <mkbestas@gmail.com>
Change-Id: I72645b5bd5772e182592a630df86f9b6166b4923
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
