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: I4b585c0b73366ba5e1f8c6461ed3ed62547af7b7
Bug: 379849040
Flag: EXEMPT 'config change'
Test: Manually verified if the satS2.data is working well in PR, HI, AK, US mainland with old format (b/377610782#comment4)
Change-Id: If3b54455a4716cb232671ba7c3a6ceafd48566ad
For zumapro it shares the same libacryl_plugins in zuma but for
libexynosdisplay it still has different version between zuma and
zumapro. Add zumapro's own libexynosdisplay for zumapro.
Bug: 357500180
Test: lunch aosp_caiman-trunk_staging-userdebug; \
m libexynosdisplay
Flag: EXEMPT refactor
Change-Id: Iaf07baa8bb93ee6cd3da01e4b50231b7f5023fe9
Re-land after making SELinux corrections.
35162f9a7c
Bug: 335874870
Flag: NONE code refactor
Test: Boot and check parameters
Signed-off-by: Will Song <jinpengsong@google.com>
Change-Id: I8a7c50d9d4a8e77714a7a87d7d974decdac1e877
This will only enable RE-Graphite for stages where the rollout aconfig
flag introduced in I30a59986d1da2dc8355c2b3cf2da436c6cc64120 is also
enabled (and if the force_compile_renderengine_graphite read-only flag
is also enabled.)
Rollout proposal discussed w/ Pixel Graphics leads out of band.
Bug: 380460068
Test: manual validation that RE-Graphite is only enabled w/ aconfig flag
Flag: com.android.graphics.surfaceflinger.flags.graphite_renderengine_preview_rollout
Change-Id: I29bade2e024771b2800ab23236ddab4b12d9425b
This does not convert /metadata to ext4, the default is still f2fs.
EXT4 would only be used if we are on 16KB mode
Flag: EXEMPT bugfix
Bug: 379759696
Change-Id: I854f563ecd49fc3d7d73ede581cf3d3081c5e555
Revert submission 30519089-move_modem_sepolicy
Reason for revert: DroidMonitor: Potential culprit for http://b/380274930 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:30519089-move_modem_sepolicy
Change-Id: I74d37465d49e31c84d5e51bb0f020988a41b66ab
This is to include the time required for AOC SSR and restart when
AOC reset and re-establish transport to finish queued commands.
This will also match the Pixel Watch HCI timeout value.
Flag: EXEMPT bugfix
Bug: 375044749
Test: build, verify on device, presubmit
Change-Id: I18fffdee2a38d784165c048d8adf9edbd0019cfc
Since our feature is not ready, we utilize build flag we applied for this project to project this undone feature built accidentally on other targets.
Test: Run test `UpdatableCrashingBootTest` on caiman `trunk_staging`, `trunk_food` and `next` targets with go/forrest (https://android-build.corp.google.com/builds/abtd/run/L28000030007788752, https://android-build.corp.google.com/builds/abtd/run/L64100030007774323).
Test: Build and flash caiman with `trunk_staging` as target, GIA is up and running.
Flag: build.RELEASE_PIXEL_GIA_ENABLED
Bug: 378865024
Change-Id: Iffa7f11659ece8c0210023630568cdc45132840f
Signed-off-by: Kai Hsieh <kaihsieh@google.com>
Revert submission 30378113-revert-29512389-gia-PMLMEKURMT
Reason for revert: Revert to fix the issue that GIA cannot be started in caimen-next-userdbg
Reverted changes: /q/submissionid:30378113-revert-29512389-gia-PMLMEKURMT
Bug: 367881686
Change-Id: I74a61360d09f85a2404d884090fd2bedb1be4030
