HomeSort by relevance Sort by last modified time
    Searched full:emulator (Results 151 - 175 of 802) sorted by null

1 2 3 4 5 67 8 91011>>

  /external/qemu/distrib/sdl-1.2.15/
sources.make 1 # This is included from the main Android emulator build script
234 $(call start-emulator-library,emulator_libSDL)
237 $(call end-emulator-library)
242 $(call end-emulator-library)
263 $(call start-emulator-library,emulator_libSDLmain)
267 $(call end-emulator-library)
273 $(call end-emulator-library)
  /sdk/docs/
howto_use_cupcake_sdk.txt 11 5- Targets, AVDs, Emulator changes
146 Please see step 5 "Emulator changes" below for important details on how to run
147 the emulator.
194 Please see paragraph 5 below for important details on how to run the emulator
200 5- Targets, AVDs, Emulator changes
205 One major change with the emulator is that now you must pre-create an "Android
206 Virtual Device" (a.k.a "AVD") before you run the emulator.
215 $ SDK/tools/emulator -help-virtual-device
221 There is a lot more explanation given by the emulator. Please run the help
224 The bottom line is that you can create many emulator configurations, or "AVDs"
    [all...]
  /external/qemu/docs/
ANDROID-QEMU-PIPE.TXT 7 The Android emulator implements a special virtual device used to provide
9 emulator itself.
33 Where <pipename> is the name of a specific emulator service you want to use.
40 In the emulator source tree:
45 implemented by any emulator pipe service.
83 The channel value sent from the kernel to the emulator with:
92 Similarly, when passing a kernel address to the emulator:
294 pass-through that doesn't depend on the very slow internal emulator
313 Connects to the QEMUD service inside the emulator. This replaces the
  /frameworks/base/docs/html/training/wearables/apps/
creating.jd 12 <li><a href="#SetupEmulator">Set Up an Android Wear Emulator</a></li>
36 <p>This lesson goes over how to set up a device or emulator and create one project to contain
59 <h2 id="SetupEmulator">Set Up an Android Wear Emulator or Device</h2>
61 gauge the user experience. However, the emulator lets you test out different
79 <li>Start the emulator:
83 <li>Wait until the emulator initializes and shows the Android Wear home screen.</li>
86 <li>Pair your handheld with the emulator:
94 <li>Start the Android Wear app on your handheld device and connect to the emulator.</li>
97 <li>The cards you select appear as notifications on the home screen of the emulator.</li>
  /device/generic/goldfish/camera/
EmulatedCameraFactory.h 38 * emulator's 'camera' service. For every camera found out there it creates an
40 * cameras. In addition to the cameras reported by the emulator, a fake camera
41 * emulator is always created, so there is always at least one camera that is
141 * 'camera' service in the emulator. For each such camera and instance of
164 /* Connection to the camera service in the emulator. */
  /sdk/emulator/opengl/
README 3 $ANDROID_BUILD_TOP/development/tools/emulator/opengl.
27 system/egl -> emulator-specific guest EGL library
28 system/GLESv1 -> emulator-specific guest GLES 1.1 library
29 system/gralloc -> emulator-specific gralloc module
48 or directly linked into the emulator UI program.
DESIGN 36 into a custom wire protocol stream that is sent to the emulator program
61 EMULATOR
63 - Specific code inside the emulator program that is capable of transmitting
71 | EMULATOR |
130 | EMULATOR |
169 1 - The ability to run the renderer in a separate process from the emulator
182 This explains why the emulator doesn't alter or even try to parse the
210 - The emulator sources are under $ANDROID/external/qemu, which we'll
214 $ANDROID/development/tools/emulator/opengl, which we'll call $EMUGL_GUEST
217 $ANDROID/sdk/emulator/opengl, which we'll call $EMUGL_HOS
    [all...]
  /frameworks/base/docs/html/tools/revisions/
platforms.jd 31 Platform for that release. If you want to test your application on an emulator, you must also
208 allowing you to test your application in an emulator using the latest Google Play services.</p>
223 allowing you to test your application in an emulator using the latest Google Play services.</p>
512 <h3>Emulator Skins</h3>
514 <p>The downloadable platform includes the following emulator skins:</p>
549 <p>To test your application on an emulator that represents the <a
552 href="{@docRoot}tools/devices/emulator.html#accel-graphics">graphics acceleration</a> in the
553 emulator configuration.</p>
581 <p class="note"><strong>Note:</strong> This system image includes support for emulator
583 (<a href="{@docRoot}tools/devices/emulator.html#accel-graphics">more info</a>)</p
    [all...]
  /bootable/recovery/
verifier_test.sh 20 emulator -wipe-data -noaudio -no-window -port $EMULATOR_PORT &
22 ADB="adb -s emulator-$EMULATOR_PORT "
53 # not necessary if we're about to kill the emulator, but nice for
  /build/target/board/generic/
BoardConfig.mk 13 # Technically, the emulator supports ARMv7-A _and_ NEON instructions, but
20 # application code generated with the NDK that uses NEON in the emulator.
44 # Build and enable the OpenGL ES View renderer. When running on the emulator,
  /docs/source.android.com/src/devices/tech/test_infra/tradefed/fundamentals/
devices.jd 44 <h3>Emulator</h3>
46 Emulator, specify the <code>--emulator</code> argument for the command. See
  /external/qemu/android/utils/
debug.h 22 _VERBOSE_TAG(init, "emulator initialization") \
44 _VERBOSE_TAG(sensors_port, "sensors emulator connected to android device") \
45 _VERBOSE_TAG(mtport, "multi-touch emulator connected to android device") \
  /frameworks/base/docs/html/tools/debugging/
debugging-devtools.jd 7 so you can use it with the Android Emulator. With the Dev Tools application, you can enable a
66 restarting the emulator.</p></dd>
74 <p>These settings will be remembered across emulator restarts.</p>
  /hardware/libhardware/include/hardware/
qemu_pipe.h 34 * emulator.
38 * 'pipeName' is the name of the emulator service you want to connect to.
48 * misconfigured emulator.
  /development/scripts/
combine_sdks.sh 32 echo " emulator and other runtime files will be copied from IMAGES and"
67 # replace tools/emulator # at this time we do not want the exe from SDK1.x
  /device/generic/mini-emulator-arm64/
mini_emulator_common.mk 40 device/generic/mini-emulator-armv7-a-neon/init.mini-emulator.rc:root/init.goldfish.rc \
  /device/generic/mini-emulator-armv7-a-neon/
mini_emulator_common.mk 40 device/generic/mini-emulator-armv7-a-neon/init.mini-emulator.rc:root/init.goldfish.rc \
  /docs/source.android.com/src/source/
using-eclipse.jd 36 <p><strong>Important</strong>: You will still be using <code>make</code> to build the files you will actually run (in the emulator or on a device). You will be using Eclipse to edit files and verify that they compile, but when you want to run something you will need to make sure files are saved in Eclipse and run <code>make</code> in a shell. The Eclipse build is just for error checking.</p>
137 <h2 id="debugging-the-emulator-with-eclipse">Debugging the emulator with Eclipse</h2>
138 <p>You can also use eclipse to debug the emulator and step through code. First, start the emulator running:</p>
143 emulator
145 <p>If the emulator is running, you should see a picture of a phone.</p>
151 <p>Now, in eclipse, you can attach to the emulator:</p>
  /external/strace/qemu_multiarch_testing/
README 29 system-image-i686 (had to s/qemu-system-i386/qemu/ in run-emulator.sh)
46 system-image-m68k - run-emulator.sh has no call of qemu-system-* (not supported yet??)
  /frameworks/base/docs/html/tools/building/
index.jd 22 of the information necessary to run your application on a device or emulator, such as compiled
27 <p>To run an application on an emulator or device, the application must be signed using debug or
  /frameworks/base/docs/html/tools/help/
sqlite3.jd 24 Emulator/device instances store SQLite3 databases in the directory
35 <pre>$ adb -s emulator-5554 shell
  /frameworks/base/docs/html/tools/testing/
testing_eclipse.jd 48 necessary to your device or emulator, runs the test package, and displays the
257 device to your computer or use the Android emulator. If you use the emulator, you must have an
302 Optional: If you are using the emulator, click Automatic, then in the Android
306 In the Emulator Launch Parameters pane, set the Android emulator flags you want to
308 <a href="{@docRoot}tools/help/emulator.html#startup-options">
309 Android Emulator</a>.
343 this message appears when you run a test to the emulator, and the emulator is not yet started
    [all...]
  /sdk/files/
alias_rules.xml 47 <!-- Create the package and install package on the default emulator -->
49 <echo>Sending package to default emulator...</echo>
  /system/core/adb/
transport_local.c 147 /* try to connect to any number of running emulator instances */
148 /* this is only done when ADB starts up. later, each new emulator */
191 /* This is relevant only for ADB daemon running inside the emulator. */
209 * condition that adbd daemon runs inside the emulator, and emulator uses QEMUD
218 * implements the emulator's side of the protocol. Another advantage of using
223 * is opened, and it becomes clear whether or not emulator supports that
231 * Note that the guest will ignore messages sent down from the emulator before
257 /* This could be an older version of the emulator, that doesn't
314 * between the device, and the emulator. *
    [all...]
  /bootable/recovery/applypatch/
imgdiff_test.sh 7 # emulator) and checks that the resulting file is correct.
25 emulator -wipe-data -noaudio -no-window -port $EMULATOR_PORT &
27 ADB="adb -s emulator-$EMULATOR_PORT "
65 # not necessary if we're about to kill the emulator, but nice for

Completed in 1017 milliseconds

1 2 3 4 5 67 8 91011>>