Package Installer Has Stopped During Installation

When installing the Binance APK, the process might get interrupted halfway with a "Package installer has stopped" pop-up. This is a crash of the Android system component PackageInstaller itself, and is unrelated to the APK file. This guide outlines the troubleshooting process. To download the APK, go to the Binance official website or the Binance official app; for iPhone installation, check the iOS installation tutorial.

What is PackageInstaller?

PackageInstaller is the built-in APK installation component of the Android system:

• It is responsible for popping up the installation confirmation window.
• It parses the APK's meta-information.
• It calls PackageManagerService to complete the installation.
• It displays the "Installing..." and "App installed" dialog boxes.

It is a system-level app itself (package name com.android.packageinstaller), with its own process and memory space.

Common Causes of Crashes

Cause 1 · Out of Memory When PackageInstaller parses an APK, it needs to load the APK's meta-information into memory. If the device's memory is tight:

• Parsing fails, causing the process to crash.
• It pops up "Has stopped running."

Cause 2 · Corrupted Cache The cache directory of PackageInstaller itself (/data/data/com.android.packageinstaller) is corrupted:

• Database anomalies.
• Temporary files are full.

Cause 3 · Permission Errors Some ROM's permission management makes abnormal adjustments to PackageInstaller:

• PackageInstaller's permissions are restricted.
• It lacks the INSTALL_PACKAGES permission during installation.

Cause 4 · APK Anomalies Causing Crashes Very rarely, the manifest inside the APK is written non-standardly, causing the parser to crash.

Troubleshooting Step 1: Restart Your Phone

The simplest method. Restarting the phone immediately after a crash can solve 80% of problems:

• Frees up memory.
• Resets the PackageInstaller state.
• Clears temporary files.

Try installing the Binance APK again after the restart.

Troubleshooting Step 2: Clear PackageInstaller Cache

If restarting doesn't fix it:

1. Go to Settings → Apps → App Management.
2. Tap the three dots at the top → "Show system apps".
3. Find "Package installer" or "PackageInstaller".
4. Go to "Storage" → "Clear cache".

On some ROMs, you might also need to tap "Clear data" (this is more thorough but will reset PackageInstaller preferences).

Troubleshooting Step 3: Cancel Other Installation Queues

PackageInstaller can only handle one installation request at a time. If you just installed another APK or an app is currently updating, a new request might cause PackageInstaller to crash:

• Wait a few minutes for the Play Store to finish all updates.
• Check the notification bar for any "Installing" messages.
• Install Binance only after everything else is completed.

Troubleshooting Step 4: Open APK with a Different File Manager

Some third-party file managers (like older versions of ES File Explorer) call PackageInstaller in non-standard ways, which can cause crashes. Change your tool:

• Use the system's built-in "Files" app.
• Or use Solid Explorer.
• Do not use ad-supported domestic file managers.

Troubleshooting Step 5: Install via ADB

If PackageInstaller consistently crashes, you can use ADB:

• Install ADB on your computer.
• Connect your phone to the computer and enable USB debugging.
• Use the command line: adb install Binance.apk

ADB installation bypasses the graphical interface of PackageInstaller and calls the underlying PackageManagerService directly.

ROM-Specific Issues

On some ROMs, PackageInstaller behaves abnormally:

ROM	Known Issue
Early MIUI 14	Occasional "Not responding"
HarmonyOS 4	Pure Mode interception displays as "Stopped running"
ColorOS 13	App security check crashes

Upgrading to the latest minor version of the ROM usually fixes these.

Memory Optimization

To reduce the probability of PackageInstaller crashing:

• Devices with tight memory should close background apps before installing.
• Devices with 8 GB of RAM or more rarely encounter this.
• Devices with 4 GB of RAM have a higher chance of crashing when installing large APKs.

At 96 MB, the Binance APK is relatively large and is particularly prone to triggering memory issues on lower-end devices.

Difference Between Error and "Not Responding"

There are two manifestations when PackageInstaller runs into issues:

• "Package installer has stopped": The process crashed, and the installation is interrupted.
• "Package installer isn't responding": The process is frozen, and you can choose to "Wait" or "Close app".

For the latter, occasionally waiting 1-2 minutes will lead to a natural recovery.

ROM Installation Monitoring

Some ROMs enable an "Installation Monitoring" service that collaborates with PackageInstaller:

• It uploads the APK hash to the cloud during installation.
• It waits for the cloud to respond (if the network is slow, the wait is long).
• If it gets too slow, PackageInstaller times out and crashes.

Solution: Install in Airplane Mode (disconnect from the cloud) or turn off the app security check.

Long-Term Suggestions

To reduce PackageInstaller issues:

• Keep your system up to date.
• Do not install third-party PackageInstaller replacements.
• Leave ample memory and storage space.
• Restart your phone before installing large APKs.

FAQ

Q: Can I change to a different PackageInstaller? A: Theoretically, you can install a third-party installer, but it requires root and is not recommended for ordinary users.

Q: Will a PackageInstaller crash corrupt my data? A: No. A failed installation will not destroy existing data.

Q: Can I install an APK without PackageInstaller? A: You can use ADB to install, but it is necessary for daily use.

Q: Are third-party installers (like SAI) more stable? A: SAI still calls the system's PackageInstaller internally.

Extended Reading

• Parse Error
• Installation Stuck
• APK Installation Tutorial