| /frameworks/base/core/java/com/android/internal/util/ |
| D | MimeIconUtils.java | 42 add("application/vnd.android.package-archive", icon);
46 add("application/ogg", icon);
47 add("application/x-flac", icon);
51 add("application/pgp-keys", icon);
52 add("application/pgp-signature", icon);
53 add("application/x-pkcs12", icon);
54 add("application/x-pkcs7-certreqresp", icon);
55 add("application/x-pkcs7-crl", icon);
56 add("application/x-x509-ca-cert", icon);
57 add("application/x-x509-user-cert", icon);
[all …]
|
| /frameworks/opt/telephony/src/java/com/google/android/mms/pdu/ |
| D | PduContentTypes.java | 42 "application/*", /* 0x10 */
43 "application/java-vm", /* 0x11 */
44 "application/x-www-form-urlencoded", /* 0x12 */
45 "application/x-hdmlc", /* 0x13 */
46 "application/vnd.wap.wmlc", /* 0x14 */
47 "application/vnd.wap.wmlscriptc", /* 0x15 */
48 "application/vnd.wap.wta-eventc", /* 0x16 */
49 "application/vnd.wap.uaprof", /* 0x17 */
50 "application/vnd.wap.wtls-ca-certificate", /* 0x18 */
51 "application/vnd.wap.wtls-user-certificate", /* 0x19 */
[all …]
|
| /frameworks/base/docs/html/google/play/licensing/ |
| D | overview.jd | 2 parent.title=Application Licensing
29 <p>Google Play Licensing is a network-based service that lets an application query a trusted
30 Google Play licensing server to determine whether the application is licensed to the current
32 to determine whether a given user is licensed to use a given application. Google Play considers a
33 user to be licensed if the user is a recorded purchaser of the application.</p>
35 <p>The request starts when your application makes a request to a service hosted by
36 the Google Play client application. The Google Play application then sends a request to
37 the licensing server and receives the result. The Google Play application sends
38 the result to your application, which can allow or disallow further use of the
39 application as needed.</p>
[all …]
|
| D | index.jd | 9 applications that you publish on Google Play. With Google Play Licensing, your application can
13 <p>Using the service, you can apply a flexible licensing policy on an application-by-application
14 basis—each application can enforce licensing in the way most appropriate for it. If necessary,
15 an application can apply custom constraints based on the licensing status obtained from Google Play.
16 For example, an application can check the licensing status and then apply custom constraints
17 that allow the user to run it unlicensed for a specific validity period. An application can also
18 restrict use of the application to a specific device, in addition to any other constraints. </p>
21 application checks the licensing status, the Google Play server signs the licensing status
22 response using a key pair that is uniquely associated with the application. Your application
26 <p>Any application that you publish through Google Play can use the Google Play Licensing
[all …]
|
| D | adding-licensing.jd | 2 parent.title=Application Licensing
42 <li><a href="#app-publishing">Publishing a Licensed Application</a></li>
58 <li><a href="#manifest-permission">Adding the licensing permission</a> your application's manifest.…
62 <li><a href="#impl-lc">Adding code to check the license</a> in your application's main
69 integration, you should be able to compile your application successfully and you
81 <p>To use the Google Play application for sending a license check to the
82 server, your application must request the proper permission,
83 <code>com.android.vending.CHECK_LICENSE</code>. If your application does
87 <p>To request the licensing permission in your application, declare a <a
94 <p>For example, here's how the LVL sample application declares the permission:
[all …]
|
| D | licensing-reference.jd | 2 parent.title=Application Licensing
54 access to the application, based on the license response. </td>
86 application to a specific device. Called from LicenseValidator. Implementing
124 <td>One-way IPC callback implementation over which the application receives an
135 licensing server. In general, an application should handle all of these response
153 <td>The application is licensed to the user. The user has purchased the
154 application, or is authorized to download and install the alpha or beta version
155 of the application.</td>
162 <td>The application is licensed to the user, but there is an updated application
168 application version is invalid or compromised. The application can allow access
[all …]
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| D | WspTypeDecoder.java | 60 WELL_KNOWN_MIME_TYPES.put(0x10, "application/*");
61 WELL_KNOWN_MIME_TYPES.put(0x11, "application/java-vm");
62 WELL_KNOWN_MIME_TYPES.put(0x12, "application/x-www-form-urlencoded");
63 WELL_KNOWN_MIME_TYPES.put(0x13, "application/x-hdmlc");
64 WELL_KNOWN_MIME_TYPES.put(0x14, "application/vnd.wap.wmlc");
65 WELL_KNOWN_MIME_TYPES.put(0x15, "application/vnd.wap.wmlscriptc");
66 WELL_KNOWN_MIME_TYPES.put(0x16, "application/vnd.wap.wta-eventc");
67 WELL_KNOWN_MIME_TYPES.put(0x17, "application/vnd.wap.uaprof");
68 WELL_KNOWN_MIME_TYPES.put(0x18, "application/vnd.wap.wtls-ca-certificate");
69 WELL_KNOWN_MIME_TYPES.put(0x19, "application/vnd.wap.wtls-user-certificate");
[all …]
|
| /frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/ |
| D | Wap230WspContentTypeTest.java | 54 WELL_KNOWN_SHORT_MIME_TYPES.put(0x10, "application/*");
55 WELL_KNOWN_SHORT_MIME_TYPES.put(0x11, "application/java-vm");
56 WELL_KNOWN_SHORT_MIME_TYPES.put(0x12, "application/x-www-form-urlencoded");
57 WELL_KNOWN_SHORT_MIME_TYPES.put(0x13, "application/x-hdmlc");
58 WELL_KNOWN_SHORT_MIME_TYPES.put(0x14, "application/vnd.wap.wmlc");
59 WELL_KNOWN_SHORT_MIME_TYPES.put(0x15, "application/vnd.wap.wmlscriptc");
60 WELL_KNOWN_SHORT_MIME_TYPES.put(0x16, "application/vnd.wap.wta-eventc");
61 WELL_KNOWN_SHORT_MIME_TYPES.put(0x17, "application/vnd.wap.uaprof");
62 WELL_KNOWN_SHORT_MIME_TYPES.put(0x18, "application/vnd.wap.wtls-ca-certificate");
63 WELL_KNOWN_SHORT_MIME_TYPES.put(0x19, "application/vnd.wap.wtls-user-certificate");
[all …]
|
| /frameworks/base/docs/html/guide/topics/data/ |
| D | install-location.jd | 11 <li>You can allow your application to install on the device's external storage.</li>
34 <p>Beginning with API Level 8, you can allow your application to be installed on the
36 for your application with the <a
39 <em>not</em> declare this attribute, your application will be installed on the internal storage
42 <p>To allow the system to install your application on the external storage, modify your
55 <p>If you declare "{@code preferExternal}", you request that your application be installed on the
56 external storage, but the system does not guarantee that your application will be installed on
58 storage. The user can also move your application between the two locations.</p>
60 <p>If you declare "{@code auto}", you indicate that your application may be installed on the
62 decide where to install your application based on several factors. The user can also move your
[all …]
|
| /frameworks/base/docs/html/guide/practices/ |
| D | screens-support-1.5.jd | 16 an application designed for Android 1.5</li>
47 default, an application written for Android 1.5 or below that does not set the <a
52 <em>normal</em> screen size (basically, the system displays the application in a small window
55 <p>This document describes how to get your application out of <a
71 <p>If you have already developed and published an Android application based on
73 need to make some changes to your application in order for it to properly run on newer devices with
74 different screen configurations. You should be able to make these changes to your application such
77 <p>The recommended strategy is to develop your application against Android 1.6 (because it's the
78 lowest version that includes support for multiple screens) and test your application on each
79 platform version your application supports (especially the minimum platform, such as Android 1.5).
[all …]
|
| D | optimizing-for-3.0.jd | 65 you to enhance your user's experience on tablets and similar devices. Any application you've already
69 your application looks and works great on the new platform and new device form-factors.</p>
71 <p>This document shows how you can optimize your existing application for Android 3.0 and
72 maintain compatibility with older versions or upgrade your application completely with new APIs.</p>
83 <p>Read this section if you have an existing application and want to
85 manifest file to declare support for Android 3.0, test your application on the new platform, and
89 <p>Read this section if you want to upgrade your application to use APIs introduced in
90 Android 3.0 or create a new application targeted to tablets and similar devices. Compared to
93 application that's fully enhanced for tablets.</p></li>
97 application based on screen configuration</a>.</li>
[all …]
|
| D | seamlessness.jd | 25 <p>Even if your application is fast and responsive, certain design decisions can
30 application. In short, you should strive to develop an application that
33 <p>A common seamlessness problem is when an application's background process
36 you are building and testing your application in isolation, on the emulator.
37 However, when your application is run on an actual device, your application may
39 it could end up that your application would display it's dialog behind the
40 active application, or it could take focus from the current application and
42 phone call, for example). That behavior would not work for your application or
45 <p>To avoid these problems, your application should use the proper system
48 notifications, your application can signal the user that an event has
[all …]
|
| D | screens-distribution.jd | 13 <li>If necessary, you can control distribution of your application based on the device
35 <p>Although we recommend that you design your application to function properly on multiple
37 application to certain types of screens, such as only tablets and other large devices or only
40 application supports.</p>
42 <p>However, before you decide to restrict your application to certain screen configurations, you
45 them to the best of your ability. By supporting multiple screens, your application can be made
53 need to filter your application from larger screens. As long as you follow the <a
55 Independence</a>, your application should work well on larger screens such as tablets. However, you
56 might discover that your application can't scale up well or perhaps you've decided to publish two
57 versions of your application for different screen configurations. In such a case, you can use the <a
[all …]
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | receiver-element.jd | 19 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a…
27 subclass) as one of the application's components. Broadcast receivers enable
29 applications, even when other components of the application are not running.
48 The <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a…
49 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#enabled">enabled</a></code>…
50 application components, including broadcast receivers. The
51 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></c…
59 outside its application — "{@code true}" if it can, and "{@code false}"
61 receive are those sent by components of the same application or applications
68 application-internal use (since others would not normally know the class name).
[all …]
|
| D | supports-screens-element.jd | 27 <dd itemprop="description">Lets you specify the screen sizes your application supports and enable <a
29 larger than what your application supports. It's important that you always use this element in your
30 application to specify the screen sizes your application supports.
32 <p>An application "supports" a given screen size if it resizes properly to fill the entire screen.
34 extra work to make your application work on screens larger than a handset device. However, it's
35 often important that you optimize your application's UI for different screen sizes by providing <a
40 <p>However, if your application does not work well when resized to fit different screen sizes, you
42 application should be distributed to smaller screens or have its UI scaled up ("zoomed") to fit
53 android:largestWidthLimitDp}. If you're developing your application for Android 3.2 and higher,
58 using screen compatibility mode with your application, read
[all …]
|
| D | service-element.jd | 20 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a…
28 of the application's components. Unlike activities, services lack a
47 The <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a…
48 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#enabled">enabled</a></code>…
49 application components, including services. The
50 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></c…
60 components of the same application or applications
67 application-internal use (since others would not know the class name). So in
83 If it is not set, the icon specified for the application
84 …(see the <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application&…
[all …]
|
| D | uses-sdk-element.jd | 15 <li><a href="#fc">Application forward compatibility</a></li>
16 <li><a href="#bc">Application backward compatibility</a></li>
50 <dd itemprop="description"><p> Lets you express an application's compatibility with one or more ve…
51 by means of an API Level integer. The API Level expressed by an application will be compared to the
71 for the application to run. The Android system will prevent the user from installing
72 the application if the system's API Level is lower than the value specified in
77 application is compatible with all versions of Android. If your application is
80 then when installed on a system with an API Level less than 3, the application
87 <dd>An integer designating the API Level that the application targets. If not set, the default
92 with the target version. The application is still able to run on older versions (down to {@code
[all …]
|
| D | manifest-element.jd | 25 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a…
44 contain an <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application…
55 <dd>A full Java-language-style package name for the Android application. The
66 The package name serves as a unique identifier for the application.
67 It's also the default name for the application process (see the
68 …<code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></…
70 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#aff">process</a></code>
78 <p class="caution"><strong>Caution:</strong> Once you publish your application, you
79 <strong>cannot change the package name</strong>. The package name defines your application's
80 identity, so if you change it, then it is considered to be a different application and users of
[all …]
|
| D | supports-gl-texture-element.jd | 38 the application.
40 <p>An application "supports" a GL texture compression format if it is capable of
42 application is installed on a device. The application can provide the
48 <code>android:name</code> attribute. If your application supports multiple
58 (such as Google Play) or applications can check your application's
60 interacting with your application. For this reason, it's very important that
62 your application is capable of supporting. </p>
69 <p>Assuming that the application is built with SDK Platform Tools r3 or higher,
79 <dd>Specifies a single GL texture compression format supported by the application,
121 Bionic, and others. If your application requires a specific DXT variant, declare
[all …]
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | localization.jd | 2 parent.title=Application Resources
42 your application should handle text, audio files, numbers, currency, and
43 graphics in ways appropriate to the locales where your application will be used.
55 localized aspects of your application as much as possible from the core Java
59 <li>You can put most or all of the <em>contents</em> of your application's
79 data that your Android application needs. An application can include multiple
81 user runs the application, Android automatically selects and loads the
93 <strong>When you write your application:</strong>
102 <strong>When a user runs your application:</strong>
108 <p>When you write your application, you create default and alternative resources
[all …]
|
| /frameworks/base/docs/html/guide/practices/app-design/ |
| D | seamlessness.jd | 24 <p>Even if your application is fast and responsive, certain design decisions can
29 application. In short, you should strive to develop an application that
32 <p>A common seamlessness problem is when an application's background process
35 you are building and testing your application in isolation, on the emulator.
36 However, when your application is run on an actual device, your application may
38 it could end up that your application would display it's dialog behind the
39 active application, or it could take focus from the current application and
41 phone call, for example). That behavior would not work for your application or
44 <p>To avoid these problems, your application should use the proper system
47 notifications, your application can signal the user that an event has
[all …]
|
| /frameworks/base/test-runner/src/android/test/ |
| D | ApplicationTestCase.java | 19 import android.app.Application;
24 * This test case provides a framework in which you can test Application classes in
26 * Application, and hooks by which you can inject various dependencies and control
27 * the environment in which your Application is tested.
30 * Every Application is designed to be accessed within a specific sequence of
31 * method calls (see {@link android.app.Application} for more details).
32 * In order to support the lifecycle of a Application, this test case will make the
40 * automatically called, and it will stop & destroy your application by calling its
45 * Every Application has one inherent dependency, the {@link android.content.Context Context} in
50 * <p>If simply run your tests as-is, your Application will be injected with a fully-functional
[all …]
|
| /frameworks/base/core/java/android/content/pm/ |
| D | ApplicationInfo.java | 40 * Information you can retrieve about a particular application. This
42 * <application> tag.
47 * Default task affinity of all activities in this application. See
55 * application's components. From the "permission" attribute.
60 * The name of the process this application should run in. From the
67 * Class implementing the Application object. From the "class"
74 * description of an application. From the "description" attribute
81 * default visual theme of the application. From the "theme" attribute
87 * Class implementing the Application's manage space
95 * Class implementing the Application's backup functionality. From
[all …]
|
| /frameworks/base/docs/html/training/in-app-billing/ |
| D | test-iab-app.jd | 1 page.title=Testing Your In-app Billing Application
28 …t In-app Billing is functioning correctly in your application, you should test the test the applic…
31 Test your In-app Billing application with static responses by using Google Play’s reserved product …
35 <p>To test your In-app Billing Version 3 application using your own product IDs:
37 …ne or more tester accounts to the developer account that you are using to publish your application.
42 …application. To learn how to build and sign your APK, see <a href="{@docRoot}tools/publishing/prep…
44 …application to the Developer Console, and associated one or more in-app products with your applica…
45 …test device by using the {@code adb} tool. To learn how to install the application, see <a href="{…
48 …rsionName} attributes values in the {@code AndroidManifest.xml} of the application that you are in…
49 …<li>Your application is signed with the same certificate that you used for the APK that you upload…
[all …]
|
| /frameworks/base/docs/html/guide/appendix/ |
| D | glossary.jd | 7 <dt id="apk">.apk file</dt> <dd>Android application package file. Each
8 Android application is compiled and packaged in a single file that
9 includes all of the application's code (.dex files), resources, assets,
10 and manifest file. The application package file can have any name but
12 <code>myExampleAppname.apk</code>. For convenience, an application package
14 <p>Related: <a href="#application">Application</a>.</p>
18 <dd>Compiled Android application code file.
28 for a Web URL, or com.example.rumbler.SHAKE_PHONE for a custom application
34 <dd>A single screen in an application, with supporting Java code, derived
42 <dd>Android Debug Bridge, a command-line debugging application included with the
[all …]
|