Hello All ,
I am working on IMX6 Solo light EVK Borad , whener I add new system service to the android framework (Android Lollipop 5.0.1) following error is coming and android is not booting.
Log Message:
....
....
ALSA device list:
#0: wm8962-audio
#1: imx-spdif
Freeing unused kernel memory: 340K (80e7b000 - 80ed0000)
type=1403 audit(1.640:2): policy loaded auid=4294967295 ses=4294967295
type=1404 audit(1.650:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
init: /dev/hw_random not found
Console: switching to colour dummy device 80x30
init: /dev/hw_random not found
EXT4-fs (mmcblk1p5): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/mmcblk1p5,target=/system,type=ext4)=0
EXT4-fs (mmcblk1p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk1p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
fs_mgr: __mount(source=/dev/block/mmcblk1p4,target=/data,type=ext4)=0
EXT4-fs (mmcblk1p6): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk1p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
fs_mgr: __mount(source=/dev/block/mmcblk1p6,target=/cache,type=ext4)=0
EXT4-fs (mmcblk1p7): mounted filesystem with ordered data mode. Opts: (null)
fs_mgr: __mount(source=/dev/block/mmcblk1p7,target=/device,type=ext4)=0
binder:
err_no_context_mgr_node
binder: 116:116 transaction faileddd 29189, size 0-0
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
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'
android_usb: already disabled
read descriptors
read strings
mtp_bind_config
android_work: sent uevent USB_STATE=CONNECTED
android_work: sent uevent USB_STATE=DISCONNECTED
android_usb gadget: high-speed config #1: android
android_work: sent uevent USB_STATE=CONFIGURED
healthd: BatteryTemperaturePath not found
healthd: BatteryTechnologyPath not found
csi_v4l_open: Internal error, camera is not found!
csi_v4l_open: Internal error, camera is not found!
warning: `main' uses 32-bit capabilities (legacy support in use)
request_suspend_state: wakeup (3->0) at 47887247671 (1970-01-01 00:00:46.238294463 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
binder: undelivered transaction 17836
alarm_release: clear alarm, pending 0
binder: 120:213 transaction faileddd 29189, size 68-0
request_suspend_state: wakeup (0->0) at 200971899606 (1970-01-01 00:03:19.322946606 UTC)
csi_v4l_open: Internal error, camera is not found!
csi_v4l_open: Internal error, camera is not found!
request_suspend_state: wakeup (0->0) at 218105294358 (1970-01-01 00:03:36.456341233 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
binder: 120:214 transaction faileddd 29189, size 68-0
alarm_release: clear alarm, pending 0
request_suspend_state: wakeup (0->0) at 229731951735 (1970-01-01 00:03:48.082998610 UTC)
csi_v4l_open: Internal error, camera is not found!
csi_v4l_open: Internal error, camera is not found!
request_suspend_state: wakeup (0->0) at 246836643778 (1970-01-01 00:04:05.187690695 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
binder: undelivered transaction 24411
alarm_release: clear alarm, pending 0
binder: 120:214 transaction faileddd 29189, size 68-0
request_suspend_state: wakeup (0->0) at 258011735363 (1970-01-01 00:04:16.362781905 UTC)
csi_v4l_open: Internal error, camera is not found!
csi_v4l_open: Internal error, camera is not found!
request_suspend_state: wakeup (0->0) at 275193878365 (1970-01-01 00:04:33.544925199 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
alarm_release: clear alarm, pending 0
binder: 120:214 transaction faileddd 29189, size 68-0
request_suspend_state: wakeup (0->0) at 286352135241 (1970-01-01 00:04:44.703182033 UTC)
csi_v4l_open: Internal error, camera is not found!
csi_v4l_open: Internal error, camera is not found!
Please help me sort out this issue...
Regards,
Kishore P
已解决! 转到解答。
Hi Kishore,
It means your SystemServer is crashing during its initialization, most likely due to your custom system service.
Please check your logcat, it will hopefully give you more information.
Regards,
Gary
Hi Kishore,
It means your SystemServer is crashing during its initialization, most likely due to your custom system service.
Please check your logcat, it will hopefully give you more information.
Regards,
Gary
You did not include more details on which service you're adding but I would suggest maybe looking at the Android Developer Forums on the specifics of the kind of service you're adding. You're also welcome to add it here so other community users may contribute.
Hello Gary,
I followed the following Blog to add new custom System Service to the AOSP (Lollipop 5.0.2).
shridutt kothari's blog: Adding New System Service in Android
Android-Adding SystemService - Texas Instruments Wiki
After adding new System Service , we have to add the Service to /external/sepolicy/service_contexts to avoid SELinux policy denies
refer the below post
Regards,
Kishore P