| /external/bluetooth/bluez/tools/ |
| rfcomm.1 | 39 prints information about the configured RFCOMM devices.
46 Prints information about all configured RFCOMM devices.
124 is specified for the RFCOMM device, then all devices that have
|
| /external/e2fsprogs/misc/ |
| base_device.c | 63 * For md devices, we treat them all as if they were all
71 /* Handle DAC 960 devices */
81 /* Now let's handle /dev/hd* and /dev/sd* devices.... */
|
| /external/webkit/Source/WebKit/android/wds/client/ |
| AdbConnection.cpp | 50 // Some commands (host:devices for example) close the connection so we call
186 if (!sendRequest("host:devices")) {
205 // Grab the list of devices. The format is as follows:
|
| /frameworks/base/docs/html/resources/articles/ |
| live-wallpapers.jd | 77 To ensure that your application can only be installed on devices that support
92 displays your application only to users whose devices support live wallpapers,
93 while hiding it from other devices on which it would not be able to run. For
|
| index.jd | 8 <dd>Mobile devices often have limited memory, and memory leaks can cause your application to waste this valuable resource without your knowledge. This article provides tips to help you avoid common causes of memory leaks on the Android platform.</dd>
13 <dd>The Android platform strives to ensure backwards compatibility. However, sometimes you want to use new features which aren't supported on older platforms. This article discusses strategies for selectively using these features based on availability, allowing you to keep your applications portable across a wide range of devices.</dd>
23 <dd>Input Method Editors (IMEs) provide the mechanism for entering text into text fields and other Views. Android devices come bundled with at least one IME, but users can install additional IMEs. This article covers the basics of developing an IME for the Android platform.</dd>
83 <dd>Live wallpapers are richer, animated, interactive backgrounds that users can display in their home screens. Learn how to create a live wallpaper and bundle it in an application that users can install on their devices.</dd>
98 <dd>Quick Search Box (QSB) is a powerful, system-wide search framework. QSB makes it possible for users to quickly and easily find what they're looking for, both on their devices and on the web. This article discusses how to work with the QSB framework to add new search results for an installed application.</dd>
133 <dd>This article discusses the improved Contacts API introduced in Android 2.0 and how to use it to manage and integrate contacts from multiple accounts and data sources. The article also discusses techniques for using the new API on devices that support it, while maintaining backward compatibility with the old API on other devices. </dd>
|
| /frameworks/base/services/java/com/android/server/usb/ |
| UsbService.java | 67 /* Returns a list of all currently attached USB devices (host mdoe) */
68 public void getDeviceList(Bundle devices) {
70 mHostManager.getDeviceList(devices);
|
| /hardware/ti/omap3/omx/system/src/openmax_il/perf/tests/ |
| armtime | 84 /^[0-9]+ / { # /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state lines
218 cat /proc/uptime /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state >$my_log
225 cat /proc/uptime /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state >>$my_log
|
| /ndk/docs/ |
| CPU-ARM-NEON.html | 32 Not all ARMv7-based Android devices will support NEON, but those that
90 As said previously, NOT ALL ARMv7-BASED ANDROID DEVICES WILL SUPPORT NEON !
127 a NEON-optimized one for devices that support it.
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.tests/src/com/android/ide/eclipse/adt/internal/sdk/ |
| config_sample.xml | 17 <d:layout-devices
19 xmlns:d="http://schemas.android.com/sdk/android/layout-devices/1">
137 </d:layout-devices>
|
| /sdk/sdkmanager/app/tests/com/android/sdkmanager/ |
| MainTest.java | 57 assertEquals("[P Available Android Virtual Devices:\n]", getLog().toString());
79 "[P Available Android Virtual Devices:\n"
109 "[P Available Android Virtual Devices:\n"
|
| /frameworks/base/docs/html/sdk/ |
| RELEASENOTES.jd | 55 you use to create applications for compliant Android-powered devices. </p>
67 your <a href="{@docRoot}guide/developing/devices/managing-avds.html">Android Virtual
68 Devices</a> and download new SDK packages (such as platform versions and
225 <a href="{@docRoot}guide/developing/devices/managing-avds.html#createavd">Creating an
235 <li>The issue preventing adb from recognizing Samsung Galaxy devices (linux SDK
250 Android-powered devices, includes fixes to the permissions-checking
300 Magic devices. For other devices, contact the device manufacturer
321 you use to create applications for compliant Android-powered devices. </p>
333 <li>Introduces <a href="{@docRoot}guide/developing/devices/managing-avds.html">Androi
[all...] |
| android-4.0-highlights.jd | 116 from apps, and much more. On smaller-screen devices, notifications appear at the
117 top of the screen, while on larger-screen devices they appear in the System
139 <p>On smaller-screen devices, the home screen now includes a customizable
238 <p>Mobile devices can make extensive use of network data for streaming content,
259 support users on new devices that use virtual buttons in the System Bar, rather
449 across all of their devices. Android 4.0 adds new browsing and email
526 NFC-enabled devices, It lets people instantly exchange favorite apps, contacts,
549 option that lets users unlock their devices with their faces. It takes advantage
552 unlocking the device. Users just hold their devices in front of their faces to
559 nearby peer devices over Wi-Fi, for more reliable, higher-speed communication
[all...] |
| /frameworks/base/docs/html/guide/appendix/ |
| market-filters.jd | 9 <li>Android Market applies filters that control which Android-powered devices can access your
92 user's registered devices for compatibility, though, and only allows them to install the application
134 devices. </p>
139 Market makes the application available to both normal- and large-screen devices,
141 devices.</p>
155 devices that have normal or larger screens. </p>
171 devices, users, unless other filters apply. </p>
177 devices, unless other filters apply. </p>
198 request certain hardware features, and Android Market will show the app only on devices that have the required hardware.</p>
287 application requires a camera and should not be shown to users whose devices d
[all...] |
| api-levels.jd | 35 application's compatibility with devices on which it may be installed. </p>
267 <p>Forward compatibility is important because many Android-powered devices
299 likely to be many devices in the field that run earlier versions of the
300 platform. Even among devices that receive OTA updates, some might lag and
323 application if their devices are running a compatible version of the Android
325 their devices. </p>
329 it will run properly on devices running the latest version of the platform, but
330 <em>not</em> on devices running earlier versions of the platform. In the latter
358 href="{@docRoot}guide/developing/devices/index.html">Creating and Managing Virtual Devices</a>. I
[all...] |
| /external/bluetooth/bluez/input/ |
| fakehid.c | 352 .devices = NULL,
383 for (l = fake_hid->devices; l != NULL; l = l->next) {
394 /* New device? Add it to the list of known devices,
402 fake_hid->devices = g_list_append(fake_hid->devices, fake);
|
| /frameworks/base/docs/html/guide/developing/debugging/ |
| index.jd | 24 port so it can communicate with the application VMs on your devices. The main components that
33 connected emulators and devices.</dd>
38 <dd>DDMS is a graphical program that communicates with your devices through <code>adb</code>. DDMS can
43 <a href="{@docRoot}guide/developing/devices/index.html">Android Virtual Device</a></strong></dt>
56 Devices tab of DDMS. DDMS forwards the appropriate port to port 8700. Most modern Java IDEs include a JDWP debugger,
|
| /frameworks/base/docs/html/guide/developing/ |
| device.jd | 1 page.title=Using Hardware Devices
31 Android-powered devices are available.</p>
34 to purchase the Nexus S and other Android-powered devices, visit <a
39 href="{@docRoot}guide/developing/devices/emulator.html">Android emulator</a> to test your
120 devices</code> from your SDK {@code platform-tools/} directory. If connected,
|
| /sdk/bash_completion/ |
| adb.bash | 62 COMMAND="devices connect disconnect push pull sync shell emu logcat lolcat forward jdwp install uninstall bugreport help version start-server kill-server get-state get-serialno status-window remount reboot reboot-bootloader root usb tcpip"
69 local devices=$(command adb devices '2>' /dev/null | grep -v "List of devices" | awk '{ print $1 }')
70 COMPREPLY=( $(compgen -W "${devices}" -- ${cur}) )
|
| /external/kernel-headers/original/linux/ |
| pci.h | 27 * The PCI interface treats multi-function devices as independent
28 * devices. The slot/function address of each device is encoded
109 * The pci_dev structure is used to describe PCI devices.
112 struct list_head global_list; /* node in list of all PCI devices */
207 * For PCI devices, the region numbers are assigned this way:
228 struct list_head devices; /* list of devices on this bus */ member in struct:pci_bus
401 extern struct list_head pci_devices; /* list of all devices */
543 /* Proper probing supporting hot-pluggable devices */
744 * The world is not perfect and supplies us with broken PCI devices
[all...] |
| /sdk/ddms/libs/ddmlib/src/com/android/ddmlib/ |
| DeviceMonitor.java | 126 * Returns the devices.
154 * Monitors the devices. This connects to the Debug Bridge
223 // remove all devices from list
273 byte[] request = AdbHelper.formAdbRequest("host:track-devices"); //$NON-NLS-1$
307 String[] devices = result.split("\n"); //$NON-NLS-1$ local
309 for (String d : devices) {
312 // new adb uses only serial numbers to identify devices
322 // now merge the new devices with the old ones.
333 // array to store the devices that must be queried for information.
398 // at this point we should still have some new devices in newList, so w
[all...] |
| /external/webkit/Source/WebCore/platform/graphics/chromium/ |
| TransparencyWin.cpp | 66 // Make a list of all devices. The iterator goes top-down, and we want
78 Vector<DeviceInfo> devices; local
82 devices.append(DeviceInfo(iter.device(), iter.x(), iter.y()));
91 for (int i = devices.size() - 1; i >= 0; i--) {
92 const SkBitmap& srcBmp = devices[i].device->accessBitmap(false);
95 destRect.fLeft = devices[i].x;
96 destRect.fTop = devices[i].y;
|
| /frameworks/base/core/java/android/bluetooth/ |
| BluetoothClass.java | 166 // Devices in the COMPUTER major class
175 // Devices in the PHONE major class
204 // Devices in the WEARABLE major class
212 // Devices in the TOY major class
220 // Devices in the HEALTH major class
230 // Devices in PERIPHERAL major class
291 * devices. It tries to err on the side of false positives.
|
| /frameworks/base/core/java/android/view/ |
| InputDevice.java | 34 * Some input devices present multiple distinguishable sources of input.
76 * Use {@link #getMotionRange} to query the range of the pointing device. Some devices permit
150 * This code is also used for other mouse-like pointing devices such as trackpads
188 * A special input source constant that is used when filtering input devices
189 * to match devices that provide any type of input source.
310 * Gets the ids of all input devices in the system.
496 * This value is mainly useful for calibrating self-centering devices.
|
| /frameworks/base/docs/html/guide/practices/design/ |
| seamlessness.jd | 178 <p>Different Android-powered devices will support different screen resolutions.
192 <p>Android devices will come with a variety of network-connectivity options. All
195 GSM networks. Even 3G-capable devices will spend lots of time on non-3G
220 saying that some Android devices will have full "QWERTY" keyboards, while
222 some devices will have touch-screens, but many won't.
226 in restricting your application so that it can only be used on those devices.
232 wall. Mobile devices are battery-powered, and the longer we can make that
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| uses-feature-element.jd | 52 devices. One of the ways Market filters applications is by feature compatibility.</p>
62 devices meet the application's feature requirements, rather than presenting it
81 without it. Because feature support can vary across Android devices, the
122 devices running API Level 4 or higher, it is recommended to include these
124 is "3" or lower. Devices running older versions of the platform will simply
184 which is supported by all Android-powered devices.</p>
221 their devices. One of the ways Market filters applications is by feature
235 provides a shared set of feature constants that both applications and devices
285 filters the application from users on devices that do not provide that feature.
331 devices and a declaration was unnecessary.</li
[all...] |
