Report COMPLIANCE_WARNING_INPUT_POWER_LIMITED instead of
COMPLIANCE_WARNING_OTHER to flag incompatible chargers. The underlying
logic that generates the warning remains the same, what's changed is
the enum that's being used.
The purpose of the change is to have a warning type that better
represents what actually happens and free up COMPLIANCE_WARNING_OTHER
that was intended to act as a fallback reason code.
The flag enable_input_power_limited_warning controls whether to switch
to the new enum, while the flag enable_usb_data_compliance_warning
controls the new enums that are added as FlaggedApi in the framework.
Both flags need to be on to enable the change.
Bug: 308700954
Test: manual tests with local flag override
Change-Id: I6595706d1b83d533fc2d3e29086773270e045ede
am skip reason: Merged-In I11edf6e50411a05c6723f7523f3672a9a8116d7a with SHA-1 a9ba6b344f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2794142
Change-Id: I392c9fef8f8f8e92b8e441733edde8cc9137424b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I11edf6e50411a05c6723f7523f3672a9a8116d7a with SHA-1 a9ba6b344f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2794142
Change-Id: I405cb08e29f9ef7e17525d0b104dfdc73aa3542c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I11edf6e50411a05c6723f7523f3672a9a8116d7a with SHA-1 a9ba6b344f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2794142
Change-Id: Ia010473ea85fa3e68e402ef8a5bc2ab1dc2de9fa
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I11edf6e50411a05c6723f7523f3672a9a8116d7a with SHA-1 a9ba6b344f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2794142
Change-Id: I2be8c638af351e60a54ed22d915f1bf81b681ce9
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I11edf6e50411a05c6723f7523f3672a9a8116d7a with SHA-1 a9ba6b344f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2794142
Change-Id: I2cc67b57702ee6289bf055be54b0aceadd665d6f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Set `avb_keys=no_such_key` for dynamic kernel partitions to allow booting
unlocked devices with a custom kernel. This allows a few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: I11edf6e50411a05c6723f7523f3672a9a8116d7a
Merged-In: I11edf6e50411a05c6723f7523f3672a9a8116d7a
The MDS will be signed with platform key and become a platform app. To
make the selinux rules for modem_diagnostic_app work, need to set it to
platform app in app context.
Bug: 287683516
Test: Tested with both dev key or platform key signed MDS apps and the selinux rules works.
Change-Id: Ia0dacafc5e096c101e115b7356d8490391cb6bbd
Set `avb_keys=no_such_key` for dynamic kernel partitions to allow booting
unlocked devices with a custom kernel. This allows a few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: I11edf6e50411a05c6723f7523f3672a9a8116d7a
Bug: 305120274
Test: Compile pass. Flash the build to WHI_PRO devices and no sensor
related avc denied log.
Change-Id: I48d959d439565e9c31ce83812bf29b6d8025c35b
Signed-off-by: Rick Chen <rickctchen@google.com>
1. Move rls_service context from vndservice_contexts to
service_contexts.
2. Allow binder calls from rlsservice to servicemanager
3. Change rls_service type from vndservice_manager_type to
service_manager_type.
Bug: 301520085
Test: GCA
Change-Id: Ief845b5691487f48d570c531de1ea99945087e42
Bug: 307392882
Test: Local generate brownout for data upload
Change-Id: I06b846b9a0a9d8eb4edd5e1636248a44940f0683
Signed-off-by: George Lee <geolee@google.com>
Checks syntax and simple brace balances for all JSON files.
Test: Edit any json and try upload
Bug: 127794899
Change-Id: I12e5ca0a0fe249f7d93adbd540d4964cafb09249
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:e4a81c0e8f9f8d89f0e42e8fd7ec40cec6b887ed)
Merged-In: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
This reverts commit c13cd03ccf.
Reason for revert: Let's go through a proper security review for this.
Bug: 306264015
Change-Id: I51fe3f32f8a4ec92cb2d38869568a51dc2522bb4
Set `avb_keys=/avb` for dynamic kernel partitions to allow booting
unlocked devices with a custom kernel that is signed using a test key.
This allows a few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Test: flash production userdebug build, then flash custom kernel.
Bug: 274825778
Change-Id: I11edf6e50411a05c6723f7523f3672a9a8116d7a
