Flicky
by MLM Games · GPL-3.0-only · open source
An app store for open-source apps that you can use with a TV remote. It browses F-Droid, IzzyOnDroid and other repositories, and installs and updates apps on Android TV and Google TV.
Needs:No root · Android 6.0+ · made for TV
2113 Apps is independent, not affiliated with or endorsed by MLM Games. Official sources: source code on GitHub.
- Version
- 4.5.3
- Size
- 4.4 MB
- Requires
- Android 6.0+
- Updated
- 2026-09-23
Screenshots
Introduction
Flicky is an unofficial client for F-Droid-style repositories: an app for finding, installing and updating open-source apps. Unlike most F-Droid clients, it is built for a television. Its README says “The UI is TV oriented, Android UI is secondary.” It shows up on the Android TV home screen and is driven with the arrow keys of a remote.
It has nothing to do with Flicky, Sega’s 1984 arcade game.
What it does
- Repositories. Eight are switched on from the start: F-Droid, IzzyOnDroid, NewPipe’s own repository, KDE’s nightly builds, Cromite, IronFox, Brave and CloudBurst. More are listed but off, among them the F-Droid archive, microG, the Guardian Project, Molly, Bitwarden and LibRetro.
- Six ways to install: System, Session (the default), Root, Shizuku, App Manager and Dhizuku. A second installer can be set as a fallback if the first one fails.
- Background updates, added in version 4.4.2 and off by default. Android 12 and later lets an app update other apps without a prompt only in certain cases, for example when that same app installed them, so expect prompts for apps you installed some other way.
- An option to skip alpha and beta versions, and a “suggested” label on the version Flicky would install.
To get Flicky onto a TV in the first place, see how to install APKs on Android TV. The README suggests a browser on the TV or sending the file from a phone with LocalSend.
How it checks what it installs
Before installing, Flicky checks the downloaded APK against the SHA-256 hash listed in the repository’s index, and it compares signing keys before updating an app that is already installed.
There is one difference from F-Droid’s own app. F-Droid signs each repository index, and its client carries the public key to check that signature. From our reading of Flicky’s 4.5.3 source code, Flicky downloads the index file directly over HTTPS and doesn’t check that signature. So the hashes it trusts are only as good as the HTTPS connection to each repository.
What goes online
Flicky downloads the indexes and APKs of the repositories you have switched on. When you open an app’s page, it also asks Techlore’s Plexus service how well that app works without Google services, which sends Plexus the app’s package name; we found no setting that turns this off. It downloads IzzyOnDroid’s download statistics too, but as whole files that don’t reveal which app you are looking at. Our scan found no tracker libraries.
About this file
- This is the developer’s own build, from IzzyOnDroid, signed with the developer’s key (SHA-256 fingerprint starting 4A:ED:2F:69). F-Droid also carries Flicky as builds signed by the developer, split by processor type.
- Flicky isn’t on Google Play any more (see the FAQ below).
- The 4.4 MB file runs on Android 6.0 and later, on ARM and x86, 32- and 64-bit, so it also fits TV boxes with a 32-bit system. It declares 15 permissions, 1 of which needs your approval. Installing, updating and deleting apps are among them; that is what an app store needs.
- Flicky is licensed under GPL-3.0.
What’s inside the APK
Trackers
No code matching the Exodus Privacy tracker signatures.
Native code
Runs on 64-bit and older 32-bit ARM phones.
Android versions
Built for Android 17 (target API 37).
Permissions
1 of them need your approval first.
Shizuku API. Uses the Shizuku API, so it can do ADB-level work without root once Shizuku is running. (rikka.shizuku.Shizuku$$ExternalSyntheticLambda0)
CPU types in this build: arm64-v8a (64-bit ARM, almost every phone since 2017); armeabi-v7a (32-bit ARM, older and budget phones); x86 (32-bit Intel, emulators); x86_64 (64-bit Intel, emulators and Chromebooks).
Asks you first (1)
Android shows a prompt before the app can use these.
- Write shared storage (Android 10 and older) · WRITE_EXTERNAL_STORAGE
You switch these on in Settings (1)
Special app access. Nothing is granted until you turn it on yourself.
- Install unknown apps · REQUEST_INSTALL_PACKAGES
Granted at install (10)
Low-risk permissions Android grants automatically, plus any we have not classified.
- ACCESS_NETWORK_STATE
- ENFORCE_UPDATE_OWNERSHIP
- EXPAND_STATUS_BAR
- FOREGROUND_SERVICE
- INTERNET
- QUERY_ALL_PACKAGES
- RECEIVE_BOOT_COMPLETED
- REQUEST_DELETE_PACKAGES
- UPDATE_PACKAGES_WITHOUT_USER_ACTION
- WAKE_LOCK
Defined by other apps (3)
Permissions that belong to another app or to this app itself.
- app.flicky.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
- com.rosan.dhizuku.permission.API
- moe.shizuku.manager.permission.API_V23
More Information
- Package name
- app.flicky
- Version
- 4.5.3 (build 981)
- File size
- 4.4 MB (4,365,409 bytes)
- Requires
- Android 6.0 or later
- Category
- System Tools
- License
- GPL-3.0-only
- Developer
- MLM Games
- Source code
- github.com/mlm-games/flicky
- Released
- Sep 23, 2026
- Signer SHA-256
- 4aed2f691df64a7b0fea25a6b8c80183c6dc520e049dac0178defa1d6472228f
- File SHA-256
- 6a8462c3874c0dfa3ee5cfc4288ca1df36da96cf86d5c1aece00d5d88ede1dc5
- Checked
- , against the IzzyOnDroid index · how we check · verify it yourself
Common questions
Is this APK the official Flicky release?
Yes. It is the developer’s own release of Flicky 4.5.3, byte for byte as IzzyOnDroid distributes it. Its SHA-256 matches IzzyOnDroid’s signed index, and it is signed with the certificate IzzyOnDroid records for the app (SHA-256 4aed2f691df64a7b0fea25a6b8c80183c6dc520e049dac0178defa1d6472228f).
What Android version does Flicky need?
Android 6.0 or later (API level 23). Version 4.5.3 is built for Android 17 (target API 37). Runs on 64-bit and older 32-bit ARM phones.
Can Flicky access the internet?
Yes. The APK requests Android’s internet permission. In total it declares 15 permissions, and 1 of them needs your approval first.
Does Flicky contain trackers?
No known trackers: our scan of version 4.5.3 found no code matching the Exodus Privacy tracker signatures. The scan covers known tracker libraries; it doesn’t show what data the app itself sends.
Is Flicky open source?
Yes. Flicky is released under the GPL-3.0-only licence, and its source code is published at https://github.com/mlm-games/flicky.
Does Flicky work on a phone?
It installs and runs on phones too, but the developer says the interface is made for TV first and that the phone layout is secondary. On a phone, the README recommends Droid-ify or F-Droid Basic instead.
Can I update this Flicky from F-Droid or IzzyOnDroid?
Yes, from the next release on. This file and F-Droid’s builds carry the same developer key; F-Droid’s metadata for Flicky allows only that key. But F-Droid’s 4.5.3 builds have lower internal version codes (977 to 980) than this universal file (981), so F-Droid won’t offer them as an update to this one.
Why isn’t Flicky on Google Play?
It was, but the README says Google suspended it under the “Device and Network Abuse” policy, which bans apps that install apps from outside Google Play. The developer says they won’t update the Google Play build.
Recent releases
| Version | Released | Size | Requires |
|---|---|---|---|
| v4.5.3 · this download | Sep 23, 2026 | 4.4 MB | Android 6.0+ |
| v4.5.2 | Aug 1, 2026 | 4.3 MB | Android 6.0+ |
| v4.4.3 | Jul 22, 2026 | 4.3 MB | Android 6.0+ |
Versions currently kept in the IzzyOnDroid repository. We host and check only the newest one. Full changelog.
