v2.11.0

Updates can install themselves, with Shizuku.

• Install updates through Shizuku, under Settings → About, for anyone who already runs Shizuku. An update then installs with nothing to confirm: no Android install screen, and no Play Protect scan prompt. Shizuku holds an identity you granted it yourself, and an install made with that identity is not asked about, the same as installing from a computer. The row only appears when Shizuku is on the device, the switch asks Shizuku for permission the first time, and an update falls back to Android's own installer whenever Shizuku is not running. It is the same APK from the same Releases page, and Android still refuses one signed with a different key.
• Why an update asks at all, now written down in docs/INSTALL.md. Android skips its confirmation only for the app recorded as having installed the current copy, so the first in-app update asks and later ones do not. Play Protect is separate: it offers to scan every APK it has not seen, which is every release. Tapping Scan app is the quickest way through it — Google answers in seconds, and that release then installs quietly.

---

Download the APK below and open it; Android will ask you to allow installing from this source. Grant notification access on first run — that is how it sees what is playing.

Signed with the project release key; arm64-v8a, minSdk 29.