HomeSort by relevance Sort by last modified time
    Searched full:significant (Results 276 - 300 of 2960) sorted by null

<<11121314151617181920>>

  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/sysroot/usr/include/
strings.h 49 The least-significant bit is position 1, the most-significant 32. */
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot/usr/include/
strings.h 109 The least-significant bit is position 1, the most-significant 32. */
  /prebuilts/go/darwin-x86/src/crypto/rand/
util.go 55 // Don't let the value be too small, i.e, set the most significant two bits.
112 // b is the number of bits in the most significant byte of max.
  /prebuilts/go/darwin-x86/src/encoding/binary/
varint.go 10 // least significant bits
11 // - the most significant bit (msb) in each output byte indicates if there
  /prebuilts/go/linux-x86/src/crypto/rand/
util.go 55 // Don't let the value be too small, i.e, set the most significant two bits.
112 // b is the number of bits in the most significant byte of max.
  /prebuilts/go/linux-x86/src/encoding/binary/
varint.go 10 // least significant bits
11 // - the most significant bit (msb) in each output byte indicates if there
  /system/core/include/mincrypt/
p256.h 64 // Return bit. Index 0 is least significant.
97 // Returns the bits shifted out of most significant digit.
  /external/zlib/src/doc/
rfc1951.txt 254 significant bit, and since we write numbers with the most-
255 significant digit on the left, we also write bytes with the most-
256 significant bit on the left. In the diagrams below, we number the
257 bits of a byte so that bit 0 is the least-significant bit, i.e.,
266 the least-significant byte first (at the lower memory address).
275 | + more significant byte = 2 x 256
276 + less significant byte = 8
300 with the least-significant bit of the byte.
302 starting with the least-significant bit of the data
305 significant bit of the code
    [all...]
  /external/valgrind/drd/
drd_bitmap.h 57 /** Number of least significant address bits that are ignored. */
71 * Number of bits assigned to the least significant component of an address.
77 * compute the least significant part of an address split, after having
82 /** Compute least significant bits of an address of type Addr. */
107 /** Compute most significant bits of an address of type Addr. */
155 * in order to compute the least significant part of an UWord.
174 * Return the least significant bits.
  /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/ImageMagick/ImageMagick/api/
magick.html 89 <p>GetMagickPrecision() returns the maximum number of significant digits to be printed.</p>
146 <p>SetMagickPrecision() sets the maximum number of significant digits to be printed.</p>
166 <dd>set the maximum number of significant digits to be printed. </dd>
  /external/ImageMagick/www/api/
magick.html 93 <p>GetMagickPrecision() returns the maximum number of significant digits to be printed.</p>
150 <p>SetMagickPrecision() sets the maximum number of significant digits to be printed.</p>
170 <dd>set the maximum number of significant digits to be printed. </dd>
  /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/v8/src/
property-details.h 65 // Order of kinds is significant.
70 // Order of modes is significant.
75 // Order of properties is significant.
  /hardware/invensense/6515/libsensors_iio/
sensors.h 154 {"MPL Significant Motion", "Invensense", 1, SENSORS_SIGNIFICANT_MOTION_HANDLE,
219 {"MPL Significant Motion", "Invensense", 1, SENSORS_SIGNIFICANT_MOTION_HANDLE,
277 {"MPL Significant Motion", "Invensense", 1,
sensors_mpl.cpp 66 static const char *smdWakelockStr = "significant motion";
139 /* Significant Motion wakelock support */
152 /* No significant motion events pending yet */
  /toolchain/binutils/binutils-2.25/gas/config/
atof-vax.c 284 Bits n-1:0 (if any) are most significant bits of fraction.
285 Bits 15:0 of the next word are the next most significant bits.
298 /* Seek (and forget) 1st significant bit. */
  /external/icu/android_icu4j/src/main/java/android/icu/text/
DecimalFormat.java 169 * <td>Significant digit
266 * significant integer digits, the <em>primary grouping size</em>, and one used for all
358 * not use <a href="#sci">scientific notation</a> or <a href="#sigdig">significant
362 * digits</em>, then only the least significant digits are shown. For example, 1997 is
426 * significant digits logic. The maximum number of significant digits limits the total
429 * section on significant digits for more details.
431 * <li>The number of significant digits shown is determined as follows: If
432 * areSignificantDigitsUsed() returns false, then the minimum number of significant digits
433 * shown is one, and the maximum number of significant digits shown is the sum of th
    [all...]
  /external/icu/icu4j/main/classes/core/src/com/ibm/icu/text/
DecimalFormat.java 168 * <td>Significant digit
265 * significant integer digits, the <em>primary grouping size</em>, and one used for all
357 * not use <a href="#sci">scientific notation</a> or <a href="#sigdig">significant
361 * digits</em>, then only the least significant digits are shown. For example, 1997 is
425 * significant digits logic. The maximum number of significant digits limits the total
428 * section on significant digits for more details.
430 * <li>The number of significant digits shown is determined as follows: If
431 * areSignificantDigitsUsed() returns false, then the minimum number of significant digits
432 * shown is one, and the maximum number of significant digits shown is the sum of th
    [all...]
  /art/runtime/interpreter/mterp/mips64/
footer.S 133 * significant bits of a0 must be 0.
  /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 45 allocated significant engineering resources to improve Android and bring Android

Completed in 1626 milliseconds

<<11121314151617181920>>