| /frameworks/base/services/core/jni/ |
| D | com_android_server_lights_LightsService.cpp | 67 Devices* devices; in init_native() local
69 devices = (Devices*)malloc(sizeof(Devices)); in init_native()
73 devices->lights[LIGHT_INDEX_BACKLIGHT] in init_native()
75 devices->lights[LIGHT_INDEX_KEYBOARD] in init_native()
77 devices->lights[LIGHT_INDEX_BUTTONS] in init_native()
79 devices->lights[LIGHT_INDEX_BATTERY] in init_native()
81 devices->lights[LIGHT_INDEX_NOTIFICATIONS] in init_native()
83 devices->lights[LIGHT_INDEX_ATTENTION] in init_native()
85 devices->lights[LIGHT_INDEX_BLUETOOTH] in init_native()
87 devices->lights[LIGHT_INDEX_WIFI] in init_native()
[all …]
|
| /frameworks/av/services/audiopolicy/ |
| D | audio_policy.conf | 91 devices {
110 devices speaker
119 devices AUDIO_DEVICE_IN_BUILTIN_MIC
133 devices AUDIO_DEVICE_OUT_REMOTE_SUBMIX
141 devices AUDIO_DEVICE_IN_REMOTE_SUBMIX
|
| /frameworks/base/packages/SystemUI/src/com/android/systemui/qs/tiles/ |
| D | CastTile.java | 97 final Set<CastDevice> devices = mController.getCastDevices(); in handleUpdateState() local
99 for (CastDevice device : devices) { in handleUpdateState()
111 mDetailAdapter.updateItems(devices); in handleUpdateState()
192 private void updateItems(Set<CastDevice> devices) { in updateItems() argument
195 if (devices != null && !devices.isEmpty()) { in updateItems()
197 for (CastDevice device : devices) { in updateItems()
211 for (CastDevice device : devices) { in updateItems()
214 items = new Item[devices.size()]; in updateItems()
218 if (!devices.contains(device)) continue; in updateItems()
|
| /frameworks/base/docs/html/training/tv/start/ |
| D | index.jd | 17 Android offers a rich user experience that's optimized for apps running on large screen devices,
25 existing apps to also run on TV devices. However, the user interaction model for TV is
26 substantially different from phone and tablet devices. In order to make your app successful on TV
27 devices, you must design new layouts that can be easily understood from 10 feet away, and provide
34 hardware features that are not typically available on TV devices.
51 app project to run on TV devices.</dd>
62 features, and manage controller devices.</dd>
|
| D | start.jd | 29 modify your existing apps to also run on TV devices or create new apps based on what you already
41 minimum required changes to enable an app to run on TV devices.
48 This section discusses how to modify an existing app to run on TV devices, or create a new one.
49 These are the main components you must use to create an app that runs on TV devices:
54 declare an activity that is intended to run on TV devices.</li>
57 available for TV devices that provide widgets for building user interfaces.</li>
79 In order to access new APIs for TV devices, you must create a project or modify an existing
87 <p>An application intended to run on TV devices must declare a launcher activity for TV
95 your app, it is not visible to users running the Google Play store on TV devices. Also, if your
149 libraries provide APIs and user interface widgets for use on TV devices. The libraries are
[all …]
|
| D | hardware.jd | 20 TV hardware is substantially different from other Android devices. TVs do not
21 include some of the hardware features found on other Android devices, such as touch screens,
22 cameras, and GPS receivers. TVs are also completely dependent on secondary hardware devices.
30 hardware features, and discusses the requirements for handling controllers for TV devices.
37 If you are building an app that operates both on TV devices and other devices, you may need to
76 TVs have a different purpose from other devices, and so they do not have hardware features that
77 other Android-powered devices often have. For this reason, the Android system does not support
117 not get installed on devices that do not provide those features. If you are extending an existing
127 on TV devices, even though your app may use these features on non-TV devices:
148 devices or appearing in the Android TV home screen launcher.
[all …]
|
| /frameworks/base/docs/html/guide/webapps/ |
| D | index.jd | 13 client-side application (developed using the Android SDK and installed on user devices in an APK)
15 browser—there's nothing to install on user devices).</p>
17 <p>If you chose to provide a web-based app for Android-powered devices, you can rest
30 <p>To start developing web pages for Android-powered devices, see the following documents:</p>
35 <dd>How to properly size your web app on Android-powered devices and support
37 application that you at least expect to be available on Android-powered devices (which you should
38 assume for anything you publish on the web), but especially if you're targeting mobile devices
49 Android-powered devices.</dd>
|
| D | best-practices.jd | 31 <p>Developing web pages and web applications for mobile devices presents a different set of
35 devices.</p>
39 <li>Redirect mobile devices to a dedicated mobile version of your web site
44 devices. If necessary, you can also identify the specific operating system in the User Agent string
46 <p class="note"><strong>Note:</strong> Large screen Android-powered devices that should be served
54 <li>Use a valid markup DOCTYPE that's appropriate for mobile devices
57 ensures specific markup for your web site that works best on mobile devices. For instance, it does
58 not allow HTML frames or nested tables, which perform poorly on mobile devices. Along with the
83 <p>For more information about how to use viewport meta data for Android-powered devices, read <a
89 <p>Because mobile devices typically have a connection speed far slower than a desktop
|
| /frameworks/base/docs/html/training/connect-devices-wirelessly/ |
| D | index.jd | 35 enable communication with other devices on the same local network, and even
36 devices which are not on a network, but are physically nearby. The addition of
44 connecting to other devices from your application. Specifically, it
59 <dd>Learn how to fetch a list of nearby peer devices, create an access point
60 for legacy devices, and connect to other devices capable of Wi-Fi P2P
64 <dd>Learn how to discover services published by nearby devices without being
|
| /frameworks/base/core/java/android/bluetooth/ |
| D | BluetoothManager.java | 171 List<BluetoothDevice> devices = new ArrayList<BluetoothDevice>(); in getDevicesMatchingConnectionStates() local
176 if (iGatt == null) return devices; in getDevicesMatchingConnectionStates()
177 devices = iGatt.getDevicesMatchingConnectionStates(states); in getDevicesMatchingConnectionStates()
182 return devices; in getDevicesMatchingConnectionStates()
|
| /frameworks/base/docs/html/training/multiple-apks/ |
| D | index.jd | 13 <!-- Required platform, tools, add-ons, devices, knowledge, etc. -->
39 the right devices, as well as the smart way to avoid pitfalls such as unnecessary redundancy across
41 devices on Google Play. By going through any of these lessons, you'll know how to develop
42 multiple APKs the smart way, make sure they're targeting the devices you want them to,
56 <dd>Learn how to target Android devices by screen size using multiple APKs. Also learn how to
61 <dd>Learn how to target Android devices based on their support for GL texture. Also learn
66 <dd>Learn how to target different Android devices based on more than one configuration
|
| /frameworks/base/docs/html/about/dashboards/ |
| D | index.jd | 29 about your users' devices. Those stats may help you prioritize the device profiles for which
33 <p>This page provides information about the relative number of devices that share a certain
36 href="{@docRoot}training/basics/supporting-devices/index.html">supporting different devices</a>
37 by revealing which devices are active in the Android and Google Play ecosystem.</p>
39 <p>This data reflects devices running the latest Google Play Store app, which is compatible
40 with Android 2.2 and higher. Each snapshot of data represents all the devices that visited the
45 <p><strong>Note:</strong> Beginning in September, 2013, devices running versions older than Android
46 2.2 do not appear in this data because those devices do not support the new Google Play Store
47 app. Only the new app is able to measure the number of devices that actively visit Google Play Store
54 <p>This section provides data about the relative number of devices running a given version of
[all …]
|
| /frameworks/base/tools/layoutlib/ |
| D | README | 2 …y is to provide layout rendering in Eclipse that are very very close to their rendering on devices.
4 None of the com.android.* or android.* classes in layoutlib run on devices.
|
| /frameworks/base/docs/html/guide/practices/ |
| D | compatibility.jd | 33 <p>Android is designed to run on many different types of devices, from phones
35 the range of devices provides a huge potential audience for your app. In order for your app
36 to be successful on all these devices, it should tolerate some feature variability
46 experience on a variety of devices.
49 which types of devices can install your app from Google Play Store. This page explains how you can
50 control which devices have access to your apps, and how to prepare your apps to make sure they
52 to different devices, read <a href="{@docRoot}training/basics/supporting-devices/index.html"
72 only devices that are Android compatible include Google Play Store. So you can rest assured that
78 available on all devices. For example, some devices may not include a
80 of a compass sensor, then your app is compatible only with devices that
[all …]
|
| D | screens-support-1.5.jd | 35 baseline HVGA screen used on the T-Mobile G1 and similar devices, which is <em>normal</em> screen
61 necessary to support Android 1.5. To see the relative number of devices that are still running
73 need to make some changes to your application in order for it to properly run on newer devices with
75 that you can distribute a single {@code .apk} to all devices.</p>
83 <li>Maintain compatibility with existing devices by leaving your application's <a
86 devices and multiple screens. </li>
87 <li>Extend compatibility for Android 1.6 (and higher) devices by adding <a
129 application will no longer be compatible with devices running on that version.</li>
133 Users of devices with QVGA resolution at low density may want to download your application, so you
136 devices.</p>
|
| /frameworks/base/docs/html/training/search/ |
| D | backward-compat.jd | 32 devices, but want to target Android 3.0 or later versions. When you do this, your application
34 older devices:</p>
44 <p>To invoke the search dialog on older devices, call {@link
46 menu item from the options menu. Because Android 3.0 and higher devices show the
67 android.widget.SearchView} does not occur on older devices. In our example code, this happens in
|
| /frameworks/base/docs/html/guide/topics/connectivity/usb/ |
| D | index.jd | 20 readers; and much more. This gives Android-powered devices that do not have host capabilities the
22 Android-powered devices and must adhere to the <a href=
24 host mode, the Android-powered device acts as the host. Examples of devices include digital
25 cameras, keyboards, mice, and game controllers. USB devices that are designed for a wide range of
38 library to support a broader range of devices. Device manufacturers can choose whether or not to
42 dependant on the device's hardware, regardless of platform level. You can filter for devices that
|
| D | host.jd | 14 <a href="#working-d">Working with devices</a>
40 and enumerates connected USB devices. USB host mode is supported in Android 3.1 and higher.</p>
59 <td>Allows you to enumerate and communicate with connected USB devices.</td>
121 <li>Because not all Android-powered devices are guaranteed to support the USB host APIs,
135 devices that you want to filter. The following list describes the attributes of
138 of USB devices, such as mass storage devices or digital cameras. You can specify none or
196 <p>When users connect USB devices to an Android-powered device, the Android system can determine
201 <li>Discover connected USB devices by using an intent filter to be notified when the user
202 connects a USB device or by enumerating USB devices that are already connected.</li>
212 <p>Your application can discover USB devices by either using an intent filter to be notified when
[all …]
|
| /frameworks/base/docs/html/training/ |
| D | best-ui.jd | 9 devices. Android provides a flexible framework for UI design that allows your app to display
10 different layouts for different devices, create custom UI widgets, and even control aspects
|
| /frameworks/base/docs/html/about/ |
| D | index.jd | 9 <p>Android powers hundreds of millions of mobile devices in more than 190
12 Android devices for the first time and start looking for apps, games,
34 <blockquote>Every day more than 1 million new Android devices are activated worldwide.</blockquote>
60 <blockquote>Easily optimize a single binary for phones, tablets, and other devices.</blockquote>
65 devices—from phones to tablets and beyond.</p>
86 device or create virtual devices that emulate any hardware configuration.</p>
104 devices or focus on specific segments, devices, or ranges of hardware
119 <p>Preinstalled on hundreds of millions of Android devices around the world,
149 than 100 devices with a single app binary, then iterate rapidly to ensure
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | supports-gl-texture-element.jd | 12 they can be installed only on devices that can handle their textures
64 <p>Applications and devices typically declare their supported GL texture
90 Android-powered devices that support OpenGL ES 2.0.</td>
102 <td>ATI texture compression. Available on devices running Adreno GPU, including
104 devices may also declare a <code><supports-gl-texture></code> element with the
113 <td>S3 DXT1 texture compression. Supported on devices running Nvidia Tegra2
119 <td>S3 texture compression, nonspecific to DXT variant. Supported on devices
126 <td>PowerVR texture compression. Available in devices running PowerVR SGX530/540
150 their devices. One of the ways it filters applications is by texture
152 application to various devices, based on the capabilities of their GPUs.</p>
|
| /frameworks/base/docs/html/guide/topics/connectivity/ |
| D | bluetooth.jd | 15 <li><a href="#QueryingPairedDevices">Querying paired devices</a></li>
16 <li><a href="#DiscoveringDevices">Discovering devices</a></li>
50 which allows a device to wirelessly exchange data with other Bluetooth devices.
53 connect to other Bluetooth devices, enabling point-to-point and multipoint
59 <li>Scan for other Bluetooth devices</li>
60 <li>Query the local Bluetooth adapter for paired Bluetooth devices</li>
62 <li>Connect to other devices through service discovery</li>
63 <li>Transfer data to and from other devices</li>
69 and communicating between Android devices. For Bluetooth devices with low power requirements,
77 Bluetooth, finding devices that are either paired or available in the local
[all …]
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-3.1-highlights.jd | 88 peripherals and accessories. Users can attach many types of input devices
94 hardware devices designed to attach to Android-powered devices as USB hosts. When an
103 support for USB on specific devices may vary and is determined by device
127 and pointing devices</h3>
130 Android-powered devices, to create a familiar environment and work more
131 efficiently. One or more input devices can be attached to the system simultaneously
133 driver is needed, in most cases. When multiple devices are connected, users can
137 <p>For pointing devices, the platform supports most types of mouse with a single
138 button and optionally a scroll wheel, as well as similar devices such as
177 that are optimized for use on larger screen devices. The sections below
[all …]
|
| /frameworks/base/docs/html/design/style/ |
| D | index.jd | 24 …<a href="{@docRoot}design/style/devices-displays.html" class="landing-page-link">Devices and Displ…
27 <a href="{@docRoot}design/style/devices-displays.html">
|
| /frameworks/compile/libbcc/gdb_plugin/ |
| D | android-commands.py | 116 devices = self.devices()
117 if len(devices) == 1:
118 self.set_current_device(devices[0])
122 if len(devices) == 0:
125 msg = "Too many devices (" + ", ".join(devices) + ") detected. " \
246 def devices(self): member in ADB
741 devices = adb.devices()
742 if serial in devices:
746 + "device(s): \n" + "\n".join(devices))
|