Home
last modified time | relevance | path

Searched refs:alive (Results 1 – 12 of 12) sorted by relevance

/frameworks/base/core/jni/
Dandroid_util_Binder.cpp982 bool alive = target->isBinderAlive(); in android_os_BinderProxy_isBinderAlive() local
983 return alive ? JNI_TRUE : JNI_FALSE; in android_os_BinderProxy_isBinderAlive()
/frameworks/base/docs/html/training/multiple-threads/
Dcreate-threadpool.jd179 Keep alive time and time unit
/frameworks/base/docs/html/training/basics/activity-lifecycle/
Dstopping.jd36 that ensures your users perceive that your app is always alive and doesn't lose their progress.
/frameworks/base/docs/html/guide/components/
Dactivities.jd361 cover the entire screen. A paused activity is completely alive (the {@link android.app.Activity}
367 "background"). A stopped activity is also still alive (the {@link android.app.Activity}
609 stopped—all information about its members and current state is still alive. Thus, any changes
Dprocesses-and-threads.jd162 kind of process alive is for caching purposes, to improve startup time the next time a component
Dbound-services.jd588 android.content.Context#BIND_AUTO_CREATE} in order to create the service if its not already alive.
Dfragments.jd666 still alive (all state and member information is retained by the system). However, it is no longer
/frameworks/base/docs/html/training/efficient-downloads/
Defficient-network-access.jd161 …ag()} value. These libraries also tag and untag sockets when recycled through keep-alive pools.</p>
/frameworks/base/docs/html/tools/debugging/
Dddms.jd252 keep-alive pools. In the following example,
/frameworks/base/docs/html/preview/
Dapi-overview.jd293 apps to find out which of their notifications are currently alive. To see an app implementation
/frameworks/base/docs/html/training/articles/
Dmemory.jd271 the system prefers to keep alive, such as those hosting a running service.</p>
/frameworks/base/docs/html/google/play/
Dexpansion-files.jd530 &lt;!-- Required to keep CPU alive while downloading files