iMX6q Display problem(unexpected blue dot or area will display on UI)

[yixuan_guo]

Hi communities

we have a display problem when we run application on iMx6 board with android 4.4.2_1.0.0.

when we run our android application on the device, sometimes, the unexpected blue dot or area will display on UI.

you can see this phenomenon through the attachment pictures.

Replace with new lcd ,The problems still exist.

We doubt that there may be bugs in Android 4.4 display driver.

Someone else encountered this problem? and how to solve it ?

or can Freescale provide display driver patch to solve this problem?

thanks in advance.

[igorpadykov]

Hi yasin

problem nay be caused by lcd signals quality, as on link below

LCD colors look wrong. Android 4.3 with18-bit Parallel RGB on IMX6S.

One can try to decrease lcd clock (or framerate). Also recommended to check

if splashscreen is used in Uboot and disable it. Memory corruption also may be the reason,

so it may be recommended to recheck memory

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

Best regards

igor

[simon_cai]

HI igorpadykov

thanks for your kindly relay.

as yixuan.guo describes, we meet some unexpected noise point on display panel.

our testing display devices include TTL lcd panel, LVDS panel and even on VGA panel (TTL to VGA).

The unexpected noise points appear on display UI， but sometimes these noise points were gone and disappeared.(OS: FSL android 4.4.2)

BTW, everything display well if we running the FSL android 4.2.2 OS, but FSL android 4.4.2 didnot.  (with the same HW board)

so,

i think it is not the problems of TTL lcd signals quality.

AND, our HW board and our application can keep stable running over 1 week  with FSL android 4.4.2.

it is  maybe not the problems of DDR stability.

would you help give some other advices?

thanks for your support!

BM

[igorpadykov]

also please check, this also may be cause of such behaviour

https://community.freescale.com/message/320311#320311

~igor

[yixuan_guo]

Hi Igor

igorpadykov 撰写:

also please check, this also may be cause of such behaviour

https://community.freescale.com/message/320311#320311

~igor

According to your suggestion，We disable android swap rectangle feature

+++ frameworks/native/opengl/include/EGL/eglext.h       (working copy)

@@ -581,7 +581,8 @@

/* EGL_ANDROID_swap_rectangle

  */

#ifndef EGL_ANDROID_swap_rectangle

-#define EGL_ANDROID_swap_rectangle 1

+//#define EGL_ANDROID_swap_rectangle 1

+#define EGL_ANDROID_swap_rectangle 0

#ifdef EGL_EGLEXT_PROTOTYPES

EGLAPI EGLBoolean EGLAPIENTRY eglSetSwapRectangleANDROID (EGLDisplay dpy, EGLSurface draw, EGLint left, EGLint top, EGLint width, EGLint height);

#endif /* EGL_EGLEXT_PROTOTYPES */

And after the test,yet the problem persists.

[igorpadykov]

Hi yasin

can this be reproduced with Sabre LCD : HannStar

with Demo (unchanged Freescale images) ?

IMX6_SABRE_AI_KK442_100_ANDROID_DEMO_BSP :

~igor

[huangbaokang]

is it related to GPU ?? I have the same problem in android4.4.2,, but  android4.2.2  is OK .  IS there any path  about  GPU in android 4.4.2???

[igorpadykov]

you can try to disable it and check.

[huangbaokang]

hi igorpadykov , I have try at the machine "i.MX 6 Series SABRE for Smart Devices" , buy from freescale .  Only if I restart the machne and start my APK  several times , the bug arise ..   the linking below is the picture when bug arise ,and the apk I use for test .

picture:

http://pan.baidu.com/s/1mgkiriC

! !
APK :

http://pan.baidu.com/s/1eQisAnK

[igorpadykov]

Hi yasin

please try to make big pauses between board restarting -

so all power supplies will be fully discharged before board power-up.

~igor

[huangbaokang]

igorpadykov 撰写:

Hi yasin

please try to make big pauses between board restarting -

so all power supplies will be fully discharged before board power-up.

~igor

Hi igorpadykov:

    it seems doesn't related to what you say above.

1、the "blue dot" arise randomly , ones it arise , it alway be there .but if it dosn't arise in 2 or 3 minute after the machine start, it will not be arise anymore.

2、at one time the "blue dot" arese , I resrart the "android system service" , it means that the machine will resrart form "Dynamic logo"  ,  when the machine startup , "blue dot"  doesn't arise.

3、the "blue dot" is so small that it can't be seen at 1080p  resolution . so the resolution must be under 720p ,so as to see the "blue dot" ,,The lower resolution , more obvious to see the "blue dot".

so  I  suppose that if it is some problem at  Android  initialization , but I can't find where the problem is . so please git some help.thanks..

[igorpadykov]

Hi yasin

I think such behaviour just confirms suggestion that

memory is not working properly on your board.

2 or 3 minute pauses on Sabre board also removes this effect,

since smaller pause does not provide chance for correct memory initialization .

~igor

[huangbaokang]

igorpadykov 撰写:

Hi yasin

I think such behaviour just confirms suggestion that

memory is not working properly on your board.

2 or 3 minute pauses on Sabre board also removes this effect,

since smaller pause does not provide chance for correct memory initialization .

~igor

Hi igorpadykov:

     Android4.4.2 has the problem , but at Android4.2.2  is OK  , so i think it is softwar problem.

[igorpadykov]

please try to reproduce this on Freescale reference board

with big pauses between restarts.

Best regards

igor

[huangbaokang]

Hi igorpadykov:

    I reprodeced it on Freescale reference board  "i.MX 6 Series SABRE for Smart Devices" , software was downed from freescale, named  "android_kk4.4.2_1.0.0-ga_core_image_6qsabresd".

   I pauses the machine about 2 minute between restarts.  when the machine start , I restart the apk  several times ,the bug arise.

[igorpadykov]

Hi bateman

tobe sure that this is not HW problem one

can run NG image on Freescale reference board.

Best regards

igor

[simon_cai]

Hi igor

thanks,

yes,it is the same HW board.

I am sure with the same HW boards ,running FSL Android 4.2.2 is good, running FSL android 4.4.2 is NG (unexpected noise).

[igorpadykov]

Hi bateman

to be sure that this is not HW problem, try reproduce this

on Freescale reference board.

Best regards

igor