Searched
full:scenario (Results
351 -
375 of
709) sorted by null
<<11121314151617181920>>
/frameworks/base/docs/html/training/gestures/ |
scale.jd | 185 common scenario is <em>panning</em>, which is when a user's dragging motion causes scrolling
|
scroll.jd | 49 necessary for special scenarios. This lesson describes such a scenario: displaying
|
/frameworks/base/docs/html/training/tv/discovery/ |
recommendations.jd | 28 content. An ideal scenario for many TV users is: sit down, turn on, and watch. The fewest steps
|
/frameworks/base/packages/DocumentsUI/src/com/android/documentsui/dirlist/ |
Model.java | 318 // have identical numerical sort keys. One common example of this scenario is seen
|
/frameworks/base/packages/SystemUI/src/com/android/systemui/recents/tv/ |
RecentsTvActivity.java | 113 // be unnecessarily shown in the scenario: PIP->Fullscreen->PIP.
|
/frameworks/base/telephony/java/com/android/internal/telephony/ |
RILConstants.java | 79 int INTERNAL_ERR = 38; /* Hit unexpected vendor internal error scenario */
|
/frameworks/native/libs/binder/ |
IMemory.cpp | 299 // remote call without mLock held, worse case scenario, we end up
|
/frameworks/opt/bitmap/src/com/android/bitmap/ |
ContiguousFIFOAggregator.java | 38 * A characteristic scenario is as follows:
|
/hardware/qcom/audio/msm8909/hal/audio_extn/ |
utils.c | 409 * Handles scenario where input sample rate is higher
|
/hardware/qcom/display/msm8084/libhwcomposer/ |
hwc_virtual.cpp | 187 // In this scenario, the first VDS draw call will have HWC
|
/hardware/qcom/display/msm8226/libhwcomposer/ |
hwc_virtual.cpp | 203 // In this scenario, the first VDS draw call will have HWC
|
/hardware/qcom/gps/msm8909/loc_api/libloc_api_50001/ |
LocEngAdapter.cpp | 335 * functionality, that can't be used in SSR scenario, as it
|
/hardware/qcom/gps/msm8996/loc_api/libloc_api_50001/ |
LocEngAdapter.cpp | 335 * functionality, that can't be used in SSR scenario, as it
|
/hardware/qcom/msm8996/original-kernel-headers/linux/ |
msm_mdp_ext.h | 261 * based on validate call failure scenario.
|
/libcore/luni/src/main/java/java/util/concurrent/ |
BlockingQueue.java | 103 * Usage example, based on a typical producer-consumer scenario.
|
/libcore/ojluni/src/main/java/java/util/zip/ |
Deflater.java | 383 * compression (should be used in normal use scenario). A return value
|
/packages/apps/Messaging/src/com/android/messaging/ui/ |
AsyncImageView.java | 283 // Check whether we are in a simple reuse scenario: detached from window, and reattached
|
/packages/services/Telephony/src/com/android/phone/ |
NetworkSetting.java | 467 // It's not a error in following scenario, we just ignore it.
|
/prebuilts/gdb/darwin-x86/lib/python2.7/email/ |
generator.py | 95 # We can't write the headers yet because of the following scenario:
|
/prebuilts/gdb/linux-x86/lib/python2.7/email/ |
generator.py | 95 # We can't write the headers yet because of the following scenario:
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/email/ |
generator.py | 95 # We can't write the headers yet because of the following scenario:
|
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/email/ |
generator.py | 95 # We can't write the headers yet because of the following scenario:
|
/system/connectivity/shill/ |
active_link_monitor_unittest.cc | 471 // This value doesn't match real life (the timer in this scenario
|
/cts/tests/tests/location/src/android/location/cts/ |
LocationManagerTest.java | [all...] |
/external/caliper/caliper/src/main/java/com/google/caliper/options/ |
ParsedOptions.java | 377 " -n, --dry-run instead of measuring, execute a single rep for each scenario", 387 " -t, --trials number of independent trials to peform per benchmark scenario; ",
|
Completed in 1833 milliseconds
<<11121314151617181920>>