| /external/bluetooth/bluez/test/ |
| test-health-sink | 48 devices = adapter.ListDevices() variable
50 if len(devices) == 0:
51 print "No devices available"
55 for dev in devices:
66 select = devices[pos]
|
| /frameworks/base/core/java/android/bluetooth/ |
| BluetoothDevicePicker.java | 47 * Broadcast when someone want to select one BT device from devices list.
61 /** Ask device picker to show all kinds of BT devices */
63 /** Ask device picker to show BT devices that support AUDIO profiles */
65 /** Ask device picker to show BT devices that support Object Transfer */
67 /** Ask device picker to show BT devices that support
70 /** Ask device picker to show BT devices that support Network Access Point (NAP) profile */
|
| /frameworks/base/core/java/android/hardware/usb/ |
| UsbConstants.java | 111 * USB class for audio devices.
115 * USB class for communication devices.
119 * USB class for human interface devices (for example, mice and keyboards).
123 * USB class for physical devices.
127 * USB class for still image devices (digital cameras).
135 * USB class for mass storage devices.
143 * USB class for CDC devices (communications device class).
147 * USB class for content smart card devices.
151 * USB class for content security devices.
155 * USB class for video devices
[all...] |
| /development/pdk/docs/ |
| README | 3 engineers doing building devices) is also built as part of the site build.
8 compatibility -- information about building compatible devices
|
| /development/samples/USB/AdbTest/ |
| _index.html | 5 connecting to multiple devices and running multiple <code>adb</code> commands simultaneously.</p>
10 <li>Matching devices based on interface class, subclass and protocol (see <code>device_filter.xml</code>)</li>
|
| /docs/source.android.com/src/source/ |
| sidebar.md | 6 - [Building for Devices](building-devices.html)
|
| /frameworks/base/data/etc/ |
| android.hardware.location.xml | 17 <!-- These are the location features for devices that do not include GPS. Note
18 that network location is required for all devices. -->
|
| /frameworks/base/docs/html/guide/appendix/ |
| index.jd | 7 <dt><a href="g-app-intents.html">Intents List: Invoking Google Applications on Android Devices</a></dt>
8 <dd>Intents you can send to invoke Google applications on Android devices.</dd>
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/ |
| plugin.properties | 5 view.name.Devices = Devices
|
| /build/target/board/vbox_x86/ |
| README.txt | 4 Most of the Android devices (networking, phones, sound, etc) do not work.
|
| /external/bluetooth/bluez/scripts/ |
| bluetooth-hid2hci.rules | 6 # Variety of Dell Bluetooth devices - match on a mouse device that is
8 # Known supported devices: 413c:8154, 413c:8158, 413c:8162
13 # Logitech devices
27 # CSR devices
|
| /external/oprofile/events/x86-64/family15h/ |
| unit_masks | 4 # Copyright (c) 2006-2010 Advanced Micro Devices
|
| /external/qemu/hw/ |
| boards.h | 1 /* Declarations for use by board files for creating devices. */
|
| /frameworks/base/core/java/android/app/admin/ |
| package.html | 5 require rich control over employee devices.</p>
|
| /frameworks/base/core/java/android/hardware/ |
| package.html | 4 not all Android-powered devices support all hardware features, so you should declare hardware
|
| /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/X11/extensions/ |
| lbxbuf.h | 3 * Copyright 1988, 1989, 1990, 1994 Network Computing Devices, Inc.
9 * documentation, and that the name Network Computing Devices, Inc. not be
13 * THIS SOFTWARE IS PROVIDED `AS-IS'. NETWORK COMPUTING DEVICES, INC.,
17 * COMPUTING DEVICES, INC., BE LIABLE FOR ANY DAMAGES WHATSOEVER, INCLUDING
|
| /development/samples/ActionBarCompat/ |
| _index.html | 17 <p>This sample shows how to use the action bar design pattern on pre-API 11 devices and the built-in
18 <a href="../../../reference/android/app/ActionBar.html">ActionBar</a> on devices supporting API
19 11 or greater. The example 'compatible' action bar, instantiated on pre-Android 3.0 devices,
|
| /external/kernel-headers/original/linux/ |
| node.h | 8 * Basic handling of the devices is done in drivers/base/node.c
9 * and system devices are handled in drivers/base/sys.c.
11 * Nodes are exported via driverfs in the class/node/devices/
|
| /sdk/hierarchyviewer/src/com/android/hierarchyviewer/ui/action/ |
| ShowDevicesAction.java | 32 putValue(NAME, "Devices");
33 putValue(SHORT_DESCRIPTION, "Devices");
34 putValue(LONG_DESCRIPTION, "Show Devices");
|
| /development/samples/BluetoothChat/src/com/example/android/BluetoothChat/ |
| DeviceListActivity.java | 41 * This Activity appears as a dialog. It lists any paired devices and
42 * devices detected in the area after discovery. When a device is chosen
79 // Initialize array adapters. One for already paired devices and
80 // one for newly discovered devices
84 // Find and set up the ListView for paired devices
89 // Find and set up the ListView for newly discovered devices
105 // Get a set of currently paired devices
108 // If there are paired devices, add each one to the ArrayAdapter
143 // Turn on sub-title for new devices
155 // The on-click listener for all devices in the ListView
[all...] |
| /external/e2fsprogs/lib/blkid/ |
| libblkid.3.in | 20 library is used to identify block devices (disks) as to their content (e.g.
31 than root, or those not in the "disk" group) to locate devices by label/id.
38 multiple devices, use of the cache is highly recommended (even if empty) as
39 devices will be scanned at most one time and the on-disk cache will be
42 In some cases (modular kernels), block devices are not even visible until
44 some way to locate these devices without enumerating only visible devices,
|
| /frameworks/base/docs/html/guide/webapps/ |
| 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 deskto
[all...] |
| /development/tools/labpretest/ |
| README | 13 and can also be used to verify that lab infrastructure is ready for devices.
14 The idea is to run this script at the same time for multiple devices, typically
15 I would connect 8 devices to a host and run this script in 8 separate shell
23 have multiple devices attached use the -d <device_id> parameter to target a
24 specific devices. Additional parameters are -i for how many cycles and -m for
28 Adding support for new devices or from scratch:
|
| /frameworks/base/docs/html/guide/practices/ |
| compatibility.jd | 32 <p>Android is designed to run on many different types of devices. For
33 developers, the range and number of devices means a huge potential audience: the
34 more devices that run Android apps, the more users who can access your app. In
40 what types of devices your app is available to. With a bit of forethought and
42 whose devices can?t run your app will never see it in the Android Market, and
44 control which devices have access to your apps, and how to prepare your apps to
60 devices. Every compatible Android device your app will land on will include
65 Android to prevent apps from being visible to devices which don?t have features
72 only the devices capable of running them.</p>
82 <li>Devices are required to declare the features they include to Androi
[all...] |
| /packages/apps/Calendar/res/values/ |
| config.xml | 16 <!-- supported only for x-large devices -->
19 <!-- not supported for X-large devices -->
22 <!-- the "show details" mode is recommended for devices with large screens -->
|
