DiPlayVIP

LOCAL FILE CHECK · FREE

APK requirements checker.
Before you install.

Read what your APK declares, then compare it with your head unit’s actual Android system.

01

Choose an APK

02

Compare your head unit

Optional. Use the Android version and supported ABIs reported by the head unit’s system, not the chip’s marketing name.

Supported system ABIs

Select every ABI your system supports. Leave blank if unknown.

How do I find these values?

Check Android system information. With existing authorized ADB access, adb shell getprop ro.build.version.sdk reads the API level and adb shell getprop ro.product.cpu.abilist reads supported ABIs. On older systems also check ro.product.cpu.abi and ro.product.cpu.abi2. Do not enable extra permissions just to use this tool.

File names, package metadata and selected system values are never sent to analytics.

03

Your results

Your APK tells the story.

Choose a file and select Inspect APK to see its declared requirements here.

This checks declared installation requirements. It does not verify the APK signature, scan for malware, or guarantee CarPlay, audio or vehicle compatibility.

What the check can tell you

Minimum Android API

minSdkVersion is the minimum OS API declared by the package. Android 7.0 is API 24; Android 7.1 is API 25. targetSdkVersion is a behavior target, not the minimum installation version.

Packaged native architectures

The tool lists native libraries under lib/<ABI>/*.so. The head unit’s OS must support a matching ABI. A 64-bit processor may still run a 32-bit Android system.

Missing or incomplete evidence

No native libraries does not prove universal support. Split packages need companion APKs. ZIP64, encrypted archives, app bundles and unresolved resource values are reported as unsupported or unknown.

Downloads on the Official Website Android requirements guide Installation guide

References: Android SDK requirements · Android native ABIs

APK requirements: common questions

How do I check an APK’s minimum Android version?

Choose a single .apk file and select Inspect APK. The checker reads minSdkVersion from the compiled Android manifest and reports its API level. For example, Android 7.1 is API 25. Compare this minimum with the API level reported by your head unit’s Android system.

Can a 64-bit head unit install every arm64-v8a APK?

No. A 64-bit processor may run a 32-bit Android system. Compare the APK’s packaged native ABIs with the ABIs supported by the operating system. A missing native-library entry or an unknown system ABI does not prove compatibility.

Does a matching result guarantee the APK is safe or works with CarPlay?

No. A match covers the declared requirements inspected by this tool. It does not verify the signature, scan for malware or test CarPlay. Split APKs also need companion packages. Use the Official Website’s download and installation guides before proceeding.

Calculate screen dimensions and scaling