HomeSort by relevance Sort by last modified time
    Searched full:improve (Results 101 - 125 of 1748) sorted by null

1 2 3 45 6 7 8 91011>>

  /frameworks/base/docs/html/distribute/engage/
gcm.jd 26 possibility is to improve the experience for users with multiple devices, by
  /frameworks/base/docs/html/guide/topics/renderscript/
index.jd 18 since then. One of the major goals of this past year was to improve the performance
  /frameworks/base/docs/html/topic/performance/
index.jd 3 page.metaDescription=Improve your app's performance by learning how to optimize power consumption, launch times, and other important areas of performance.
  /frameworks/base/libs/hwui/
AnimatorManager.h 70 // To improve the efficiency of resizing & removing from the vector
  /prebuilts/go/darwin-x86/src/go/types/testdata/
conversions.src 86 // TODO(gri) add more tests, improve error message
  /prebuilts/go/linux-x86/src/go/types/testdata/
conversions.src 86 // TODO(gri) add more tests, improve error message
  /external/shflags/doc/
coding_standards.txt 6 understand. To improve code readability and usability, some guidelines have
52 brackets, e.g. '${flags_someVariable}' to improve code readability.
72 Where it makes sense to improve readability, variables can have the first
  /frameworks/native/vulkan/libvulkan/
swapchain.cpp 234 // TODO(jessehall): Improve error reporting. Can we enumerate possible
469 // TODO(jessehall): Improve error reporting. Can we enumerate possible
495 // TODO(jessehall): Improve error reporting. Can we enumerate possible
504 // TODO(jessehall): Improve error reporting. Can we enumerate possible
515 // TODO(jessehall): Improve error reporting. Can we enumerate possible
535 // TODO(jessehall): Improve error reporting. Can we enumerate possible
546 // TODO(jessehall): Improve error reporting. Can we enumerate possible
558 // TODO(jessehall): Improve error reporting. Can we enumerate possible
576 // TODO(jessehall): Improve error reporting. Can we enumerate possible
598 // TODO(jessehall): Improve error reporting. Can we enumerate possibl
    [all...]
  /external/curl/docs/
ROADMAP.md 11 Improve performance. Measurements and tests have shown that in several cases
116 Improve
124 simplify or improve the situation as we are likely to keep adding
  /external/liblzf/
Changes 7 - improve C++ compatibility of the code.
8 - slightly improve compressor speed.
10 which can improve the speed quite a bit on older cpus.
  /frameworks/base/docs/html/topic/performance/rendering/
overdraw.jd 2 page.metaDescription=Improve performance by reducing unnecessary rendering.
167 If you encounter this sort of issue, you may be able to improve performance by
184 significantly to overdraw. You can improve overdraw in these situations by
  /device/google/contexthub/firmware/inc/algos/
ap_hub_sync.h 29 * This implements an AP-HUB time sync algorithm that is expected to improve time sync accuracy by
  /docs/source.android.com/src/security/enhancements/
enhancements70.jd 33 improve reliability against non-malicious data corruption.</li>
  /external/ceres-solver/internal/ceres/
detect_structure.h 42 // we can use template specialization to improve the performance of
  /external/chromium-trace/catapult/third_party/gsutil/third_party/rsa/doc/
index.rst 13 If you have the time and skill to improve the implementation, by all
  /external/clang/www/
clang_video-07-25-2007.html 18 <p><b>Details:</b> The LLVM 2.0 release brings a number of new features and capabilities to the LLVM toolset. This talk briefly describes those features, then moves on to talk about what is next: llvm 2.1, llvm-gcc 4.2, and puts a special emphasis on the 'clang' C front-end. This describes how the 'clang' preprocessor can be used to improve the scalability of distcc by up to 4.4x.
  /external/hyphenation-patterns/fr/
hyph-fr.lic.txt 43 % did their best effort to improve the list of patterns.
  /external/icu/android_icu4j/cts-coverage/src/main/tests/android/icu/cts/coverage/util/
CurrencyTest.java 28 * Extra tests to improve CTS Test Coverage.
  /external/icu/android_icu4j/src/main/java/android/icu/util/
Measure.java 70 // TODO improve this to catch more cases (two different longs that have same double values, BigDecimals, etc)
  /external/icu/android_icu4j/src/main/tests/android/icu/dev/util/
Timer.java 94 // Timing on Java is very tricky, especially when you count in garbage collection. This is a simple strategy for now, we might improve later.
  /external/icu/icu4j/main/tests/framework/src/com/ibm/icu/dev/util/
Timer.java 93 // Timing on Java is very tricky, especially when you count in garbage collection. This is a simple strategy for now, we might improve later.
  /external/libbrillo/brillo/
file_utils_unittest.cc 30 // to improve readability of tests.
  /external/libgdx/extensions/gdx-bullet/jni/src/bullet/BulletCollision/CollisionShapes/
btSphereShape.h 64 //to improve gjk behaviour, use radius+margin as the full margin, so never get into the penetration case
  /external/libgdx/extensions/gdx-bullet/jni/swig-src/dynamics/
dynamics_wrap.h 6 * coding conventions designed to improve portability and efficiency. Do not make
  /external/libvpx/libvpx/vp9/encoder/
vp9_tokenize.h 73 * improve cache locality, since it's needed for costing when the rest of the

Completed in 634 milliseconds

1 2 3 45 6 7 8 91011>>