Argument-dependent lookup will only work for operator>> if the operator
is in one of the argument's namespaces. This caused the enumerations to
pretty-print for V1_0, but not for V1_1 or V1_2. This change ensures the
V1_0 namespace is used.
Test: mma
Test: atest VtsHalNeuralnetworksV1_0TargetTest (verified the test output "OFFLINE" for DeviceStatus and "DEVICE_UNAVAILABLE" for ErrorStatus instead of raw byte value representation)
Test: atest VtsHalNeuralnetworksV1_1TargetTest (verified the test output "OFFLINE" for DeviceStatus and "DEVICE_UNAVAILABLE" for ErrorStatus instead of raw byte value representation)
Test: atest VtsHalNeuralnetworksV1_2TargetTest (verified ran and passed tests)
Fixes: 124316129
Change-Id: I764a46e2d87615b1f3da0ab0e6edb134bb533887
(cherry picked from commit 42a35bee10)
am: af9e17465b -s ours
am skip reason: change_id If8b8cabd249f17247d8a5278b8360685c97c68e6 with SHA1 b9319bd3bf is in history
Change-Id: Ibedd716ac9a4cc19212c2810653155d9c2e33a58
This change corrects the description of openDisplay()'s behavior when
new client requests to access a display resource.
Bug: 122671398
Test: N/A
Change-Id: Ic7380748f4907376563771498e8823ed739e09a6
Signed-off-by: Changyeon Jo <changyeon@google.com>
Also some refactoring to make the code more readable and less
indent.
Also clarify the unknown error case that per stream error code
might still be provided.
Test: GCA smoke test and camera CTS
Bug: 120986771
Change-Id: I3b7d3eadfe3895a3fdf3888735a3932d5c6c03bc
Argument-dependent lookup will only work for operator>> if the operator
is in one of the argument's namespaces. This caused the enumerations to
pretty-print for V1_0, but not for V1_1 or V1_2. This change ensures the
V1_0 namespace is used.
Test: mma
Test: atest VtsHalNeuralnetworksV1_0TargetTest (verified the test output "OFFLINE" for DeviceStatus and "DEVICE_UNAVAILABLE" for ErrorStatus instead of raw byte value representation)
Test: atest VtsHalNeuralnetworksV1_1TargetTest (verified the test output "OFFLINE" for DeviceStatus and "DEVICE_UNAVAILABLE" for ErrorStatus instead of raw byte value representation)
Test: atest VtsHalNeuralnetworksV1_2TargetTest (verified ran and passed tests)
Fixes: 124316129
Change-Id: I764a46e2d87615b1f3da0ab0e6edb134bb533887
am: 41b6d5e3df -s ours
am skip reason: change_id I5969beb1ec365c992765f40d7693630606f16e18 with SHA1 350d91b1df is in history
Change-Id: I6137a96f60c840f76db3494d444efaf8532eb045
am: 740e0c6042 -s ours
am skip reason: change_id Id0f28d061dc5858fa00ef1bac5f7aa467d860864 with SHA1 70d25b813e is in history
Change-Id: I35691b0e5d8208c3de49a7e9974022525e76922a
The tmp directory is only removed when the driver reports caching not
supported, otherwise it is kept for debugging purpose.
Test: 1.2 VTS tests with sample driver
Change-Id: I5969beb1ec365c992765f40d7693630606f16e18
Merged-In: I5969beb1ec365c992765f40d7693630606f16e18
(cherry picked from commit 350d91b1df)
Test was failing with segmentation fault (and crashing whole VTS) when
device was not available.
Change-Id: Id0f28d061dc5858fa00ef1bac5f7aa467d860864
Merged-In: Id0f28d061dc5858fa00ef1bac5f7aa467d860864
(cherry picked from commit 70d25b813e)
Modify the document for 'hasKnownUserIntentEmergency'.
In the scenarios that the 'address' in the 'dialInfo' field has other
functions besides the emergency number function, if the
'hasKnownUserIntentEmergency' field is true, the user's intent for this
dial request is emergency call, and the modem must treat this as an
actual emergency dial; if the 'hasKnownUserIntentEmergency' field is
false, Android does not know user's intent for this call.
Test: compile
Bug: 121345950
Change-Id: I3457e7519be564ac5043e06380e9450a1b12425f
(cherry picked from commit 7208840ec0148ad5a01bdf419170282cd1b32437)
am: 6dbe34c37c -s ours
am skip reason: change_id I6baaf54c626778129c1aab4f6622af570b34ec3f with SHA1 4135a8e94c is in history
Change-Id: I51718bedf07a3397b68ed051dc6d716e2b7bb88b
The test is flaky with the current timeout and this CL
increases it to a safe value.
Bug: 120994008
Test: test passes
Change-Id: I63e0e11fcc1eb3bed490cdb21193e2c332cccf80
The actual lockout reset is asynchronous and returns its result in the
onLockoutChanged() callback
Bug: 121196511
Bug: 121198195
Bug: 123262389
Test: Builds
Change-Id: Ia5fd34d77ae1f8dba1a943e0e1fc51d458753090
