Loading video...
Video Failed to Load
This is the new GrapheneOS boot animation. It's generated frame-by-frame using a script. It has a minimum 3.5s total runtime for the intro including a small pause. The rest of the animation gets interrupted once the device is booted to avoid any delay so there can't be an outro.
80,095 views • 9 days ago •via X (Twitter)
27 Comments

Intro 0.00-1.90: Atoms appear one-by-one and gather 1.90-2.70: Bonds expand; name fades in from 2.20 2.70-3.50: Hold Transition 0.00-1.20: Hold 0.00-0.80: Outer and split inner bonds retract; name fades 0.80-1.40: Ease into spin Loop 0.00-4.00: One rotation from initial offset

That is super cool!!! 😎

When the bad cops see it :

This looks fantastic.

Love it!

hell yeah!!!

How do you generate the frames? Script-based or something like ffmpeg?

Each frame is generated by a Python script using the Pillow library. Android boot animation zips are a series of PNG images in a zip. There are standard shaders for fading in and out. Android 17 QPR1 supports custom shaders which are only currently used by the Pixel 11 stock OS.

FFmpeg is only used to convert the frames into a video for watching it without the boot animation code. It isn't part of the process of creating the animation and is only needed so it can be viewed without needing to boot up GrapheneOS with the new boot animation zip.

love it

Not bad! 🔥

This is awesome!

that's kinda awesome

I miss the times, were i was able to set these up by myself🥲

Feels like it needs some sort of polishing but it's still great

Is there a better term for that type of graphic? It’s the opposite of having a video or rotated image asset, but I don’t know of a technical term for either.

Good mood every boot

Will this get rid of that nasty Google logo on startup?

No, that's the firmware boot splash. It will be a Motorola logo on the upcoming Motorola phones. We aren't going to bother having a transition from the boot splash into our boot animation since we'd need to carefully make that for each device including inner and outer screens.

Ok

Are you able to and/or did you get rid of the Google logo at the beginning/during the boot process?

No, that's the firmware boot splash. It will be a Motorola logo on the upcoming Motorola phones. We aren't going to bother having a transition from the boot splash into our boot animation since we'd need to carefully make that for each device including inner and outer screens.

Can you guys fix the text editing please?! If I misspell a word going back to edit is a nightmare.

generated? whats wrong with

Our script generates a boot animation zip properly sized for each device. For folding devices, it's currently sized based on the outer screen size and uses the same animation for both. It could theoretically eventually be split into 2 animations to use the full inner screen.

OOOOH i get it now cool beans

Cyanogen vibes, but better.
