| /hardware/qcom/gps/msm8084/utils/ |
| loc_target.cpp | 95 * based on property value. For 1530 scenario, the value shall be one of the
|
| /hardware/qcom/gps/msm8909/utils/ |
| loc_target.cpp | 96 * based on property value. For 1530 scenario, the value shall be one of the
|
| /hardware/qcom/gps/msm8994/loc_api/libloc_api_50001/ |
| LocEngAdapter.cpp | 159 * functionality, that can't be used in SSR scenario, as it
|
| /hardware/qcom/gps/msm8994/utils/ |
| loc_target.cpp | 96 * based on property value. For 1530 scenario, the value shall be one of the
|
| /hardware/qcom/gps/msm8996/utils/ |
| loc_target.cpp | 96 * based on property value. For 1530 scenario, the value shall be one of the
|
| /hardware/qcom/gps/utils/ |
| loc_target.cpp | 96 * based on property value. For 1530 scenario, the value shall be one of the
|
| /packages/apps/Dialer/src/com/android/dialer/widget/ |
| SearchEditTextLayout.java | 109 // search view. This accelerates the long-press scenario for copy/paste.
|
| /prebuilts/gdb/darwin-x86/lib/python2.7/test/ |
| test_winsound.py | 38 # scenario as they have no sound devices whatsoever (not even
|
| /prebuilts/gdb/linux-x86/lib/python2.7/test/ |
| test_winsound.py | 38 # scenario as they have no sound devices whatsoever (not even
|
| /prebuilts/go/darwin-x86/src/sync/ |
| pool.go | 39 // that scenario. It is more efficient to have such objects implement their own
|
| /prebuilts/go/linux-x86/src/sync/ |
| pool.go | 39 // that scenario. It is more efficient to have such objects implement their own
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
| test_winsound.py | 38 # scenario as they have no sound devices whatsoever (not even
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/test/ |
| test_winsound.py | 38 # scenario as they have no sound devices whatsoever (not even
|
| /sdk/docs/ |
| Notes_on_WST_StructuredDocument.txt | 178 list seems the most useful scenario. There's no actual iterator provided for inner regions.
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.tests/src/com/android/ide/eclipse/adt/internal/build/ |
| AaptParserTest.java | 108 // This test is disabled because I can't find a useful scenario for handling this error
|
| /external/webrtc/webrtc/modules/audio_processing/beamformer/ |
| nonlinear_beamformer.cc | 33 // interferer scenario.
37 // scenario is proportional to this constant.
56 // postfilter expression. It handles the scenario mismatch between the true and
|
| /frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/ |
| WifiConnectivityManagerTest.java | 528 * Verify that scan interval for screen on and wifi disconnected scenario
591 * Verify that scan interval for screen on and wifi connected scenario
700 * in this scenario.
[all...] |
| /frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/dataconnection/ |
| DcTrackerTest.java | 383 // Test the normal data call setup scenario.
442 // Test the scenario where the first data call setup is failed, and then retry the setup later.
682 // Test the default data switch scenario.
[all...] |
| /external/autotest/server/hosts/ |
| adb_host.py | 696 that scenario will undoubtedly be a development scenario (test station
697 is also the moblab) and not the typical live test running scenario so
781 that scenario will undoubtedly be a development scenario (test station
782 is also the moblab) and not the typical live test running scenario so
[all...] |
| /external/iproute2/man/man7/ |
| tc-hfsc.7 | 194 The only workaround in this scenario is to allow the 1st class to send the
459 This is important to keep those settings in mind, as in scenario like: no
513 curve there, and in such a scenario HFSC simply doesn't throttle at all.
|
| /art/runtime/gc/ |
| reference_processor.cc | 70 // scenario where it becomes non-null during the reference processing phase.
|
| /cts/apps/CtsVerifier/src/com/android/cts/verifier/sensors/ |
| SignificantMotionTestActivity.java | 119 * It ensures that Significant Motion will not trigger in that scenario.
|
| /development/samples/Support4Demos/src/com/example/android/supportv4/media/ |
| MediaController.java | 277 // The second scenario involves the user operating the scroll ball, in this
|
| /development/samples/ToyVpn/server/linux/ |
| ToyVpnServer.cpp | 33 // example for the simplest scenario. Let us say that a Linux box has a
|
| /external/apache-http/src/org/apache/commons/logging/ |
| package.html | 198 purposes. A typical scenario for a server application is to have each
|
