Easter eggs

There is a small toy hidden in every recent Android release, and it is reached the same way each time: open Settings, go to About phone, and tap the Android version row repeatedly. The tradition is old enough to have its own folklore, and the toys have grown from a single image into a small interactive game.

TL;DR#

• The easter egg lives behind repeated taps on the Android version in Settings, About phone.
• The tradition goes back to Android 2.3 Gingerbread, which showed a zombie gingerbread man next to the Android mascot.
• Early eggs were static images; later ones became small interactive scenes and, in some releases, a playable game.
• The trick works because the version row has a click counter and, past a threshold, launches a hidden activity — nothing magical, just an OnClickListener with a threshold.
• The egg is not a security boundary. It is a hidden feature, not a hidden system. Do not read it as evidence of anything else.

Mental model#

Think of the last page of a book that has a small illustration hidden under the dust jacket.

Nothing about the book's content depends on it. It is not an appendix, not a footnote, not a secret chapter. It is a deliberate gift from the people who made the thing, placed where only the curious will find it.

Android's eggs are the same: they are part of the shipped system, they use the ordinary activity machinery, and they are entirely optional. The interesting part is not that they exist but that they have persisted through a decade of platform rewrites, which tells you something about the culture of the team that makes Android.

Where the analogy breaks#

A hidden illustration does not require the reader to do anything. Android's egg requires a specific sequence of taps, and in some releases a second gesture after the first. That is not concealment for its own sake; it is a small puzzle, and the puzzle is the point. The mechanic is closer to a Konami code than to a hidden page.

The big picture#

The valuable thing to notice in that diagram is span: the eggs survive every architectural change. Dalvik to ART, Treble, Mainline, GKI, the Compose transition — the toy is still there. A feature that survives four platform reorganisations is a cultural commitment, not an accident.

Deep dive#

The tap in About phone#

The path has been stable for years:

1. Open Settings.
2. Open About phone (on some devices, About device or About tablet).
3. Find the row showing the Android version.
4. Tap it repeatedly. Most builds use seven taps.unverified(The exact tap count varies by release and is not part of a documented API)

Past the threshold, the screen changes: a large version graphic appears, and a further tap or gesture opens the egg itself. The exact gesture after the first stage varies by release, which is part of the game.

The tap counter is the reason the interaction is discoverable-but-not-accidental. A single tap does nothing, which is what you want for a settings row. Seven taps is unlikely enough that no one triggers it by mistake and memorable enough that the curious will try.

A short history of the toys#

The tradition started small and grew.

Android 2.3 Gingerbread (API 9) is the first release with a recorded easter egg: an image of the Android mascot standing next to a zombie gingerbread man, with more zombies behind.¹ It was a picture, not an interaction.

Android 3.0 Honeycomb (API 11) followed with a Tron-themed image, continuing the pattern of a single designed graphic per release.

Android 4.x kept the tradition alive through the Holo era, and by then the egg had become something users expected to look for after an upgrade.

Android 8.1 Oreo (API 27) is recorded with an official Oreo cookie picture, which is a neat example of the egg reflecting the dessert name of the release even as the platform was moving toward modularity.¹

Later releases escalated from images to small scenes, and some added a playable game after a second gesture.unverified(The sequence of eggs after Android 8.1 is not covered by a single primary source used on this site) The pattern is consistent: the egg is a small piece of craft, built with the same UI toolkit as the rest of the system, shipped to every device.

The eggs and the release cycle#

An egg is designed at the same time as the release it belongs to, and it is part of the release's identity in a way that a feature list is not. That is why the eggs are one of the few places where a release's personality shows: a zombie gingerbread man is a joke about a version name, and the joke only makes sense in that release.

The tradition also shows how a platform's culture survives reorganisation. The eggs were designed by a small team in the Dalvik era and are still shipped by a much larger organisation that has replaced the runtime, split the vendor interface and moved to a modular update model. Nobody has a roadmap item for the egg; it persists because it is part of how the team thinks about the product.

How the trick is built#

The mechanism is ordinary Android, and reading it is a good exercise in how a hidden feature is just a feature.

A preference row in Settings is a view with a click listener. The listener increments a counter. When the counter passes a threshold, the code starts an activity. The activity is not exported to the launcher, has no icon, and is not listed in the app drawer, so the only way to reach it is the tap sequence.

Two details make it feel like a secret rather than a bug:

• The counter resets. If you stop tapping, or leave the screen, the count resets, so the sequence must be deliberate.
• The visual feedback is delayed. Nothing visible happens until the threshold, so the first few taps feel like nothing — which is exactly the point.

This is the same pattern as a hidden debug screen in any app: a threshold on an existing control, then a startActivity to something not exposed in the UI. Once you have seen it, you notice it everywhere.

Reading the egg as a system exercise#

The egg is a good first target for reading the platform, because it is small and self-contained. It has an entry point (the version row), a state change (the tap counter), and a destination (the hidden activity). That is the same three-part shape as a much larger feature.

A reading exercise that works: find the version preference in the Settings app, find the click handler, and follow the startActivity call. The path is short enough to finish in an afternoon, and every step is a piece of the framework you will meet again: a preference screen, an OnPreferenceClickListener, and an activity that is not exported.

The other useful exercise is to ask why the destination is not exported to the launcher. The answer is that it does not need to be: the only intended entry point is the tap sequence, and an exported activity would add an attack surface for no benefit. That reasoning applies to every hidden screen in the system.

What the eggs tell you about the platform#

Three observations are worth more than the toys themselves.

They ship with the system image. The egg is part of the platform build, not an app installed later. That means it goes through the same build, review and compatibility processes as everything else — a small joke that has passed the same gates as the settings app.

They use the public toolkit. The eggs are built with the same views, activities and resources as ordinary system UI. They are a useful reminder that "system app" does not mean "special machinery"; it means "ships on the system image".

They survive reorganisations. The tradition outlasted Dalvik, the Treble split, Mainline and the move to Compose-first. Culture is one of the more durable parts of a platform.

How it evolved#

The UI rows from Gingerbread to Oreo show the visual eras the eggs lived through: pre-Holo, Holo, Material. The egg changed style with each era because it was built with the toolkit of its time.

Under the hood#

• ‹›↗the Settings app, where the About phone screen and the version row live
• ‹›Activity.java↗the startActivity path any hidden screen uses
• ‹›↗the platform resources a system UI screen draws from

Curiosity corner#

• The first egg was a picture. The zombie gingerbread man did not do anything; it was a joke rendered as an image.
• The tap count is not a standard. Some builds use seven, some differ, and the count is a convention rather than a documented contract.
• Developer options is a different gesture. It is a separate hidden feature, reached from the build number row, and it is documented. Confusing the two is the most common egg myth.

Try it#

$ adb shell getprop ro.build.version.release
adb shell getprop ro.build.version.sdk
adb shell am start -a android.settings.DEVICE_INFO_SETTINGS

Illustrative output — values differ per device.

Build it#

B01 — Hello lifecycle shows the activity and lifecycle machinery that a hidden screen uses; once you have built one, the egg stops looking magical.

Check yourself#

Sources#