【VTS_P version】VtsTrebleVendorVintfTest 跟hash相关fail

问题描述

 VtsTrebleVendorVintfTest测试时可能会遭遇以下两种情况报hash的错误:
Case1:
01-05 12:25:53 D/ModuleListener: ModuleListener.testStarted(VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit)
01-05 12:25:53 D/ModuleListener: ModuleListener.testFailed(VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit, test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:57
Failed
vendor.sw.swfingerprint@1.0::ISwfingerprint has an empty hash. This is because it was compiled without being frozen in a corresponding current.txt file.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:57
Failed
Case2:

vendor.oppo.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint has an empty hash. This is because it was compiled without being frozen in a corresponding current.txt file.

继续阅读“【VTS_P version】VtsTrebleVendorVintfTest 跟hash相关fail”

P版本上 fileManager上不能新建的问题

问题描述

 在P版本上,进文件管理APP, 进SD卡,或者手机内部存储 无法创建文件:
**MTK 内部机器也存在这个问题
O版本:
进SD卡,或者进入手机内部存储, 都可以创建文件
P版本:
进SD卡,或者进入手机内部存储 ,都不可以创建文件

继续阅读“P版本上 fileManager上不能新建的问题”

【cts_P】CtsLibcoreTestCases libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight

问题描述


run cts -m CtsLibcoreTestCases -t libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight -o
 01-07 16:35:46 I/ModuleListener: [1/1] libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight fail:
junit.framework.ComparisonFailure: expected:<February 27, []04:00 – 00:00> but was:<February 27, [2018, ]04:00 – 00:00>
at junit.framework.Assert.assertEquals(Assert.java:85)
at junit.framework.Assert.assertEquals(Assert.java:91)
at libcore.libcore.icu.DateIntervalFormatTest.testEndAtMidnight(DateIntervalFormatTest.java:442)
at java.lang.reflect.Method.invoke(Native Method)

 

Android P HAL3 metadata中的BLOB stream size配置

问题描述


Android P HAL3版本,camera sensor metadata scaler.h中的BLOB stream size配置

 

解决方案


目前hal3,API2架构camera preview,capture时,default吃的是capture mode(scenario id=1).
相关camera cts测试pass的conditions有:
1.不能超过sensor full resolution (capture mode时的size).
2.能达到30fps.

继续阅读“Android P HAL3 metadata中的BLOB stream size配置”

手机升级到P版本后,很多海外APP报数据库table找不到的错误

问题描述


安装某三方应用后,启动应用,应用crash. crash log中出现如下类似LOG:
SQLite: No Such Table Error’ after copying database from assets
android.database.sqlite.SQLiteException: no such table: xxxxxxxx
crash不一定是报在数据库中,可能是某个逻辑报空指针异常之类的。
但这类问题很可能是因为数据库中查不到数据,导致了空指针异常。

 

继续阅读“手机升级到P版本后,很多海外APP报数据库table找不到的错误”

[GTS_6.0.R1]GtsPlacementTestCases 下6条CaseFail

问题描述


GtsPlacementTestCases  下6条CaseFail
 com.google.android.placement.gts.DefaultIntentTest#testDefaultIntentHandlers
com.google.android.placement.gts.HomescreenLayoutTest#testFolderPlacement
com.google.android.placement.gts.HomescreenLayoutTest#testShortcutPlacement
com.google.android.placement.gts.HomescreenLayoutTest#testWidgetPlacement
com.google.android.placement.gts.InstalledAppsTest#testAppsInstalled
com.google.android.placement.gts.InstalledAppsTest#testSystemAppsInstalled
第一种报错信息:
java.lang.AssertionError: Unable to execute because authorization failed, please ensure the service account key is properly installed..

 

解决方案

继续阅读“[GTS_6.0.R1]GtsPlacementTestCases 下6条CaseFail”

[CTS9.0-R3]CtsUsageStatsTestCases包下,五条case测试fail

问题描述


ndroid.app.usage.cts.NetworkUsageStatsTest#testAppDetails
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903 tag null state STATE_ALL
android.app.usage.cts.NetworkUsageStatsTest#testAppSummary
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903
android.app.usage.cts.NetworkUsageStatsTest#testTagDetails
fail junit.framework.AssertionFailedError: No Rx bytes tagged with 0xf00d for uid 10903
android.app.usage.cts.NetworkUsageStatsTest#testUidDetails
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903
android.app.usage.cts.NetworkUsageStatsTest#testUidTagStateDetails
fail junit.framework.AssertionFailedError: No Rx bytes usage for uid 10903 tag 0xf00d state STATE_FOREGROUND

解决方案

继续阅读“[CTS9.0-R3]CtsUsageStatsTestCases包下,五条case测试fail”

android P 隐藏API对系统APP的影响

android P限制了第三方APK对@hide API的调用,那么对系统APK有什么影响呢?

国内各大手机厂商对ROM进行各种定制,可以很容易绕过这些限制,那对于需要出海并且满足CTS要求的厂商有什么影响呢?

先说结论:对系统厂商APK没有任何影响,依然可调用任何API

  • 第三方APK,受hide限制
  • 系统platform签名APK,不受限制
  • 非platform签名APK,集成在system分区,又在hiddenapi-package-whitelist.xml,不受限制。(且目前不影响CTS)

继续阅读“android P 隐藏API对系统APP的影响”

[VTS 9.0_R3] fail项:VtsHalRadioV1_1Target

[DESCRIPTION]
 armeabi-v7a VtsHalRadioV1_1Target
Test Result Details
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(imsrild1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(imsrild2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(se1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(se2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(slot1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(slot2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(imsrild1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(imsrild2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(se1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
报错讯息如下:
09-27 10:08:35 D/ModuleListener: ModuleListener.testFailed(VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(se1)_32bit, hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
Expected equality of these values:
  CardState::PRESENT
    Which is: 4-byte object <01-00 00-00>
  cardStatus.cardState
    Which is: 4-byte object <00-00 00-00>)
09-27 10:08:35 I/ConsoleReporter: [8/42 armeabi-v7a VtsHalRadioV1_1Target 0123456789ABCDEF] VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(se1)_32bit fail: hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
Expected equality of these values:
  CardState::PRESENT
    Which is: 4-byte object <01-00 00-00>  期望插卡
  cardStatus.cardState
    Which is: 4-byte object <00-00 00-00>  实际无卡
[SOLUTION]

继续阅读“[VTS 9.0_R3] fail项:VtsHalRadioV1_1Target”

Android P上打开AVB2.0的配置方法

AVB2.0 是google 设计的 verified boot 流程用于保护boot,recovery/system/vendor partion的完整性。每一个partion可以设置为hash或者是chain partion方式

   更多AVB2.0的资讯,您可以参考google spec
https://android.googlesource.com/platform/external/avb/+/master/README.md
   如果你的平台使用的kernel版本大于等于4.9,并且是Android P版本,AVB2.0是必须要开启的
   MTK默认的配置为:recovery,systemchain partion,其余为hash。您也可以根据需要修改

   P版本开启AVB2.0的方法

继续阅读“Android P上打开AVB2.0的配置方法”

/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17′ (or `GLIBC_2.18′) not found

Android P 9.0 编译时报如下错误:

原因应该是ubuntu 版本太低 12.04, 要求最低版本:ubuntu 14.04

继续阅读“/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17′ (or `GLIBC_2.18′) not found”

Android P(9.0) userdebug版本执行adb remount失败

[DESCRIPTION]
     在android P版本上如果按照“FAQ18076 android 6.0 M userdebug版本执行adb remount失败”的做法在userdebug版本上执行adb remount会提示以下错误:
remount of the / superblock failed: Permission denied
remount failed
     原因是android P版本后google启用avb(Android Verified Boot)2.0,verified boot and DM-verity默认启用策略发生了变化。详情如下:
DM-Verity behavior changes from vboot1.0 to avb2.0.
On vboot1.0, dm-verity is turned off on eng build and is enabled on userdebug/user build.
DM-verity could be disabled with adb (not fastboot) on userdebug build without unlocking device first.
DM-Verity could not be disabled on user build.
On avb2.0, dm-verity behavior are the same on all build variants.
It’s turned on by default and could only be disabled after device is unlocked.
dm-verity disable flag is moved from system image dm-verity metadata(vboot1.0) to vbmeta image(avb2.0), and you have two ways to disable it: adb and fastboot.
  

继续阅读“Android P(9.0) userdebug版本执行adb remount失败”