android.security.cts.PackageSignatureTest
testPackageSignatures (fail)
testPackageSignatures (fail)
单跑命令: run cts -c android.security.cts.PackageSignatureTest -m testPackageSignatures
之所以会Fail, 是因为这两个apk用了google 默认的签名
相关的FAQ贵司可以参考:
ID: FAQ05362
如何采用第三方带密码的密钥进行APK签名
相关的FAQ贵司可以参考:
ID: FAQ05362
如何采用第三方带密码的密钥进行APK签名
如果是第三方APK的话,贵司有如下三种方案:
1. 如果非必要apk,卸载掉即可
2.请第三方apk提供商直接修改即可,不能用google 默认的apk,
3.贵司自行修改
自行修改参考方式如下:
如何手动给apk签名,在相应版本的alps/下执行以下命令:
java -jar out/host/linux-x86/framework/signapk.jar build/target/product/security/common/platform.x509.pem build/target/product/security/common/platform.pk8 Example.apk Example-signMTK.apk
PS:build/target/product/security/common/platform.x509.pem这个是对应的默认mtk签名路径,如果贵司使用自己的签名key,则需要修改为对应的路径
网络上的参考: http://blog.csdn.net/wys7250578/article/details/8959480
ID: FAQ05362
如何采用第三方带密码的密钥进行APK签名
1. 如果非必要apk,卸载掉即可
2.请第三方apk提供商直接修改即可,不能用google 默认的apk,
3.贵司自行修改
自行修改参考方式如下:
如何手动给apk签名,在相应版本的alps/下执行以下命令:
java -jar out/host/linux-x86/framework/signapk.jar build/target/product/security/common/platform.x509.pem build/target/product/security/common/platform.pk8 Example.apk Example-signMTK.apk
PS:build/target/product/security/common/platform.x509.pem这个是对应的默认mtk签名路径,如果贵司使用自己的签名key,则需要修改为对应的路径
网络上的参考: http://blog.csdn.net/wys7250578/article/details/8959480
ID: FAQ05362
如何采用第三方带密码的密钥进行APK签名
Android CTS Setup SOP.pptx
参考49~51页修改签名
参考49~51页修改签名
这个问题你需要自己gen一个default key,然后重新build system img,具体做法如下:
1,generate key.
./makeMtk <project> gen-relkey
2,Sign binary released APK
1,Turn on “MTK_SIGNATURE_CUSTOMIZATION” in “mediatek/config/common/ProjectConfig.mk” or “mediatek/config/<project>/ProjectConfig.mk” (if both have this switch, <project> setting will overwrite common setting),
2,Make sure “MTK_INTERNAL” is disabled
3,If the above steps are checked ok, please clean the alps/out/ folder then build the project
4,Start a normal build, the binary released APK will be signed automatically
1,generate key.
./makeMtk <project> gen-relkey
2,Sign binary released APK
1,Turn on “MTK_SIGNATURE_CUSTOMIZATION” in “mediatek/config/common/ProjectConfig.mk” or “mediatek/config/<project>/ProjectConfig.mk” (if both have this switch, <project> setting will overwrite common setting),
2,Make sure “MTK_INTERNAL” is disabled
3,If the above steps are checked ok, please clean the alps/out/ folder then build the project
4,Start a normal build, the binary released APK will be signed automatically
关于android.security.cts.PackageSignatureTest fail项,麻烦查看SOP Google Default Key部分,大概在40页左右
DCC:
/Document Tree/SW/3G Phone Data/Smart Phone/Standard Package/MT6575 SW Doc Package/Certification/CTS/Android CTS Setup SOP.pptx
DCC:
/Document Tree/SW/3G Phone Data/Smart Phone/Standard Package/MT6575 SW Doc Package/Certification/CTS/Android CTS Setup SOP.pptx
这个命令adb shell dumpsys package > package.txt
检查内部的packages
检查内部的packages
android.security.cts.AudioPolicyBinderTest
-- test_isStreamActive fail junit.framework.AssertionFailedError at android.security.cts.AudioPolicyBinderTest.test_isStreamActive(AudioPolicyBinderTest.java:48)
-- test_startOutput fail junit.framework.AssertionFailedError at android.security.cts.AudioPolicyBinderTest.test_startOutput(AudioPolicyBinderTest.java:32)
-- test_stopOutput fail junit.framework.AssertionFailedError at android.security.cts.AudioPolicyBinderTest.test_stopOutput(AudioPolicyBinderTest.java:40)
-- test_isStreamActive fail junit.framework.AssertionFailedError at android.security.cts.AudioPolicyBinderTest.test_isStreamActive(AudioPolicyBinderTest.java:48)
-- test_startOutput fail junit.framework.AssertionFailedError at android.security.cts.AudioPolicyBinderTest.test_startOutput(AudioPolicyBinderTest.java:32)
-- test_stopOutput fail junit.framework.AssertionFailedError at android.security.cts.AudioPolicyBinderTest.test_stopOutput(AudioPolicyBinderTest.java:40)
MTK==>
waiting for google feedback.
已提交分析材料给Google,等待google 反馈.
可以申请分析报告.
西研所定位问题点==>
status_t status = aps->startOutput(output, (audio_stream_type_t)(-1), session);
if (status == NO_ERROR) {
return false