[EVS] Increase VTS stream startup limit to 1000ms Camera sensor bootup and hardware frame synchronization from IVI deserializers can require up to 500ms before streaming begins. Bumping kMaxStreamStartMilliseconds from 500ms to 1000ms accommodates valid hardware initialization latencies without forcing permanent camera power-on or disabling frame sync, avoiding vehicle battery degradation. Also this is the same time limit fixed for HIDL 1.0 VTS test VtsHalEvsV1_0TargetTest.cpp as well. Bug: 481293611 Test: atest VtsHalEvsTargetTest Flag: EXEMPT BUGFIX (cherry picked from commit 4f8d66e62c787074a51434331a0f5c6011f4962b) Cherrypick-From: https://googleplex-android-review.googlesource.com/q/commit:f2dd5cae3bfc70ef15d4d3d9caed20c04352cc03 Merged-In: Ia3b479a13bbadb81b44eab5bf874d87fd31bf9a7 Change-Id: Ia3b479a13bbadb81b44eab5bf874d87fd31bf9a7
diff --git a/automotive/evs/1.1/vts/functional/VtsHalEvsV1_1TargetTest.cpp b/automotive/evs/1.1/vts/functional/VtsHalEvsV1_1TargetTest.cpp index ff7f41c..a3dedd0 100644 --- a/automotive/evs/1.1/vts/functional/VtsHalEvsV1_1TargetTest.cpp +++ b/automotive/evs/1.1/vts/functional/VtsHalEvsV1_1TargetTest.cpp
@@ -18,7 +18,7 @@ // These values are called out in the EVS design doc (as of Mar 8, 2017) -static const int kMaxStreamStartMilliseconds = 500; +static const int kMaxStreamStartMilliseconds = 1000; static const int kMinimumFramesPerSecond = 10; static const int kSecondsToMilliseconds = 1000;
diff --git a/automotive/evs/aidl/vts/VtsHalEvsTargetTest.cpp b/automotive/evs/aidl/vts/VtsHalEvsTargetTest.cpp index aad5478..1fdb330 100644 --- a/automotive/evs/aidl/vts/VtsHalEvsTargetTest.cpp +++ b/automotive/evs/aidl/vts/VtsHalEvsTargetTest.cpp
@@ -59,7 +59,7 @@ namespace { // These values are called out in the EVS design doc (as of Mar 8, 2017) -constexpr int kMaxStreamStartMilliseconds = 500; +constexpr int kMaxStreamStartMilliseconds = 1000; constexpr int kMinimumFramesPerSecond = 10; constexpr int kSecondsToMilliseconds = 1000; constexpr int kMillisecondsToMicroseconds = 1000;