Repository navigation
Keyflow 1.6.4 · Your playlist first, a visible download queue and smaller APKs
A first start that begins with your own playlist, a download queue you can see, smaller APKs and a lighter touch while you play.
- On the first start Keyflow asks for a YouTube Music playlist before anything else. While its songs become levels in the background, you can warm up with the three built-in songs; their home screen shows when your playlist's first level is ready and takes you there with one tap.
- Settings › Download queue lists every song still to be downloaded and prepared, in the order the worker takes them, with its stage, an estimate of when it's ready, or what it waits for. Locked levels keep their hidden titles.
- Download ahead and Download all wait for Wi-Fi by default, and can also wait for a charger. Your next two levels and Arcade always download. They start again on their own when Wi-Fi or a charger comes back while Keyflow is open.
- While a game is on screen, preparation runs at about half speed so the game stays smooth. A song you're waiting for, and the next song of an Arcade run, aren't slowed.
- Wait estimates learn download time and charting time separately, and take each song's length into account.
- Chords are harder to get: linked tiles count as tapped together only within 35 ms of each other (was 65 ms).
- A song that fails on its own no longer stops the rest of the queue; only lost connections pause it.
- Releases come as one APK per processor:
keyflow-1.6.4.apkfor phones (about 170 MB, was 218 MB) andkeyflow-1.6.4-x86_64.apkfor emulators. The app is shrunk with R8 and starts faster with a baseline profile. - The chart models are read straight from the APK instead of being copied out, saving about 95 MB of storage. ONNX Runtime's start-up telemetry is removed, so the engine loads only when a song is charted.
- Large playlists are read from disk only when they change, and preparation progress is no longer written to the playlist file every percent.
Development releases may reset app data. APKs, source archive and SHA-256 checksums are attached by the release workflow.