diff options
| author | sqian <shuoq@google.com> | 2019-07-01 13:20:45 -0700 |
|---|---|---|
| committer | sqian <shuoq@google.com> | 2019-07-01 17:37:24 -0700 |
| commit | 8c9947de8deada14648756814ef09b5dafaed75e (patch) | |
| tree | 3ad31fcc567dd8e8cdc27f6fbd1bbc241848eacf /identity/support/src/cppbor_parse.cpp | |
| parent | 15afbba38a40b251cf7d4fe262472ea81ee4daab (diff) | |
Hang up EmergencyDial after Trigger in VTS
The whole test case run emergencyDial.RadioHidlTest_v1_4 first and then
come after startNetworkScan.RadioHidlTest_v1_4 test case immediately
(within ~3 secs) the NWscan failure is device in emergency call in
progress/connected while doing emergencyDial.RadioHidlTest_v1_4 test
Although emergencyDial.RadioHidlTest_v1_4 only care about command/response
is successful or not and don't care call is established or not, modem do
care about call condition is in idle/progress/connected state before it
can do NWscan
When there's dedicated channel established, modem can not perform AP
request NWscan in parallel as we are single HW modem restriction.
Test: run vts
Bug: 135595082
Change-Id: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
Merged-In: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
(cherry picked from commit 07a53471c45c53c00ca0fbe1d83b23a3f2c2ba76)
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions