| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 4 <p>In most cases, every Android application runs in its own Linux process.
5 This process is created for the application when some of its code needs to
9 <p>An unusual and fundamental feature of Android is that an application process's
19 of the application's process. <strong>Not using these components correctly can
20 result in the system killing the application's process while it is doing
23 <p>A common example of a process life-cycle bug is a
29 process no longer needed (unless other application components are active in
30 it). So, the system may kill the process at any time to reclaim memory, and in doing so,
31 it terminates the spawned thread running in the process. The solution to this problem
33 system knows that there is still active work being done in the process.</p>
[all …]
|
| /frameworks/base/tools/preload/ |
| D | LoadedClass.java | 63 if (load.process.fromZygote()) { in isSharable()
64 procNames.add(load.process.name); in isSharable()
71 if (init.process.fromZygote()) { in isSharable()
72 procNames.add(init.process.name); in isSharable()
144 if (operation.process.fromZygote()) { in addProcessNames()
145 names.add(operation.process.name); in addProcessNames()
|
| D | Operation.java | 36 final Proc process; field in Operation
57 Operation(Proc process, LoadedClass loadedClass, long startTimeNanos, in Operation() argument
59 this.process = process; in Operation()
|
| D | Root.java | 56 Proc process = processes.get(record.pid); in indexClassOperation() local
85 o = process.endOperation(record.tid, record.className, in indexClassOperation()
94 process.startOperation(record.tid, loadedClass, record.time, in indexClassOperation()
99 process.startOperation(record.tid, loadedClass, record.time, in indexClassOperation()
|
| D | MemoryUsage.java | 232 final Process process = Runtime.getRuntime().exec(commands); in measure() local
234 final InputStream err = process.getErrorStream(); in measure()
247 new InputStreamReader(process.getInputStream())); in measure()
258 process.destroy(); in measure()
|
| D | PrintCsv.java | 84 procNames.add(op.process.name); in printRow()
86 procNames.add(op.process.name); in printRow()
|
| D | PrintHtmlDiff.java | 107 for (Operation op : clazz.loads) procNames.add(op.process.name); in printTable()
109 procNames.add(op.process.name); in printTable()
|
| D | PrintBugReports.java | 232 procNames.add(op.process.name); in printTable()
235 procNames.add(op.process.name); in printTable()
|
| /frameworks/base/docs/html/guide/basics/ |
| D | appmodel.jd | 7 the process it runs in, and the icon and application the user interacts with.
27 <li><p>A <strong>process</strong> is a low-level kernel process in which
29 .apk is run in one, dedicated process for that .apk; however, the
30 {@link android.R.styleable#AndroidManifestApplication_process process} tag
198 into another process.
200 process.
202 a separate process that can be killed independently of other parts of the
207 {@link android.R.styleable#AndroidManifestApplication_process process} attribute
208 is used to control the process that particular application components run in.
210 two .apks that are not sharing the same user ID try to run in the same process,
[all …]
|
| D | building-blocks.jd | 10 <p>Generally, these components all run in the same system process. It's
11 possible (and quite common) to create multiple threads within that process,
54 its own process, or in the context of another application's process,
|
| /frameworks/base/docs/html/guide/appendix/faq/ |
| D | framework.jd | 8 application run in a single process?</a></li>
10 an application process?</a></li>
27 single process?</h2>
29 <p>All Activities and Services in an application run in a single process by
30 default. If needed, you can declare an <code>android:process</code> attribute
32 another process.</p>
39 process?</h2>
41 <p>By default, all of the application code in a single process runs
45 separate pool of transaction threads in each process to dispatch all
108 may choose to kill its process and restart it later. If you have data
[all …]
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | application-element.jd | 18 android:<a href="#proc">process</a>="<i>string</i>"
39 {@code icon}, {@code label}, {@code permission}, {@code process},
142 subclass implemented for the application. When the application process
173 <dt><a name="proc"></a>{@code android:process}</dt>
174 <dd>The name of a process where all components of the application should run.
175 Each component can override this default by setting its own {@code process}
179 By default, Android creates a process for an application when the first
180 of its components needs to run. All components then run in that process.
181 The name of the default process matches the package name set by the
185 <p>By setting this attribute to a process name that's shared with another
[all …]
|
| D | receiver-element.jd | 12 android:<a href="#proc">process</a>="<i>string</i>" >
143 <dt><a name="proc"></a>{@code android:process}</dt>
144 <dd>The name of the process in which the broadcast receiver should run.
145 Normally, all components of an application run in the default process created
148 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#proc">process</a></code> at…
150 with its own {@code process} attribute, allowing you to spread your
155 process, private to the application, is created when it's needed and
156 the broadcast receiver runs in that process.
157 If the process name begins with a lowercase character, the receiver will run
158 in a global process of that name, provided that it has permission to do so.
[all …]
|
| D | service-element.jd | 12 android:<a href="#proc">process</a>="<i>string</i>" >
150 <dt><a name="proc"></a>{@code android:process}</dt>
151 <dd>The name of the process where the service is to run. Normally,
152 all components of an application run in the default process created for the
155 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#proc">process</a></code>
158 with its own {@code process} attribute, allowing you to spread your
163 process, private to the application, is created when it's needed and
164 the service runs in that process.
165 If the process name begins with a lowercase character, the service will run
166 in a global process of that name, provided that it has permission to do so.
[all …]
|
| D | provider-element.jd | 16 android:<a href="#proc">process</a>="<i>string</i>"
162 relative to other content providers hosted by the same process.
183 every client process — "{@code true}" if instances can run in multiple
187 Normally, a content provider is instantiated in the process of the
189 the system can create an instance in every process where there's a client
226 <dt><a name="proc"></a>{@code android:process}</dt>
227 <dd>The name of the process in which the content provider should run. Normally,
228 all components of an application run in the default process created for the
231 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#proc">process</a></code>
234 with its own {@code process} attribute, allowing you to spread your
[all …]
|
| D | manifest-element.jd | 55 It's also the default name for the application process (see the
58 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#aff">process</a></code>
59 process</a></code> attribute) and the default task affinity of an activity
72 other's data and, if desired, run in the same process.</dd>
|
| /frameworks/base/docs/html/guide/topics/ |
| D | fundamentals.jd | 66 <li>By default, every application runs in its own Linux process.
67 Android starts the process when any of the application's code needs to be
68 executed, and shuts down the process when it's no longer needed and system
71 <li>Each process has its own Java virtual machine (VM), so application code
84 in the same Linux process, sharing the same VM.
102 For this to work, the system must be able to start an application process
190 the application process. So that they won't block other components or the
242 Android makes sure that the application process of the component is running,
526 that application's process. Android maintains this user experience by keeping
897 starts a Linux process for it with a single thread of execution. By default,
[all …]
|
| /frameworks/base/docs/html/guide/developing/tools/ |
| D | aidl.jd | 23 <p>Since each application runs in its own process, and you can write a service that
24 runs in a different process from your Application's UI, sometimes you need to pass objects
25 between processes. On the Android platform, one process can not normally access the memory
26 of another process. So to talk, they need to decompose their objects into primitives that
36 in one process (for example, in an Activity) that needs to call methods on an
37 object in another process (for example, a Service), you would use AIDL to
140 the build process (you don't need to run AIDL first and then build your project).
151 methods without building between--the Android build process will process .aidl
188 <p>If you have a class that you would like to send from one process to another through
201 that declares your parcelable class (as shown below). If you are using a custom build process,
|
| D | ddms.jd | 6 and heap information on the device, logcat, process, and radio state information,
18 the device. On Android, every application runs in its own process,
19 each of which hosts its own virtual machine (VM). And each process
26 or terminated. Once a VM is running, DDMS retrieves the the VM's process ID (pid), via adb,
30 …forwarded between the debugger and the associated VM. Debugging can then process like any remote d…
70 somehow failed to make a successful handshake with the VM process. Try restarting DDMS.</p>
78 <p>This view shows some general information about the selected VM, including the process
82 <p> The threads view has a list of threads running in the process of the target VM.
91 <li> <strong>Tid</strong> - the Linux thread ID. For the main thread in a process,
92 this will match the process ID. </li>
[all …]
|
| /frameworks/base/docs/html/guide/topics/security/ |
| D | security.jd | 24 <p>Android is a multi-process system, in which each application (and parts of the
25 system) runs in its own process. Most security between applications and
26 the system is enforced at the process level through standard Linux facilities,
30 operations that a particular process can perform, and per-URI permissions
43 <p>An application's process is a secure sandbox. It can't disrupt other
77 process level, the code of any two packages can not normally
78 run in the same process, since they need to run as different Linux users.
339 permission has been granted to the current calling process. Note that this can
340 only be used when you are executing a call coming in from another process,
342 given to another process.</p>
[all …]
|
| /frameworks/base/include/binder/ |
| D | IPCThreadState.h | 37 sp<ProcessState> process();
|
| /frameworks/base/core/java/android/app/ |
| D | ActivityManager.java | 321 public String process; field in ActivityManager.RunningServiceInfo
415 dest.writeString(process); in writeToParcel()
432 process = source.readString(); in readFromParcel()
|
| /frameworks/base/cmds/am/src/com/android/commands/am/ |
| D | Am.java | 313 String process = nextArgRequired(); in runProfile() local
334 if (!mAm.profileControl(process, start, profileFile, fd)) { in runProfile()
335 throw new AndroidException("PROFILE FAILED on process " + process); in runProfile()
|
| /frameworks/base/libs/rs/ |
| D | rsFileA3D.h | 98 bool process(Context *rsc);
|
| /frameworks/base/libs/audioflinger/ |
| D | AudioMixer.h | 84 void process(void* output);
|