0x192 / 0x192/universal-android-debloater
Uninstalling com.samsung.android.mobileservice breaks Secure Folder
- Lingua principale
- Rust
- Stelle
- 19.9k
- Fork
- 1.1k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**Your phone**: Samsung Galaxy Tab S3
**Describe the issue**
Uninstalling com.samsung.android.mobileservice causes Secure Folder to sign out of its Samsung Account and have no way of signing back in (tapping Sign In causes a load, then an app crash that takes you back to Secure Folder being unable to sign in). Thus, I would recommend switching it from 'Recommended' to 'Advanced' as it seems you guys have been putting packages that break things when uninstalled in there rather than 'Recommended'.
**You have a solution?**
Restoring com.samsung.android.mobileservice lets you sign into the Samsung Account and access Secure Folder once again, thankfully. It can just take a while for an uninformed user to track down this package as being the one that broke it.
**UAD log**
Not sure where I would find this, but since I was able to fix it by myself I'm not sure if it's still necessary?
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
The issue is about the classification of the package 'com.samsung.android.mobileservice' in the debloater tool's lists. Look at the code that manages the package lists, likely in a directory like 'resources' or 'data'. Find where packages are categorized as 'Recommended' vs 'Advanced'. Check if this specific package is currently in the 'Recommended' list. The fix is to move it to 'Advanced'. Test by building and running the tool to verify the change.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- android, rust
- Ambito
- mobile, tooling
- Tipo di issue
- Bug
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 65/100