Allow persist.vendor.nfc.antenna. to be vendor public values for NFC
companion app to access from userdebug or eng builds
avc: denied { read } for name="u:object_r:vendor_nfc_antenna_prop:s0" dev="tmpfs" ino=414 scontext=u:r:untrusted_app:s0:c79,c257,c512,c768 tcontext=u:object_r:vendor_nfc_antenna_prop:s0 tclass=file permissive=0 app=com.google.android.apps.internal.nfcassistancetool
Bug: 361050657
Test: m selinux_policy
Flag: NONE add permission
Change-Id: I47c54642dbc801dfcaee8330e75a29d11030337c
We didn't add the formattable flag to ext4 fstab entry because init
only uses the first entry for re-formatting, but now init can choose
the right fs type base on page size, we can add the formattable flag.
Now data resets in 16KB mode would go back to ext4.
Test: th
Bug: 356202847
Change-Id: Ieb01c2592b3bb8e3342b2b6178ee73c0fb8a4288
This reverts commit 8bb0da99a9.
Reason for revert: Incremental ota support is now available: b/339658378
Fixes disk size regression issue now that OTA signing issues are resolved.
Change-Id: Id897a60473e6ea99522d9ab372511e7c2ebdd757
Use the -L flag to preserve symlinks.
Fixed various flags to ensure we handle symlinks right,
and adjusted the awk string to handle difference in how dates are
represented.
Test: atest CopyEfsTest
Flag: TEST_ONLY
Bug: 352567354
Change-Id: I686c16fc1d771bf00bdc7465beb29a91eaef9e46
am skip reason: Merged-In I181937f9e49d4b9e1088fc92df7681d1a39e3d26 with SHA-1 c8436d8183 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3254799
Change-Id: I90a90a60fa55277d8b8f5061f33e8cbc7d015d4a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial zuma devices (Pixel 8)
launched with API level 34.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: I181937f9e49d4b9e1088fc92df7681d1a39e3d26
Merged-In: I181937f9e49d4b9e1088fc92df7681d1a39e3d26
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial zuma devices (Pixel 8)
launched with API level 34.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: I181937f9e49d4b9e1088fc92df7681d1a39e3d26
am skip reason: Merged-In I4b2a0a61ebaff5d85a4daac445d81ae3d21aa9c3 with SHA-1 2d0a254101 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3258122
Change-Id: I8bf59b12c6f440cb32f7df35d151ef2eb77155ea
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I9181b2344f2448b9debe1522528545ce90de8768 with SHA-1 fb98394c54 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma-sepolicy/+/3258561
Change-Id: I411d96644364dcb9efdea5c1fe708b9651f8c12d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I4b2a0a61ebaff5d85a4daac445d81ae3d21aa9c3 with SHA-1 2d0a254101 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3258122
Change-Id: I22de6d889530896c87c8be5e914e80acb5223765
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I9181b2344f2448b9debe1522528545ce90de8768 with SHA-1 fb98394c54 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma-sepolicy/+/3258561
Change-Id: Iedc2cb039f534e4d1e7b873bec0f4f4d41fb4ab6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
The mq-deadline I/O scheduler is more stable than BFQ. Additionally, the
boot time is shorter with the mq-deadline I/O scheduler. It only changes the scheduler on new kernel.
Bug: 186902601
Test: forrest build
Change-Id: I51605b32afb4340d416fe4923570bb3f4af24ab8
Signed-off-by: Ocean Chen <oceanchen@google.com>
