Hi,
I was trying to debug the boot loop issue on my target running ICS. I tried
to narrow down using a minimal set of init.rc commands
to try to get to the adb shell and launch other services.
However I am stuck because of crash in adbd itself. See here:
[ 4.640000] init: processing action 0x2ee70
(property:sys.usb.config=mass_storage)
[ 4.650000] android_usb: already disabled
[ 4.650000] init: command 'write' r=0
[ 4.660000] init: command 'write' r=0
[ 4.660000] init: command 'write' r=0
[ 4.670000] init: command 'write' r=0
[ 4.670000] ep_matches, wrn: endpoint already claimed, ep(0xc07a8210,
0xd9a0a800, ep1-bulk)
[ 4.680000] [sw_udc]: sw_udc_pullup, is_on = 1
[ 4.690000] init: command 'write' r=0
[ 4.700000] init: starting 'adbd'
[ 4.700000] init: command 'start' r=0
[ 4.710000] init: command 'setprop' r=0
[ 4.720000] binder: 66 RLIMIT_NICE not set
[ 4.730000] init: waitpid returned pid 68, status = 00000100
[ 4.730000] init: process 'adbd', pid 68 exited
[ 4.740000] init: process 'adbd' killing any children in process group
[ 9.750000] init: starting 'adbd'
[ 9.760000] init: waitpid returned pid 69, status = 00000100
[ 9.770000] init: process 'adbd', pid 69 exited
[ 9.770000] init: process 'adbd' killing any children in process group
[ 14.780000] init: starting 'adbd'
I wonder if adbd has some requirements to start with?
My init.rc has config like:
service console /system/bin/sh /dev/ttyS0
class core
console
on property:ro.debuggable=1
start console
# adbd is controlled via property triggers in init.<platform>.usb.rc
service adbd /sbin/adbd
class core
disabled
Any ideas on how to get the adbd to run without crashing? Do I need to
modify adbd?
Is it possible to access shell on serial console? (ttyS0)
Thanks for your help.
-N
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
