| /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...] |
| index.jd | 15 avd</code>) the emulator (<code>emulator</code>), and the Dalvik Debug Monitor Server
34 <dt><a href="emulator.html">Android Emulator (emulator)</a></dt>
46 <dd>Helps you create a disk image that you can use with the emulator, to simulate the presence
49 <dd>Runs on your emulator or device and generates pseudo-random streams of user events such
53 <dd>Provides an API for writing programs that control an Android device or emulator from
76 Android Debug Bridge is a versatile tool that lets you manage the state of an emulator instance or
|
| /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
75 * the emulator about new memory block being allocated from the heap. The entire
78 * replacing pointers with target_ulong) is also declared in the emulator's
103 * has occurred. This field is used by the emulator to report errors in
105 * emulator sets this field to zero (invalid value for a process ID).
120 /* Describes memory block info queried from emulator. This structure is passed
125 * rather we keep it in the emulator, we need to query emulator for tha
[all...] |
| /external/qemu/ |
| Makefile.common | 4 # - the emulator-ui program (which is target-agnostic)
6 # - the "standalone" emulator programs (embed both UI and engine in a single
7 # binary and process), i.e. "emulator" for ARM and "emulator-x86" for x86.
52 ### emulator-common: LIBRARY OF COMMON FUNCTIONS
136 $(call start-emulator-library, emulator-common)
140 $(call end-emulator-library)
148 $(call start-emulator-library, emulator64-common)
152 $(call end-emulator-library
[all...] |
| /external/qemu/android/ |
| help.c | 27 " Only one emulator process can run a given AVD at a time, but\n"
34 " emulator @foo\n\n"
50 " SPECIAL NOTE: in the case where you are *not* using the emulator\n"
102 " The emulator detects that you are working from the Android build system\n"
108 " In this case, the emulator will look by default for the following image\n"
114 " - kernel-qemu : the emulator-specific Linux kernel image.\n\n"
119 " Skins will be looked in <build-root>/development/tools/emulator/skins/\n\n"
131 " automatically removed when the emulator exits. There is thus no way to\n"
132 " make persistent changes to this image through the emulator, even if\n"
139 " SPECIAL NOTE: If you are using the emulator with the Android SDK, the\n
[all...] |
| main-emulator.c | 13 /* This is the source code to the tiny "emulator" launcher program
14 * that is in charge of starting the target-specific emulator binary
15 * for a given AVD, i.e. either 'emulator-arm' or 'emulator-x86'
18 * known as 'emulator-ui', but is a good placeholder until this
39 # define D(...) do { if (android_verbose) printf("emulator:" __VA_ARGS__); } while (0)
54 /* Normally emulator is compiled in 32-bit. In standalone it can be compiled
55 in 64-bit (with ,/android-configure.sh --try-64). In this case, emulator-$ARCH
105 * 2) '-force-32bit' which always use 32-bit emulator on 64-bit platforms
154 D("Found target-specific emulator binary: %s\n", emulatorPath)
[all...] |
| /external/qemu/hw/ |
| goldfish_pipe.h | 21 * system and the emulator program.
23 * To open a new pipe to the emulator, a guest client will do the following:
35 * emulator.
37 * This header provides the interface used by pipe services in the emulator
80 * emulator is not ready to receive data yet.
100 * In this case, when the pipe is loaded, the emulator will automatically
109 * be loaded. In this case, the emulator will automatically force-close
173 #define PIPE_CMD_WRITE_BUFFER 4 /* send a user buffer to the emulator */
174 #define PIPE_CMD_WAKE_ON_WRITE 5 /* tell the emulator to wake us when writing is possible */
181 #define PIPE_CMD_READ_BUFFER 6 /* receive a page-contained buffer from the emulator */
[all...] |
| /sdk/apps/SdkController/src/com/android/tools/sdkcontroller/lib/ |
| Channel.java | 34 * Encapsulates basics of a connection with the emulator.
39 * that defines logical format of the data transferred between the emulator and
41 * and transfers sensor value changes from the device to the emulator. "Multi-touch"
43 * events to the emulator, while receiving frame buffer updates from the emulator.
45 * Besides connection with the emulator, each channel may contain one or more UI
51 * - Implementing posting of messages to emulator in opposite to direct message
58 * Encapsulates a message posted to be sent to the emulator from a worker
143 /** Service-side emulator is connected. */
145 /** Service-side emulator is disconnected. *
[all...] |
| ProtocolConstants.java | 6 * Contains declarations of constants that are tied to emulator implementation.
18 * Header sizes for packets sent / received by SDK controller emulator.
70 * Constants related to handshake protocol between the emulator and a channel.
76 * When emulator connects to SDK controller, the first thing that goes
93 * emulator connection for this channel. Emulator should stop connection
127 /** Size of an event entry in the touch event message to the emulator. */
144 /** Message that delivers sensor events to emulator. */
|
| /external/chromium_org/build/android/ |
| avd.py | 20 from pylib.utils import emulator namespace
25 # the emulator to find the system images upon launch.
55 logging.critical('ERROR: Emulator SDK not installed. Run '
59 emulator.LaunchEmulators(options.emulator_count, options.abi, True)
|
| /external/qemu/docs/ |
| ANDROID-SKIN-FILES.TXT | 1 Android Emulator Skin File Specification:
12 The Android emulator program is capable of displaying a window containing
22 This document specifies how to generate a new skin for the emulator.
23 The emulator also supports dynamically creating the layout section of
33 the emulator to specify them. This will instruct the program to look into
37 For skin-specific files. Without these options, the emulator will look for
89 - 'width': The width of the emulator window in pixels, as an integer
91 - 'height': The height of the emulator window in pixels, as an integer
93 - 'color' : Background color to be used to fill the emulator window.
98 the emulator switches/initializes this layout. This is used t
[all...] |
| ANDROID-ELFF.TXT | 4 by the emulator to extract debugging information from symbol files of the
7 The ELFF library has been introduced to provide the emulator's memory checker
|
| ANDROID-KERNEL.TXT | 1 HOW TO REBUILT THE ANDROID EMULATOR-SPECIFIC KERNEL:
66 emulator -kernel path/to/your/new/zImage <other-options>
73 emulator -kernel path/to/your/new/zImage <other-options> -qemu -cpu cortex-a8
76 the emulator binary will automatically enable ARMv7 emulation for you, so doing
79 emulator -kernel path/to/your/kernel-armv7 <other-options>
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/preferences/ |
| messages.properties | 14 LaunchPreferencePage_Default_Emu_Options=Default emulator options:
|
| /frameworks/base/docs/html/tools/building/ |
| building-eclipse.jd | 11 <li><a href="#RunningOnEmulatorEclipse">Running on an Emulator</a></li>
26 Eclipse invokes ADB and installs your application to a device or emulator, so you do not have to
34 <p>This document shows you how to run your application on an emulator or a real device
39 <h2 id="RunningOnEmulatorEclipse">Running on the emulator</h2>
41 <p>Before you can run your application on the Android Emulator, you must <a href=
54 <li>Install and start the application on an emulator (or device), based on the Deployment
112 <p>The run configuration specifies the project to run, the Activity to start, the emulator or
137 <p>You can specify any emulator options to the Additional Emulator Command Line Options
139 accurate size, based on the dpi of your computer monitor. For a full list of emulator
[all...] |
| /build/target/board/generic_x86/ |
| BoardConfig.mk | 14 # The IA emulator (qemu) uses the Goldfish devices
33 # Build and enable the OpenGL ES View renderer. When running on the emulator,
|
| /development/tools/emulator/test-apps/ConnectivityTest/ |
| AndroidManifest.xml | 17 package="com.android.emulator.connectivity.test"
23 <instrumentation android:targetPackage="com.android.emulator.connectivity.test" android:name="android.test.InstrumentationTestRunner" />
|
| /development/tools/emulator/test-apps/GpsLocationTest/ |
| AndroidManifest.xml | 17 package="com.android.emulator.gps.test"
22 <instrumentation android:targetPackage="com.android.emulator.gps.test"
|
| /device/generic/goldfish/gps/ |
| Android.mk | 16 # We're moving the emulator-specific platform libs to
17 # development.git/tools/emulator/. The following test is to ensure
|
| /docs/source.android.com/src/source/ |
| flashing.jd | 27 <p>To run the emulator, type</p>
28 <pre><code>$ emulator
|
| /external/smali/smali-integration-tests/src/test/smali/junit-tests/ |
| TestSuite.smali | 7 #device/emulator, and then zip up the classes.dex containing this class
8 #and all of the tests and push that to the device/emulator.
|
| /sdk/apps/SdkController/ |
| Implementation.txt | 14 to the emulator and provides a number of "handlers". Handlers can be
20 handler to deal with emulator connections starts/stopping. Some handlers
26 composed of a background handler (that consumes data form the emulator and
27 can send data to the emulator) and an optional activity for UI (that displays
58 The emulator connection is separated in the "lib" subpackage:
59 - EmulatorConnection abstracts a connection to the emulator.
63 - EmulatorListener is a callback: the emulator connection uses it to indicate
69 Emulator
|
| /sdk/apps/SdkController/src/com/android/tools/sdkcontroller/handlers/ |
| MultiTouchChannel.java | 37 * A new frame buffer has been received from the emulator.
42 * A multi-touch "start" command has been received from the emulator.
47 * A multi-touch "stop" command has been received from the emulator. There
77 * counterpart in the emulator.
89 * counterpart in the emulator.
100 * A message has been received from the emulator.
103 * @param msg_data Packet received from the emulator.
122 * A query has been received from the emulator.
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/launch/ |
| ILaunchController.java | 27 * Launches an application on a device or emulator
30 * @param device the device or emulator to launch the application on
|
| /frameworks/base/docs/html/sdk/ |
| OLD_RELEASENOTES.jd | 85 <li>The KML-based mock location provider supported in previous releases is no longer supported. In the current SDK, you can use the emulator console to send GPS fix updates to the emulator and applications running on it. Also, the DDMS tool provides an UI that you can use to easily upload GPX and KML files. DDMS handles playback of the KML or GPX tracks automatically. </li>
145 <li>Launch configuration now has an option to wipe emulator data on launch. This always asks for confirmation.</li>
146 <li>Launch configuration now has an option to disable the boot animation. This will let the emulator start faster on older computers.</li>
157 <p><b>Emulator</b></p>
160 <li>The console port number of a given emulator instance is now displayed in its window's title bar.</li>
161 <li>You can define the console port number used by a given emulator instance.
163 specify which port the emulator should bind to for the console. <port> must be an *even* integer between 5554 and 5584 inclusive. The corresponding ADB port will be <port>+1.</li>
165 <li>Voice/sms are automatically forwarded to other emulator instances running on the same machine, as long as you use their console port number as the destination phone number. For example, if you have two emulators running, the first one will typically use console port 5554, and the second one will use port 5556, dialing 5556 on the first emulator will generate an incoming call on the second emulator. You can also hold/unhold calls. This also w (…)
[all...] |
