Canta: uninstall Android apps without root, using Shizuku
Uninstall any Android app without root (with power of Shizuku). Debloat your device as you wish, no PC required.
At a glance
- What is it?
- Canta is a Kotlin Android app that removes pre-installed and user apps through Shizuku instead of root. It is aimed at people who want to debloat a phone without a PC, and it inherits both the safety net and the blast radius of that approach.
- Who is it for?
- Canta fits someone who wants to strip pre-installed apps from a personal Android 9.0+ device without root and is willing to read the Universal Debloat List recommendations before tapping the trash button. It is the wrong tool if you have no way to activate Shizuku, if your device is an oplus model whose apps refuse uninstall, or if you cannot accept a factory reset as a possible outcome of removing a critical app.
- Can I use it commercially?
- Yes, with conditions. LGPL-3.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 13 days ago.
- What is it written in?
- Mainly Kotlin, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 29, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What Canta removes, and who is holding the phone
Pre-installed Android apps are awkward to delete. The package manager normally refuses to uninstall them for a regular user, and the usual workarounds involve a PC, an ADB shell, or root. Canta targets that gap directly: the README states it allows you to uninstall pre-installed or user apps without root, by leveraging Shizuku. The device stays unrooted, the bootloader stays locked, and no computer is required after the initial Shizuku activation.
The intended user is someone who wants to debloat a phone they own, on Android 9.0 (SDK 28) or newer. Canta is not a system-modding framework and it does not grant privileges beyond what Shizuku already has. If you have never activated Shizuku, that step is the real gate, not the install of Canta itself. The README points to the Shizuku setup guide and to an Android Police walkthrough for a longer explanation.
How Shizuku gives Canta the power to uninstall
Shizuku runs a privileged process that an app can bind to, so Canta issues package removal requests through that channel rather than through its own UID. That is the whole mechanism: no root daemon, no custom recovery, no patched system image. The README frames the dependency plainly, describing Canta as powered by Shizuku.
Two consequences follow from that design. First, Canta only works while Shizuku is running, and Shizuku itself has to be restarted after a reboot through its own activation flow. Second, the set of apps Canta can remove is bounded by what the privileged process is permitted to do, which is why the README flags an exception: some oplus apps are known to be stubborn and do not allow uninstallations, tracked in issue 338.
Canta also keeps its own record of what it removed. The README lists detection of previously uninstalled apps, even across reinstalls, as a feature, so the app can show you what is gone rather than leaving you to reconstruct it from memory. It additionally integrates the Universal Debloat List to provide safe recommendations, which is the part that matters most for anyone who does not already know which packages are load-bearing.
Installing Canta and removing your first app
The README's how-to is three steps, and the order matters. Shizuku has to be installed and activated before Canta is useful.
Install Shizuku from its Play Store listing and activate it by following the setup guide the README links. The README notes that Android 16 might need a forked version of Shizuku, pointing to the thedjchi fork. Then install Canta from one of the listed channels: F-Droid, IzzyOnDroid, GitHub releases, or Google Play.
# no shell install step is documented; get Canta from F-Droid, IzzyOnDroid, GitHub releases, or Google PlayOnce both are running, the documented workflow is short: select an app and click the trash button. There is no config file to edit and no CLI. Before removing anything, open the app description screen, which pulls from the Universal Debloat List, and read the recommendation. The README shows this as a distinct screen for a reason.
If you download an APK rather than installing from a store, the README publishes a SHA-256 certificate fingerprint you can compare against your file:
0A:26:40:31:7C:43:27:21:88:C3:E1:31:94:C1:54:60:69:1F:12:C3:9E:A1:9B:BA:72:7D:D6:7F:B5:62:89:D4The bootloop warning is not boilerplate
Canta's own README carries a disclaimer to use it at your own risk, and then a more specific line: uninstalling critical apps can cause a bootloop and force a factory reset. That is the genuine failure mode, and it is worth stating without softening. Removing a package the system depends on at boot does not produce a polite error message. It produces a device that does not start.
The distinction the README draws is between permanent bricking, which it says does not happen, and a factory reset, which it says can. That is a meaningful difference for anyone deciding whether to try this on a daily driver, but it is not a small one. A factory reset costs your data.
The oplus caveat is the second limitation, and it is the opposite problem: apps that simply will not uninstall. If your device is an oplus model, the tracking issue is the place to check before assuming Canta is broken. And if you have no way to activate Shizuku at all, Canta has nothing to offer you, because the README documents no root path and no ADB fallback.
Canta against the ADB-and-PC debloat workflow
The obvious alternative is the Universal Android Debloater, or UAD, which the README itself links to through the Universal Debloat List integration. The difference is architectural rather than cosmetic. UAD runs on a desktop and drives a phone over ADB, so the phone stays untouched and the tooling lives on the computer. Canta runs on the phone and reaches privileged operations through Shizuku on the device.
That changes the practical trade-offs. With a PC-based tool you get a keyboard, a larger screen, and a workflow you can script. With Canta you get no PC requirement, which is the point the README makes in its own description. If you are setting up a single phone at a desk, the desktop route is easier to review. If you are cleaning up a phone you already carry, or you do not have a machine to tether to, Canta is the one that fits.
Both approaches share the same hazard: they remove packages the system may need, and neither makes the decision for you. Canta's integration with the Universal Debloat List is what narrows that gap, and it is the same list that feeds the desktop tools, so the recommendations are not a Canta-specific invention.
Licence, releases and what maintenance looks like
Canta is licensed under LGPL-3.0. For someone installing the app from a store, that is mostly a redistribution question rather than a day-to-day one: if you fork the project or ship a modified build, the licence terms apply to that build. This is not legal advice, and anyone planning to redistribute should read the licence text in the repository rather than a summary.
The repository is not archived, and the last push was on 2026-09-17. Recent releases listed are v3.2.2 and v3.2.0, both dated 2026-03-01, and 3.1.2 from 2025-10-10. So the codebase has activity more recent than the newest tagged release, which is normal for a project that merges work between releases but worth knowing if you are pinning to a tag.
Upgrade cost is low by construction. There is no server component, no database migration, and no configuration to carry forward. You install a new APK and your existing Shizuku setup keeps working. The one thing to re-check after an upgrade is the certificate fingerprint if you sideload, since that is the README's stated authenticity check.
Editorial conclusion
Canta fits someone who wants to strip pre-installed apps from a personal Android 9.0+ device without root and is willing to read the Universal Debloat List recommendations before tapping the trash button. It is the wrong tool if you have no way to activate Shizuku, if your device is an oplus model whose apps refuse uninstall, or if you cannot accept a factory reset as a possible outcome of removing a critical app. Before you start, confirm the Shizuku setup guide applies to your Android version, note that Android 16 may need the forked Shizuku build the README links, and check the published SHA-256 certificate fingerprint against the APK you install.
Frequently asked questions
How do I install Canta?
Install Shizuku first and activate it, then install Canta from F-Droid, IzzyOnDroid, GitHub releases, or Google Play. The README notes that Android 16 might need a forked version of Shizuku.
How do I use Canta and Shizuku together?
Shizuku provides the privileged process and Canta issues the uninstall requests through it, so Shizuku must be installed and activated before Canta can remove anything. Once both run, the README's workflow is to select an app and click the trash button.
Is Canta debloater safe?
The README states there is no permanent bricking, but warns that uninstalling critical apps can cause a bootloop and require a factory reset. It also carries a use-at-your-own-risk disclaimer, so the safety of any given removal depends on the app you pick.
How do I use Canta without Shizuku?
The README documents no way to use Canta without Shizuku. Shizuku is the mechanism that provides the uninstall capability, and no root or ADB alternative is described.
How does Canta compare to the Universal Android Debloater?
Canta runs on the phone and uses Shizuku, so no PC is required, while the Universal Android Debloater is the desktop and ADB approach the README links to through the Universal Debloat List. Both draw on the same recommendation list.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/samolego-canta)