HomeSort by relevance Sort by last modified time
    Searched full:lose (Results 351 - 375 of 848) sorted by null

<<11121314151617181920>>

  /external/openssl/crypto/engine/
README 68 we would lose our ability to link selectively by selectively loading certain
  /external/pixman/pixman/
pixman-radial-gradient.c 308 * lose 11 bits of precision in each of the multiplication and
  /external/qemu/distrib/jpeg-6b/
jfdctint.c 82 #define PASS1_BITS 1 /* lose a little precision to avoid overflow */
jidctfst.c 81 #define PASS1_BITS 1 /* lose a little precision to avoid overflow */
jidctint.c 82 #define PASS1_BITS 1 /* lose a little precision to avoid overflow */
jidctred.c 47 #define PASS1_BITS 1 /* lose a little precision to avoid overflow */
  /external/qemu/hw/
goldfish_events_device.c 126 fprintf(stderr, "##KBD: Full queue, lose event\n");
  /external/skia/src/opts/
SkBitmapProcState_matrix_repeat_neon.h 325 * motion if possible; this ensures that we don't lose
  /external/valgrind/main/VEX/
Makefile-icc 83 # 810: conversion from ... to ... may lose significant bits
  /external/wpa_supplicant_8/src/wps/
wps_upnp_event.c 255 * we have to queue them, if we lose them then the subscriber will
  /external/zlib/src/contrib/minizip/
miniunz.c 467 unzCloseCurrentFile(uf); /* don't lose the error */
  /frameworks/base/core/java/android/app/
LauncherActivity.java 308 // change the same instance and we would lose the
  /frameworks/base/docs/html/distribute/googleplay/strategies/
app-quality.jd 58 One sure-fire way to lose your users is to give them a slow, unresponsive UI. Research has shown that <a href="http://googleresearch.blogspot.com/2009/06/speed-matters.html">speed matters</a>... for any interface, be it desktop, web, or mobile. In fact, the importance of speed is amplified on mobile devices since users often need their information on the go and in a hurry.</p>
  /frameworks/base/docs/html/guide/practices/app-design/
seamlessness.jd 76 appeared, your application will likely lose that data when your application is
  /frameworks/base/docs/html/guide/practices/
seamlessness.jd 77 appeared, your application will likely lose that data when your application is
  /frameworks/opt/calendar/tests/src/com/android/calendarcommon2/
RecurrenceProcessorTest.java     [all...]
  /frameworks/opt/vcard/java/com/android/vcard/
VCardConfig.java 51 * In order to avoid "misinterpretation" of charset and lose any data in vCard,
  /frameworks/rs/cpu_ref/
rsCpuIntrinsicBlur.cpp 76 // the gaussian curve begins to lose its shape
  /libcore/luni/src/main/java/java/nio/
DatagramChannelImpl.java 195 // TODO: disallow mapped buffers and lose this conditional?
  /libcore/luni/src/main/java/java/util/concurrent/
DelayQueue.java 61 * and lose leadership while waiting.
TimeUnit.java 150 * truncate, so lose precision. For example converting
  /ndk/sources/host-tools/make-3.81/
alloca.c 54 lose
expand.c 127 /* Expanding V causes infinite recursion. Lose. */
  /ndk/sources/host-tools/sed-4.2.1/lib/
alloca.c 59 lose
  /packages/apps/Contacts/src/com/android/contacts/activities/
ActionBarAdapter.java 444 // we'd lose restored tab.

Completed in 903 milliseconds

<<11121314151617181920>>