HomeSort by relevance Sort by last modified time
    Searched full:launching (Results 251 - 275 of 806) sorted by null

<<11121314151617181920>>

  /platform_testing/tests/jank/uibench_wear/src/com/android/wearable/uibench/janktests/
UiBenchRenderingJankTests.java 109 // Ensuring that we head back to the first screen before launching the app again
  /sdk/eclipse/plugins/com.android.ide.eclipse.ndk/src/com/android/ide/eclipse/ndk/internal/launch/
GdbServerTask.java 77 /** Returns any exceptions that might have occurred while launching gdbserver. */
  /external/chromium-trace/catapult/telemetry/
README.md 12 * Launching a browser with arbitrary flags on any platform.
14 * Launching an Android application with intents through ADB.
  /external/chromium-trace/catapult/third_party/gsutil/third_party/boto/boto/pyami/
launch_ami.py 54 key_name - the name of the keypair to use when launching the AMI
61 The -r option reloads the Python module to S3 without launching
  /external/skia/site/user/quick/
ios.md 104 * Once the build is complete, launching the app will display a window with lots of shaded text examples. On the upper left there is a drop down
112 [Launching Your App on Devices](https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/LaunchingYourApponDevices/LaunchingYourApponDevices.html) for more information.
  /frameworks/base/docs/html-intl/intl/ja/training/basics/activity-lifecycle/
starting.jd 16 <li><a href="#launching-activity">??????????????????????</a></li>
141 <h2 id="launching-activity">????????? ????????????</h2>
  /frameworks/base/docs/html-intl/intl/ko/training/basics/activity-lifecycle/
starting.jd 16 <li><a href="#launching-activity">? ?? ??? ???? ????</a></li>
141 <h2 id="launching-activity">? ?? ??? ???? ????</h2>
  /frameworks/base/docs/html-intl/intl/ru/training/basics/activity-lifecycle/
starting.jd 16 <li><a href="#launching-activity">???????? ????????, ??????????? ??????????</a></li>
141 <h2 id="launching-activity">???????? ????????, ??????????? ??????????</h2>
  /frameworks/base/docs/html-intl/intl/zh-cn/training/basics/activity-lifecycle/
starting.jd 16 <li><a href="#launching-activity">??????????Activity</a></li>
141 <h2 id="launching-activity">??????????Activity</h2>
  /frameworks/base/docs/html-intl/intl/zh-tw/training/basics/activity-lifecycle/
starting.jd 16 <li><a href="#launching-activity">?????????????????</a></li>
141 <h2 id="launching-activity">?????????????????</h2>
  /frameworks/base/services/core/java/com/android/server/am/
ActivityMetricsLogger.java 104 * Notifies the tracker that the activity is actually launching.
145 * Notifies the tracker the the activity is actually launching.
  /packages/services/Telephony/tests/src/com/android/phone/tests/
OtaspTestActivity.java 141 // we get re-started after launching the PERFORM_CDMA_PROVISIONING
155 // it ends by directly launching the Home activity.
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/launch/junit/
AndroidJUnitLaunchAction.java 36 import org.eclipse.jdt.launching.IVMRunner;
37 import org.eclipse.jdt.launching.VMRunnerConfiguration;
  /prebuilts/tools/common/m2/repository/org/eclipse/tycho/extras/tycho-p2-extras-plugin/0.18.1/
tycho-p2-extras-plugin-0.18.1.jar 
  /frameworks/base/packages/SystemUI/src/com/android/systemui/recents/views/
RecentsTransitionHelper.java 121 // If we are launching into another task, cancel the previous task's
140 // If we are launching into another task, cancel the previous task's
195 * @param taskView this is the {@link TaskView} that we are launching from. This can be null if
  /prebuilts/eclipse/mavenplugins/tycho/tycho-dependencies-m2repo/org/eclipse/tycho/tycho-p2-director-plugin/0.20.0/
tycho-p2-director-plugin-0.20.0.jar 
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/launch/
AndroidLaunchController.java 70 import org.eclipse.jdt.launching.IJavaLaunchConfigurationConstants;
71 import org.eclipse.jdt.launching.IVMConnector;
72 import org.eclipse.jdt.launching.JavaRuntime;
286 * @param project The project we're launching
351 * The UI must show which devices are compatibles, and allow launching new emulators
424 "Automatic Target Mode: Preferred AVD '%1$s' is not available. Launching new emulator.",
514 "Automatic Target Mode: launching new emulator with compatible AVD '%1$s'",
552 "Launching new emulator with compatible AVD '%1$s'",
    [all...]
  /cts/tests/tests/content/src/android/content/cts/
ContentQueryMapTest.java 226 }//wait the listener to be ready before launching onChange event
255 }//wait the listener to be ready before launching onChange event
  /docs/source.android.com/src/devices/graphics/
automate-tests.jd 63 <p>The command line Test Executor is a portable C++ tool for launching a test run
133 directory with the <code>python ?m SimpleHTTPServer 8000</code> command. After launching the server, just point the Chrome browser to <code>http://localhost:8000</code> to view the test log.</p>
  /external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/share/
JDWPUnitDebuggeeProcessWrapper.java 139 * if error occurred in launching process
159 * if error occurred in launching process
  /external/autotest/site_utils/
brillo_test_launcher.py 46 """An error while launching and running a test."""
97 @returns The adb host to use for launching tests.
  /external/google-breakpad/src/testing/gtest/include/gtest/
gtest-death-test.h 148 // death test, which already incurs significant overhead by launching
156 // when launching the sub-process. This means that the user must
  /external/gtest/include/gtest/
gtest-death-test.h 148 // death test, which already incurs significant overhead by launching
156 // when launching the sub-process. This means that the user must
  /external/llvm/utils/unittest/googletest/include/gtest/
gtest-death-test.h 137 // death test, which already incurs significant overhead by launching
145 // when launching the sub-process. This means that the user must
  /external/mesa3d/src/gtest/include/gtest/
gtest-death-test.h 137 // death test, which already incurs significant overhead by launching
145 // when launching the sub-process. This means that the user must

Completed in 1196 milliseconds

<<11121314151617181920>>