APK Downloader
·5 min read

If this contains more than one APK, it is a split package

The APK downloads fine, installs on your friend's phone, and refuses on yours. Compatibility on Android is decided by three independent checks that have nothing to do with each other — the API level, the CPU architecture, and the screen density — plus one packaging decision that silently breaks installs on some devices. Here is how to read all four in about a minute, with the exact commands.

androidapkhowtomobile

An APK that installs on one Android phone and not another is not a mystery. Compatibility is decided by a small number of independent conditions, each with its own failure signal, and each checkable with one command.

The reason people get stuck is that they treat "incompatible" as a single diagnosis. It is four, and they are evaluated in order.

The four conditions

ConditionWhat it meansFails as
minSdkVersionThe oldest Android the build supportsINSTALL_FAILED_OLDER_SDK
ABIThe CPU instruction set the native code targetsINSTALL_FAILED_NO_MATCHING_ABIS
targetSdkVersionBehavior contract with the current AndroidInstalls, then misbehaves
Split APKsThe app ships as base + config APKsINSTALL_FAILED_INVALID_APK / missing resources

Two are hard blocks. Two are soft failures that only show up after installation, which is why "it installed but does not work" is a distinct problem from "it will not install".

Reading the manifest

One command gives you three of the four:

aapt2 dump badging app.apk | grep -E "sdkVersion|targetSdkVersion|native-code|package:"

Typical output:

package: name='com.example.app' versionCode='4201' versionName='4.2.1'
sdkVersion:'26'
targetSdkVersion:'34'
native-code: 'arm64-v8a' 'armeabi-v7a'

minSdkVersion

sdkVersion:'26' means Android 8.0. It will not install on anything below. The mapping matters because it is the most common hard failure:

APIAndroidYear
215.0 Lollipop2014
236.0 Marshmallow2015
268.0 Oreo2017
29102019
31122021
33132022
34142023
35152024

Check your own version in Settings → About phone → Android version.

ABI

native-code: 'arm64-v8a' 'armeabi-v7a' means the package contains native libraries for both 64-bit and 32-bit ARM. This is the current standard. What you need to watch for:

  • `armeabi-v7a` only — will run on most phones, but Google Play stopped accepting such builds in 2019, so it is an old package
  • `x86` / `x86_64` only — emulator builds; will not run on a real phone
  • No `native-code` line at all — pure Java/Kotlin app, works on any architecture. Not a problem.

Your phone's architecture: adb shell getprop ro.product.cpu.abi returns arm64-v8a on essentially every phone shipped since 2016.

A 32-bit-only APK on a 64-bit-only device is a real scenario on newer phones that dropped 32-bit support. The install fails with NO_MATCHING_ABIS and there is no workaround.

targetSdkVersion

targetSdkVersion does not affect whether the install succeeds. It affects behavior after. What it controls:

  • Below 23: Android 14+ restricts installation and warns. Old permission model.
  • Below 26: no notification channels. Notifications behave inconsistently on Android 13+.
  • Below 30: scoped storage opt-out; file access may be blocked on Android 11+.
  • Below 33: no POST_NOTIFICATIONS handling; notifications may silently never appear on Android 13+.
  • Below 34: foreground service types not declared; background services may be killed on Android 14+.

This is the answer to a very common question: *"the app installed fine but notifications do not work."* Check targetSdkVersion before you check anything else.

Split APKs: the fourth condition

Modern apps frequently ship as base.apk plus configuration splits (per-ABI, per-density, per-language). You cannot install one split alone, and you cannot install them as separate files by tapping them.

Symptoms of getting this wrong:

  • INSTALL_FAILED_INVALID_APK: Missing split for ...
  • Install succeeds but the app crashes with Resources$NotFoundException
  • Only some languages or densities are missing

How to check:

# If this contains more than one APK, it is a split package
unzip -l app.apk | head

If the download was an .xapk, .apks, or a folder of split_*.apk files, install the whole set:

adb install-multiple base.apk split_config.arm64_v8a.apk split_config.xxhdpi.apk

Or use a tool that understands the format. Installing only `base.apk` from a split package is a common and confusing failure — it usually installs and then crashes on launch.

Checking the device side

# Android version and API level
adb shell getprop ro.build.version.release
adb shell getprop ro.build.version.sdk

# CPU architecture
adb shell getprop ro.product.cpu.abi
adb shell getprop ro.product.cpu.abilist

# Screen density
adb shell wm density
adb shell wm size

abilist shows every supported ABI, most preferred first. Compare it against the package's native-code line — if there is no overlap, the install is impossible.

Density: rarely blocks, often looks wrong

Density mismatch does not prevent installation when the package is a universal APK. It matters in two cases:

  1. Split APKs: a package containing only xxhdpi resources on an ldpi device renders badly, and some split designs fail to install if the device density does not match any included split.
  2. Ancient apps: pre-2012 packages with only mdpi assets look upscaled and blurry.

adb shell wm density returns something like Physical density: 440. Values map roughly:

RangeBucket
120ldpi
160mdpi
240hdpi
320xhdpi
480xxhdpi
640xxxhdpi

Diagnostic order

When an install fails, check in this order — it matches the order the system evaluates:

  1. Read the actual error code with adb install app.apk. On-device "App not installed" tells you nothing.
  2. If OLDER_SDK → minSdkVersion exceeds your Android version. Nothing to fix; get a build with a lower minSdk.
  3. If NO_MATCHING_ABIS → architecture mismatch. Look for a different build variant.
  4. If INVALID_APK or missing resources → you are installing a split package incorrectly.
  5. If UPDATE_INCOMPATIBLE → this is a signature problem, not compatibility. Different issue entirely.
  6. If it installs but crashes → check targetSdkVersion and logcat:
adb logcat -c && adb logcat | grep -E "FATAL|AndroidRuntime"

The practical summary

  • Will not install at all: minSdkVersion or ABI. Both are hard blocks with no workaround.
  • Installs but the UI is broken or missing features: split APKs installed incompletely.
  • Installs and runs but behaves wrong: targetSdkVersion — the app was written for older Android behavior.
  • Installs but crashes immediately: usually an incompletely installed split, or a missing Google services dependency on ROMs without GMS.

One habit covers most of this: before downloading, note the package name, minSdkVersion, and native-code from the listing. Sites that publish them — gptoapk.com does this per build — let you rule out two hard failures before you spend the bandwidth.