Hi, maybe you can use the following two script taken from http://elinux.org/Android_on_OMAP#Start_via_scripts
start_android.sh echo "Starting Android..." fsck.ext2 -pv /dev/sda1 mount /dev/sda1 /mnt/usb rm -f /mnt/usb/tmp/* umount /proc umount /sys mount -t proc proc /mnt/usb/proc mount -t sysfs sysfs /mnt/usb/sys umask 000 chroot /mnt/usb/a.sh a.sh: #!/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 & runtime & /system/bin/sh In this mode you can debug with more accuracy app_process and runtime using strace via the following command: /system/bin/strace -f -ff -o runtime.log -tt -s 400 runtime& /system/bin/strace -f -ff -o app_process.log -tt -s 400 /system/bin/app_process -Xzygote /sytem/bin --zygote & Strace it's not present on the android ramdisk, is needed to compile it for arm architecture from source code. Best Regards, Andrea 2008/7/15 deepak singal <[EMAIL PROTECTED]>: > > Hi All, > > We are trying to port Android on ARM11(imx31) using following think: > > --->android-sdk_m5-rc15_linux-x86 or android-sdk_m5-rc14_linux-x86 > root file system > --->linux-2.6.23-android-m5-rc14.tar.gz android kernel patch > --->linux-2.6.22.6 kernel > ----> android file system in SD-card (ext2 file system) > > First boot into my normal file system and then switch to Android file > system and start Android init script. > > imx31#mount /dev/mmcblk0 /sd/ (mount sd card) > imx31#./a.sh > > /*************a.sh***************/ > > echo "" > echo "=======================" > echo " Initing Android Start " > echo "=======================" > echo "" > export PATH=/sbin:/system/sbin:/system/bin:$PATH > export LD_LIBRARY_PATH=/system/lib > export ANDROID_BOOTLOGO=1 > export ANDROID_ROOT=/system > export ANDROID_ASSETS=/system/app > export ANDROID_DATA=/data > export EXTERNAL_STORAGE=/sdcard > export DRM_CONTENT=/data/drm/content > umask 000 > chroot /sd/android-root /system/bin/sh > > /********************end_a.sh***********/ > > After that android shell shown in the console > > #./init & > > The binder messages keep printing on the console and the red eye on > the LCD keeps moving and stop after printing all the below messages. > Have any of you faced the following problem? > > Log of the binder error message is: > > # ./init & > init: HOW ARE YOU GENTLEMEN > init: reading config file > # init: device init > init: mtd partition -1, > init: mtd partition 0, "Bootloade > init: mtd partition 1, "Kernel" > init: mtd partition 2, "rootfs" > init: mtd partition 3, "IPL-SPL" > init: mtd partition 4, "kernel" > init: mtd partition 5, "rootfs" > init: mtd partition 6, "userfs" > binder_open: 1681:1681 > binder_mmap: 1681 40008000-40408000 (4096 K) vma 71 pagep 5f > binder_open: 1691:1691 > binder_mmap: 1691 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder_flush: 1691 woke 3 threads > binder_open: 1719:1719 > binder_mmap: 1719 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder: 1691 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1691 woke 0 threads > binder: release 1691:1698 transaction 107 in, still active > binder: send failed reply for transaction 107 to 1719:1719 > binder: 1681 close vm area 40008000-40408000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1681 woke 0 threads > binder_release: 1681 threads 4, nodes 2 (ref 1), refs 16, active > transactions 0, buffers 1, pages 1 > binder: 1719 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1719 woke 0 threads > binder_release: 1719 threads 2, nodes 0 (ref 0), refs 7, active > transactions 0, buffers 0, pages 1 > binder_open: 1726:1726 > binder_mmap: 1726 40008000-40408000 (4096 K) vma 71 pagep 5f > binder_open: 1728:1728 > binder_mmap: 1728 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder_release: 1691 threads 5, nodes 19 (ref 22), refs 2, active > transactions 1, buffers 4, pages 1 > binder_flush: 1728 woke 2 threads > binder: 1728 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1728 woke 0 threads > binder_release: 1728 threads 4, nodes 12 (ref 12), refs 1, active > transactions 0, buffers 3, pages 1 > binder: 1726 close vm area 40008000-40408000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1726 woke 0 threads > binder_release: 1726 threads 4, nodes 1 (ref 0), refs 12, active > transactions 0, buffers 1, pages 1 > binder_open: 1758:1758 > binder_mmap: 1758 40008000-40408000 (4096 K) vma 71 pagep 5f > binder_open: 1760:1760 > binder_mmap: 1760 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder_flush: 1760 woke 2 threads > binder_open: 1787:1787 > binder_mmap: 1787 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder: 1760 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1760 woke 0 threads > binder: release 1760:1760 transaction 320 in, still active > binder: send failed reply for transaction 320 to 1787:1787 > binder: 1758 close vm area 40008000-40408000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1758 woke 0 threads > binder_release: 1758 threads 4, nodes 2 (ref 1), refs 16, active > transactions 0, buffers 1, pages 1 > binder: 1787 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1787 woke 0 threads > binder_release: 1787 threads 3, nodes 0 (ref 0), refs 7, active > transactions 0, buffers 0, pages 1 > binder_open: 1795:1795 > binder_mmap: 1795 40008000-40408000 (4096 K) vma 71 pagep 5f > binder_release: 1760 threads 4, nodes 19 (ref 22), refs 2, active > transactions 1, buffers 4, pages 1 > binder_open: 1799:1799 > binder_mmap: 1799 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder_flush: 1799 woke 3 threads > binder_open: 1827:1827 > binder_mmap: 1827 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder: 1799 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1799 woke 0 threads > binder: release 1799:1799 transaction 464 in, still active > binder: send failed reply for transaction 464 to 1827:1827 > binder_release: 1799 threads 5, nodes 19 (ref 22), refs 2, active > transactions 1, buffers 4, pages 1 > binder: 1795 close vm area 40008000-40408000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1795 woke 0 threads > binder_release: 1795 threads 4, nodes 2 (ref 1), refs 16, active > transactions 0, buffers 1, pages 1 > binder: 1827 close vm area 42641000-42a41000 (4096 K) vma 2020071 > pagep 5f > binder_flush: 1827 woke 0 threads > binder_release: 1827 threads 2, nodes 0 (ref 0), refs 7, active > transactions 0, buffers 0, pages 1 > binder_open: 1836:1836 > binder_mmap: 1836 40008000-40408000 (4096 K) vma 71 pagep 5f > binder_open: 1838:1838 > binder_mmap: 1838 42641000-42a41000 (4096 K) vma 71 pagep 5f > binder_flush: 1838 woke 3 threads > > /****************After that red eye on the LCD stop > ***********************************/ > > > Any help will be highly appreciated. Thanks in Advance. > > Deepak Singal > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
