Remove b/376602341, b/314054292 and b/367943515 as they are closed
Flag: EXEMPT sepolicy
Test: SELinuxUncheckedDenialBootTest
Bug: 382362125
Change-Id: I7911102a96cdb602fecf8dae5f87c41448b7e6ba
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
Merged-In: I2912cbc905ff0ee716c293021c29061e3b6d3dca
Change-Id: I2912cbc905ff0ee716c293021c29061e3b6d3dca
The command line "kasan=off" should be unconditionally set when we're
compiling for a normal (non-_fullmte) build. The current logic
sets "kasan=off" for a normal ENG build only, which is insufficent.
Test: _fullmte userdebug/eng: "sanitizer-status mte" shows MTE enabled.
Test: _fullmte userdebug/eng: "kasan=off" IS NOT present in /proc/cmdline
Test: !_fullmte userdebug: "sanitizer-status mte" shows MTE disabled.
Test: !_fullmte eng: "sanitizer-status mte" shows MTE enabled
Test: !_fullmte userdebug/eng: "kasan=off" IS present in /proc/cmdline
Change-Id: Idd61747156daa135e919ce71fd63bfab1f4d9239
Bug: 381940217
Flag: EXEMPT bugfix
am skip reason: Merged-In I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced with SHA-1 a6c71987d5 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/30626095
Change-Id: I49afe6d3367ef8da752021f4e6cf39a44d89de07
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This string is not device specific, and already set at,
frameworks/base/packages/SettingsLib/res/values-mcc311-mnc480/strings.xml
frameworks/base/packages/SettingsLib/res/values-mcc310-mnc004/strings.xml
Bug: 377907543
Flag: EXEMPT clean up
Test: m
Change-Id: I3bd290c8839ac510a0b11c70a7aaa55d58591964
The 16k mode does not use these modules.
Bug: 378293897
Bug: 379704287
Change-Id: I237fd9cf7ca2f7972fafa08a3df65c0472e1ef03
Test: Built husky-trunk_staging target and tested
4kb and 16kb mode.
Flag: EXEMPT bugfix
Since pixel performance has a shared configuration,
we need to move override values into late init.
Bug: 381100494
Test: Boot
Flag: EXEMPT bug fix
Change-Id: I20d38e481d43d1068a6faebec298446929812ffb
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: I2912cbc905ff0ee716c293021c29061e3b6d3dca
For zumapro it shares the same libacryl_plugins in zuma but for
libexynosdisplay it still has different version between zuma and
zumapro. In ag/30508311 it already split
hardware/google/graphics/zuma/libhwc2.1 to it's own soong_namespace
which need to add it to product config for zuma.
Bug: 357500180
Test: lunch aosp_husky-trunk_staging-userdebug; \
m libexynosdisplay
Flag: EXEMPT refactor
Change-Id: I8adc95085067456aa2a29822e89f9777ece241f3
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: I91c114f476b6894361523a5bc8b66930df9f49a5
Meeded for system server to monitor usb gadget state.
Grant hal_usb_impl read access as it's needed by UsbDataSessionMonitor.
Starting at board level api 202504 due to its dependency on aosp/3337514
10956 10956 W android.hardwar: type=1400 audit(0.0:327): avc: denied { read } for name="state" dev="sysfs" ino=84394 scontext=u:r:hal_usb_impl:s0 tcontext=u:object_r:sysfs_udc:s0 tclass=file permissive=0
Bug: 339241080
Test: tested on Shiba
Flag: android.hardware.usb.flags.enable_udc_sysfs_usb_state_update
Change-Id: Ied2d669df74a2f71771e672e27327b60e7687168
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: I7fc88068835f662d1f1827488089f5898e88ff9d
