Test purpose:
to detect you doing Android system meets the compatibility requirements, popular point that, Google Android system should be considered to meet the conditions, you need to meet.
Such as the frame layer is exposed to certain application layer interfaces, Google is because you believe that there is, and that you delete it, it will fail in the test project. Or, conversely, Google think you should hide interface, you may also be open to fail.
Test conditions:
1. Delivery user version
2.selinux: the Enable
3. connect the ADB, Stay Awake
4. ZTE application programming Key
5. The external network environment (IPv6)
ATV9 test preparation:
Language: English-UN
Wi-Fi: Testing machine & board are required to connect to external networks
vpn wireless account: ASUs vpn password: 1qaz2wsX administrator @ Zheng Zhi
Hong Kong Tunnel wireless account: android_g5 Hong Kong Tunnel code: 87654321 administrator @ Tan Wang
Google account:
account: ztestbcts password: 1qaz2wsX
All rights application startup wizard pops up, all open, agreed.
--- end --- >> Power Wizard to open the debugging the USB
Setting the About --- --- >> >> Build (click below 7 developers get permission) --- >> Return to the previous --- >> {developer} --- >> stay awake && usb debugging ( to stay awake && open adb function)
============== I am dividing line =========== ====
here to emphasize the difference ZTE ATV9 box with the original is that we have added custom modifications: CI CTSEable, only set 1 when u adb port is available, but the network port configuration adb no restrictions.
============== I am dividing line ===============
change the configuration CTSEnable = 1 (restart to take effect): Installation Zheng boss Configure gadgets ProductCfgTool.apk Note: U disk copy &&
Install apk has the authority under the selinux permissive guide key: widevine, dhcp, pleady key .
A key command (create cts / directory in the u disk, put the key)
, On the principle of burning key Please read 'a key command and script writer'
cp / mnt / media_rw / 363A-448D / CTS / .zip / the Data && cd / && the unzip the Data keys.zip the unzip out.zip && && cd / Data / Burn Keys && the chmod 777 && ./burn_hdcp.sh ./burn_widevinekey.sh widevinekeybox_zl && && && ./burn_playready.sh CD / Data / OUT. 1 && echo> / SYS / class / unifykeys / echo the attach && "hdcp22_fw_private"> / sys / class / unifykeys / name && dd if = hdcp22_fw_private.bin of = / sys / class / unifykeys / write
import media files (not turned also, the test media module downloaded from Google): cd ~ / CTS / android- cts-media-1.4 /; ./copy_media.sh -s xxxxxxx
bidirectional usb line tester is connected to the set-top box
last check:
external network system shall ok (linux && testing machine set-top box) of ping through www.baidu.com to
the test machine should be able to detect the adb device STB device
to be tested should be in a set-top box selinux getenforce: Enable Status
on test:
entering test tool directory, a test command, for example:
alec@framework01:~/CTS/cts/android9.0/android-cts-9.0_r7-linux_x86-arm/android-cts/tools$ ./cts-tradefed
cts-tf > run cts -s 003
如有异常，请见GMS认证Q&A综合 文档，如果文档中无你的问题，可以向@吴职钦 @郑智 或者开发经理咨询。