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

1 2 34 5 6 7 8 91011>>

  /development/build/
sdk.atree 75 # emulator skins from sdk.git
76 development/tools/emulator/skins/QVGA platforms/${PLATFORM_NAME}/skins/QVGA
77 development/tools/emulator/skins/WQVGA432 platforms/${PLATFORM_NAME}/skins/WQVGA432
78 development/tools/emulator/skins/WQVGA400 platforms/${PLATFORM_NAME}/skins/WQVGA400
79 development/tools/emulator/skins/HVGA platforms/${PLATFORM_NAME}/skins/HVGA
80 development/tools/emulator/skins/WVGA800 platforms/${PLATFORM_NAME}/skins/WVGA800
81 development/tools/emulator/skins/WVGA854 platforms/${PLATFORM_NAME}/skins/WVGA854
82 development/tools/emulator/skins/WSVGA platforms/${PLATFORM_NAME}/skins/WSVGA
83 development/tools/emulator/skins/WXGA720 platforms/${PLATFORM_NAME}/skins/WXGA720
84 development/tools/emulator/skins/WXGA800 platforms/${PLATFORM_NAME}/skins/WXGA80
    [all...]
  /external/qemu/android/
android.h 56 /* default network settings for emulator */
60 /* enable/disable interrupt polling mode. the emulator will always use 100%
88 /* this is the port used for the control console in this emulator instance.
  /external/qemu/android/utils/
debug.c 22 fprintf( stdout, "emulator: ");
49 dprintn( "emulator: WARNING: " );
61 dprintn( "emulator: ERROR: " );
  /external/qemu/docs/
ANDROID-SKIN-FILES.TXT 1 Android Emulator Skin File Specification:
10 The Android emulator program is capable of displaying a window containing
20 This document specifies how to generate a new skin for the emulator.
28 the emulator to specify them. This will instruct the program to look into
32 For skin-specific files. Without these options, the emulator will look for
84 - 'width': The width of the emulator window in pixels, as an integer
86 - 'height': The height of the emulator window in pixels, as an integer
88 - 'color' : Background color to be used to fill the emulator window.
93 the emulator switches/initializes this layout. This is used to
103 codes. You can use the following emulator console commands t
    [all...]
  /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.
  /system/core/libcutils/
process_name.c 55 // If we know we are not running in the emulator, then return.
72 // If the emulator was started with the "-trace file" command line option
76 // this code if we are just running in the emulator without the "-trace"
  /system/core/rootdir/
Android.mk 18 # the /system/etc/init.goldfish.sh is needed to enable emulator support
21 # to run the dex pre-optimization *in* the emulator. So keep the file until
55 # the emulator.
  /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
57 $(call start-emulator-library, emulator-common)
134 $(call end-emulator-library)
139 ### emulator-libui: LIBRARY OF UI-RELATED FUNCTIONS
141 ### THESE ARE USED BY 'emulator-ui' AND THE STANDALONE PROGRAM
    [all...]
  /external/qemu/memcheck/
memcheck_common.h 32 /* Notifies the emulator that libc has been initialized for a process.
38 /* Notifies the emulator about new memory block being allocated.
41 * of the descriptor is used by emulator to report failure in handling this
42 * event. In case of failure emulator will zero that filed before completing
47 /* Notifies the emulator about memory block being freed.
50 * freed. Note that 'libc_pid' field of the descriptor is used by emulator to
51 * report failure in handling this event. In case of failure emulator will zero
56 /* Queries the emulator about memory block information.
59 * field of the descriptor is used by emulator to report failure in handling
60 * this event. In case of failure emulator will zero that filed befor
    [all...]
  /frameworks/base/docs/html/resources/faq/
troubleshooting.jd 12 <li><a href="#nodevice">ADB reports &quot;no device&quot; when an emulator is running</a></li>
23 <li><a href="#eclipse">Eclipse isn't talking to the emulator</a></li>
27 app in the emulator</a></li>
69 <a name="nodevice"></a><h2>ADB reports &quot;no device&quot; when an emulator is running</h2>
76 <li>You often must restart your device or emulator before a new activity shows
134 the emulator not being started, not being able to run the application, or even seeming to run an old version of the application.</p>
167 <a name="eclipse"></a><h2>Eclipse isn't talking to the emulator</h2>
168 <p>When communication doesn't seem to be happening between Eclipse and the emulator, symptoms can include: nothing happening when you press run, the emulator hanging waiting
170 to find the emulator or shell. By far the most common symptom is that when you press run, the emulator starts (o
    [all...]
  /build/target/board/generic_x86/
BoardConfig.mk 14 # The IA emulator (qemu) uses the Goldfish devices
  /external/quake/
setupdevicesdcard.sh 4 # Based on emulator.sh
  /frameworks/base/data/keyboards/
qwerty.idc 16 # Emulator keyboard configuration file #1.
qwerty2.idc 16 # Emulator keyboard configuration file #2.
  /frameworks/base/docs/html/guide/developing/debugging/
debugging-projects-cmdline.jd 44 <li>Load an AVD with the Android emulator or connect a device to your computer.</li>
49 <li>Install and run your <code>.apk</code> file on the device or emulator. In DDMS, you should see your
59 emulator. You must either attach your IDE to that port (listed on the Info tab for that VM), or
63 <p>Your IDE should attach to your application running on the emulator, showing you its threads
  /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/
plugin.properties 10 view.name.Emulator_Control = Emulator Control
  /system/core/rootdir/etc/
vold.fstab 15 ## Example of a standard sdcard mount for the emulator / Dream
init.goldfish.sh 15 # device by the emulator.
60 # set up the second interface (for inter-emulator connections)
  /cts/tests/tests/app/src/android/app/cts/
KeyguardManagerTest.java 53 notes = "There is no method to enable the key guard in the emulator",
62 notes = "There is no method to enable the key guard in the emulator",
  /external/qemu/telephony/
remote_call.h 37 * this will try to connect to a remote emulator. the result function
47 /* call this function to send a SMS to a remote emulator */
  /frameworks/base/docs/html/intl/ja/guide/developing/
other-ide.jd 23 <li><a href="{@docRoot}guide/developing/tools/emulator.html">Android Emulator</a></li>
41 <dt><a href="{@docRoot}guide/developing/tools/emulator.html">Android Emulator</a></dt>
235 <pre>emulator -avd <em>&lt;your_avd_name&gt;</em></pre>
243 <pre>adb -s emulator-5554 install /my/project/path/myapp.apk</pre>
257 <li><a href="{@docRoot}guide/developing/tools/emulator.html">Android Emulator</a></li>
  /cts/tests/tests/view/src/android/view/cts/
OrientationListenerTest.java 69 + "to simulate sensor events on the emulator",
78 + "to simulate sensor events on the emulator",
83 @ToBeFixed(explanation = "Can not simulate sensor events on the emulator.")
135 + "because there is no way to simulate the sensor events on the emulator.",
139 @ToBeFixed(explanation = "Can not simulate sensor events on the emulator.")
143 // TODO can not simulate sensor events on the emulator.
  /external/opencv/
README.rdoc 13 For those of you running on the emulator, I built a very simple Socket-based Camera server that will send images over a socket connection. This uses the QuickTime libraries which are present by default on Mac OS X, but I haven't tested on other OSes. If it doesn't work for you, you can always try the original WebcamBroadcaster I derived mine from which uses the JMF (which doesn't work with Mac OS X, hence the QTWebcamBroadcaster):
44 Before attempting to run the VideoEmulator application, you must first copy this XML file into the emulator in the following location:
51 In order to use the VideoEmulator, you have to use the emulator (hence the name.) If you have a Dev Phone, you can play around with the old 'OpenCVSample' test or modify the VideoEmulator to support a real camera. This is something we will work on resolving in the future.
53 Using the emulator there are two slightly different 'flavors' of running. Both are socket based cameras, but one is written in C++ and emulates a real OpenCV Capture while the other (loosely) emulates a camera implementation in Java. The C++ version is the default as it is slightly faster and takes a little less memory. Also, the ultimate goal is to hook up with a real camera in C++ so that we don't have to pass huge amounts of data (images) back and forth through the JNI interface.
55 <b>NOTE:</b> For all of these examples you cannot use localhost or 127.0.0.1 as your address for the socket camera. The reason is because when the client is running on the Android emulator, both of these map to Android's localhost, not the machine you are running the emulator on. This means you have to be connected to a network in order to use the socket camera, a limitation.
  /frameworks/base/docs/html/guide/topics/testing/
what_to_test.jd 80 You can use the emulator to test network access and bandwidth. To learn more, please see
81 <a href="{@docRoot}guide/developing/tools/emulator.html#netspeed">Network Speed Emulation</a>.
82 To test GPS, you can use the emulator console and {@link android.location.LocationManager}. To
83 learn more about the emulator console, please see
84 <a href="{@docRoot}guide/developing/tools/emulator.html#console">
85 Using the Emulator Console</a>.
  /system/core/adb/
OVERVIEW.TXT 20 as well as when emulator instances start/stop.
40 meaning that the ADB server detected a new device/emulator, but could not
115 where '<serialnumber>' is used to identify a given device/emulator; after
125 or emulator. There are currently two kinds of transports:
133 a connection between an ADB server and a device/emulator connected to/
137 and the device/emulator they point to. The ADB server must handle

Completed in 650 milliseconds

1 2 34 5 6 7 8 91011>>