Searched
full:significant (Results
701 -
725 of
2106) sorted by null
<<21222324252627282930>>
/frameworks/base/core/java/android/util/ |
LongSparseArray.java | 37 * the performance difference is not significant, less than 50%.</p>
|
SparseArray.java | 37 * the performance difference is not significant, less than 50%.</p>
|
/frameworks/base/docs/html/sdk/ |
OLD_RELEASENOTES.jd | 33 Significant API Changes</b> 41 <li>ContentProvider Cursors have had significant changes to make them easier to create and remove certain data consistency bugs. 49 <li>Significant changes to the Location API to make it easier to use and better self-documenting 204 <li>Due to significant API changes in the upstream open-source project and due to the timeline of getting certain Bluetooth profile implementations certified, a comprehensive Bluetooth API will not be possible or present in Android 1.0.
|
/frameworks/base/docs/html/training/articles/ |
perf-anr.jd | 26 but still feels sluggish, hang or freeze for significant periods, or take too
|
/frameworks/base/docs/html/training/wearables/watch-faces/ |
performance.jd | 149 <p>Animations are often computationally expensive and consume a significant amount of power. Most
|
/frameworks/base/graphics/java/android/graphics/drawable/ |
DrawableWrapper.java | 67 * after significant state changes, e.g. from the One True Constructor and
|
/frameworks/base/services/core/java/com/android/server/display/ |
OverlayDisplayWindow.java | 385 * Watches for significant changes in the overlay display window lifecycle.
|
/frameworks/base/services/core/java/com/android/server/hdmi/ |
HdmiUtils.java | 240 // Get the parent of the new path by clearing the least significant
|
/frameworks/opt/telephony/src/java/android/telephony/ |
SmsCbCmasInfo.java | 138 /** CMAS severity type: Significant threat to life or property. */
|
/frameworks/support/v4/java/android/support/v4/util/ |
LongSparseArray.java | 34 * the performance difference is not significant, less than 50%.</p>
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/vp8/common/ |
mfqe.c | 13 * In rate limited situations keyframes may cause significant visual artifacts
|
/hardware/invensense/6515/libsensors_iio/ |
MPLSensor.h | 98 #define INV_DMP_SIGNIFICANT_MOTION 0x004 //significant motion
|
/libcore/luni/src/main/java/java/io/ |
PushbackInputStream.java | 287 * least significant byte of the integer {@code oneByte} is pushed back.
|
/ndk/docs/Programmers_Guide/html/ |
md_3__key__topics__c_p_u__support__c_p_u-_a_r_m-_n_e_o_n.html | 70 <p>Not all ARMv7-based Android devices will support NEON, but those that do may benefit in significant ways from the scalar/vector instructions.</p>
|
/ndk/sources/third_party/googletest/googletest/include/gtest/ |
gtest-death-test.h | 148 // death test, which already incurs significant overhead by launching
|
/packages/apps/ManagedProvisioning/src/com/android/managedprovisioning/ |
Utils.java | 103 * significant.
|
/packages/apps/Settings/src/com/android/settings/applications/ |
ProcStatsEntry.java | 128 // See if there is one significant package that was running here.
|
/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/sysroot/usr/include/ |
tic.h | 68 ** byte-order, i.e., least-significant byte first.
|
/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot/usr/include/linux/ |
dm-ioctl.h | 65 * Wait for a significant event to occur to the device. This
|
/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot/usr/include/ |
tic.h | 68 ** byte-order, i.e., least-significant byte first.
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/decimaltestdata/ |
ddReduce.decTest | 111 -- some significant trailing zeros, were we to be trimming
|
dqReduce.decTest | 112 -- some significant trailing zeros, were we to be trimming
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
test_long_future.py | 195 # if the least significant bit of q=ans*2**53 is zero.
|
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/test/decimaltestdata/ |
ddReduce.decTest | 111 -- some significant trailing zeros, were we to be trimming
|
dqReduce.decTest | 112 -- some significant trailing zeros, were we to be trimming
|
Completed in 405 milliseconds
<<21222324252627282930>>