/packages/apps/Contacts/src/com/android/contacts/interactions/ |
GroupCreationDialogFragment.java | 16 package com.android.contacts.interactions;
|
GroupDeletionDialogFragment.java | 16 package com.android.contacts.interactions;
|
GroupNameDialogFragment.java | 16 package com.android.contacts.interactions;
|
JoinContactsDialogFragment.java | 17 package com.android.contacts.interactions;
|
TestLoaderManagerBase.java | 17 package com.android.contacts.interactions;
|
SmsInteraction.java | 16 package com.android.contacts.interactions;
|
/packages/apps/Messaging/src/com/android/messaging/ui/ |
SnackBarManager.java | 296 final List<SnackBarInteraction> interactions = snackBar.getInteractions(); local 297 for (final SnackBarInteraction interaction : interactions) { 308 final List<SnackBarInteraction> interactions = snackBar.getInteractions(); local 309 for (final SnackBarInteraction interaction : interactions) {
|
/external/ceres-solver/internal/ceres/ |
dense_sparse_matrix_test.cc | 94 // Try with a not entirely zero vector to verify column interactions, which 123 // Try with a not entirely zero vector to verify column interactions, which
|
/packages/apps/Camera2/src/com/android/camera/async/ |
ConcurrentBufferQueue.java | 32 * interactions.<br> 36 * this enables cleanly shutting down producer-consumer interactions without
|
/packages/apps/Messaging/src/com/android/messaging/ui/conversationlist/ |
ConversationListFragment.java | 386 final List<SnackBarInteraction> interactions = new ArrayList<SnackBarInteraction>(1); local 389 interactions.add(fabInteraction); 390 return interactions;
|
/cts/suite/cts/hostTests/jank/app/src/com/android/cts/jank/opengl/ |
CtsDeviceJankOpenGl.java | 92 // This is where user interactions would go, in this case just sleep
|
/development/samples/ApiDemos/src/com/example/android/apis/app/ |
ActionBarTabs.java | 82 * the interactions between different tabs.
|
LocalService.java | 92 // This is the object that receives interactions from clients. See
|
/development/samples/Support7Demos/src/com/example/android/supportv7/app/ |
ActionBarTabs.java | 79 * the interactions between different tabs.
|
/external/mockito/src/org/mockito/verification/ |
VerificationWithTimeout.java | 49 * If you want to verify there were NO interactions with the mock
|
/frameworks/base/docs/html/design/wear/ |
creative-vision.jd | 48 <p>Staying true to the strengths afforded by a smaller form factor, Android Wear focuses on simple interactions, only requiring input by the user when absolutely necessary. Most inputs are based around touch swipes or voice, and inputs requiring fine-grained finger movements are avoided. Android Wear is gestural, simple, and fast.</p>
|
/frameworks/base/docs/html/guide/topics/connectivity/nfc/ |
index.jd | 12 contain operating environments, allowing complex interactions with code executing on the tag.
|
/frameworks/base/docs/html/training/basics/intents/ |
index.jd | 50 interactions with other apps, such as start another app, receive a result from that app, and
|
/frameworks/base/docs/html/training/design-navigation/ |
index.jd | 22 <p>One of the very first steps to designing and developing an Android application is to determine what users are able to see and do with the app. Once you know what kinds of data users are interacting with in the app, the next step is to design the interactions that allow users to navigate across, into, and back out from the different pieces of content within the app.</p>
|
/frameworks/base/docs/html/training/in-app-billing/ |
index.jd | 29 <p>In-app billing is a service hosted on Google Play that lets you charge for digital content or for upgrades in your app. The In-app Billing API makes it easy for you to integrate In-app Billing into your applications. You can request product details from Google Play, issue orders for in-app products, and quickly retrieve ownership information based on users' purchase history. You can also query the Google Play service for details about in-app products, such as local pricing and availability. Google Play provides a checkout interface that makes user interactions with the In-app Billing service seamless, and provides a more intuitive experience to your users.</p>
|
/frameworks/data-binding/baseLibrary/src/main/java/android/databinding/ |
BindingAdapter.java | 49 * This is useful when there are unusual interactions between attributes. For example:
|
/packages/apps/Camera2/src/com/android/camera/burst/ |
BurstController.java | 26 * Controls the interactions with burst.
|
/packages/apps/Camera2/src/com/android/camera/filmstrip/ |
FilmstripDataAdapter.java | 25 * An interface which defines the interactions between the
|
/packages/apps/Contacts/tests/src/com/android/contacts/interactions/ |
ContactInteractionUtilTest.java | 16 package com.android.contacts.interactions;
|
/packages/apps/Dialer/src/com/android/dialer/interactions/ |
UndemoteOutgoingCallReceiver.java | 17 package com.android.dialer.interactions;
|