Lines Matching full:application
74 available to your application, based on the <code>android:minSdkVersion</code>
75 value the application declares in its manifest. For more information, see
85 <p>If you've been developing an application using an Android 1.1 SDK, you need
88 code of an existing application should be needed, provided that your application
91 <p>To ensure that your existing application will work properly on a device
93 to migrate the application to the new SDK, compile it using the platform
94 matching the application's original API Level, and run it against the most
103 lets you create a test package containing tests for your application. These
146 application packages whose contained uncompressed files are all aligned on
149 the amount of memory used by the application at run time. The SDK includes
154 aligning your application packages. After you build an .apk, the SDK tools can
162 Wizard to export a signed application package, ADT signs and then automatically
164 to export an unsigned application package, then it will not zipalign the
169 application package, provided that you have specified the location of a valid
178 <p>In general, note that you must <code>zipalign</code> an application only
186 creating or importing a new Android application project. </p>
190 <p>If you are using Windows and want to develop or test your application on an
244 fixes, as described below, and a new application — an IME for Japanese
255 enforcement, you are strongly encouraged to test your application
259 <p>In particular, if your application uses any of the system areas listed below,
260 you should add the required permissions to the application's manifest and then
262 Even if you believe your application does not use the permissions-protected
263 services, you should compile and test your application under the latest platform
265 application. </p>
270 <li>When an application requests access to device camera (through
273 <li>When an application requests access to device audio capture (through
306 <li>When you use adb to uninstall an upgraded application, the Android system
308 previous (downgrade) version of the application</li>
331 Android 1.5). The tools are updated to let you deploy your application
345 and export and sign your application for publishing.</li>
360 <p>If you've been developing an application using an Android 1.1 SDK, you need
363 code of an existing application should be needed, provided that your application
366 <p>To ensure that your existing application will work properly on a device
368 to migrate the application to the new SDK, compile it using the platform
369 matching the application's original API Level, and run it against the most
389 Google APIs add-on gives your application access to the com.google.android.maps
397 <p>The SDK now gives you the capability to compile an application against any
402 <li>Targets that are SDK add-ons, which typically provide application access to
436 <p>If you are using Windows and want to develop or test your application on an
467 <li>If your application uses the Sensor API and you are running it in the
469 application may generate ANR messages or crash when using the sensors. The
499 <p>If you are using this SDK to build an application that is compatible
502 <code>android:minSdkVersion</code> attribute in the application's manifest to
518 users will only be able to install your application if their devices are running
519 the Android 1.1 platform. In turn, this ensures that your application will
523 <p>If your application uses APIs introduced in Android 1.1 but does not declare
527 <p>If your application does not use any new APIs introduced in Android 1.1, you
529 setting the attribute to "1". However, before publishing your application, you
530 must make sure to compile your application against the Android 1.0 system image
532 properly for Android 1.0 devices. You should test the application against system
533 images corresponding to the API Levels that the application is designed to be
536 <p>If you are sure your application is not using Android 1.1 APIs and has no
553 <p>If you've been developing an application using an Android 1.0 SDK no
554 changes to your application are needed. You may want to wipe application
556 application on the Android 1.1 emulator for the first time.</p>
563 easily integrate Google Maps into your application. Before you can
576 <p>If you using Windows and want to develop or test your application on an
641 <p>This SDK release includes the Android 1.0 platform and application API.
667 application. Before you can access the maps data, you will need to register with
678 <p>If you using Windows and want to develop or test your application on an
728 <p>This SDK release is the first to include the Android 1.0 platform and application API. Applications developed on this SDK will be compatible with mobile devices running the Android 1.0 platform, when such devices are available.</p>
738 <p>If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Be sure to wipe application user data (emulator option <code>-wipe-data</code>) when running your application on the Android 1.0 SDK emulator.</p>
744 <p>MapView is a class that lets you easily integrate Google Maps into your application. Before you can access the maps data, you will need to register with the Google Maps service and receive a Maps API Key, which you then add to your MapView for authentication to the server.</p>
746 <p>Currently, the registration service for MapView is not yet active and Google Maps is not yet enforcing the Maps API Key requirement. However, note that the registration service will be activated soon, so that MapViews in any application deployed to a mobile device will require registration and a valid Maps API Key. </p>
