| /build/target/product/ |
| full_x86.mk | 19 # build quite specifically for the emulator, and might not be
22 # If running on an emulator or some other device that has a LAN connection
29 include $(SRC_TARGET_DIR)/product/emulator.mk
44 PRODUCT_MODEL := AOSP on IA Emulator
|
| full_x86_64.mk | 19 # build quite specifically for the emulator, and might not be
22 # If running on an emulator or some other device that has a LAN connection
32 include $(SRC_TARGET_DIR)/product/emulator.mk
47 PRODUCT_MODEL := AOSP on IA x86_64 Emulator
|
| aosp_arm64.mk | 19 # build quite specifically for the emulator, and might not be
28 include $(SRC_TARGET_DIR)/product/emulator.mk
32 PRODUCT_MODEL := AOSP on ARM arm64 Emulator
|
| full.mk | 19 # build quite specifically for the emulator, and might not be
25 include $(SRC_TARGET_DIR)/product/emulator.mk
31 PRODUCT_MODEL := AOSP on ARM Emulator
|
| full_mips.mk | 19 # mips build quite specifically for the emulator, and might not be
25 include $(SRC_TARGET_DIR)/product/emulator.mk
31 PRODUCT_MODEL := AOSP on MIPS Emulator
|
| full_mips64.mk | 19 # mips64 build quite specifically for the emulator, and might not be
28 include $(SRC_TARGET_DIR)/product/emulator.mk
34 PRODUCT_MODEL := AOSP on MIPS64 Emulator
|
| /device/htc/flounder/flounder32/ |
| BoardConfig.mk | 16 # Re-enable emulator for 32-bit
|
| /sdk/apps/SdkController/assets/ |
| intro_help.html | 30 <b>SdkController</b> is used to send sensor data from an actual device to an emulator. <p/>
36 <li>Finally <b>run an emulator</b> with an AVD targetting <b>API 15</b>.
37 Multi-touch emulation must be explicitly enabled in emulator either by setting "Touch screen type" property to "multi-touch" in AVD Manager,
38 or by starting the emulator with "-screen multi-touch" option.</li>
|
| /external/qemu/docs/ |
| ANDROID-QEMUD.TXT | 8 communication channel between the emulated system and the emulator program
10 the emulator program is using qemu pipes (see ANDROID-QEMU-PIPE.TXT for details
14 emulator without requiring special kernel support; this simplifies a lot of
21 The emulator provides 'services' to various parts of the emulated system.
44 to the emulator. It does so by:
59 will pass all messages between clients and emulator services. Thus,
63 emulator <==serial==> qemud <---> /dev/socket/qemud <-+--> client1
86 Zero-sized packets are silently discard by qemud and the emulator and
90 emulator. These are the following:
93 name to the daemon, the later sends to the emulator
[all...] |
| DEVELOPMENT.TXT | 5 emulator codebase, which will be useful for anyone planning to
9 THE ANDROID EMULATOR SOURCES ARE CURRENTLY HEAVILY BEING REFACTORED, IF YOU
24 The Android emulator sources contains many, heavily-modified, sources from the
44 Contains various third-party libraries the emulator depends on
74 Only a fraction of the QEMU sources are actually part of the Android emulator
82 There is currently very limited automated testing for the Android emulator,
89 the emulator binaries with existing SDK system images remains necessary.
96 emulator code (e.g. to gain new features, like the ability to emulate new CPUs,
101 both Android emulator and QEMU documentation before trying to do so though.
104 Android emulator. It's generally preferable to write stubs. The Android emulato
[all...] |
| /development/tools/emulator/test-apps/SmokeTests/ |
| AndroidManifest.xml | 17 package="com.android.emulator.smoketests">
23 <instrumentation android:targetPackage="com.android.emulator.smoketests"
25 <application android:label="Emulator Smoke Tests">
|
| /device/generic/goldfish/qemu-props/ |
| Android.mk | 15 # this file is used to build emulator-specific program tools
16 # that should only run in the emulator.
22 # to setup various system properties sent by the emulator program.
|
| /device/generic/mini-emulator-arm64/ |
| mini_emulator_arm64.mk | 17 $(call inherit-product, device/generic/mini-emulator-armv7-a-neon/mini_emulator_common.mk)
20 PRODUCT_DEVICE := mini-emulator-armv7-a-neon
22 PRODUCT_MODEL := mini-emulator-armv7-a-neon
|
| /device/generic/mini-emulator-armv7-a-neon/ |
| m_e_arm.mk | 17 $(call inherit-product, device/generic/mini-emulator-armv7-a-neon/mini_emulator_common.mk)
20 PRODUCT_DEVICE := mini-emulator-armv7-a-neon
22 PRODUCT_MODEL := mini-emulator-armv7-a-neon
|
| /device/generic/mini-emulator-mips/ |
| mini_emulator_mips.mk | 17 $(call inherit-product, device/generic/mini-emulator-armv7-a-neon/mini_emulator_common.mk)
20 PRODUCT_DEVICE := mini-emulator-mips
22 PRODUCT_MODEL := mini-emulator-mips
|
| /device/generic/mini-emulator-x86/ |
| mini_emulator_x86.mk | 17 $(call inherit-product, device/generic/mini-emulator-armv7-a-neon/mini_emulator_common.mk)
20 PRODUCT_DEVICE := mini-emulator-x86
22 PRODUCT_MODEL := mini-emulator-x86
|
| /device/generic/mini-emulator-x86_64/ |
| mini_emulator_x86_64.mk | 17 $(call inherit-product, device/generic/mini-emulator-armv7-a-neon/mini_emulator_common.mk)
20 PRODUCT_DEVICE := mini-emulator-x86_64
22 PRODUCT_MODEL := mini-emulator-x86_64
|
| /external/qemu/android/utils/ |
| filelock.h | 22 ** a FileLock is useful to prevent several emulator instances from using the same
26 ** NULL only if the corresponding path is already locked by another emulator
30 ** function can detect stale file locks that can longer when the emulator
|
| /prebuilts/android-emulator/linux-x86_64/ |
| emulator | |
| /sdk/apps/SdkController/src/com/android/tools/sdkcontroller/lib/ |
| Connection.java | 33 * Encapsulates a connection between SdkController service and the emulator. On
35 * 'android.sdk.controller'. On the emulator side the connection is established
42 * The way communication between the emulator and SDK controller service works
45 * 1. Both sides, emulator and the service have components that implement a particular
46 * type of emulation. For instance, AndroidSensorsPort in the emulator, and
52 * 2. Channels are connected to emulator via separate socket instance (though all
55 * 3. Connection is initiated by the emulator side, while the service provides
61 * 1. Bind to "android.sdk.controller" socket, listening to emulator connections.
65 * 3. Bind emulator connection with service-side channel via port name, provided by
66 * the emulator
[all...] |
| /frameworks/base/docs/html/training/basics/firstapp/ |
| running-app.jd | 7 page.tags=emulator
21 <li><a href="#Emulator">Run on the Emulator</a></li>
43 real device and on the Android emulator, and in both cases with either Android Studio or the command
101 <h2 id="Emulator">Run on the Emulator</h2>
103 <p>Whether you're using Android Studio or the command line, to run your app on the emulator you need
105 AVD is a device configuration for the Android emulator that allows you to model a specific
148 <li>In the <strong>Choose Device</strong> window, click the <strong>Launch emulator</strong> radio
150 <li>From the <strong>Android virtual device</strong> pull-down menu, select the emulator
[all...] |
| /system/core/adb/ |
| SERVICES.TXT | 35 host:emulator:<port>
37 new emulator starts up. <port> is a decimal number corresponding
38 to the emulator's ADB control port, i.e. the TCP port that the
39 emulator will forward automatically to the adbd daemon running
40 in the emulator system.
42 This mechanism allows the ADB server to know when new emulator
46 Ask to switch the connection to the device/emulator identified by
57 Ask to switch the connection to one emulator connected through TCP.
58 This will fail if there is more than one such emulator instance
63 either the device or emulator connect to/running on the host
[all...] |
| /external/qemu/ |
| Makefile.android | 132 $(info emulator: Ignoring unsupported GCC flag $(GCC_W_NO_MISSING_FIELD_INITIALIZERS))
228 # $(call start-emulator-library, <module-name>)
232 # $(call end-emulator-library)
234 start-emulator-library = \
242 $(call start-emulator-library, $1) \
245 # Used with start-emulator-library
246 end-emulator-library = \
247 $(eval $(end-emulator-module-ev)) \
250 # A variant of start-emulator-library to start the definition of a host
251 # program instead. Use with end-emulator-progra
[all...] |
| /frameworks/base/docs/html/tools/help/ |
| emulator.jd | 1 page.title=Android Emulator
17 <li><a href="{@docRoot}tools/devices/emulator.html">Using the Android Emulator</a></li>
25 <p>The Android SDK includes a mobile device emulator — a virtual mobile device
26 that runs on your computer. The emulator lets you develop and test
31 For a complete guide to using the Android Emulator, see
32 <a href="{@docRoot}tools/devices/emulator.html">Using the Android Emulator</a>.
37 <p>Table 1 summarizes the mappings between the emulator keys and the keys of your keyboard.</p>
39 <p class="table-caption"><strong>Table 1.</strong> Emulator keyboard mapping</p
[all...] |
| /bionic/libc/bionic/ |
| malloc_debug_qemu.cpp | 31 * usage in the emulator to detect memory allocation violations, such as
35 * code is to notify the emulator about memory being allocated/deallocated,
36 * providing information about each allocation. The idea is that emulator will
41 * every time emulator detects access to any of these guarding areas, it can be
76 * the emulator about new memory block being allocated from the heap. The entire
79 * replacing pointers with target_ulong) is also declared in the emulator's
104 * has occurred. This field is used by the emulator to report errors in
106 * emulator sets this field to zero (invalid value for a process ID).
121 /* Describes memory block info queried from emulator. This structure is passed
126 * rather we keep it in the emulator, we need to query emulator for tha
[all...] |
