arm64-v8a CtsAccessibilityServiceTestCases

junit.framework.AssertionFailedError: Did not receive required events. Got:

junit.framework.AssertionFailedError: Did not receive required events. Got:

junit.framework.AssertionFailedError: Did not receive required events. Got:

junit.framework.AssertionFailedError: Did not receive required events. Got:

junit.framework.AssertionFailedError: Did not receive required events. Got:

junit.framework.AssertionFailedError: Did not receive required events. Got:

java.lang.AssertionError: More than 2.0% of pixels have wrong color primaryPixels=253799 secondaryPixels=0 wrongPixels=104281

java.lang.AssertionError: on-device tests failed:

java.lang.AssertionError: on-device tests failed:

java.lang.AssertionError: on-device tests failed:

java.lang.AssertionError: on-device tests failed:

java.lang.AssertionError: on-device tests failed:

java.lang.AssertionError: on-device tests failed:

android.autofillservice.cts.RetryableException: waitForObject(BySelector [RES='\Qandroid:id/autofill_dataset_picker\E']) (timeout=UI_DATASET_PICKER_TIMEOUT: [current=10000ms; multiplier=2.0x; max=10000ms])

java.lang.AssertionError: Should not be showing save UI for type 0 after 5000ms, but got [Save to InstrumentedAutoFillService?, NO THANKS, SAVE]

java.lang.Exception: There were 4 errors:

java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it.

java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it.

java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it.

java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: getActiveSubscriptionInfoCount() should be non-zero

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

junit.framework.AssertionFailedError: This test requires a SIM card with carrier privilege rule on it.

java.lang.AssertionError: This test requires a SIM card with carrier privilege rule on it.

java.lang.AssertionError: On-device tests failed:

java.lang.AssertionError: On-device tests failed:

java.lang.AssertionError: On-device tests failed:

java.lang.AssertionError: On-device tests failed:

java.lang.AssertionError: System feature android.hardware.vulkan.level version 1 doesn't match best physical device hardware level 0 expected:<0> but was:<1>

java.lang.AssertionError: on-device tests failed:

java.lang.Exception: Failed on curve 0 and challege 0

java.lang.Exception: Failed on key size 512 challenge [], purposes [2, 3] and paddings [PKCS1]

java.lang.AssertionError: Invalid IP address incorrectly recognized as valid: 1.2.3.4.

java.lang.AssertionError

java.net.ConnectException: Failed to connect to google-ipv6test.appspot.com/31.13.72.34:80

android.system.ErrnoException: DatagramCheck on [type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), failover: false, available: true, roaming: false] failed: EPROTO (Protocol error)

java.lang.AssertionError: Could not open session

java.lang.AssertionError

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.io.IOException: Secure Element is not present.

java.lang.AssertionError: Unexpected Exception java.io.IOException: Secure Element is not present.

java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: unexpected exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError: View with text 'Fragment preference' was not found!

java.lang.AssertionError: View with text 'List preference' was not found!

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError: Screenshots do not match!

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.AssertionError

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer First printer even though we retried.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer First printer even though we retried.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer First printer even though we retried.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899209582 and now the last time the queue went idle was: 1575899246475. If these numbers are the same your activity might be hogging the event queue.

java.lang.AssertionError: Activity was not destroyed

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899259287 and now the last time the queue went idle was: 1575899304444. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899160109 and now the last time the queue went idle was: 1575899204291. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575899108030 and now the last time the queue went idle was: 1575899155213. If these numbers are the same your activity might be hogging the event queue.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Test printer even though we retried.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897441987 and now the last time the queue went idle was: 1575897483621. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897243247 and now the last time the queue went idle was: 1575897288314. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897342531 and now the last time the queue went idle was: 1575897386474. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897392246 and now the last time the queue went idle was: 1575897437553. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897292869 and now the last time the queue went idle was: 1575897337397. If these numbers are the same your activity might be hogging the event queue.

java.lang.AssertionError: Activity was not destroyed

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried.

Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details

Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried.

Test failed to run to completion. Reason: 'Failed to receive adb shell test output within 1800000 ms. Test may have timed out, or adb connection to device became unresponsive'. Check device logcat for details

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer TestPrinter even though we retried.

android.support.test.uiautomator.UiObjectNotFoundException: Could not find printer Printer1 even though we retried.

java.lang.AssertionError: Activity was not destroyed

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898304820 and now the last time the queue went idle was: 1575898345955. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898354488 and now the last time the queue went idle was: 1575898399040. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898404157 and now the last time the queue went idle was: 1575898448115. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898453874 and now the last time the queue went idle was: 1575898499195. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898503618 and now the last time the queue went idle was: 1575898548925. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898553278 and now the last time the queue went idle was: 1575898598346. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898603060 and now the last time the queue went idle was: 1575898646419. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898652777 and now the last time the queue went idle was: 1575898696496. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898702504 and now the last time the queue went idle was: 1575898747574. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898752240 and now the last time the queue went idle was: 1575898797655. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897699959 and now the last time the queue went idle was: 1575897741663. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898802670 and now the last time the queue went idle was: 1575898846738. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898852749 and now the last time the queue went idle was: 1575898895438. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897749385 and now the last time the queue went idle was: 1575897793102. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897799055 and now the last time the queue went idle was: 1575897842100. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575897849187 and now the last time the queue went idle was: 1575897893254. If these numbers are the same your activity might be hogging the event queue.

java.lang.AssertionError: Activity was not destroyed

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898103578 and now the last time the queue went idle was: 1575898149651. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898155062 and now the last time the queue went idle was: 1575898200729. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898205902 and now the last time the queue went idle was: 1575898250809. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575898255096 and now the last time the queue went idle was: 1575898299884. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575896935294 and now the last time the queue went idle was: 1575896979346. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575896883681 and now the last time the queue went idle was: 1575896929209. If these numbers are the same your activity might be hogging the event queue.

java.lang.AssertionError: Activity was not destroyed

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575896984948 and now the last time the queue went idle was: 1575897030913. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575908769722 and now the last time the queue went idle was: 1575908810020. If these numbers are the same your activity might be hogging the event queue.

java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=android.print.cts/android.print.test.PrintDocumentActivity (has extras) } within 45 seconds. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1575908717892 and now the last time the queue went idle was: 1575908763949. If these numbers are the same your activity might be hogging the event queue.

java.lang.AssertionError: Activity was not destroyed

junit.framework.AssertionFailedError: Expected to get a IMAGE_CAPTURE result; your camera app should respond to the CAMERA and DPAD_CENTER keycodes

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError

junit.framework.AssertionFailedError: These packages should not be signed with a well known key: [com.android.storagemanager, com.android.printspooler, com.android.backup, com.android.defcontainer, com.android.systemui.overlay.ct, com.qualcomm.qti.poweroffalarm, com.android.protips, com.qualcomm.qti.simsettings, com.android.pacprocessor, android.telephony.overlay.cmcc, com.android.wallpaper.livepicker, com.android.providers.telephony, com.qualcomm.qti.ltedirect, com.qualcomm.qti.networksetting, com.qualcomm.qti.roamingsettings, com.android.providers.contacts, com.qualcomm.qti.qmmi, com.qualcomm.qti.qms.service.trustzoneaccess, com.android.mtp, com.android.sharedstoragebackup, com.android.documentsui, com.android.launcher3, com.android.bookmarkprovider, com.android.vpndialogs, org.codeaurora.gallery, com.google.android.gmsintegration, com.qualcomm.qti.autoregistration, com.android.emergency, com.android.internal.display.cutout.emulation.corner, com.qualcomm.simcontacts, com.android.carrierdefaultapp, com.qualcomm.qti.optinoverlay, com.qualcomm.qti.dynamicddsservice, com.android.location.fused, com.android.statementservice, com.android.systemui.overlay.cmcc, com.android.systemui.theme.dark, com.android.providers.settings, com.qti.qualcomm.datastatusnotification, com.android.systemui, org.codeaurora.ims, com.android.bips, com.android.companiondevicemanager, com.qualcomm.location, com.android.dreams.basic, com.qualcomm.qti.remoteSimlockAuth, com.qualcomm.qcrilmsgtunnel, com.android.shell, com.qualcomm.embms, com.qti.xdivert, com.android.backupconfirm, com.qualcomm.timeservice, com.android.settings, com.android.providers.userdictionary, com.qualcomm.qti.ims, com.qualcomm.qti.telephonyservice, com.android.soundrecorder, com.qualcomm.qti.confdialer, com.android.settings.intelligence, com.qti.dpmserviceapp, com.android.bluetoothmidiservice, com.android.internal.display.cutout.emulation.double, com.android.carrierconfig, com.android.phone, com.android.mms.service, com.android.egg, com.android.captiveportallogin, com.android.inputdevices, cn.nubia.systemupdate, com.android.calllogbackup, com.android.providers.partnerbookmarks, com.android.providers.calendar, com.qti.confuridialer, com.android.externalstorage, org.codeaurora.bluetooth, com.qualcomm.qti.callfeaturessetting, com.qualcomm.qti.services.secureui, com.android.server.telecom, android.ui.overlay.ct, com.android.keychain, com.android.wallpaperbackup, cn.nubia.factory, com.android.networksettings.overlay.ct, com.android.managedprovisioning, com.android.providers.media, com.android.stk, com.cyanogenmod.filemanager, com.android.wallpapercropper, com.android.mms.overlay.cmcc, android, org.codeaurora.snapcam, cn.nubia.advanced, com.android.certinstaller, com.android.settings.overlay.cmcc, com.qualcomm.qti.qtisystemservice, com.android.se, com.android.proxyhandler, com.android.simappdialog, com.android.musicfx, com.android.music, com.android.smspush, com.android.providers.downloads, com.qti.qualcomm.deviceinfo, com.qualcomm.atfwd, com.android.internal.display.cutout.emulation.tall, com.android.bluetooth, com.qualcomm.location.XT, com.android.providers.downloads.ui, com.qualcomm.qti.lpa, com.qti.diagservices, com.android.providers.blockednumber, com.qualcomm.qti.uim, com.android.traceur, com.qualcomm.qti.callenhancement, com.android.htmlviewer]

java.lang.NullPointerException: Attempt to invoke virtual method 'void android.support.test.uiautomator.UiObject2.click()' on a null object reference

junit.framework.AssertionFailedError

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

java.lang.IllegalArgumentException: Invalid destinationAddress

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

junit.framework.AssertionFailedError: [RERUN] SIM card does not provide phone number. Use a suitable SIM Card.

junit.framework.AssertionFailedError: Action failed to complete before timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

Wanted but not invoked:

java.lang.AssertionError: expected:<6> but was:<7>

Wanted but not invoked:

java.lang.AssertionError

java.lang.AssertionError

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

java.lang.SecurityException: Injecting to another application requires INJECT_EVENTS permission

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

java.lang.AssertionError: Missing START_DRAG

org.junit.ComparisonFailure: expected:<[TestDialog]> but was:<[StatusBar]>

org.junit.ComparisonFailure: expected:<[android.server.cts.wm/android.server.wm.DialogFrameTestActivity]> but was:<[StatusBar]>

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

junit.framework.AssertionFailedError: unexpected timeout

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError: Unexpected Exception java.lang.SecurityException: Exception in setUpChannelAccess()java.security.AccessControlException: SecureElement-AccessControlEnforceraccess denied: No ARF exists

java.lang.AssertionError