| /frameworks/base/libs/hwui/ |
| D | ResourceCache.h | 41 ResourceReference() { refCount = 0; recycled = false; destroyed = false;} in ResourceReference()
43 refCount = 0; recycled = false; destroyed = false; resourceType = type; in ResourceReference()
48 bool destroyed; variable
|
| D | ResourceCache.cpp | 35 i, ref->refCount, ref->recycled, ref->destroyed, ref->resourceType); in logCache()
141 ref->destroyed = true; in destructor()
158 ref->destroyed = true; in destructor()
172 ref->destroyed = true; in destructor()
186 ref->destroyed = true; in destructor()
200 if (ref->destroyed) { in deleteResourceReference()
|
| /frameworks/base/services/java/com/android/server/am/ |
| D | EventLogTags.logtags | 50 # An activity is being destroyed:
67 # A service is being destroyed
|
| /frameworks/base/docs/html/guide/topics/fundamentals/ |
| D | activities.jd | 66 is popped from the stack (and destroyed) and the previous activity resumes. (The back stack is
91 the activity is being created, stopped, resumed, or destroyed. The two most important callback
103 activity (though it does not always mean the activity is being destroyed). This is usually where you
110 to be stopped and even destroyed. All of the lifecycle callback methods are discussed later, in
423 // The activity is about to be destroyed.
553 may happen because it is being destroyed, or because another activity
565 <td>Called before the activity is destroyed. This is the final call
622 remains intact (left), or the activity is destroyed, then recreated and the activity must restore
627 android.app.Activity} object is destroyed, so the system cannot simply resume it with its state
630 that the system destroyed the activity and recreated it and, thus, probably
[all …]
|
| D | services.jd | 81 can run in the background indefinitely, even if the component that started it is destroyed. Usually,
91 but when all of them unbind, the service is destroyed.</dd>
165 <dd>The system calls this method when the service is no longer used and is being destroyed.
281 the component that started it is destroyed. As such, the service should stop itself when its job
296 destroyed.</p>
724 that you pay close attention to how your service is created and destroyed, because a service
727 <p>The service lifecycle—from when it's created to when it's destroyed—can follow two
806 // The service is no longer used and is being destroyed
|
| D | tasks-and-back-stack.jd | 96 key, the current activity is popped from the top of the stack (the activity is destroyed) and the
107 destroyed and the previous activity resumes.</p>
169 destroyed. The previous activity in the stack is resumed. When an activity is destroyed, the system
180 the state of your activities using callback methods, in case the activity is destroyed and must
396 destroyed and this intent is delivered to the resumed instance of the activity (now on top),
|
| D | bound-services.jd | 13 <li>A bound service is destroyed once all clients unbind, unless the service was also started</li>
547 <p>When your client is destroyed, it will unbind from the service, but you should always unbind
625 two of those activities, the service may be destroyed and recreated as the current activity unbinds
|
| D | processes-and-threads.jd | 69 components running in the process that's killed are consequently destroyed. A process is started
367 when the activity is destroyed, see the source code for the <a
|
| D | fragments.jd | 74 fragments in it, and when the activity is destroyed, so are all fragments. However, while an
175 fragment (though it does not always mean the fragment is being destroyed). This is usually where you
484 destroyed when the transaction is committed and the user cannot navigate back to it. Whereas, if you
|
| /frameworks/base/docs/html/resources/articles/ |
| D | faster-screen-orientation-change.jd | 50 destroyed and recreated. </p>
110 // The activity was destroyed/created automatically, populate the grid
|
| D | avoiding-memory-leaks.jd | 83 drawables' callbacks to null when the activity is destroyed. Interestingly
|
| D | painless-threading.jd | 139 …ks across configuration changes and how to cancel them properly when the activity is destroyed.</p>
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | runtime-changes.jd | 47 process may have been destroyed. To learn how you can restore your activity state, read about the <a
248 destroyed before the user returns to it.</p>
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | activity_task_design.jd | 403 destroyed. Starting Email again from its icon would simply bring the
426 destroyed when BACK is pressed. When the user starts playing music in
429 destroyed, and continues playing music, even though its activity is no
|
| /frameworks/base/docs/html/guide/topics/testing/ |
| D | activity_testing.jd | 195 activity to be destroyed, so you should test that accidental device movements don't
|
| /frameworks/base/docs/html/guide/basics/ |
| D | appmodel.jd | 169 be destroyed and a new instance started.</p>
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | menus.jd | 283 android.view.Menu} you define in this method until your activity is destroyed. If you want to change
572 application is destroyed. If you have application settings that you would like to save for the user,
|
| D | actionbar.jd | 242 current task, then all activities on top of it are destroyed and it is brought to the front.
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| D | 2d-graphics.jd | 150 …out the underlying {@link android.view.Surface}, such as when it is created, changed, or destroyed.
|
| /frameworks/base/docs/html/guide/topics/ |
| D | fundamentals.jd | 109 and has a distinct lifecycle that defines how the component is created and destroyed.</p>
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | camera.jd | 458 // underlying surface is created and destroyed.
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | activity-element.jd | 315 activity is ignored. The activity is not re-parented, but destroyed.
|
| /frameworks/base/docs/html/resources/tutorials/testing/ |
| D | activity_test.jd | 434 even if it's interrupted by a phone call or destroyed because of memory constraints.
|
| /frameworks/base/docs/html/guide/publishing/ |
| D | licensing.jd | 1563 {@link android.content.Context} is destroyed. If your application does not
|