A reported issue on the Universal Android Debloater Next Generation project highlights problems with uninstalling system apps via ADB (Android Debug Bridge) on non-rooted Android 17 devices.
According to the issue report on GitHub, the current “Uninstall” method for removing system apps is causing excessive problems for users. The issue submitter has requested that “Disable mode” — referred to as “Freeze” in the related AppManager tool — should become the default behavior instead of uninstall functionality.
The distinction between these two approaches is significant. Uninstalling system apps entirely removes them from the device, whereas disabling or freezing them leaves the apps in place but prevents them from running. On non-rooted devices, the more limited disabling approach may be more compatible with Android 17’s security architecture.
The request reflects a broader challenge in the Android debloating community: while power users and developers often want to completely remove pre-installed system applications they don’t use, doing so on newer Android versions with standard ADB access (without root privileges) can create stability or compatibility issues.
The issue has been formally filed in the project’s repository, suggesting that maintainers are considering whether to shift the default behavior away from uninstall operations to the less invasive disable mode. This would align user expectations with what is reliably possible on current Android versions without requiring root access.
No timeline for implementation or final decision has been announced, but the issue tracks ongoing discussion about how debloating tools should handle system app removal on non-rooted Android 17 devices.
Key facts
- ADB uninstall of system apps fails on non-rooted Android 17
- Users are requesting that ‘Disable mode’ become the default instead of ‘Uninstall’
- Disabling apps (freezing) leaves them in place but prevents them from running
- The issue was filed on the Universal Android Debloater Next Generation GitHub project