SurfaceFlinger Error When Booting AOSP


#1

Hello,

I am trying to setup AOSP 7.1.2 on a Hikey 620 board (I have a ongoing project so need 7.1.2). I followed the instructions mentioned on this page: https://source.android.com/setup/devices .

I compiled the userspace, kernel, made the bootimage, and then recompiled android again. I tried flashing with pins 1-2 and 3-4 closed. I also tried (in a separate instance) to also use the 1-2 and 5-6 step mentioned in the link above.

I am getting the following error when I try to boot the board:

01-01 00:00:21.645 1964 1964 E SurfaceFlinger: hwcomposer module not found
01-01 00:00:21.645 1964 1964 W SurfaceFlinger: no suitable EGLConfig found, trying a simpler query
01-01 00:00:21.646 1964 1964 F SurfaceFlinger: no suitable EGLConfig found, giving up
01-01 00:00:21.646 1964 1964 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1964 (surfaceflinger)
01-01 00:00:21.646 1737 1737 W : debuggerd: handling request: pid=1964 uid=1000 gid=1003 tid=1964
01-01 00:00:21.653 1979 1979 E : debuggerd: Unable to connect to activity manager (connect failed: No such file or directory)
01-01 00:00:21.654 1979 1979 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 00:00:21.654 1979 1979 F DEBUG : Build fingerprint: 'generic/hikey/hikey:7.1.2/N2G48H/02151024:userdebug/test-keys’
01-01 00:00:21.654 1979 1979 F DEBUG : Revision: '0’
01-01 00:00:21.654 1979 1979 F DEBUG : ABI: 'arm64’
01-01 00:00:21.655 1979 1979 F DEBUG : pid: 1964, tid: 1964, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
01-01 00:00:21.655 1979 1979 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-01 00:00:21.658 1979 1979 F DEBUG : Abort message: 'no suitable EGLConfig found, giving up’
01-01 00:00:21.658 1979 1979 F DEBUG : x0 0000000000000000 x1 00000000000007ac x2 0000000000000006 x3 0000000000000008
01-01 00:00:21.658 1979 1979 F DEBUG : x4 6579614c74656700 x5 0000000000000000 x6 0000007fb7f4a000 x7 0000000000000000
01-01 00:00:21.658 1979 1979 F DEBUG : x8 0000000000000083 x9 ffffffffffffffdf x10 0000000000000000 x11 0000000000000001
01-01 00:00:21.658 1979 1979 F DEBUG : x12 ffffffffffffffff x13 0000000000000000 x14 0000000000000000 x15 0009a08115b5ddca
01-01 00:00:21.659 1979 1979 F DEBUG : x16 0000007fb7b19ee0 x17 0000007fb7ac32e4 x18 00000000ffffffff x19 0000007fb7ffeb40
01-01 00:00:21.659 1979 1979 F DEBUG : x20 0000000000000006 x21 0000007fb7ffea98 x22 0000000000000000 x23 0000000000000001
01-01 00:00:21.659 1979 1979 F DEBUG : x24 0000000000000001 x25 0000007fb7d323a8 x26 0000007fb7d32360 x27 be00bad7c7c1b58d
01-01 00:00:21.659 1979 1979 F DEBUG : x28 0000000000000000 x29 0000007ffffff260 x30 0000007fb7ac078c
01-01 00:00:21.659 1979 1979 F DEBUG : sp 0000007ffffff240 pc 0000007fb7ac32ec pstate 0000000060000000
01-01 00:00:21.666 1979 1979 F DEBUG :
01-01 00:00:21.666 1979 1979 F DEBUG : backtrace:
01-01 00:00:21.667 1979 1979 F DEBUG : #00 pc 000000000006b2ec /system/lib64/libc.so (tgkill+8)
01-01 00:00:21.667 1979 1979 F DEBUG : #01 pc 0000000000068788 /system/lib64/libc.so (pthread_kill+64)
01-01 00:00:21.667 1979 1979 F DEBUG : #02 pc 0000000000023ce8 /system/lib64/libc.so (raise+24)
01-01 00:00:21.667 1979 1979 F DEBUG : #03 pc 000000000001c76c /system/lib64/libc.so (abort+52)
01-01 00:00:21.667 1979 1979 F DEBUG : #04 pc 0000000000010ad8 /system/lib64/libcutils.so (__android_log_assert+232)
01-01 00:00:21.667 1979 1979 F DEBUG : #05 pc 000000000003ba70 /system/lib64/libsurfaceflinger.so
01-01 00:00:21.667 1979 1979 F DEBUG : #06 pc 000000000003b4c8 /system/lib64/libsurfaceflinger.so
01-01 00:00:21.667 1979 1979 F DEBUG : #07 pc 0000000000040484 /system/lib64/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+808)
01-01 00:00:21.667 1979 1979 F DEBUG : #08 pc 0000000000001350 /system/bin/surfaceflinger
01-01 00:00:21.667 1979 1979 F DEBUG : #09 pc 000000000001a594 /system/lib64/libc.so (__libc_init+88)
01-01 00:00:21.667 1979 1979 F DEBUG : #10 pc 00000000000011ec /system/bin/surfaceflinger

I wanted to ask if there is any way to resolve this. Is this because the branch I’m trying to setup is older than the master branch ?

Thanks


#2

Officially, only master branch is supported and Mali driver (binary blobs) you downloaded (step 2) are aligned with this master branch. Backward compatibility is not guaranteed.


#3

@Loic Okay thank you.