HomeSort by relevance Sort by last modified time
    Searched full:significant (Results 251 - 275 of 2519) sorted by null

<<11121314151617181920>>

  /frameworks/base/docs/html/training/efficient-downloads/
efficient-network-access.jd 32 <p>Using the wireless radio to transfer data is potentially one of your app's most significant sources of battery drain. To minimize the battery drain associated with network activity, it's critical that you understand how your connectivity model will affect the underlying radio hardware.</p>
38 <p>A fully active wireless radio consumes significant power, so it transitions between different energy states in order to conserve power when not in use, while attempting to minimize latency associated with "powering up" the radio when it's required.</p>
46 <p>While the low and idle states drain significantly less battery, they also introduce significant latency to network requests. Returning to full power from the low state takes around 1.5 seconds, while moving from idle to full can take over 2 seconds.</p>
96 <p>You could choose to prefetch an entire album, however should the user stop listening after the first song, you've wasted a significant amount of bandwidth and battery life.</p>
104 <p>Using this approach, the radio will be forced to remain active for the majority of users' news-reading session as they scroll headlines, change categories, and read articles. Not only that, but the constant switching between energy states will result in significant latency when switching categories or reading articles.</p>
108 <p>Another alternative is to prefetch every headline, thumbnail, article text, and possibly even full article pictures&mdash;typically in the background on a predetermined schedule. This approach risks spending significant bandwidth and battery life downloading content that's never used, so it should be implemented with caution.</p>
116 <p>An app that pings the server every 20 seconds, just to acknowledge that the app is running and visible to the user, will keep the radio powered on indefinitely, resulting in a significant battery cost for almost no actual data transfer.</p>
  /external/chromium_org/crypto/
ghash.cc 17 // matches the description in the paper[1]), thus the most significant bit is
154 // If the most-significant bit was set before shifting then it, conceptually,
205 // least-significant 8 bits, save for the term at x^128. Therefore we can
  /external/chromium_org/third_party/icu/source/common/
utrace.c 140 /* Little Endian. Move p to most significant end of the value */
146 * most significant to least significant end */
  /external/chromium_org/third_party/icu/source/test/intltest/
compactdecimalformattest.cpp 291 // We expect 3 significant digits by default
331 // All tests are written for two significant digits, so we explicitly set here
332 // in case default significant digits change.
  /external/icu/icu4c/source/common/
utrace.c 140 /* Little Endian. Move p to most significant end of the value */
146 * most significant to least significant end */
  /external/icu/icu4c/source/test/intltest/
compactdecimalformattest.cpp 291 // We expect 3 significant digits by default
331 // All tests are written for two significant digits, so we explicitly set here
332 // in case default significant digits change.
  /hardware/invensense/6515/libsensors_iio/
sensors_mpl.cpp 65 static const char *smdWakelockStr = "significant motion";
128 /* Significant Motion wakelock support */
142 /* No significant motion events pending yet */
  /art/compiler/dex/quick/mips/
README.mips 31 o Expand the def/use mask (which, unfortunately, is a significant change)
  /art/runtime/
memory_region.h 60 // significant bit in the first byte.
  /bionic/libc/bionic/
c32rtomb.cpp 87 // of 6 bits, least significant last. The first octet is
  /development/samples/ApiDemos/src/com/example/android/apis/os/
TriggerSensors.java 31 * <h3>Application showing the Trigger Sensor API for the Significant Motion sensor. </h3>
  /docs/source.android.com/src/devices/camera/
camera3_metadata.jd 54 without introducing significant stutter or delay to the output frame stream.
  /docs/source.android.com/src/devices/sensors/
power-use.jd 34 <li> Significant motion </li>
  /docs/source.android.com/src/source/
index.jd 39 allocated significant engineering resources to improve Android and bring Android
  /external/apache-xml/src/main/java/org/apache/xalan/processor/
XSLProcessorVersion.src 56 * significant, externally apparent enhancement from
  /external/apache-xml/src/main/java/org/apache/xml/serializer/
Version.java 81 * significant, externally apparent enhancement from
Version.src 81 * significant, externally apparent enhancement from
  /external/bouncycastle/bcprov/src/main/java/org/bouncycastle/asn1/x509/
SubjectKeyIdentifier.java 107 * the value 0100 followed by the least significant 60 bits of the
  /external/chromium_org/chrome/browser/mac/
keystone_promote_preflight.sh 87 # significant, but chmod -R and -h can't be used together. Do another
  /external/chromium_org/chrome/browser/net/
connect_interceptor.cc 44 // significant path.
  /external/chromium_org/chrome/browser/sync/test/integration/
two_client_themes_sync_test.cc 108 // Most other tests have significant coverage of model association. This test
  /external/chromium_org/chrome/browser/ui/cocoa/bookmarks/
bookmark_model_observer_for_cocoa.h 33 // Callback called on a significant model change. |nodeWasDeleted| will
  /external/chromium_org/gpu/command_buffer/common/
id_allocator_test.cc 55 // Allocate a significant number of resources.
  /external/chromium_org/net/spdy/
hpack_constants.h 25 // Represents a symbol and its Huffman code (stored in most-significant bits).
hpack_huffman_table.h 112 // Codes are stored in the most-significant bits of the word.

Completed in 342 milliseconds

<<11121314151617181920>>