| /frameworks/base/libs/hwui/unit_tests/ |
| D | LinearAllocatorTests.cpp | 65 bool destroyed[10]; in TEST() local
69 la.alloc<SignalingDtor>()->setSignal(destroyed + i); in TEST()
74 auto sd = new (la) SignalingDtor(destroyed + 5 + i); in TEST()
80 EXPECT_FALSE(destroyed[i]); in TEST()
84 EXPECT_TRUE(destroyed[i]); in TEST()
89 bool destroyed; in TEST() local
98 sigdtor->setSignal(&destroyed); in TEST()
99 EXPECT_FALSE(destroyed); in TEST()
102 EXPECT_TRUE(destroyed); in TEST()
104 destroyed = false; in TEST()
[all …]
|
| /frameworks/support/v7/appcompat/tests/src/android/support/v7/app/ |
| D | BaseKeyEventsTestCase.java | 38 final AtomicBoolean destroyed = new AtomicBoolean(); in testBackDismissesActionMode() local
62 destroyed.set(true); in testBackDismissesActionMode()
73 assertTrue("ActionMode was destroyed", destroyed.get()); in testBackDismissesActionMode()
|
| /frameworks/base/libs/hwui/ |
| D | ResourceCache.h | 46 refCount = 0; destroyed = false; resourceType = type; in ResourceReference()
50 bool destroyed; variable
|
| D | ResourceCache.cpp | 40 i, ref->refCount, ref->destroyed, ref->resourceType); in logCache()
126 ref->destroyed = true; in destructorLocked()
137 if (ref->destroyed) { in deleteResourceReferenceLocked()
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | recreating.jd | 31 <p>There are a few scenarios in which your activity is destroyed due to normal app behavior, such as
37 <p>When your activity is destroyed because the user presses <em>Back</em> or the activity finishes
43 saved data that describes the state of the activity when it was destroyed. The saved data that the
47 <p class="caution"><strong>Caution:</strong> Your activity will be destroyed and recreated each time
54 into an {@link android.widget.EditText} object). So, if your activity instance is destroyed and
69 event that your activity is destroyed unexpectedly. If
80 If the activity is destroyed and the same instance must be recreated, the system passes the state
123 <p>When your activity is recreated after it was previously destroyed, you can recover your saved
133 that was destroyed.</p>
143 // Check whether we're recreating a previously destroyed instance
|
| D | stopping.jd | 124 other state data in case your activity is destroyed and recreated).</p>
136 the activity was previously stopped, but not destroyed.</p>
187 additional threads are destroyed and other long-running actions like method tracing are also
|
| D | index.jd | 71 <dd>Learn what happens when your activity is destroyed and how you can rebuild the activity
|
| /frameworks/base/services/core/java/com/android/server/am/ |
| D | EventLogTags.logtags | 50 # An activity is being destroyed:
67 # A service is being destroyed
|
| /frameworks/base/core/java/android/print/ |
| D | PrintManager.java | 532 final boolean destroyed; in setObserver()
535 destroyed = isDestroyedLocked(); in setObserver()
538 if (destroyed && observer != null) { in setObserver()
|
| /frameworks/base/docs/html/training/camera/ |
| D | cameradirect.jd | 113 // underlying surface is created and destroyed.
242 preview surface destroyed is a pretty good hint that it’s time to stop the
248 // Surface will be destroyed when we return, so stop the preview.
|
| /frameworks/base/docs/html/guide/components/ |
| D | activities.jd | 61 is popped from the stack (and destroyed) and the previous activity resumes. (The back stack is
86 the activity is being created, stopped, resumed, or destroyed. The two most important callback
98 activity (though it does not always mean the activity is being destroyed). This is usually where you
105 to be stopped and even destroyed. All of the lifecycle callback methods are discussed later, in
418 // The activity is about to be destroyed.
548 may happen because it is being destroyed, or because another activity
560 <td>Called before the activity is destroyed. This is the final call
614 android.app.Activity} object is destroyed, so the system cannot simply resume it with its state
617 that the system destroyed the activity and recreated it and, thus, probably
639 focus with its state intact: either the activity is destroyed, then recreated and the activity must…
[all …]
|
| D | services.jd | 66 can run in the background indefinitely, even if the component that started it is destroyed. Usually,
76 but when all of them unbind, the service is destroyed.</dd>
150 <dd>The system calls this method when the service is no longer used and is being destroyed.
247 the component that started it is destroyed. As such, the service should stop itself when its job
262 destroyed.</p>
685 that you pay close attention to how your service is created and destroyed, because a service
688 <p>The service lifecycle—from when it's created to when it's destroyed—can follow two
758 // The service is no longer used and is being destroyed
|
| D | tasks-and-back-stack.jd | 92 button, the current activity is popped from the top of the stack (the activity is destroyed) and the
105 destroyed and the previous activity resumes.</p>
174 destroyed. The previous activity in the stack is resumed. When an activity is destroyed, the system
192 the state of your activities using callback methods, in case the activity is destroyed and must
411 destroyed and this intent is delivered to the resumed instance of the activity (now on top),
|
| /frameworks/base/docs/html-intl/intl/ru/training/basics/activity-lifecycle/ |
| D | recreating.jd | 142 // Check whether we're recreating a previously destroyed instance
|
| /frameworks/base/docs/html-intl/intl/zh-tw/training/basics/activity-lifecycle/ |
| D | recreating.jd | 142 // Check whether we're recreating a previously destroyed instance
|
| /frameworks/base/docs/html-intl/intl/ja/training/basics/activity-lifecycle/ |
| D | recreating.jd | 142 // Check whether we're recreating a previously destroyed instance
|
| /frameworks/base/docs/html-intl/intl/ko/training/basics/activity-lifecycle/ |
| D | recreating.jd | 142 // Check whether we're recreating a previously destroyed instance
|
| /frameworks/base/docs/html/training/basics/fragments/ |
| D | fragment-ui.jd | 161 to the back stack, the fragment that is removed is stopped (not destroyed). If the user navigates
163 stack, then the fragment is destroyed when removed or replaced.</p>
|
| /frameworks/base/docs/html-intl/intl/zh-cn/training/basics/activity-lifecycle/ |
| D | recreating.jd | 142 // Check whether we're recreating a previously destroyed instance
|
| /frameworks/base/docs/html/ndk/reference/ |
| D | struct_a_native_activity_callbacks.jd | 89 <p>NativeActivity is being destroyed. See Java documentation for Activity.onDestroy() for more info…
115 <p>The input queue for this native activity's window is being destroyed. You should no longer try t…
154 <p>The drawing window for this native activity is going to be destroyed. You MUST ensure that you d…
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | runtime-changes.jd | 46 process may have been destroyed. To learn how you can restore your activity state, read about the <a
81 of your activity that you have marked to retain are not destroyed. You can add such fragments to
285 destroyed before the user returns to it.</p>
|
| /frameworks/base/docs/html/ndk/samples/ |
| D | sample_teapot.jd | 133 information so that the system can restore a destroyed activity. This ability is useful, for
135 destroyed, then immediately restored in the new orientation), or when the lock
|
| /frameworks/base/docs/html/training/location/ |
| D | location-testing.jd | 177 to keep running even if the app's main {@link android.app.Activity} is destroyed because of
216 main {@link android.app.Activity} is destroyed.
280 thread is also destroyed.
|
| /frameworks/base/docs/html/training/tv/playback/ |
| D | now-playing.jd | 41 has been destroyed. For this discussion, the media playback app is assumed to be running in a
|
| /frameworks/base/docs/html-intl/intl/pt-br/training/basics/activity-lifecycle/ |
| D | recreating.jd | 142 // Check whether we're recreating a previously destroyed instance
|