Android 4.4.2_1 boot failure

Discuss Android on the Wandboard, as well as app development for or on the Wandboard.

Android 4.4.2_1 boot failure

Postby rdbirt » Thu Feb 12, 2015 1:23 am

Hi All,

I have built 4.4.2_1 from the source tarball on wandboard.org. Android starts to come up but gets stuck trying to bring up the display. Please see below for the end of one of the tombstone files.

Anyone know how to fix this?

Regards,
Ralph

01-01 00:50:58.030 22216 22216 E SurfaceFlinger: hwcomposer module not found
01-01 00:50:58.030 22216 22216 W SurfaceFlinger: getting VSYNC period from fb HAL: 16154305
01-01 00:50:58.040 22216 22216 W SurfaceFlinger: no suitable EGLConfig found, trying a simpler query
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: EGL informations:
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: vendor : Android
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: version : 1.4 Android META-EGL
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer EGL_ANDROID_recordable
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: Client API: OpenGL_ES
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: EGLSurface: 8-8-8-0, config=0x2bb70688
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: OpenGL ES informations:
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: vendor : Vivante Corporation
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: renderer : Vivante GC2000
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: version : OpenGL ES 2.0
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: 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_01-01 00:50:58.040 22216 22216 I SurfaceFlinger: GL_MAX_TEXTURE_SIZE = 8192
01-01 00:50:58.040 22216 22216 I SurfaceFlinger: GL_MAX_VIEWPORT_DIMS = 8192
01-01 00:50:58.040 22216 22216 E cutils-trace: Error opening trace file: No such file or directory (2)
01-01 00:50:58.110 22216 22216 W GraphicBufferAllocator: alloc(1280, 720, 2, 00001b00, ...) failed -12 (Out of memory)
01-01 00:50:58.110 22216 22216 D GraphicBufferAllocator: Allocated buffers:
0x2ac50c60: 3600.00 KiB | 1280 (1280) x 720 | 2 | 0x00001b00
0x2ac50db0: 3600.00 KiB | 1280 (1280) x 720 | 2 | 0x00001b00
Total allocated (estimate): 7200.00 KB
01-01 00:50:58.110 22216 22216 E : GraphicBufferAlloc::createGraphicBuffer(w=1280, h=720) failed (Out of memory), handle=0x0
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] queueBuffer: slot 1 is not owned by the client (state=3)
01-01 00:50:58.110 22216 22216 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -22
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] queueBuffer: slot 1 is not owned by the client (state=3)
01-01 00:50:58.110 22216 22216 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -22
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] queueBuffer: slot 1 is not owned by the client (state=3)
01-01 00:50:58.110 22216 22216 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -22
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] queueBuffer: slot 1 is not owned by the client (state=3)
01-01 00:50:58.110 22216 22216 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -22
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] queueBuffer: slot 1 is not owned by the client (state=3)
01-01 00:50:58.110 22216 22216 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -22
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
01-01 00:50:58.110 22216 22216 E BufferQueue: [FramebufferSurface] queueBuffer: slot 1 is not owned by the client (state=3)
01-01 00:50:58.110 22216 22216 E Surface : queueBuffer: error queuing buffer to SurfaceTexture, -22
01-01 00:50:58.120 22216 22216 D SurfaceFlinger: Screen acquired, type=0 flinger=0x2cb3b450
01-01 00:50:58.130 22216 22216 E BufferQueue: [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
01-01 00:50:58.130 22216 22216 F SurfaceFlinger: eglSwapBuffers(0x1, 0x2ac50de0) failed with 0x0000300b
01-01 00:50:58.130 22216 22216 F libc : Fatal signal 6 (SIGABRT) at 0x000056c8 (code=-6), thread 22216 (surfaceflinger)
rdbirt
 
Posts: 21
Joined: Wed Jan 07, 2015 5:36 pm

Re: Android 4.4.2_1 boot failure

Postby Richard » Mon Feb 16, 2015 3:10 am

Hello, Rdbirt:

For these information, it seems there are some permission issues on your /system partition.
Please refer to following steps to install android partition.

Code: Select all
Install Android into SD card:

$ sudo umount /dev/sdX
$ sudo dd if=/dev/zero of=/dev/sdX bs=1M count=1
$ sudo ./wand_fsl_sdcard-part.sh /dev/sdX
$ sudo dd if=wand-4.4.2_1/bootable/bootloader/uboot-imx/SPL of=/dev/sdX bs=1K seek=1
$ sudo mount -t vfat /dev/sdX1 /media/imx6
$ mkdir -p /media/imx6/boot
$ sudo cp wand-4.4.2_1/kernel_imx/arch/arm/boot/uImage /media/imx6/boot/
$ sudo cp wand-4.4.2_1/bootable/bootloader/uboot-imx/u-boot.img /media/imx6/boot/
$ sudo cp wand-4.4.2_1/bootable/bootloader/uboot-imx/wandboard.bmp.gz /media/imx6/boot/
$ sudo cp wand-4.4.2_1/bootable/bootloader/uboot-imx/uEnv.txt /media/imx6/boot/
$ sudo mkimage -A arm -O linux -T ramdisk -C none -a 0x10800800 -n "Android Root Filesystem" -d wand-4.4.2_1/out/target/product/wandboard/ramdisk.img /media/imx6/boot/uramdisk.img
$ sudo cp settings/uEnv_fairy_hdmi_720P.txt /media/imx6/boot/uEnv.txt
If your product is wandboard solo, please replace above command as:
   $ sudo cp settings/uEnv_wand_solo_hdmi_720P.txt /media/imx6/boot/uEnv.txt
$ sudo umount /dev/sdX
$ sudo dd if=./wand-4.4.2_1/out/target/product/wandboard/system.img of=/dev/sdX5 && sudo sync

The point is you need to install your system partition via "dd" command instead of "cp".
E.g.
use
Code: Select all
sudo dd if=./wand-4.4.2_1/out/target/product/wandboard/system.img of=/dev/sdX5 && sudo sync

instead of
Code: Select all
sudo mount -t ext4 /dev/sdX5 /media/system
sudo cp -ap ./wand-4.4.2_1/out/target/product/wandboard/system/* /media/system/


BTW, what kind of CPU module you use for android (i.mx6 Quad/DL/Solo)?

BR,

Richard
Richard
Site Admin
 
Posts: 138
Joined: Tue Dec 17, 2013 6:57 am

Re: Android 4.4.2_1 boot failure

Postby rdbirt » Wed Feb 18, 2015 3:12 am

Hi Richard,

'dd' did it! Thank you very much for the help. BTW, how did you know it was a permissions problem?

I'm using a quad board.

Regards,
Ralph
rdbirt
 
Posts: 21
Joined: Wed Jan 07, 2015 5:36 pm


Return to Software - Android

Who is online

Users browsing this forum: No registered users and 6 guests

cron