HomeSort by relevance Sort by last modified time
    Searched full:situation (Results 376 - 400 of 1397) sorted by null

<<11121314151617181920>>

  /development/samples/SearchableDictionary/res/raw/
definitions.txt 258 diplomacy - n. subtly skillful handling of a situation
335 equilibrium - n. a stable situation in which forces cancel one another
    [all...]
  /external/libusb/libusb/
io.c 437 * the situation where all packets transfer the full amount of requested data.
684 * Unfortunately, the situation is complicated further when multiple threads
    [all...]
  /libcore/ojluni/src/main/java/java/lang/
Throwable.java 47 * are freshly created in the context of the exceptional situation so
175 * diagnosability of that situation. These objects are created
333 * flow between two sub-systems, is another situation where
    [all...]
  /art/runtime/
fault_handler.cc 43 // In order to handle this situation, before we call the stack tracer we do the following:
  /bionic/libc/arch-mips/string/
memset.S 158 of 4 so avoid this situation when using PREPAREFORSTORE. */
  /bionic/libc/malloc_debug/
Config.cpp 380 // This situation can occur if the free_track option is specified and
  /cts/apps/CtsVerifier/src/com/android/cts/verifier/bluetooth/
BluetoothChatService.java 319 // Situation normal. Start the connected thread.
  /cts/tests/tests/database/src/android/database/cts/
CursorWrapperTest.java 475 * that can cause corruption in database in the following situation:
  /cts/tests/tests/webkit/src/android/webkit/cts/
CookieManagerTest.java 333 // situation up with two TestServers on different ports (these count as having
  /developers/build/prebuilts/gradle/BluetoothChat/Application/src/main/java/com/example/android/bluetoothchat/
BluetoothChatService.java 338 // Situation normal. Start the connected thread.
  /developers/samples/android/connectivity/bluetooth/BluetoothChat/Application/src/main/java/com/example/android/bluetoothchat/
BluetoothChatService.java 338 // Situation normal. Start the connected thread.
  /development/samples/BluetoothChat/src/com/example/android/BluetoothChat/
BluetoothChatService.java 313 // Situation normal. Start the connected thread.
  /development/samples/browseable/BluetoothChat/src/com.example.android.bluetoothchat/
BluetoothChatService.java 338 // Situation normal. Start the connected thread.
  /development/tools/labpretest/
labpretest.sh 12 # times. It will detect if it is in a low battery situation and wait for it to
  /device/asus/fugu/libaudio/
alsa_utils.cpp 388 // We try to detect that situation and allow 4X rate even if the
  /device/google/contexthub/inc/
chre_re.h 66 * situation is detected that is likely to have widespread impact, though
  /docs/source.android.com/src/devices/sensors/
batching.jd 146 <p>Here is a situation we want to avoid:</p>
  /docs/source.android.com/src/devices/tv/
HDMI-CEC.jd 231 * some reason. HAL implementation should take the situation into account
  /docs/source.android.com/src/source/
downloading.jd 191 settings of the TCP/IP stack and using non-parallel commands can improve the situation. You
known-issues.jd 147 improve the situation for some users.</p>
  /external/apache-http/src/org/apache/commons/logging/impl/
WeakHashtable.java 94 * Such a situation occurs when the commons-logging.jar is
  /external/apache-xml/src/main/java/org/apache/xml/serializer/
NamespaceMappings.java 290 // the optimization of essentially this situation:
  /external/autotest/client/site_tests/graphics_PiglitBVT/
generate_scripts.py 296 # TODO(ihf): If we ever get into the situation that one test takes more than
  /external/autotest/client/site_tests/security_SymlinkRestrictions/
security_SymlinkRestrictions.py 255 # Test the basic "root follows evil symlink" situation first, in
  /external/autotest/server/
kvm.py 401 # In that situation, nothing is to

Completed in 1642 milliseconds

<<11121314151617181920>>