源
We are constantly reviewing our Android and Google Play policies, tools, APIs, and programs to ensure a safe and secure ecosystem. As part of these ongoing reviews, this week we are announcing two changes that will be enforced starting January 2019:
继续阅读“SMS, CALL_LOG Permissions and Contacts Provider API Changes”
Please make sure that there is no LovelyFonts.apk on your build.
Use this command to check:
adb shell "dumpsys package com.valmedia.fdelux"
If apk exists, you can config LOVELYFONTS_SUPPORT = no to remove it in ProjectConfig.mk.
We recently updated the Unbundled GMS folder with the latest Google Play services (GmsCore) version 13.2.92 binaries. With this version, we introduced the additional APK variants as below:
Please make sure the right APK Variant was used on your device builds if you have downloaded this new version of Google Play services for production purpose.
As part of the GTS v6.0r2 release, we will check for the presence of Android Messages (CarrierServiceTest) by default against all devices for any ACSA (Agreement to preload Carrier Services and Android Messages) partner.
In addition, for any device with Android Message installed, regardless of ACSA status, the GTS tests will run to check proper system permissions for Android Message, as well as checking system permission and privileges for Carrier Services.
The only way to exempt devices/builds from the above tests is for the Google Comms OEM team to write an exemption.
The October releases of the Android Compatibility Test Suite (CTS) for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are released on the AOSP website; see the android-partners announcement for more details.
These releases also contain continuous improvements of tests and test infrastructure and verify security patches up to September 2018 Public Security Bulletin.
These versions will be required for GMS approvals as shown in the table below:
[DESCRIPTION]
GTS 3.0R2在M平台上运行时会报如下错误：
com.google.android.xts.permissions.InitialRuntimePermissionStateTest
-- testAllSystemAppsUsingRuntimePermissionsTargetMncAndAboveSdk fail junit.framework.AssertionFailedError: testAllSystemAppsUsingRuntimePermissionsTargetMncAndAboveSdk errors: Package:com.mediatek.voicecommand.overlay uses runtime permissions but doesn't target 23+ SDK
com.google.android.xts.permissions.InitialRuntimePermissionStateTest
-- testAllSystemAppsUsingRuntimePermissionsTargetMncAndAboveSdk fail junit.framework.AssertionFailedError: testAllSystemAppsUsingRuntimePermissionsTargetMncAndAboveSdk errors: Package:com.mobisystems.office uses runtime permissions but doesn't target 23+ SDK
[SOLUTION]
[DESCRIPTION]
GtsPackageManagerHostTestCases---com.google.android.pm.gts.PackageManagerHostTest#testSettingsReadable
[SOLUTION]
[DESCRIPTION]
run gts -m GtsBackupHostTestCases -t com.google.android.gts.backup.LocaleSettingsRestoreHostSideTest#testLocaleRestore
junit.framework.AssertionFailedError: Locales after restore are not as expected. expected:<[en-US, gl-ES, ga-IE, af-ZA]> but was:<[en-US, gl-ES]>
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.failNotEquals(Assert.java:287)
at junit.framework.Assert.assertEquals(Assert.java:67)
at com.google.android.gts.backup.testscontainerapp.LocaleSettingsRestoreTest.checkLocales(LocaleSettingsRestoreTest.java:105)
at java.lang.reflect.Method.invoke(Native Method)
[SOLUTION]
继续阅读“GTS com.google.android.gts.backup.LocaleSettingsRestoreHostSideTest#testLocaleRestore”
AOSP：即为"Android Open-Source Project"的缩写，中文意为 ："安卓开放源代码项目"。
Google官方宣称：任何人都可以以任何目的使用Android源代码，我们也十分欢迎这样做。但是为了共享整个Android生态系统的应用程序，所有设备制造商必须参加“安卓兼容性计划”，但事实上......在中国很难实现兼容计划~！。
目前，我们可以下载Google原生未定制修改的AOSP版Android源码进行测试编译，但是一定要保证整套源码的健全性，否则无法编译通过。
配置Ubantu系统服务器，需要在“终端”输入指定的命令来安装指定的程序，进行对应的操作，类似于Windows中的命令行，因此在进行接下来的配置操作之前，我们需要搜索并打开打开“终端”程序。
VMware Workstation是一款运行在Windows上的虚拟PC软件，它提供专业技术人员每天所依赖的创新功能，支持 Win 8.1、Win 10 、平板电脑传感器和即将过期的虚拟机，可使你的工作无缝、直观、更具关联性，但VMware64位虚拟机才会支持64位的Ubantu操作系统。
工欲善其事，必先利其器”，要想提高团队整体的开发效率，尽可能的提前完成开发任务，必须要配备一套配置给力的开发设备。源码编译服务器硬件配置的高低，直接影响着系统固件升级和ROM版本发布的速度和效率。
由于目前Google发布的最新版本的Android系统源码体积越来越大，因此，越是定制高版本的系统，对编译服务器的硬件配置要求就越高，这里根据调研，给出目前Android 6.0及以下版本源码定制开发的基本配置，供大家参考。
AVB2.0 是google 设计的 verified boot 流程用于保护boot,recovery/system/vendor partion的完整性。每一个partion可以设置为hash或者是chain partion方式
P版本开启AVB2.0的方法
[SOLUTION]
出现fatal error: openssl/名单.h: No such file or directory。原因是libssl-dev～没有安装
libssl-dev包含libraries, header files and manpages，是openssl的一部分
使用sudo apt-get install libssl-dev来安装libssl-dev
Android P 9.0 编译时报如下错误：
|
1 2 3 4 5 6 7 8 |
<span style="font-family: arial, helvetica, sans-serif;">FAILED: out/soong/.intermediates/external/protobuf/aprotoc/linux_glibc_x86_64/obj/external/protobuf/src/google/protobuf/dynamic_message.o PWD=/proc/self/cwd prebuilts/misc/linux-x86/ccache/ccache prebuilts/clang/host/linux-x86/clang-4691093/bin/clang++ -c -Iexternal/protobuf/android -Iexternal/protobuf/src -Iexternal/protobuf -Wa,--noexecstack -fPIC -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -fstack-protector-strong -m64 -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument -fcolor-diagnostics -Wno-expansion-to-defined -Wno-zero-as-null-pointer-constant -fdebug-prefix-map=$PWD/= -Iexternal/zlib -Iexternal/libcxx/include -Iexternal/libcxxabi/include -Isystem/core/include -Isystem/media/audio/include -Ihardware/libhardware/include -Ihardware/libhardware_legacy/include -Ihardware/ril/include -Ilibnativehelper/include -Iframeworks/native/include -Iframeworks/native/opengl/include -Iframeworks/av/include -Ilibnativehelper/include_jni -Wall -Wno-error=format -Wno-error=format-extra-args -Wno-error=ignored-qualifiers -Wno-error=sign-promo -Wno-unused-function -Wno-sign-compare -Wno-unused-parameter -Wno-sign-promo -Wno-error=return-type -DHAVE_ZLIB=1 -Werror -Wno-error=unused-const-variable -Wno-error=user-defined-warnings -target x86_64-linux-gnu -Bprebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/bin -fPIE -D_USING_LIBCXX -std=gnu++14 -Wsign-promo -Wno-inconsistent-missing-override -Wno-null-dereference -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS -Wno-thread-safety-negative -Wno-gnu-include-next -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8 -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/backward -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/x86_64-linux -nostdinc++ -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -Werror=address-of-temporary -Werror=return-type -Wno-tautological-constant-compare -Wno-null-pointer-arithmetic -Wno-enum-compare -Wno-enum-compare-switch -MD -MF out/soong/.intermediates/external/protobuf/aprotoc/linux_glibc_x86_64/obj/external/protobuf/src/google/protobuf/dynamic_message.o.d -o out/soong/.intermediates/external/protobuf/aprotoc/linux_glibc_x86_64/obj/external/protobuf/src/google/protobuf/dynamic_message.o external/protobuf/src/google/protobuf/dynamic_message.cc prebuilts/clang/host/linux-x86/clang-4691093/bin/clang++.real: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/android/src/android_p0/prebuilts/clang/host/linux-x86/clang-4691093/bin/../lib64/libc++.so.1) prebuilts/clang/host/linux-x86/clang-4691093/bin/clang++.real: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.18' not found (required by /home/android/src/android_p0/prebuilts/clang/host/linux-x86/clang-4691093/bin/../lib64/libc++.so.1) ninja: build stopped: subcommand failed. 15:53:28 ninja failed with: exit status 1 [0;31m#### failed to build some targets (46 seconds) ####[00m</span> |
原因应该是ubuntu 版本太低 12.04， 要求最低版本：ubuntu 14.04
继续阅读“/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' (or `GLIBC_2.18') not found”
The CTS September releases for Android 9.0, 8.1, 8.0, 7.1, 7.0 and 6.0 are available on the Compatibility Test Suite Downloads page. The releases for Android 8.1, 8.0, 7.1, 7.0 and 6.0 also contain continuous improvements of tests and test infrastructure, and verify security patches up to the August 2018 Public Security Bulletin.
Details are available in the following change lists:
On 2018/9/22,Google has announced that STS failed will not block certification from October 1, 2018 , refer the message below . You can keep on sending devices to 3PL for certification
继续阅读“[MTK]STS fail will not block certification from 2018/10/1”
[DESCRIPTION]
GTS测试是云测试测试之前要检查网络，两个基础指标要确认：
1、测试机所连接网络可正常访问google官网；
2、测试机连接网络后可以正常播放youtube官网视频；
测试过程中如有遇到如下现象：
1、测试周期拉长，比如32位项目GTS测试完正常时间一般6-8小时；有时超过这个时间仍然没有生成一次full run的结果；
2、一些视频相关的case失败；
