0x192 / 0x192/universal-android-debloater
borneo: Gametime, Interactive Wallpaper, and Power Touch not removed
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
**Your phone:**
**Packages:**
```
com.motorola.gamemode
com.motorola.livewallpaper3
com.motorola.motofpstouch
```
- [x] **I removed all those packages on my phone**
If not why. Leave the brackets blank and explain why.
## Document each package the best you can
**List**: `Google`|`Misc`|`Oem` (manufacturer)|`Aosp`|`Pending`|`Carrier` (isp).
**Removal**: `Recommended`, `Advanced`, `Expert` (this can break important features), `Unsafe` (this can bootloop the phone or break extremely important features).
### com.motorola.gamemode
**List**: Oem
**Removal**: Recommended
> Moto Gametime. Allows the user to block calls, quick screenshots, float social apps, etc when playing a game. https://play.google.com/store/apps/details?id=com.motorola.gamemode&gl=US
### com.motorola.livewallpaper3
**List**: Oem
**Removal**: Recommended
> Motorola Interactive Wallpaper. It's just a glorified live wallpaper feature. The user can still apply live wallpapers from other apps. https://play.google.com/store/apps/details?id=com.motorola.livewallpaper3&gl=US
### com.motorola.motofpstouch
**List**: Oem
**Removal**: Recommended
> Moto Power Touch. Allows the user to create custom actions depending on how the user presses the power button. https://play.google.com/store/apps/details?id=com.motorola.motofpstouch&gl=US
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue is about documenting three Motorola packages for the debloater tool. Look at the existing package lists in the codebase, likely in a data directory or configuration file. Add entries for com.motorola.gamemode, com.motorola.livewallpaper3, and com.motorola.motofpstouch with the provided details (list: Oem, removal: Recommended). Verify the format matches existing entries and test by running the tool to see if the packages appear correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, rust
- Domain
- mobile, tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 70/100