Searched full:application (Results 1 – 25 of 91) sorted by relevance
1234
| /docs/source.android.com/src/devices/tech/security/overview/ |
| D | app-security.jd | 1 page.title=Application security
27 <p>Android provides an open source platform and application environment for mobile
33 <p>The main Android application building blocks are:</p>
39 receivers, and content providers described below) in an application. This also
46 Activities never display UIs. Typically, one of the application's Activities
47 is the entry point to an application.</p>
51 or in the context of another application's process. Other components "bind" to
60 …tent.html">Intent</a> is issued by the operating system or another application. An application may
66 <p>All applications on Android run in an Application Sandbox, described earlier in this document.
67 By default, an Android application can only access a limited range of system
[all …]
|
| D | kernel-security.jd | 30 native code is constrained by the Application Sandbox. Whether that code is
31 the result of included application behavior or a exploitation of an application
32 vulnerability, the system would prevent the rogue application from harming
59 <h3 id="the-application-sandbox">The Application Sandbox</h3>
61 means of identifying and isolating application resources. The Android system
62 assigns a unique user ID (UID) to each Android application and runs it as that user
66 <p>This sets up a kernel-level Application Sandbox. The kernel enforces security
70 limited access to the operating system. If application A tries to do something
71 malicious like read application B's data or dial the phone without permission
72 (which is a separate application), then the operating system protects against
[all …]
|
| D | index.jd | 71 <li>Provide application isolation</li>
76 <li>Mandatory application sandbox for all applications</li>
78 <li>Application signing</li>
79 <li>Application-defined and user-granted permissions</li>
|
| /docs/source.android.com/src/devices/tech/datausage/ |
| D | kernel-overview.jd | 19 <p>The per-application/delegated data usage monitoring and tracking
30 restrict background data traffic for an application (refer to
36 per-socket basis for every application using the unique UID of the
37 owning application. There are two tag components associated with any
39 the application which is responsible for the data transfer (Linux
41 the UID of the calling application). The second tag component is used
42 to support additional characterization of the traffic into application
43 developer specified categories. Using these application level tags, an
44 application can profile the traffic into several sub-categories.</p>
48 to the UID of the requesting application using the
|
| /docs/source.android.com/src/devices/tech/security/ |
| D | index.jd | 29 consumers. To protect that value, the platform must offer an application
54 related to the browser or SMS application. Recommended best practices for
59 <p>Android provides an open source platform and application environment for mobile
66 restricted by the Application Sandbox.</p>
84 <p><strong>Android Application Runtime</strong>: Android applications are most often written
89 Application Sandbox. Applications get a dedicated part of the filesystem in
106 environment supporting any third-party application. Google Play offers
118 application <a href="https://developer.android.com/guide/publishing/licensing.html">license
119 verification</a>, application security scanning, and other security services.</p>
127 <p><strong>Application Services</strong>: Frameworks that allow Android applications to use
[all …]
|
| D | implement.jd | 58 <strong>should</strong> be run on all application code using the Android SDK.
92 <p>Application signatures play an important role in device security. They are used
94 for signing applications, it is important to consider whether an application
105 different keys. This often occurs when creating an application for different
106 devices, especially when using the platform key. If the application is
107 device-independent, then use the same key across devices. If the application
115 your application has a unique package name.</p>
163 an application with low or no privileges to handle network traffic.</li>
186 <p>The Android Application Sandbox provides applications with an expectation of
188 debuggers. Unless debugging is specifically enabled by the application and the
[all …]
|
| /docs/source.android.com/src/devices/sensors/ |
| D | sensor-stack.jd | 38 <p>When registering to a sensor, the application specifies its preferred sampling
41 <li> For example, an application might register to the default accelerometer,
44 <li> The application will receive events from the accelerometer at a rate of at
50 framework level, only a single application could access each sensor at any
53 <li> When a first application registers to a sensor, the framework sends a request
56 into account requirements from each application and sends the updated requested
62 …um reporting latency</a> will be the minimum of the requested ones. If one application requests one
68 <li> When the last application registered to one sensor unregisters from it, the
76 <li> When an application requests a specific sampling frequency, there is no
77 guarantee that events won’t arrive at a faster rate. If another application
[all …]
|
| /docs/source.android.com/src/compatibility/2.2/ |
| D | android-2.2-cdd.xhtml | 29 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
54 <a href="#section-5">5. Application Packaging Compatibility</a><br/>
83 <a href="#section-8.15">8.15. Application Shared Storage</a><br/>
150 <a name="resources13"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
180 web-application APIs. This section details the hard and soft APIs that are
187 Android applications. The Android application programming interface (API) is
200 be enforced at application compile time. This section details the "soft" APIs
229 accessible to third-party application code. For Android 2.2, this field MUST have
341 <a name="section-3.2.3.1"></a><h4>3.2.3.1. Core Application Intents</h4>
362 <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
[all …]
|
| /docs/source.android.com/src/devices/tech/security/enhancements/ |
| D | enhancements42.jd | 11 <li><strong>Application verification</strong> - Users can choose to enable “Verify Apps" and
12 have applications screened by an application verifier, prior to installation.
14 harmful; if an application is especially bad, it can block installation.</li>
16 application attempts to send SMS to a short code that uses premium services
18 application to send the message or block it.</li>
|
| /docs/source.android.com/src/accessories/ |
| D | custom.jd | 45 adb or audio protocol), you must provide an Android application that can detect the connection of
58 <li>If you are planning to build an Android application that communicates with your accessory
60 …<a href="http://developer.android.com/tools/adk/adk2.html#src-download">application source code</a>
70 use it. You can also provide a secondary Android application that handles any specialized
80 <li>If you are planning to build an Android application that communicates with your accessory
82 …<a href="http://developer.android.com/tools/adk/adk2.html#src-download">application source code</a>
94 that accessory. No secondary software application is required on the Android device.</p>
|
| D | aoa2.jd | 24 (HID) to the Android device. The Android SDK APIs available to Android application developers
63 Android application.</li>
179 application to communicate directly with a USB host (accessory) over USB. AOA 2.0 keeps that
187 HID support, but does not need to communicate with an application on the Android device. In that
189 attached accessory with an Android application that can communicate with it. To prevent these
193 2.0 without the system attempting to find an application to communicate with the accessory. Also,
|
| /docs/source.android.com/src/compatibility/4.0/ |
| D | android-4.0-cdd.xhtml | 35 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
43 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
61 <a href="#section-3.8.7">3.8.7. Recent Application Display</a><br/>
68 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
86 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
128 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
202 <a name="resources20"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
257 Android applications. The Android application programming interface (API) is
275 be enforced at application compile time.</p>
302 accessible to third-party application code. For Android 4.0.1 - 4.0.2, this
[all …]
|
| /docs/source.android.com/src/compatibility/2.1/ |
| D | android-2.1-cdd.xhtml | 63 <a name="resources13"/><li>Application Resources: <a href="http://code.google.com/android/reference…
92 web-application APIs. This section details the hard and soft APIs that are
99 Android applications. The Android application programming interface (API) is
112 be enforced at application compile time. This section details the "soft" APIs
141 accessible to third-party application code. For Android 2.1, this field MUST have
253 <h4>3.2.3.1. Core Application Intents</h4>
274 <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
324 application .apk file as an ELF .so file compiled for the appropriate device
351 <p>Device implementations MUST accurately report the native Application Binary
387 Browser application. What's more, the standalone Browser MAY be based on an
[all …]
|
| /docs/source.android.com/src/devices/tech/security/selinux/ |
| D | index.jd | 29 <p>The Android security model is based in part on the concept of application
30 sandboxes. Each application runs in its own sandbox. Prior to Android 4.3,
32 application at time of installation. Starting with Android 4.3,
34 the Android application sandbox.</p>
43 access to application data and system logs, reduce the effects of malicious
62 incremental application of SELinux to an ever-increasing portion of the system.
|
| /docs/source.android.com/src/devices/ |
| D | index.jd | 54 <h2 id="Application framework">Application framework</h2>
56 The application framework is used most often by application developers. As a
64 The Binder Inter-Process Communication (IPC) mechanism allows the application
67 services. At the application framework level, this communication is hidden from
73 Functionality exposed by application framework APIs communicates with system
|
| /docs/source.android.com/src/compatibility/2.3/ |
| D | android-2.3-cdd.xhtml | 29 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
53 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
109 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
186 <a name="resources18"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
224 web-application APIs. This section details the hard and soft APIs that are
231 Android applications. The Android application programming interface (API) is
248 be enforced at application compile time. This section details the "soft" APIs
277 accessible to third-party application code. For Android 2.3, this field MUST have
394 <a name="section-3.2.3.1"></a><h4>3.2.3.1. Core Application Intents</h4>
415 <!-- <li>LivePicker (that is, the Live Wallpaper picker application; MAY be omitted
[all …]
|
| /docs/source.android.com/src/compatibility/4.2/ |
| D | android-4.2-cdd.xhtml | 35 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
43 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
61 <a href="#section-3.8.7">3.8.7. Recent Application Display</a><br/>
71 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
94 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
138 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
214 <a name="resources20"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
271 <a name="resources77"></a><li>Android Application Development-Related Settings: <a href="http://dev…
285 Android applications. The Android application programming interface (API) is
303 be enforced at application compile time.</p>
[all …]
|
| /docs/source.android.com/src/compatibility/4.3/ |
| D | android-4.3-cdd.xhtml | 35 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
43 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
62 <a href="#section-3.8.8">3.8.8. Recent Application Display</a><br/>
71 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
94 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
140 <a href="#section-7.6.2">7.6.2. Application Shared Storage</a><br/>
216 <a name="resources20"></a><li>Application Resources: <a href="http://code.google.com/android/refere…
273 <a name="resources77"></a><li>Android Application Development-Related Settings: <a href="http://dev…
290 Android applications. The Android application programming interface (API) is
308 be enforced at application compile time.</p>
[all …]
|
| /docs/source.android.com/src/devices/camera/ |
| D | camera3_metadata.jd | 34 getCameraInfo() method to provide this information to the application.</p>
40 clamping or rounding took place, and so that the application can compensate for
42 <p>For example, if an application sets frame duration to 0 in a request, the HAL
45 <p>So if an application needs to implement a custom 3A routine (for example, to
|
| /docs/source.android.com/src/devices/graphics/ |
| D | port-tests.jd | 64 <td><p>New platform port and application stub can be implemented as described in <a href="#test_fra…
77 <p>The deqp test framework platform port requires two components: An application
80 <p>The application entry point is responsible for creating the platform object,
81 …opening a test log (<code>tcu::TestLog</code>), and iterating the test application (<code>tcu::App…
111 <td><p>Standard application entry point</p>
|
| /docs/source.android.com/src/compatibility/4.4/ |
| D | android-4.4-cdd.xhtml | 35 <a href="#section-3.2.3.1">3.2.3.1. Core Application Intents</a><br/>
44 <a href="#section-3.3.1">3.3.1 Application Binary Interfaces</a><br/>
63 <a href="#section-3.8.8">3.8.8. Recent Application Display</a><br/>
74 <a href="#section-4">4. Application Packaging Compatibility</a><br/>
98 <a href="#section-7.1.5">7.1.5. Legacy Application Compatibility Mode</a><br/>
225 <a name="resources20"></a><li id="resources20">Application Resources: <a href="http://code.google.c…
285 <a name="resources77"></a><li id="resources77">Android Application Development-Related Settings: <a…
314 Android applications. The Android application programming interface (API) is
332 be enforced at application compile time.</p>
359 accessible to third-party application code. For Android 4.4, this
[all …]
|
| /docs/source.android.com/src/compatibility/ |
| D | overview.jd | 33 <p><em>Provide a consistent application and hardware environment to application
44 <p><em>Enable a consistent application experience for consumers.</em>
45 If an application runs well on one compatible Android device, it should run well on
|
| D | android-cdd.html | 33 <p class="toc_h4"><a href="#3_2_3_1_core_application_intents">3.2.3.1. Core Application Intents</a>…
45 <p class="toc_h3"><a href="#3_3_1_application_binary_interfaces">3.3.1. Application Binary Interfac…
105 <p class="toc_h1"><a href="#4_application_packaging_compatibility">4. Application Packaging Compati…
177 <p class="toc_h3"><a href="#7_1_5_legacy_application_compatibility_mode">7.1.5. Legacy Application …
261 <p class="toc_h3"><a href="#7_6_2_application_shared_storage">7.6.2. Application Shared Storage</a>…
541 Android applications. The Android application programming interface (API) is
561 applications that cannot be enforced at application compile time.</p>
589 to third-party application code. For Android ANDROID_VERSION, this field MUST have the
595 to third-party application code. For Android ANDROID_VERSION, this field MUST have the
749 <h4 id="3_2_3_1_core_application_intents">3.2.3.1. Core Application Intents</h4>
[all …]
|
| /docs/source.android.com/src/devices/tech/test_infra/tradefed/ |
| D | index.jd | 20 on Android devices. It's a Java application which runs on a host computer, and communicates to one …
46 An application developer, on the other hand, can modify the app, but has little control over most
74 <p>An Application Developer builds an app which needs to run well across a variety of platform
90 build of the application.</p>
|
| /docs/source.android.com/src/compatibility/5.1/ |
| D | android-5.1-cdd.html | 33 <p class="toc_h4"><a href="#3_2_3_1_core_application_intents">3.2.3.1. Core Application Intents</a>…
45 <p class="toc_h3"><a href="#3_3_1_application_binary_interfaces">3.3.1. Application Binary Interfac…
105 <p class="toc_h1"><a href="#4_application_packaging_compatibility">4. Application Packaging Compati…
175 <p class="toc_h3"><a href="#7_1_5_legacy_application_compatibility_mode">7.1.5. Legacy Application …
259 <p class="toc_h3"><a href="#7_6_2_application_shared_storage">7.6.2. Application Shared Storage</a>…
539 Android applications. The Android application programming interface (API) is
559 applications that cannot be enforced at application compile time.</p>
587 to third-party application code. For Android 5.1, this field MUST have the
593 to third-party application code. For Android 5.1, this field MUST have the
747 <h4 id="3_2_3_1_core_application_intents">3.2.3.1. Core Application Intents</h4>
[all …]
|
1234