Lines Matching full:application
10 <li>You can allow your application to install on the device's external storage.</li>
33 <p>Beginning with API Level 8, you can allow your application to be installed on the
35 for your application with the <a
38 <em>not</em> declare this attribute, your application will be installed on the internal storage
41 <p>To allow the system to install your application on the external storage, modify your
54 <p>If you declare "{@code preferExternal}", you request that your application be installed on the
55 external storage, but the system does not guarantee that your application will be installed on
57 storage. The user can also move your application between the two locations.</p>
59 <p>If you declare "{@code auto}", you indicate that your application may be installed on the
61 decide where to install your application based on several factors. The user can also move your
62 application between the two locations.</p>
64 <p>When your application is installed on the external storage:</p>
66 <li>There is no effect on the application performance so long
71 <li>The unique container in which your application is stored is encrypted with a randomly
73 application installed on an SD card works for only one device.</li>
74 <li>The user can move your application to the internal storage through the system settings.</li>
85 <p>The ability for your application to install on the external storage is a feature available only
88 storage (even on devices with API Level 8). However, if your application is designed to support an
100 than</em> "8") and be certain that your application code uses only APIs compatible with that
102 <li>In order to compile your application, change your build target to API Level 8. This is
104 attribute and will not compile your application when it's present.</li>
107 <p>When your application is installed on a device with an API Level lower than 8, the {@code
108 android:installLocation} attribute is ignored and the application is installed on the internal
115 backward compatibility in your application code, see the <a
124 unmounts or removes the external storage), any application
126 unaware of the application until mass storage is disabled and the external storage is
127 remounted on the device. Besides killing the application and making it unavailable to the user,
128 this can break some types of applications in a more serious way. In order for your application to
129 consistently behave as expected, you <strong>should not</strong> allow your application to be
138 your application when applications installed on external storage have become available to the
158 available for the user to select until the system resets the home application (usually not until a
172 before the external storage is mounted to the device. If your application is installed on the
175 <dd>Your application cannot be installed to a device's SD card if it uses Google Play's
177 <a href="{@docRoot}guide/google/play/licensing.html">Application Licensing</a> instead, your
178 application <em>can</em> be installed to internal or external storage, including SD cards.</dd>
181 <p>If your application uses any of the features listed above, you <strong>should not</strong> allow
182 your application to install on external storage. By default, the system <em>will not</em> allow your
183 application to install on the external storage, so you don't need to worry about your existing
184 applications. However, if you're certain that your application should never be installed on the
188 change the default behavior, it explicitly states that your application should only be installed
203 <p>If your application requires several megabytes for the APK file, you should
204 carefully consider whether to enable the application to install on the external storage so that
