AnsweredAssumed Answered

Crash of android on imx6 board when playing with GUI.

Question asked by oussama on Jan 20, 2015
Latest reply on Mar 4, 2015 by oussama

Whenever I play with android GUI, no video, just navigate through settings, the android crash/hang after few seconds.

I'm using android kitkat  with kernel based on the fsl kernel 3.10.17 with custom board similar to the sabresd one.

 

Here's some info/error from logcat about SurfaceFlinger:

 

I/SurfaceFlinger(  144): renderer  : Vivante GC2000

I/SurfaceFlinger(  144): version   : OpenGL ES 2.0

I/SurfaceFlinger(  144): extensions: GL_EXT_debug_marker GL_OES_compressed_ETC1_RGB8_texture GL_OES_compressed_paletted_texture GL_OES_EGL_image GL_OES_depth24 GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_rgb8_rgba8 GL_OES_stencil1 GL_OES_stencil4 GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_depth_texture GL_OES_packed_depth_stencil GL_OES_standard_derivatives GL_OES_get_program_binary GL_EXT_texture_format_BGRA8888 GL_IMG_read_format GL_EXT_blend_minmax GL_EXT_read_format_bgra GL_EXT_multi_draw_arrays GL_APPLE_texture_format_BGRA8888 GL_APPLE_texture_max_level GL_ARM_rgba8 GL_EXT_frag_depth GL_VIV_shader_binary GL_VIV_direct_texture GL_OES_mapbuffer GL_OES_EGL_image_external GL_EXT_discard_framebuffer GL_EXT_multisampled_render_to_texture GL_VIV_clamp_to_border GL_OES_vertex_type_10_10_10_2 GL_EXT_texture_type_2_10_10_10_REV GL_EXT_texture_filter_anisotropic GL_OES_element_index_uint

I/SurfaceFlinger(  144): GL_MAX_TEXTURE_SIZE = 8192

I/SurfaceFlinger(  144): GL_MAX_VIEWPORT_DIMS = 8192

E/cutils-trace(  144): Error opening trace file: Permission denied (13)

E/SurfaceFlinger(  144): HWComposer: framebufferTarget is null

E/SurfaceFlinger(  144): HWComposer: framebufferTarget is null

E/SurfaceFlinger(  144): HWComposer: framebufferTarget is null

E/SurfaceFlinger(  144): HWComposer: framebufferTarget is null

I/iptables(  142): iptables terminated by exit(3)

E/Netd    (  142): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j fw_INPUT

D/SurfaceFlinger(  144): Screen acquired, type=0 flinger=0x78318450

I/ip6tables(  142): ip6tables terminated by exit(3)

E/Netd    (  142): exec() res=0, status=768 for /system/bin/ip6tables -t filter -A INPUT -j fw_INPUT

W/SurfaceFlinger(  144): Ignoring duplicate VSYNC event from HWC (t=0)

W/SurfaceFlinger(  144): Ignoring duplicate VSYNC event from HWC (t=0)

 

And there is more than 14000 occurance of the last message!

 

What's is the cause of those 14000 message of "Ignoring duplicate VSYNC event from HWC (t=0)"?

Is there some way to check if the android graphic stack can function properly?

 

Sometimes there some messages like this

[  325.901798] binder: 143:805 transaction failed 29189, size 164-

Outcomes