Home
last modified time | relevance | path

Searched refs:calls (Results 1 – 25 of 225) sorted by relevance

123456789

/frameworks/base/services/tests/servicestests/src/com/android/server/content/
DObserverNodeTest.java62 ArrayList<ObserverCall> calls = new ArrayList<ObserverCall>(); in testUri() local
65 root.collectObserversLocked(uris[i], 0, null, false, myUserHandle, calls); in testUri()
66 assertEquals(nums[i], calls.size()); in testUri()
67 calls.clear(); in testUri()
92 ArrayList<ObserverCall> calls = new ArrayList<ObserverCall>(); in testUriNotNotify() local
95 root.collectObserversLocked(uris[i], 0, null, false, myUserHandle, calls); in testUriNotNotify()
96 assertEquals(nums[i], calls.size()); in testUriNotNotify()
97 calls.clear(); in testUriNotNotify()
/frameworks/rs/api/
DGenerateStubsWhiteList.cpp414 static void generateTestCall(GeneratedFile* file, ostringstream* calls, in generateTestCall() argument
417 *calls << " "; in generateTestCall()
422 *calls << "*(" << ret->rsType << "*)" << addVariable(file, variableNumber) << " = "; in generateTestCall()
425 *calls << permutation.getName() << "("; in generateTestCall()
430 *calls << separator; in generateTestCall()
433 *calls << "context"; in generateTestCall()
435 *calls << "(" << p->rsType << "*) " << addVariable(file, variableNumber); in generateTestCall()
437 *calls << "*(" << p->rsType << "*)" << addVariable(file, variableNumber); in generateTestCall()
441 *calls << ");\n"; in generateTestCall()
475 ostringstream calls; in generateApiTesterFile() local
[all …]
/frameworks/opt/net/ims/
DREADME.txt2 especially making and taking VoLTE calls using IMS.
3 At the moment, this only supports VoLTE calls which is compliant to GSMA IR.92 specification.
16 With the ImsManager, you can initiate VoLTE calls with ImsManager#makeCall()
27 To receive calls, an IMS application MUST provide a BroadcastReceiver that
47 Provides APIs for IMS services, such as initiating IMS calls, and provides access to
51 Provides IMS voice / video calls over LTE network.
54 Manages all IMS calls which are established hereafter the initial 1-to-1 call is established.
55 It's for providing the dummy calls which are disconnected with the IMS network after
95 Manages all calls which are established hereafter the initial 1-to-1 call is established.
96 It's for providing the dummy calls which are disconnected with the IMS network after
[all …]
/frameworks/native/opengl/libs/GLES_trace/
DDESIGN.txt7 egl_display_t::initialize() calls initEglTraceLevel() to figure out whether tracing should be
10 calls GLTrace_start() to start the trace server.
12 egl_display_t::initialize() then calls setGLHooksThreadSpecific() where we set the thread
18 While the application is running, all its GLES calls are directly routed to their corresponding
21 For EGL calls, the trace library provides a bunch of functions that must be explicitly called
64 EGL/eglApi.cpp to initialize the trace library, and to inform the library of EGL calls.
66 All GL calls are present in GLES_Trace/src/gltrace_api.cpp. This file is generated by the
/frameworks/base/docs/html/training/swipe/
Drespond-refresh-request.jd37 indicator and calls your app's callback method. Your callback method is
60 Your update method calls {@link
85 // The method calls setRefreshing(false) when it's finished.
94 If the user requests a refresh by using the action bar, the system calls the
133 // This method calls setRefreshing(false) when it's finished.
155 The method which actually refreshes the data calls {@link
/frameworks/base/docs/html/training/basics/activity-lifecycle/
Dpausing.jd43 <p>As your activity enters the paused state, the system calls the {@link
47 the user returns to your activity from the paused state, the system resumes it and calls the
57 your activity, the system calls {@link android.app.Activity#onPause onPause()} and the activity
59 system calls {@link android.app.Activity#onResume onResume()} (2).</p>
64 <p>When the system calls {@link android.app.Activity#onPause()} for your activity, it
117 <p>When the user resumes your activity from the Paused state, the system calls the {@link
120 <p>Be aware that the system calls this method every time your activity comes into the foreground,
Dstarting.jd50 <p>During the life of an activity, the system calls a core set of lifecycle methods in
56 <p>As the user begins to leave the activity, the system calls other methods that move the activity
132 the next state by calling the next lifecycle callback method. That is, after the system calls
133 {@link android.app.Activity#onCreate onCreate()}, it quickly calls {@link
144 <p>When the user selects your app icon from the Home screen, the system calls the {@link
225 calls the {@link android.app.Activity#onStart()} and {@link android.app.Activity#onResume()} methods
243 structure with an emphasis on the three main callbacks that the system calls in sequence when
258 onCreate()}, its very last callback is {@link android.app.Activity#onDestroy}. The system calls
280 <p class="note"><strong>Note:</strong> The system calls {@link android.app.Activity#onDestroy}
287 immediately calls {@link android.app.Activity#onDestroy} without calling any of the other
Dstopping.jd64 calls {@link android.app.Activity#onStop onStop()} to stop the activity (1). If the user returns
65 while the activity is stopped, the system calls {@link android.app.Activity#onRestart onRestart()}
68 stop, the system always calls {@link android.app.Activity#onPause onPause()} before calling {@link
131 {@link android.app.Activity#onRestart()}. The system also calls the {@link
145 to the {@link android.app.Activity#onStop()} method, because the system calls {@link
182 <p>When the system destroys your activity, it calls the {@link android.app.Activity#onDestroy()}
Drecreating.jd67 The system calls this method when the user is leaving your activity
77 calls {@link android.app.Activity#onSaveInstanceState onSaveInstanceState()} (1) so you can specify
89 <p>As your activity begins to stop, the system calls {@link android.app.Activity#onSaveInstanceState
157 android.app.Activity#onRestoreInstanceState onRestoreInstanceState()}, which the system calls
158 after the {@link android.app.Activity#onStart()} method. The system calls {@link
Dindex.jd43 focus. During this process, the Android system calls a series of lifecycle methods on the
45 action that starts another activity or switches to another app, the system calls another set of
/frameworks/base/docs/html/tools/help/uiautomator/
DUiWatcher.jd32 …<div class="jd-descrdiv">The testing framework calls this handler method automatically when the fr…
67 …calls this handler method automatically when the framework is unable to find a match using the <co…
/frameworks/base/docs/html/training/transitions/
Dcustom-transitions.jd77 method. The framework calls this method for every view in the starting scene. The method
124 <p>The framework calls the {@link android.transition.Transition#captureEndValues} method
153 framework calls this method, it passes in the scene root view and the {@link
157 <p>The number of times the framework calls the {@link
162 scene plus a new target, then the framework calls {@link
163 android.transition.Transition#createAnimator createAnimator()} six times: three of the calls
164 animate the fading out and fading in of the targets that stay in both scene objects; two more calls
/frameworks/base/docs/html/guide/topics/connectivity/
Dsip.jd37 services that let applications easily set up outgoing and incoming voice calls,
167 <p>If your application is designed to receive calls, you must also define a receiver ({@link androi…
201 <li>Initiating and receiving calls.</li>
223 device as the location to send SIP calls to for your SIP address.</p>
237 <p>The following code excerpt opens the local profile for making calls and/or
238 receiving generic SIP calls. The caller can make subsequent calls through
242 an intent filter to receive calls</a>). This is the registration step:</p>
342 <p>To receive calls, a SIP application must include a subclass of {@link
358 pending intent that fires your receiver when someone calls the local profile.
367 <p>To receive calls, your SIP application must subclass {@link
[all …]
/frameworks/base/docs/html/tools/debugging/
Ddebugging-tracing.jd58 The thin lines underneath the first row show the extent (entry to exit) of all the calls to the
75 with a yellow background. The last column in the table shows the number of calls to this method
76 plus the number of recursive calls. The last column shows the number of calls out of the total
77 number of calls made to that method. In this view, we can see that there were 14 calls to
78 …dListener.nativeFinished();</code> looking at the timeline panel shows that one of those calls took
143 <p>When your application calls {@link android.os.Debug#startMethodTracing() startMethodTracing()},
148 <p>The system then begins buffering the generated trace data, until your application calls
222 <li><code>&lt;numcalls&gt;</code> -- Number of calls</li>
/frameworks/base/docs/html/training/custom-views/
Doptimizing-view.jd45 infrequently as possible. Most calls to {@link android.view.View#onDraw onDraw()} are the result of
47 android.view.View#invalidate() invalidate()}, so eliminate unnecessary calls to {@link
51 <p>Another very expensive operation is traversing layouts. Any time a view calls {@link
/frameworks/base/services/core/java/com/android/server/content/
DContentService.java277 ArrayList<ObserverCall> calls = new ArrayList<ObserverCall>(); in notifyChange() local
280 userHandle, calls); in notifyChange()
282 final int numCalls = calls.size(); in notifyChange()
284 ObserverCall oc = calls.get(i); in notifyChange()
1118 ArrayList<ObserverCall> calls) { in collectMyObserversLocked() argument
1137 calls.add(new ObserverCall(this, entry.observer, selfChange)); in collectMyObserversLocked()
1148 ArrayList<ObserverCall> calls) { in collectObserversLocked() argument
1154 targetUserHandle, calls); in collectObserversLocked()
1159 targetUserHandle, calls); in collectObserversLocked()
1168 observer, observerWantsSelfNotifications, targetUserHandle, calls); in collectObserversLocked()
/frameworks/base/docs/html/training/backward-compatible-ui/
Dnew-implementation.jd44 …etc.), the concrete classes that use these newer APIs simply proxy method calls and their results.…
57 …ndividual tabs. <code>CompatTabHoneycomb</code> simply proxies all method calls to its contained {…
86 …entation of the <code>TabHelper</code> abstract class that proxies method calls to an actual {@lin…
88 <p>Implement <code>TabHelperHoneycomb</code>, proxying method calls to the {@link android.app.Actio…
/frameworks/opt/telephony/src/java/com/android/internal/telephony/
DCallManager.java1921 private Call getFirstNonIdleCall(List<Call> calls) { in getFirstNonIdleCall() argument
1923 for (Call call : calls) { in getFirstNonIdleCall()
1935 private Call getFirstNonIdleCall(List<Call> calls, int subId) { in getFirstNonIdleCall() argument
1937 for (Call call : calls) { in getFirstNonIdleCall()
2166 private Call getFirstActiveCall(ArrayList<Call> calls) { in getFirstActiveCall() argument
2167 for (Call call : calls) { in getFirstActiveCall()
2178 private Call getFirstActiveCall(ArrayList<Call> calls, int subId) { in getFirstActiveCall() argument
2179 for (Call call : calls) { in getFirstActiveCall()
2191 private Call getFirstCallOfState(ArrayList<Call> calls, Call.State state) { in getFirstCallOfState() argument
2192 for (Call call : calls) { in getFirstCallOfState()
[all …]
/frameworks/base/docs/html/training/wearables/data-layer/
Devents.jd17 <p>When you make calls to the Data Layer API, you can receive the status
24 <p>You'll notice that calls to the Data Layer API sometimes return a
36 <h3 id="async-waiting">Asynchronous calls</h3>
37 <p>If your code is running on the main UI thread, do not make blocking calls
38 to the Data Layer API. You can run the calls asynchronously by adding a callback method
52 <h3 id="sync-waiting">Synchronous calls</h3>
55 it's fine for the calls to block. In this case, you can call
198 and calls your callbacks via IPC. This has the consequence
244 <li>When the connection to Google Play services is established, the system calls
/frameworks/base/docs/html/ndk/samples/
Dsample_teapot.jd29 <li>Wrappers for JNI calls for platform features such as texture loading.</li>
80 code calls it to display a popup window for displaying text.</p>
101 <p>These function calls perform the actual rendering of the teapot. It uses
165 <p>The app calls the following functions in response to various Android
179 <p>Then, the following function calls back to the Java side to update the UI display.</p>
199 <p>Next, this function calls back to the Java side to draw a text box
Dsample_hellojni.jd50 <p>The {@code helloJNI.java} file is located in {@code hellojni/src/com/example/hellojni/}. It calls
71 <p>The Android framework calls the function loaded and declared in the
117 <p>The following line calls the VM API {@code (*env)}, and passes it a return value:
/frameworks/base/docs/html/guide/topics/ui/controls/
Dpickers.jd123 <p>For example, here's a button that, when clicked, calls a method to show the dialog:</p>
133 <p>When the user clicks this button, the system calls the following method:</p>
142 <p>This method calls {@link
228 <p>For example, here's a button that, when clicked, calls a method to show the dialog:</p>
238 <p>When the user clicks this button, the system calls the following method:</p>
247 <p>This method calls {@link
/frameworks/compile/mclinker/lib/Support/Windows/
DSystem.inc44 /// srandom - set the initial seed value for future calls to random().
/frameworks/base/tools/layoutlib/create/
DREADME.txt26 calls in Eclipse.
93 - specific methods for which to delegate calls.
134 ReplaceMethodCallsAdapter replaces calls to certain methods. This is different from the
136 changes the calls to a method in each class instead of changing the implementation of the method.
152 listeners from these overridden method calls based on the method signatures.
172 - OverrideMethod and its associated MethodListener and MethodAdapter are used to intercept calls to
240 b- A brand new implementation of SomeClass.MethodName() which calls to a non-existing static method
/frameworks/base/docs/html/guide/components/
Dbound-services.jd96 client and service, it calls {@link
101 <p>Multiple clients can connect to the service at once. However, the system calls your service's
198 make calls to the bound service using the methods provided.</li>
243 <p>Here's an activity that binds to {@code LocalService} and calls {@code getRandomNumber()}
333 all calls to the service, whereas, a pure AIDL interface sends simultaneous requests to the
505 system then calls the service's {@link android.app.Service#onBind
513 system calls to deliver the {@link android.os.IBinder}.</p>
524 <dd>The system calls this to deliver the {@link android.os.IBinder} returned by
528 <dd>The Android system calls this when the connection to the service is unexpectedly
536 <li>When the system calls your {@link android.content.ServiceConnection#onServiceConnected
[all …]

123456789