OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:devices
(Results
51 - 75
of
1889
) sorted by null
1
2
3
4
5
6
7
8
9
10
11
>>
/packages/apps/Calendar/res/values-xlarge/
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 -->
/system/bluetooth/data/
audio.conf
6
#
devices
, and the local device is a Source
29
# service interacts with remote headset
devices
)
36
# Maximum number of connected HSP/HFP
devices
per adapter. Defaults to 1
/development/samples/USB/MissileLauncher/
README.txt
8
- filtering for multiple
devices
based on vendor and product IDs (see device_filter.xml)
/device/samsung/tuna/recovery/
Android.mk
17
# Edify extension functions for doing bootloader updates on Tuna
devices
.
/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/e2fsprogs/lib/blkid/
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
*/
118
* Priority settings for different types of
devices
/external/oprofile/events/x86-64/family15h/
events
4
# Copyright (c) 2006-2010 Advanced Micro
Devices
/external/webkit/Source/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/
BluetoothProfile.java
91
* Default priority for
devices
that we try to auto-connect to and
98
* Default priority for
devices
that allow incoming
105
* Default priority for
devices
that does not allow incoming
118
* Get connected
devices
for this specific profile.
120
* <p> Return the set of
devices
which are in state {@link #STATE_CONNECTED}
124
* @return List of
devices
. The list will be empty on error.
129
* Get a list of
devices
that match any of the given connection
132
* <p> If none of the
devices
match any of the given states,
140
* @return List of
devices
. The list will be empty on error.
/frameworks/base/core/java/android/hardware/usb/
package.html
4
devices
. Use {@link android.hardware.usb.UsbManager} to access the state of the USB and to
/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.
/packages/apps/Settings/src/com/android/settings/bluetooth/
BluetoothDeviceFilter.java
42
/** Bonded
devices
only filter (referenced directly). */
45
/** Unbonded
devices
only filter (referenced directly). */
77
/** Filter that matches all
devices
. */
84
/** Filter that matches only bonded
devices
. */
91
/** Filter that matches only unbonded
devices
. */
107
/** Filter that matches
devices
that support AUDIO profiles. */
128
/** Filter that matches
devices
that support Object Transfer. */
142
/** Filter that matches
devices
that support PAN User (PANU) profile. */
156
/** Filter that matches
devices
that support NAP profile. */
/prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/X11/extensions/
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
/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
/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 as driven by flagship Android
devices
. This allows developers
117
manufacturer begins mass producing
devices
, and we turn to releasing th
[
all
...]
/docs/source.android.com/src/
faqs.md
31
cell phone and other
devices
.
70
devices
running Android actually make it to market.
82
We focus on releasing great
devices
into a competitive marketplace, and
87
on a small number of "flagship"
devices
, and develops the next version of
89
devices
absorb much of the product risk and blaze a trail for the broad OEM
90
community, who follow up with many more
devices
that take advantage of the
92
according to the actual needs of real-world
devices
.
100
devices
. This branch is kept suitable for release at all times.
125
of the platform as driven by flagship Android
devices
. This allows developers
156
manufacturer begins mass producing
devices
, and we turn to releasing th
[
all
...]
/development/pdk/docs/about/
index.jd
6
other
devices
. The Android Open Source Project (AOSP), led by Google, is
8
manufacturers have brought to market
devices
running Android, and they are
/development/pdk/docs/compatibility/
overview.jd
5
manufacturers to develop compatible Android
devices
.</p>
9
<p>Each group depends on the others. Users want a wide selection of
devices
11
for their apps with many
devices
in users' hands; device manufacturers rely
17
developers.</b><p>Without a strong compatibility standard,
devices
can vary so
19
for different
devices
. The compatibility program provides a precise definition
27
Android
devices
will differ in hardware and software capabilities, so the
34
manufacturers the flexibility to create unique
devices
that are nonetheless
85
attached
devices
or an emulator. The CTS is a set of unit tests designed to be
/docs/source.android.com/src/compatibility/
overview.md
20
manufacturers to develop compatible Android
devices
.
27
Each group depends on the others. Users want a wide selection of
devices
29
for their apps with many
devices
in users' hands; device manufacturers rely
37
Without a strong compatibility standard,
devices
can vary so
39
for different
devices
. The compatibility program provides a precise definition
48
Android
devices
will differ in hardware and software capabilities, so the
57
manufacturers the flexibility to create unique
devices
that are nonetheless
114
attached
devices
or an emulator. The CTS is a set of unit tests designed to be
/external/qemu/hw/
sysbus.h
4
/*
Devices
attached directly to the main system bus. */
52
/* Legacy helper function for creating
devices
. */
/external/quake/quake/src/QW/client/
input.h
20
// input.h -- external (non-keyboard) input
devices
27
// oportunity for
devices
to stick commands on the script buffer
/external/quake/quake/src/WinQuake/
input.h
20
// input.h -- external (non-keyboard) input
devices
27
// oportunity for
devices
to stick commands on the script buffer
/frameworks/base/docs/html/guide/topics/wireless/
index.jd
17
wirelessly exchange data with other Bluetooth
devices
. The application framework provides access to
19
wirelessly connect to other Bluetooth
devices
, enabling point-to-point and multipoint wireless
Completed in 502 milliseconds
1
2
3
4
5
6
7
8
9
10
11
>>