I typed "am start" instruction directly on the terminal.
Then I got the message below.
# am start -a android.intent.action.MAIN -n
com.example.helloworld/com.example.helloworld.MainActivity
Starting: Intent { act=android.intent.action.MAIN
cmp=com.example.helloworld/.MainActivity }
Error type 3
Error: Activity class
{com.example.helloworld/com.example.helloworld.MainActivity} does not exist.I'm not familiar with Android.. So I don't know why it can not find my application. I only put my *.apk file in the /android-img-mounted-dir/system/app directory. Do I have to install by the adb install instruction? If do I have to, then, how could I use the adb shell instruction on the terminal? In the /gem5/util/term/m5term localhost 3456, It does not support the gdb. Or did I just type the am start instruction wrong? Thank you... 2012/10/17 이주성 <[email protected]> > I think I figured out that my own application not even started. > The screen lock which I seen was just came out by the time-out, I guess. > I type the ps instruction in the terminal. > However, there were not exist my own application. > The output below shows the ps results. > USER PID PPID VSIZE RSS WCHAN PC NAME > root 1 0 320 168 c00c4ca4 0000875c S /init > root 2 0 0 0 c0060a54 00000000 S kthreadd > root 3 2 0 0 c0051514 00000000 S ksoftirqd/0 > root 4 2 0 0 c007ec40 00000000 S migration/0 > root 5 2 0 0 c007f1fc 00000000 S watchdog/0 > root 6 2 0 0 c005d2d8 00000000 S events/0 > root 7 2 0 0 c005d2d8 00000000 S khelper > root 10 2 0 0 c0066ddc 00000000 S async/mgr > root 13 2 0 0 c005d2d8 00000000 S suspend > root 147 2 0 0 c009d92c 00000000 S sync_supers > root 149 2 0 0 c009e3d8 00000000 S bdi-default > root 151 2 0 0 c005d2d8 00000000 S kblockd/0 > root 157 2 0 0 c005d2d8 00000000 S ata_aux > root 158 2 0 0 c005d2d8 00000000 S ata_sff/0 > root 163 2 0 0 c01f09d0 00000000 S khubd > root 166 2 0 0 c020f22c 00000000 S kseriod > root 170 2 0 0 c005d2d8 00000000 S kmmcd > root 260 2 0 0 c005d2d8 00000000 S rpciod/0 > root 268 2 0 0 c007f4e4 00000000 S khungtaskd > root 269 2 0 0 c009842c 00000000 S kswapd0 > root 319 2 0 0 c005d2d8 00000000 S aio/0 > root 326 2 0 0 c005d2d8 00000000 S nfsiod > root 370 2 0 0 c005d2d8 00000000 S scsi_tgtd/0 > root 375 2 0 0 c01b7d38 00000000 S scsi_eh_0 > root 397 2 0 0 c005d2d8 00000000 S kpsmoused > root 433 2 0 0 c005d2d8 00000000 S usbhid_resumer > root 436 2 0 0 c005d2d8 00000000 S binder > root 465 1 300 4 c00c4ca4 0000875c S /sbin/ueventd > system 631 1 820 216 c023d8c4 afd0b6fc S > /system/bin/servicemanager > root 632 1 3872 524 ffffffff afd0bdac S /system/bin/vold > root 634 1 680 200 c0273eac afd0c0cc S > /system/bin/debuggerd > root 635 1 1284 456 c00651e0 afd0bdac S /system/bin/rild > bluetooth 638 1 1268 524 c00c4ca4 afd0c59c S > /system/bin/dbus-daemon > root 639 1 828 332 c02d047c afd0b45c S /system/bin/installd > keystore 641 1 1756 252 c0273eac afd0c0cc S /system/bin/keystore > root 642 1 748 200 c004ed30 afd0c3ac S /system/bin/sh > root 643 1 1352 4 ffffffff 00008294 S /sbin/adbd > root 660 2 0 0 c00d3944 00000000 S flush-8:0 > media 707 1 17876 3576 ffffffff afd0b6fc S > /system/bin/mediaserver > root 708 1 3848 276 ffffffff afd0bdac S /system/bin/netd > root 709 1 61388 26576 c00c4ca4 afd0b844 S zygote > system 716 709 138148 40288 ffffffff afd0b6fc S system_server > system 787 709 75536 22936 ffffffff afd0c51c S com.android.systemui > app_15 792 709 78356 19564 ffffffff afd0c51c S > com.android.inputmethod.latin > radio 819 709 83760 19876 ffffffff afd0c51c S com.android.phone > app_9 839 709 74548 19768 ffffffff afd0c51c S > android.process.acore > app_5 873 709 85648 29112 ffffffff afd0c51c S com.android.launcher > app_1 899 709 74096 17384 ffffffff afd0c51c S > com.android.providers.calendar > app_11 907 709 71988 17124 ffffffff afd0c51c S > android.process.media > root 920 642 908 244 00000000 afd0b45c R ps > > So I conclude myself that "am start" instruction does not work. > Or naturally not working in the *.rcS files. > Then how can I start up my app? > Please help me... > Thank you! > > Joosung Lee > > > 2012/10/17 이주성 <[email protected]> > >> Hi, I'm Joosung Lee. >> I'm sorry for bothering you to send a similar mail. >> But I'm eagerly wanna know about the way to port my own app on the gem5. >> >> I'm trying to run my own application on Android Gingerbread with gem5. >> >> I mounted ARMv7a-Gingerbread-Android.SMP.mouse.nolock.clean.img and put >> my apk file in the /mounted-directory/system/app directory. >> And then, I added some lines to Benchmarks.py file in >> /gem5-directory/configs/common/ as below. >> 'helloworld-gb': [SysConfig('helloworld-gb.rcS', '256MB', >> >> 'ARMv7a-Gingerbread-Android.SMP.mouse.nolock.clean.img')], >> >> After that, I made some rcS fils in the /gem5-directory/configs/boot/ >> directory. >> Which is helloworld-gb.rcS, as below. >> >> run_hello_test() { >> am start -a android.intent.action.MAIN -n >> com.example.helloworld/com.example.helloworld.MainActivity >> return >> } >> >> sleep 10 >> /sbin/m5 dumpstats >> /sbin/m5 resetstats >> run_hello_test >> >> Finally, I typed build/ARM/gem5.opt configs/example/fs.py -b >> helloworld-gb --kernel=vmlinux.smp.mouse.arm to run. >> However after booting done, nothing happened but only shows screen lock. >> I thought it's weird because the OS which with BBench were not showed >> screen lock. >> So I modified Benchmarks.py again as >> 'helloworld-gb': [SysConfig('helloworld-gb.rcS', '256MB', >> >> 'ARMv7a-Gingerbread-Android.SMP.mouse.nolock.img')], >> to use the non-clean version OS. >> But it only shows the web browser. >> >> What can I do to remove the screen lock and run my own application on >> clean version OS? >> Or what can I do to run my own application on non-clean version? (How can >> modify it to not showing web browser?) >> >> Please help me... >> sorry for my poor English... >> >> >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
