0x192 / 0x192/universal-android-debloater
Getting play store links
- Lingua principale
- Rust
- Stelle
- 19.9k
- Fork
- 1.1k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I have made a macro with MacroDroid (https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid) to fetch all system apps and build the would be link to the Google Play Store, it then checks the link leads to the app's Play Store page. If there is a link, it prints the package name and link into a text file in the internal storage /storage/emulated/0/MacroDroid/[device_model]_system_apps_play_store_links.txt and into the 'User log' tile of MacroDroid.
To get it to work, all you need to do is:
1) Install MacroDroid on your phone/tablet or other Android device.
2) Download the file: [Google_play_store_links.macro.txt](https://github.com/0x192/universal-android-debloater/files/8164745/Google_play_store_links.macro.txt)
2) Rename the file to end with .macro (remove .txt)
3) Transfer the file to your Android device and open it, select MacroDroid if prompted which will Install the macro to MacroDroid
4) Press 'Empty trigger' and wait until it says 'Finished'
5) Find and share the [device_model]_system_apps_play_store_links.txt file to UAD documentation updates
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
The issue describes a user-contributed macro for MacroDroid that generates Play Store links for system apps. To integrate this into the UAD documentation, locate the documentation files (likely in a docs/ or wiki folder) that list system apps or debloating instructions. Review the output file format from the macro and see where similar links or package references are currently documented. Add a section explaining how to use the macro and where to find the generated link list, ensuring it aligns with the existing documentation structure.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- android, rust
- Ambito
- documentation, mobile
- Tipo di issue
- Documentazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 75/100