On-device boot animation management
The module curls to webhook.site - I want some dopamine on occasion. Data Sent:
- Your Magisk Version - to ensure compatibility with most people
- Your OS Name - so I don't get excited about my own machines
- The Module Version - literally just tracking, sorry. (I also use this data to distinguish more people, so I can get my dopamine without lying to myself)
- Pick from a curated list of animations packed straight from my
~/Documents/custom_bootanimations/bootanimationsfolder, because I'm not risking more potential code execution vulnerabilities! - (if you don't know how to drop zipfiles and run a few shell commands, you shouldn't be installing untrusted modules anyway.)
- Tested on LineageOS 20 for
merlinxandnx659j - Magisk on
/data/adb/magisk-/sbinmight work, but isn't officially supported.
- If you’re unsure which animation you want, flash the module first.
- Create the config file first with just the
telemetry=falseline if you're privacy-conscious - If you take privacy even more serious, remove the curl altogether and build the module yourself.
- Create a folder at:
/storage/emulated/0/config - Inside that folder, create a config file named:
bootanimation.txt - In the file, use this format:
anim=animation telemetry=false|true - If you haven’t flashed the module yet, do so now. Otherwise, hit the action button in Magisk Manager to apply the animation.
- (I'm not planning to implement inotify, so manual triggering after every settings change it is! :/ - assuming nobody wants to make a PR)
- My code is MIT licensed. Most of the boot animations are borrowed or fall under "I don't care what people do with my work."
My personal animations are also MIT licensed, but I'd really appreciate it if you ask me before using them — or at least give me a heads-up, please? 🙂
(Sorry if I publish a broken build)