| /frameworks/base/docs/html/guide/practices/ |
| optimizing-for-3.0.jd | 523 <supports-screens>}</a> element for the reverse scenario (when your application is not compatible
584 <compatible-screens>}</a> element for the reverse scenario (when your application is not
[all...] |
| /frameworks/base/docs/html/preview/ |
| behavior-changes.jd | 405 directly, you should still test your app for this scenario.
782 must be able to gracefully handle this scenario. Otherwise, it crashes
853 the system requires user confirmation. In this scenario, apps should expect
|
| /cts/tests/tests/renderscript/src/android/renderscript/cts/ |
| RSUtils.java | 195 // includeNegatives to true. In this scenario, the upper bound is set to the larger of
|
| /developers/build/prebuilts/gradle/RuntimePermissionsWear/Wearable/src/main/java/com/example/android/wearable/runtimepermissions/ |
| MainWearActivity.java | 58 * phone is trying to access hasn't been granted (wear's sensors). If granted in that scenario,
|
| /developers/samples/android/wearable/wear/RuntimePermissionsWear/Wearable/src/main/java/com/example/android/wearable/runtimepermissions/ |
| MainWearActivity.java | 58 * phone is trying to access hasn't been granted (wear's sensors). If granted in that scenario,
|
| /development/samples/browseable/RuntimePermissionsWear/Wearable/src/com.example.android.wearable.runtimepermissions/ |
| MainWearActivity.java | 58 * phone is trying to access hasn't been granted (wear's sensors). If granted in that scenario,
|
| /device/generic/goldfish/camera/ |
| EmulatedCameraDevice.h | 316 * and terminated in StopCapturing. Since this is such a typical scenario,
|
| /docs/source.android.com/src/source/ |
| known-issues.jd | 164 (there can be several hundred requests in a worst-case scenario).</p>
|
| /external/autotest/cli/ |
| server.py | 317 # to handle scenario that both role and status are changed.
|
| /external/autotest/client/cros/cellular/ |
| base_station_pxt.py | 150 'SCENArio:LOAD "FDD_Combined_v6.3.lbmf"',
|
| /external/dnsmasq/ |
| setup.html | 170 VPNs but it is fully general. The scenario is this: you have a
|
| /external/fonttools/Lib/fontTools/pens/ |
| basePen.py | 361 # testing the "no on-curve point" scenario
|
| /external/google-breakpad/src/client/windows/unittests/ |
| exception_handler_death_test.cc | 196 // the out of process scenario, since it's happening in a different
|
| /external/jacoco/org.jacoco.doc/docroot/doc/ |
| flow.html | 306 scenario for java applications (albeit not for plain unit tests). Probes must
|
| /external/llvm/bindings/python/llvm/ |
| object.py | 63 # In this example, we mix a working and failing scenario.
|
| /external/llvm/test/Transforms/SimplifyCFG/ |
| empty-cleanuppad.ll | 341 ; This case tests a scenario where an empty cleanup pad is not dominated by all
|
| /external/llvm/tools/dsymutil/ |
| dsymutil.cpp | 168 // name. In the real usage scenario, we'll want to ensure that the
|
| /external/mesa3d/src/mesa/drivers/dri/radeon/ |
| radeon_tcl.c | 281 * Prediction has to aim towards the best possible value that is worse than worst case scenario
|
| /external/nist-sip/java/gov/nist/javax/sip/ |
| EventScanner.java | 313 * example in the following scenario:
|
| /external/testng/doc/ |
| selenium.html | 71 <p>Considering this scenario, the first thing that comes to mind is creating a long test case that goes through all the steps. This might be a good approach if you are writing a manual test case. However, since we are writing an automated test, we want to write our script as modular as possible to be able to reuse parts of it in future scenarios.</p>
|
| /external/webrtc/webrtc/modules/video_coding/include/ |
| video_coding.h | 169 // scenario
|
| /frameworks/base/core/java/android/os/ |
| LocaleList.java | 345 if (mList.length == 1) { // just one locale, perhaps the most common scenario
|
| /frameworks/base/core/tests/coretests/src/android/database/ |
| DatabaseCursorTest.java | 484 * This test is for that scenario.
|
| /frameworks/base/core/tests/coretests/src/android/view/ |
| FocusFinderTest.java | 295 * Real scenario grabbed from song playback screen.
|
| /frameworks/base/docs/html/google/play/billing/ |
| billing_promotions.jd | 153 Your app should also support the scenario where a user redeems a promo code
|
