| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/sys/ |
| socket.h | 203 When a connection arrives, open a new socket to communicate with it,
|
| /system/core/adb/ |
| adb.h | 466 #define CS_NOPERM 5 /* Insufficient permissions to communicate with the device */
|
| /system/core/include/system/ |
| graphics.h | 85 * communicate video pixel formats between their HAL modules. These formats
|
| /system/core/init/ |
| util.c | 84 * daemon. We communicate the file descriptor's value via the environment
|
| /external/libnfc-nxp/src/ |
| phLibNfc.h | 116 * to this mode,external reader can communicate with this SE.
118 *\b WiredMode: Wired mode is used to communicate with the Secure Element internally.
[all...] |
| /external/chromium/chrome/common/extensions/docs/ |
| background_pages.html | 383 You can communicate between your various pages using direct script calls,
384 similar to how frames can communicate.
|
| /external/chromium/chrome/common/extensions/docs/static/ |
| content_scripts.html | 53 <a href="#host-page-communication">communicate with web pages</a>
313 <p>Although the execution environments of content scripts and the pages that host them are isolated from each other, they share access to the page's DOM. If the page wishes to communicate with the content script (or with the extension via the content script), it must do so through the shared DOM.</p>
|
| overview.html | 338 alt="A browser window containing a browser action that's displaying a popup. The popup's HTML file (popup.html) can communicate with the extension's background page (background.html)." />
544 The HTML pages within an extension often need to communicate.
|
| /external/chromium_org/chrome/common/extensions/docs/templates/articles/ |
| app_codelab8_webresources.html | 17 It runs in a separate sandboxed process and can't communicate directly with the application.</p>
450 One feature we didn't mention here is that webviews can communicate with your app and vice-versa using asynchronous <a href="app_external.html#postMessage">postMessages</a>.</p></li>
|
| app_usb.html | 4 This document describes how to use the <a href="usb.html">USB API</a> to communicate
128 communicate with USB devices using connection handles.
|
| content_scripts.html | 53 <a href="#host-page-communication">communicate with web pages</a>
345 <p>Although the execution environments of content scripts and the pages that host them are isolated from each other, they share access to the page's DOM. If the page wishes to communicate with the content script (or with the extension via the content script), it must do so through the shared DOM.</p>
|
| overview.html | 314 alt="A browser window containing a browser action that's displaying a popup. The popup's HTML file (popup.html) can communicate with the extension's background page (background.html)." />
520 The HTML pages within an extension often need to communicate.
|
| sencha_framework.html | 31 <li>Communicate between Chrome App and sandboxed files.</li>
153 <h2 id="four">Communicate between files</h2>
|
| /external/llvm/utils/lit/lit/ |
| TestRunner.py | 38 out,err = p.communicate()
199 procData[-1] = procs[-1].communicate()
|
| /frameworks/base/docs/html/guide/topics/connectivity/ |
| bluetooth-le.jd | 55 This allows Android apps to communicate with BLE devices that have low power requirements,
178 <p>Before your application can communicate over BLE, you need
|
| bluetooth.jd | 76 the four major tasks necessary to communicate using Bluetooth: setting up
150 application registers to communicate with a remote Bluetooth health
202 <p>Before your application can communicate over Bluetooth, you need to verify
[all...] |
| /cts/tests/tests/openglperf/src/android/openglperf/cts/ |
| GLSurfaceViewCustom.java | 135 * the event, you may need to communicate with the Renderer object
138 * one relatively easy way to communicate with your renderer is
570 * to communicate with the Renderer on the rendering thread.
670 * communicate with the renderer from the UI thread, because that's where
671 * input events are received. Clients can communicate using any of the
[all...] |
| /frameworks/base/opengl/java/android/opengl/ |
| GLSurfaceView.java | 131 * the event, you may need to communicate with the Renderer object
134 * one relatively easy way to communicate with your renderer is
566 * to communicate with the Renderer on the rendering thread.
666 * communicate with the renderer from the UI thread, because that's where
667 * input events are received. Clients can communicate using any of the
[all...] |
| /external/chromium_org/chrome/test/pyautolib/ |
| remote_inspector_client.py | 105 communicate with a remote Chrome instance following the remote debugging
113 working together with this class to communicate with a remote Chrome
278 communicate with a remote Chrome instance following the remote inspector
[all...] |
| /external/chromium_org/tools/gyp/pylib/gyp/ |
| msvs_emulation.py | 125 for line in p.communicate()[0].splitlines():
[all...] |
| /bionic/libc/bionic/ |
| pthread-timers.c | 106 /* the following are used to communicate between
|
| /bootable/recovery/minadbd/ |
| fdevent.c | 37 ** both stdout and stderr are used to communicate between the client
|
| /build/tools/releasetools/ |
| sign_target_files_apks | 289 data, _ = p.communicate()
|
| /development/samples/training/threadsample/src/com/example/android/threadsample/ |
| DisplayActivity.java | 37 * An IntentHandler is used to communicate between the active Fragment and this
|
| /development/testrunner/ |
| adb_interface.py | 18 """Provides an interface to communicate with the device via the adb command.
|
