This commit establishes a soong config variable `sim_count` for
easier converting Android.mk to Android.bp when dealing with multiple
SIMs.
Bug: 343823190
Test: presubmit
Change-Id: Idbd52236b95e8d69516226a71a848d591f181d94
V12 is not frozen yet. We should still allow V11 for `next` build.
Test: trigger test build
Bug: 309897479
Bug: 303162192
Change-Id: Iea9df905efd6bf131d178dcb483e76a0f9d58a14
Signed-off-by: Leo Chen <yinchiuan@google.com>
The change disables the dumpstate strict-run flag in gs201 devices, which is enabled by default. Disabling this flag increases the timeout for capturing incident report to 120 seconds, from the default 20 seconds. This is done because 20s isn't enough to capture incident report proto in some cases, especially when device is throttling.
Bug: 330400782
Test: Booted a gs201 device with the change. Then manually thermal throttled the device and captured bugreports. In some tests Incident report took a lot more more than 20s, and in all these cases it was succesfully captured.
Change-Id: I177bd4aebc550ade855a8abf46ce261eea94d352
Add the flag "use_lassen_modem" for bp to do the same checking like
"USES_LASSEN_MODEM" in mk.
Bug: 330654744
Test: 1. lunch aosp_cheetah-trunk_staging-userdebug
2. m RilConfigService
Change-Id: Icb99b639837237b2afeea858de14669d583bf385
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>
Reporting learning(relaxation) and model loading once a day
* learning and model loading path moved from uevent to
sysfs collector.
Bug: 329124192
Signed-off-by: Chungro Lee <chungro@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5dc71cfae1304564ccb2861109e9e1451032f0e7)
Merged-In: I91039ce3a8ee4630a76113ef7ae6be3bc6908f64
Change-Id: I91039ce3a8ee4630a76113ef7ae6be3bc6908f64
Revert submission 26384060-c2aidl-pixel-enable
Reason for revert: Culprit for b/335892284. Will be verifying through ABTD for confirmation and before submitting the revert.
Reverted changes: /q/submissionid:26384060-c2aidl-pixel-enable
Change-Id: I4acee85037309e699e82c8f378b72381be7de316
Revert submission 26467635-feature_cs
Reason for revert: b/329350496 - Introducing new config with `android.*` namespace is not allowed in 24Q2.
Reverted changes: /q/submissionid:26467635-feature_cs
Change-Id: I36c1408c09a3fa73e2958216e996a8d1e0d94487
Revert submission 26348985-bb-sepolicy-poc
Reason for revert: Droidfood blocking bug: b/327991669
Bug: 327991669
Reverted changes: /q/submissionid:26348985-bb-sepolicy-poc
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:3f5c12abada31befa0d9f869bf6628d06ee05aa4)
Merged-In: Id77188dd9f6f5acaed1506a9489f5d6f9874dde9
Change-Id: Id77188dd9f6f5acaed1506a9489f5d6f9874dde9
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.
[VSR-4.2.004.001] MUST support the smallest width/height alignment allowed
by the video standard. For AVC/HEVC/VCC, this requires 2x2 pixel alignment
for YUV 4:2:0 profiles, and 2x1 pixel alignment for YUV 4:2:2 profiles.
For VP8/VP9/AV1, this requires 1x1 pixel alignment for any profiles.
Note: This is usually stored as the crop rectangle in the bitstream.
Bug: 329378524
Test: CtsMediaV2TestCases
Change-Id: I0e84a342bf1093c74c712d2c811b37eca9c7908c
This change includes tachyon targets for edgetpu in the final image
TESTED:
Create a private build with this change and verified that the tachyon targets were present after flashing on a local device.
Bug: 307591410
Change-Id: Id584ee4ad626e28b7093e6df9a14c3e19dbe51ea
This reverts commit a929e8bc02.
Reason for revert: disable until gs201/main prebuilts get updated
The gs201/main prebuilts are a couple of weeks old, which means that some heap size fixes for the Secretkeeper TA are not present for these devices.
This in turn blocks:
- aosp/2997056: re-enable SK in pVMs
- aosp/3000947: add large DICE chain VTS tests
So revert for now, so we can submit those two CLs and have Secretkeeper test coverage happening on shusky.
Then when gs201/main prebuilts are updated to something more recent (i.e. that includes aosp/3005090), we can re-enable the HAL service.
Bug: 291228655
Bug: 306364873
Change-Id: I543310092ad6430a2dee30ae0b950fadbe869e15
The prebuilts on `main` have been updated to include:
- the Secretkeeper TA in Trusty (in ab/11346410)
- the ABL changes to retrieve the Secretkeeper identity pub key.
for the relevant devices:
- pantah (http://ag/26396674 to Trusty ab/11498491)
- felix (http://ag/26385511 to Trusty ab/11498491)
- lynx (http://ag/26395689 to Trusty ab/11498491)
- tangorpro (http://ag/26396492 to Trusty ab/11498491)
So enable the corresponding HAL service for Secretkeeper when the
relevant build flag is enabled.
Bug: 291228655
Bug: 306364873
Test: VtsSecretkeeperTargetTest on cheetah
Change-Id: I42804579ab4ff5a8ac0edd48fead8631f580dc37
