Lines Matching full:applications
22 applications make use of advanced hardware and software, as well as local and
25 environment that ensures the security of users, data, applications, the device,
39 into how applications work, and control over those applications. This design
42 malware, and attacks on third-party applications on Android. Android was
50 discuss security issues that are unique to specific applications, such as those
52 building Android devices, deploying Android devices, or developing applications
73 <p><strong>Android Application Runtime</strong>: Android applications are most often written
75 However, many applications, including core Android services and applications
76 are native applications or include native libraries. Both Dalvik and native
77 applications run within the same security environment, contained within the
78 Application Sandbox. Applications get a dedicated part of the filesystem in
82 <p>Android applications extend the core Android operating system. There are two
83 primary sources for applications:</p>
86 <p><strong>Pre-Installed Applications</strong>: Android includes a set of pre-installed
87 applications including phone, email, calendar, web browser, and contacts. These
88 function both as user applications and to provide key device capabilities that
89 can be accessed by other applications. Pre-installed applications may be part
94 <p><strong>User-Installed Applications</strong>: Android provides an open development
96 users hundreds of thousands of applications.</p>
104 allow users to discover, install, and purchase applications from their Android
116 <p><strong>Application Services</strong>: Frameworks that allow Android applications to use
131 applications and devices built on and around the Android platform and supported
156 to provide information about specific applications directly to users.</li>
165 Android platform (over-the-air updates), removing applications from Google
166 Play, and removing applications from devices in the field.</li>
179 <li>Mandatory application sandbox for all applications</li>
195 facility to enable secure communication between applications running in
200 other applications, the Android system, or the device itself.</p>
232 (including the traditional Linux configuration), where multiple applications
235 between applications and the system at the process level through standard Linux
236 facilities, such as user and group IDs that are assigned to applications. By
237 default, applications cannot interact with each other and applications have
245 native code and to operating system applications. All of the software above the
247 framework, application runtime, and all applications run within the Application
255 Android due to all applications and their resources being sandboxed at the OS
264 libraries, application runtime, application framework, and applications. This
266 only core Android applications are available. This ensures that the user can
273 applications, files created by one application cannot be read or altered by
280 Android provides a set of cryptographic APIs for use by applications. These
289 applications to use the system credential storage for private
341 applications run with root permissions. Android does not prevent a user or
344 applications and all application data. Users that change the permissions on an
345 Android device to grant root access to applications increase the security
346 exposure to malicious applications and potential application flaws.
353 root access for purposes of debugging applications and system components or to
354 access features not presented to applications by Android APIs.
366 data from root users. Applications can add a layer of data protection using
418 <p>In addition to use in applications included with the Android system, these APIs
425 <h2 id="elements-of-applications">Elements of Applications</h2>
428 applications are most often written in the Java programming language and run in
429 the Dalvik virtual machine. However, applications can also be written in native
430 code. Applications are installed from a single file with the .apk file
473 <p>All applications on Android run in an Application Sandbox, described earlier in this document.
483 sensitive APIs are intended for use by trusted applications and protected
505 of the permissions granted to the application, and applications that are
510 <p>Within the device settings, users are able to view permissions for applications
521 Applications may declare their own permissions for other applications to use.
524 user is to be informed of applications requiring the permission, or who is
530 intents, that are not available to third-party applications, but that may be
531 used by applications pre-installed by the OEM. These permissions use the
533 <h2 id="how-users-understand-third-party-applications">How Users Understand Third-Party Applications</h2>
535 third-party applications and inform the user of the capabilities those
536 applications have. Prior to installation of any application, the user is shown
544 the application to other alternative applications.</p>
546 permission at the start of each session or while applications are in use. The
547 vision of Android is to have users switching seamlessly between applications at
563 information about applications easily accessible to a wide range of users. For
585 <p><em>Figure 2: Display of permissions for applications</em></p>
617 that other applications have exposed via a ContentProvider, and an application
630 permission to third-party applications requesting use of cost sensitive APIs.
649 information (contacts) on the SIM card memory. Applications also cannot access
655 data within third-party applications installed by users. Applications that
657 protect the data from third-party applications.</p>
670 <p>Any applications which collect personal information will, by default, have that
672 make the data available to other applications though IPC, the application
677 applications to interact with the surrounding environment, such as camera,
688 disable location based services for all applications on the user's device.</p>
693 <p>By default applications do not have access to operating system logs,
703 signed by the developer. Applications that attempt to install without being
712 id is associated with which application; different applications run under
721 <p>Applications can be signed by a third-party (OEM, operator, alternative market)
724 Applications do not have to be signed by a central authority. Android currently
726 <p>Applications are also able to declare security permissions at the Signature
727 protection level, restricting access only to applications signed with the same
731 feature</a> where two or more applications signed with same developer key can
737 enable ?Verify Apps" and have applications evaluated by an application verifier
745 applications manage rights-protected content according to the license
754 <p>A DRM framework API, which is exposed to applications through the Android
755 application framework and runs through the Dalvik VM for standard applications.</p>
