Download and install checks

Separate Android storage problems from install permission

A download that stops, a file that will not open and a blocked installation are different failures. Identify the stage first, then change only the setting connected to it.

Keep security controls on: unknown-app permission does not prove a file is safe. Keep Play Protect enabled and stop when the destination or warning is unexpected.

Match the symptom before opening Settings

Download never begins

Check the page connection and browser download permission. Tap once and wait; repeated taps can create duplicate or partial files.

Download stops part-way

Review free space and network stability, then remove only incomplete copies. Do not rename a temporary file to make it look complete.

Finished file will not open

Open the completed item from the browser download list or the expected file manager. Confirm which app is handling the request.

Install permission is blocked

Android grants this permission per source. The browser may be allowed while the file manager remains blocked, or the reverse.

Android reports low storage

Free space must cover temporary installation work and the installed app, not only the compressed download shown in the file list.

App not installed still appears

If storage and permission are sufficient, check for an existing-app, signing, version or profile conflict instead.

Open the package-conflict guide →

Allow only the app opening the expected file

  1. Identify the source app

    Note whether the package is being opened by the browser, Downloads app or file manager. Do not guess.

  2. Open the specific Android setting

    Look for Apps, Special app access and Install unknown apps. Names and paths differ by Android version and phone brand.

  3. Limit the temporary change

    Allow only the identified source app. Do not enable messaging, remote-control or unrelated apps.

  4. Make one controlled attempt

    Return to the completed file and read every Android warning. Stop if the file or requested action differs from what you expected.

  5. Restore the setting

    Disable the per-source permission again after the intended attempt, whether installation succeeded or failed.

Create working space without deleting evidence

  • Compare available device storage with the downloaded file size.
  • Remove duplicate partial downloads, not the one complete file you are diagnosing.
  • Clear ordinary cache before deleting app data, saved files or account records.
  • Restart once after freeing space so Android can refresh its storage state.
  • If the same message remains, record it and move to the package-conflict check.

Retry once, then keep the evidence

A repeated failure after storage and permission checks needs diagnosis, not more random changes. Preserve the exact message and the stage where it occurs.

Storage and permission questions

Which app needs unknown-app installation permission?

Only the browser or file manager that is opening the expected package may need the per-source permission. Android settings vary by device, and unrelated apps should not be enabled.

Why does installation need more space than the downloaded file?

Android needs temporary working space to verify and install a package, and the installed app may use more space than the compressed download. Free space should therefore exceed the visible file size.

Reviewed 10 August 2026. This independent page explains general Android storage and per-source install-permission checks and links to Google Play Protect guidance.