ObliviOS Developer portal Project site

Home / Decisions / ADR-152

The boot screen of the Pixel targets shows the SovereignOS lighthouse picture, no longer the AegisOS boot identity of ADR-019 or the stock GrapheneOS logo.

Accepted, recorded 11 October 2026.

Decision
ADR-152
Date
2026-10-11
Status
AcceptedAccepted; the size and the alignment of the loading texture are superseded by ADR-156
Mentions
ADR-019, ADR-156
Mentioned by
ADR-156, ADR-219, ADR-227, ADR-249

1Decision

The boot screen of the Pixel targets shows the SovereignOS lighthouse picture, no longer the AegisOS boot identity of ADR-019 or the stock GrapheneOS logo.

The built-in boot renderer shows it: a full-screen mask of 1080 x 2400 with a transparent window for the loading bar, and a scrolling texture of 720 x 2160 behind it, as the rewritten patch package branding/boot of sovereignos-platform (three patches for frameworks/base: the clear colour, the 60 fps redraw, the two PNGs). The Aegis package, its generated preview and its two flat patches are removed.

The clear colour becomes (3,7,6); the 60 fps redraw stays. Supersedes ADR-019: its Aegis assets, its clear colour (18,19,24) and the Superdesign draft behind them; its analysis of the renderer and the choice of 60 fps stay valid. Design: 2026-10-11-boot-picture-design.md.

2Why and evidence

Owner decision 2026-10-11 (chat): the picture (approved on the reference page after several rounds), replacing the old package, and going on with the assets, the ADR with the specification and the patches. Owner direction 2026-10-09 (chat): rank levers by memory, so the memory of the two textures is recorded and the fallback ends in the stock images.

Measured on the build server 2026-10-11 (frameworks/base, branch sovereignos-2026091900-r2): the two PNGs equal upstream (sha256 75efac98, 73c2cb64), so the images show the stock logo on the ink clear colour, and BootAnimation.cpp differs from the file before ADR-019 in exactly the clear colour (line 803) and the redraw (lines 842-843).

Verified in source (BootAnimation.cpp, android() lines 787-860, threadLoop() lines 762-768): with no archive the renderer loads these two textures once, draws the scrolling one twice side by side from the top left of the mask and the mask over it, and the scroll is a constant 240 px/s. A boot animation archive was rejected: each frame is a full texture of about 10 MB (computed) and trimming works only against a flat colour (FORMAT.md).

A simulation of the drawing found that a scrolling texture narrower than the right edge of the window (670 px) leaves part of the bar blank at some offsets; it is 720 px and the package test fails for 480 px. The package test (BOOT-001) fails for each of six deliberate defects.

Both routes to the new files (the three patches on the stock files, and the single delta commit on the ADR-019 state) give the same blobs (BootAnimation.cpp 673b4b6d, mask d2a77598, shine dff60465).

3Consequences

Texture memory is 10.4 MB and 6.2 MB (computed) for as long as the renderer runs (about twice the mask while it loads), which includes shutdown and a userspace reboot (the same renderer runs when no archive exists). The bar moves linearly, one pass every 3.0 s; the eased motion of the design is not possible, as already accepted in ADR-019.

Boot time, memory, CPU, heat and banding on the panel are not measured (BOOT-003 to BOOT-008 are NOT_RUN); the fallback is 30 fps, then 12 fps, then the stock images. The panel height of stallion is not read. The Guardian app took its mark from the AegisOS boot asset; that asset leaves the boot screen and Guardian keeps its own copy. The product logo is not decided by this entry.

Whether the picture resembles an existing logo or trademark is not checked, and the Manrope files used for the name do not embed their licence text (OFL-1.1-RFN in the package metadata). The delta patch is landed on the build server (aa9f259f, frameworks/base, 2026-10-11, the three blobs read back equal to the package's) and the package is committed; no image has been built.

4Review when

The boot time is later, or the memory of the boot animation process higher, than with the stock images; the panel shows banding or the picture is cut on a display that is not 1080 x 2400; the patches stop applying after an upstream rebase; a product logo is chosen that should replace the picture; upstream changes BootAnimation::android().

Read from docs/governance/decision-log.md, entry ADR-152.