[8.1R7] [CTSV] USB Audio Peripheral Attributes Test

[DESCRIPTION]
 Google 从[8.1R7] 开始需要用新的设备测试USB Audio Peripheral Attributes Test

其中三条用到的设备如下:具体测试步骤请参考:

https://source.android.com/compatibility/cts/usb-audio

继续阅读“[8.1R7] [CTSV] USB Audio Peripheral Attributes Test”

[CTS_8.1] android.server.cts.KeyguardLockedTests#testDismissKeyguardActivity_method fail

[DESCRIPTION]
android.server.cts.KeyguardLockedTests#testDismissKeyguardActivity_method fail
 junit.framework.AssertionFailedError: Not in logcat: onDismissSucceeded
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at android.server.cts.KeyguardTestBase.assertInLogcat(KeyguardTestBase.java:70)
at android.server.cts.KeyguardTestBase.assertOnDismissSucceededInLogcat(KeyguardTestBase.java:41)
at android.server.cts.KeyguardLockedTests.testDismissKeyguardActivity_method(KeyguardLockedTests.java:119)

继续阅读“[CTS_8.1] android.server.cts.KeyguardLockedTests#testDismissKeyguardActivity_method fail”

windows环境下repo下载Android源代码

官方推荐Android源码的下载方式是Linux系统上是通过Repo来完成的。Win环境下Repo的使用又依赖Git、Python。源码的下载又涉及到伟大的长城防火墙。所以这篇文章的核心有三个:安装Repo依赖环境、让Repo在Win上面跑起来、使用国内源避开墙。

如果是使用Win10上面用Linux子系统下载,可以参考微软官方的教程(不过依然还是会出问题)。如果直接在Win环境下面,可以参考本教程。

以下是Win下面下载Aosp源代码的步奏。

继续阅读“windows环境下repo下载Android源代码”

repo下载Android源码时报 python windowserror 5

WindowsError: [Error 5]

repo sync之后,突然停在了这个地方

看到这个报错我就有点尴尬了。因为这个repo的脚本是由大神改的。完全不懂脚本啊。
修改后的脚本:

继续阅读“repo下载Android源码时报 python windowserror 5”

windows下repo sync error: cannot initialize work tree

1. 问题描述

下载Android源代码时,出现这个错误

 


2. 问题分析

2.1 查看哪里出了问题

从log来看,.repo/repo/project.py是要关注的地方,可以定位到脚本:
raise GitError("cannot initialize work tree")
其所在的函数为_InitWorkTree

_InitWorkTree完整的代码如下:

继续阅读“windows下repo sync error: cannot initialize work tree”

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失败”

【CTS_All version】android.net.cts.legacy.api22.ConnectivityManagerLegacyTest#testStartUsingNetworkFeature_enableHipri

[DESCRIPTION]

android.net.cts.legacy.api22.ConnectivityManagerLegacyTest
-- testStartUsingNetworkFeature_enableHipri
fail
junit.framework.AssertionFailedError: Did not receive expected CONNECTED broadcast for type 5 after 30000 ms at junit.framework.Assert.fail(Assert.java:50)

继续阅读“【CTS_All version】android.net.cts.legacy.api22.ConnectivityManagerLegacyTest#testStartUsingNetworkFeature_enableHipri”