About a CTS ProgressDialogTest of AndroidKK4.4.3 for i.MX6Quad

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

About a CTS ProgressDialogTest of AndroidKK4.4.3 for i.MX6Quad

1,514 Views
yuuki
Senior Contributor II

Dear all,

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?

Best Regards,
Yuuki

Labels (1)
Tags (4)
0 Kudos
10 Replies

1,124 Views
SergioSolis
NXP Employee
NXP Employee

Hello Yuuki,

can you please attach the logcat information files again? (sorry about that)...

0 Kudos

1,124 Views
yuuki
Senior Contributor II

Dear Sergio-san,

We work with Sugiyama-san.
Please refer to the log file which he attached.

Best Regards,
Yuuki

0 Kudos

1,124 Views
SergioSolis
NXP Employee
NXP Employee

Hello Yuuki,

Have you tried with the following patch and see the results?

https://community.freescale.com/docs/DOC-104222

0 Kudos

1,124 Views
yuuki
Senior Contributor II

Dear Sergio-san,

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?

Best Regards,
Yuuki

0 Kudos

1,124 Views
SergioSolis
NXP Employee
NXP Employee

Hello Yuuki,

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:31 I/0123456789ABCDEF: -----------------------------------------

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?

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.

0 Kudos

1,124 Views
yuuki
Senior Contributor II

Dear Dergio-san,

===========================================

What do you mean about the following?

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.

===========================================

When the following test was run under conditions of DPI=320,  failure occurs.

android.app.cts.ProgressDialogTest
  - testSetMessage

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.

Best Regards,

Yuuki

0 Kudos

1,124 Views
yuuki
Senior Contributor II

Dear Dergio-san,

    
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

===========================================================

Best Regards,

Yuuki

0 Kudos

1,124 Views
norimitsusugiya
Contributor I

Dear Sergio-san,

Could you try to set ro.sf.lcd_density to 320 ?

Best Regards

0 Kudos

1,124 Views
norimitsusugiya
Contributor I

Dear Sergio-san,


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 ?


Best Regards

0 Kudos

1,124 Views
norimitsusugiya
Contributor I

Attach the log file.

Could you check it ?

0 Kudos