| /frameworks/base/services/jni/ |
| D | com_android_server_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/base/docs/html/training/connect-devices-wirelessly/ |
| D | index.jd | 29 enable communication with other devices on the same local network, and even
30 devices which are not on a network, but are physically nearby. The addition of
38 connecting to other devices from your application. Specifically, it
53 <dd>Learn how to fetch a list of nearby peer devices, create an access point
54 for legacy devices, and connect to other devices capable of Wi-Fi Direct
58 <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/guide/webapps/ |
| D | best-practices.jd | 13 <p>Developing web pages and web applications for mobile devices presents a different set of
17 devices.</p>
21 <li>Redirect mobile devices to a dedicated mobile version of your web site
26 devices. If necessary, you can also identify the specific operating system in the User Agent string
28 <p class="note"><strong>Note:</strong> Large screen Android-powered devices that should be served
36 <li>Use a valid markup DOCTYPE that's appropriate for mobile devices
39 ensures specific markup for your web site that works best on mobile devices. For instance, it does
40 not allow HTML frames or nested tables, which perform poorly on mobile devices. Along with the
65 <p>For more information about how to use viewport meta data for Android-powered devices, read <a
71 <p>Because mobile devices typically have a connection speed far slower than a desktop
|
| D | overview.jd | 12 client-side application (developed using the Android SDK and installed on user devices as an {@code
14 browser—there's nothing to install on user devices).</p>
49 <p>To develop a web application for Android-powered devices, you should read the
55 <dd>How to properly size your web app on Android-powered devices and support
57 application that you at least expect to be available on Android-powered devices (which you should
58 assume for anything you publish on the web), but especially if you're targeting mobile devices
69 Android-powered devices.</dd>
|
| /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/guide/practices/ |
| D | compatibility.jd | 33 <p>Android is designed to run on many different types of devices. For
34 developers, the range and number of devices means a huge potential audience: the
35 more devices that run Android apps, the more users who can access your app. In
41 what types of devices your app is available to. With a bit of forethought and
43 whose devices can’t run your app will never see it on Google Play, and
45 control which devices have access to your apps, and how to prepare your apps to
61 devices. Every compatible Android device your app will land on will include
66 Android to prevent apps from being visible to devices which don’t have features
73 only the devices capable of running them.</p>
85 <li>Google Play uses your app’s stated requirements to filter it from devices
[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>
|
| D | optimizing-for-3.0.jd | 39 <li><a href="#FilteringTabletApps">Filtering a tablet app from mobile devices</a></li>
65 you to enhance your user's experience on tablets and similar devices. Any application you've already
66 published is compatible with devices running Android 3.0, by default, because Android applications
67 are forward-compatible. However, new tablet devices running Android 3.0 are now available to the
82 <li><a href="#Optimizing">Optimize your app for tablets and similar devices</a>.
88 <li><a href="#Upgrading">Upgrade or develop a new app for tablets and similar devices</a>.
90 Android 3.0 or create a new application targeted to tablets and similar devices. Compared to
99 for tablets and similar devices.</li>
122 <li><a href="{@docRoot}tools/devices/managing-avds.html">Create an AVD</a> for a tablet-type
171 APIs, your app should work fine on devices running Android 3.0. However, in order to provide users
[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/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/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/design/style/ |
| D | index.jd | 23 …<a href="{@docRoot}design/style/devices-displays.html" class="landing-page-link">Devices and Displ…
26 <a href="{@docRoot}design/style/devices-displays.html">
|
| /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/guide/topics/connectivity/ |
| D | bluetooth.jd | 11 other devices</li>
21 <li><a href="#QueryingPairedDevices">Querying paired devices</a></li>
22 <li><a href="#DiscoveringDevices">Discovering devices</a></li>
56 which allows a device to wirelessly exchange data with other Bluetooth devices.
59 connect to other Bluetooth devices, enabling point-to-point and multipoint
65 <li>Scan for other Bluetooth devices</li>
66 <li>Query the local Bluetooth adapter for paired Bluetooth devices</li>
68 <li>Connect to other devices through service discovery</li>
69 <li>Transfer data to and from other devices</li>
78 Bluetooth, finding devices that are either paired or available in the local
[all …]
|
| /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))
|
| /frameworks/base/docs/html/guide/topics/admin/ |
| D | index.jd | 3 …you can take advantage of APIs and system capabilities to manage Android devices and control acces…
16 bring their personal Android devices to work. In this post, we’re going to have a look at the key
|
| /frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/policy/ |
| D | BluetoothController.java | 103 Set<BluetoothDevice> devices = adapter.getBondedDevices(); in updateBondedBluetoothDevices() local
104 if (devices != null) { in updateBondedBluetoothDevices()
105 for (BluetoothDevice device : devices) { in updateBondedBluetoothDevices()
|
| /frameworks/base/docs/html/training/displaying-bitmaps/ |
| D | index.jd | 37 <li>Mobile devices typically have constrained system resources. Android devices can have as little
42 perform under this minimum memory limit. However, keep in mind many devices are configured with
45 camera on the <a href="http://www.android.com/devices/detail/galaxy-nexus">Galaxy Nexus</a> takes
49 per-app limit on some devices.</li>
|
| /frameworks/base/docs/html/about/dashboards/ |
| D | index.jd | 26 about your users' devices. Those stats may help you prioritize the device profiles for which
30 <p>This page provides information about the relative number of devices that share a certain
33 href="{@docRoot}training/basics/supporting-devices/index.html">supporting different devices</a>.</p>
35 <p>Each snapshot of data represents all the devices that visited the Google Play Store in the
47 <p>This section provides data about the relative number of devices running a given version of
50 <p>For information about how to target your application to devices based on
52 href="{@docRoot}training/basics/supporting-devices/platforms.html">Supporting Different
72 <p>This section provides data about the relative number of devices that have a particular
98 <p>This section provides data about the relative number of devices that support a particular
410 // if there are any devices of this size
|
| /frameworks/base/docs/html/training/backward-compatible-ui/ |
| D | older-implementation.jd | 34 …n discusses how to create an implementation that mirrors newer APIs yet supports older devices.</p>
60 … for backporting newer UI components to older devices. Be mindful of the user experience: on older…
104 // Our activity layout for pre-Honeycomb devices
126 …elper</code>: one that works on devices running Android 3.0 or later and uses new APIs, and anothe…
|
| /frameworks/base/docs/html/tools/help/ |
| D | sdk-manager.jd | 41 on the latest devices, we recommend that you use the latest platform version as your build target.
43 version in order to use new features when running on devices with the latest version of Android.
47 <dd>Recommended. Although you might have one or more Android-powered devices on which to test
50 your app running on them with the <a href="{@docRoot}tools/devices/emulator.html">Android emulator<…
54 plus others not included in the framework at all) on devices running
|