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

1 2 3 4 56 7 8 91011>>

  /development/tools/emulator/opengl/
README 37 system/egl -> emulator-specific guest EGL library
38 system/GLESv1 -> emulator-specific guest GLES 1.1 library
39 system/gralloc -> emulator-specific gralloc module
58 or directly linked into the emulator UI program.
  /development/tools/emulator/opengl/system/OpenglSystemCommon/
QemuPipeStream.h 20 * to communicate with the emulator's 'opengles' service. See
  /development/tools/emulator/opengl/system/egl/
Android.mk 25 # Ensure that this file is only copied to emulator-specific builds.
  /development/tools/emulator/opengl/tests/event_injector/
EventInjector.cpp 17 #include "emulator-console.h"
EventInjector.h 39 /* Keycode values expected by the Linux kernel, and the emulator */
emulator-console.h 29 * a given emulator port. Note that this always succeeds since the
  /development/tools/emulator/system/camera/
EmulatedCameraHal.cpp 19 * under the emulator.
  /development/tools/emulator/test-apps/GpsLocationTest/src/com/android/emulator/gps/test/
GpsLocationTest.java 16 package com.android.emulator.gps.test;
  /device/samsung/maguro/
Android.mk 18 # including x86, the emulator, and the SDK. Modules must be uniquely
  /device/ti/panda/
Android.mk 18 # including x86, the emulator, and the SDK. Modules must be uniquely
  /external/android-mock/src/com/google/android/testing/mocking/
UsesMocks.java 27 * added to the APK uploaded to the device/emulator).
  /external/qemu/android/
core-init-utils.h 15 * of the emulator's core initialization.
hw-control.h 22 * default is around 105, and we probably don't want to dim the emulator's
keycode-array.h 16 * to be transferred to the emulator core for further processing.
  /external/qemu/android/protocol/
ui-commands-api.h 20 /* Changes the scale of the emulator window at runtime.
ui-commands-proxy.h 33 /* Changes the scale of the emulator window at runtime.
ui-commands-qemu.c 15 * control commands for standalone (monolithic) emulator.
  /external/qemu/
cpus.h 2 * QEMU System Emulator
  /external/qemu/docs/
ANDROID-FRAMEBUFFER.TXT 5 Android emulator.
22 the emulated system, but not in the emulator's process space which
38 - holds a contiguous pixel buffer allocated by the emulator.
43 The emulator will periodically call 'qframebuffer_check_updates()' which
  /external/quake/
cleanupdevicesdcard.sh 4 # Based on emulator.sh
  /frameworks/base/docs/html/guide/developing/devices/
index.jd 5 <p>An Android Virtual Device (AVD) is an emulator configuration that lets you model an actual
6 device by defining hardware and software options to be emulated by the Android Emulator.</p>
30 <li>Other options: You can specify the emulator skin you want to use with the AVD, which lets
63 library is present. If you want to run your application on an emulator, create an AVD that
  /sdk/ddms/libs/ddmlib/src/com/android/ddmlib/
IShellOutputReceiver.java 21 * command on a device/emulator.
  /development/pdk/docs/source/
using-eclipse.jd 20 : You will still be using "make" 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 "make" in a shell. The Eclipse build is just for error checking.
106 <h2><a>Debugging the emulator with Eclipse</a>
108 <p>You can also use eclipse to debug the emulator and step through code. First, start the emulator running:
110 <pre>cd /path/to/android/root <br>. build/envsetup.sh <br>lunch 1 # to build the emulator <br>make # if you didn't already do this <br>emulator # you should see a GUI picture of a phone <br></pre>
114 <p>Now, in eclipse, you can attach to the emulator:
  /docs/source.android.com/src/source/
using-eclipse.md 33 **Important**: You will still be using `make` 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 `make` in a shell. The Eclipse build is just for error checking.
128 ## Debugging the emulator with Eclipse ##
130 You can also use eclipse to debug the emulator and step through code. First, start the emulator running:
136 emulator
138 If the emulator is running, you should see a picture of a phone.
147 Now, in eclipse, you can attach to the emulator:
  /frameworks/base/docs/html/sdk/1.0_r1/
upgrading.jd 20 <li>Wipe your emulator data. <p>Some data formats have changed since the last
21 SDK release, so any previously saved data in your emulator must be removed. Open a console/terminal
23 emulator with the <code>-wipe-data</code> option. </p>
24 <p>Windows: <code>emulator -wipe-data</code><br/>
25 Mac/Linux: <code>./emulator -wipe-data</code></p>
102 <p>All applications must now be signed before you can install them on the emulator. Both
154 preinstalled in the emulator.</p>

Completed in 371 milliseconds

1 2 3 4 56 7 8 91011>>