HomeSort by relevance Sort by last modified time
    Searched full:emulator (Results 26 - 50 of 587) sorted by null

12 3 4 5 6 7 8 91011>>

  /frameworks/base/docs/html/guide/developing/tools/
mksdcard.jd 7 emulator, to simulate the presence of an SD card in the device. Because you can specify an SD
47 <p>Once you have created the disk image file, you can load it in the emulator at startup using
48 the emulator's <code>-sdcard</code> option. For more information, see <a href=
49 "{@docRoot}guide/developing/tools/emulator.html">Android Emulator</a>.</p>
52 <pre>emulator -sdcard &lt;file&gt;</pre>
adb.jd 10 <li>Manage the state of an emulator or device</li>
12 <li>Manage port forwarding on an emulator or device</li>
13 <li>Copy files to/from an emulator or device</li>
19 <li><a href="#devicestatus">Querying for Emulator/Device Instances</a></li>
20 <li><a href="#directingcommands">Directing Commands to a Specific Emulator/Device Instance</a></li>
23 <li><a href="#copyfiles">Copying Files to or from an Emulator/Device Instance</a></li>
32 <li><a href="emulator.html">Emulator</a></li>
39 emulator instance or connected Android-powered device. It is a client-server program that includes
44 <li>A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device. </li
    [all...]
emulator.jd 1 page.title=Android Emulator
11 <li><a href="#startup-options">Emulator Startup Options</a></li>
12 <li><a href="#KeyMapping">Emulator Keyboard Mapping</a></li>
17 <li><a href="{@docRoot}guide/developing/devices/emulator.html">Using the Android Emulator</a></li>
25 <p>The Android SDK includes a mobile device emulator &mdash; a virtual mobile device
26 that runs on your computer. The emulator lets you develop and test
29 <p>When the emulator is running, you can interact with the emulated mobile
35 For a complete guide to using the Android Emulator, see
36 <a href="{@docRoot}guide/developing/devices/emulator.html">Using the Android Emulator</a>
    [all...]
index.jd 15 include the Android SDK and AVD Manager (<code>android</code>), the emulator
16 (<code>emulator</code>), and the Dalvik Debug Monitor Server
35 <dt><a href="emulator.html">Android Emulator (emulator)</a></dt>
47 <dd>Helps you create a disk image that you can use with the emulator, to simulate the presence
50 <dd>Runs on your emulator or device and generates pseudo-random streams of user events such
54 <dd>Provides an API for writing programs that control an Android device or emulator from
74 Android Debug Bridge is a versatile tool that lets you manage the state of an emulator instance or
  /external/qemu/distrib/
README 1 This is source release of the Android emulator. simply run the "build-emulator.sh" script to
2 generate a statically linked "emulator" binary in the current directory.
8 This emulator is probably not usable without other support files provided by the Android project,
12 This emulator is licensed under the GNU General Public License (GPL) version 2, which can be
23 emulator to generate "profile" files that can later be analyzed with external tools
48 - new APIs: SDL_WM_GetPos() and SDL_WM_SetPos() are used to retrieve and set the emulator
49 window position. this allows us to implement a simple-yet-useful feature: the emulator remembers
  /system/core/adb/
console.c 13 fprintf(stderr, "error: more than one emulator detected. use -s option\n");
15 fprintf(stderr, "error: no emulator detected\n");
SERVICES.TXT 33 host:emulator:<port>
35 new emulator starts up. <port> is a decimal number corresponding
36 to the emulator's ADB control port, i.e. the TCP port that the
37 emulator will forward automatically to the adbd daemon running
38 in the emulator system.
40 This mechanism allows the ADB server to know when new emulator
44 Ask to switch the connection to the device/emulator identified by
55 Ask to switch the connection to one emulator connected through TCP.
56 This will fail if there is more than one such emulator instance
61 either the device or emulator connect to/running on the host
    [all...]
  /external/qemu/
Makefile.target 2 # modules for the Android emulator. It will be called several times
18 ### emulator-target-$CPU: target-specific emulation code.
45 $(call start-emulator-library, emulator-target-$(EMULATOR_TARGET_CPU))
227 $(call end-emulator-library)
232 ### qemu-android-$CPU: headless emulator core program
235 $(call start-emulator-program, qemu-android-$(EMULATOR_TARGET_ARCH))
248 emulator-libqemu \
249 emulator-target-$(EMULATOR_TARGET_CPU) \
250 emulator-libelff
    [all...]
  /build/target/board/vbox_x86/
init.vbox_x86.rc 15 # disable some daemons the emulator doesn't want
19 setprop ro.setupwizard.mode EMULATOR
25 # For the emulator, which bypasses Setup Wizard, you can specify
46 # program to check wether it runs on the emulator
  /external/bluetooth/bluez/test/
hciemu.1 3 hciemu \- HCI emulator
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/preferences/
messages.properties 10 LaunchPreferencePage_Default_Emu_Options=Default emulator options:
  /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...]
  /external/qemu/android/utils/
filelock.h 18 ** a FileLock is useful to prevent several emulator instances from using the same
22 ** NULL only if the corresponding path is already locked by another emulator
26 ** function can detect stale file locks that can longer when the emulator
  /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.
147 #define PIPE_CMD_WRITE_BUFFER 4 /* send a user buffer to the emulator */
148 #define PIPE_CMD_WAKE_ON_WRITE 5 /* tell the emulator to wake us when writing is possible */
155 #define PIPE_CMD_READ_BUFFER 6 /* receive a page-contained buffer from the emulator */
156 #define PIPE_CMD_WAKE_ON_READ 7 /* tell the emulator to wake us when reading is possible */
164 /* Bit-flags used to signal events from the emulator */
    [all...]
  /external/qemu/memcheck/
memcheck_util.h 29 // Transfering data between guest and emulator address spaces.
33 * in the emulator's address space.
36 * qemu_address - Address of the bufer in the emulator's address space.
43 /* Copies buffer residing in the emulator's address space to a buffer in the
46 * qemu_address - Address of the bufer in the emulator's address space.
55 * to a string buffer in emulator's address space.
57 * qemu_str - Address of the string bufer in the emulator's address space.
59 * qemu_buffer_size - Size of the emulator's string buffer.
68 * to a string buffer in emulator's address space.
70 * qemu_str - Address of the string bufer in the emulator's address space
    [all...]
  /bionic/libc/bionic/
malloc_debug_qemu.c 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/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>/sdk/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)
137 D("Found target-specific emulator binary: %s\n", emulatorPath);
150 D("Quoted emulator binary path: %s\n", emulatorPath);
177 /* Find the target-specific emulator binary. This will be something
178 * like <programDir>/emulator-<targetArch>, where <programDir> i
    [all...]
  /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
44 PRODUCT_MODEL := Full Android on x86 Emulator
  /sdk/screenshot/src/com/android/screenshot/
Screenshot.java 40 boolean emulator = false;
55 if (emulator || serial != null) {
63 emulator = true;
70 if (device || emulator) {
145 if (emulator || device) {
147 // this test works because emulator and device can't both be true at the same
149 if (d.isEmulator() == emulator) {
152 if (emulator) {
153 printAndExit("Error: more than one emulator launched!",
171 printAndExit("Error: more than one emulator or device available!"
    [all...]
  /external/quake/
setupdevice.sh 4 # Based on emulator.sh
  /sdk/emulator/tests/
Android.mk 1 # This directory contains various host tests to be used with the emulator
  /system/core/rootdir/etc/
init.goldfish.rc 22 # disable some daemons the emulator doesn't want
31 setprop ro.setupwizard.mode EMULATOR
37 # For the emulator, which bypasses Setup Wizard, you can specify
72 # program to check wether it runs on the emulator
  /frameworks/base/docs/html/guide/developing/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
102 <p>The run configuration specifies the project to run, the Activity to start, the emulator or
127 <p>You can specify any emulator options to the Additional Emulator Command Line Options
129 accurate size, based on the dpi of your computer monitor. For a full list of emulator
    [all...]
  /build/core/
user_tags.mk 114 emulator \
115 emulator-arm \
116 emulator-core \
117 emulator-elff \
118 emulator-hw \
119 emulator-memcheck \
120 emulator-tcg \
121 emulator-ui \

Completed in 769 milliseconds

12 3 4 5 6 7 8 91011>>