| /frameworks/base/packages/SystemUI/src/com/android/systemui/recent/ |
| RecentsPanelView.java | 636 public void onTasksLoaded(ArrayList<TaskDescription> tasks, boolean firstScreenful) {
638 mRecentTaskDescriptions = new ArrayList<TaskDescription>(tasks);
640 mRecentTaskDescriptions.addAll(tasks);
[all...] |
| /packages/apps/Nfc/src/com/android/nfc/ |
| P2pLinkManager.java | 401 List<RunningTaskInfo> tasks = mActivityManager.getRunningTasks(1); local
402 if (tasks.size() > 0) {
403 runningPackage = tasks.get(0).topActivity.getPackageName();
[all...] |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/ |
| build-hardy-toolchain.sh | 811 # Variant of task define for dual tasks
812 # This really defines two tasks named '<task>_1' and '<task>_2"
856 # $2+: other tasks this task depends on.
865 # $2+: other non-dual tasks this dual task depends on
875 # $2+: other dual tasks this dual task depends on
[all...] |
| /frameworks/base/docs/html/google/play/billing/v2/ |
| billing_integrate.jd | 26 implementation tasks, using the sample application as an example.</p>
51 <p>The in-app billing sample application shows you how to perform several tasks that are common to
65 security tasks, such as signature verification.</p>
155 running the sample application involves three tasks:</p>
[all...] |
| /frameworks/base/docs/html/guide/components/ |
| activities.jd | 44 <li><a href="{@docRoot}guide/components/tasks-and-back-stack.html">Tasks and Back
68 discussed more in the <a href="{@docRoot}guide/components/tasks-and-back-stack.html">Tasks
[all...] |
| /external/chromium/chrome/browser/extensions/ |
| extension_file_browser_private_api.cc | 141 // Given the list of selected files, returns array of context menu tasks
156 // If there is nothing to do for one file, the intersection of tasks for all
421 // TODO(zelidrag, serya): Add intent content tasks to result_list once we
[all...] |
| /external/chromium/chrome/browser/sync/engine/ |
| syncer_thread2_unittest.cc | 624 // Test nudges / polls don't run in config mode and config tasks do.
644 // TODO(tim): This will fail once CONFIGURATION tasks are implemented. Update
[all...] |
| /external/llvm/docs/ |
| HowToReleaseLLVM.rst | 57 Release Administrative Tasks
60 This section describes a few administrative tasks that need to be done for the
346 Release Final Tasks
|
| /frameworks/base/docs/html/tools/testing/ |
| testing_ui.jd | 58 <p>One common approach to UI testing is to run tests manually and verify that the app is behaving as expected. However, this approach can be time-consuming, tedious, and error-prone. A more efficient and reliable approach is to automate the UI testing with a software testing framework. Automated testing involves creating programs to perform testing tasks (test cases) to cover specific usage scenarios, and then using the testing framework to run the test cases automatically and in a repeatable manner.</p>
123 <p>Before using the {@code uiautomator} testing framework, complete these pre-flight tasks:
162 <p>Once you have completed these prerequisite tasks, you're almost ready to start creating your {@code uiautomator} tests. </li>
|
| /dalvik/vm/compiler/ |
| Utility.cpp | 42 /* Arena-based malloc for compilation tasks */
|
| /development/scripts/app_engine_server/gae_shell/ |
| shell.py | 23 Can be used for system administration tasks, as an interactive way to try out
|
| /docs/source.android.com/src/devices/ |
| audio_avoiding_pi.jd | 306 low-priority tasks and in time-sensitive systems mutexes are more
|
| /docs/source.android.com/src/source/ |
| developing.jd | 64 <p>The task list below shows a summary of how to do common Repo and Git tasks.
|
| /external/bluetooth/bluedroid/include/ |
| gki_target.h | 72 /* The number of GKI tasks in the software system. */
|
| /external/chromium/base/ |
| shared_memory_unittest.cc | 377 #define MAYBE_Tasks Tasks
|
| /external/chromium/chrome/browser/automation/ |
| ui_controls_mac.mm | 25 // into the event queue. (I can post other kinds of tasks but can't
|
| /external/chromium/chrome/browser/chromeos/ |
| proxy_config_service_impl.h | 226 // True if tasks can be posted, which can only happen if constructor has
|
| /external/chromium/chrome/browser/ |
| external_tab_container_win.h | 302 // Allows us to run tasks on the ExternalTabContainer instance which are
|
| /external/chromium/chrome/browser/metrics/ |
| thread_watcher.cc | 351 // The WatchDogThread object must outlive any tasks posted to the IO thread
|
| /external/chromium/chrome/browser/printing/ |
| print_job.cc | 301 // - We don't want to run tasks while the thread is quitting.
|
| /external/chromium/chrome/browser/sync/glue/ |
| data_type_manager_impl.cc | 318 // outstanding tasks.
|
| /external/chromium/chrome/browser/sync/ |
| profile_sync_service_unittest.cc | 101 // operates. It is needed because the SyncBackend can post tasks back to
|
| /external/chromium/chrome/browser/ui/cocoa/ |
| history_menu_bridge.h | 165 // notification receiver. Finishes initialization tasks by subscribing for
|
| /external/chromium/chrome/browser/ui/gtk/tabs/ |
| tab_gtk.cc | 376 // Make sure we only run EndDrag once by canceling any tasks that want
|
| /external/chromium/chrome/browser/ui/views/tab_contents/ |
| tab_contents_drag_win.cc | 304 // We need to enable recursive tasks on the message loop so we can get
|
