| /frameworks/base/docs/html/guide/components/ |
| D | aidl.jd | 12 <li><a href="#Implement">Implement the interface</a></li>
13 <li><a href="#Expose">Expose the interface to clients</a></li>
30 worked with. It allows you to define the programming interface that both
40 different applications, you should create your interface by <a
43 implement your interface <a
49 <p>Before you begin designing your AIDL interface, be aware that calls to an AIDL interface are
56 this is your main UI thread, that thread continues to execute in the AIDL interface. If it is
60 interface by <a href="{@docRoot}guide/components/bound-services.html#Binder">implementing a
65 happening at the same time. In other words, an implementation of an AIDL interface must be
70 The implementation of the interface eventually receives this as a regular call from the {@link
[all …]
|
| D | bound-services.jd | 44 <p>A bound service is the server in a client-server interface. A bound service allows components
61 method returns an {@link android.os.IBinder} object that defines the programming interface that
109 <p>When you implement your bound service, the most important part is defining the interface
111 different ways you can define your service's {@link android.os.IBinder} interface and the following
119 that provides the programming interface that clients can use to interact with the service. There
120 are three ways you can define the interface:</p>
125 (which is common), you should create your interface by extending the {@link android.os.Binder} class
131 application. The only reason you would not create your interface this way is because
135 <dd>If you need your interface to work across different processes, you can create
136 an interface for the service with a {@link android.os.Messenger}. In this manner, the service
[all …]
|
| /frameworks/base/docs/html/training/tv/discovery/ |
| D | in-app-search.jd | 24 users to find what they are looking for. A search interface can help your users get to the
30 library</a> provides a set of classes to enable a standard search interface within your app that
35 This lesson discusses how to provide a search interface in your app using Leanback support
44 browsing interface, you can enable a search interface as a standard part of the user
45 interface. The search interface is an icon that appears in the layout when you set {@link
85 android.support.v17.leanback.app.SearchFragment.SearchResultProvider} interface in order to
91 android.support.v17.leanback.app.SearchFragment} class to provide a search interface and results:
145 queries from blocking the main user interface thread.
|
| /frameworks/native/cmds/ip-up-vpn/ |
| D | ip-up-vpn.c | 85 const char *interface = env("INTERFACE"); in main() local
95 strncpy(ifr.ifr_name, interface, IFNAMSIZ); in main()
97 ALOGE("Cannot bring up %s: %s", interface, strerror(errno)); in main()
118 fprintf(state, "%s\n", interface); in main()
|
| /frameworks/base/services/core/jni/ |
| D | com_android_server_UsbHostManager.cpp | 111 struct usb_interface_descriptor *interface = (struct usb_interface_descriptor *)desc; in usb_device_added() local
112 char *name = usb_device_get_string(device, interface->iInterface); in usb_device_added()
116 interface->bInterfaceNumber, interfaceName, interface->bAlternateSetting, in usb_device_added()
117 interface->bInterfaceClass, interface->bInterfaceSubClass, in usb_device_added()
118 interface->bInterfaceProtocol); in usb_device_added()
|
| /frameworks/wilhelm/tests/sandbox/ |
| D | engine.c | 116 void *interface = NULL; in main() local
118 result = (*engineObject)->GetInterface(engineObject, engine_ids[index], &interface); in main()
140 void *interface = NULL; in main() local
141 result = (*engineObject)->GetInterface(engineObject, engine_ids[index], &interface); in main()
143 printf("interface[%u] %p\n", index, interface); in main()
150 assert(interface_again == interface); in main()
|
| /frameworks/base/docs/html/training/basics/fragments/ |
| D | communicating.jd | 46 <p>To allow a Fragment to communicate up to its Activity, you can define an interface
48 the interface implementation during its onAttach() lifecycle method and can then call
57 // Container Activity must implement this interface
58 public interface OnHeadlineSelectedListener {
67 // the callback interface. If not, it throws an exception
81 onArticleSelected()} method (or other methods in the interface) using the {@code mCallback}
82 instance of the {@code OnHeadlineSelectedListener} interface.</p>
85 item. The fragment uses the callback interface to deliver the event to the parent activity.</p>
100 implement the interface defined in the fragment class.</p>
102 <p>For example, the following activity implements the interface from the above example.</p>
|
| /frameworks/av/services/audiopolicy/ |
| D | AudioPolicyFactory.cpp | 27 extern "C" void destroyAudioPolicyManager(AudioPolicyInterface *interface) in destroyAudioPolicyManager() argument
29 delete interface; in destroyAudioPolicyManager()
|
| /frameworks/wilhelm/doc/ |
| D | README.txt | 1 …nk the OpenSLES_IID.c file into your project. This file contains unique interface IDs for all Open…
2 have been automatically generated. Application developers should not edit these interface IDs.
|
| /frameworks/av/media/libeffects/preprocessing/ |
| D | Android.mk | 15 external/webrtc/src/modules/interface \
16 external/webrtc/src/modules/audio_processing/interface \
|
| /frameworks/base/tools/aidl/ |
| D | generate_java_binder.cpp | 250 generate_method(const method_type* method, Class* interface, in generate_method() argument
289 interface->elements.push_back(decl); in generate_method()
523 Class* interface = new Class; in generate_binder_interface_class() local
524 interface->comment = gather_comments(iface->comments_token->extra); in generate_binder_interface_class()
525 interface->modifiers = PUBLIC; in generate_binder_interface_class()
526 interface->what = Class::INTERFACE; in generate_binder_interface_class()
527 interface->type = interfaceType; in generate_binder_interface_class()
528 interface->interfaces.push_back(IINTERFACE_TYPE); in generate_binder_interface_class()
534 interface->elements.push_back(stub); in generate_binder_interface_class()
552 generate_method(method_item, interface, stub, proxy, method_item->assigned_id); in generate_binder_interface_class()
[all …]
|
| /frameworks/av/media/mtp/ |
| D | MtpDevice.cpp | 67 struct usb_interface_descriptor *interface = (struct usb_interface_descriptor *)desc; in open() local
69 if (interface->bInterfaceClass == USB_CLASS_STILL_IMAGE && in open()
70 interface->bInterfaceSubClass == 1 && // Still Image Capture in open()
71 interface->bInterfaceProtocol == 1) // Picture Transfer Protocol (PIMA 15470) in open()
78 } else if (interface->bInterfaceClass == 0xFF && in open()
79 interface->bInterfaceSubClass == 0xFF && in open()
80 interface->bInterfaceProtocol == 0) { in open()
81 char* interfaceName = usb_device_get_string(device, interface->iInterface); in open()
157 if (usb_device_claim_interface(device, interface->bInterfaceNumber)) { in open()
163 MtpDevice* mtpDevice = new MtpDevice(device, interface->bInterfaceNumber, in open()
[all …]
|
| /frameworks/base/tools/layoutlib/bridge/tests/res/testApp/MyApplication/ |
| D | proguard-rules.pro | 13 # and specify the fully qualified class name to the JavaScript interface
15 #-keepclassmembers class fqcn.of.javascript.interface.for.webview {
|
| /frameworks/volley/ |
| D | proguard-project.txt | 16 # and specify the fully qualified class name to the JavaScript interface
18 #-keepclassmembers class fqcn.of.javascript.interface.for.webview {
|
| /frameworks/base/tests/MusicServiceDemo/ |
| D | proguard-project.txt | 16 # and specify the fully qualified class name to the JavaScript interface
18 #-keepclassmembers class fqcn.of.javascript.interface.for.webview {
|
| /frameworks/base/tests/Camera2Tests/SmartCamera/SimpleCamera/ |
| D | proguard-project.txt | 16 # and specify the fully qualified class name to the JavaScript interface
18 #-keepclassmembers class fqcn.of.javascript.interface.for.webview {
|
| /frameworks/base/docs/html/guide/topics/ui/controls/ |
| D | spinner.jd | 109 android.widget.AdapterView.OnItemSelectedListener} interface and the corresponding {@link
111 For example, here's an implementation of the interface in an {@link android.app.Activity}:</p>
124 // Another interface callback
135 <p>Then you need to specify the interface implementation by calling {@link
144 android.widget.AdapterView.OnItemSelectedListener} interface with your {@link
146 <code>this</code> as the interface instance.</p>
|
| /frameworks/opt/net/ims/ |
| D | README.txt | 11 - 3GPP TS 24.623 : XCAP over the Ut interface for manipulating supplementary services
84 It provides APIs for the supplementary service settings using IMS (Ut interface, XCAP).
91 Wrapper class which has an ICallGroup interface.
94 Implements ICallGroup interface.
103 Provides the interface to manage all calls which are established hereafter the initial
|
| /frameworks/av/cmds/stagefright/ |
| D | audioloop.cpp | 106 client.interface(), in main()
120 client.interface(), in main()
|
| /frameworks/base/docs/html/training/backward-compatible-ui/ |
| D | index.jd | 49 <dd>Learn how to create an implementation of your interface that uses newer APIs.</dd>
52 <dd>Learn how to create a custom implementation of your interface that uses older APIs.</dd>
55 …<dd>Learn how to choose an implementation to use at runtime, and begin using the interface in your…
|
| /frameworks/base/docs/html/tools/support-library/ |
| D | features.jd | 46 Android versions and provide APIs for recommended user interface patterns.</p>
60 user interface features, accessibility, data handling, network connectivity, and programming
67 - Adds support for encapsulation of user interface and functionality
135 you download the Android Support Libraries. The library does not contain user interface
162 after you download the Android Support Libraries. The library does not contain user interface
189 interface <a href="{@docRoot}design/patterns/actionbar.html">design
191 <a href="{@docRoot}design/material/">material design</a> user interface
204 <a href="{@docRoot}design/patterns/actionbar.html">user interface pattern</a>. For more
220 interface resources. To include it in your application project, follow the instructions for
241 download the Android Support Libraries. The library contains user interface
[all …]
|
| /frameworks/native/opengl/tools/glgen2/registry/ |
| D | reg.py | 406 def beginFeature(self, interface, emit): argument
408 self.featureName = interface.get('name')
410 self.featureExtraProtect = interface.get('protect')
560 def beginFeature(self, interface, emit): argument
562 OutputGenerator.beginFeature(self, interface, emit)
896 def requireAndRemoveFeatures(self, interface, api, profile): argument
899 for feature in interface.findall('require'):
903 for feature in interface.findall('remove'):
962 def generateRequiredInterface(self, interface): argument
967 for features in interface.findall('require'):
|
| /frameworks/av/include/media/stagefright/ |
| D | OMXClient.h | 32 sp<IOMX> interface() { in interface() function
|
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| D | services.jd | 47 <p>An accessibility service is an application that provides user interface enhancements to
50 might need additional or alternative interface feedback.</p>
223 user interface control in an application for which your accessibility service is providing feedback.
249 <p>The Android system provides information to accessibility services about the user interface
252 detail about a user interface control selected by the user, offered limited contextual
256 <p>An example of an interface where context is critical is a calendar or day planner. If the
259 the resulting feedback is confusing. In this case, the context of a user interface control is
263 obtain about an user interface interaction by composing accessibility events based on the view
264 hierarchy. A view hierarchy is the set of user interface components that contain the component (its
265 parents) and the user interface elements that may be contained by that component (its children). In
[all …]
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | descendant-lateral.jd | 55 …gation can be provided using lists, tabs, and other user interface patterns. <em>User interface pa…
66 …ion interface. Examples of such targets include buttons, fixed-size list views, or text links, alt…
70 …alt="Example button-based navigation interface with relevant screen map excerpt. Also shows dashbo…
72 <p class="img-caption"><strong>Figure 3.</strong> Example button-based navigation interface with re…
89 …scrolling lists are often the most straightforward and familiar kind of interface. For more visual…
153 …alt="Example horizontal paging navigation interface with relevant screen map excerpt" id="figure-p…
155 <p class="img-caption"><strong>Figure 6.</strong> Example horizontal paging navigation interface wi…
169 …rn can be used along with tabs above the content region to maximize the interface's intuitiveness.…
|