APK Extractor extrahiert eine installierte Anwendung als APK und kopiert sie auf die SD-Karte. * Schnell und einfach zu benutzen. * Extrahiert fast alle Apps. Febr. Android-Apps könnt ihr aber auch völlig unabhängig von der zentralen APK- Dateien installieren: Hier könnt ihr Apps bedenkenlos. Juli Wir zeigen Ihnen, wie der Download der APK-Datei funktioniert und wie Sie die App auf Ihrem Android-Handy installieren. Das ist ganz einfach.
Apps downloaded from Google Play are automatically installed on your device, while those downloaded from other sources must be installed manually.
Typically, users never see APK files because Android handles app installation in the background via Google Play or another app distribution platform.
However, there are many websites that offer direct APK file download for Android users who want to install apps manually themselves. In this case, you should be careful that you trust the source of the APK file, because malware can be distributed in APK files, just as it can in the case of Windows and.
You can install APK files manually by following these instructions. Make sure that you trust the source of the APK file.
Android packages contain all the necessary files for a single Android program. Below is a list describing the most prominent files and folders: To receive updates regarding the download progress and to interact with the DownloaderService , you must implement the Downloader Library's IDownloaderClient interface.
Usually, the activity you use to start the download should implement this interface in order to display the download progress and send requests to the service.
With the IDownloaderService object initialized, you can send commands to the downloader service, such as to pause and resume the download requestPauseDownload and requestContinueDownload.
To provide a useful message to your users, you can request a corresponding string for each state by calling Helpers.
This returns the resource ID for one of the strings bundled with the Downloader Library. For examples of these callbacks that update the download progress UI, see the SampleDownloaderActivity in the sample app provided with the Apk Expansion package.
If you do use the Downloader Library as discussed in the previous section, the library performs all interaction with the APKExpansionPolicy so you don't have to use this class directly.
The class includes methods to help you get the necessary information about the available expansion files:. For more information about how to use the APKExpansionPolicy when you're not using the Downloader Library , see the documentation for Adding Licensing to Your App , which explains how to implement a license policy such as this one.
Once your APK expansion files are saved on the device, how you read your files depends on the type of file you've used. Regardless of how you read your files, you should always first check that the external storage is available for reading.
There's a chance that the user has the storage mounted to a computer over USB or has actually removed the SD card.
When your application starts, you should always check whether the external storage space is available and readable by calling getExternalStorageState.
This returns one of several possible strings that represent the state of the external storage. As described in the overview , your APK expansion files are saved using a specific file name format:.
To get the location and names of your expansion files, you should use the getExternalStorageDirectory and getPackageName methods to construct the path to your files.
Here's a method you can use in your application to get an array containing the complete path to both your expansion files:.
You can call this method by passing it your application Context and the desired expansion file's version. There are many ways you could determine the expansion file version number.
One simple way is to save the version in a SharedPreferences file when the download begins, by querying the expansion file name with the APKExpansionPolicy class's getExpansionFileName int index method.
You can then get the version code by reading the SharedPreferences file when you want to access the expansion file. For more information about reading from the shared storage, see the Data Storage documentation.
This is an optional library that helps you read your expansion files when they're saved as ZIP files. Using this library allows you to easily read resources from your ZIP expansion files as a virtual file system.
If you're using your expansion files to store media files, a ZIP file still allows you to use Android media playback calls that provide offset and length controls such as MediaPlayer.
For example, when using the zip tool, you should use the -n option to specify the file suffixes that should not be compressed:.
The above code provides access to any file that exists in either your main expansion file or patch expansion file, by reading from a merged map of all the files from both files.
Context and the version number for both the main expansion file and patch expansion file. If you'd rather read from a specific expansion file, you can use the ZipResourceFile constructor with the path to the desired expansion file:.
For more information about using this library for your expansion files, look at the sample application's SampleDownloaderActivity class, which includes additional code to verify the downloaded files using CRC.
Beware that if you use this sample as the basis for your own implementation, it requires that you declare the byte size of your expansion files in the xAPKS array.
Before publishing your application, there are two things you should test: Reading the expansion files and downloading the files.
Before you upload your application to Google Play, you should test your application's ability to read the files from the shared storage.
All you need to do is add the files to the appropriate location on the device shared storage and launch your application:. For example, if your package name is com.
Plug in your test device to your computer to mount the shared storage and manually create this directory. For example, regardless of the file type, the main expansion file for the com.
The version code can be whatever value you want. Because your application must sometimes manually download the expansion files when it first opens, it's important that you test this process to be sure your application can successfully query for the URLs, download the files, and save them to the device.
To test your application's implementation of the manual download procedure, you can publish it to the alpha or beta channel, so it will only be available to authorized testers.
If everything works as expected, your application should begin downloading the expansion files as soon as the main activity starts. Previously you could test an app by uploading an unpublished "draft" version.
This functionality is no longer supported; instead, you must publish it to the alpha or beta distribution channel. Updating Your Application One of the great benefits to using expansion files on Google Play is the ability to update your application without re-downloading all of the original assets.
Because Google Play allows you to provide two expansion files with each APK, you can use the second file as a "patch" that provides updates and new assets.
Doing so avoids the need to re-download the main expansion file which could be large and expensive for users. The patch expansion file is technically the same as the main expansion file and neither the Android system nor Google Play perform actual patching between your main and patch expansion files.
Your application code must perform any necessary patches itself. Even if you only need to make changes to the patch expansion file, you must still update the APK in order for Google Play to perform an update.
If you don't require code changes in the application, you should simply update the versionCode in the manifest. See also [ edit ] Computing portal.
How to install apk files on Android Emulator". Archived from the original on OPhone Software Developer Network. Archived from the original on 8 February General Structure of an APK".
Archived from the original on 17 July Retrieved 16 June Retrieved from " https: