Lines Matching refs:processes

34 different components in your application to run in separate processes, and you can create additional
37 <p>This document discusses how processes and threads work in an Android application.</p>
63 other processes that are more immediately serving the user. Application
67 <p>When deciding which processes to kill, the Android system weighs their relative importance to
71 rules used to decide which processes to terminate is discussed below. </p>
77 eventually needs to remove old processes to reclaim memory for new or more important processes.  To
78 determine which processes to keep
85 types of processes in order of importance (the first process is <em>most important</em> and is
112     <p>Generally, only a few foreground processes exist at any given time.  They are killed only as
114 point, the device has reached a memory paging state, so killing some foreground processes is
133 is required to keep all foreground processes running. </p>
139 higher categories. Although service processes are not directly tied to anything the user sees, they
142 to retain them along with all foreground and visible processes. </p>
147 {@link android.app.Activity#onStop onStop()} method has been called). These processes have no direct
150 visible, or service process. Usually there are many background processes running, so they are kept
163 needs to run in it.  The system often kills these processes in order to balance overall system
173   <p>In addition, a process's ranking might be increased because other processes are dependent on
386 <p> Similarly, a content provider can receive data requests that originate in other processes.