Unit tests were depending on a non test library unecesarrily and it was
causing unit test build failure.
Fixes: 155239061
Test: atest android.hardware.sensors@2.0-halproxy-unit-tests
Change-Id: I057a432fdbef93680a67558c27ed7adc7fedfbbc
In order to implement Identity Credential on resource-restricted
secure hardware, we need to limit the number of possible
AccessControlProfile in a credential. A limit of 32 means that such
hardware only need to devote four bytes of RAM for a bitmask with
information about which profiles are authorized.
Document this, add new VTS test, and update the default
implementation.
Bug: 155100967
Test: atest android.security.identity.cts
Test: atest VtsHalIdentityTargetTest
Merged-In: Ia4f2ee0013b330561df744e0595f298a0d156122
Change-Id: I2dd672447bedfa9407bf1044e6261af26fd137f9
SOC manufacturers have requested that devices be allowed to ship with R
without using the IRadio 1.5 API.
Fixes: 153495340
Test: build flame
Change-Id: Iba2ac5902e69fc0af0c5f4d7cae4fed77204acd1
Fixed following bugs in WritableIdentityCredential.cpp
- Do not allow startPersonalization to be called more than once per
aidl.
- Do not preceed with beginAddEntry if addAccessControlProfile and
startPersonalization profile count mismatch.
- Verify access control profile ids are unique.
- Do not let empty name space to mess up beginAddEntry.
- Do not allow beginAddEntry to add entries interleaving namespace
groupings. Enforce all entries must be added in namespace "groups"
per aidl.
- Fix counting error that allowed one entries to be added per name
space than startPersonalization limit.
- Do not approve finishAddingEntries if there are more profiles or
entries to be added than startPersonalization set accounting.
- Add testing utilities library for identity credential.
- Refactored end to end tests.
Bug: 154909726
Test: atest VtsHalIdentityTargetTest
Test: atest android.security.identity.cts
Merged-In: I51902681776c6230e49589fc75a8145e79d7d1a6
Change-Id: Ib7c108f67c61125edba6177dcac61cfbf58da671
So it can be used by other Vehicle HAL implementations.
Test: adb shell lshal debug android.hardware.automotive.vehicle@2.0::IVehicle/default --user-hal
Test: adb shell lshal debug android.hardware.automotive.vehicle@2.0::IVehicle/default --help
Test: m -j android.hardware.automotive.vehicle@2.0-emulated-user-hal-lib
Bug: 150167241
Bug: 150409377
Merged-In: I2d0c5039c3b994dfe10d3b411f6d502bebe7cca0
Change-Id: I2d0c5039c3b994dfe10d3b411f6d502bebe7cca0
Also removed the hash check on Vehicle HAL files, as they're still being
worked on.
Test: m
Bug: 15249991
Change-Id: I214ebc9b5bbd71e5db1a1332296ceb4e426c50cf
When calling se reset, connected state should be reported with false and then true.
Bug: 154572079
Test: run vts -m VtsHalSecureElementV1_2TargetTest
Change-Id: I907d32a2c44230b581680d1872c9b01e517a5d81
Switch to std::string and libbase to simplify the test and avoid
string manipulation bugs
Bug: 154070740
Bug: 149044096
Test: atest VtsHalPowerV1_0TargetTest
Change-Id: Ic80ca462cfeb650edcdc6420bf1b3190aa14dbe4
Signed-off-by: Connor O'Brien <connoro@google.com>
This change contains no actual syntactical or semantic changes, just
clarifications on the inputs and outputs.
Test: N/A
Bug: 151082886
Merged-In: I794b8d0360c1eda37b4dbe757d7a7fadcbdda7bc
Change-Id: I5ad596ec0fa4dac7473d8fd435f538dbb5529846
Several features for auto need libc++fs, but the previous solution of
symlinking to external/libcxx would cause problems later down the
line. Instead, we will compile a separate version of libc++fs with a
different namespace, as to not interfere with the canonical
std::filesystem.
Change summary
===============================================================
directory_iterator.cpp:
-----------------------
* _LIBCPP_BEGIN_NAMESPACE_FILESYSTEM --> namespace android::hardware::automotive::filesystem {
* _LIBCPP_END_NAMESPACE_FILESYSTEM --> } // namespace android::hardware::automotive::filesystem
* disable clang-format (to reduce diff size)
* "" --> <> for non-local includes
filesystem_common.h:
--------------------
* FILESYSTEM_COMMON_H --> AUTO_FILESYSTEM_COMMON_H
* "" --> <> for non-local includes
* filesystem --> automotive/filesystem
* don't include apple_availability.h
* add using std::error_code
* _LIBCPP_BEGIN_NAMESPACE_FILESYSTEM --> namespace android::hardware::automotive::filesystem {
* use namespace std::chrono
* use std::error_code, std::is_floating_point, std::micro, std::nano, std::ratio
* LIBCPP_END_NAMESPACE_FILESYSTEM --> } // namespace android::hardware::automotive::filesystem
* disable clang format (to reduce diff size)
filesystem:
-----------
* _LIBCPP_FILESYSTEM --> _LIBAUTO_FILESYSTEM
* std::filesystem --> android::hardware:automotive::filesystem
* _VSTD_FS --> android::hardware::automotive::filesystem
* _LIBCPP_END_NAMESPACE_FILESYSTEM --> } // namespace android::hardware::automotive::filesystem
* Copied _FilesystemClock from chrono
* use namespace std and std::chrono
* use std::basic_string, std::enable_if, std::error_code, and std::false_type
operations.cpp:
---------------
* filesystem --> automotive/filesystem
* "" --> <> for non-local includes
* _LIBCPP_BEGIN_NAMESPACE_FILESYSTEM --> namespace android::hardware::automotive::filesystem {
* _VSTD_FS --> android::hardware::automotive::filesystem
* _LIBCPP_END_NAMESPACE_FILESYSTEM --> } // namespace android::hardware::automotive::filesystem
* disable clang-format (to reduce diff size)
* fix "the the" typo (to pass lint)
Bug: 152067309
Test: Manual
Change-Id: I5551b3e634b85b4d7236e888de68740bfda6aad1
The list of possible paths for the audio configuration
files is now retrieved using audio_get_configuration_paths()
function. All duplicated lists of known configuration
directories have been removed.
Bug: 153680356
Test: atest VtsHalAudioV6_0TargetTest \
VtsHalAudioPolicyV1_0TargetTest \
VtsHalAudioEffectV6_0TargetTest
Change-Id: I1e40fdf8d6e3a5ac339f7f138f62063bb87bd3da
Merged-In: I1e40fdf8d6e3a5ac339f7f138f62063bb87bd3da
on_ring_buffer_data_callback callback is invoked on getting the
corresponding driver/firmware ringbuffer logs. This callback further
stores the ringbuffer data locally in cur_buffer. While the data is
getting updated through this callback, writeRingbufferFilesInternal
can get triggered from a different context which accesses the same buffer
-cur_buffer.
Synchronization is missing between these two contexts while accessing the
buffer and this commit attempts the same.
Bug: 153970986
Test: Manual - collect the bugreport and check the ring buffer logs.
Change-Id: Id99a517f4d72872b84b48c3df75dd29743f3e9b2
