cts_gts认证一些fail项解决办法
承接上一篇: http://blog.csdn.net/xxm282828/article/details/48289391
1
com.android.cts.aadb.TestDeviceFuncTest
2
android.app.cts.SystemFeaturesTest
testSensorFeatrues
-- testCameraFeatures
--testSensorFeatures
关于上面的2项，在device.mk中添加：
$(FRAMEWORK_ETC_PATH)/android.hardware. camera.autofo cus.xml:$(PERMISSIONS_PATH)/android.hardware.camera.autofocus.xml \
后，--testCameraFeatures 这一项通过了。
-- testSensorFeatures 这一项去掉的内容比较多，
去掉
android.hardware.sensor.accelerometer.xml
android.hardware.se nsor.gyroscope.xml
android.hardware.sensor.light.xml
android.hardware.sensor.proximi ty.xml
也去掉了
./tablet_core_hardware.xml:29:
./android.hardware.sensor.compass.xml:19:
./handheld_core_hardware.xml:30:
这里面的内容，才通过。
关于testSensorFeatures，请去掉anzhen4_mrd7_w/device.mk中的
$(FRAMEWORK_ETC_PATH)/android.hardware.sensor.compass.xml:$(PERMISSIONS_PATH)/android.hardware.sensor.compass.xml
$(FRAMEWORK_ETC_PATH)/android.hardware.sensor.compass.xml:$(PERMISSIONS_PATH)/android.hardware.sensor.compass.xml
3
libcore.java.net.ConcurrentCloseTest
解决： 连接VPN，测试通过
4
android.net.cts.DnsTest
-- testDnsWorks
testDnsWorks 需要ip v6才可以测试通过，就是找一个可以连接到美国去才行，香港台湾都不行
5
CTS verify 的测试
在测试5.0R3的CTS Verifier Data Backup test的时候，发现只有第一次备份可以成功，但是之后在备份测试就一直不成功了
请在测试步骤中增加红色部分的的命令(一次即可):
adb shell bmgr enable true
adb shell bmgr transport android/com.android.internal.backup.LocalTransport
adb shell bmgr run
或者
adb shell bmgr enable true
adb shell bmgr transport android/com.android.internal.backup.LocalTransport
adb shell bmgr run
或者
在文件vendor/google/products/gms_overlay/frameworks/base/packages/SettingsProvider/res/values/defaults.xml 和
frameworks/base/packages/SettingsProvider/res/values/defaults.xml中，指定def_backup_transport为android/com.android.internal.backup.LocalTransport 即可通过测试。
frameworks/base/packages/SettingsProvider/res/values/defaults.xml中，指定def_backup_transport为android/com.android.internal.backup.LocalTransport 即可通过测试。
6
android.app.cts.ActivityManagerMemoryClassTest
-- testGetMemoryClass
dalvik.vm.heapgrowthlimit 设置至少为192m
7
com.android.cts.devicepolicy.DeviceOwnerTest
testApplicationRestrictions
-- testCaCertManagement
-- testDeviceOwnerSetup
-- testKeyManagement
-- testLockTask
-- testPersistentIntentResolving
-- testScreenCaptureDisabled
解决办法： Settings --- Account --- Remove account already existed.
8
android.admin.cts.DevicePolicyManagerTest
-- testPasswordQuality_complexLetters
-- testPasswordQuality_complexLowerCase
-- testPasswordQuality_complexNonLetter
-- testPasswordQuality_complexNumeric
-- testPasswordQuality_complexSymbols
-- testPasswordQuality_complexUpperCase
解决办法:
--- a/services/devicepolicy/java/com/android/server/devicepolicy/DevicePolicyManagerService.java
+++ b/services/devicepolicy/java/com/android/server/devicepolicy/DevicePolicyManagerService.java
@@ -380,12 +380,15 @@ public class DevicePolicyManagerService extends IDevicePolicyManager.Stub {
int minimumPasswordLowerCase = DEF_MINIMUM_PASSWORD_LOWER_CASE;
- static final int DEF_MINIMUM_PASSWORD_LETTERS = 1;
+ static final int DEF_MINIMUM_PASSWORD_LETTERS = 0;
int minimumPasswordLetters = DEF_MINIMUM_PASSWORD_LETTERS;
- static final int DEF_MINIMUM_PASSWORD_NUMERIC = 1;
+ static final int DEF_MINIMUM_PASSWORD_NUMERIC = 0;
int minimumPasswordNumeric = DEF_MINIMUM_PASSWORD_NUMERIC;
- static final int DEF_MINIMUM_PASSWORD_SYMBOLS = 1;
+ static final int DEF_MINIMUM_PASSWORD_SYMBOLS = 0;
int minimumPasswordSymbols = DEF_MINIMUM_PASSWORD_SYMBOLS;
static final int DEF_MINIMUM_PASSWORD_NON_LETTER = 0;
9
1.Profile-aware location settings //Location那里work profile 不存在
这个在5.0中没有，在5.1中有，可以申请waiver。
10
android.app.cts.ActivityManagerTest
-- testGetRunningAppProcesses
11
以下是部分5.1的waive项目
CTS（ CTS_r3）:
1. android.webkit.cts.WebSettingsTest#testUserAgentString_default
waiver
GTS:
1. com.google.android.os.xts.BuildVersionTest#testReleaseVersion
wavier
2. com.google.android.xts.placement.UiPlacementTest#testPlayStore
如果是China版（non-GMS），可以直接waiver，否则要确保default home screen上有play store，以下是之前Google的回复：
If testPlayStore failed, we can check the image in the GTS report to find the playstore. If playstore could be found, then we can waive this.
12.
[Android L] [GTS] com.google.android.xts.devicepolicy.DeviceOwnerTest#testProxy FAIL
run xts -c com.google.android.xts.devicepolicy.DeviceOwnerTest -m testProxy
Solution:
We found this issue is caused by Google's commit: Fix null handling in proxies (https://android.googlesource.com/platform/frameworks/base/+/93edcc139722cc6c3f8dc3368846ae364d8ae82d). Revert this commit, GTS is passed.
Pasted from: >
13.
- com.google.android.xts.devicepolicy.DeviceOwnerTest#testUserManagement
Solution:
diff --git a/configs/handheld_core_hardware.xml b/configs/handheld_core_hardware.xmlindex 503b837..7f2a355 100644--- a/configs/handheld_core_hardware.xml+++ b/configs/handheld_core_hardware.xml@@ -46,9 +46,6 @@<feature name="android.software.device_admin" />-- <feature name="android.software.managed_users" />-