Installing Folio

Folio 0.6.9, released 2026-10-31. Android 12 and up. 11.8 MB. Free, and the source is on GitHub.

The download comes straight from GitHub. What is in this release.

Install it

1. Open the file on your phone and allow the install when Android asks.
2. Press Home and pick Folio, or open Folio and tap Set as home app.
3. To go back, press Home and pick your old launcher again. Folio changes nothing else on your phone.

Updates on their own: tap Add to Obtainium above.Obtainium installs and updates apps straight from GitHub releases, so Folio updates like any other app without a store.

Check what you downloaded

Two different things are worth checking, and they answer different questions. The file checksumproves you have the exact bytes that were uploaded. The signing certificate proves the app was built by whoever holds Folio's key, and it is how Android tells that an update comes from the same place as the app you already have.

The app's package name is com.mccal.folio. The release APKs are the ones signed with the key below; Android will not let a build signed by anyone else update a Folio you already have.

Scanned on VirusTotal

0 of 68 security vendors flagged this file as malicious when it was scanned on November 1, 2026. The full report is on VirusTotal, and its checksum is the one below. A clean scan only shows what those scanners detect, so it is not a guarantee. The signing certificate and the permission list are the checks that tie the file to Folio and say what it can do.

The file

shasum -a 256 Folio-0.6.9.apk

The signing certificate

This one never changes. Every Folio release, past and future, is signed with the same key. If it ever differs, something is wrong and you should not install it.

keytool -printcert -jarfile Folio-0.6.9.apk

keytool comes with any JDK. With Android's build tools you can useapksigner verify --print-certs Folio-0.6.9.apk instead. Either prints the same SHA-256 digest as above.

The checksum is on the release page as SHA256SUMS.txt, so the site and GitHub can be compared against each other. Some releases also carry signing-certificate.txt, and since the key never changes, the value above is the one to compare with. Obtainium installs through Android's own installer, so the same rule applies there: an update signed with a different key is refused.

Older versions

Every release stays on GitHub. Each one's page has its own file and checksum. If a new version breaks something for you, open an issue and I will look at it.

• Folio 0.6.8, 2026-10-07, 9.4 MB
• Folio 0.6.7.3, 2026-09-29, 8.6 MB
• Folio 0.6.7, 2026-09-27, 8.6 MB
• Folio 0.6.6, 2026-09-21, 5.1 MB
• Folio 0.6.5, 2026-09-20, 4.1 MB
• Folio 0.6.0, 2026-09-16, 3.7 MB
• Folio 0.5.1, 2026-09-16, 3.6 MB
• Folio 0.5.0, 2026-09-15, 3.6 MB

Google's developer verification

Google is starting to require that developers register before their apps can be installed on certified Android phones, including apps installed from outside the Play Store. It began on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, and Google says it expands to certified phones everywhere from 2027. Google says a free account for students, teachers and hobbyists is limited to 20 devices, and that there will be an advanced way for people to install apps from developers who have not registered. The details are onGoogle's page, and they may change.

Warnings you may see

"Uncommon download"

Chrome shows this for files it has not seen before. Every new Folio release starts that way and it clears by itself as more people download it. It is not a finding about the file.

Play Protect asks to scan the app

Android checks apps installed outside the Play Store. Letting it scan is fine. Folio asks for no permission it does not explain, and every one is listed inPERMISSIONS.md with what happens if you say no.

An update will not install

A release APK cannot install over a build you compiled yourself, because the signing keys differ. Uninstall the one you built first, or keep using it.