I have an ICS tree that I've used to successfully build Android for the Motorola XOOM and the Samsung Galaxy Tab 1. I've recently been trying to prepare a build for the Acer A200 and haven't been able to get the device to boot. When I do some debugging through adb, I can see that none of the services are able to start up successfully, including servicemanager.
<5>[ 9.899505] init: process 'servicemanager', pid 105 exited <5>[ 9.899619] init: process 'servicemanager' killing any children in process group <5>[ 9.899839] init: service 'zygote' is being killed <5>[ 9.900051] init: starting 'zygote' <5>[ 9.900563] init: service 'media' is being killed <5>[ 9.900764] init: starting 'media' <5>[ 9.901155] init: service 'surfaceflinger' is being killed <5>[ 9.901462] init: starting 'surfaceflinger' <5>[ 9.901881] init: service 'drm' is being killed <5>[ 9.902089] init: starting 'drm' I've compared the kmsg logs with those I pulled from the same device running the stock factory build, and I don't see any notable differences. I've tried using both the kernel I extracted from the stock build, as well as a kernel I've built myself (which, FWIW, I'm able to repackage and successfully redeploy with the stock build, so I'm pretty sure this isn't the issue). At any rate, I'm at a loss to understand why these services are failing. The kernel has been compiled with ICP and I can't see any logcat output to get further information. Does anybody have any advice on how I can further troubleshoot this? I'm pretty sure that the trouble lies somewhere with in the init process, because I've tried doing something simple like creating a file at /proc/ in the initialization method of the servicemanager, but nothing ever gets created. Any help would be really appreciated. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
