Set the /dev/acd-com.google.umfw_stat security context type to
aoc_device.
Bug: 254464877
Test: Verified /dev/acd-com.google.umfw_stat security context.
Change-Id: Ibeba4c65f479c38ab740e156dd244e2f40d00dd4
Merged-In: Ibeba4c65f479c38ab740e156dd244e2f40d00dd4
Bug: 240530709
Test: adb bugreport
and the following file got to dumpstate_board.bin:
extended_log_uim.txt
extended_log_os.txt
nv_normal.bin
nv_protected.bin
Change-Id: Ie6439c7487b11c564cd6c0d1266928e6b9b384ee
Bug: 240530709
Test: adb bugreport
Create empty files starting with the following prefix
/data/vendor/camera/profiler/session-ended-
/data/vendor/camera/profiler/high-drop-rate-
/data/vendor/camera/profiler/watchdog-
/data/vendor/camera/profiler/camera-ended-
and do adb bugreport and make sure they end up in dumpstate_board.bin
Change-Id: I2f9dfb74476af295db8a392ebf7757681404841e
1. mediacodec_samsung.te is copied from ag/20742869
2. add common settings which will be used by differnt vendor
Bug: 263444717
Test: build pass, camera record, youtube
Change-Id: I62a4c33ea59d1b3f70990f221b11fe9d905e15f1
- gpsd segmentfault protect code
- android.hardware.gnss@2.1-service-brcm segmentfault
- AGC field is missing when requested deep indoor
- TestGnssMeasurementIntervals_LocationOnAfterMeasurement fix
- mismatch between bearing value and fixed location
- location jumped in the office and the reported accuracy is
much higher
- Can't enter duty cycle mode
- fix IGnssConfiguration setBlocklist issue
Test: atest VtsHalGnssTargetTest
Test: atest CtsLocationGnssTestCases
Test: verify test at b/269048821
Test: verify test at b/269049429
Bug: 260300008
Bug: 262632321
Bug: 266760732
Bug: 264597734
Bug: 266343909
Bug: 254357787
Bug: 262829108
Bug: 265106280
Change-Id: I6097ed175b798df4324f26624ea30ca16447c405
Watchdogd should be alive to complete shutdown
safely. This also aligns the behavior with previous
watchdogd.
Bug: 267080705
Test: boot
Change-Id: Iad85a0d730d032ae57530e0aa6965e2123488b2f
Signed-off-by: Martin Liu <liumartin@google.com>
Background:
Darwinn Runtime team wants to use a cloud-based infra (Android Core Experiments) to push flags from server to device. The flags will be stored into android properties under the namespace: `persist.device_config.edgetpu_native`, which has a property context called `device_config_edgetpu_native_prop` as added by the other CL: https://android-review.git.corp.google.com/c/platform/system/sepolicy/+/2434232
Change:
Allow EdgeTpu service to read device_config_edgetpu_native_prop
Test: Verified EdgeTpu has access to read the property
Bug: 243553703
Bug: 246401730
Change-Id: I19dca0e2d3008e36bdbca50f610810148a7e11dd
vendor.brownout_reason did not get triggered as battery_mitigation.rc
looked for reboot,ocp,buck3m and not reboot,ocp,BUCK3M.
Bug: 268700448
Test: Confirm triggering of bugreport
Change-Id: Icf7dd70d1bd050616583af807fc16e8f7680f95d
Signed-off-by: George Lee <geolee@google.com>
vendor.brownout_reason was set because sys.boot.reason still contains
the reason from prior reboot. By enforcing thermal check prior to
bootreason check guarantees the sys.boot.reason will have the most
recent boot reason.
Bug: 268344942
Test: Confirm through artificial triggering of brownout
Change-Id: I69cb459f4c51f7db439d5993330691a7ad1f5dbe
Signed-off-by: George Lee <geolee@google.com>
