Install with Obtainium
The apps are not in Google Play. They are released on GitHub. Obtainium is an app that installs apps from their releases on GitHub and tells you when an update is out.
Not every app has a release yet. The apps page shows which ones do.
The names of buttons and settings can differ a little between versions of Obtainium.
What you need
- A phone with Android 15 or newer. GrapheneOS is the first target.
- Obtainium. Get it from its releases on GitHub: https://github.com/ImranR98/Obtainium/releases.
Add an app
All apps of the suite are released from one repository. Each release is
named after its app and version, for example catalog-v0.1.0. A filter
makes Obtainium look only at the releases of one app.
- Open Obtainium and tap Add app.
- In App source URL, type
https://github.com/shkriuss/shkriuss.app. - Find the setting Filter release titles by regular expression. Type
^catalog-v. For another app, use its name in lower case in place ofcatalog, for example^water-v. - Tap Add.
- Obtainium shows the newest release of that app. Tap Install.
- The first time, Android asks whether Obtainium may install apps. Allow it, then go back and tap Install again.
- Before you use the app, check that it is genuine: Verify with AppVerifier.
Pre-releases
A version with a hyphen, such as 1.0.0-rc.1, is a pre-release for
testing. Obtainium skips pre-releases unless you turn on Include
prereleases for that app.
Updates
Obtainium checks for new releases and tells you when one is out. Tap the app in Obtainium, then Update.
Android installs an update only if it is signed with the same key as the app on your phone, or with a new key that the old key approved. The second happens only when the project changes its signing key, which is announced (When the signing key changes). So once you have checked an app with AppVerifier, an update from anyone who does not hold the key cannot replace it.
Update the apps only in Obtainium. If Android asks "Update this app using Package installer?", tap Cancel. It means something other than Obtainium is trying to update the app.
When the signing key changes
Every app of the suite is signed with one key. The project may move to a new key, as a plan or after a theft. The release notes and the website then announce it, and Obtainium warns once for each app.
- In Obtainium, tap the app, then Update.
- Obtainium shows "Signing certificate mismatch". It says that installing it "will most likely fail". After a real key change, it works.
- Compare the hashes in that dialog. Every pair of characters must be
the same.
- The first line under "Downloaded certificate hash" must be the same as "Expected certificate hash". That is the key of the app on your phone now.
- The last line under "Downloaded certificate hash" must be the new fingerprint on https://shkriuss.app/verify/.
- If both match, tap Install anyway. If Android asks whether to update the app, allow it. The app keeps its data.
- If either does not match, tap Don't install. Report it privately, as the security policy explains.
- Check the app with AppVerifier, as After a new signing key says.
- If you typed fingerprints into the app's settings in Obtainium, add the new one.
Why the last line matters: until you update, the app on your phone still has the old key. Anyone who holds the old key, for example a thief, could make a file that your phone would also accept. Obtainium would warn about it in the same way. Only the last downloaded hash shows whose new key it is. Once your app has our new key, Android refuses the old key alone, and a new key that a thief made from it.
The texts of the dialog above are those of Obtainium 1.7.4.
If Obtainium says "Too many requests"
Obtainium may stop with "Error 403" for an address that starts with
https://api.github.com/, and "Too many requests (rate limited) - try
again in" some minutes. GitHub has refused too many requests from your
phone's internet address. Nothing is wrong with the app.
- Wait a few minutes, then try again.
- Or switch between mobile data and Wi-Fi, then try again.