0x192 / 0x192/universal-android-debloater

Uninstallation commands and installation on Linux

未關閉
#815 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
enhancement
主要語言
Rust
星號
19.9k
分支
1.1k
PR 合併指標
30 天內沒有已合併 PR

描述

Hi,

First of all, great work! Adding a GUI to ADB for debloating Android is extremly useful, thanks a lot! 👍

Still, I have a two minor questions that I tried to answer by inspecting the source code, however I did not find an easy answer. I don't know whether feature request is the right form, still I found it the best matching one. Therefore, I'd like to quickly ask:

1. How are the respective packages removed? On the command line, I noticed that usually two commands are required:
```
# first, uninstall any updates that might have been installed (without this step, they might be kept)
adb uninstall

# disable the app and delete user data (adding '-k' keeps the data)
adb shell pm uninstall --user 0
```

Doing so, I never had any automatic re-installations or re-activations (as noted). Therefore, I wanted to ask whether both steps are performed here, too? If not, it might be worth extending, but I'm not an ADB expert...

2. Besides this functional issue, I am curious whether there is a way for a system-wide install on Linux, in particular for Debian-/ubuntu-based distributions?

As far as I see, there are no configuration files created (or are there any?) and besides ADB, there seems to be no real dependency, i.e. installing can be done by copying the binary to `/usr/local/bin` (or a similar path on other distros). If this is the easiest option (or is there maybe a PPA somewhere?), I think this could be realized using a small shell script that downloads the latest binary from GitHub. Do you have any interest in adding such a script to the repo? If so, I would create one as soon as I find the time for it...

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

查看解除安裝命令的原始碼,很可能在負責ADB操作的Rust模組中。檢查是否同時執行了 'adb uninstall' 和 'adb shell pm uninstall --user 0'。對於Linux安裝,檢查建置系統和現有的安裝腳本。該任務涉及更新文件或添加用於系統範圍安裝的shell腳本,但需要理解專案的ADB命令流和打包方法。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
rust, shell
領域
cli, developer-experience, documentation
Issue 類型
文件
難度
2/5
預估耗時
1-3 小時
活躍度
停滯
描述清晰度
基本清楚
新手友好度
40/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。