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

<<11121314151617181920>>

  /frameworks/base/core/java/android/app/
AlarmManager.java 48 * etc) it is easier and much more efficient to use
122 * etc) it is easier and much more efficient to use {@link android.os.Handler}.</b>
196 * timeouts, etc) it is easier and much more efficient to use
407 * the top of every hour. These alarms are more power-efficient than
  /frameworks/base/core/java/android/view/
WindowId.java 31 * not use this, instead relying on the simpler (and more efficient) methods available
  /frameworks/base/core/java/android/widget/
HeterogeneousExpandableList.java 36 * will be of the appropriate group or child type, resulting in a more efficient reuse of the
  /frameworks/base/docs/html/about/versions/
android-3.1-highlights.jd 71 interface more intuitive and more efficient to use.</p>
331 for more efficient and precise handling of events.</p>
370 <li>A new LRU cache class lets applications benefit from efficient caching.
375 Views, which makes drawing operations in those Views more efficient.</li>
  /frameworks/base/docs/html/design/get-started/
ui-overview.jd 45 <p>Recents provides an efficient way of switching between recently used applications. It provides a
  /frameworks/base/docs/html/design/patterns/
swipe-views.jd 12 <p>Efficient navigation is one of the cornerstones of a well-designed app. While apps are generally
  /frameworks/base/docs/html/google/play-services/
maps.jd 38 vector-based tiles for efficient caching and drawing; animated transitions; and much more.
  /frameworks/base/docs/html/training/graphics/opengl/
touch.jd 90 renderer that it is time to render the frame. This approach is the most efficient in this example
  /frameworks/base/media/java/android/media/
Image.java 26 * <p>This class allows for efficient direct application access to the pixel
  /frameworks/base/media/mca/filterfw/java/android/filterfw/core/
SerializedFrame.java 58 * responsible for synchronization. This is more efficient than a ByteArrayOutputStream, as
  /frameworks/base/tests/Camera2Tests/SmartCamera/SimpleCamera/src/androidx/media/filterfw/
Frame.java 45 * the most efficient backings for the intended type of access.
  /frameworks/compile/slang/
slang_rs_type_spec.h 106 // efficient decoding process (see DecodeTypeMetadata).
  /frameworks/native/opengl/tests/gldual/src/com/android/gldual/
TriangleRenderer.java 66 * the screen. The most efficient way of doing this is to use
  /hardware/ti/omap4xxx/hwc/
hal_public.h 87 /* In order to do efficient cache flushes we need the buffer dimensions
  /libcore/luni/src/main/java/java/io/
Serializable.java 93 * <strong>JSON</strong> is concise, human-readable and efficient. Android
  /libcore/luni/src/main/java/org/xml/sax/helpers/
LocatorImpl.java 44 * is more efficient to provide location information only when
  /ndk/sources/cxx-stl/gabi++/src/
one_time_construction.cc 42 * code simpler and slightly more efficient
  /packages/apps/Gallery2/src/com/android/gallery3d/data/
Path.java 82 // TODO: toString() should be more efficient, will fix it later
  /packages/apps/Gallery2/src/com/android/photos/data/
GalleryBitmapPool.java 27 * Pool allowing the efficient reuse of bitmaps in order to avoid long
  /packages/apps/UnifiedEmail/src/com/android/mail/utils/
SparseLongArray.java 21 * there can be gaps in the indices. It is intended to be more efficient
  /packages/apps/UnifiedEmail/src/org/apache/james/mime4j/decoder/
UnboundedFifoByteBuffer.java 26 * UnboundedFifoByteBuffer is a very efficient buffer implementation.
  /packages/inputmethods/LatinIME/native/jni/src/suggest/core/layout/
proximity_info_params.cpp 73 // learning or something would be efficient.
  /prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/lib/gcc/arm-eabi/4.6.x-google/include/
unwind.h 272 is to have efficient data types large enough to hold the leb128 type
  /prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/lib/gcc/arm-eabi/4.6.x-google/plugin/include/config/arm/
elf.h 102 the code more efficient, but for Thumb-1 it's better to put them out of
  /prebuilts/gcc/darwin-x86/arm/arm-eabi-4.7/lib/gcc/arm-eabi/4.7/include/
unwind-arm-common.h 242 is to have efficient data types large enough to hold the leb128 type

Completed in 885 milliseconds

<<11121314151617181920>>