AnsweredAssumed Answered

android lollypop goes into deep sleep after boot

Question asked by bikash bag on May 10, 2015
Latest reply on May 14, 2015 by bikash bag

Hi,

 

I am facing an issue in porting android lollypop(release: L5.0.0_1.0.0-alpha )on our custom board based on imx6q processor.

After successfully bootup, it seems the system goes into deep sleep mode(or poweroff not sure.).

 

 

Please see the log as below:

===================================

Freeing unused kernel memory: 344K (80e4e000 - 80ea4000)

init: /dev/hw_random not found

Console: switching to colour dummy device 80x30

init: /dev/hw_random not found

EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)

fs_mgr: __mount(source=/dev/block/sda5,target=/system,type=ext4)=0

EXT4-fs (sda4): Ignoring removed nomblk_io_submit option

EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended

EXT4-fs (sda4): recovery complete

EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic

fs_mgr: __mount(source=/dev/block/sda4,target=/data,type=ext4)=0

EXT4-fs (sda6): Ignoring removed nomblk_io_submit option

EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit

fs_mgr: __mount(source=/dev/block/sda6,target=/cache,type=ext4)=0

EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)

fs_mgr: __mount(source=/dev/block/sda7,target=/device,type=ext4)=0

FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

fs_mgr: __mount(source=/dev/block/sda1,target=/boot,type=vfat)=0

FAT-fs (sda2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

fs_mgr: __mount(source=/dev/block/sda2,target=/recovery,type=vfat)=0

rfkill: BT RF going to : off

binder: 121:121 transaction failed 29189, size 0-0

init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead

init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno'

init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial'

init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead

init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead

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

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

root@sabresd_6dq:/ # healthd: No charger supplies found

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

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

request_suspend_state: wakeup (3->0) at 12929386667 (2014-11-13 00:22:26.330551667 UTC)

lowmemorykiller: lowmem_shrink: convert oom_adj to oom_score_adj:

lowmemorykiller: oom_adj 0 => oom_score_adj 0

lowmemorykiller: oom_adj 1 => oom_score_adj 58

lowmemorykiller: oom_adj 2 => oom_score_adj 117

lowmemorykiller: oom_adj 3 => oom_score_adj 176

lowmemorykiller: oom_adj 9 => oom_score_adj 529

lowmemorykiller: oom_adj 15 => oom_score_adj 1000

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

request_suspend_state: sleep (0->3) at 49251130338 (2014-11-13 00:23:02.652295338 UTC)

active wake lock PowerManagerService.Display

PM: suspend entry 2014-11-13 00:23:02.664781672 UTC

Freezing user space processes ... (elapsed 0.091 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.126 msecs

PM: suspend devices took 0.050 seconds

PM: late suspend of devices complete after 0.376 msecs

PM: noirq suspend of devices complete after 0.521 msecs

Disabling non-boot CPUs ...

CPU1: shutdown

CPU2: shutdown

CPU3: shutdown

 

 

 

 

When I am using busybox filesystem with the same kernel image, i am not seeing such issue. So it seems android is forcing the system to sleep.

 

Please help me in this issue

Outcomes