| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/launch/ |
| AndroidLaunchController.java | 68 import org.eclipse.jdt.launching.IJavaLaunchConfigurationConstants;
69 import org.eclipse.jdt.launching.IVMConnector;
70 import org.eclipse.jdt.launching.JavaRuntime;
284 * @param project The project we're launching
349 * The UI must show which devices are compatibles, and allow launching new emulators
419 "Automatic Target Mode: Preferred AVD '%1$s' is not available. Launching new emulator.",
509 "Automatic Target Mode: launching new emulator with compatible AVD '%1$s'",
547 "Launching new emulator with compatible AVD '%1$s'",
[all...] |
| /cts/tests/tests/content/src/android/content/cts/ |
| ContentQueryMapTest.java | 220 }//wait the listener to be ready before launching onChange event
249 }//wait the listener to be ready before launching onChange event
|
| /external/chromium/chrome/browser/service/ |
| service_process_control.cc | 112 // If we already in the process of launching, then we are done.
179 // If we don't have process handle that means launching the service process
|
| service_process_control.h | 133 // This class is responsible for launching the service process on the
|
| /external/chromium/chrome/browser/ui/gtk/ |
| content_setting_bubble_gtk.cc | 276 // The views interface implicitly closes because of the launching of a new
285 // The views interface implicitly closes because of the launching of a new
|
| /external/chromium/testing/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
|
| /external/chromium_org/chrome/browser/first_run/ |
| upgrade_util_win.cc | 129 // On Windows 8 we always use the delegate_execute for re-launching chrome.
251 // First try to rename exe by launching rename command ourselves.
|
| /external/chromium_org/chrome/browser/service_process/ |
| service_process_control.cc | 107 // If we already in the process of launching, then we are done.
177 // If we don't have process handle that means launching the service process
|
| /external/chromium_org/chrome/browser/ui/gtk/ |
| content_setting_bubble_gtk.cc | 340 // The views interface implicitly closes because of the launching of a new
349 // The views interface implicitly closes because of the launching of a new
|
| /external/chromium_org/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/chromium_org/third_party/mesa/src/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
|
| /external/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
|
| /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
|
| /external/open-vcdiff/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
|
| /external/protobuf/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
|
| /frameworks/base/core/java/android/test/ |
| InstrumentationTestCase.java | 73 * Utility method for launching an activity.
101 * Utility method for launching an activity with a specific Intent.
|
| /frameworks/base/tests/AppLaunch/src/com/android/tests/applaunch/ |
| AppLaunch.java | 64 private static final int BETWEEN_LAUNCH_SLEEP_TIMEOUT = 2000; //2s between launching apps
337 Log.w(TAG, "Error launching app", e);
|
| /ndk/sources/third_party/googletest/googletest/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
|
| /packages/apps/QuickSearchBox/src/com/android/quicksearchbox/ |
| SearchActivity.java | 66 // True if the user has taken some action, e.g. launching a search, voice search,
410 if (DBG) Log.d(TAG, "Launching suggestion " + id);
|
| /cts/tests/tests/preference2/res/values/ |
| strings.xml | 21 <string name="launching_preferences">Preference/2. Launching preferences</string>
|
| /developers/samples/android/background/alarms/Scheduler/src/com/example/android/scheduler/ |
| SampleAlarmReceiver.java | 44 // Start the service, keeping the device awake while it is launching.
|
| /development/samples/ApiDemos/src/com/example/android/apis/app/ |
| ReceiveResult.java | 33 * Shows how an activity can send data to its launching activity when done.y.
|
| /external/chromium/chrome/browser/ |
| external_protocol_handler.cc | 22 // Whether we accept requests for launching external protocols. This is set to
|
| shell_integration.h | 76 // Set up command line arguments for launching a URL or an app.
|
