AnsweredAssumed Answered

device suspend automatically after booting

Question asked by bikash bag on May 7, 2015
Latest reply on Jul 9, 2015 by SergioSolis

Hi,

 

we are using android lollypop in imx6q processor. The device is going to suspend mode imediately the android shell comes, The log is as follow:

 

 

1>init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'

<11>init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery'

<11>healthd: No charger supplies found

<14>healthd: No battery devices found

<6>warning: `main' uses 32-bit capabilities (legacy support in use)

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

<6>request_suspend_state: wakeup (3->0) at 11640884667 (2014-11-06 13:01:09.354261334 UTC)

<6>lowmemorykiller: lowmem_shrink: convert oom_adj to oom_score_adj:

<6>lowmemorykiller: oom_adj 0 => oom_score_adj 0

<6>lowmemorykiller: oom_adj 1 => oom_score_adj 58

<6>lowmemorykiller: oom_adj 2 => oom_score_adj 117

<6>lowmemorykiller: oom_adj 3 => oom_score_adj 176

<6>lowmemorykiller: oom_adj 9 => oom_score_adj 529

<6>lowmemorykiller: oom_adj 15 => oom_score_adj 1000

<3>ERROR: v4l2 capture: slave not found!

<3>ERROR: v4l2 capture: slave not found!

root@sabresd_6dq:/ # request_suspend_state: sleep (0->3) at 52899520339 (2014-11-06 13:01:50.612897339 UTC)

active wake lock PowerManagerService.Display

PM: suspend entry 2014-11-06 13:01:50.625343672 UTC

Freezing user space processes ... (elapsed 0.023 seconds) done.

Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

sd 0:0:0:0: [sda] Synchronizing SCSI cache

sd 0:0:0:0: [sda] Stopping disk

PM: suspend of devices complete after 44.298 msecs

PM: suspend devices took 0.050 seconds

PM: late suspend of devices complete after 0.360 msecs

PM: noirq suspend of devices complete after 0.512 msecs

Disabling non-boot CPUs ...

CPU1: shutdown

CPU2: shutdown

CPU3: shutdown

Outcomes