In a CTS test of AndroidKK4 .4.3, there is the next item.
android.app.cts.ProgressDialogTest - testSetMessage
Fail is frequent if DPI=320 is set.
Would you teach a cause and the workaround for this Fail?
can you please attach the logcat information files again? (sorry about that)...
Attach the log file.
Could you check it ?
We work with Sugiyama-san.Please refer to the log file which he attached.
Have you tried with the following patch and see the results?
This issue occurs on KK4.4.3.
The specified patch is for KK4.4.2.
Is it possible to apply the specified patch for KK4.4.3 ?
Thank you for your support.
We use KK4.4.3.However, the URL that you said explains KK4.4.2.We understand that GPU library of KK4.4.3 is different from KK4.4.2.
Is this patch effective for KK4.4.3?
One of our engineers tried the same configuration and passed the CTS:
My test result showed below,
04-09 16:17:19 I/TestInvocation: Starting invocation for 'cts' on build '4.4_r3' on device 0123456789ABCDEF
04-09 16:17:19 I/0123456789ABCDEF: Created result dir 2015.04.09_16.17.19
04-09 16:17:30 I/0123456789ABCDEF: Collecting device info
04-09 16:17:31 I/0123456789ABCDEF: -----------------------------------------
04-09 16:17:31 I/0123456789ABCDEF: Test package android.app started
04-09 16:17:39 I/0123456789ABCDEF: android.app.cts.ProgressDialogTest#testSetMessage PASS
04-09 16:17:41 I/0123456789ABCDEF: Saved log device_logcat_7077452758048040122.zip
04-09 16:17:41 I/0123456789ABCDEF: Saved log host_log_6676776121100094177.zip
04-09 16:17:41 I/0123456789ABCDEF: android.app package complete: Passed 1, Failed 0, Not Executed 0
04-09 16:17:41 I/0123456789ABCDEF: Created xml report file at file:///work/jay/kk/out/host/linux-x86/cts/android-cts/repository/results/2015.04.09_16.17.19/testResult.xml
04-09 16:17:41 I/0123456789ABCDEF: XML test result file generated at 2015.04.09_16.17.19. Passed 1, Failed 0, Not Executed 0
04-09 16:17:41 I/0123456789ABCDEF: Time: 0s
What do you mean about the following?
Could you try to set ro.sf.lcd_density to 320 ?
When the following test was run under conditions of DPI=320, failure occurs.
For fail Content, please refer to attached Log file by Sugiyama-san.
We want to know the cause that this failure occurs.
And we want to know the method to evade this problem.
Change the following value in init.rc to "320". ===========================================================
# Set the density to 160dpi, default 128dpi is not good
setprop ro.sf.lcd_density 320
Retrieving data ...