HomeSort by relevance Sort by last modified time
    Searched full:communication (Results 351 - 375 of 904) sorted by null

<<11121314151617181920>>

  /development/pdk/docs/porting/
stk.jd 11 <li><a href="#androidSTKRILRilUp">Communication from the RIL up</a></li>
12 <li><a href="#androidSTKRILApplciationDown">Communication from the application down</a></li>
30 <p> The Sim Toolkit communication flow is bi-directional and commands can originate from the <code>STK RIL</code> packaged in <code>RIL_UNSOL_STK_PROACTIVE_COMMAND</code>, <code>RIL_UNSOL_STK_EVENT_NOTIFY</code>, <code>RIL_UNSOL_REFRESH</code> and <code>RIL_UNSOL_STK_SESSION_END</code> messages.</p>
40 <a name="androidSTKRILRilUp"></a><h4>Communication from the RIL up</h4>
42 <p>Communication to the upper layers is done using the <code>RIL_UNSOL_xxx</code> family of commands defined in <code>/hardware/ril/include/ril.h</code>. The payload for each command is encoded using BER-TLV. As stated above, it is not necessary to remove extraneous fields. This allows the SIM to pass a complete command to the upper layers and simplifies STK RIL code. Below is the mapping from RIL_UNSOL_xxx commands to the SIM commands.</p>
47 <p> The Sim Toolkit communication flow is bi-directional and commands can originate from the <code>STK RIL</code> packaged in <code>RIL_UNSOL_STK_PROACTIVE_COMMAND</code>, <code>RIL_UNSOL_STK_EVENT_NOTIFY</code>, <code>RIL_UNSOL_REFRESH</code> and <code>RIL_UNSOL_STK_SESSION_END</code> messages.</p>
180 <a name="androidSTKRILApplciationDown"></a><h4>Communication from the application down</h4>
182 <p>Communication from the upper layers to the RIL uses the commands below (defined in <code>ril.h</code>):</p>
  /external/chromium/chrome/browser/
browser_process.h 111 // communication with renderers, etc.
192 // Returns an object which handles communication with the SafeBrowsing
  /external/libnfc-nxp/src/
phLibNfc_target.c 79 * communication.
226 * Interface used to send data from target to initiator during P2P communication
  /frameworks/base/docs/html/sdk/
android-2.0-highlights.jd 92 a contact's information and communication modes. For example, a user can tap a
104 <li>New way to hover on a person to see more info and select communication
  /hardware/ril/mock-ril/src/java/com/android/internal/communication/
Msg.java 17 package com.android.internal.communication;
21 import com.android.internal.communication.MsgHeader;
  /frameworks/base/docs/html/guide/topics/usb/
accessory.jd 39 <li><a href="#terminating-a">Terminating communication with an accessory</a></li>
245 up communication with the accessory if desired. To do this, your application has to:</p>
358 //call method to set up accessory communication
400 up the communication between the device and accessory in another thread, so you don't lock the
438 <h3 id="terminating-a">Terminating communication with an accessory</h3>
451 // call your method that cleans up and closes communication with the accessory
  /external/chromium/chrome/common/extensions/docs/static/
content_scripts.html 53 <a href="#host-page-communication">communicate with web pages</a>
311 <h2 id="host-page-communication">Communication with the embedding page</h2>
337 <p>In the above example, example.html (which is not a part of the extension) creates a custom event and then can decide to fire the event by setting the event data to a known location in the DOM and then dispatching the custom event. The content script listens for the name of the custom event on the known element and handles the event by inspecting the data of the element, and turning around to post the message to the extension process. In this way the page establishes a line of communication to the extension. The reverse is possible through similar means.</p>
411 You can find other simple examples of communication via messages in the
  /hardware/ril/mock-ril/
NOTICE 67 means any form of electronic, verbal, or written communication sent
69 communication on electronic mailing lists, source code control systems,
72 excluding communication that is conspicuously marked or otherwise
  /hardware/ril/mock-ril/src/cpp/
msgheader.pb.cpp 13 namespace communication { namespace
81 "droid.internal.communication", 148);
427 } // namespace communication
  /sdk/eclipse/features/com.android.ide.eclipse.ddms/
feature.xml 76 means any form of electronic, verbal, or written communication sent
78 communication on electronic mailing lists, source code control systems,
81 excluding communication that is conspicuously marked or otherwise
  /sdk/eclipse/features/com.android.ide.eclipse.gldebugger/
feature.xml 70 means any form of electronic, verbal, or written communication sent
72 communication on electronic mailing lists, source code control systems,
75 excluding communication that is conspicuously marked or otherwise
  /sdk/eclipse/features/com.android.ide.eclipse.hierarchyviewer/
feature.xml 71 means any form of electronic, verbal, or written communication sent
73 communication on electronic mailing lists, source code control systems,
76 excluding communication that is conspicuously marked or otherwise
  /sdk/eclipse/features/com.android.ide.eclipse.pdt/
feature.xml 70 means any form of electronic, verbal, or written communication sent
72 communication on electronic mailing lists, source code control systems,
75 excluding communication that is conspicuously marked or otherwise
  /sdk/eclipse/features/com.android.ide.eclipse.traceview/
feature.xml 71 means any form of electronic, verbal, or written communication sent
73 communication on electronic mailing lists, source code control systems,
76 excluding communication that is conspicuously marked or otherwise
  /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/
about.html 74 means any form of electronic, verbal, or written communication sent
76 communication on electronic mailing lists, source code control systems,
79 excluding communication that is conspicuously marked or otherwise
  /sdk/eclipse/plugins/com.android.ide.eclipse.hierarchyviewer/
about.html 67 means any form of electronic, verbal, or written communication sent
69 communication on electronic mailing lists, source code control systems,
72 excluding communication that is conspicuously marked or otherwise
  /external/libnfc-nxp/inc/
phNfcHalTypes.h 121 * stores the refernce to the communication driver passed by the HAL client
122 * for usage during communication with the NFC Device
138 * stores the refernce to the communication driver passed by the HAL client
139 * for usage during communication with the NFC Device
639 * data structure (buffer and length) for communication with remote device
    [all...]
  /development/tools/emulator/opengl/tests/event_injector/
sockets.h 319 /* create a new socket intended for IPv4 communication. returns the socket number,
324 /* create a new socket intended for IPv6 communication. returns the socket number,
  /external/chromium/chrome/browser/policy/
cloud_policy_controller.cc 143 VLOG(1) << "An error in the communication with the policy server occurred"
150 VLOG(1) << "A temporary error in the communication with the policy server"
  /external/chromium/chrome/common/extensions/docs/examples/api/webNavigation/basic/
navigation_collector.js 16 * communication between background pages and popups.
62 // Bind handler to extension messages for communication from popup.
  /external/dbus/doc/
dbus-test-plan.xml 152 there is still the issue of testing client-server communication.
183 communication. This means that the bus daemon code can be
  /external/openssl/crypto/rand/
rand_egd.c 75 * -1 if an error occured during connection or communication.
87 * -1 if an error occured during connection or communication _or_
  /external/oprofile/doc/
op-jit-devel.xml 83 <listitem>Implement a function to set up initial communication with the VM.
84 Once communication to the VM is established, your agent library should call
  /external/qemu/
charpipe.c 25 /* we want to implement a bi-directionnal communication channel
30 * we implement communication through charpipe_poll() which
sockets.h 311 /* create a new socket intended for IPv4 communication. returns the socket number,
316 /* create a new socket intended for IPv6 communication. returns the socket number,

Completed in 532 milliseconds

<<11121314151617181920>>