| /external/chromium_org/chrome/browser/prefs/ |
| proxy_config_dictionary.cc | 14 // See ProxyPrefs for possible values and interactions with the other proxy
|
| /external/chromium_org/chrome/browser/ui/cocoa/profiles/ |
| profile_signin_confirmation_view_controller_browsertest.mm | 77 // Visible for testing UI interactions.
|
| /external/chromium_org/net/http/ |
| failing_http_transaction_factory.cc | 28 // to test interactions between cache and network.
|
| /external/chromium_org/ppapi/native_client/tests/ppapi_test_lib/ |
| module_instance.cc | 6 // instance in browser interactions and provides a way to register custom
|
| /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 | 50 <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 | 49 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/testing/espresso/espresso-lib/src/main/java/com/google/android/apps/common/testing/ui/espresso/ |
| ViewAction.java | 29 * <li>Inject motion events or key events via the UiController to simulate user interactions.
|
| /packages/apps/Contacts/src/com/android/contacts/interactions/ |
| SmsInteraction.java | 16 package com.android.contacts.interactions;
|
| /packages/apps/Contacts/tests/src/com/android/contacts/interactions/ |
| ContactInteractionUtilTest.java | 16 package com.android.contacts.interactions;
|
| /external/ceres-solver/internal/ceres/ |
| visibility_based_preconditioner.h | 78 // cameras that we expect have strong interactions, and then using the
98 // identifying strong interactions between cluster pairs. This is done
|
| /external/chromium_org/tools/telemetry/telemetry/web_perf/ |
| timeline_interaction_record.py | 36 As a page runs, typically a number of different (simulated) user interactions
40 interactions.
|
| /frameworks/native/include/gui/ |
| BufferQueueConsumer.h | 77 // interactions with the BufferQueue by the producer to fail.
87 // state, causing most interactions with the BufferQueue by the producer to
|
| /external/lldb/test/functionalities/thread/state/ |
| TestThreadStates.py | 174 # Go back to synchronous interactions
260 # Go back to synchronous interactions
326 # Go back to synchronous interactions
|
| /frameworks/base/services/core/java/com/android/server/job/ |
| JobServiceContext.java | 50 * There are two important interactions into this class from the
54 * - Cancelling is trickier, because there are also interactions from the client. It's possible
85 // Messages that result from interactions with the client service.
|
| /docs/source.android.com/src/devices/ |
| audio_avoiding_pi.jd | 186 <strong>Note</strong>: Atomic operations and their interactions with memory barriers
307 system and the interactions. Tools such as
|
| /external/mockito/src/org/mockito/ |
| MockSettings.java | 126 * Specifies default answers to interactions.
166 * during test debugging in order to find wrong interactions with this mock.
|
| /frameworks/base/docs/html/tools/testing/ |
| contentprovider_testing.jd | 126 database operations but stubs out other interactions with the Android system.
192 Test the standard provider interactions: Most providers offer six access methods:
|
| /packages/apps/Contacts/src/com/android/contacts/editor/ |
| GroupMembershipView.java | 41 import com.android.contacts.interactions.GroupCreationDialogFragment;
42 import com.android.contacts.interactions.GroupCreationDialogFragment.OnGroupCreatedListener;
|
| /frameworks/base/media/java/android/media/ |
| MediaFocusControl.java | 712 // event filtering based on voice-based interactions
[all...] |
| /development/samples/ApiDemos/src/com/example/android/apis/app/ |
| NotifyingService.java | 117 // This is the object that receives interactions from clients. See
|
| /development/samples/Support7Demos/src/com/example/android/supportv7/app/ |
| ActionBarWithDrawerLayout.java | 67 // prescribed interactions between a top-level sliding drawer and the action bar.
|
