26.10.06 21:33
Why Android warns about this APK - and what to tap
FastMediaSorter is a free app from an independent developer, and the builds on the downloads page are installed directly from a file instead of from an app store. Android treats a package it has not seen before with extra caution, so you will meet one or two warnings on the way. Here is what each one says, why it appears, and exactly what to do.
What you will see
Two different screens, in this order.
“For security, your phone currently isn’t allowed to install unknown apps from this source.” This is the browser or file manager asking for a one-time permission to hand the file to the installer. It is about the app you downloaded with, not about FastMediaSorter.
“Unsafe app blocked” / “Play Protect doesn’t recognize this app’s developer” or, on some versions, “Scan app?”. This is Google Play Protect, the scanner built into Android. It reports that the package is new to it, not that it found anything in it.
Why it appears
The APK is signed with our release key - the same key as the builds on Google Play - but a key earns recognition from the number of installs Google has already seen. A build handed out directly - from a GitHub release, the Drive mirror or the IzzyOnDroid repository - does not pass through that count, so Play Protect meets a developer it cannot vouch for and says so. That is the warning working correctly, not a mistake and not something you should have been spared. All three of those channels meet it; only the Play Store edition does not.
Recognition is not the only thing the scanner weighs. Play Protect also looks at what an app is able to do, and the full edition handed out outside the store uses four capabilities that such checks watch closely, because harmful apps use them too:
- An accessibility service - it draws the edge gesture strip and takes a screenshot without the system capture dialog.
- Display over other apps - the same gesture strip and the small recording indicator, on devices where the accessibility service is not switched on.
- Install other apps - so that an
.apkfile you open in the file browser can be handed to the Android installer, which still asks you to confirm. - All files access - so that the browser can work with every folder on the device directly.
Each one is off until you switch it on in system settings for the feature behind it, and the other editions use fewer of them or none. Signing the file with a known key does not remove a flag raised by these checks, and we do not promise that any warning disappears - the page tells you what triggers it, so you can decide with the facts in front of you.
If you would rather not meet any of this, the Play Store edition is the same app without the direct downloads - it simply carries fewer features, because some of them cannot be published to a store.
What to tap
- Open the downloaded
.apkfile. When the phone says the source is not allowed to install unknown apps, tap Settings, turn on Allow from this source for that one app, and go back. - Tap Install.
- If Play Protect says it does not recognize the developer, tap More details, then Install anyway. If it offers to scan the app first, let it - the scan takes a moment and changes nothing else.
That is all. Two settings worth knowing about afterwards:
- The Allow from this source switch is per app and reversible. Turn it back off in Settings > Apps > Special app access > Install unknown apps once you are done, and Android will ask again next time.
- Play Protect stays on. Nothing on this page asks you to switch it off, to disable an antivirus, or to lower any device setting - none of that is needed to install this app, and we will never ask for it.
What the app never does
These are the same facts as the privacy policy and the permission list in it.
- It has no servers. There is nowhere for your files or your settings to be sent, because we do not operate a backend of any kind.
- It contains no analytics, no advertising and no tracking. Nothing about how you use the app is measured or reported.
- Your files stay where they are - on the device, on your own network servers, or in the cloud account you connected. File operations run directly between your device and that storage.
- Credentials you enter for SMB, SFTP, FTP or a cloud account are encrypted on the device and are never transmitted anywhere except to the server they belong to.
- Every permission is asked for at the moment the feature behind it is used, is optional, and is explained in the privacy policy. Denying one disables that feature and nothing else.
When the warning goes away
It may never go away completely. The part that depends on recognition can weaken as more devices install the app, but the part that depends on the capabilities above stays as long as the edition uses them. This page stays either way: anyone installing a build from outside the store can meet the warning, and the page is the answer they are looking for.
Questions: GitHub Issues or sza@ukr.net.