| /external/valgrind/coregrind/m_syswrap/ |
| syscall-amd64-darwin.S | 49 interactions.
|
| syscall-amd64-linux.S | 49 interactions.
|
| syscall-mips32-linux.S | 49 interactions.
|
| syscall-x86-darwin.S | 49 interactions.
|
| /external/valgrind/gdbserver_tests/ |
| README_DEVELOPERS | 94 This also help to avoid interactions between two successive tests:
|
| /frameworks/base/core/java/android/service/voice/ |
| VoiceInteractionService.java | 45 * in the background to instigate voice interactions.
|
| VoiceInteractionSession.java | 73 * when done. It can also initiate voice interactions with applications by calling
337 * this point, further interactions with the request will result in
[all...] |
| /frameworks/base/core/java/android/text/style/ |
| SuggestionSpan.java | 53 * Sets this flag if the suggestions should be easily accessible with few interactions.
|
| /frameworks/base/core/java/android/view/ |
| InputFilter.java | 47 * a different sequence of motion events, key presses or other system-level interactions.
|
| /frameworks/base/docs/html/guide/practices/ |
| screens-support-1.5.jd | 121 Observe the way your application looks and runs, and test all of the user interactions.</li>
|
| /frameworks/base/docs/html/training/activity-testing/ |
| activity-ui-testing.jd | 182 helper class provides convenience methods for simulating touch interactions
|
| /frameworks/base/docs/html/training/app-indexing/ |
| deep-linking.jd | 115 It is okay to prompt users on subsequent interactions or when they open the app
|
| /frameworks/base/docs/html/training/design-navigation/ |
| multiple-sizes.jd | 53 <p>In addition to addressing these user expectations, it's usually necessary to provide multiple panes of information on tablets to avoid leaving too much whitespace or unwittingly introducing awkward interactions, for example 10 x 0.5-inch buttons.</p>
|
| /frameworks/base/test-runner/src/android/test/ |
| ActivityUnitTestCase.java | 42 * normal system and will not participate in the normal interactions with other Activities.
|
| /frameworks/native/include/gui/ |
| Surface.h | 209 // interactions with the server using this interface.
|
| /frameworks/support/v4/java/android/support/v4/view/accessibility/ |
| AccessibilityWindowInfoCompat.java | 222 * user interactions without changing the windows an accessibility service
|
| /packages/apps/Contacts/src/com/android/contacts/activities/ |
| ContactEditorBaseActivity.java | 29 import com.android.contacts.interactions.ContactDeletionInteraction;
|
| /packages/apps/Contacts/src/com/android/contacts/interactions/ |
| ContactDeletionInteraction.java | 17 package com.android.contacts.interactions;
|
| /packages/apps/Contacts/src/com/android/contacts/quickcontact/ |
| QuickContactActivity.java | 100 import com.android.contacts.common.interactions.TouchPointManager;
132 import com.android.contacts.interactions.CalendarInteractionsLoader;
133 import com.android.contacts.interactions.CallLogInteractionsLoader;
134 import com.android.contacts.interactions.ContactDeletionInteraction;
135 import com.android.contacts.interactions.ContactInteraction;
136 import com.android.contacts.interactions.SmsInteractionsLoader;
[all...] |
| /packages/apps/ContactsCommon/src/com/android/contacts/common/interactions/ |
| ImportExportDialogFragment.java | 17 package com.android.contacts.common.interactions;
|
| /packages/apps/Exchange/src/com/android/exchange/eas/ |
| EasProvision.java | 41 * Provisioning actually consists of two server interactions:
|
| /frameworks/base/core/java/android/app/admin/ |
| DeviceAdminReceiver.java | 426 * <p> Note that provisioning completes without waiting for any server interactions, so the
428 * other data that is set as a result of server interactions).
|
| /frameworks/base/core/java/android/widget/ |
| ZoomButtonsController.java | 292 * focusable, then trackball and arrow key interactions are possible.
293 * Otherwise, only touch interactions are possible.
|
| /frameworks/base/docs/html/about/versions/ |
| lollipop.jd | 113 <p>With Android TV you can now <strong>create big, bold experiences</strong> for your app or game content and support interactions with game controllers and other input devices. To help you build cinematic, 10-foot UIs for television, Android provides a <strong>leanback UI framework</strong> in the <a href="{@docRoot}tools/support-library/features.html#v17-leanback">v17 support library</a>.</p>
223 <p>New <strong>interaction composite sensors</strong> are now available to detect special interactions such as a <em>wake up</em> gesture, a <em>pick up</em> gesture, and a <em>glance</em> gesture.</p>
|
| /frameworks/base/docs/html/design/wear/ |
| watchfaces.jd | 310 consistent system interactions, and for making watch face interactions as simple as
|
