Emulator running Android image

After the completion of the compilation needs to run, see the effect, the operation of a lot of problems   first explain android4.0, and then explain the android2.3.4, the two are the same   one. android4.0.1 can see the following link:http://www.cnblogs.com/hoji-real/articles/2144892.html  execute the command on this one: Emulator-system Sytem.img-data userdata.img-ramdisk ramdisk.img Description: Emulator is in the/working/android4.0/out/host/linux-x86/bin directory, Which is generated after compiling, look at the above command, it means to get this directory into path.   The subsequent  sytem.img userdata.img ramdisk.img are in the/working/android4.0/out/target/product/generic directory, so This directory has to be under path, too.   errors are as follows: 1.emulator:warning:system partition size adjusted to match image file (166 MB > (MB)) required Insufficient space, emulator add parameter-partition-size 1024 , i.e.: Emulator -partition-size 1024 -system sytem.img-data Userdata.img-ramdisk ramdisk.img taken from: http://www.dedecms.com/knowledge/servers/linux-bsd/2012/0822/12849.html    Finally, I added the following code in. BASHRC: Export Android_product_out_bin=/working/android4.0/out/host/linux-x86/binexport Android_product_out=/working/android4.0/out/target/product/genericexport Android_swt=/working/android4.0/ouT/host/linux-x86/frameworkexport path=${path}:${android_product_out_bin}:${android_product_out}; android_ SWT: Seems to have been holding swt.jar mistakes or something, according to the hint on the export.   needs to do the following: source ~/.bashrc 

2.

qemu: could not load initrd  ' ramdisk.img ', this error description, can be see the following link: http://bbs.csdn.net/topics /390120289 I remove the back of this:  -ramdisk ramdisk.img, simulator can come out, hehe, but always want to why people come out, I will not come out, on the search, finally see this:/http Blog.sina.com.cn/s/blog_66e96efa0101ia8j.html finally mentions that, in addition to chmod 777, it also needs to be executed with an absolute path, and the final execution code is as follows: Emulator-partition-size 1024-system System.img-data userdata.img-ramdisk/working/android4.0/out/target/product/generic/ramdisk.img  Finally, the simulator came out, hahaha to two pictures, haha:        two. android2.3.4 this is the same as the previous step, just change the path in the. BASHRC, and change the path of RAMDisk when running, #android4.0#export android_product_out_bin=/ Working/android4.0/out/host/linux-x86/bin#export android_product_out=/working/android4.0/out/target/product/ Generic#export Android_swt=/working/android4.0/out/host/linux-x86/framework#export PATH=${PATH}:${ANDROID_ product_out_bin}:${android_product_out};  #android2.3export android_product_out_bin=/working/android2.3.4/ Out/host/linux-x86/binexport android_product_out=/working/android2.3.4/out/target/product/genericexport Android_swt=/working/android2.3.4/out/host/linux-x86/frameworkexport PATH The =${path}:${android_product_out_bin}:${android_product_out};  effect is as follows:         You will find 2.3.4 more fluent than 4.0, haha      

Emulator runs Android image