Hi, I am trying to use the system and data directory from the Android Source 1.0 by building it. But i am still getting the same errors...... Zygote process dies due to Segmentation Fault or may be due to SIGBUS error sometimes.
Can anybody give the solutions ??? Regards, Saroj K Pradhan On Feb 11, 11:53 pm, Rizvan S <[email protected]> wrote: > Hi Saroj, > > First you need to exact system and data from running emulator using > 'busybox'. > Then only you will have all these binaries. > > 1. Start the Android emulator > > 2. Get the busybox for android > http://benno.id.au/blog/2007/11/14/android-busybox > > 2. Load static compiled busybox into emulator > > # adb push busybox . > > 3. launch the Android shell > > # adb shell > > 4. make tarball with busybox > > # chmod +x /busybox > # busybox tar -c /data.tar /data > # busybox tar -c /system.tar /system > # exit > > 5. extract tarball from the emulator > > # adb pull /data.tar . > # adb pull /system.tar . > > Now you have system.tar and data.tar, get these two on your sd card and > run steps as I have mentioned in my last mail. > > Let me know if you still have any issue. > Thanks > Rizavan > > On Tue, Feb 10, 2009 at 11:20 PM, saroj <[email protected]> wrote: > > > Hello Rizvan, > > > runtime binary is missing in my android 1.0 filesystem. > > How you build it ??? > > > Regards, > > Saroj > > > On Feb 11, 12:34 am, Rizvan S <[email protected]> wrote: > > > Use below script to start android processes rather than init directly. > > > Switch to android fs from your rootfs before running this script. > > > Make sure you can read/write on mounted sd card partition before > > > starting this script. > > > > #!/system/bin/sh -x > > > > export PATH=/sbin:/system/sbin:/system/bin:$PATH > > > export LD_LIBRARY_PATH=/system/lib > > > export ANDROID_ROOT=/system > > > export ANDROID_ASSETS=/system/app > > > export ANDROID_DATA=/data > > > export EXTERNAL_STORAGE=/sdcard > > > export DRM_CONTENT=/data/drm/content > > > > /system/bin/app_process -Xzygote /system/bin --zygote & > > > /system/bin/dbus-daemon --system & > > > /system/bin/strace -ff -F -tt -s 200 runtime & > > > /system/bin/sh > > > > Thanks > > > Rizavan > > > > On Feb 10, 2:48 am, Rajesh N <[email protected]> wrote: > > > > > kindly format u r SDcard with EXT2 filesystem , it will work > > > > > Rajesh > > > > > On Tue, Feb 10, 2009 at 3:04 PM, Saroj (सरोज) <[email protected]> > > wrote: > > > > > Hello rajesh, > > > > > > I tried this command "/system/bin/strace -ff -F -tt -s 200 -o > > /dev/null > > > > > /init" > > > > > It gives the following error message: > > > > > > init: log_fd value=3<6>init: log init=/dev//dev/__kmsg__ > > > > > init: reading config file > > > > > init: device init > > > > > init: open_uevent_socket=4 > > > > > init: device_init...fd = 4 > > > > > init: coldboot 4722170 uS > > > > > init: init_property_area return 0 > > > > > init: > > > > > load_properties_from_file > > > > > init: cannot open '/initlogo.rle' > > > > > init: processing action 0x25098 (init) > > > > > init: .....do_loglevel start.... > > > > > init: log_level=level=3 > > > > > init: service 'console' requires console > > > > > init: cannot find '/system/bin/playmp3', disabling 'bootsound' > > > > > FAT: bogus number of reserved sectors > > > > > VFS: Can't find a valid FAT filesystem on dev mmcblk0. > > > > > warning: `rild' uses 32-bit capabilities (legacy support in use) > > > > > PANIC: handle_group_exit: 1690 leader 1670 > > > > > PANIC: handle_group_exit: 1689 leader 1670 > > > > > PANIC: handle_group_exit: 1688 leader 1670 > > > > > PANIC: handle_group_exit: 1687 leader 1670 > > > > > PANIC: handle_group_exit: 1685 leader 1670 > > > > > PANIC: handle_group_exit: 1676 leader 1670 > > > > > PANIC: handle_group_exit: 1677 leader 1670 > > > > > PANIC: handle_group_exit: 1675 leader 1670 > > > > > PANIC: handle_group_exit: 1674 leader 1670 > > > > > PANIC: handle_group_exit: 1672 leader 1670 > > > > > > What would be the reason ????? > > > > > > Regards, > > > > > Saroj K Pradhan > > > > > > On Tue, Feb 10, 2009 at 10:42 AM, Rajesh N <[email protected] > > >wrote: > > > > > >> Hi Saroj, > > > > > >> i went through u r mail,dont start ./init directly first time start > > it > > > > >> with this command > > > > >> "/system/bin/strace -ff -F -tt -s 200 -o /dev/null /init" > > > > > >> then u wont get zygoat problem! , I dont know why it happens, > > probabily > > > > >> it must be due to rw permissions in ext2 formated disk over which > > mounting > > > > >> takes place, where /data is read only! > > > > > >> Best Regards, > > > > >> Rajesh N > > > > > >> On Mon, Feb 9, 2009 at 9:01 PM, saroj <[email protected]> wrote: > > > > > >>> Hello, > > > > > >>> I ported my linux kernel 2.6.25 to Freescale based IMX31 board. > > After > > > > >>> that i applied the android kernel patches from the android 1.0 > > source > > > > >>> to my kernel 2.6.25. > > > > >>> I build the filesystem and load on my ext2 formatted SD card. > > > > > >>> Then i load my normal linux kernel 2.6.25 and mount the sdcard and > > run > > > > >>> the android ./init process. > > > > >>> After sometimes the Zygote process gets died due to SIGSEGV. > > > > > >>> Log messages: > > > > >>> # logcat > > > > >>> I/DEBUG ( 1651): debuggerd: Jan 19 2009 17:28:23 > > > > >>> E/mountd ( 1650): could not read initial mass storage state > > > > >>> E/mountd ( 1650): inotify_init failed, Function not implemented > > > > >>> E/flash_image( 1659): can't find recovery partition > > > > >>> D/AndroidRuntime( 1653): > > > > >>> D/AndroidRuntime( 1653): >>>>>>>>>>>>>> AndroidRuntime START > > > > >>> <<<<<<<<<<<<<< > > > > >>> D/AndroidRuntime( 1653): CheckJNI is ON > > > > >>> I/ ( 1654): ServiceManager: 0xaab8 > > > > >>> W/AudioHardwareInterface( 16read Setting54): Using stubbed audio > > > > >>> hardware. No sound will be produced. > > > > >>> I/AudioFlinger( 1654): AudioFlinger's main thread ready to run. > > > > >>> I/Parcel ( 1654): read Setting data pos of 0xa834 to 76 > > > > >>> I/Parcel ( 1654): read Setting data pos of 0xa834 to 76 > > > > >>> I/CameraService( 1654): CameraService started: pid=1654 > > > > >>> I/Parcel ( 1654): data pos of 0xa834 to 76 > > > > >>> D/AndroidRuntime( 1653): --- registering native functions --- > > > > >>> I/Zygote ( 1653): Preloading classes... > > > > >>> D/dalvikvm( 1653): GC freed 746 objects / 41240 bytes in 3ms > > > > >>> D/dalvikvm( 1653): GC freed 302 objects / 18584 bytes in 3ms > > > > >>> D/dalvikvm( 1653): GC freed 309 objects / 18720 bytes in 4ms > > > > >>> D/dalvikvm( 1653): Trying to load lib /system/lib/libmedia_jni.so > > 0x0 > > > > >>> D/dalvikvm( 1653): Added shared lib /system/lib/libmedia_jni.so 0x0 > > > > >>> D/dalvikvm( 1653): Trying to load lib /system/lib/libmedia_jni.so > > 0x0 > > > > >>> D/dalvikvm( 1653): Shared lib '/system/lib/libmedia_jni.so' already > > > > >>> loaded in same CL 0x0 > > > > >>> D/dalvikvm( 1653): Trying to load lib /system/lib/libmedia_jni.so > > 0x0 > > > > >>> D/dalvikvm( 1653): Shared lib '/system/lib/libmedia_jni.so' already > > > > >>> loaded in same CL 0x0 > > > > >>> I/DEBUG ( 1651): *** *** *** *** *** *** *** *** *** *** *** *** > > *** > > > > >>> *** *** *** > > > > >>> I/DEBUG ( 1651): Build fingerprint: > > 'generic/generic/generic/:1.0/ > > > > >>> TC3/eng.deepak.singal.20090119.170753:eng/test-keys' > > > > >>> I/DEBUG ( 1651): pid: 1653, tid: 1653 >>> zygote <<< > > > > >>> I/DEBUG ( 1651): signal 11 (SIGSEGV), fault addr 0000002c > > > > >>> I/DEBUG ( 1651): r0 0000bb00 r1 41106f58 r2 00000000 r3 > > 00000003 > > > > >>> I/DEBUG ( 1651): r4 befa0398 r5 00000000 r6 41106f58 r7 > > 00000000 > > > > >>> I/DEBUG ( 1651): r8 00000162 r9 00000000 10 4104acac fp > > 00000000 > > > > >>> I/DEBUG ( 1651): ip ad07f030 sp befa0340 lr ad050eaa pc > > > > >>> ad051eb6 cpsr 20000030 > > > > >>> I/DEBUG ( 1651): #00 pc ad051eb6 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #01 pc ad051f60 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #02 pc ad05a0a4 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #03 pc ad05a93e /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #04 pc ad0121dc /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #05 pc ad02a92c /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #06 pc ad0169d0 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #07 pc ad051f40 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #08 pc ad051f60 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #09 pc ad03ddd0 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #10 pc ad012748 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #11 pc ad02a92c /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #12 pc ad0169d0 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #13 pc ad051f40 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #14 pc ad051f60 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #15 pc ad05a0a4 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #16 pc ad05ab8c /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #17 pc ad00f7e8 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #18 pc ad02a92c /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #19 pc ad0169d0 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #20 pc ad051f40 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #21 pc ad051f60 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #22 pc ad05a0a4 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #23 pc ad05a17e /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #24 pc ad03c560 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #25 pc ad03c5e2 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #26 pc ad012748 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #27 pc ad02a92c /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #28 pc ad0169d0 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #29 pc ad051f40 /system/lib/libdvm.so > > > > >>> I/DEBUG ( 1651): #30 pc ad03f8aa /system/lib/libdvm.so > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
