Hi Rizavan please find the logs which i captured using Strace. please help me out
[r...@linux /]#/system/bin/strace f -ff -tt -s 400 /dev/null /init /system/bin/strace: f: command not found [r...@linux /]#/system/bin/strace -f -ff -tt -s 400 /dev/null /init 00:01:12.447707 execve("/dev/null", ["/dev/null", "/init"], [/* 11 vars */]) = -1 EACCES (Permission denied) 00:01:12.451095 dup(2) = 3 00:01:12.452323 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) 00:01:12.453717 fstat64(3, {st_mode=S_IFCHR|0600, st_rdev=makedev(4, 64), ...}) = 0 00:01:12.456087 ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 00:01:12.457813 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40000000 00:01:12.459051 _llseek(3, 0, 0xbee22830, SEEK_CUR) = -1 ESPIPE (Illegal seek) 00:01:12.460811 write(3, "strace: exec: Permission denied\n", 32strace: exec: Permission denied ) = 32 00:01:12.462423 close(3) = 0 00:01:12.463538 munmap(0x40000000, 4096) = 0 00:01:12.464681 exit_group(1) = ? Process 813 detached On Fri, Feb 13, 2009 at 12:03 PM, Rizvan S <porting.begin...@gmail.com>wrote: > Sayiram, > > You have to check that strace log messages, it must give you hint whats > going wrong. > You also have to look in /dev/log/main , this also has log messages. > > Most of time.. I got very useful details with this logs to solve my > problem. > You have to figure out what init do step-by-steps , strace must give you > log and details where > is the problem. You can forward that strace log to me, I will check in case > I get time and will reply you. > > > Thanks > Rizavan > > > On Thu, Feb 12, 2009 at 5:42 PM, Sayiram K N <sayiram.koth...@gmail.com>wrote: > >> Hi rizvan >> my usb stick is recongnised by the target . on the USB stick >> i have extracted complete rootfs including system and data folders. but >> still, not able to switch to Android GUI. in back ground robot is flickering >> and after some time no actions. >> currently i am loading the kernel from RAM and the FS is pointing to usb >> stick i.e. to /sbin/init to mount in standard linux kernel. once i got the >> commnad prompt then executing the ./init (tried ./init_android) but no luck. >> so tried /system/bin/strcace - xx xx xx xx x /init method which i got in >> your earlier mails.but with this i got error saying systrace with error and >> exited. >> as i am using some git kernel, can you suggest me any other methos. >> can you help me out >> Sayiram K N >> >> >> >> On Fri, Feb 13, 2009 at 1:14 AM, Rizvan S <porting.begin...@gmail.com>wrote: >> >>> On your host machine, format usb stick with ext2 and flash image. >>> If you are using source then you will have system.image and >>> userdata.image in >>> 'android-source/out/target/product/generic' after successful build. There >>> is also ramdisk.img in case you want to use. >>> >>> First check whether your target kernel has driver for usb stick and you >>> can access stick ( after >>> mount using respective device node ) on target. If this works then you >>> can try steps I have mentioned in last mail. >>> >>> Thanks >>> Rizavan >>> >>> >>> >>> >>> On Wed, Feb 11, 2009 at 11:40 PM, Sayiram K N <sayiram.koth...@gmail.com >>> > wrote: >>> >>>> Hi Rizvan >>>> thanks for reply. i am using USB Stick as EXT2 FS.as i haven't >>>> flashed the Image also. its runnnig through a RAM bootloader. >>>> do you have any idea from where i can get the sys/folder. currently its >>>> empty >>>> Sayiram K N >>>> >>>> >>>> >>>> On Thu, Feb 12, 2009 at 1:01 PM, Rizvan S >>>> <porting.begin...@gmail.com>wrote: >>>> >>>>> Hi Sayiram, >>>>> >>>>> First of all, as per my understanding, don't try to put /sys and /data >>>>> on NAND because >>>>> it takes lots of space and most of time couldn't write all contents on >>>>> NAND properly. >>>>> I was trying in same way and face lot more issues. >>>>> Everytime see some new problem and its takes a lot to bring sys and >>>>> data on NAND. >>>>> >>>>> If you have SD/MMC card support on your target then do below steps. >>>>> Formate sd / mmc card with ext2 ( on host linux machine using fdisk ). >>>>> Put sys and data on sd card. >>>>> Create android.sh is script as below and copy it on sd card in /. >>>>> >>>>> #!/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 -f -ff -t -s 200 runtime & >>>>> /system/bin/sh >>>>> >>>>> Also copy strace for android on sd card in /system/bin. >>>>> http://benno.id.au/blog/2007/11/18/android-runtime-strace >>>>> >>>>> Boot android kernel ( either from source or by android patch ) whatever >>>>> way you have. >>>>> Mount the sd card . i.e mount -t ext2 /dev/mmcblk0 /mnt >>>>> ( In /mnt , now you will have /sys /data and android.sh) >>>>> Switch to android fs from your rootfs and run android.sh as default >>>>> program . >>>>> chroot /mnt /android.sh >>>>> >>>>> You can check strace log and also /dev/log/main for debugging. This >>>>> will give you hint whats going wrong. >>>>> I have done porting on my target long back using android patch , not >>>>> from source. >>>>> >>>>> >>>>> Thanks >>>>> Rizavan >>>>> >>>>> >>>>> >>>>> On Wed, Feb 11, 2009 at 10:20 PM, Sayiram K N < >>>>> sayiram.koth...@gmail.com> wrote: >>>>> >>>>>> Hi Rozavan >>>>>> Thanks for the reply. i am building from the source. >>>>>> steps are : >>>>>> got the kernel git for PXA27x >>>>>> the kernel working fine with normal jffs2. >>>>>> once i moved to yaffs(using normal technique like extracting the >>>>>> system and data from emulator) strucked up in the situation where >>>>>> neighter i >>>>>> can see robot continuously. >>>>>> i found that in my sys/ folder there are no android_power directory. >>>>>> can you help me out from where i can get those files too. >>>>>> as well your pointers to comeout from my current situatio >>>>>> Sayiram >>>>>> >>>>>> >>>>>> On Thu, Feb 12, 2009 at 12:28 AM, Rizvan S < >>>>>> porting.begin...@gmail.com> wrote: >>>>>> >>>>>>> Hi Sayiram, >>>>>>> >>>>>>> Are you building from source or using patch ( hack ) to bring android >>>>>>> on your target ? >>>>>>> Specify your setup and steps so I can try to help you. >>>>>>> >>>>>>> Thanks >>>>>>> Rizavan >>>>>>> >>>>>>> >>>>>>> On Wed, Feb 11, 2009 at 9:40 AM, sram <sayiram.koth...@gmail.com>wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi >>>>>>>> even i am facing the same issue. can any one helpout on this >>>>>>>> >>>>>>>> On Jan 30, 11:43 am, Rajesh N <rajesh.andr...@gmail.com> wrote: >>>>>>>> > HI all, >>>>>>>> > >>>>>>>> > I am unable to progress further in android booting, when I >>>>>>>> execute ./init& >>>>>>>> > inside android shell, I am able to see Android logo and this >>>>>>>> process seems >>>>>>>> > to repeating continuously!!!!! , I am pasting the logcat messages >>>>>>>> below, if >>>>>>>> > anyone could help me in solving this issue, it would be a great >>>>>>>> help for me. >>>>>>>> > >>>>>>>> > root >>>>>>>> > login[1844]: root login on 'ttymxc0' >>>>>>>> > >>>>>>>> > BusyBox v1.6.1 () Built-in shell (ash) >>>>>>>> > Enter 'help' for a list of built-in commands. >>>>>>>> > >>>>>>>> > r...@freescale ~$ mount /de r...@freescale ~$ mount /dev/ >>>>>>>> [Jsda [8D >>>>>>>> > r...@freescale ~$ mount /dev/sda [J >>>>>>>> > /dev/sda /dev/sda1 >>>>>>>> > r...@freescale ~$ mount /dev/sda [J1 /sd >>>>>>>> > r...@freescale ~$ cd cd / >>>>>>>> > r...@freescale /$ ls >>>>>>>> > bin lost+found sqlite_stmt_journals >>>>>>>> > cache mnt start-android >>>>>>>> > data opt sys >>>>>>>> > dev proc system >>>>>>>> > etc root tmp >>>>>>>> > home sbin unit_tests >>>>>>>> > lib sd usr >>>>>>>> > linuxrc sdcard var >>>>>>>> > r...@freescale /$ ./st r...@freescale /$ ./start-android [J >>>>>>>> > =============================== >>>>>>>> > Initing Android >>>>>>>> > =============================== >>>>>>>> > \...@\h \w$ init & >>>>>>>> > init: not found >>>>>>>> > \...@\h \w$ ./init & >>>>>>>> > \...@\h \w$ init: cannot open '/initlogo.rle' >>>>>>>> > init: command 'loglevel' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'export' r=0 >>>>>>>> > init: command 'symlink' r=-1 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mount' r=0 >>>>>>>> > init: command 'mount' r=0 >>>>>>>> > init: command 'write' r=0 >>>>>>>> > init: command 'write' r=-1 >>>>>>>> > init: command 'write' r=0 >>>>>>>> > init: command 'write' r=-1 >>>>>>>> > init: command 'write' r=-1 >>>>>>>> > init: mtd partition 0, nand.bootloade >>>>>>>> > init: mtd partition 1, nand.kernel >>>>>>>> > init: mtd partition 2, nand.rootfs >>>>>>>> > init: mtd partition 3, nand.configure >>>>>>>> > init: mtd partition 4, nand.userfs >>>>>>>> > init: command 'mount' r=-1 >>>>>>>> > init: command 'mount' r=-1 >>>>>>>> > init: command 'mount' r=-1 >>>>>>>> > init: command 'chown' r=-30 >>>>>>>> > init: command 'chmod' r=-30 >>>>>>>> > init: command 'mount' r=-1 >>>>>>>> > init: command 'chown' r=-30 >>>>>>>> > init: command 'chmod' r=-30 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chmod' r=-2 >>>>>>>> > init: command 'mkdir' r=-30 >>>>>>>> > init: command 'mkdir' r=-2 >>>>>>>> > init: command 'mkdir' r=-30 >>>>>>>> > init: command 'mkdir' r=-2 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-30 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'mkdir' r=-17 >>>>>>>> > init: command 'chown' r=-30 >>>>>>>> > init: command 'chmod' r=-30 >>>>>>>> > init: command 'mkdir' r=-30 >>>>>>>> > init: command 'mkdir' r=-30 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chmod' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chmod' r=-2 >>>>>>>> > init: Created socket '/dev/socket/property_service' with mode >>>>>>>> '666', user >>>>>>>> > '0', group '0' >>>>>>>> > init: processing action 0x24a28 (boot) >>>>>>>> > init: command 'ifup' r=0 >>>>>>>> > init: command 'hostname' r=0 >>>>>>>> > init: command 'domainname' r=0 >>>>>>>> > init: command 'setrlimit' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'write' r=0 >>>>>>>> > init: command 'write' r=0 >>>>>>>> > init: command 'write' r=0 >>>>>>>> > init: command 'write' r=0 >>>>>>>> > init: command 'chown' r=0 >>>>>>>> > init: command 'chown' r=0 >>>>>>>> > init: command 'chown' r=0 >>>>>>>> > init: command 'chown' r=0 >>>>>>>> > init: command 'chown' r=0 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chmod' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=-2 >>>>>>>> > init: command 'chown' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: command 'setprop' r=0 >>>>>>>> > init: starting 'console' >>>>>>>> > sh: can't access tty; job control turned off >>>>>>>> > # init: starting 'servicemanager' >>>>>>>> > init: starting 'mountd' >>>>>>>> > init: Created socket '/dev/socket/mountd' with mode '660', user >>>>>>>> '0', group >>>>>>>> > '1009' >>>>>>>> > init: starting 'debuggerd' >>>>>>>> > init: starting 'ril-daemon' >>>>>>>> > init: Created socket '/dev/socket/rild-debug' with mode '660', >>>>>>>> user '1001', >>>>>>>> > group '1000' >>>>>>>> > init: starting 'zygote' >>>>>>>> > init: Created socket '/dev/socket/zygote' with mode '666', user >>>>>>>> '0', group >>>>>>>> > '0' >>>>>>>> > init: Created socket '/dev/socket/rild' with mode '660', user >>>>>>>> '0', group >>>>>>>> > '1001' >>>>>>>> > init: starting 'media' >>>>>>>> > init: starting 'bootsound' >>>>>>>> > init: starting 'dbus' >>>>>>>> > init: Created socket '/dev/socket/dbus' with mode '660', user >>>>>>>> '1002', group >>>>>>>> > '1002' >>>>>>>> > init: starting 'installd' >>>>>>>> > init: Created socket '/dev/socket/installd' with mode '600', user >>>>>>>> '1000', >>>>>>>> > group '1000' >>>>>>>> > init: starting 'flash_recovery' >>>>>>>> > init: command 'class_start' r=0 >>>>>>>> > init: processing action 0x254b8 >>>>>>>> (property:persist.service.adb.enable=1) >>>>>>>> > init: starting 'adbd' >>>>>>>> > init: command 'start' r=0 >>>>>>>> > init: waitpid returned pid 2101, status = 00000100 >>>>>>>> > init: process 'flash_recovery', pid 2101 exited >>>>>>>> > init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'add', '/kernel/uids/1000', 'kernel', '', -1, -1 } >>>>>>>> > init: event { 'add', '/kernel/uids/1013', 'kernel', '', -1, -1 } >>>>>>>> > init: event { 'add', '/kernel/uids/1002', 'kernel', '', -1, -1 } >>>>>>>> > init: event { 'add', '/kernel/uids/1001', 'kernel', '', -1, -1 } >>>>>>>> > fsl-ehci fsl-ehci.1: dev 1 ep1in scatterlist error -104/-121 >>>>>>>> > usb 2-1: reset high speed USB device using fsl-ehci and address 2 >>>>>>>> > init: waitpid returned pid 2094, status = 0000ff00 >>>>>>>> > init: process 'bootsound', pid 2094 exited >>>>>>>> > init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 } >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: waitpid returned pid 2088, status = 00000009 >>>>>>>> > init: process 'zygote', pid 2088 exited >>>>>>>> > init: process 'zygote' killing any children in process group >>>>>>>> > init: starting 'zygote' >>>>>>>> > init: Created socket '/dev/socket/zygote' with mode '666', user >>>>>>>> '0', group >>>>>>>> > '0' >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: waitpid returned pid 2710, status = 00000009 >>>>>>>> > init: process 'zygote', pid 2710 exited >>>>>>>> > init: process 'zygote' killing any children in process group >>>>>>>> > init: starting 'zygote' >>>>>>>> > init: Created socket '/dev/socket/zygote' with mode '666', user >>>>>>>> '0', group >>>>>>>> > '0' >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: waitpid returned pid 2736, status = 00000009 >>>>>>>> > init: process 'zygote', pid 2736 exited >>>>>>>> > init: process 'zygote' killing any children in process group >>>>>>>> > init: starting 'zygote' >>>>>>>> > init: Created socket '/dev/socket/zygote' with mode '666', user >>>>>>>> '0', group >>>>>>>> > '0' >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: waitpid returned pid 2762, status = 00000009 >>>>>>>> > init: process 'zygote', pid 2762 exited >>>>>>>> > init: process 'zygote' killing any children in process group >>>>>>>> > init: starting 'zygote' >>>>>>>> > init: Created socket '/dev/socket/zygote' with mode '666', user >>>>>>>> '0', group >>>>>>>> > '0' >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'remove', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'remove', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > init: event { 'add', '/class/vc/vcs7', 'vc', '', 7, 7 } >>>>>>>> > init: event { 'add', '/class/vc/vcsa7', 'vc', '', 7, 135 } >>>>>>>> > >>>>>>>> > Best Regards. >>>>>>>> > Rajesh >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks >>>>>>> Rizavan >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks >>>>> Rizavan >>>>> >>>>> >>>>> >>>>> >>>>> >>> >>> >>> -- >>> Thanks >>> Rizavan >>> >>> >>> >>> >>> > > > -- > Thanks > Rizavan > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---