Contexthub (CHRE) team is removing the chre daemon and incorporating
its functionalities into the next gen HAL. This CL copied the
permissions we received in whitechapel/vendor/google/chre.te to
hal_contexthub.te to enable the same set of permissions on gs101.
Bug: 247124878
Test: launch the hal process on oriole and verify it can perform
required operations such as loading nanoapps holding wakelocks,
query nanoapps, etc.
Change-Id: I8ce6b4f7f411e50cf454bb5f1286f73d4d46aced
The license declaration can't be handled in Android.bp currently.
So keep them in Android.bp.
Bug: 310058310
Test: NA
Change-Id: I3e25fa07f6b3e1bffaf585d69e342c651b50f6ef
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
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: If890f7caaac33e5ddc6c02cc8084654a10cea416
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I1f546f53b63b7db94cd7443650688027c61e185b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I254534a8ec4b951fdc7a5aa8d731f84dda03e900
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: Ia2839d3e016de4ee45b4323a790ad42abb48c0d6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I5bbe3a94b51939ec0d8050ef32292ec1fb8020ab
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: Ibae31049dc107670bbc5d13bfac967ebf19c8e55
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
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: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Merged-In: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
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: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Bug: 305120274
Test: Compile pass. Flash the build to WHI devices and no sensor
related avc denied log.
Change-Id: I56174a24d159968c01d1572e84f4bcdd7930a709
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: I7badfe2ddb73b13884b54d2c8972e1921af6ea38
Checks syntax and simple brace balances for all JSON files.
Test: Edit any json file and try upload
Bug: 127794899
Change-Id: I70ad38f73a4fea908442b4411e3aa7ffbaeb7d88
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:1bc693d338e8d26307d51bb6731d8e94f1df33f9)
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
