On the linux terminal, enter:
Xxnan @ xxnan-pt :~ /Android-sdk-linux/tools $./emulator-avd android4.0.3
Is to open the simulator you created.
~ The/android-sdk-linux/tools $ directory is the sdk's tools directory, and android4.0.3 is the name of the simulator I created.
For example
Generally, we sometimes modify the content in the source code, compile the content, repackage system. img, and view the effect in the simulator (make snod in the source code directory ),
So how can system. img, userdata. img, and ramdisk. img be loaded when the simulator is started?
Generally, we use the following command:
Remember to go to the tools directory of the sdk:
Xxnan @ xxnan-pt :~ /Android-sdk-linux/tools $./emulator-avd android4.0.3-kernel source code/prebuilt/android-arm/kernel/kernel-qemu-armv7-system
System. img path/system. img-data userdata. img path/userdata. img-ramdisk. img path/ramdisk. img
The following is my path:
[Plain]
Xxnan @ xxnan-pt :~ /Android-sdk-linux/tools $./emulator-avd android4.0.3
-Kernel ~ /Android_source/android_4.0.3/prebuilt/android-arm/kernel/kernel-qemu-armv7
-System ~ /Android_source/android_4.0.3/out/target/product/generic/system. img
-Data ~ /Android_source/android_4.0.3/out/target/product/generic/userdata. img
-Ramdisk ~ /Android_source/android_4.0.3/out/target/product/generic/ramdisk. img
In this way, the system. img, userdata. img, and ramdisk. img can be loaded when the simulator starts, and you can see the effect of modifying the source code in the simulator.