/frameworks/base/services/usage/java/com/android/server/usage/ |
D | IntervalStats.java | 31 public final ArrayMap<Configuration, ConfigurationStats> configurations = new ArrayMap<>(); field in IntervalStats 62 ConfigurationStats configStats = configurations.get(config); in getOrCreateConfigurationStats() 68 configurations.put(config, configStats); in getOrCreateConfigurationStats() 144 ConfigurationStats activeStats = configurations.get(activeConfiguration); in updateConfigurationStats()
|
D | UsageStatsXmlV1.java | 206 statsOut.configurations.clear(); in read() 260 final int configCount = stats.configurations.size(); in write() 262 boolean active = stats.activeConfiguration.equals(stats.configurations.keyAt(i)); in write() 263 writeConfigStats(xml, stats, stats.configurations.valueAt(i), active); in write()
|
D | UserUsageStatsService.java | 259 accResult.addAll(stats.configurations.values()); 263 final int configCount = stats.configurations.size(); 265 accResult.add(new ConfigurationStats(stats.configurations.valueAt(i))); 602 final ArrayMap<Configuration, ConfigurationStats> configStats = stats.configurations; in printIntervalStats()
|
/frameworks/base/core/java/android/hardware/camera2/params/ |
D | StreamConfigurationMap.java | 92 StreamConfiguration[] configurations, in StreamConfigurationMap() argument 102 if (configurations == null) { in StreamConfigurationMap() 109 mConfigurations = checkArrayElementsNotNull(configurations, "configurations"); in StreamConfigurationMap() 172 if (configurations != null && in StreamConfigurationMap() 1287 StreamConfiguration[] configurations = in getInternalFormatSizes() local 1290 for (StreamConfiguration config : configurations) { in getInternalFormatSizes() 1421 StreamConfiguration[] configurations = in isSupportedInternalConfiguration() local 1424 for (int i = 0; i < configurations.length; i++) { in isSupportedInternalConfiguration() 1425 if (configurations[i].getFormat() == format && in isSupportedInternalConfiguration() 1426 configurations[i].getSize().equals(size)) { in isSupportedInternalConfiguration()
|
/frameworks/data-binding/compilerCommon/ |
D | build.gradle | 48 classpath configurations.runtime 55 classpath configurations.runtime
|
/frameworks/base/docs/html/guide/practices/ |
D | screens-distribution.jd | 38 configurations of screen size and density, you can instead choose to limit the distribution of your 41 Google Play by adding elements to your manifest file that specify the screen configurations your 44 <p>However, before you decide to restrict your application to certain screen configurations, you 59 versions of your application for different screen configurations. In such a case, you can use the <a 76 because each screen size has four density configurations. You must declare each one of 193 <supports-screens>}</a> only when you cannot provide compatibility on all screen configurations 195 configurations.</p> 203 application when each APK supports a different set of screen configurations (as declared in 212 APK that can support a wide range of device configurations</strong>. Supporting multiple screen
|
D | screens-support-1.5.jd | 37 configurations and added APIs that allow applications to control how they operate on different 38 screens, using alternative resources for different screen configurations.</p> 74 different screen configurations. You should be able to make these changes to your application such 147 complete support for different screen configurations.</p>
|
D | compatibility.jd | 38 configurations.</p> 77 device configuration. Because Android runs on a wide range of device configurations, some features … 96 device configurations as possible using a single APK. In most situations, you can do so by 99 with alternatives for different configurations (such as different layouts for different 262 To simplify the different configurations, Android generalizes these variants into groups that make 317 configurations.
|
D | screens_support.jd | 73 design for different screen configurations. For example, you might want a UI for tablets 83 displays properly and provides an optimized user experience on all supported screen configurations, 104 configurations that the system supports, and an overview of the API and underlying 153 densities, reflecting the many different screen configurations that a device may have. You can use 295 different screen configurations.</p> 305 for the screen density, as appropriate. To more gracefully handle different screen configurations, 452 provide special resources for different screen configurations.</p> 574 configuration qualifiers (not just for screen configurations), see 612 you test your application on different screen configurations. For example:</p> 731 <p>The different resource configurations that you can specify based on the space available for your [all …]
|
/frameworks/data-binding/developmentPlugins/localizeMavenPlugin/src/main/groovy/android/databinding/ |
D | MavenDependencyCollectorTask.groovy | 50 project.configurations.each { conf -> 53 project.buildscript.configurations.each { conf ->
|
/frameworks/base/docs/html/guide/topics/resources/ |
D | overview.jd | 25 configurations such as different languages or screen sizes, which becomes increasingly 26 important as more Android-powered devices become available with different configurations. In order 27 to provide compatibility with different configurations, you must organize resources in your 72 alternative resources for specific device configurations.</dd>
|
D | runtime-changes.jd | 24 <p>Some device configurations can change during runtime 29 application adapt to new configurations by automatically reloading your application with 61 changes, but receive a callback when the configurations do change, so that you can manually update 213 <p>Now, when one of these configurations change, {@code MyActivity} does not restart. 255 configurations, not just the ones that have changed. Most of the time, you won't care exactly how
|
D | index.jd | 54 configurations.</p>
|
/frameworks/base/core/java/android/hardware/usb/ |
D | UsbDevice.java | 299 … Parcelable[] configurations = in.readParcelableArray(UsbInterface.class.getClassLoader()); 302 device.setConfigurations(configurations);
|
/frameworks/base/tools/aapt2/ |
D | todo.txt | 27 X Generate resource tables for all configurations.
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | compatible-screens-element.jd | 31 with specific screen configurations and enable filtering for users. Any screen configuration that is 40 application absolutely does not work with specific screen configurations. Instead of using this 114 because each screen size has four different density configurations. You must declare each one of
|
/frameworks/base/docs/html/google/play/publishing/ |
D | multiple-apks.jd | 11 device configurations</li> 58 for your application that are each targeted to different device configurations. Each APK is a 67 alternative resources for different configurations (for example, different layouts for different 69 a few cases, however, a single APK is unable to support all device configurations, because 74 many device configurations as possible, doing so is sometimes not possible. To help 95 different device configurations <strong>only when your APK is too large</strong> (greater than 96 50MB) due to the alternative resources needed for different device configurations. 97 Using a single APK to support different configurations is always the best practice, 159 specific set of device configurations. However, there are several rules based on the manifest 226 applications to support all screen configurations with a single APK. You should avoid creating [all …]
|
/frameworks/data-binding/compiler/ |
D | build.gradle | 71 from { configurations.compile.collect { it.isDirectory() ? it : zipTree(it) } }
|
/frameworks/base/docs/html/training/basics/supporting-devices/ |
D | index.jd | 29 as possible on Android, your app needs to adapt to various device configurations. Some of the
|
/frameworks/data-binding/library/ |
D | build.gradle | 56 configurations {
|
/frameworks/base/docs/html/tools/devices/ |
D | managing-avds.jd | 23 to create and manage Android virtual devices (AVDs), which define device configurations 98 configurations such as the screen size, memory options, input type, and sensors.</p> 325 <li>Specify additional hardware-specific device configurations an <code>hardware.ini</code>
|
/frameworks/base/docs/html/training/basics/fragments/ |
D | index.jd | 65 <dd>Learn how to build your app with layouts that provide different fragment configurations for
|
/frameworks/base/docs/html/about/dashboards/ |
D | index.jd | 79 you design your user interfaces for different screen configurations, Android divides the range of 82 <p>For information about how you can support multiple screen configurations in your 93 <br/>Any screen configurations with less than 0.1% distribution are not shown.</em></p>
|
/frameworks/base/docs/html/guide/ |
D | index.jd | 53 for different device configurations. For example, you can create different XML
|
/frameworks/base/docs/html/guide/topics/ui/ |
D | index.jd | 49 optimized for several screen configurations.</p>
|