HomeSort by relevance Sort by last modified time
    Searched full:devices (Results 26 - 50 of 1380) sorted by null

12 3 4 5 6 7 8 91011>>

  /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
lbxopts.h 3 * Copyright 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/simulator/app/
PhoneCollection.h 4 // Our collection of devices.
14 * known devices, and methods for scanning for devices.
  /external/bluetooth/bluez/src/
hcid.conf 7 # Automatically initialize new devices
19 # multi - Allow pairing with already paired devices
27 # Default settings for HCI 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");
  /system/bluetooth/data/
audio.conf 6 # devices, and the local device is a Source
25 # service interacts with remote headset devices)
32 # Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
  /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,
blkidP.h 38 struct list_head bid_devs; /* All devices in the cache */
58 * They are also linked via bit_values for all devices, so one can easily
73 * from the cache. This is to avoid re-probing all devices which were
85 /* This describes an entire blkid cache file and probed devices.
86 * We can traverse all of the found devices via bic_list.
89 * through all devices with a specific tag type (e.g. LABEL).
93 struct list_head bic_devs; /* List head of all devices */
101 #define BLKID_BIC_FL_PROBED 0x0002 /* We probed /proc/partition devices */
119 * Priority settings for different types of 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...]
  /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...]
  /development/pdk/docs/
faqs.jd 11 cell phone and other devices.</p>
44 devices running Android actually make it to market.</p>
53 <p>We focus on releasing great devices into a competitive marketplace, and
57 on a small number of "flagship" devices, and develops the next version of
59 devices absorb much of the product risk and blaze a trail for the broad OEM
60 community, who follow up with many more devices that take advantage of the
62 according to the actual needs of real-world devices.</p>
69 devices. This branch is kept suitable for release at all times.</p>
90 of the platform using the flagship Android devices. This allows developers
117 manufacturer begins mass producing devices, and we turn to releasing th
    [all...]
  /external/bluetooth/bluez/test/
bdaddr.8 32 device specific. For this reason, not all devices are supported, and not all
33 options are supported on all devices.
52 devices only.
58 devices only.
  /external/bluetooth/bluez/tools/
hciattach.8 3 hciattach \- attach serial devices via UART HCI to BlueZ stack
107 devices. In general the following speeds are supported:
111 Supported vendor devices are automatically initialised to their respective
130 specifies the Bluetooth Address to use. Some devices (like the STLC2500)
  /external/webkit/WebKit/android/wds/client/
main.cpp 106 const DeviceList& devices = conn.getDeviceList(); local
107 // host:devices closes the connection, reconnect
111 if (type == Device::NONE && devices.size() > 1) {
114 } else if (devices.size() == 0) {
115 LOGE("No devices connected");
122 device = devices[0]; // grab the only one
125 for (unsigned i = 0; i < devices.size(); i++) {
126 if (devices[i]->type() == type) {
127 device = devices[i];
  /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 */
  /frameworks/base/wifi/java/android/net/wifi/
package.html 10 <p>Remember, not all Android devices are guaranteed to have Wi-Fi functionality.</p>
  /packages/apps/Email/res/xml/
providers_product.xml 4 platform devices should be defined in providers.xml.
senders_product.xml 4 platform devices should be defined in senders.xml.
stores_product.xml 4 platform devices should be defined in stores.xml.
  /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/
virtio_config.h 3 /* Virtio devices use a standardized configuration space to define their
  /system/core/adb/
OVERVIEW.TXT 7 - keep track of all Android devices and emulators instances
19 if to sense the USB ports to know when devices are attached/removed,
22 It thus maintains a list of "connected devices" and assigns a 'state'
28 services and devices.
35 (through USB for devices, through TCP for emulators) and provide a
44 devices when they are in the bootloader or recovery mode.
65 communicate with a device at all. A typical example is "adb devices"
66 which is used to return the list of currently known devices and their
127 - USB transports, for physical devices through USB
  /system/core/rootdir/
init.lowmem.rc 1 # Adjustments to the out-of-memory killer, for devices that are
  /frameworks/base/docs/html/resources/dashboard/
platform-versions.jd 39 <p>This page provides data about the relative number of active devices
42 the development of your application features for the devices currently in
43 the hands of users. For information about how to target your application to devices based on
49 <p>The following pie chart and table is based on the number of Android devices that have accessed
72 <p style="font-size:.9em">* <em>Other: 0.1% of devices running obsolete versions</em></p>
80 active Android devices running different versions of the Android platform. It also provides a
81 valuable perspective of how many devices your application is compatible with, based on the
85 version at the top. This format indicates the total percent of active devices that are compatible
88 compatible with 100% of active devices (and all future versions), because all Android APIs are
90 then it is currently compatible with the percentage of devices indicated on the y-axis, where th
    [all...]

Completed in 1420 milliseconds

12 3 4 5 6 7 8 91011>>