0x192 / 0x192/universal-android-debloater
Can't enable com.android.fileexplorer
- Lenguaje dominante
- Rust
- Estrellas
- 19.9k
- Forks
- 1.1k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**Describe the bug**
Can't enable com.android.fileexplorer on Redmi 8. Also I do not think I disabled it at all, but I understand I might have clicked accidentally so won't argue with this one
Log say it is enabled for user 999, but can't enable it for user 0 and that it can't change state from null to 1
Didn't notice any real difference with my phone, but not having an option to quickly turn the changes back troubles me a bit. Overall not a big deal, just wanted devs to know about a potential bug
**Expected behavior**
com.android.fileexplorer to become enabled?
**You have a solution?**
Sorry, to dumb
**UAD log**
2023-11-20 00:08:46 INFO [src\gui\mod.rs:457] -----------------------------------------------------------------
2023-11-20 00:08:46 INFO [src\gui\mod.rs:458] ANDROID_SDK: 29 | PHONE: Xiaomi Redmi 8
2023-11-20 00:08:47 WARN [src\gui\views\list.rs:142] No custom selection imported: Не удается найти указанный файл. (os error 2)
2023-11-20 00:08:56 ERROR [src\core\utils.rs:228] [Advanced] pm enable --user 0 com.android.fileexplorer -> Security exception: Shell cannot change component state for com.android.fileexplorer/null to 1
java.lang.SecurityException: Shell cannot change component state for com.android.fileexplorer/null to 1
at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:21969)
at com.android.server.pm.PackageManagerService.setApplicationEnabledSetting(PackageManagerService.java:21850)
at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:1826)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:210)
at android.os.ShellCommand.exec(ShellCommand.java:111)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:22447)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4882)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4104)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
2023-11-20 00:08:56 INFO [src\core\utils.rs:222] [Advanced] pm enable --user 999 com.android.fileexplorer -> Package com.android.fileexplorer new state: enabled
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
The error occurs in src/core/utils.rs line 228 when running 'pm enable' for user 0. Look at the ADB command execution logic and how package states are managed. Check if there's special handling for system packages or user 0 vs user 999. The fix likely involves understanding Android's package manager security restrictions for shell commands.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, rust
- Área
- cli, mobile, tooling
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100