MTE is a low overhead tool which enables detection of memory
safety bugs in interactive workloads. See
https://source.android.com/docs/security/test/memory-safety/arm-mte
for background and information.
This change enables MTE by default on -eng builds. See
go/mte-eng for more information.
Co-authored-by: Evgenii Stepanov <eugenis@google.com>
Test: Device boots and no MTE crashes
Bug: 316398899
Flag: EXEMPT only affects eng builds, not shipping code
Change-Id: I8be52af4f0349907651ae661972c85ea46e2aa72
Enable settings by different groups.
Bug: 355612114
Flag: NONE init rc file does not support flag
Test: build pass
Change-Id: Ic4eccc64797cb6511f5f3c50f9e5a0b8f0791edc
Add profiles for sched qos setting. The original uclamp_fork_reset
will be removed later.
Bug: 355612114
Flag: NONE vendor task_profiles.json does not support flag
Test: build pass
Change-Id: I287547c902f79d3e16c0aab913d7f1004f8df184
Set the full module path of libacryl_hdr_plugin and the include dir for
lobacryl conversion to soong. It will take effect after aosp/3286932 and
aosp/3287183 merged.
Bug: 370414334
Test: lunch aosp_caiman-trunk_staging-userdebug ; m libacryl_hdr_plugin libacryl
Change-Id: I21a9cee4a36e1951979481c50bce871a6853504c
VSS support removed from zumapro and made device specific
BUG: 369721391
Flag: EXEMPT refactor(SUPPORT_VENDOR_SATELLITE_SERVICE)
Test: Manual Test(Satellite Basic Test)
Change-Id: I52cb3e36dedecf7fb8dd14135dfe8da400210144
Makefile contain the following sysprops
bluetooth.profile.bap.unicast.server.enabled
bluetooth.profile.tbs.server.enabled
bluetooth.profile.vc.server.enabled
However, CS indicates the above sysprops aren't defined anywhere
nor read anywhere? Given how the following LE Audio sysprops are
missing from the makefile, and the similarities in naming, we
suspect there was a typo?
bluetooth.profile.bap.unicast.client.enabled
bluetooth.profile.ccp.server.enabled
bluetooth.profile.vcp.controller.enabled
Bug: 372711861
Test: builds
Flag: EXEMPT bugfix
Change-Id: I2e9812060733ba6d380a104d79e58867a3e01aa2
Set InputDispatche and InputReader prefer idle explicitly, which is a
workaround and should be removed after they become ADPF.
Bug: 366146314
Flag: NONE init rc file change does not support flags
Test: tasks set as expected
Change-Id: Ica1cc1bcf44205f6ccfb09529a52107b1c5091b3
This patch prevents a Null Pointer Exception in
queryMoistureDetectionStatus() when getPortStatusHelper() fails to open
the /sys/class/typec file. The failure results in an empty
currentPortStatus vector, causing the NPE when accessing its first
element.
Bug: 361097811
Flag: EXEMPT bugfix
Test: NPE does not occur when getPortStatusHelper() fails
Change-Id: I4657ab8dbc9bb7e5d2dc46c1a20b66477604ec36
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
There are 4 partitions that are flashed at the factory and use F2FS fs with
4kb block size:
- /dev/block/by-name/efs
- /dev/block/by-name/efs_backup
- /dev/block/by-name/modem_userdata
- /dev/block/by-name/persist
These partitions can NOT be mounted by 16kb kernels because F2FS
expects BLOCK_SIZE == PAGE_SIZE.
In order to access the files in these partitions by 16kb kernels,
the dump.f2fs tool is used.
This change will perform these steps at boot time ONLY for 16kb mode. For
every partition (efs/efs_backup/modem_userdata/persist):
1. Use dump.f2fs to copy the content of the partition
to /data/vendor/copied/<partition name>.img.
2. If the copy was succesfull, rename /data/vendor/copied/<partition name>.img
to /data/vendor/copied/<partition name>
3. fsync the content of the directory /data/vendor/copied/<partition name>.
After the content of the partitions is in /data/vendor/copied,
bind-mount the partitions to the directory /mnt/vendor. See conf/fstab.efs.from_data.
Note: This change ONLY applies to 16kb kernels. This change does not modify
the original partitions.
Bug: 347015136
Bug: 362368691
Test: $ source build/envsetup.sh
$ lunch [zumapro]-trunk_staging-userdebug
$ m
$ ./vendor/google/tools/flashall -w
Flag: EXEMPT bugfix
Change-Id: Idf46a2a3a4f0b2e91ee4a0322a0c469e055684c8
