Android adt preliminary understanding and analysis (3)

The sdk has been installed before. Although it only downloads the first 1.5, there is at least one sdk. The following will use a simulator to run the image file in the sdk.

Open the android virtual device manager tool and click new

After the configuration is completed, of course, only one api can be selected at present, so it is as follows:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/103SM219-0.png "title =" ttttt.png "/>

Select a small screen and click OK. At this time, the avd android virtual device has been created and the created path is

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/103SH242-1.png "title =" dddffdf.png "/>

Marked in red.

There are several files

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/103SJ5B-2.png "title =" ddfdsfas30831120.12.png "/>

The config. ini and hardware-qemu.ini files are very important. Open the analysis.

Config. ini file

Avd. ini. encoding = ISO-8859-1

Hw. dPad = no

Hw. LCD. density = 160

Hw. cpu. arch = arm

Hw. device. hash = 1473123938

Hw. camera. back = none

Disk. dataPartition. size = 200 M

Skin. path = 320x480

Skin. dynamic = yes

Hw. keyboard. lid = yes

Hw. keyboard = yes

Hw. ramSize = 512

Hw. device. manufacturer = Generic

Hw. sdCard = no

Hw. mainKeys = yes

Hw. accelerometer = yes

Skin. name = 320x480

Abi. type = armeabi

Hw. trackBall = no

Hw. device. name = 3.2in HVGA slider (ADP1)

Hw. battery = yes

Hw. sensors. proximity = yes

Image. sysdir.1 = platforms \ android-3 \ images \

Hw. sensors. orientation = yes

Hw. audioInput = yes

Hw. gps = yes

Vm. heapSize = 16

Hardware-qemu.ini this file is a lot of content, not all posted

Kernel. path = G: \ downtest \ android_test_sdk/platforms \ android-3 \ images \/kernel-qemu

Kernel. parameters = android. checkjni = 1

Disk. ramdisk. path = G: \ downtest \ android_test_sdk/platforms \ android-3 \ images \/ramdisk. img

Disk. systemPartition. initPath = G: \ downtest \ android_test_sdk/platforms \ android-3 \ images \/system. img

Disk. systemPartition. size = 200 m

The two files link the simulator with the sdk.

Kernel. path = G: \ downtest \ android_test_sdk/platforms \ android-3 \ images \/kernel-qemu

Indicates that the linux kernel uses the android-3 \ images \/kernel-qemu kernel, which is included in the installed sdk directory.

Of course, this kernel can also be downloaded and compiled by yourself through the android source code in the future.

Disk. ramdisk. path = G: \ downtest \ android_test_sdk/platforms \ android-3 \ images \/ramdisk. img

Ramdisk. img

A partitioned image file is mounted in read-only mode when the kernel is started. This file only contains/init and some configuration files. This ramdisk is used to call init, and mount the real root file system.
# In fact, ramdisk. img only compresses the/out/target/product/generic/root directory.

Disk. systemPartition. initPath = G: \ downtest \ android_test_sdk/platforms \ android-3 \ images \/system. img

It contains the entire system, android framework, application, and so on. It will be mounted to "/" and contains all the binary files in the system.
# System. img is out/target. A ing of the system directory under the product/generic/directory is similar to the image of the root file system, which contains android applications, configuration files, and fonts.

There are two links to describe the role of each img. Refer

Http://www.360doc.com/content/11/1213/19/3700464_172010379.shtml

Http://www.360doc.com/content/11/1213/19/3700464_172010221.shtml

These are all compiled and released only after google strict tests. The files that call these images are stored in

The G: \ downtest \ android_test_sdk \ tools \ emulator file contains versions that support different CPUs and operating systems.

The precondition for emulator to start is to find these kernel images, and avd is just an integrated configuration file among many configuration parameters when emulator starts.

If emulator is generated, it can also be generated from make PRODUCT-sdk in google source code, but it is indeed complicated and will not be discussed for the moment.

Basically, is it possible to understand the relationship between the simulator and the sdk?

Of course, there are still a lot of details, but you can leave them for further explanation.

Finally, take a picture and share it with you.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/103SG196-3.png "title =" OK .png "/>