V14 is not frozen yet. We should still allow V13 for 'next' build.
Bug: 381463038
Bug: 378407278
Test: build pass
Flag: EXEMPT bugfix
Change-Id: Ie0caca924696b90f855ef46023d53040adcde93a
am skip reason: Merged-In I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced with SHA-1 1a173d6997 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3391984
Change-Id: Iabf8df4e7c1a5c05033d6da866f7357ac362c838
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced with SHA-1 1a173d6997 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3413724
Change-Id: Ie99645db6be25d30257a7df2209f1d6664d761e7
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
For multi-window foreground app group.
Bug: 200769420
Change-Id: I2b65feb4732e33b27155dcfaf0b64a38b1b01026
Test: build pass
Flag: NONE vendor init file does not support flag
instead of using ADPF, let's use task_profile to boost input tasks'
priroity
Bug: 378761104
Flag: EXEMPT new task_profile behavior
Change-Id: Ice311b1abcf3d629917e16f1490d4cb63fd83796
Signed-off-by: Chungkai Mei <chungkai@google.com>
Bug: 335874870
Test: Checked that permissions and values for all affected files are correct (ls -l, cat)
Flag: EXEMPT not supported by this component yet
Change-Id: Ifbea91bce20e046a6e1b92295814a27e99f41dbe
For solving sepolicy conflicts for different AP version, modem_svc_sit will support devices from gs101 to zuma_pro.
Bug: 372400955
Change-Id: Icef24314461008651230779358b253429c277b76
Flag: NONE local testing only
Add task profiles and set permissions.
Bug: 355612114
Flag: NONE init rc file does not support flag
Test: build pass
Change-Id: I4b285a95b5a9d3934a5b95ba57424a89a98f9b2a
am skip reason: Merged-In I2912cbc905ff0ee716c293021c29061e3b6d3dca with SHA-1 d1cf23e6f7 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3391984
Change-Id: I48b292a241f1ee1b8531850190b174f6b9b8dea5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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
am skip reason: Merged-In I3977722564241817575d94b2d2023eac6939ce1c with SHA-1 f42925e978 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/30284975
Change-Id: Icd021cbd1b5384ff22e2913d053fb96006fbd4bb
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
