[VTS10R3][Vsim]VtsTrebleVendorVintfTest

问题描述

VtsTrebleVendorVintfTest
VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.HalsAreServed/0_64bit fail:
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
android.hardware.radio@1.2::IRadio not available.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
android.hardware.radio@1.2::ISap not available.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
android.hardware.radio@1.4::IRadio not available.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51
vendor.mediatek.hardware.mtkradioex@1.5::IMtkRadioEx not available.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:51

解决方案

继续阅读“[VTS10R3][Vsim]VtsTrebleVendorVintfTest”

[CTS10R3]android.media.cts.HeifWriterTest

问题描述

 CtsMediaTestCases
android.media.cts.HeifWriterTest#testInputBitmap_Grid_Handler
android.media.cts.HeifWriterTest#testInputBitmap_Grid_NoHandler
android.media.cts.HeifWriterTest#testInputBitmap_NoGrid_Handler
android.media.cts.HeifWriterTest#testInputBitmap_NoGrid_NoHandler
android.media.cts.HeifWriterTest#testInputBuffer_Grid_Handler
android.media.cts.HeifWriterTest#testInputBuffer_Grid_NoHandler
android.media.cts.HeifWriterTest#testInputBuffer_NoGrid_Handler
android.media.cts.HeifWriterTest#testInputBuffer_NoGrid_NoHandler
android.media.cts.HeifWriterTest#testInputSurface_Grid_Handler
android.media.cts.HeifWriterTest#testInputSurface_Grid_NoHandler
android.media.cts.HeifWriterTest#testInputSurface_NoGrid_Handler
android.media.cts.HeifWriterTest#testInputSurface_NoGrid_NoHandler
Fail:
java.lang.NullPointerException

解决方案

继续阅读“[CTS10R3]android.media.cts.HeifWriterTest”

[CTS10R3]CtsMediaTestCases

问题描述

CtsMediaTestCases
android.media.cts.HeifWriterTest#testInputBitmap_Grid_Handler
android.media.cts.HeifWriterTest#testInputBitmap_Grid_NoHandler
android.media.cts.HeifWriterTest#testInputBitmap_NoGrid_Handler
android.media.cts.HeifWriterTest#testInputBitmap_NoGrid_NoHandler
android.media.cts.HeifWriterTest#testInputBuffer_Grid_Handler
android.media.cts.HeifWriterTest#testInputBuffer_Grid_NoHandler
android.media.cts.HeifWriterTest#testInputBuffer_NoGrid_Handler
android.media.cts.HeifWriterTest#testInputBuffer_NoGrid_NoHandler
android.media.cts.HeifWriterTest#testInputSurface_Grid_Handler
android.media.cts.HeifWriterTest#testInputSurface_Grid_NoHandler
android.media.cts.HeifWriterTest#testInputSurface_NoGrid_Handler
android.media.cts.HeifWriterTest#testInputSurface_NoGrid_NoHandler
Fail1:
java.util.concurrent.TimeoutException: timed out waiting for result
at androidx.heifwriter.HeifWriter$ResultWaiter.waitForResult(HeifWriter.java:683)
at androidx.heifwriter.HeifWriter.stop(HeifWriter.java:510)
at android.media.cts.HeifWriterTest.doTest(HeifWriterTest.java:501)
at android.media.cts.HeifWriterTest.doTestForVariousNumberImages(HeifWriterTest.java:265)
at android.media.cts.HeifWriterTest.testInputBitmap_Grid_Handler(HeifWriterTest.java:210)
Fail2:
java.lang.NullPointerException
at android.media.MediaCodec.native_setup(Native Method)
at android.media.MediaCodec.<init>(MediaCodec.java:1864)
at android.media.MediaCodec.createByCodecName(MediaCodec.java:1842)
at androidx.heifwriter.HeifEncoder.<init>(HeifEncoder.java:218)
at androidx.heifwriter.HeifWriter.<init>(HeifWriter.java:355)
at androidx.heifwriter.HeifWriter$Builder.build(HeifWriter.java:296)
at android.media.cts.HeifWriterTest.doTest(HeifWriterTest.java:450)
at android.media.cts.HeifWriterTest.doTestForVariousNumberImages(HeifWriterTest.java:265)
at android.media.cts.HeifWriterTest.testInputBitmap_Grid_Handler(HeifWriterTest.java:210)

[VTS10.0_r3]VtsHalMediaOmxV1_0Host

问题描述

VtsHalMediaOmxV1_0Host

VtsHalMediaOmxV1_0Host#ComponentHidlTest.Flush_OMX.MTK.VIDEO.DECODER.DIVX3_video_decoder.divx3(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.Flush_OMX.MTK.VIDEO.DECODER.DIVX_video_decoder.divx(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.Flush_M_OMX.MTK.VIDEO.DECODER.DIVX3_video_decoder.divx3(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.Flush_M_OMX.MTK.VIDEO.DECODER.DIVX_video_decoder.divx(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.PortModeConfig_OMX.MTK.VIDEO.DECODER.DIVX3_video_decoder.divx3(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.PortModeConfig_OMX.MTK.VIDEO.DECODER.DIVX_video_decoder.divx(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.StateTransitions_OMX.MTK.VIDEO.DECODER.DIVX3_video_decoder.divx3(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.StateTransitions_OMX.MTK.VIDEO.DECODER.DIVX_video_decoder.divx(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.PortEnableDisable_Idle_OMX.MTK.VIDEO.DECODER.DIVX3_video_decoder.divx3(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.PortEnableDisable_Idle_OMX.MTK.VIDEO.DECODER.DIVX_video_decoder.divx(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.PortEnableDisable_Execute_OMX.MTK.VIDEO.DECODER.DIVX3_video_decoder.divx3(default)_64bit
VtsHalMediaOmxV1_0Host#ComponentHidlTest.PortEnableDisable_Execute_OMX.MTK.VIDEO.DECODER.DIVX_video_decoder.divx(default)_64bit
Fail:
hardware/interfaces/media/omx/1.0/vts/functional/common/media_hidl_test_common.cpp:359
Expected equality of these values:
  status
    Which is: 4-byte object <EA-FF FF-FF>
  ::android::hardware::media::omx::V1_0::Status::OK
    Which is: 4-byte object <00-00 00-00>
hardware/interfaces/media/omx/1.0/vts/functional/common/media_hidl_test_common.cpp:399
Expected: allocateBuffer(omxNode, &buffer, portIndex, portDef.nBufferSize, portMode) doesn't generate new fatal failures in the current thread.
  Actual: it does.
hardware/interfaces/media/omx/1.0/vts/functional/common/media_hidl_test_common.cpp:457
Expected: allocatePortBuffers( omxNode, oBuffer, kPortIndexOutput, pm[1], allocGrap) doesn't generate new fatal failures in the current thread.
  Actual: it does.
hardware/interfaces/media/omx/1.0/vts/functional/component/VtsHalMediaOmxV1_0TargetComponentTest.cpp:527
Expected: changeStateLoadedtoIdle(omxNode, observer, &iBuffer, &oBuffer, kPortIndexInput, kPortIndexOutput, portMode) doesn't generate new fatal failures in the current thread.
  Actual: it does.

从log可以看出沒有divx license:

Line 22818: 03-12 07:45:10.007   706   814 E VPUD    : DivX license so is missed

[VTS10.0R3]VtsHalSensorsV2_0Target

问题描述

VtsHalSensorsV2_0Target
VtsHalSensorsV2_0Target#SensorsHidlTest.AccelerometerBatchingOperation(default)_64bit
VtsHalSensorsV2_0Target#SensorsHidlTest.MagnetometerBatchingOperation(default)_64bit
VtsHalSensorsV2_0Target#SensorsHidlTest.AccelerometerBatchingOperation(default)_32bit
VtsHalSensorsV2_0Target#SensorsHidlTest.MagnetometerBatchingOperation(default)_32bit
Fail:
hardware/interfaces/sensors/common/vts/utils/SensorsHidlTestBase.cpp:583 Expected: (nEvent) > ((size_t)(minFifoCount * 9 / 10)), actual: 2700 vs 2700 03-16 15:16:25 I/TestFailureListener: FailureListener.testFailed
Fail:
hardware/interfaces/sensors/common/vts/utils/SensorsHidlTestBase.cpp:583 Expected: (nEvent) > ((size_t)(minFifoCount * 9 / 10)), actual: 540 vs 540 03-16 15:16:25 I/TestFailureListener: FailureListener.testFailed

MainlineModule

问题描述

GtsOsTestCases
com.google.android.os.gts.MainlineModulePreloadTest
com.google.android.os.gts com.google.android.os.gts.MainlineConfigurationTest#testMainlineApprovedTrain

解决方案

Q1: Mainline release 是什麼? What is Mainline release?Ans: Google 列進 Mainline scope 的 module 會由 Google 出 prebuilt binary 並 release 給有 GMS license 的廠商, Android 10 要過 Google GMS 認證需要 preload Mainline release, 也就是要用 Google build 的 binary, 不能用客戶修改過、客戶自己用 AOSP build 出的 binary。

继续阅读“MainlineModule”

[CTS9_R11][CtsUsageStatsTestCases

问题描述

android.app.usage.cts.NetworkUsageStatsTest#testAppDetails
android.app.usage.cts.NetworkUsageStatsTest#testAppSummary
android.app.usage.cts.NetworkUsageStatsTest#testCallback
android.app.usage.cts.NetworkUsageStatsTest#testDeviceSummary
android.app.usage.cts.NetworkUsageStatsTest#testTagDetails
android.app.usage.cts.NetworkUsageStatsTest#testUidDetails
android.app.usage.cts.NetworkUsageStatsTest#testUidTagStateDetails
android.app.usage.cts.NetworkUsageStatsTest#testUserSummary
Fail:
junit.framework.AssertionFailedError: android.hardware.wifi is a reported system feature, however no corresponding connected network interface was found or the attempt to connect has timed out (timeout = 15000ms). Please make sure you are connected to a WiFi access point.

解决方案

继续阅读“[CTS9_R11][CtsUsageStatsTestCases”

[CTS10R3] CtsProviderUiTestCases fail

问题描述

CtsProviderUiTestCases
android.providerui.cts.MediaStoreUiTest#testImageCaptureWithInadequeteLocationPermissions[0]
android.providerui.cts.MediaStoreUiTest#testGetDocumentUri[0]
android.providerui.cts.MediaStoreUiTest#testGetDocumentUri_ThrowsWithoutPermission[0]
android.providerui.cts.MediaStoreUiTest#testGetDocumentUri_Symmetry[0]
Fail:
java.lang.AssertionError: Expected to get a IMAGE_CAPTURE result; your camera app should respond to the CAMERA and DPAD_CENTER keycodes

解决方案

继续阅读“[CTS10R3] CtsProviderUiTestCases fail”

[VTS10R2]VtsHalWifiSupplicantV1_2Host

问题描述

VtsHalWifiSupplicantV1_2Host
VtsHalWifiSupplicantV1_2Host#SupplicantStaIfaceHidlTest.StartDppEnrolleeInitiator(default,default,default,default,default)_64bit
VtsHalWifiSupplicantV1_2Host#SupplicantStaIfaceHidlTest.StartDppConfiguratorInitiator(default,default,default,default,default)_64bit
VtsHalWifiSupplicantV1_2Host#SupplicantStaNetworkHidlTest.SetGetGroupMgmtCipher(default,default,default,default,default)_64bit
Fail:
hardware/interfaces/wifi/supplicant/1.2/vts/functional/supplicant_sta_iface_hidl_test.cpp:407
Expected equality of these values:
  std::cv_status::no_timeout
    Which is: 4-byte object <00-00 00-00>
  wait(SupplicantStaIfaceHidlTest::DppCallbackType::EVENT_FAILURE)
    Which is: 4-byte object <01-00 00-00>

解决方案

继续阅读“[VTS10R2]VtsHalWifiSupplicantV1_2Host”

在非GO的EEA项目跑CTS Express脚本发生Error!!! Assistant icon is not on screen +1 on EEA build问题

问题描述

 在非GO的EEA项目跑CTS Express脚本发生Error!!! Assistant icon is not on screen +1 on EEA build问题

解决方案

继续阅读“在非GO的EEA项目跑CTS Express脚本发生Error!!! Assistant icon is not on screen +1 on EEA build问题”

[CTS10R2]android.appsecurity.cts.AdoptableHostTest#testEjected

问题描述

android.hardware.camera2.cts.StillCaptureTest#testAeCompensation
Fail:
java.lang.Exception: There were 8 errors:
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.250000) observed(1.000000). Normal exposure time 30001 us, sensitivity 156. Compensated exposure time 30001 us, sensitivity 156, value 4.0 is out of range [0.8, 1.2])
  java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.500000) observed(1.000000). Normal exposure time 30001 us, sensitivity 156. Compensated exposure time 30001 us, sensitivity 156, value 2.0 is out of range [0.8, 1.2])

继续阅读“[CTS10R2]android.appsecurity.cts.AdoptableHostTest#testEjected”

[VTSR10R2]CtsStatsdHostTestCases

问题描述

CtsStatsdHostTestCases
android.cts.statsd.atom.UidAtomTests#testDeviceCalculatedPowerBlameUid
android.cts.statsd.validation.BatteryStatsValidationTests#testPowerBlameUid
Fail:
junit.framework.AssertionFailedError: No power value for uid 10149
junit.framework.AssertionFailedError: No power value for uid 10146
junit.framework.AssertionFailedError: Statsd: No power value for uid 10151

解决方案

继续阅读“[VTSR10R2]CtsStatsdHostTestCases”

[CTS10R2]CtsMediaTestCases

问题描述

CtsMediaTestCases
android.media.cts.VideoDecoderPerfTest#testAvcOther1Perf0320x0240
android.media.cts.VideoDecoderPerfTest#testAvcOther1Perf0720x0480
android.media.cts.VideoDecoderPerfTest#testAvcOther1Perf1280x0720
android.media.cts.VideoDecoderPerfTest#testAvcOther1Perf1920x1080
Fail:
junit.framework.AssertionFailedError: Failed to get achievable frame rates for OMX.MTK.VIDEO.DECODER.AVC.l3 video/avc 320x240
junit.framework.AssertionFailedError: Failed to get achievable frame rates for OMX.MTK.VIDEO.DECODER.AVC.l3 video/avc 320x240
junit.framework.AssertionFailedError: Failed to get achievable frame rates for OMX.MTK.VIDEO.DECODER.AVC.l3 video/avc 720x480
junit.framework.AssertionFailedError: Failed to get achievable frame rates for OMX.MTK.VIDEO.DECODER.AVC.l3 video/avc 1280x720
junit.framework.AssertionFailedError: Failed to get achievable frame rates for OMX.MTK.VIDEO.DECODER.AVC.l3 video/avc 1920x1080

解决方案

继续阅读“[CTS10R2]CtsMediaTestCases”

[VTS10R2]CtsMediaTestCases-android.media.cts.AudioRecordTest#testTimestamp

问题描述

CtsMediaTestCases
CtsMediaTestCases-android.media.cts.AudioRecordTest#testTimestamp
Fail:
java.lang.AssertionError: timestamp frames should be increasing

解决方案

继续阅读“[VTS10R2]CtsMediaTestCases-android.media.cts.AudioRecordTest#testTimestamp”

[CTS10R2]android.view.cts.ASurfaceControlTest#testSurfaceTransaction_setColorAndBuffer_bufferAlpha_0_5

问题描述

CtsViewTestCases
android.view.cts.ASurfaceControlTest#testSurfaceTransaction_setColorAndBuffer_bufferAlpha_0_5
Fail:
java.lang.SecurityException: Permission Denial: startForeground from pid=20136, uid=10154 requires android.permission.INSTANT_APP_FOREGROUND_SERVICE

解决方案

继续阅读“[CTS10R2]android.view.cts.ASurfaceControlTest#testSurfaceTransaction_setColorAndBuffer_bufferAlpha_0_5”

[GTSR3]com.google.android.dialer.gts.GtsDialerDeviceTest#makeCall_verifyDialerWorking

问题描述

GtsDialerDeviceTestCases  com.google.android.dialer.gts.GtsDialerDeviceTest#makeCall_verifyDialerWorking
Fail:
java.lang.AssertionError: Error running self check - Active call audio not available.: Not true that <FAILED> is equal to <SUCCESS>

解决方案

继续阅读“[GTSR3]com.google.android.dialer.gts.GtsDialerDeviceTest#makeCall_verifyDialerWorking”