This is used on cuttlefish for tests, and so it has to be frozen like
1.0 in order to avoid having to add an exception to the test (which is
considered the worst of all bad solutions here).
Bug: 191115626
Test: build (hash correctness check is done at build time)
Change-Id: I3bbe18e6f6e21c39f8e5efd0ddcbfb0c66385f8c
Freeze vehicle hal interface for android s.
Bug: 157608908
Test: atest vts_treble_vintf_vendor_test
Change-Id: I092f7c7facbb08f381560840c449ae1211625c65
Adding TEST_PATTERN_MODE_BLACK to support the new sensor privacy
feature on more limited-capability camera implementations.
Also updating older docs due to an API being moved to public.
Test: Camera CTS continues to pass
Bug: 189507251
Change-Id: I043d011ad43070d6c402cdffbff3d2e9b70ffd7b
Currently, vendors are asked to duplicate old events to onEvent()
and onEvent_1_1(). This is not the typically way other modules
would do. Thus, remove the requirement of duplicate events,
and replace it with only firing onEvent_1_1 when feasible.
Note no VTS is added currently, from vendor feedback, there is
no reliable way to guarantee the callbacks will be called in the
test.
Test: hidl-gen -L hash -r android.hardware:hardware/interfaces \
android.hardware.tetheroffload.control@1.1
Bug: 149467454
Merged-In: I75c1a7788e5d48fb3e2836d54b4fd854c0247214
Change-Id: I75c1a7788e5d48fb3e2836d54b4fd854c0247214
(cherry-picked from ag/14408065)
Currently, vendors are asked to duplicate old events to onEvent()
and onEvent_1_1(). This is not the typically way other modules
would do. Thus, remove the requirement of duplicate events,
and replace it with only firing onEvent_1_1 when feasible.
Note no VTS is added currently, from vendor feedback, there is
no reliable way to guarantee the callbacks will be called in the
test.
Test: hidl-gen -L hash -r android.hardware:hardware/interfaces \
android.hardware.tetheroffload.control@1.1
Bug: 149467454
Change-Id: I75c1a7788e5d48fb3e2836d54b4fd854c0247214
Previously, the NNAPI used std::chrono::steady_clock to represent and
measure timings. However, steady_clock does not count while the system
is suspended. Instead, boot_clock is monotonic like steady_clock but
does include the time when the system is suspended.
This change also indicates that services may convert from
std::chrono::steady_clock::time_point to
android::base::boot_clock::time_point in the HIDL 1.3 NN HAL.
Bug: 183118340
Test: mma
Test: VtsHalNeuralnetworksV1_3TargetTest
Test: VtsHalNeuralnetworksTargetTest
Test: presubmit
Change-Id: I5a7d039a31d9ce98602a301387ec99635f279f42
Merged-In: I5a7d039a31d9ce98602a301387ec99635f279f42
(cherry picked from commit b8cf54cf5a)
Previously, the NNAPI used std::chrono::steady_clock to represent and
measure timings. However, steady_clock does not count while the system
is suspended. Instead, boot_clock is monotonic like steady_clock but
does include the time when the system is suspended.
This change also indicates that services may convert from
std::chrono::steady_clock::time_point to
android::base::boot_clock::time_point in the HIDL 1.3 NN HAL.
Bug: 183118340
Test: mma
Test: VtsHalNeuralnetworksV1_3TargetTest
Test: VtsHalNeuralnetworksTargetTest
Test: presubmit
Change-Id: I5a7d039a31d9ce98602a301387ec99635f279f42
Merged-In: I5a7d039a31d9ce98602a301387ec99635f279f42
Makes a ABI preserving change to radio hal by adding deprecation
comments for following interfaces:
- startLceService
- stopLceService
- pullLceData
- lceData
- setSimCardPower
- setIndicationFilter
- setupDataCall
- deactivateDataCall
- startNetworkScan
- startNetworkScan_1_2
Bug: 170288130
Test: make
Merged-In: I4563b7081dec6fa64b7faff7c8e3c2c3b1239880
Change-Id: I4563b7081dec6fa64b7faff7c8e3c2c3b1239880
(cherry picked from commit 1fd7cb029b)
Makes a ABI preserving change to radio hal by adding deprecation
comments for following interfaces:
- startLceService
- stopLceService
- pullLceData
- lceData
- setSimCardPower
- setIndicationFilter
- setupDataCall
- deactivateDataCall
- startNetworkScan
- startNetworkScan_1_2
Bug: 170288130
Test: make
Change-Id: I4563b7081dec6fa64b7faff7c8e3c2c3b1239880
While we cannot run clang-format on types.hal directly, we can do so on
the canonical Types.h (which is generated from the same template) and
observe the difference. See change Ia43936d8.
Bug: 160667417
Test: m
Change-Id: Id6a237f29c8156b213455ab093d11ed4c2015460
Merged-In: Id6a237f29c8156b213455ab093d11ed4c2015460
(cherry picked from commit dfc4a2fa32)
NNAPI HAL comment strings were reformated due to
template changes for new versioning scheme.
Test: Image built
Bug: 177298018
Change-Id: I67b3a38c087edf6ba3c295f5ac43ca02b8359f6a
Merged-In: I67b3a38c087edf6ba3c295f5ac43ca02b8359f6a
(cherry picked from commit 87ff8d20ae)
NNAPI HAL comment strings were reformated due to
template changes for new versioning scheme.
Test: Image built
Bug: 177298018
Change-Id: I67b3a38c087edf6ba3c295f5ac43ca02b8359f6a
The HAL 1.0 docs are using the incorrect format for HALs. Update them to
match what is now used in 1.1/1.2.
Fixes: 177248013
Test: presubmits
Change-Id: If5bdac0cec9e271ba6b79ecc10f4b3a93aff040c
Update Contexthub HAL 1.2 to support passing permissions information
about host apps and nanoapps to the HAL and contexthub framework.
Bug: 166846988
Test: hidl-gen && Run VTS against default HAL
Change-Id: I483cb066b3228c4a80bab8f12f8bfee2610c9e6b
HIDL never validated these, and these will be logspam/errors now (error
for interfaces where a new annotation, @SensitiveData, is important not
to have typoes, but warnings where otherwise the annotation is
inconsequential).
Bug: 173732508
Test: builds w/o warnings/errors
Change-Id: Ic95d58098fa0104a3a7f1c85644ab1a015bcdd19
Clarify that configs with the same group should differ only
by refresh rate.
Test: n/a
Merged-In: I2b09689825fc9564665324ff18eb1907765b9016
Change-Id: I2b09689825fc9564665324ff18eb1907765b9016
