IssueTracker

Our handset with android platform 7.1.1 and density value set to 640 fails to pass this test case. The error info is shown as below

02-21 14:13:28 I/ThemeHostTest: Device density detected as 640 (xxxhdpi)
02-21 14:16:36 I/ThemeHostTest: Wrote 1 failures to file:C:\Users\10102660\AppData\Local\Temp\failures7813412060236123027.zip
02-21 14:16:37 D/ModuleListener: ModuleListener.testFailed(android.theme.cts.ThemeHostTest#testThemes, junit.framework.AssertionFailedError: 1 failures in theme test
        at junit.framework.Assert.fail(Assert.java:50)
        at junit.framework.Assert.assertTrue(Assert.java:20)
        at android.theme.cts.ThemeHostTest.testThemes(ThemeHostTest.java:218)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at junit.framework.TestCase.runTest(TestCase.java:168)
        at junit.framework.TestCase.runBare(TestCase.java:134)  

We believe that the failure lies in the holo_button_pressed.png within the
xxxhdpi.zip in CtsThemeHostTestCases.jar This png seems not right as it is totally same as the holo_button.png, which are not the case in any other dpi zip files in CtsThemeHostTestCases.jar.  

Google Pixel also fails this test after we change its density from 560 to 640 through the adb command "wm density 640". So we believe this test fails in the phone with density set as 640. We also refer this issue to Qcom (our cpu provider) for support, and they hold the same opinion.

I attached all the related log files to this report.
Thank you for your time.