AM3505 Display problem in Android2.3.4

It looks like the resolution may not be configured correctly in the display driver.

How have you configured the LCD in the kernel?

Hi Vishveshwar,Thanks for your reply.
but the kernel logo and android first logo are correct if that is the display driver problem, and if i use SGX driver with same kernel in am3517, the display is ok.

my lcd configtion as belows:

static struct omap_video_timings kd035g7_timings = {

    .x_res = 480,
    .y_res = 272,

    .pixel_clock    = 9000,

    .hsw        = 36,
    .hfp        = 48,
    .hbp        = 50,

    .vsw        = 4,
    .vfp        = 30,
    .vbp        = 30,
};

loginfo:
I/SurfaceFlinger(  944): SurfaceFlinger is starting
I/SurfaceFlinger(  944): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/gralloc (  944): Framebuffer: upper_margin = 0,lower_margin = 0,              left_margin=0, right_margin = 0, pixclock = 0
I/gralloc (  944): using (fd=26)
I/gralloc (  944): id           = omapfb
I/gralloc (  944): xres         = 480 px
I/gralloc (  944): yres         = 272 px
I/gralloc (  944): xres_virtual = 480 px
I/gralloc (  944): yres_virtual = 544 px
I/gralloc (  944): bpp          = 32
I/gralloc (  944): r            = 16:8
I/gralloc (  944): g            =  8:8
I/gralloc (  944): b            =  0:8
I/gralloc (  944): width        = 76 mm (160.421051 dpi)
I/gralloc (  944): height       = 43 mm (160.669769 dpi)
I/gralloc (  944): refresh rate = 60.00 Hz
D/libEGL  (  944): egl.cfg not found, using default config
D/libEGL  (  944): loaded /system/lib/egl/libGLES_android.so
W/SurfaceFlinger(  944): ro.sf.lcd_density not defined, using 160 dpi by default.
I/SurfaceFlinger(  944): EGL informations:
I/SurfaceFlinger(  944): # of configs : 8
I/SurfaceFlinger(  944): vendor    : Android
I/SurfaceFlinger(  944): version   : 1.4 Android META-EGL
I/SurfaceFlinger(  944): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_ANDROID_image_native_buffer EGL_ANDROID_swap_rectangle
I/SurfaceFlinger(  944): Client API: OpenGL ES
I/SurfaceFlinger(  944): EGLSurface: 5-6-5-0, config=0x0
I/SurfaceFlinger(  944): OpenGL informations:
I/SurfaceFlinger(  944): vendor    : Android
I/SurfaceFlinger(  944): renderer  : Android PixelFlinger 1.4
I/SurfaceFlinger(  944): version   : OpenGL ES-CM 1.0
I/SurfaceFlinger(  944): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture
I/SurfaceFlinger(  944): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger(  944): GL_MAX_VIEWPORT_DIMS = 4096
I/SurfaceFlinger(  944): flags = 000c0000

I have sloved this problem,That's display driver problem!

Thanks very much!

Do post the cause of the issue and its solution here. This information can be useful to other users too.

Thanks

Because i configure LCD driver to 24bit(8-8-8) mode,it's ok when use SGX driver,but in non-SGX , it's will have problem.

Because i configure LCD driver to 24bit(8-8-8) mode,it's ok when use SGX driver,but in non-SGX , it's will have problem.

Thanks!

Dear All,

I would like to mention that the CPU is using AM3505 not 3517, Peter is using Mistral Crane board BSP which is for AM3517, we expected 3505 is same BSP no required to change anything but now the color still wrong.

B.R

Edwin

Following is the response from my co-worker with some experience in this...

1) That display shows that Android is configured for 16bpp though Framebuffer is configured for 32bpp. So they need to set FB format to HAL_PIXEL_FORMAT_RGBX_8888 or HAL_PIXEL_FORMAT_BGRA_8888 based on their FB configuration.

2) If the colors are inverted then ask them to verify that they are setting the correct color format in "hardware/libhardware/modules/gralloc/framebuffer.cpp:fb_device_open()"

Dear Sir,

The color display is correct now but once change the display to other page eg. Android top mune chage to sub mune, the LCD will flashing around 2 second, then will back to normal, but it is no problem on AM3517 platform.

BR

Edwin

Your device does not support SGX graphics acceleration, hence you are seeing the tearing effects.

You can try the solution mentioned below, however this has the side-effect of making the display "slow"

http://code.google.com/p/rowboat/issues/detail?id=91

Do let us know if this helps.