Searched
full:scenario (Results
401 -
425 of
709) sorted by null
<<11121314151617181920>>
/external/libchrome/base/metrics/ |
field_trial.h | 10 // produces "better" results across our user population. In that scenario, UMA
|
/external/libnfc-nxp/src/ |
phHal4Nfc_ADD.c | [all...] |
phHciNfc_Emulation.c | 835 /* Error Scenario due to SWP Disable Config */ [all...] |
/external/llvm/include/llvm/CodeGen/ |
FastISel.h | 273 /// In this scenario, \p LI is "A", and \p FoldInst is "C". We know about "B"
|
/external/llvm/test/Transforms/MemCpyOpt/ |
form-memset.ll | 181 ; store followed by memset, different offset scenario
|
/external/mesa3d/src/mesa/drivers/dri/r200/ |
r200_tcl.c | 289 * Prediction has to aim towards the best possible value that is worse than worst case scenario
|
/external/opencv3/modules/ml/src/ |
lr.cpp | 199 as in multi class class scenario, we will have n thetas for n classes */
|
/external/v8/tools/ |
profile.js | 666 * for this scenario:
|
/external/valgrind/coregrind/ |
vgdb-invoker-solaris.c | 33 is the same - to work on the following scenario:
|
/external/webrtc/webrtc/base/ |
scoped_ptr.h | 233 // prevent the scenario initially described from occurring and
|
/external/webrtc/webrtc/modules/audio_processing/aec/ |
system_delay_unittest.cc | 368 // Here we test a buffer under run scenario. If we keep on calling
|
/frameworks/av/media/libstagefright/codecs/amrnb/enc/src/ |
cor_h.cpp | 61 scenario. Moved cor_h.h after cnst.h in the Include section.
|
/frameworks/av/services/camera/libcameraservice/device3/ |
Camera3OutputStream.cpp | 153 * Release the lock briefly to avoid deadlock for below scenario:
|
/frameworks/base/core/java/android/printservice/ |
PrinterDiscoverySession.java | 395 * A scenario when you may be requested to track a printer's state is if
|
/frameworks/base/core/java/android/view/accessibility/ |
AccessibilityInteractionClient.java | 58 * is blocked waiting for a result is has to compute! To avoid this scenario [all...] |
/frameworks/base/core/java/android/widget/ |
MediaController.java | 568 // The second scenario involves the user operating the scroll ball, in this
|
/frameworks/base/docs/html/guide/topics/appwidgets/ |
host.jd | 279 For example, many hosts align icons and widgets in a grid. In this scenario,
|
/frameworks/base/docs/html/guide/topics/location/ |
strategies.jd | 354 scenario also describes good practices for when you should start and stop listening for the
|
/frameworks/base/docs/html/training/articles/ |
wear-permissions.jd | 107 scenario is the applicable one when Wear requests this data.</p>
|
/frameworks/base/docs/html/training/scheduling/ |
alarms.jd | 82 <p>A common scenario for triggering an operation outside the lifetime of your app is
|
/frameworks/base/graphics/java/android/graphics/drawable/ |
RippleDrawable.java | 244 // Worst-case scenario. [all...] |
/frameworks/base/packages/DocumentsUI/src/com/android/documentsui/ |
BaseActivity.java | 646 * covers the scenario where a user opens DocumentsUI and just starts typing.
|
/frameworks/native/include/media/hardware/ |
HardwareAPI.h | 249 // scenario when these SW-readable/writable buffers are locked using gralloc_lock.
|
/frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/ |
GsmCdmaPhoneTest.java | 405 // old sharedPreference set (testing upgrade from M to N scenario)
|
/frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/gsm/ |
GsmInboundSmsHandlerTest.java | 604 * Test scenario: 2 messages are received with same address, ref number, count, and
|
Completed in 1945 milliseconds
<<11121314151617181920>>