| /frameworks/base/docs/html/training/multiple-apks/ |
| screensize.jd | 96 <td>large</td>
110 <td class="greenCell">large</td>
198 <td class="blueCell">large</td>
204 <td class="greenCell">large</td>
210 <td class="blackCell">large</td>
223 <td class="greenCell">large</td>
348 <p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.telephony was implicitly added. Since most (if not all) xlarge devices are tablets without telephony hardware in them, Google Play will filter out this APK in these cases, until future devices come along which are both large enough to report as xlarge screen size, and possess telephony hardware.
|
| /external/libogg/src/ |
| bitwise.c | 600 static unsigned long large[]= local
666 oggpack_write(&o,large[i],32);
672 if(oggpack_look(&r,32)!=large[i]){
673 fprintf(stderr,"%ld != %ld (%lx!=%lx):",oggpack_look(&r,32),large[i],
674 oggpack_look(&r,32),large[i]);
752 oggpackB_write(&o,large[i],32);
758 if(oggpackB_look(&r,32)!=large[i]){
759 fprintf(stderr,"%ld != %ld (%lx!=%lx):",oggpackB_look(&r,32),large[i],
760 oggpackB_look(&r,32),large[i]);
|
| /frameworks/base/docs/html/tools/revisions/ |
| platforms.jd | 230 Nexus 7 (7.3", 800 x 1280, Large tvdpi screen)
242 10.1" WXGA Tablet (1280 x 800, X-Large mdpi screen)
245 7.0" WSVGA Tablet (1024 x 600, Large mdpi screen)
248 5.4" FWVGA (480 x 854, Large mdpi screen)
251 5.1" WVGA (480 x 800, Large mdpi screen)
374 WSVGA (1024x600, medium density, large screen)
377 WXGA800-7in (1280x800, high density, large screen) <span class="new">new</span>
490 WSVGA (1024x600, medium density, large screen)
575 WSVGA (1024x600, medium density, large screen) <span class="new">new</span>
|
| /libcore/luni/src/main/java/javax/xml/datatype/ |
| Duration.java | 81 * even though {@link Duration} can hold very large or very small values,
316 * very large values in its fields. See the {@link #addTo(Calendar)}
353 * very large values in its fields. See the {@link #addTo(Date)}
380 * Fields of a duration object may contain arbitrary large value.
722 * a very large value in the years or months fields.</p>
755 * arbitrarily large/small/precise values, the request may be beyond the
779 * arbitrarily large/small/precise values, the request may be beyond the
805 * arbitrarily large/small/precise values, the request may be beyond the
848 * arbitrarily large/small/precise values, the request may be beyond the
[all...] |
| /cts/tests/tests/content/src/android/content/res/cts/ |
| ConfigTest.java | 356 checkValue(res, R.configVarying.simple, "simple large");
358 R.styleable.TestConfig, new String[]{"bag large"});
560 checkValue(res, R.configVarying.simple, "simple large");
562 R.styleable.TestConfig, new String[]{"bag large"});
705 checkValue(res, R.configVarying.large, "default");
714 checkValue(res, R.configVarying.large, "default");
720 checkValue(res, R.configVarying.simple, "simple large");
723 checkValue(res, R.configVarying.large, "large");
732 checkValue(res, R.configVarying.large, "large")
[all...] |
| /development/samples/HoneycombGallery/src/com/example/android/hcgallery/ |
| MainActivity.java | 50 * When running on a "large" or larger screen, this activity displays both the
278 // Notifications in Android 3.0 now have a standard mechanism for displaying large
280 // appropriate size for large bitmaps in notifications.
|
| /external/chromium_org/ash/ |
| ash_switches.cc | 37 // kAshDefaultWallpaper{Large,Small} are OEM-specific (i.e. they are not
42 const char kAshDefaultWallpaperLarge[] = "ash-default-wallpaper-large";
140 const char kAshGuestWallpaperLarge[] = "ash-guest-wallpaper-large";
|
| /external/chromium_org/remoting/host/linux/ |
| x_server_clipboard.cc | 182 // TODO(lambroslambrou): Properly support large transfers -
186 // If the property is zero-length then the large transfer is complete.
204 // Large selection - just read and ignore these for now.
|
| /external/chromium_org/third_party/freetype/src/smooth/ |
| ftsmooth.c | 160 FT_ERROR(( "ft_smooth_render_generic: glyph too large:"
171 FT_ERROR(( "ft_smooth_render_generic: glyph too large:"
239 FT_ERROR(( "ft_smooth_render_generic: glyph too large: %u x %u\n",
|
| /external/chromium_org/third_party/icu/ |
| icu4c.css | 321 font-size: large;
326 font-size: large;
332 font-size: large;
|
| /external/chromium_org/third_party/icu/source/test/iotest/ |
| stream.cpp | 152 /* Test large buffer (size > 200) when using '<<' and UnicodeString */
179 log_err("Large UnicodeString operator << output incorrect.\n");
182 log_err("Error converting string for large stream buffer testing.\n");
|
| /external/chromium_org/third_party/tcmalloc/vendor/doc/ |
| tcmalloc.html | 35 For small objects, there is virtually zero contention. For large
90 differently from larger objects. Large objects are allocated directly
92 aligned region of memory). I.e., a large object is always
199 <h2><A NAME="Large_Object_Allocation">Large Object Allocation</A></h2>
201 <p>A large object size (> 32K) is rounded up to a page size (4K)
228 either a large object that has been handed off to the application, or
260 <p>If the object is large, the span tells us the range of pages covered
290 lists. Some threads need large caches to perform well while others
445 large number of threads, whereas PTMalloc achieves generally 0.5-1
449 to zero for large numbers of threads (i.e. with PTMalloc, lots of CP
[all...] |
| /external/chromium_org/third_party/tcmalloc/vendor/src/ |
| common.h | 55 // Using large pages speeds up the execution at a cost of larger memory use.
59 // As the number of size classes increases with large pages, we increase
124 // an unreasonably large value if bytes is huge enough.
|
| /external/chromium_org/ui/gfx/ |
| icon_util.h | 62 // The size of the large icon entries in .ico files on Windows Vista+.
66 // image, even at the large or extra large icons views.
|
| /external/chromium_org/ui/message_center/views/ |
| bounded_label_unittest.cc | 181 // - Empty and very large strings
182 // - Zero, very large, and negative line limit values
205 // Large width values should yield all words on one line.
|
| /external/chromium_org/v8/test/webkit/ |
| dfg-arith-add-overflow-check-elimination-tower-of-large-numbers-expected.txt | 24 Tests that if we have a tower of large numerical constants being added to each other, the DFG knows that a sufficiently large tower may produce a large enough value that overflow check elimination must be careful.
|
| /external/compiler-rt/lib/asan/tests/ |
| asan_mem_test.cc | 53 // Large OOB, we find it only if the redzone is large enough.
109 // fprintf(stderr, " large oob memset: %p %p %zd\n", x1, x2, size);
|
| /external/e2fsprogs/intl/ |
| printf-parse.c | 151 /* n too large, would lead to out of memory later. */
221 /* n too large, would lead to out of memory later. */
278 /* n too large, would lead to out of memory
|
| /external/eigen/doc/ |
| A10_Eigen2SupportModes.dox | 20 By defining EIGEN2_SUPPORT before including any Eigen 3 header, you get back a large part of the Eigen 2 API, while keeping the Eigen 3 API and ABI unchanged.
28 The primary reason why EIGEN2_SUPPORT alone may not be enough to migrate a large project from Eigen 2 to Eigen 3 is that some of the Eigen 2 API is inherently incompatible with the Eigen 3 API. This happens when the same identifier is used in Eigen 2 and in Eigen 3 with different meanings. To help migrate projects that rely on such API, we provide a staged migration path allowing to perform the migration \em incrementally.
88 Stage 40 is the first where it's "comfortable" to stay for a little longer period, since it preserves 100% Eigen 3 compatibility. However, we still encourage you to complete your migration as quickly as possible. While we do run the Eigen 2 test suite against Eigen 3's stage 10 support mode, we can't guarantee the same level of support and quality assurance for Eigen 2 support as we do for Eigen 3 itself, especially not in the long term. \ref Eigen2ToEigen3 "This page" describes a large part of the changes that you may need to perform.
|
| /external/freetype/src/smooth/ |
| ftsmooth.c | 160 FT_ERROR(( "ft_smooth_render_generic: glyph too large:"
171 FT_ERROR(( "ft_smooth_render_generic: glyph too large:"
239 FT_ERROR(( "ft_smooth_render_generic: glyph too large: %u x %u\n",
|
| /external/icu4c/ |
| icu4c.css | 321 font-size: large;
326 font-size: large;
332 font-size: large;
|
| /external/jpeg/ |
| cjpeg.1 | 100 index of a large image library, for example. Try
151 Set limit for amount of memory to use in processing large images. Value is
185 JPEG file and a better-looking image. Too large a smoothing factor will
|
| /external/libvpx/libvpx/examples/includes/geshi/geshi/ |
| css.php | 110 'katakana-iroha', 'katakana', 'landscape', 'larger', 'large',
131 'white', 'wider', 'x-fast', 'x-high', 'x-large', 'x-loud',
132 'x-low', 'x-small', 'x-soft', 'xx-large', 'xx-small', 'yellow',
|
| /external/llvm/include/llvm/ADT/ |
| SmallPtrSet.h | 32 /// for small and one for large sets.
38 /// array, we grow into the 'large set' case. SmallSet should be used when the
42 /// Large sets use a classic exponentially-probed hash table. Empty buckets are
|
| /external/llvm/include/llvm/CodeGen/ |
| CommandFlags.h | 67 clEnumValN(CodeModel::Large, "large",
68 "Large code model"),
|
