IMX8MQ EVK Android services starting-dying loop

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMX8MQ EVK Android services starting-dying loop

Jump to solution
1,806 Views
akhila_karonnon
Contributor I

evk_8mq:/ $ [ 5.195810] healthd: unable to get HAL interface, using defaults
[ 5.203621] healthd: No battery devices found
[ 5.211083] healthd: battery l=100 v=0 t=42.4 h=2 st=2 chg=a
[ 9.540083] init: Service 'surfaceflinger' (pid 2893) killed by signal 1
[ 9.546978] init: Sending signal 9 to service 'surfaceflinger' (pid 2893) process group...
[ 9.555854] init: Successfully killed process cgroup uid 1000 pid 2893 in 0ms
[ 9.565272] init: starting service 'zygote'...
[ 9.583667] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 9.951866] init: starting service 'surfaceflinger'...
[ 9.960265] init: property_set("ro.boottime.surfaceflinger", "9955361828") failed: property already set
[ 9.960454] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory
[ 9.960765] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[ 9.961054] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory
[ 14.579519] init: starting service 'zygote'...
[ 14.593983] init: property_set("ro.boottime.zygote", "14587585695") failed: property already set
[ 14.594202] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 14.960882] init: starting service 'surfaceflinger'...
[ 14.977952] init: property_set("ro.boottime.surfaceflinger", "14971023630") failed: property already set
[ 14.978635] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory
[ 14.979107] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[ 14.979386] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory
[ 15.238707] init: Untracked pid 3311 exited with status 0
[ 15.247960] init: Service 'zygote' (pid 3269) killed by signal 6
[ 19.592886] init: starting service 'zygote'...
[ 19.607620] init: property_set("ro.boottime.zygote", "19601513736") failed: property already set
[ 19.607902] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 19.976507] init: starting service 'surfaceflinger'...
[ 19.991791] init: property_set("ro.boottime.surfaceflinger", "19985667112") failed: property already set
[ 19.992203] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[ 19.992542] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory
[ 20.283875] init: Untracked pid 3525 exited with status 0
[ 20.291468] init: Service 'zygote' (pid 3483) killed by signal 6
[ 20.297746] init: Sending signal 9 to service 'zygote' (pid 3483) process group...

i was facing this problem while booting and HDMI display is stopping .  where i can search root of this problem??

please check the attached logs.

Am giving the following  bootargs for HDMI 

                setenv bootargs console=ttymxc0,115200 earlycon=imxuart,0x30860000,115200 init=/init video=HDMI-A-1:1920x1080-32@60 androidboot.zygote=zygote64_32
androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=800M
androidboot.selinux=permissive
saveenv

0 Kudos
1 Solution
1,403 Views
diegoadrian
NXP Employee
NXP Employee

Hello,

Are you using a custom board or is one of our EVK boards?

This is because there is no need to change the bootargs. The default bootargs, should work for the HDMI displays.

Best regards,

Diego.

View solution in original post

0 Kudos
3 Replies
1,404 Views
diegoadrian
NXP Employee
NXP Employee

Hello,

Are you using a custom board or is one of our EVK boards?

This is because there is no need to change the bootargs. The default bootargs, should work for the HDMI displays.

Best regards,

Diego.

0 Kudos
1,403 Views
akhila_karonnon
Contributor I

Yes am using NXP EVK board.

Thanks.it works for me.

0 Kudos
1,290 Views
vinays
Contributor II

I am facing the same issue, Surfaceflingers are getting crashed continuously. 

could you help us rectify this problem?

 

regards

Parvathi

 

0 Kudos