HomeSort by relevance Sort by last modified time
    Searched full:communicate (Results 126 - 150 of 628) sorted by null

1 2 3 4 56 7 8 91011>>

  /build/tools/releasetools/
common.py 315 p.communicate()
365 p.communicate()
401 p.communicate()
411 stdout, stderr = p.communicate()
465 p.communicate(password)
471 p.communicate()
701 _, _ = p.communicate()
880 _, err = p.communicate()
check_target_files_signatures 99 out, err = p.communicate(cert)
173 out, err = p.communicate(data)
220 manifest, err = p.communicate()
build_image.py 38 p.communicate()
  /external/chromium/chrome/browser/importer/
firefox_importer_unittest_utils_mac.cc 30 // |handle| - On return, the process handle to use to communicate with the
63 // Class to communicate on the server side of the IPC Channel.
  /external/qemu/docs/
ANDROID-QEMU-PIPE.TXT 18 3/ Simply use read() and write() to communicate with the service.
56 The device and driver use an I/O memory page and an IRQ to communicate.
ANDROID-QEMUD.TXT 25 "gsm" Used to communicate with the emulated GSM modem with
191 different protocol to communicate with the emulator.
197 to communicate. However, the multiplexing protocol swaps the position of
  /external/smack/src/org/xbill/DNS/
SimpleResolver.java 93 * Sets the address of the server to communicate with.
102 * Sets the address of the server to communicate with (on the default
  /frameworks/base/services/java/com/android/server/wm/
ViewServer.java 35 * The ViewServer is local socket server that can be used to communicate with the
79 * @param windowManager The window manager used to communicate with the views.
  /frameworks/base/docs/html/tools/adk/
adk2.jd 47 communicate with Android devices.</p>
329 ready to communicate with your Android device.</li>
370 <p>The essential feature of any Android accessory is its ability to connect and communicate with an
379 communicate. This connection allows two way communication between the ADK accessory and Android
477 objects from the socket to communicate with the accessory:</p>
489 <p>The ADK 2012 app and hardware accessory can also use a USB connection to communicate, similar to
592 <p>Once the connection is established, the app can communicate with the accessory through file input
  /frameworks/base/docs/html/training/in-app-billing/
preparing-iab-app.jd 33 <p>Before you can start using the In-app Billing service, you'll need to add the library that contains the In-app Billing Version 3 API to your Android project. You also need to setting the permissions for your application to communicate with Google Play. In addition, you'll need to establish a connection between your application and Google Play. You should also verify that the In-app Billing API version that you are using in your application is supported by Google Play.</p>
92 <p>Your app needs to have permission to communicate request and response messages to the Google Play?s billing service. To give your app the necessary permission, add this line in your {@code AndroidManifest.xml} manifest file:</p>
129 <p>If the setup completed successfully, you can now use the {@code mHelper} reference to communicate with the Google Play service. When your application is launched, it is a good practice to query Google Play to find out what in-app items are owned by a user. This is covered further in the <a href="{@docRoot}training/in-app-billing/purchase-iab-products.html#QueryPurchases">Query Purchased Items</a> section.</p>
  /packages/inputmethods/LatinIME/java/src/com/android/inputmethod/latin/
BinaryDictionaryFileDumper.java 72 // Using protocol version 2 to communicate with the dictionary pack
203 Log.e(TAG, "Can't communicate with the dictionary pack", e);
230 Log.e(TAG, "Can't communicate with the dictionary pack", e);
  /external/chromium/testing/gtest/test/
gtest_test_utils.py 233 # communicate returns a tuple with the file obect for the child's
235 self.output = p.communicate()[0]
  /external/clang/tools/scan-view/
Reporter.py 184 data,err = p.communicate()
217 data, err = p.communicate()
  /external/gtest/test/
gtest_test_utils.py 233 # communicate returns a tuple with the file obect for the child's
235 self.output = p.communicate()[0]
  /external/libvpx/libvpx/third_party/googletest/src/test/
gtest_test_utils.py 233 # communicate returns a tuple with the file obect for the child's
235 self.output = p.communicate()[0]
  /external/protobuf/gtest/test/
gtest_test_utils.py 228 # communicate returns a tuple with the file obect for the child's
230 self.output = p.communicate()[0]
  /external/protobuf/src/google/protobuf/compiler/
subprocess.cc 143 bool Subprocess::Communicate(const Message& input, Message* output,
342 bool Subprocess::Communicate(const Message& input, Message* output,
  /external/qemu/android/protocol/
fb-updates-proxy.c 43 /* Looper used to communicate framebuffer updates. */
52 /* Socket used to communicate framebuffer updates. */
  /frameworks/base/docs/html/guide/practices/ui_guidelines/
icon_design_launcher.jd 97 <li>Don't try to communicate too much with the icon. A simple icon will have more impact and be
126 <li>Communicate well at small sizes.</li>
  /frameworks/base/docs/html/training/multiple-threads/
create-threadpool.jd 128 <a href="communicate-ui.html">Communicate with the UI Thread</a>. For example:
  /hardware/samsung_slsi/exynos5/libsecurepath/
content_protect.cpp 102 LOG_E("Tlc Communicate Error");
166 LOG_E("Tlc Communicate Error");
  /development/samples/ApiDemos/src/com/example/android/apis/app/
LocalServiceActivities.java 85 * bind to, receiving an object through which it can communicate with the service.</p>
  /development/samples/Support4Demos/src/com/example/android/supportv4/content/
LocalServiceBroadcaster.java 39 * Demonstrates the use of a LocalBroadcastManager to easily communicate
  /development/testrunner/
android_build.py 66 shell=True).communicate()[0]
  /docs/source.android.com/src/accessories/
custom.jd 36 <p>If you use the general accessory protocol to communicate with your accessory (rather than the

Completed in 285 milliseconds

1 2 3 4 56 7 8 91011>>