| /frameworks/base/docs/html/distribute/monetize/ |
| ads.jd | 165 Discover where people are downloading your app, and the features they
|
| /frameworks/base/docs/html/distribute/stories/games/ |
| noodlecake-super-stickman.jd | 104 href="https://developers.google.com/games/services/common/concepts/achievements">achievements</a> to your games and discover more about
|
| /frameworks/base/docs/html/distribute/users/ |
| know-your-user.jd | 14 users — how they discover your app, what devices they use, what they do
|
| /frameworks/base/docs/html/guide/topics/connectivity/usb/ |
| host.jd | 201 <li>Discover connected USB devices by using an intent filter to be notified when the user
212 <p>Your application can discover USB devices by either using an intent filter to be notified when
220 <p>To have your application discover a particular USB device, you can specify an intent filter to
290 intent filter</a> to discover USB devices as they're connected, it automatically receives
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| uses-permission-element.jd | 24 relying on Google Play to "discover" the requirements in
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| controls.jd | 46 here. Browse the {@link android.widget} package to discover more. If your app requires a
|
| /frameworks/base/docs/html/training/design-navigation/ |
| screen-planning.jd | 38 <p>Once you define the information model, you can begin to define the contexts necessary to enable users to effectively discover, view, and act upon the data in your application. In practice, one way to do this is to <em>determine the exhaustive set of screens</em> needed to allow users to navigate to and interact with the data. The set of screens we actually expose should generally vary depending on the target device; it's important to consider this early in the design process to ensure that the application can adapt to its environment.</p>
|
| /frameworks/base/docs/html/training/secure-file-sharing/ |
| request-file.jd | 94 can't discover and open any other files in the server app. Only the client app gets access to
|
| /libcore/ojluni/src/main/java/java/util/ |
| Stack.java | 35 * the stack for an item and discover how far it is from the top.
|
| /ndk/ |
| README.md | 20 and be added to the `PATH` for build scripts to discover.
|
| /ndk/sources/cxx-stl/llvm-libc++/patches.android/ |
| 0006-Emulate-__has_feature-for-GCC.patch | 7 language features: for clang it uses __has_feature() to discover; for gcc most
|
| /packages/apps/Dialer/InCallUI/src/com/android/incallui/widget/multiwaveview/ |
| Tweener.java | 63 // Iterate through arguments and discover properties to animate
|
| /packages/apps/Settings/src/com/android/settings/localepicker/ |
| LocaleLinearLayoutManager.java | 35 * <p>Also, the remove functionality is difficult to discover and use
|
| /prebuilts/gdb/darwin-x86/lib/python2.7/unittest/test/ |
| test_program.py | 22 suite = loader.discover('unittest.test')
|
| /prebuilts/gdb/linux-x86/lib/python2.7/unittest/test/ |
| test_program.py | 22 suite = loader.discover('unittest.test')
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/unittest/test/ |
| test_program.py | 22 suite = loader.discover('unittest.test')
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/unittest/test/ |
| test_program.py | 22 suite = loader.discover('unittest.test')
|
| /system/bt/stack/avdt/ |
| avdt_defs.h | 45 #define AVDT_SIG_DISCOVER 1 /* discover */
|
| /system/bt/tools/bdtool/ |
| adapter.c | 145 fprintf(stdout, "Discover state %s\n", state_name);
|
| /frameworks/base/services/core/java/com/android/server/display/ |
| WifiDisplayController.java | 81 // We repeatedly issue calls to discover peers every so often for a few reasons.
88 // we ask to discover again, particularly for the isSessionAvailable() property.
392 Slog.d(TAG, "Discover peers succeeded. Requesting peers now.");
403 Slog.d(TAG, "Discover peers failed with reason " + reason + ".");
411 // Retry discover peers periodically until stopped.
[all...] |
| /system/bt/bta/gatt/ |
| bta_gattc_cache.c | 358 APPL_TRACE_DEBUG("discover range [%d ~ %d]",p_rec->s_handle, p_rec->e_handle);
463 APPL_TRACE_DEBUG("starting discover characteristics descriptor");
770 /* discover services result, add services into a service list */
792 /* start discover primary service */
872 /* discover services result, add services into a service list */
[all...] |
| /system/bt/stack/gatt/ |
| gatt_cl.c | 804 /* discover all services */
821 GATT_TRACE_ERROR("discover all service response parsing failure");
826 /* discover included service */
885 else /* discover characterisitic */
923 /* send callback if is discover procedure */
[all...] |
| /external/chromium-trace/catapult/telemetry/docs/pydoc/ |
| telemetry.internal.platform.tracing_controller_backend.html | 24 <a href="telemetry.core.discover.html">telemetry.core.discover</a><br>
|
| telemetry.record_wpr.html | 28 <a href="telemetry.core.discover.html">telemetry.core.discover</a><br>
|
| /external/chromium-trace/catapult/telemetry/telemetry/ |
| benchmark_runner.py | 28 from telemetry.core import discover
251 benchmarks += discover.DiscoverClasses(search_dir,
|
