Set the system property that lets the DevicePolicyManager know it can
control Memory Tagging Extension on the device.
With this property set, when the user turns on AAPM, it will turn on
MTE.
Bug: 352420507
Test: Manual
Flag: android.security.aapm_feature_memory_tagging_extension
Change-Id: I2cf9b650286659bc36d0e304c1ad05ff5dac4d5c
US(mainland, hawaii, alaska), PuertoRico, Canada, Europe
Bug: 362312117
Flag: EXEMPT 'config change'
Test: Manually verified if the enhanced geofence file is working well
with the satellite_access_config.json file.(b/382816070)
Change-Id: I65dec5b1e9602979f102ab34764a8067e54bde05
Bug: 362312117
Flag: EXEMPT 'config change'
Test: Manually verified if the enhanced geofence file is working well
with the satellite_access_config.json file.
Change-Id: I9a27b9bc67dcd5d48e4487b1af973847b3a0912c
For solving sepolicy conflicts for different AP version, modem_svc_sit will support devices from gs101 to zuma_pro.
Bug: 372400955
Change-Id: I926fe12be95f10a2c4db13c06dab8b1586f9dcc8
Flag: NONE local testing only
am skip reason: Merged-In I4b585c0b73366ba5e1f8c6461ed3ed62547af7b7 with SHA-1 1887e6e521 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zumapro/+/3392061
Change-Id: I513abbc2c25c9fcc516f089d20f0ff079bb0858f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Let InputPolicy have all the feature of ADPF task.
Bug: 355612114
Flag: NONE vendor task_profiles.json does not support flag
Test: build pass
Change-Id: I5c2964c0328d2d3a95c84d4c2908ace198202e06
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: I4b585c0b73366ba5e1f8c6461ed3ed62547af7b7
Change-Id: I4b585c0b73366ba5e1f8c6461ed3ed62547af7b7
* changes:
usb: support device state monitoring with internal hub enabled
usb: dump port name for usb device state update
usb: clean up monitor thread in UsbDataSessionMonitor destructor
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
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: Ib7681d0acde908f3cb7b0628c54a2d42a002e21c
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: I359c33622f18c9345ee3f250ca5d5c61bc1440cc
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
