This is necessary to implement fingerprint HAL in Rust.
Bug: 366409699
Test: Build pass
Merged-In: I6d925fadb94252cd9d66f93b3085c231ff52fe86
Change-Id: I6d925fadb94252cd9d66f93b3085c231ff52fe86
For host-side fake VHAL, it does not have access to android system
property so it needs to override the config.
Flag: EXEMPT HAL change
Test: Presubmit
Bug: 365994148
Change-Id: Ica0483bd5c9dc4dc2a5301acf5115745a4aa46fb
Some of the vintf build steps in Android.mk have been moved into soong
with the system_compatibility_matrix.xml phony module, so we need to
bump those now too.
Test: build/make/tools/finalization/build-step-0-and-m.sh
cf_x86_64_phone && m
Bug: 331696132
Change-Id: I8d017b12aa2d2ecc097ae58c39007ce6585429e1
Cleaning up the OWNERS file for those who are no longer on the team.
Test: The ghost of trong@'s account cannot approve changes in this
repository
Change-Id: Ib777c16b53691f82de5bea33bd3cc363a8720982
Change-Id: I6c2bcdbfc6177b5d8e9416a5b93edf7e5e8a2b5b
This feature flag also needs some work in implementing the corresponding
access control rules. Otherwise, the CTS tests will fail. Re-enable this once that is fully implemented.
Bug: 289193458
Change-Id: I426bce4db0715c5136c15ddf68afdcf2966cb7af
Test: atest OmapiTest
The UDS_pub is supposed to be the first element of DiceCertChain
according to generateCertificateRequestV2.cddl.
Bug: 365711214
Test: rkp_factory_extraction_tool
Change-Id: I454a99058d92ce9743810a9334c7ccacccc694e0
Revert submission 3254876-disallow_degenerate_chains
Reason for revert: Droidmonitor created revert due to b/365592588.
Reverted changes: /q/submissionid:3254876-disallow_degenerate_chains
Change-Id: I31f78d6c708f34f0a6fe9f54daef82981a91ac8f
Due to security concerns, ThreadNetwork HAL service's debug log should
not be visible on user builds.
The "debuggable" field defines the flags that will be applied to
userdebug/eng variant builds.
Bug: 359338609
Test: No debug log from android.hardware.threadnetwork-service in logcat
Change-Id: I13993191efd3841fc8db1888be7c59c86f6608d3
Bug: 323246910
Test: atest libkeymint_remote_prov_support_test & manual testing of
`rkp_factory_extraction_tool` with/without `allow_degenerate=false` on a
device with a degenerate DICE chain
Change-Id: Ia1833c0bb6a895ae5b8aefea24850a41cf956f38
Revert submission 3235656-revert-3195743-compatibility_matrix-KLJOLWYIMW
Reason for revert: The root cause of the break is already be merged. Related changes: ag/29139095, ag/29139608
Reverted changes: /q/submissionid:3235656-revert-3195743-compatibility_matrix-KLJOLWYIMW
Change-Id: I6ef91cbf72f63013778056183e0997d5ece06854
This reverts commit ca6839888e.
Reason for revert: This is likely the cause of b/357792919 and no longer needed for the camera test cases since they have their own defaults.
Merged-In: I4a94280ef2ff63b569d43d8cd90de5a8f2058be9
Change-Id: I4a94280ef2ff63b569d43d8cd90de5a8f2058be9
(cherry picked from commit 8ac9e1b75e)
* changes:
libhealthloop: Use designated initializers
libhealthloop: Reduce the number of ScheduleBatteryUpdate() calls
libhealthloop: Terminate KLOG messages with a newline
The VTS test already verifies that the MMap hardware position
never resets or goes back, but the official wording in the AIDL
interface was lacking.
Bug: 350998390
Bug: 363139283
Test: none, doc change
Change-Id: I07b9842f53c89549fe648ee839d875d31a7a849d
The HealthLoop code only checks the name of the subsystem in the uevents
that it receives. Since the recently added BPF filter only passes power
supply uevents, all we need to know is whether or not any such uevents
have been received. We do not need to know how many of these events have
been received. Hence, reduce the size of the uevent receive buffer.
This CL reduces the number of ScheduleBatteryUpdate() calls if uevents
are received faster than these can be processed.
Bug: 362986353
Change-Id: If286ae5d05a95d59bc637a869c94d5c5472b5be2
Signed-off-by: Bart Van Assche <bvanassche@google.com>
Let epoll_wait() wake up healthd if a receive buffer overflow has
happened. If a receive buffer overflow happened, this indicates that one
or more power supply uevent messages have been discarded. Handle this by
updating the battery statistics. This is the approach recommended in the
netlink(7) man page. From that manual page: "However, reliable
transmissions from kernel to user are impossible in any case. The kernel
can't send a netlink message if the socket buffer is full: the message
will be dropped and the kernel and the user-space process will no longer
have the same view of kernel state. It is up to the application to
detect when this happens (via the ENOBUFS error returned by recvmsg(2))
and resynchronize."
Bug: 362986353
Change-Id: I0c89907eaa014f9e2859a73b29239e82f066f03f
Signed-off-by: Bart Van Assche <bvanassche@google.com>
Previous commit was reverted as it removed wifi vintf fragment from
devices, which was caused by 'no_full_install' property from
vintf_fragment module. This change relands the change, with removing
no_full_install property from the vintf_fragment module
Bug: 322089980
Test: aosp_cf_x86_64_phone build succeeded
Test: mokey_go32 build contains
/vendor/etc/vintf/manifest/android.hardware.wifi.supplicant.xml file
Change-Id: I523ce570068b180805b65f984a0d6def0612db87
Make the code somewhat easier to read by using designated initializers.
No functionality has been changed.
Bug: 362986353
Change-Id: I707ea158c9c45eeb2662d7b5c1efc9b63f0375cb
Signed-off-by: Bart Van Assche <bvanassche@google.com>
Instead of hard-coding input lengths, let the compiler calculate the
input length.
Change-Id: I47d849b85dd983706bfada0293ccbdd04c8a597a
Signed-off-by: Bart Van Assche <bvanassche@google.com>
Instead of calling ScheduleBatteryUpdate() every time a uevent has been
received, only call it after the netlink socket receive buffer has been
drained. This change is safe because the contents of the power supply
uevent messages is ignored.
A subtle change in this CL is that an additional call to
uevent_kernel_multicast_recv() is introduced after all the receive
buffer has been drained. In case of a receive buffer overflow, this
extra call will receive and clear the socket error (sk_err).
Bug: 362986353
Change-Id: Ic1c489dde3338f0142def743b4cd654363517486
Signed-off-by: Bart Van Assche <bvanassche@google.com>
